{"id":1738,"date":"2024-04-10T07:15:22","date_gmt":"2024-04-10T07:15:22","guid":{"rendered":"http:\/\/neu.koetzingit.de\/verfahren-zur-einrichtung-des-neuen-microsoft-teams-auf-der-plattform-windows-2022\/"},"modified":"2026-06-02T13:31:58","modified_gmt":"2026-06-02T13:31:58","slug":"verfahren-zur-einrichtung-des-neuen-microsoft-teams-auf-der-plattform-windows-2022","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/verfahren-zur-einrichtung-des-neuen-microsoft-teams-auf-der-plattform-windows-2022\/","title":{"rendered":"Procedure for setting up the new Microsoft Teams on the VDI W2022, W2019, W10, and W11 multi-user platform"},"content":{"rendered":"

M<\/span>Microsoft is forcing its customers to use the \u201enew teams<\/strong>\u201cto switch over\u2014and all by mid-2024! The feedback so far is that customers are once again Beta tester<\/strong> and Microsoft hasn't even conducted extensive testing. For example, there are issues with Microsoft FSLogix and the Outlook add-in. The \u201enew Teams\u201c is also available on a Server 2019 or Server 2022<\/strong> is yet another challenge. I've developed a PowerShell script that sets up Teams on Server 2022, Server 2019, Windows 10, and Windows 11 installed in a multi-user environment<\/strong> and the Outlook add-in is also taken into account.\u00a0<\/p>\n

<\/p>\n

The Team installation itself is straightforward, but it also requires installing the EdgeWebView Runtime version, and the whole process\u2014involving registry entries and the like\u2014isn't exactly easy. With that in mind, I have specifically chosen to install the new teams on VDI systems<\/strong>, <\/strong>PowerShell scripts were created for the installation.<\/p>\n

Let's start with FSLogix and the fact that FSLogix Profiles<\/strong> which is the best option, and whether using Office Containers or FSLogix profiles in combination with Office Containers causes issues with the \u201enew Teams.\u201c Microsoft has released an initial version of FSLogix to address this issue, which is intended to resolve several issues with the \u201enew Teams.\u201c The following paths should be specified as exceptions for FSLogix:<\/p>\n

<\/code>
AppData\\Local\\Packages\\MSTeams_8wekyb3d8bbwe\\LocalCache\\Microsoft\\MSTeams\\Logs<\/code>
AppData\\Local\\Packages\\MSTeams_8wekyb3d8bbwe\\LocalCache\\Microsoft\\MSTeams\\PerfLog<\/code>
AppData\\Local\\Packages\\MSTeams_8wekyb3d8bbwe\\LocalCache\\Microsoft\\MSTeams\\EBWebView\\WV2Profile_tfw\\WebStorage<\/code>
AppData\\Local\\Packages\\MSTeams_8wekyb3d8bbwe\\LocalCache\\Microsoft\\MSTeams\\EBWebView\\WV2Profile_tfw\\GPUCache<\/code><\/p>\n

Unfortunately, Microsoft has only made a half-hearted effort to update Teams, so while the installation is provided as an MSIX package, it includes an MSI package for the Teams Outlook add-in. This causes problems on Server 2022, and although there\u2019s been a lot written about it, there hasn\u2019t been a solution\u2014until now! After a long analysis of the problem on Server 2022, I noticed that Server 2022, as Standard .NET 6.x enabled<\/strong> has. Version \u201ecompatibility\u201c is a tricky thing, so I just .NET 3.x <\/strong>It was enabled on the server in 2022, and only then did the add-in load properly.
Server 2019<\/strong> requires a different approach and additional components. The script for 2019 also downloads all necessary media files at once and therefore requires an internet connection.<\/p>\n

However, for the loading to work at all, Outlook must be \u201eforced\u201c to do so using the following registry values:<\/p>\n

HKCU\\Software\\Microsoft\\Office\\Outlook\\Addins\\TeamsAddin.FastConnect<\/code>
LoadBehavior REG_DWORD = 0x00000003<\/code><\/p>\n

HKCU\\Software\\Microsoft\\Office\\Outlook\\Addins\\TeamsAddin.FastConnect<\/code>
Description REG_SZ = Microsoft Teams Meeting Add-in for Microsoft Office<\/code><\/p>\n

HKCU\\Software\\Microsoft\\Office\\Outlook\\Addins\\TeamsAddin.FastConnect<\/code>
FriendlyName REG_SZ = Microsoft Teams Meeting Add-in for Microsoft Office<\/code><\/p>\n

HKCU\\Software\\Microsoft\\Office\\16.0\\Outlook\\Resiliency\\DoNotDisableAddinList<\/code>
TeamsAddin.FastConnect REG_DWORD = 0x00000001<\/code><\/p>\n

However, the Teams add-in should also be installed manually so that it is loaded centrally for all users and is not stored in the user\u2019s profile. With this in mind, Teams\u2019 auto-update feature should also be disabled. The installation also requires the specific version of the add-in to prevent issues with future updates. The script takes all these points into account.<\/p>\n

\u00a0<\/p>\n

Citrix Virtual Channel<\/span><\/h3>\n

To ensure that the new Teams is fully functional, the following paths must also be added to the Approved List for Virtual Channels<\/strong> can be added to a Citrix policy:<\/p>\n