This is just a brake on runaway meetings, so if someone locks their workstation and goes on vacation while signed into a meeting the meeting will eventually end. However, you can immediately reactivate a deactivated meeting. It’s like a server-driven version of the exit-and-end-meeting presenter command. Deactivation and expiration are related, but different.ĭeactivation is when the server will forcefully shut down a meeting. However, this was only half of the story. These settings apply to Lync on-premises also, but I wanted to know if they could be modified. I knew I’d seen something mentioned about modifying when conferences end, and Brian Ricks reminded me of Set-CsUserServicesConfiguration. With this cmdlet, we can set a parameter -DeactivationGracePeriod that allows us to set the maximum amount of time that a meeting can remain active. To clarify, meeting activation is whenever a conference is accessed by a participant. For a recurring scheduled meeting without a specified end date, the expiry time is 6 months after the last meeting activation.For an ad hoc IM or A/V conference, the expiry time is 8 hours.For a recurring scheduled meeting with an end date, the expiry time is the scheduled end time of the last meeting occurrence plus 14 days.For a one-time scheduled meeting, the expiry time is the scheduled end time plus 14 days.In the first instance, I managed to find this about conference expiration in Office 365: I came across this recently when I had to conduct a bit of a deep dive into how Lync conferences behave when they effectively reach “end of life”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |