-
-
Enable roaming for the new Microsoft Teams
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
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 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:
-
Install the new 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.
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.
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:
-
Log on to a machine.
-
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.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.