Thursday, November 13, 2008 11:46 AM
Can I confirm if the following is by design and if there is anyway to limit this?
When a number of anonymous users are invited to a one time scheduled live meeting and the meeting organiser leaves (+10 minutes) or terminates the meeting the anonymous users are kicked out.
However I have observed that the anonymous users can then go back into the live meeting and chat or use voice\video subsequently for another 10 minutes before they are kicked out, though they can then repeat going back in.
Is this correct default behaviour?
How can I limit this?
Thanks for any advice.
Wednesday, April 08, 2009 8:11 AMAlistair:
This is the design behavior and is controlled by the UnauthenticatedUserGracePeriod WMI setting documented in the OCS Administration Guide (see below)...
Managing Meeting Life Cycles
Meeting life cycles are controlled by the following processes:
· Deactivation. Deactivating a meeting ends the instance of the meeting, but the meeting continues to exist in the database and can be reactivated and rejoined.
· Expiration. When the expiration time is reached, 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. 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 12.
Table 12. MSFT_SIPMeetingScheduleSetting WMI class in the root\CIMV2 namespace
Grace period allowed for anonymous or federated users to stay in the meeting without any authenticated user in the meeting.
(0 ~ 8760)
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 13.
Table 13. MSFT_SIPDataMCUCapabilitySetting WMI class in the root\CIMV2 namespace
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 (WBEMTest) and the following procedure to modify deactivation and expiration WMI settings.
- Proposed As Answer by Rick000983838383 Wednesday, April 08, 2009 8:12 AM