Procedure for setting up the new Microsoft Teams on VDI W2022, W2019, W10 and W11 Multiuser platform

Microsoft is forcing its customers to switch to the "new Teams" by mid-2024! The feedback so far is that customers are once again beta testers, and extensive tests have not even been carried out by Microsoft. There are problems with Microsoft FSLogix and the Outlook add-in. The "new Teams" on a Server 2019 or Server 2022 is yet another challenge. I have developed a Powershell scripts that installs Teams on Server 2022, Server 2019, Windows 10 and Windows 11 multiuser and also takes the Outlook add-in into account. 

The Teams installation itself is simple, but also requires the installation of the EdgeWebView Runtime version and does not necessarily make the entire installation with registration values etc. easy. Considering this, I have explicitly created a Powershell script for the installation of the new Teams on VDI systems. 

Let's start with FSLogix and the fact that FSLogix Profile is the best option and Office Container or FSLogix Profile together with Office Container leads to problems with the "new Teams". Microsoft has released a first version of FSLogix in this regard, which should fix some of the problems with the "new Teams". The following paths should be specified as exceptions for FSLogix:

<!--Microsoft New Teams-->
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs</Exclude>
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLog</Exclude>
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage</Exclude>
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\GPUCache</Exclude>

Unfortunately, Microsoft has only half-heartedly renewed Teams and so the installation comes as an MSIX package, but includes an MSI package for the Teams Outlook Add-in. This leads to problems on Server 2022 and much is written about it, but no solution yet! After a long analysis of the problem on Server 2022, I realized that Server 2022 has .NET 6.x enabled by default. The "compatibility" of versions is such a thing, and so I simply activated .NET 3.x on Server 2022 and only then was the add-in loaded properly.
Server 2019 needs a different approach and additional components. The script for 2019 downloads all required media and the reason you need free internet access.

In order for the loading to work at all, Outlook must be "forced" to do so via the following registry values:

HKCU\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect
LoadBehavior REG_DWORD = 0x00000003

HKCU\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect
Description REG_SZ = Microsoft Teams Meeting Add-in for Microsoft Office

HKCU\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect
FriendlyName REG_SZ = Microsoft Teams Meeting Add-in for Microsoft Office

HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList
TeamsAddin.FastConnect REG_DWORD = 0x00000001

However, the Teams Add-In should also be installed manually so that it is loaded centrally for all users and is not located in the user's profile. Considering this, the Teams auto-update should be deactivated. The manual installation also requires the version of the add-in so that there are no problems with subsequent updates. All these points are considered by the script.

Citrix Virtual Channel

For the new Teams to be fully functional, the following paths must also be added to the Virtual channel allow list in a 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

Shortcut for the new Teams

Creating a shortcut for the new teams is pretty simple, by using msteams:/ as location. Basically, this is a URL shortcut.

New teams shortcut in Windows start menu

The shortcut in the start menu can be removed, by editing the MSIX package. You only have to add AppListEntry="none" in the manifest file. You edit the teams MSIX package with the MSIX Packing Tool, but you have to sign it with your own certificate when saving the file.

Teams shortcut not in Windows start menu

It can happen that the Teams shortcut does not appear in the start menu. This is a bug which can be fixed by the following exclusion
AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState

Switching from Teams Classic to Teams new

Teams Classic is simply uninstalled on the server, and then the new Teams is installed using a script. However, the problem is the user profiles that still contain components of Teams Classic. This can lead to various problems and should therefore be cleaned up directly when logging in. To accomplish this, execute the following Powershell commands:

Remove-Item -Path "HKCU:Software\Classes\ms-teams" -Recurse -Force
Remove-Item -Path "HKCU:Software\Classes\msteams" -Recurse -Force
Remove-Item -Path "HKCU:Software\Classes\CLSID\{00425F68-FFC1-445F-8EDF-EF78B84BA1C7}" -Recurse -Force
Remove-Item -Path "HKCU:Software\Classes\CLSID\{d1b22d3d-8585-53a6-acb3-0e803c7e8d2a}" -Recurse -Force
Remove-Item -Path "HKCU:Software\Classes\TeamsURL" -Recurse -Force
Remove-Item -Path "HKCU:Software\Classes\WOW6432Node\CLSID\{00425F68-FFC1-445F-8EDF-EF78B84BA1C7}" -Recurse -Force
Remove-Item -Path "HKCU:Software\Classes\WOW6432Node\CLSID\{409667f8-3eb8-4181-1c94-941bd33cdfad}" -Recurse -Force

Remove-Item -Path "$env:USERPROFILE\AppData\Roaming\Microsoft\Teams" -Recurse -Force
Remove-Item -Path "$env:USERPROFILE\AppData\Local\Microsoft\TeamsMeetingAddin" -Recurse -Force

Complete scripts on Github

For Windows Server 2022, Windows 10 and Windows 11 multiuser
https://github.com/Koetzing/Powershell-Scripts/blob/main/install-new-teams.ps1

For Windows Server 2019
https://github.com/Koetzing/Powershell-Scripts/blob/main/install-new-teams-srv2019.ps1