4 Comments

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 taken into account by the script.

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.

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 

 

Write comments...
or post as a guest
People in conversation:
Loading comment... The comment will be refreshed after 00:00.
  • This commment is unpublished.
    Bryan McNally · 3 days ago
    Will this work for Amazon WorkSpaces which runs on either Server 2019 or Server 2022? 
  • This commment is unpublished.
    DNY · 8 days ago
    what a terrible package, it's working except i cant get rid of the shortcut in startmenu,  edit teh package didn't work, any options? we are using ivanti workspace control, tricks to hide the shortcut?

    • This commment is unpublished.
      Thomas Kötzing · 8 days ago
      @DNY I don't write about stuff, that I haven't done myself. Editing the MSIX packages does work, but you have to do it in the right way.
      Important things editing the teams msix package:
      - You must sign it with your own signing certificate
      - The signing certificate must be trusted by the system
      - You must increase the version number
      - You must NOT use the teams teamsbootstrapper with your own package
      - I used the free MSIXTroubleshooter

      I tried FSLogix to hide teams but didn't work for the start menu.

  • This commment is unpublished.
    Brian · 1 months ago
    How can I tell if I am using the TEAMS for VDI app?

    This is what is displays in the about App, there is no mention of VDI

    Version
    You have Microsoft Teams version 24033.811.2738.2546.
    Issue occurred while checking for updates. Citrix HDX Optimized.
    The client version is 49/24031414718.

    • This commment is unpublished.
      Thomas Kötzing · 1 months ago
      @Brian The new Microsoft Teams supports VDI/DaaS since version 2.1 (2023)
      There is no specific „Teams for VDI“ version.
      You are using version 2.4
  • This commment is unpublished.
    Danny · 1 months ago
    Nice scripts, but how to prevent the autoupdate, reg key is not working in server 2022. Teams Client shows Update message and that is not working because it's Citrix
    • This commment is unpublished.
      Geert · 1 months ago
      @Thomas Kötzing That is correct. I had this issue within Citrix because I ran Teams once before applying the disable autoupdate key. The update prompt kept appearing for the test account until I cleaned the FSLogix profile.
    • This commment is unpublished.
      Thomas Kötzing · 1 months ago
      @Danny Hi Danny,
      I had the message too, but at the end it was old teams stuff in the profile. With a fresh profile, I didn't get the update message. Clean out old directories etc. from the users' profile and check again.