Compartilhar via

Managing Meeting Life Cycles

  • Artigo

Tópico modificado em: 2009-03-05

Meeting life cycles are controlled by the following processes:

  • Deactivation. When you deactivate a meeting, you end the instance of the meeting, but the meeting continues to exist in the database and can be reactivated and rejoined.
  • Expiration. When you reach the expiration time, the meeting and all associated meeting content are deleted from the database. The default expiration time is 14 days.

Meeting deactivation and expiration are primarily automatic processes in Office Communications Server 2007 R2. However, there are three WMI settings that the administrator can use to modify the meeting deactivation and expiration processes.

For conference deactivation, there are two pool-level WMI settings that are stored as properties in the MSFT_SIPMeetingScheduleSetting WMI class in the root\CIMV2 namespace, as described in Table 1.

Table 1. MSFT_SIPMeetingScheduleSetting WMI class in the root\CIMV2 namespace

Property Name Type Default Value Description

UnAuthenticatedUserGracePeriod

Integer (0~60)

10 (minutes)

Grace period allowed for anonymous or federated users to stay in the meeting without any authenticated user in the meeting.

MaxMeetingLength

Integer (0 ~ 8760)

24 (hours)

Maximum length of any meeting without join activity.

For conference expiration, there is one pool-level WMI setting that is stored as a property in the MSFT_SIPDataMCUCapabilitySetting WMI class in the root\CIMV2 namespace, as described in Table 2.

Table 2. MSFT_SIPDataMCUCapabilitySetting WMI class in the root\CIMV2 namespace

Property Name Type Default Value Description

ContentExpirationGracePeriod

Integer (0~365)

14 (days)

Grace period in addition to the expire time, after which the Web Conferencing Server should clean up content for a conference.

Use Windows Management Instrumentation Tester (that is, WBEMTest) and the following procedure to modify deactivation and expiration WMI settings.

To use WBEMTest to modify deactivation and expiration WMI settings

  1. Log on to a server with Office Communications Server 2007 R2 administrative tools installed, as a member of the RTCUniversalServerAdmins group or an account with equivalent user rights.

  2. Click Start, click Run, type wbemtest, and then click OK.

  3. In the Windows Management Instrumentation Tester dialog box, click Connect.

  4. In the Connect dialog box, in Namespace, type root\cimv2, and then click Connect.

  5. In the Windows Management Instrumentation Tester dialog box, click Open Instance.

  6. In the Get Object Path dialog box, in Object Path, type the WMI class name (that is, MSFT_SIPMeetingScheduleSetting or MSFT_SIPDataMCUCapabilitySetting), and then click OK.

  7. In the Object editor dialog box for the WMI class, click Instances.

  8. In the Query Result dialog box, double-click an instance.

  9. In the Object editor dialog box for the WMI class, double-click the property you want to edit in Properties:

    • If you specified the MSFT_SIPMeetingScheduleSetting WMI class in step 6 of this procedure, double-click UnAuthenticatedUserGracePeriod or MaxMeetingLength.
    • If you specified the MSFT_SIPDataMCUCapabilitySetting WMI class in step 6 of this procedure, double-click ContentExpirationGracePeriod.

  10. In the Property Editor dialog box, change the value to the new value in the Value box, and then click Save Property.

  11. When you are finished with the editing, in the Object editor dialog box, click Save Object.

  12. Close all dialog boxes, and then close Windows Management Instrumentation Tester.

  13. To verify that the change was applied, open Event Viewer and look for event ID 56015.