Microsoft Teams 2.x has changed its installation method and now installs under C:\Program Files\WindowsApps. Based on those changes this article provides the specific steps for the deployment of the Teams 2.x in an App Layering(AL) or User Personalization Layer(UPL) environment. For the most current steps, requirements and additional details review the Microsoft documentation found at this url

 

Note: This guidance is current as of the “Last Modified Date” of the article

---

Instructions

Steps applicable to all OSes for App Layering. Some apply to UPL:

 

• Use the latest GA release of AL 2409 or at the least the AL 2403 patch, 24.3.8

• The OS layer should have Edge WebView2 and all of the latest updates

  • If deploying Edge make sure to follow our article, CTX399422

• Disable the Teams auto update

• Existing user-layer users go through a “first-time” login experience if changes are made to the mix or versions of these two applications are changed in the image

• Elastic-fit indicates these app layers are not suitable for elastic assignment (include the UWP/Appx app layers in the published image)

• Use UPM/CPM from CVAD 2402 CU1, 2203 CU5, or 2407 (or later)

• Per UNI-90395

  • Don’t run the .MSIX file itself. This installs Microsoft Teams and would be available in the Start menu but when clicked, the process doesn’t start
  • Don’t log in to any Microsoft Teams accounts while creating the layer and don’t change any Microsoft Teams settings. Personal accounts are not supported with the new Microsoft Teams. For more information, see Microsoft documentation

• When updating Microsoft Teams in an app layer revision, remove the previous version before installing the newer version

• Use the latest Teams installer, based on the OS

• After Teams is installed verify it works by launching it, in the layer packaging machine

  • Note: Never sign in to Teams in the app layer or the layer should be discarded

• If applicable, build a new Platform Layer that doesn't include MSTeams. Uninstalling it is not recommended because of delete-token issues

• Do not select the option to remove the Windows Store in our Citrix Optimizer Tool, see the screenshot, or any other tool

  • 
  • When using User layers or UPL several folders need to be added as User Exclusions. It is acceptable to use a similar UserExclusion file for all types of AL images. Inside the Teams app layer create a .txt file in \Program Files\Unidesk\Uniservice\UserExclusions called something like TeamsExclusions.txt

  1. Use a simple editor such as notepad

  2. Add these entries (do not use quotes)

     1. c:\Users\*\AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\Meeting-Addin\

     2. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs\

     3. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLog\

     4. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage\

     5. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\GPUCache\

     6. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Service Worker\CacheStorage\

     7. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Code Cache\

     8. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\IndexedDB\ 

     9. c:\Users\*\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Cache\

     10. c:\Users\*\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState\

  3. The above entries are based on Microsoft’s guidance for folder exclusions and folders that should not be persisted. These must be configured. Review Microsoft's
     documentation for the current recommendations

 

For UPL deployments:

• An msi update is available from support for UPL, based on AL 24.3.7

• An additional registry setting is also needed to effectively bring UPL to the level of AL 24.3.8. This applies only to single-session Win 10 and 11:

  • Reg add hklm\Software\Microsoft\CurrentVersionExplorer /v DisableAppInstallsOnFirstLogon  /t REG_DWORD /d 0 /f

 

Additional step for Windows Server and Multisession OSes:

• Per the Microsoft guidance enable side-loading via the registry in the OS or the layer where Teams is installed

  • reg add hklm\Software\Policies\Microsoft\Windows\Appx /v AllowDevelopmentWithoutDevLicense /t REG_DWORD /d 1 /f

  • reg add hklm\Software\Policies\Microsoft\Windows\Appx /v AllowAllTrustedApps /t REG_DWORD /d 1 /f

  • reg add hklm\Software\Policies\Microsoft\Windows\Appx /v BlockNonAdminUserInstall /t REG_DWORD /d 0 /f

 

WS2022 and W11 multisession OSes:

There are three options to install Teams

• Use UPM/CPM and let it manage UWP apps (a GPO setting)

  • https://docs.citrix.com/en-us/profile-management/2402-ltsr/how-to/enable-new-teams-roaming.html

• Use the latest FSLogix release, and expect to not see MSTeams in the start menu on the very first logon of a new user. It should work after the initial logoff completes.

• Install MSTeams in the OS layer

  • This will not pollute other layers noticeably because MSTeams operates on a per-user basis

 

W10, W11 and WS2019:

• Install in an app layer

• Possible issue on WS2019 with unhandled reparse point

  • Does not appear to affect all WS2019 deployments

  • Waiting until after AL 2409 GA for a patch-build fix

W10 multisession:

• No additional issues known at this time

Other tips:

• To avoid using UPM/CPM or enabling the UWP App Roaming policy, the below are possible workarounds

  • Workaround 1 - This will repair/reconfigure the registration of the new Teams in the image

    1. Login with the local administrator account into the published image which has Teams contained in an App Layer

    2. Browse to "C:\Program Files\WindowsApps\" and note the name of “MSTeams_<Version Number>_x64_8wekyb3d8bbwe”

    3. Open PowerShell as an administrator

    4. Run, Add-Appxpackage -Register -DisableDevelopmentMode -Path "C:\Program Files\WindowsApps\MSTeams_<Version Number>_x64_8wekyb3d8bbwe\appxmanifest.xml"

       • Replace the “MSTeams_<VersionMSTeams_<Version*” with the previously noted data

  • Workaround 2 - Create a GPO / RunKey / RunOnceKEy to re-register Teams at logon for the users

    1. Go to this third-party url

    2. Follow the steps in the section, “Use PowerShell to register AppX applications - Systemwide”

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.