Product documentation
Profile Management
Current Release 2402 LTSR 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR 7.15
View PDF

Enable roaming for the new Microsoft Teams

June 19, 2024
Contributed by: 
C C

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 you choose:

Considerations

Both file-based and container-based profile solutions support roaming on the new Microsoft Teams. For the roaming to take effect, keep the following considerations in mind:

  • Follow the Microsoft recommendations to exclude folders.
  • For the container-based solution, make sure that AppData\LocalLow isn’t configured in the Folders to exclude from profile container policy.

  • For the file-based solution, make sure that the following folders are added to the Profile streaming exclusion list - directories policy:

    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\AC
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\AppData
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalState
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\RoamingState
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\Settings
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\SystemAppData
    • AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\TempState

  • For both file- and container-based profile solutions, if the VDA version is earlier than 2402, we recommend deploying the following registry key to optimize the new Teams client. If this registry key is missing, the new Teams client operates in non-optimized mode (server-side rendering).

    • Location: HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService
    • Key (REG_Multi_SZ): ProcessWhitelist
    • Value: msedgewebview2.exe

  • If the Start menu doesn’t display the new Teams icon (especially on Windows Server 2019 or 2022 and Windows 10), we recommend performing the following settings:

    • Add the following path to the Exclusion list - directories policy:

      AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState

    • Add the following path to the Folders to exclude from profile container policy:

      AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState

    • Set the following registry key to 1 (DWORD):

      HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\StateStore\ResetCache

Per-machine installer

Requirement: Profile Management version 2402 or later.

As an administrator, follow these steps to create the machines:

  1. Install the new Teams using the per-machine installer on the master image.

    For more information about the installation, see this Microsoft article.

  2. Install the Profile Management version 2402 or later on the master image.
  3. Create the machines using the master image.

Per-user installer

Requirement: Profile Management version 2308 or later.

As an administrator, follow these steps to prepare the machines:

  1. Upgrade Profile Management to version 2308 or later.
  2. Verify that the profile roaming feature functions correctly for users.
  3. Enable the Enable UWP apps roaming policy. For more information, see Enable UWP app roaming.

As a user who wants to use the new Teams on multiple machines, you need to install the new Teams only on one of those machines:

  1. Log on to a machine.

  2. Install the new Teams using the per-user installer.

    Profile Management captures the installed Teams and containerizes it. When you log on to a different machine, Profile Management automatically mounts the Teams container to that machine.

Enable roaming for the new Microsoft Teams
June 19, 2024
Contributed by: 
C C
June 19, 2024
Contributed by: 
C C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.