Surfacehub2s upgraded to W11 - Unable to log in email address to Microsoft Team Room

To address the issues you're facing with logging into Microsoft Teams Rooms on your Surface Hub 2S after reimaging, here are some steps and considerations:

1. Kiosk Mode Limitation: Microsoft Teams Rooms operates in a kiosk mode, which restricts access to the underlying operating system. To run PowerShell scripts or make changes outside of this environment, you typically need to access the device in a non-kiosk mode. This may involve temporarily disabling the kiosk settings or using a different method to access the system.
2. Logging into Skype Profile: Unfortunately, logging into the Skype profile outside of the kiosk environment is not straightforward. You may need to reset the device to factory settings and set it up again to ensure that the Teams Rooms application can log in properly. This may also involve ensuring that the device is correctly enrolled in your domain and that all necessary licenses are applied.
3. Licensing Requirements: Microsoft Teams Rooms does require appropriate licensing to function correctly. Ensure that the device has a valid Teams Rooms license assigned to it. This can often be managed through the Microsoft 365 Admin Center.
4. Domain and User Settings: When entering your domain and username, ensure that you are using the correct format. For example, if your domain is [Moderator note: personal info removed], the username should typically be entered as [Moderator note: personal info removed]\username (with a double backslash) or just username if the domain is already specified in the settings.
5. Troubleshooting Steps: If you continue to encounter issues, consider the following:
   • Verify that the device is connected to the internet and can communicate with Microsoft services.
   • Check for any updates to the Teams Rooms application that may need to be applied.
   • If possible, use the working Surface Hub 2S as a reference for settings and configurations.

If these steps do not resolve the issue, you may need to consult Microsoft support for further assistance, especially regarding the specific error messages you are encountering during the login process.

References:

• Migrate Surface Hub 2S to Windows 11 via Migration Launcher app
• Prepare your environment for Surface Hub

Dear @Carino, Heriberto, 

Thank you for posting your question in the Microsoft Q&A forum.   

Based on my understanding, you want to log into the Skype profile – the account running in kiosk mode on Teams Rooms – to open PowerShell and run a command. In Teams Rooms / Surface Hub: based on the article I read, to run PowerShell, you must use the Administrator account, not the Skype account. First-time setup for Surface Hub running Microsoft Teams Rooms on Windows

You mentioned, 'I have one other Surface Hub 2S that is working fine right now,' so does that device have a license? I found this article which states that Microsoft Teams Rooms devices need specific licenses like 'Microsoft Teams Rooms Pro' or 'Microsoft Teams Rooms Basic' to work. Other user licenses won't function with meeting devices. Meeting devices without a Teams Rooms license will be unable to sign in until they obtain one. Therefore, all devices running Microsoft Teams Rooms must use a Teams Rooms license. Microsoft Teams Rooms licenses

The current errors you are facing require investigation from the tenant/backend side, necessitating intervention from the Microsoft technical team. The Microsoft technical team will need to run specialized diagnostic tools, check the system logs, and potentially access the device remotely to determine the exact cause. Based on those Logs, Microsoft's high-level technical team will know how to fix the error at the system level that we cannot access. 

For Microsoft to intervene, you need to ask your organization's Global Admin to follow the steps in this link. Create a support request for Teams device issues

If there’s anything I may have misunderstood, I would truly appreciate it if you could provide a bit more detail to help me better understand your needs.

Looking forward to your response! 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Correct, I am trying to log into the skype profile, but have come to the realization that its in fact due to the license for Teams Room being lost. The other model is using Microsoft Teams Pro.

The license was lost after reimaging the device a second time. So let me clarify.

I first imaged the device successfully but didnt read ahead and learned that if a device is added to a corp domain it will be affected due to its OU placement. So, since I didnt like those changes I said what the heck, just reimage the thing once more time, but after that it went downside.

Now another thing to keep in mind is how many times I used the USB key with that "one" semm certificate.

I imaged one surface hub successfully, then played around with the key and imaged a t490 to see how it would work, imaged a second surface hub device successfully. Then wanted to go back and image the first device, causing this headache. So how can I recover the pro license? What I have in mind is, unbinding the UEFI from that semm certificate, reimage the device using any other task sequence just to refresh the scenario if you will. Create a new key with sem certificate and cross my fingers it gets a pro license? If that fails, can a Basic license be provided, Im trying to avoid cost as much as possible since the other unit is working fine.

I did also want to reply on applying the M. Teams Room, upgrade with MTR-Update-5.4.210.0.

https://v4.hkg1.meaqua.org/en-us/microsoftteams/rooms/manual-update

"The offline app update script needs to be run from an elevated command prompt while the Skype user (the user under which the app runs) is still signed in."

Since I was logged in as Admin, and I ran the powershell, it did sort of work, but said failed, since the Skype profile is not logged in.

I have another update.

I recently unbinded the first Semm certificate and reimaged the device once more using a new built key with new semm certificate and it gives me the following error:

Unable to sign in

Cant sign into Teams. The app needs to be updated to a more current version.

The working unit, has app version 5.4.210.0 with M. Teams Room Pro. I didnt do anything to this unit other than run the image then do the out of box experience then it was a wrap, it all worked beautiful. Now the set-up is a tad bit different, I'm requested to approve a contract or agree to certain policy, which before I didnt have to approve a thing. Once the out of box experience was over, I was shown on the top left a basic log in prompt, to enter a email and password nothing, else, this time its a little more secure. We need this device on a Pro license, but I dont know why this time its not self assigning.