Forum Discussion
MasoodRaufi
Dec 13, 2021Copper Contributor
couldn't sign into microsoft teams room 4.10.10.0 but calender is synced
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 (Micr...
kconway
Jan 20, 2022Copper Contributor
TheGrahamWalsh 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.
- Jan 22, 2022
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.
- kconwayJan 25, 2022Copper Contributor
TheGrahamWalsh I wish I was having the same luck. Working with Microsoft support now, we've done remote sessions and I have sent them a ton of screenshots and log files. Changed settings, modes, accounts, and still spinning my wheels. I feel like this should be something simple, but they're scratching their heads too, so we'll see.
- kconwayJan 28, 2022Copper ContributorAlright it resolved itself. Working with Microsoft, we checked all of the settings for the device and the account, everything was correct. We confirmed the registry values and pulled the log files from the Teams Admin center. Everything was connecting except for Teams, but no valuable error logs were found. So a few nights ago it did the normal 02:00 restart and update process, but this time it got the update that brought in the Cortana feature, and it all started working. Talked with Microsoft some more and they do not believe the update fixed it, but that it was coincidental. They believe the actual issue was propagation of the account with their systems and something that neither they nor I could change or impact. It was not propagation of the user or resource account, but rather the MTR system software. The support tech said that it was something he had another ticket this week to deal with, that getting everything set up and seeing the rest of it working, you have to just let it sit online for about a week and it will resolve itself. Not ideal, but thankfully I was not in a position that this impacted my business.