Install new Microsoft Teams (version 2) in Citrix

The new version of Microsoft Teams (often referred to as “Teams 2.0”) has been the new standard since July 1, 2024.

For VDI environments, this means:

October 1, 2024 → End of Support (Classic Teams in VDI)
July 1, 2025 → End of Availability

In short:
There is no way back.

The real game changer (that many underestimate)
The new Microsoft Teams is no longer delivered as an MSI or EXE package, but exclusively as:

MSIX / UWP app

This has massive implications for VDI environments:

New challenges (of course)
New installation logic
New profile behavior
New dependencies

The silent victim: legacy operating systems

The most prominent example:

Windows Server 2016

Official support until: January 12, 2027
Reality: Dead for Teams

Why?

No proper support for UWP / MSIX → New Teams simply won’t run properly (or at all)

Prerequisites for New Teams on VDI

OS Version

Windows 10 (ab 19041)
Windows 11
Windows Server 2019
Windows Server 2022

Components

WebView2 (mandatory!)
.NET Framework ≥ 4.8
Up-to-date Citrix components

Minimum Citrix versions

VDA: 2203 LTSR or newer

Workspace App:

Windows: 2203 LTSR+
Linux: 2207+
Mac: 2302+
HTML5: 2301+

Important:
1912 LTSR also works – but with limitations

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 the installation package for Microsoft Edge WebView 2

Start the installation of Microsoft Edge WebView2

Activate sideloading on the worker, start an Administrative PowerShell and enter the following commands:

New-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Appx -Name AllowAllTrustedApps -Value 1 -PropertyType DWORD -Force | Out-Null
New-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Appx -Name AllowDevelopmentWithoutDevLicense -Value 1 -PropertyType DWORD -Force | Out-Null
New-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Appx -Name BlockNonAdminUserInstall -Value 0 -PropertyType DWORD -Force | Out-Null

New-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Appx -Name AllowAllTrustedApps -Value 1 -PropertyType DWORD -Force | Out-Null

New-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Appx -Name AllowDevelopmentWithoutDevLicense -Value 1 -PropertyType DWORD -Force | Out-Null

New-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Appx -Name BlockNonAdminUserInstall -Value 0 -PropertyType DWORD -Force | Out-Null

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:

(Get-ItemProperty "HKLM:\Software\Microsoft\NET Framework Setup\NDP\v4\Full").Version

1	(Get-ItemProperty "HKLM:\Software\Microsoft\NET Framework Setup\NDP\v4\Full").Version

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

Download the installation package for .Net-Framework 4.8

Start the installation of .Net-Framework 4.8

After installing the .Net-framework, the system must be restarted

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.

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

./teamsbootstrapper -x

1	./teamsbootstrapper -x

Download the required installation files for the New Teams

Latest Teams MSIX version	32 bit	64 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

Dism.exe /Online /Add-ProvisionedAppxPackage /PackagePath:<Path to msix file> /SkipLicense

1	Dism.exe /Online /Add-ProvisionedAppxPackage /PackagePath:<Path to msix file> /SkipLicense

Windows Server 2022 & Windows 11

.teamsbootstrapper.exe -p -o <Path to msix file>

1	.teamsbootstrapper.exe -p -o <Path to msix file>

The New Teams installation must then be optimized for Citrix.

Start an Administrative PowerShell and enter the following command:

reg add "HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService" /v ProcessWhitelist /t REG_Multi_SZ /d msedgewebview2.exe /f | Out-Null
reg add "HKLM\SOFTWARE\MicrosoftTeams" /v disableAutoUpdate /t REG_DWORD /d 1 /f | Out-Null

1 2	reg add "HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService" /v ProcessWhitelist /t REG_Multi_SZ /d msedgewebview2.exe /f \| Out-Null reg add "HKLM\SOFTWARE\MicrosoftTeams" /v disableAutoUpdate /t REG_DWORD /d 1 /f \| Out-Null

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

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.

Important!
If Office x86 is installed, Teams x86 should also be installed. This means that the Teams Meeting Add-in should also be installed in x86. Otherwise, it can lead to unwanted restarts, as Teams independently installs the x86 Teams Meeting Add-in in the user session and then provokes the restart.

Start an Administrative PowerShell and enter the following command:

For x64:
msiexec.exe /i "$((Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Filter 'MSTeams*').FullName)MicrosoftTeamsMeetingAddinInstaller.msi" Reboot=ReallySuppress ALLUSERS=1 TARGETDIR="C:\Windows\MicrosoftTeamsMeetingAddin" /qn

For x86:
msiexec.exe /i "$((Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Filter 'MSTeams*').FullName)MicrosoftTeamsMeetingAddinInstallerX86.msi" Reboot=ReallySuppress ALLUSERS=1 TARGETDIR="C:\Windows\MicrosoftTeamsMeetingAddin" /qn

For x64:

msiexec.exe /i "$((Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Filter 'MSTeams*').FullName)MicrosoftTeamsMeetingAddinInstaller.msi" Reboot=ReallySuppress ALLUSERS=1 TARGETDIR="C:\Windows\MicrosoftTeamsMeetingAddin" /qn

For x86:

msiexec.exe /i "$((Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Filter 'MSTeams*').FullName)MicrosoftTeamsMeetingAddinInstallerX86.msi" Reboot=ReallySuppress ALLUSERS=1 TARGETDIR="C:\Windows\MicrosoftTeamsMeetingAddin" /qn

After installation, the add-in must be registered by executing the following commands:

$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 SilentlyContinue
Start-Process -FilePath ""$env:WinDir\SysWOW64\regsvr32.exe" -ArgumentList "/s /n /i:user `"$appX86DLL`"" -ErrorAction SilentlyContinue

If (!(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
If (!(Test-Path 'HKLM:\Software\Microsoft\Office\Outlook\Addins\')) {New-Item -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\" | Out-Null}

$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 SilentlyContinue

Start-Process -FilePath ""$env:WinDir\SysWOW64\regsvr32.exe" -ArgumentList "/s /n /i:user `"$appX86DLL`"" -ErrorAction SilentlyContinue

If (!(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

If (!(Test-Path 'HKLM:\Software\Microsoft\Office\Outlook\Addins\')) {New-Item -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\" | Out-Null}

Profile management

Required paths

%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 4
Minimum Citrix Profile Management Version 2308

Important!
Any attempts to make New Teams available via folder redirection or roaming profiles are not supported.

Anti-Virus

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

ms-teams.exe
ms-teamsupdate.exe

Limitations

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
The PowerShell window appears after New Teams has been deployed. To do this, you must delete the registry key listed below.

Location: "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run"
Name: TeamsProvisionRunKey

1 2	Location: "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run" Name: TeamsProvisionRunKey

The following features are not available in VDI:

QoS
1080p
Custom backgrounds
Teams Premium Features
Avatars
3×3 and 7×7 grid view
Noise reduction
Zoom in and out
Location-based routing
HID
“Record Video Clip” does not capture screen sharing
The Call Monitor does not display video or screen sharing

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)

Known issues with existing solutions

Over the past few months, I’ve come across various issues for which a solution is now available.

Auto-start of Teams

The auto-start in Teams is now controlled by three components:

Since this is an MSIX installation, the limitations of an MSIX package also apply. This means that only after the first manual start, the package is fully registered in the user context and therefore only then can the auto-start behaviour be defined via Settings > General
If the Auto-start Teams checkbox is greyed out, it means a system-wide GPO is disabling this option for UWP apps. To activate this options change the following registry keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] 
"EnableFullTrustStartupTasks"=dword:00000000
"EnableUwpStartupTasks"=dword:00000000
"SupportFullTrustStartupTasks"=dword:00000000
"SupportUwpStartupTasks"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]

"EnableFullTrustStartupTasks"=dword:00000000

"EnableUwpStartupTasks"=dword:00000000

"SupportFullTrustStartupTasks"=dword:00000000

"SupportUwpStartupTasks"=dword:00000000

This registry setting prevents the option from appearing in the operating system under Settings > Apps > Installed Apps. To change this, create the registry key with the values shown below:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableFullTrustStartupTasks"=dword:00000002
"EnableUwpStartupTasks"=dword:00000002
"SupportFullTrustStartupTasks"=dword:00000001
"SupportUwpStartupTasks"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]

"EnableFullTrustStartupTasks"=dword:00000002

"EnableUwpStartupTasks"=dword:00000002

"SupportFullTrustStartupTasks"=dword:00000001

"SupportUwpStartupTasks"=dword:00000001

This registry change needs a restart to be active.

This registry key in the user context controls how Teams starts automatically, allowing you to enable or disable it programmatically.

[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\TeamsTfwStartupTask]
"State"=dword:00000002
"UserEnabledStartupOnce"=dword:00000001

[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\TeamsTfwStartupTask]

"State"=dword:00000002

"UserEnabledStartupOnce"=dword:00000001

The state value defines what should be done.

0	The task is disabled.
1	The task has been deactivated by the user. Only the user can reactivate it.
2	The task is enabled.
3	The task is disabled by the administrator or group policy. Platforms that do not support startup tasks also report “DisabledByPolicy.”
4	The task is enabled by the administrator or through Group Policy.

New Teams crashes in Windows Server 2019

This issue occurs with FSLogix Hotfix 3 and earlier versions. After installing Hotfix 4 or a later version, this issue is resolved.

New Teams showed The parameter is incorrect

This issue occurs with FSLogix Hotfix 3 and earlier versions. After installing Hotfix 4 or a later version, this issue is resolved.

New Teams showed Invalid function

This issue occurs with FSLogix Hotfix 3 and earlier versions. After installing Hotfix 4 or a later version, this issue is resolved.

The Outlook Presence Indicator is not displayed

Check the following registry key:

[HKEY_CURRENT_USER\Software\IM Providers]
"DefaultIMApp"=reg_sz:MsTeams

1 2	[HKEY_CURRENT_USER\Software\IM Providers] "DefaultIMApp"=reg_sz:MsTeams

If the value “Teams” appears in the registry key, it refers to the Classic Teams and needs to be corrected.

Then check the status of the Presence module in the registry:

[HKEY_CURRENT_USER\Software\IM Providers\MsTeams]
"UpAndRunning"=dword:2

1 2	[HKEY_CURRENT_USER\Software\IM Providers\MsTeams] "UpAndRunning"=dword:2

If the value is set to 0, it doesn’t run; if it’s set to 1, it starts up; and if it’s set to 2, it runs.

New Teams does not automatically register in the user context

This error also occurs sporadically after installing FSLogix Hotfix 4. However, the latest versions of FSLogix include the “InstallAppxPackages” option, which permanently resolves this issue.

As a workaround, I also recommend implementing a scheduled task that runs when the user logs in, using the following command:

Add-AppxPackage -MainPackage "MSTeams_8wekyb3d8bbwe" -RegisterByFamilyName

1	Add-AppxPackage -MainPackage "MSTeams_8wekyb3d8bbwe" -RegisterByFamilyName

The New Teams icon is missing from the Start menu

This error also occurs sporadically after installing FSLogix Hotfix 4. However, the latest versions of FSLogix include the “InstallAppxPackages” option, which permanently resolves this issue.

The registry key DisableAppInstallsOnFirstLogon should also be set to 0. This can be done in the golden image using the following command.

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer /v DisableAppInstallsOnFirstLogon /t REG_DWORD /d 0 /f

1	reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer /v DisableAppInstallsOnFirstLogon /t REG_DWORD /d 0 /f

As a workaround, I also recommend implementing a scheduled task that runs when the user logs in, using the following command:

Add-AppxPackage -MainPackage "MSTeams_8wekyb3d8bbwe" -RegisterByFamilyName

1	Add-AppxPackage -MainPackage "MSTeams_8wekyb3d8bbwe" -RegisterByFamilyName

Log path for further information

%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs

SlimCore Optimization (VDI 2.0)

With this new optimization, Microsoft has brought about a true paradigm shift.

What is SlimCore?

New Media Engine Directly from Microsoft
Runs on the endpoint
Use Citrix only as a transport layer

Requirements

Windows Client
Teams ≥ 24295
VDA ≥ 2203 CU3
CWA ≥ 2203
Plugin: MsTeamsPluginCitrix
Published Desktop

Activate SlimCore

Virtual Channel Allow List (Citrix Policy)

MSTEAMS,C:\Program Files\WindowsApps\MSTeams*8wekyb3d8bbwe\ms-teams.exe
MSTEAM1,C:\Program Files\WindowsApps\MSTeams*8wekyb3d8bbwe\ms-teams.exe
MSTEAM2,C:\Program Files\WindowsApps\MSTeams*8wekyb3d8bbwe\ms-teams.exe

MSTEAMS,C:\Program Files\WindowsApps\MSTeams*8wekyb3d8bbwe\ms-teams.exe

MSTEAM1,C:\Program Files\WindowsApps\MSTeams*8wekyb3d8bbwe\ms-teams.exe

MSTEAM2,C:\Program Files\WindowsApps\MSTeams*8wekyb3d8bbwe\ms-teams.exe

Workspace App Plugin installation

CitrixWorkspaceApp.exe /installMSTeamsPlugin

1	CitrixWorkspaceApp.exe /installMSTeamsPlugin

After installation and activation, a local process named MsTeamsVdi.exe should appear

Firewall

UDP 3478–3481
TCP 80, 443

Classic:
Firewall “open” → still not working
→ SSL Deep Inspection enabled

Prerequisites for New Teams on VDI

Script based installation

Installation New Teams

Windows Server 2019 & Windows 10

Windows Server 2022 & Windows 11

Installation Teams Meeting Add-in

Profile management

Anti-Virus

Limitations

New features in New Teams for VDI

Known issues with existing solutions

Auto-start of Teams

New Teams crashes in Windows Server 2019

New Teams showed The parameter is incorrect

New Teams showed Invalid function

The Outlook Presence Indicator is not displayed

New Teams does not automatically register in the user context

The New Teams icon is missing from the Start menu

Log path for further information

SlimCore Optimization (VDI 2.0)

Requirements

Activate SlimCore

Teilen mit:

Like this:

Related posts: