Teams Room System Unable to Fetch Calendar after the update to 4.3.21.0
We are starting to get an issue after the Teams Room System Update 4.3.21.0. error on the display cannot fetch calendar (skype sign in is fine) We did a trace and we don't see anything block from our environment to Microsoft. Anyone else experiencing the same issue? pretty sure because of the update, the rest of our teams room system with the older version is fine.
Skype Room System V2 Unable to sign in
Hi, This environment has 2 accounts but one account unsuccessfully tested on the Skype Room System return with an error prompting that "We can't sign you in because server unable to be reached or the server is incompatible with the device" The device(Hub) is connecting to WiFi with no firewall blocking. From the Skype Room System logs, I was able to find "Exchange: Autodiscovery failed, SignIn: Unhealthy" Any suggestion?Can't admin one person in Lobby from SRS
HI, We use Logitech Smartdock with SRS V2 to connect to MS Team meetings. The issue is that when there is just one person in the lobby waiting to be allowed, the "Admin all" button does not show up on the SRS screen. And there is no other way to admit the person like clicking on the person's name. As soon as there are 2 or more people waiting in the lobby, the "Admin All" button becomes visible. I am not even able to disable the Lobby feature from the Meeting policies in the Teams Admin center as I get an error "We can't create the Meeting policy right now but try it again later" when trying to save an existing or new policy. I am working with MS Support on this error but till now they have no clue.Skype Room System - Cannot fetch calendar
Hi, We have a about a dozen Skype Room System units (both the Surface and Lenovo Hub 500) deployed in our environment, installed with SRS version 4.0.64.0, Windows version 10.0.16299.785 and they all have the error message "cannot fetch calendar". Some background history: This message appeared during a Exchange on-prem -> cloud migration, and was expected because of our autodiscover records still pointing to the on-prem server. It was also expected that it would be fixed by itself once we updated our autodiscover records to point to the cloud, but unfortunately this did not solve the problem. We are currently running on a Skype for Business 2013 server on-prem, and Exchange Online (hybrid) Troubleshooting: I first thought this was autodiscover related, because of what i mentioned above. I have tried to manually add the cloud autodiscover server to the hosts file a few of the systems, that did not help. Further step was checking that the licensing in Office 365 is ok, all accounts have E3 license. Installed Office 365 proplus on a few of the systems, to check if sign-in to to a normal desktop version of SFB worked and it did. The SFB client read the calendar and everything worked as it should. Created a new meeting room account in the cloud Re-installed one of the systems (worth a shot) Now, if i try with a room mailbox account only existing on our on-prem server, it works. I have looked through many SRS articles here with the same problem, and i noticed someone mentioned that it was ADFS related, but i am not sure where to look. At this point i am lost, and am hoping one of you brilliant people could help me out. Also, happy new year!
SRS V2 with Surface Pro 6
Does Skype Rooms Systems v2 work with the Surface Pro 6? I don't see it mentioned anywhere in the documentation but wondering if that it just hasn't been updated or if it is incompatible. Our two primary vendors, as well as the Microsoft store, are showing as out of stock on the old 5th gen Surface that is shown as compatible. If it is not compatible is there any estimate on when SRS might be updated to support the SP6?
