Hi
After update applied on 2014.02.07 (now is all up to date) we started to get error messagemaxConferencesExceeded whencreating a new conference.
We run Lync since 2 years now (starting to Lync 2010) and this only now started to happen (2014.02.07).
After much investigation we found that in the RTCLOCAL [rtc].[dbo].[Conference] all conferences created after 2014.02.07 have NULL ExpiryTime.
According to documentation when creating a conference using UCMA (go to definition of the property ConferenceScheduleInformation.ExpiryTime) ExpiryTime, if left NULL it will default to 8 hours.
However, now, if left NULL the conferences will never clean-up and server will eventually hit the limit.
If we set the ConferenceScheduleInformation.ExpiryTime to 1h in the future for instance, then the conference is deleted in 1h as expected.
However, we are up to 7600 conferences with NULL ExpiryTime (global maximum is 10000).
We are looking to manually set the ExpiryTime in the past into the RTCLOCAL [rtc].[dbo].[Conference] table.
Question is: will we break anything
Regards
Dan