Enable roaming for the new Microsoft Teams
This article provides guidance on how to enable roaming for the new Microsoft Teams (version 2.1 or later) using Profile Management. The process varies depending on the installer type that you choose:
- Install and configure using the per-machine installer
- Install and configure using the per-user installer
Install and configure using the per-machine installer
Requirement: Profile Management version 2402 or later.
As an administrator, follow these steps to create the machines:
-
Install the new Microsoft Teams using the per-machine installer on the master image.
For more information about the installation, see this Microsoft article.
- Install the Profile Management version 2402 or later on the master image.
- Create the machines using the master image.
- Configure required settings for Microsoft Teams roaming to take effect.
Install and configure using the per-user installer
Requirement: Profile Management version 2308 or later.
As an administrator, follow these steps to prepare the machines:
- Upgrade Profile Management to version 2308 or later.
- Verify that the profile roaming feature functions correctly for users.
- Enable the Enable UWP apps roaming policy. For more information, see Enable UWP app roaming.
- Configure required settings for Microsoft Teams roaming to take effect.
As a user who wants to use the new Microsoft Teams on multiple machines, you need to install the new Microsoft Teams only on one of those machines:
-
Log on to a machine.
-
Install the new Microsoft Teams using the per-user installer.
Profile Management captures the installed Microsoft Teams and containerizes it. When you log on to a different machine, Profile Management automatically mounts the Microsoft Teams container to that machine.
Configure required settings
Both file-based and container-based profile solutions support roaming on the new Microsoft Teams. For the roaming to take effect, complete the following required settings accordingly:
- Required settings for the file-based profile solution
- Required settings for the container-based profile solution
Required settings for the file-based profile solution
Perform the following required settings for the Microsoft Teams roaming to take effect:
-
Add the following folders to the Folders to mirror policy:
AppData\Roaming\Microsoft\Windows\CookiesAppData\Local\Microsoft\Windows\INetCookiesAppData\Local\Microsoft\Windows\WebCacheAppData\Local\Microsoft\VaultAppData\Local\Microsoft\Windows\CachesAppData\Local\Packages
-
If the Accelerate folder mirroring policy is disabled, follow Microsoft’s recommendations to exclude folders.
-
If Accelerate folder mirroring policy enabled, configure the exclusion list with the following considerations:
-
Don’t follow Microsoft’s recommendations to exclude folders.
-
Ensure that no folders under
AppData\Local\Packages\MSTeams_8wekyb3d8bbweare in the exclusion list ifAppData\Local\PackagesorAppData\Local\Packages\MSTeams_8wekyb3d8bbweis included in the Folders to mirror policy. -
Check the Microsoft Teams troubleshooting guide - Step 3: Check whether you have the Read permission to access all the following directories in the AppData folder. Ensure that all folders in the list, except those folders under
AppData\LocalLow, aren’t included in the exclusion list. (Note: You can decide whether to includeAppData\LocalLowfolders in the exclusion list).
-
- Add the following folders to the Profile streaming exclusion list - directories policy:
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\ACAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\AppDataAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCacheAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalStateAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\RoamingStateAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\SettingsAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\SystemAppDataAppData\Local\Packages\MSTeams_8wekyb3d8bbwe\TempState
-
If the Start menu doesn’t display the new Microsoft Teams icon (especially on Windows Server 2019 or 2022 and Windows 10), configure the following settings:
-
For Windows Server 2022 and Windows 10, add the following path to the exclusion list:
AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState -
For Windows Server 2019, add the following path to the exclusion list:
AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\TempState -
Set the following registry key to 1 (DWORD):
HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\StateStore\ResetCache
-
-
If the VDA version is earlier than 2402, deploy the following registry key to optimize the new Microsoft Teams client. If this registry key is missing, the new Microsoft Teams client operates in non-optimized mode (server-side rendering).
- Location: HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService
- Key (REG_Multi_SZ): ProcessWhitelist
- Value: msedgewebview2.exe
Required settings for the container-based profile solution
Configure the following required settings for the Microsoft Teams roaming to take effect:
-
If the Enable local caching for profile containers policy is disabled, configure the exclusion list with the following considerations:
-
Don’t follow Microsoft’s recommendations to exclude folders. Ensure that no folders under
AppData\Local\Packages\MSTeams_8wekyb3d8bbweare in the container exclusion list. -
Check the Microsoft Teams troubleshooting guide - Step 3: Check whether you have the Read permission to access all the following directories in the AppData folder. Ensure that all folders in the list aren’t included in the container exclusion list.
-
-
If the Enable local caching for profile containers policy is enabled, follow these steps:
-
Follow Microsoft’s recommendations to exclude folders.
-
Add the following folders to the Folders to mirror policy:
AppData\Roaming\Microsoft\Windows\CookiesAppData\Local\Microsoft\Windows\INetCookiesAppData\Local\Microsoft\Windows\WebCacheAppData\Local\Microsoft\VaultAppData\Local\Microsoft\Windows\CachesAppData\Local\Packages
-
-
If the Start menu doesn’t display the new Microsoft Teams icon (especially on Windows Server 2019 or 2022 and Windows 10), configure the following settings:
-
For Windows Server 2022 and Windows 10, add the following path to the exclusion list:
AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState -
For Windows Server 2019, add the following path to the exclusion list:
AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\TempState -
Set the following registry key to 1 (DWORD):
HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\StateStore\ResetCache
-
-
If the VDA version is earlier than 2402, we recommend deploying the following registry key to optimize the new Microsoft Teams client. If this registry key is missing, the new Microsoft Teams client operates in non-optimized mode (server-side rendering).
- Location: HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService
- Key (REG_Multi_SZ): ProcessWhitelist
- Value: msedgewebview2.exe