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!
Autologon in Intune
I have an AD environment ifsynchronized with AAD. In addition to using Intune for device management. I'm having trouble setting up Autologon with the Kiosk profile in Intune. It turns out that, although I set Autologon correctly, every time I restart to test it, the settings have been removed. In Event Viewer I notice that there is a message stating that the Autologon settings have been removed due to an EAS policy. I have searched the Internet for multiple solutions, but it is impossible, none of them apply. I don't have anything related to Exchange Active Sync, mail, calendar, etc. I also don't see the EAS-related registry entries listed on many Internet pages. It seems that the problem is given by Intune's own policies. Although I have excluded my test device from all configuration policies as well as compliance policies, the error still occurs, so I deduce that there is some default policy that affects. My question is. Is there any way to disable the EAS Built-in policy? How do I set up a PC in kiosk mode with Intune? Any clues? Thank you very much in advance. Enrique Carrasco
