couldn't sign into microsoft teams room 4.10.10.0 but calender is synced

Occasional Visitor

Hey everyone !  Although I have installed / updated the teams rooms app to the latest version and the calender is syncing correctly which means I am able to see the booking but still the device (Microsoft Surface) which has teams installed on it is not being signed in to teams and says Couldn't sign in to Microsoft teams. The other thing is that the "Join" button is disabled whenever I try to join the device into the meating.

 

Here comes some pictures for more info 

 

I would really appreciate any help.

IMG_20211213_125018.jpgIMG_20211213_124400.jpg

 

 

Thanks best regards

Masood

4 Replies

@MasoodRaufi 

 

@Graham Walsh may be able to help on this one - he has extensive experience on Teams Room and may have seen it before in the past and so identify a root cause

 

Best, Chris

Thanks @Christopher Hoard 

Did it work before @MasoodRaufi ? I would double check the licenses on that account and ensure you can sign in on a browser on the admin side with no issues or 2FA in preventing the MTR app signing in.

@Graham Walsh I have the same issue here on a new system. Four others work without issue and the account can sign in to the Teams online system or go to other systems without issue. But no account can get past the Teams login on this one HP system. I did some light reading through the Teams admin logs from the device and found only one error, repeatedly. "- info -- Failed to getHomeUserUpn value with error: Message: Unable to open RegKey: 0x2" It is running Windows 10 20h2 and the 4.10.10.0 release. Looking through Azure, it is able to authenticate with Skype and Exchange but just can't get past the Teams part, which is very frustrating. I have a ticket in with Microsoft as well, but I don't expect a fast response. This system is new, and no accounts have been able to fully get through. All licensing matches the working systems. I even got HP to send a recovery drive and reimaged the system, but it installed Windows 1803, so after confirming 20h2 is supported with 4.10.10.0 I manually updated it. Windows first then using the PS1 from Microsoft to run the app update. 

@kconway Funny enough I had seen the exact same thing on a system. It was working fine but decided to re-image the device.  It went back to 1803, it wouldn't sign in as it was 4.0.51.0 which I knew, as anything 4.8 or lower won't work.  Updated to 4.6.x, installed 1903, then 4.10.10.0 and 1909.  It just wouldn't sign in, quick look at the event logs didn't show anything.  Changed tenants and accounts, no difference.  I then started to leave it and let the nightly updates run, and suddenly it has signed in.  I do not know what update was applied or what, but it's working now.