New Teams / Meeting addin missing on Windows Server 2019 RDSH / Autostart Issue

calaneo 

We are also expericing the same issue with Window Server 2019 and New Teams in our citrix environment. 

calaneo We have the same issue as well.  Any direction Microsoft?

Server 2019

installed Teams via DISM

Have presence working seemingly after following instructions for Server 2019 in the article linked below.  Have over 100 users on Server 2019 Session Hosts.  So needing a solution for this before the deprecation of Classic teams.

New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams | Microsoft Learn

calaneo 

Hi, we faced the same problem after installing the new MS Teams. In the event log you see, that the system tries to install the addin in user context from an MSI package, but the installation fails with error code 1625. The MSI is located at ‘C:\Program Files\WindowsApps\MSTeams_24137.2216.2931.2440_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi’ and can also be manually executed and installed for all users. After i did that, the addin finally works in Outlook.

I don't know what will happen, when MS Teams get's an update. I would recommend to disable the auto update function.

calaneo Dirkberlin Spragaz kingrafe 

Perhaps my persistence to get this to work in our 2019 environment will help some of you.

Installing Teams into a 2019 RDSH Session Host Environment:

1. Download the latest MSIX file for the new Microsoft Teams
2. Save to a location on the C: drive of the server
3. run the following powershell command to install New Teams but replace file location to be where you stored your MSIX download from step 1....... DISM /Online /Add-ProvisionedAppxPackage /PackagePath:"C:\users\%username%\downloads\MSTeams-x64.msix" /SkipLicense
4. (Due to UAC issues) From another computer navigate to the c$ administrative share of your Server 2019 session host and locate the "c:\program files\windowsapps\MSTeams_#####.###.####.####_x64__iwekyb3d8bbwe\" folder (Example: \\rdsh01\c$\program files\windowsapps\MSTeams_#####.###.####.####_x64__iwekyb3d8bbwe\)
5. copy the "MicrosoftTeamsMeetingAddinInstaller.msi" file to the c:\ drive somewhere on the RDSH server
6. Run the msi file acquired in step 5 on the RDSH server and install for everyone (administrative command prompt and in install mode). Also install path should be to C:\program files (x86)\Microsoft\TeamsMeetingAdd-inn\#.##.#####\ (with # symbols being version number)
7. Find section titled “Outlook presence integration with New Teams in Windows Server 2019” from the article https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy?fbclid=IwAR3hGgEa-B4U_o7uveN1ZL9BV-NkR6vZqh5j-tGm9d4Wg0YA17eVJaBalm8
8. Click on the link in step 4 of this section to download the presence integration installer
9. If the server is up to date on all cumulative updates you should only need to open the local group policy on the machine by opening gpedit.msc from a run dialog box and enabling the policy at the following location "Computer Configuration\Administrative Templates\KB5035849 240209_02051 Feature Preview\Windows 10, version 1809 and Windows Server 2019\"
10. Don't worry about the ALLUSERS switch and running from a command line. Run from GUI after putting server into install mode. Run the installer acquired in step 8 and choose to install for "Everyone" or "all users" in the dialog screen when installing.
11. restart the RDSH server

AUTO STARTING

Auto Starting Teams - Since "new teams" is now a Windows App creating a shortcut on the desktop and auto starting it is tricky. From a run dialog box go to Shell:appsfolder Here you will find a shortcut for the New Teams app. Copy/paste to c:\users\public\desktop so it is on the desktop of everyone that logs into the RDSH server. Then also get it copied to appdata\roaming\Microsoft\Windows\Start Menu\programs\startup folder for each user that logs into the RDSH server needing teams to auto launch. I accomplish this with a script I have users run that also cleans up Teams and fixes other things in their Profile, but you can accomplish in other ways I am sure.

CORRUPT INSTALLATIONS

I have had the New Teams seemingly become corrupt and I try uninstalling from the apps area in Settings but any uninstall/re-install/etc action from that area doesn't seem to remove it. If you find yourself in this situation then you can run the following powershell commands to find your Package Name of what is supposedly installed and then remove it via powershell.

Get-AppxProvisionedPackage - Online

From this command you will be able to find the PackageName of New Teams that is installed. Then use that name to run the following command.

Remove-AppxProvisionedPackage -PackageName MSTeams_#####.####.####.####_x64__8wekyb3d8bbwe"

Then you can install a fresh version.

NOT QUITE CORRUPT

After figuring out the technique above when thinking the installation was corrupt I later found out that Windows Apps can be blacklisted if they malfunction which prevents them from running. You can remove New Teams from the blacklist by setting a registry value to 0 that is created when blacklisted. Modify the PackageStatus DWORD value in HKLM\Software\Microsoft\Windows\CurrentVersion\AppModel\StateChange\PackageList\MSTeams_#####.###.####.####_x64__8wekyb3d8bwe to be a zero. I set a group policy to enforce this to be a zero after a new version is installed (obviously the # signs in my example are placeholders for the actual version number installed).

I unfortunately tried to have teams not auto update but that didn't work for me and then when it did auto update and malfunctioned it would blacklist it again and I would have to update my Group Policy or manually update the registry on each server. Not elegant but I have a nightly powershell script that does many things and I included a check for new folders in C:\program files\WindowsApps\ and I get an email if a new folder is created within the last 7 days or so....that way I have a few reminders to update the Group Policy for my RDSH servers to get ahead of a blacklist event. Double unfortunately for a lot of reasons the installation folder for New Teams changes its name based on the version number creating some of these additional steps.

TEAMS MEETING ADDIN STILL NOT FUNCTIONAL

Probably for new installations as well and definitely for us since we transitioned from Classic Teams we had to apply group policy registry updates for users to get the New Teams Meeting Addin to work without relying on the previous installation within their profile from Classic Teams. So after the Teams Meeting Add-in is installed from the New Teams installation folder as I described in the beginning.......the following registry entries for each user need to be updated....Some based on the version number (which again is in the installation path of the meeting add-in installation).

I copied these from my script I fix profile issues with and are in the format of reg add commands but you can configure in whatever manner works for you. I also re-enforce the once with version numbers of the Teams Meeting add-in installation directory via Group Policy so I can easily update them in the future when I need to manually update the Teams Meeting Add-in.

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D} /ve /t REG_SZ /d "FastConnect Class" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\InprocServer32 /ve /t REG_SZ /d "C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.23.35502\x86\Microsoft.Teams.AddinLoader.dll" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\InprocServer32 /v ThreadingModel /t REG_SZ /d "Apartment" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\ProgID /ve /t REG_SZ /d "TeamsAddin.FastConnect.1" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\Programmable /ve /t REG_SZ /d "" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\TypeLib /ve /t REG_SZ /d "{C0529B10-073A-4754-9BB0-72325D80D122}" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\Version /ve /t REG_SZ /d "1.0" /f

reg add HKCU\Software\Classes\WOW6432Node\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\VersionIndependentProgID /ve /t REG_SZ /d "TeamsAddin.FastConnect" /f

reg add HKCU\Software\Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\InprocServer32 /ve /t REG_SZ /d "C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.23.35502\x86\Microsoft.Teams.AddinLoader.dll" /f

reg add HKCU\Software\Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\InprocServer32 /v ThreadingModel /t REG_SZ /d "Apartment" /f

reg add HKCU\Software\Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\ProgID /ve /t REG_SZ /d "TeamsAddin.FastConnect.1" /f

reg add HKCU\Software\Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\TypeLib /ve /t REG_SZ /d "{C0529B10-073A-4754-9BB0-72325D80D122}" /f

reg add HKCU\Software\Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\Version /ve /t REG_SZ /d "1.0" /f

reg add HKCU\Software\Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\VersionIndependentProgID /ve /t REG_SZ /d "TeamsAddin.FastConnect" /f

reg add HKCU\Software\Classes\TypeLib\{C0529B10-073A-4754-9BB0-72325D80D122}\1.0\0\win32 /ve /t REG_SZ /d "C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.23.35502\x86\Microsoft.Teams.AddinLoader.dll" /f

reg add HKCU\Software\Classes\TypeLib\{C0529B10-073A-4754-9BB0-72325D80D122}\1.0\0\win64 /ve /t REG_SZ /d "C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.23.35502\x64\Microsoft.Teams.AddinLoader.dll" /f

reg add HKCU\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect /v Description /t REG_SZ /d "Microsoft Teams Meeting Add-in for Microsoft Office" /f

reg add HKCU\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect /v FriendlyName /t REG_SZ /d "Microsoft Teams Meeting Add-in for Microsoft Office" /f

reg add HKCU\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect /v LoadBehavior /t REG_DWORD /d 00000003 /f

OBVIOUSLY research these changes and modify registry at your risk and verify things in test before putting into production.  This is just what has worked for me.