Forum Discussion
SRSv2 Calendar Issue only on Lenovo SmartHub 500 system
Does it actually fail to fetch the calendar long term … I assume so? We hit this issue often with one customer but it is temporary as the message goes away after a few seconds, and we don't see issues with the calendar showing up if the room is booked. We haven't tried to investigate as it self fixes so can't offer any great pointers.
However, Exchange 2010 used for auto discover is not supported. We recently had to update the local hosts file to get around autodiscover not allowing a redirect from Exchange 2010 to Exchange 2016. You could add a local hosts file entry in the SRS to point to Exchange online to cover this off if that is your issue. Note we also got warning messages saying Exchange 2010 wasn't supported which alerted us to this issue, but it could have been the SP wasn't up to date also as the Exchange version was being decommed at the time.
https://docs.microsoft.com/en-us/skypeforbusiness/manage/skype-room-systems-v2/room-systems-v2-operations
Jed
Does it actually fail to fetch the calendar long term … I assume so? We hit this issue often with one customer but it is temporary as the message goes away after a few seconds, and we don't see issues with the calendar showing up if the room is booked. We haven't tried to investigate as it self fixes so can't offer any great pointers.
However, Exchange 2010 used for auto discover is not supported. We recently had to update the local hosts file to get around autodiscover not allowing a redirect from Exchange 2010 to Exchange 2016. You could add a local hosts file entry in the SRS to point to Exchange online to cover this off if that is your issue. Note we also got warning messages saying Exchange 2010 wasn't supported which alerted us to this issue, but it could have been the SP wasn't up to date also as the Exchange version was being decommed at the time.
https://docs.microsoft.com/en-us/skypeforbusiness/manage/skype-room-systems-v2/room-systems-v2-operations
Jed
Hi Jed,
Thank you for the reply.
I agree with the Exchange 2010 part and it not being supported, mainly the redirection that it does causes the issues.
The local IT guys on site have forced the autodiscover to use Office 365 services and it connects as it should.
I think they must have had the issue before with another device and hadn't told us their workaround even though it was one that we suggested initially after discovering the Exchange 2010 in the middle of the loop.
Thanks again,
Dan
