Microsoft Teams Room version 5.2.115.0 bug: Teams Room account can't login

I will follow this. thanks

100% agreed on this, an automatic roll out of an update that breaks our Teams Room and the fix is to wipe your device and effectively leave it in an unmanaged state with the advice not to add any custom policies, security etc as it will leave the device in an unsupported state is ridiculous. In my case due to our internal policies we will need to create a new network segment to separate these devices from our internal network as we can not stand over them and see they are sufficiently secured/hardened for our internal network.

I want to provide some information that will hopefully help other folks having this same issue. Through our own reverse engineering and with info Matt Slomka and other Microsoft Engineers provided from our support case we figured out what our issue was. For starters with the introduction of version 5 the MTRs will try to run "New Teams" if they have the app installed and the required WebView 2. You can tell if your MTR is running new Teams if it has the QR code on the main screen and you haven't specifically set a setting to disable that. Prior to 5.2.115 it was able to fall back to using Old Teams but the 5.2.115 requires New Teams only and if it can't run it this is when you will see this problem. It installs New Teams as a separate MSIX package. Apparently at some point a setting got pushed from Intune to our MTRs to block non admin installs of app packages. Its interesting that setting did not stop it from updating the normal Teams room app to 5.2.115 but apparently it wasn't able to install this separate MSIX package that installs "New Teams".

This article describes the problematic setting our MTRs had https://petervanderwoude.nl/post/prevent-non-administrator-users-from-installing-windows-app-packages-via-windows-10-mdm/.  We are setting the affected devices back to 0 for that setting so they can install the New Teams package and will work on 5.2.115.

Microsoft may very well be correct in saying that it's something in the customer environment in causing this issue. We didn't think we had done anything like that but we had, probably inadvertently by sending a setting from Intune to those devices they should not have received that blocked needed app installs.

You can also look in the TeamsUWP log files on the device and look for errors pertaining to Teams21 and for us it showed that the package was missing.

Brandon

So if we have New Teams installed MTR 5.2.115.0 should work?

So if we have New Teams installed MTR 5.2.115.0 should work?

There is a specific Teams Room version of New Teams that has to be installed it seems. Microsoft has given me the process to manually sideload it in case the automated install has failed. But even doing it manually with these instructions didn't work until we removed the setting that was blocking non admin package installs because the skype user didn't have permission to do the install. And after fixing that setting a manual install isn't really needed because it should be able to install automatically as it is supposed to.

You can run this command as admin on a device to see if you are missing the New Teams package:

Run logged on as adminstrator:

Get-AppxPackage -name *teams* -User skype

If the package is missing the output will be blank.

How to Side-Loading Package via Impersonation:

Logged on as Admin:

1. Download PSTools
2. Download the https://statics.teams.cdn.office.net/production-windows-x64/24241.400.3089.3663/MSTeams-Rooms-x64.msix

Procedure:

1. Copy the msix package in as easily accessible directory (we will be using C:\Users\Skype for this)
2. Place PSTools in as easily accessible directory (we will be using C:\Users\Admin\PsTools for this )
3. Launch PSExec (this is launching a powershell session on the Skype user. DO NOT SKIP)
   • Open an admin powershell
   • Run C:\Users\Admin\PsTools\PsExec.exe -u Skype powershell
   • Press enter when prompted for the password - if you get an error that blank passwords are not allowed, set the HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LimitBlankPasswordUse key to 0 and try running PsExec.exe again.
4. Run cd C:\Users\Skype in the powershell prompt that comes up
5. Run WHOAMI (one word), it should output COMPUTERNAME\Skype => this shows you are signed in as user Skype
6. Run Add-AppxPackage .*packageFolder*packageMSIX\ (or the folder where you put in the MSIX before)**
7. Restart