Deploying Microsoft Teams Rooms via Autopilot in Self-Deployment Mode
Description: We are experiencing issues with deploying our Microsoft Teams Room (MTR) systems via Windows Autopilot in Self-Deployment Mode. Despite following the official Microsoft documentation (Autopilot Autologin for Teams Rooms), the device fails to complete the login process. Setup Details: Device: Certified Intel NUC, previously in use. OS Installation: Windows 11 Pro pre-installed. Autopilot Import: The device was successfully imported into Autopilot. Group Assignment: GroupTag "MTR-ConsoleName" has been correctly assigned. Dynamic Group: The device appears in the associated dynamic MTR group. Profiles and Assignments: Deployment Profile and Enrollment Status Page (ESP) are assigned to the device. Teams Room Update App: Deployed via Intune and assigned to the MTR group (also included in ESP). LAPS: Local Administrator Password Solution (LAPS) is active on the device. Teams Rooms Pro Console: The device appears in the console and has been assigned to a resource account with a Teams Room Pro license. Issue: After completing the deployment process, the device hangs on the login screen and cannot connect to the resource account. This prevents the self-deployment process from completing. Steps Already Taken to Resolve the Issue: The device has been completely removed from Intune and Autopilot and re-added. A custom device restriction policy was created to ensure the device is allowed. All Intune and Azure policies were reviewed and optimized to avoid conflicts. Despite these efforts, the issue persists. Questions: Are there specific requirements or limitations that we might have overlooked? Are additional settings or policies required to ensure the device connects to the resource account successfully? Could existing policies, such as LAPS, interfere with the login process? Are there any known issues related to Autopilot and Teams Room deployments, particularly for previously used devices? We urgently request your assistance in identifying and resolving this issue, as these MTR systems are critical for our operations. Thank you for your support!
Teams Room API?
Can you direct me to an API specific to Teams Rooms? We are seeking to write an application that will enable a button (available in and out of a call) to show an HTML5 page for IoT device control. This HTML5 page would be hosted externally from the nook or Team Rooms PC, but we need to enable the functionality. We have seen similar implementations but cannot find the API or SDK info on how to build it.
Teams Rooms and Conditional Access
Hello folks, regardless of using a OEM device like the Lenovo ThinkSmart hub or a teams room system console deployed onto a surface pro we got always the same issue: To secure our Office 365 Tenant we use conditional access. Any accessing device must be a in intune registered device. But when we join the console to AzureAD and register the team room system devices always the local user with the auto logon breaks. On startup the normal Windows 10 logon screen appears. We tested this serveral ways, at last with the windows 10 1803 and the teams room system deployment script. Register a surface hub (old generation) works fine. What is the right way to use team room systems with conditional access? kind regards Andy
Polycom Studio gets disconnected from HP Elite Slice - MTRs
Hi All! This is my first time posting here. I have been the Collaboration Admin for this enterprise for almost two years now, and I have been experiencing several issues with the MTRs, two of which are still recurrent. The first one is the Poly Studio USB Video Bar which stops being detected by the HP Elite Slice computers (currently the Microsoft Teams system host) The workaround for that issue was to unplug and plug the device again for it to be detected. Yet, the problem lies in a firmware version (was the conclusion after troubleshooting it with Microsoft and the Polycom engineering team). I upgraded the video bars to their latest firmware version that was known to function, but it now seems not to be mitigating the issue anymore. I experienced the HP Elite Slices stops detecting the Center of Room control touchscreen in other rooms, I have had a few like this, and the only fix I found is to connect it to a computer monitor, which makes it detect the touch panel again and send the correct signal to it and the FOR display signal on the computer monitor as designed. If this doesn’t solve the issue, the machine needs to be re-imaged. Any input on this would be of immense help and will be appreciated!
PS Script: New-Team NotFound
Hi everyone, since 3 days I can not create a TEAMS via Powershell anymore. Its the same script since 3 months at it was never a problem. My script is: # Team Display Name - declare Variables $display_name = "Ayti Test 3" $description_name = "MCCH-ORG-EXT Ayti Test 3" $mailnick_name = "MCCH-ORG-EXTAYTITEST3" $owner = "my Company Email Adress" #PS for Creation New-Team -DisplayName $display_name -MailNickName $mailnick_name -Description $description_name -Owner $owner -AllowCreateUpdateRemoveConnectors:$false -AllowCreateUpdateRemoveTabs:$false -AllowAddRemoveApps:$false -AllowDeleteChannels:$false -AllowGuestDeleteChannel:$false -AllowCreateUpdateChannels:$false -Visibility "private" The Error message since today is: New-Team : NotFound in /v1.0/teams/ endpoint At line:1 char:2 + New-Team -DisplayName $display_name -MailNickName $mailnick_name -De ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-Team], HttpRequestException + FullyQualifiedErrorId : System.Net.Http.HttpRequestException,Microsoft.Teams.PowerShell.TeamsCmdlets.NewTeam Like I told you above, this script worked since 3 months without any problems. Any Idea what the Problem is? Regards Aytac
Demystifying Microsoft Teams Rooms (Windows) application releases
There are a lot of questions recently on Teams room application update process and how Teams web app updates are related. This article is geared to demystify Teams room on Windows application releases to help customers understand the process in details and share resources that are available today for change management.
