Wednesday, March 12, 2008

Content Life Cycle OCS and Tools

Again and again questions about how OCS deals with "Content Life Cycle" are reaching me. And it isn't very strange because there is no "very" clear information on how OCS deals with expiration dates etc. Except when you purchase the OCS Resource Kit from Microsoft Press ;-)

Where can you set an expiration date within a meeting? In Live Meeting Console you can't. When using the web scheduler can.

Settings referring to this configuration items are found within the following WMI classes:

  • MSFT_SIPDataMCUCapabilitySetting
  • MSFT_SIPMeetingScheduleSetting

The meeting expiration within OCS is out of the box: 14 days you can find a integer ContentExpirationGracePeriod This property type typically describes the grace period in addition to the expire time after which the Web Conferencing should clean up content for a conference.

The maximum lenght of any meeting without any activity is covered in the MaxMeetingLength property. The OOTB value is 24 hours.

The UCAuthenticatedUserGracePeriod property defines the grace period allowed for anonymous or federated users to stay in the meeting without any authenticated user in the meeting.

You can change all values above according to your organizational needs.

The tools to make encrypted meeting content on your server more viewable are included within the OCS Resource Kit (DMInsider, DMHash and DMDel)


Anonymous said...

Personally I am very dissapointed about the OCS Resource Kit Book.

They just grabbed all the "blablabla marketing" 100+ pages-of-useless-documents-with-5pages-of-valuable-info and they wrote a preface+glossary around it. It contains lot of errors and misinformation, and misses a lot of areas, where one would need more technical info (I am not really interested in 20 pages of detailed and encrypted SIP message flows, and the telephony part / RCC is finished on 5-10 pages only. Audio Conferencing Providers support is 10 rows: yes we support it. Period. But how to configure??

One would expect that if a question pops up about interopability or any supported feature or scenario, one just have to open the book and will find the necessary info. But not in our case. Even the basic client feature-set table contains a few errors, what should I expect from complex RCC to EV scenarios.

Definitely have to issue a 2nd (fixed) edition!

Joachim Farla said...

Thanks for your feedback I will forward your comments to the OCS Resource Kit guys.

davetechsearch said...

out of box, for a 1 off meating is 14 days from schedule date (from what we've just noticed). We have a user that scheduled a meeting on Dec.19, 2008. The start date for the meeting was to be Jan 12. The meeting expired on Jan. 2 (exactly 14 days after scheduling). How and where does one change this?... changing ContentExpirationGracePeriod does not resolve this particular issue (not sure if anybody else noticed/experienced this)... this has happened to us a couple of times now... user went in a couple days before the meeting to upload content... expired... quick fix was to edit the table on the back end (dbo.Conference in the rtc database) in order to allow the user back into the meeting... where can this number (14 be cranked up?!... no, the resource kit does NOT say).

Sanjay said...

@ davetechsearch... Did you get solution for this? Even I have Issue where my one time live meeting is expired before start date/time.created on sept 15 , scheduled for Oct 18th .But got error as live meeting is expired when tried to join on oct 18thCan anyone suggest?