Microsoft Teams Desktop Client Preview: Rollout and Management Guide for Admins

Introduction

The new Microsoft Teams desktop client for Windows is rolling out in preview, offering a faster, simpler, and more flexible experience. This comprehensive guide will walk you through the process of managing the rollout as an administrator, from understanding the prerequisites to configuring settings for user access.

Prerequisites

Ensure that your users meet these requirements:

• Windows 10 version 10.0.19041 or higher
• Teams app Version 1.6.00.4472
• Appropriate Microsoft 365 Apps Security Updates

Required Microsoft 365 Apps Security Updates

Channel	Version & Build
Semi-Annual Enterprise Channel	Version 2302 (Build 16130.20306) Version 2208 (Build 15601.20578) Version 2202 (Build 14931.20944)
Monthly Enterprise Channel	Version 2301 (Build 16026.20222) Version2212 (Build 15928.20294)
Windows LTSB	Version 2018 (Build 10396.20023) Version 2021 (Build 14332.20481)

Controlling Access to the New Teams Client

As an admin, you can manage which users see the "Try the new Teams" toggle by using the Teams admin setting UseNewTeamsClient under the TeamsUpdateManagement policy. You can configure this setting via the Teams Admin Center or PowerShell.

Configuring the Toggle in Teams Admin Center

1. Sign in to the Microsoft Teams admin center.
2. Select Teams > Teams Update policies.
3. Create a new policy or modify an existing one.
4. Define the policy settings for the "Use new Teams client" option.
5. Assign the policy to specific users or user groups.

Setting	Description
Microsoft controlled	Default. The value lets Microsoft control whether the new Teams toggle switch is shown or not based on product readiness
User can choose	Use this value to show the new Teams toggle switch, to let users opt into the new Teams, and switch back if they need to.
Not enabled	Use this value to hide the new Teams toggle switch. Users won't be able to opt in to the new Teams.

Configuring the Toggle in PowerShell

1. Import the latest Teams PowerShell cmdlets (version 4.9.1 or greater).
2. Connect to an admin account using Connect-MicrosoftTeams.
3. Explore the list of related commands with *-CsTeamsUpdateManagementPolicy and tab through the commands.
4. Use the Set-CsTeamsUpdateManagementPolicy command to modify the existing Update Management policy to allow assigned users to try the new Teams.
5. Use the New-CsTeamsUpdateManagementPolicy and Grant-CsTeamsUpdateManagementPolicy commands to deploy a new policy to opt-out specific users from seeing the toggle.

Here's a step-by-step example for configuring the toggle in PowerShell:

Step 1: Import the latest Teams PowerShell cmdlets

• Install the latest Microsoft Teams PowerShell module (version 4.9.1 or greater) by running this command in an elevated PowerShell session:

Install-Module -Name MicrosoftTeams -RequiredVersion 4.9.1 -Scope AllUsers

Step 2: Connect to an admin account

• Connect to your Teams admin account using the following command:

Connect-MicrosoftTeams

• You will be prompted to enter your admin credentials.

Step 3: Modify the existing Update Management policy

• Use the following command to modify the existing Update Management policy to allow assigned users to try the new Teams:

Set-CsTeamsUpdateManagementPolicy -Identity <new_policy_name> -UseNewTeamsClient UserChoice

Replace <new_policy_name> with your desired policy name, for example:

Set-CsTeamsUpdateManagementPolicy -Identity MySetting -UseNewTeamsClient UserChoice

Step 4: Create and assign a new policy to opt-out specific users

• Use the following commands to create a new policy that hides the toggle and assign it to a specific user:

New-CsTeamsUpdateManagementPolicy -Identity <new_policy_name> -UseNewTeamsClient AdminDisabled

Replace <new_policy_name> with your desired policy name, for example:

New-CsTeamsUpdateManagementPolicy -Identity MySetting -UseNewTeamsClient AdminDisabled

• After creating the new policy, use the following command to assign it to a specific user:

Grant-CsTeamsUpdateManagementPolicy -Identity <user> -PolicyName <new_policy_name>

Replace <user> with the user's email address and <new_policy_name> with the policy name you created earlier, for example:

Grant-CsTeamsUpdateManagementPolicy -Identity john.doe@example.com -PolicyName MySetting

By following these steps, you can configure the toggle for the new Microsoft Teams desktop client in PowerShell. Users who are allowed to see the toggle can opt in or out, while users who are not allowed will not see the toggle.

Uninstalling the New Teams Client

Users can manually opt-out using the new Teams toggle. To uninstall the client completely, users can manually uninstall it from settings. To remove the new Teams from all users' computers, use the appropriate PowerShell commands.

Troubleshooting

If users experience installation issues or cannot see the App switcher toggle, check policy settings, verify the required versions for Windows and Teams, and ensure that there are no pending updates. Additionally, you can review logs and perform a clean relaunch of the Teams app.

Installation issues:

If your users are experiencing issues installing the app, as an administrator you may have set some restrictions preventing them from downloading and installing it. They may see this error:

It's possible that the MSIX package installation could be blocked by registry keys set by GPO policy/third party tool. For a complete list of registry keys: How Group Policy works with packaged apps - MSIX

The registry keys that could block new Teams MSIX package installation are:

• BlockNonAdminUserInstall
• AllowAllTrustedApps
• AllowDevelopmentWithoutDevLicense

These registry keys can be found at one of these locations:

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock
• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Appx

There are a few policies that could alter these registry keys and block app installation in your organization due to restricted policy set by the admins. Some of the known GPO policies that may be preventing installation include:

• Prevent non-admins users from installing packaged Windows apps
• Allow all trusted apps to install (disabled)

Troubleshooting the app switcher toggle

• Relaunch your current client before turning the Try the new Teams toggle ON to make sure that you have latest changes. Also, if there's any Windows update pending, including security updates, install them before you try new Teams.
• If you’re not seeing the toggle for new Teams, make sure you have the minimum required versions for Windows and Teams
• After you successfully switch to new Teams, if you can't find the toggle on the top left to switch between new Teams and Microsoft Teams (work or school), you can start the version you want by going to Start menu and searching for it or by clicking on it from the task bar.

Policies that could block user seeing the App switcher toggle

The following list of policies can block users from seeing the app switcher toggle.

• If the user is on a VDI computer (Citrix, VMware etc.).
• If the user is signed in to classic Teams with a Teams for Life account and a work account.
• If the user is signed in to classic Teams with a Teams for Life account.
• If you have an MSIX client.

To find out is any of those polices blocking you:

1. Open logs in this path: %appdata%/Microsoft/Teams
2. Open logs.txt
3. Search for appswitcher_appstateservice_check.
4. Check the enggComplete flag:

• If true, the Microsoft has turned the setting for you.
• If false, you didn’t the settings from MSFT yet or need an app relaunch (see below for steps to relaunch the app)

5. Check isAboveWin10Vibranium.

• If true, the OS version is >= what is needed for app switcher
• If false, the OS is older than what we support.

6. Check the code to find out the cause.

Code	Meaning
TFLONLY	You're only signed in to Teams for Life
TFLANDTFW	You're signed in to Teams for Life and Teams for Work
SPECIALCLOUD	You're signed in to a special cloud that isn’t supported.
CROSSCLOUD	You're signed in to a government cloud.
VDI	You're signed in to a VDI machine (VMware, Citrix, AVD/WV).

Windows 10 users may receive an error message:

Issue: Windows 10 users may receive the error “We’ve run into an issue” when they download and install the new Teams.

Action:  Download and install WebView2 Runtime. Then restart the Teams desktop app and try again.

Some users still don't see the toggle button

Make sure the user has the minimum requirements met on their computer. Next, have them sign out and back into the Teams desktop app.
If the toggle still doesn't appear, then:

1. Right-click on the Teams app icon in your taskbar and select Quit
2. Open File Explorer. In the address bar, enter the following: %appdata%/Microsoft/Teams
3. Select the arrow, or press Enter. You’ll be taken to the contents of that folder.
4. Delete all contents of the folder (don’t worry, Teams app won't be deleted, and no or on any of your custom settings). If you get any messages that a certain file or folder can’t be deleted, select Skip.
5. Relaunch the Teams app, then right-click on the icon and select Quit
6. Relaunch the Teams app one more time, and you should see the toggle switch.

Conclusion

By following this guide, you can successfully manage the rollout of the new Microsoft Teams desktop client for Windows and ensure a seamless experience for your users. Remember to monitor the preview release for updates and adjust your configurations as necessary.