Install new Microsoft Teams (version 2) in Citrix

The New Teams version (sometimes also called Teams 2.0) will become the new standard for Microsoft’s communication platform from July 1, 2024. On October 1, 2024, the Classical Teams client in the VDI context will reach its end of support and, according to the latest news, its end of availability date on July 1, 2025. These end dates have been adjusted several times in recent weeks.

Timeline VDI Clients

But the most important thing first:
The fact that New Teams is no longer offered via msi or exe package, but is only available as a UWP (Universal Windows Platform) app (MSIX package), the end-of-support and end-of-availability date for the Classical Teams client also marks the end of some operating system versions that may still be used as the basis for Citrix Worker.

The most prominent current victim is Windows Server 2016, for example, where the end-of-life date is currently set for January 12, 2027. However, since no UWP app can be integrated under Windows Server 2016, this operating system can no longer serve as a worker OS for Citrix if New Teams is also to be used there.


Minimum Windows version:

  • Windows 10 (Version 10.0.19041)
  • Windows 11
  • Windows Server 2019 (10.0.17763)
  • Windows Server 2022 (10.0.20348)

Minimum Microsoft Edge WebView2 version:

  • Version 90.0.818.66

Minimum Citrix versions:

  • Citrix Workspace app Windows 2203 LTSR (or newer)
  • Citrix Workspace App Windows 2302 CR (or newer)
  • Citrix Workspace App Linux 2207
  • Citrix Workspace App Mac 2302
  • Citrix Workspace App Chrome/HTML5 2301
  • Citrix Virtual Delivery Agent (VDA) 2203 LTSR (or newer)
  • Citrix Virtual Delivery Agent (VDA) 2212 CR (or newer)
  • Citrix Virtual Delivery Agent (VDA) 1912 LTSR CU 6 (or newer) – However, not all features of the New Teams Client are supported!

Script based installation

Simply use my NeverRed script for this. All my latest discoveries regarding New Teams are added to the installation routine on a daily basis.

Installation New Teams

First, the prerequisites for installing the New Teams Client must be installed on the target device. To do this, Microsoft Edge WebView2 must be installed and sideloading for UWP apps must be activated.

Download MS Edge WebView 2 Runtime
  • Start the installation of Microsoft Edge WebView2
MS Edge WebView 2 Runtime
  • Activate sideloading on the worker, start an Administrative PowerShell and enter the following commands:
MSIX sideloading

It must also be checked that the .Net-framework is installed higher than version 4.8 (Windows Server 2019 & Windows 10) so that the Microsoft Teams Meeting Add-in for Microsoft Office can be installed.

  • Check the installed version on the worker by starting an Administrative PowerShell and enter the following command:

If the version is lower than 4.8, it must be updated before installing New Teams.

.Net-Framework Version <4.8
.Net Framework Download
  • Start the installation of .Net-Framework 4.8
.Net Framework
.Net Framework Download Install
  • After installing the .Net-framework, the system must be restarted
.Net-Framework Version >4.8

The New Teams Client is installed either directly via the MSIX package (Windows Server 2019 & Windows 10) or via Teamsbootstrapper Executable (Windows Server 2022 & Windows 11).

The method via the Teamsbootstrapper installation is the recommended version on Citrix Worker machines.

If there is still a Teams installation on the system, it must be uninstalled first.

  • Download the required installation files for the New Teams
Latest Teams MSIX version32 bit64 bit
Teamsbootstrapper (Windows Server 2022 & Windows 11)Download
  • Start the installation of the New Teams Client with the command for the underlying operating system

Windows Server 2019 & Windows 10

New Teams Install Windows 10 Windows Server 2019 DISM

Windows Server 2022 & Windows 11

New Teams Install Windows 11 Windows Server 2022 DISM

The New Teams installation must then be optimized for Citrix.

  • Start an Administrative PowerShell and enter the following command:
Regedit disableAutoUpdate

This is no longer necessary as of Citrix Virtual Apps and Desktops version 2402.

Regedit ProcessWhitelist

Installation Teams Meeting Add-in

The add-in still needs to be installed and configured so that you can continue to schedule Teams meetings via Microsoft Outlook.

  • Start an Administrative PowerShell and enter the following command:
Teams Meeting Add-in for Microsoft Office
  • After installation, the add-in must be registered by executing the following commands:

Profile solution

The following paths must be included in the New Teams:

  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbwe
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweSettingssettings.dat
  • %LocalAppData%Publishers8wekyb3d8bbweTeamsSharedConfigapp_switcher_settings.json
  • %LocalAppData%Publishers8wekyb3d8bbweTeamsSharedConfigtma_settings.json
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweAC
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweAppData
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweLocalCache
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweLocalState
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweRoamingState
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweSettings
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweSystemAppData
  • %LocalAppData%PackagesMSTeams_8wekyb3d8bbweTempState

The following profile solutions are supported:

  • Minimum FSLogix Version 2210 Hotfix 3
  • Minimum Citrix Profile Management Version 2308
    • Aktivierung vom UWP App Roaming Feature


The following anti-virus process exceptions must be stored for the New Teams:

  • ms-teams.exe
  • ms-teamsupdate.exe


The following known topics and features are currently not available in New Teams in VDI:

  • Screen sharing from the chat for Citrix only when using Workspace app 2311
  • msteams_autostart.exe “The parameter is incorrect”: In non-persistent environments that use FSLogix (all versions prior to 2210 HotFix 4) or Citrix Profile Manager profile containers, the error is issued when new teams try to start automatically or when a user tries to start teams from the start menu
  • New Teams is not started by users who log in to non-persistent virtual desktops, or the application is not visible in the start menu
    • Admins do not have this problem – after installing new teams on the golden image, they can start it successfully
    • After sealing the golden image and deploying at scale (using provisioning tools such as Citrix MCS/PVS), users log in to the virtual machines and click on the new Teams icon but are unable to launch the app. The issue is caused by a failed registration of the MSIX package at user level with different profile management software (FSLogix before 2210 HotFix 4, Citrix CPM 2308 or 2311, but not on 2402 etc.), although the deployment of the package was successful (the OS saved the content of the package to disk in the %ProgramFiles%WindowsApps directory). This issue can be confirmed by running Get-AppxPackage -name MsTeams for the affected users. If you run this code, an empty output will be returned.
    • The PowerShell window is displayed after New Teams has been deployed. To prevent this, the registry key listed below must be deleted.

New features in New Teams for VDI

The following features are included in New Teams for VDI, compared to Classical Teams:

  • Multitenant Multi-Account
  • Performance improvements in the consumption of hardware resources
  • Channels 2.0
  • Multiple windows are activated by default without the need for a restart
  • Improvements to the sharing toolbar (including pinning/unpinning)

6 thoughts on “Install new Microsoft Teams (version 2) in Citrix”

  1. I’ve gone through your script and made some corrections as it’s missing syntax and added a little automation
    $URL01 = ‘’$APP01 = ‘teamsbootstrapper.exe’
    $URL02 = ‘’$APP02 = ‘MSTeams-x64.msix’
    $ZScalerProxy = “<PROXY>”[]::defaultwebproxy = new-object$ZScalerProxy)[]::defaultwebproxy.credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials[]::defaultwebproxy.BypassProxyOnLocal = $true
    [Net.ServicePointManager]::SecurityProtocol = ([Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3 -bor [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12 -bor [Net.SecurityProtocolType]::Tls13)
    add-type @”using System.Net;using System.Security.Cryptography.X509Certificates;public class TrustAllCertsPolicy : ICertificatePolicy {public bool CheckValidationResult(ServicePoint srvPoint, X509Certificate certificate,WebRequest request, int certificateProblem) {return true;}}”@[System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy
    Invoke-WebRequest $URL01 -OutFile “C:\Temp\$APP01” -proxy $ZScalerProxyInvoke-WebRequest $URL02 -OutFile “C:\Temp\$APP02” -proxy $ZScalerProxy
    New-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\Appx -Name AllowAllTrustedApps -Value 1 -PropertyType DWORD -Force | Out-NullNew-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\Appx -Name AllowDevelopmentWithoutDevLicense -Value 1 -PropertyType DWORD -Force | Out-NullNew-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\Appx -Name BlockNonAdminUserInstall -Value 0 -PropertyType DWORD -Force | Out-Null
    Start-Process -Wait “C:\Temp\$APP01” -ArgumentList “-p -o C:\Temp\$APP02”
    reg add “HKLM\SOFTWARE\MicrosoftTeams” /v disableAutoUpdate /t REG_DWORD /d 1 /f | Out-Null
    msiexec.exe /i “$((Get-ChildItem -Path ‘C:\Program Files\WindowsApps’ -Filter ‘MSTeams*’).FullName)\MicrosoftTeamsMeetingAddinInstaller.msi” Reboot=ReallySuppress ALLUSERS=1 TARGETDIR=”C:\Windows\Microsoft\TeamsMeetingAddin” /qn
    $appX64DLL = (Get-ChildItem -Path “C:\Windows\Microsoft\TeamsMeetingAddin\x64” -Include “Microsoft.Teams.AddinLoader.dll” -Recurse).FullName$appX86DLL = (Get-ChildItem -Path “C:\Windows\Microsoft\TeamsMeetingAddin\x86” -Include “Microsoft.Teams.AddinLoader.dll” -Recurse).FullName
    Start-Process -FilePath “$env:WinDir\SysWOW64\regsvr32.exe” -ArgumentList “/s /n /i:user "$appX64DLL“” -ErrorAction SilentlyContinueStart-Process -FilePath “$env:WinDir\SysWOW64\regsvr32.exe” -ArgumentList “/s /n /i:user "$appX86DLL“” -ErrorAction SilentlyContinueIf (!(Test-Path ‘HKLM:SOFTWARE\Microsoft\Office\Outlook\Addins’)) {New-Item -Path “HKLM:SOFTWARE\Microsoft\Office\Outlook\Addins” | Out-Null}
    New-Item -Path “HKLM:SOFTWARE\Microsoft\Office\Outlook\Addins” -Name “TeamsAddin.FastConnect” -Force -ErrorAction Ignore | Out-Null
    New-ItemProperty -Path “HKLM:SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect” -Type “DWord” -Name “LoadBehavior” -Value 3 -force | Out-Null
    New-ItemProperty -Path “HKLM:SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect” -Type “String” -Name “Description” -Value “Microsoft Teams Meeting Add-in for Microsoft Office” -force | Out-Null
    New-ItemProperty -Path “HKLM:SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect” -Type “String” -Name “FriendlyName” -Value “Microsoft Teams Meeting Add-in for Microsoft Office” -force | Out-Null

  2. I have issues with the Presence function to work with Outlook. The presence status is not working with Teams 2.1. Anybody have any solution?

  3. I see the Microsoft documentation do not mention the NET Framework version have to be 4.8. I am not running NET Framework 4.8 on my VDA Servers. Where did you find that NET Framework version 4.8 is required by Teams 2.1? 

  4. Another question i am running Windows Server 2019 and i have only enabled “Developer mode” during installation of Teams 2.1 after installation is complete i have disabled “Developer Mode” For proper running av Teams 2.1 do i need to keep the OS in Developer mode and not revert back to normal mode?

  5. I have issues with not Presence is not showing up in Outlook. In the Micrsoft guide:

    Outlook presence integration with New Teams in Windows Server 2019

    For Outlook to properly display presence status, the following steps are required on the golden image:

    Install machine-wide (ALLUSERS=1) the ‘Windows 10 1809 and Windows Server 2019 KB5035849 240209_02051 Feature Preview.msi‘.
    Open your Group Policy Editor. Navigate to Computer Configuration\Administrative Templates\KB5035849 240209_02051 Feature Preview\Windows 10, version 1809 and Windows Server 2019. Change the value of that Setting to Enabled.
    Install KB5035849 March 2024 cumulative update from the Microsoft Update Catalog or WSUS for Enterprises.
    Install machine-wide (ALLUSERS=1) the ‘MSTeamsNativeUtility.msi‘.
    Reboot the virtual machine.
    Install new Teams 24033.811.2738.2546 or higher, using Dism as described in the section above.

    In your guide you have not installed MSTeamsNativeUtility.msi‘.
    Is Presence working for you?

  6. Awesome Article. 
    Recently upgraded PVS vDisk from Windows Server 2016 OS to Windows Server 2022 (Version 10.0.20348), PVS TD Agent 2203 LTSR CU4 and VDA 2203 LTSR CU4 Update 1. 
    We’re using FSLogix for Profile solution and Hotfix 4 in installed. 
    1) All is working fine so far Except Outlook Teams Meeting addin isn’t available for new Users. It comes up as Skype Addin. Any Ideas?? 
    2) Any Registry settings needs to be updated for new teams to work with FSLOgix??
    Thanks in Advance

Leave a Reply

Your email address will not be published. Required fields are marked *

* I consent to having this website store my submitted information so they can respond to my inquiry.