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!
New Teams Won't Show in Start Menu or Add/Remove Programs After Intune Install
Hi.. We are starting to add the new Teams app to our Intune autopilot deployment sequence. We are using the teamsbootstrapper.exe file to install The problem is that while we know it does install as we can see the Teams folder in c:\ProgramFiles\WindowsApps directory, Teams icon/shortcut does not get added to the Windows start menu nor is it listed in add/remove programs. In Intune we've tried the following install commands: 1: teamsbootstrapper.exe -p 2: and this powershell script: function ProvisionTeams { param ( [string]$ProvisionMode ) if ($ProvisionMode -eq "AllUsers") { Start-Process -FilePath ".\teamsbootstrapper.exe" -ArgumentList "-p" -Wait -WindowStyle Hidden } elseif ($ProvisionMode -eq "CurrentUser") { Start-Process -FilePath ".\teamsbootstrapper.exe" -ArgumentList "-p" -Wait -WindowStyle Hidden } else { Write-Host "Invalid ProvisionMode specified. Use 'AllUsers' or 'CurrentUser'." } } # Provision for all users ProvisionTeams -ProvisionMode "AllUsers" # Provision for the current user ProvisionTeams -ProvisionMode "CurrentUser" And neither yield allow for Teams to show up in start menu for users to access. Anyone got any ideas????
Teams no longer autostarts and asks for login
Hello We switched the Update channel for Microsoft 365 Apps from Monthly Enterprise Channel to Current Channel (Preview) because it's recommended by Microsoft and we wanted the new Teams. Since then Teams is no longer autostarting after device enrollment and also asks for login. Previously it was always autostarting and logged in automatically. Some additional info: - Azure AD (Entra ID?) account is listed under Access work or school and shows as connected, so everything should be fine there and as mentioned is was working before. - We are only rolling out Teams from Microsoft 365 Apps, so no Word, Excel, etc. Has anyone else observed this behavior and does anyone know how to restore the old behavior? Thanks Michael
New Teams and Outlook not working for my organization.
Hi All. I've been trying to allow the New teams/Outlook for my organization. Here's how we curently have everything setup: We use Windows Information Protection with enrolled devices. WIP works with “classic” version of MS Teams and Outlook but not the latest “new” version that is being rolled out. We know that it relates to WIP, as both new versions work fine with WIP turned off. We don’t seem to able to add the correct details to the WIP policy in order to add the new MS Team and Outlook as protected apps (enlightened or unenlightened); they keep showing as “personal” in Task Manager “Enterprise Context”. These are the configurations that I've tried so far and didn't seem to work for both apps. Outlook Name: Outlook Product name: microsoft.windowscommunicationsapps Type: Universal app Publisher: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Min Version: * Max Version: * Action: Allow Teams Name: Microsoft Teams Product name: * Type: Desktop apps Publisher: O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US File: ms-teams.exe Min Version: * Max Version: * Action: Allow Is there anyone who can advise with the WIP config or is there an alternative way to get the users to switch to the new Apps? Thank you.GPO settings for MS Store - teamsbootstrapper.exe says "Store Failure"
Dear Community, we're working hard to distribute apps via Intune. Currently we're having problems with MS Teams. We use the teamsbootstrapper.exe and get error codes 0x80073CF0 / 0x80073CF9 over and over again. Both errors point to the MS Store. The MS Store is activated in our company. Does anyone know which GPO must be activated or deactivated so that communication with the MS Store works without errors? I've tested it within a sandbox on my system - everything worked fine (only the download from teams didn't work caus of no connection to the MS Store). Thanks a lot!
Microsoft Teams not working when Company Intune Portal is installed
Hello can someone help me why MS Teams force to closed the app when the company intune portal is installed. I need the company portal to sign in on teams because of policy in our company. But when I installed it crashed the MS team app Using android 13.
Teams Needs an Update Message
Hi, I'm pushing out Microsoft 365 apps via intune, and this is working (mostly), However on some machines (Specifically Microsoft Surface 3) the users are promped to update them on first start. This then takes them off to a website to download and install Teams again manually This doesn't seem to happen on our Dell Laptops (Although I still need to 100% verify this). Any ideas why this is happening? I have the App set to use Monthly Enterprise Channel and Latest version. Anyone any ideas?
