New Teams meeting add-in is missing from outlook

Update for RDS setup on Windows Server 2019. The only way I got this to work was to make sure that the addininstaller.install state file was located here: "C:\Program Files (x86)\Microsoft\TeamsMeetingAddin<version>"

So I ran a command similar to this"

msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_X.X.X.X_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAddin<version>"

And the only way I can get this to install for a standard user is applying this registry edits to 0.  DisableUserInstalls, DisableMSI,

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

This is not ideal from an IT perspective when using RDS to prevent users from installing other software. Microsoft support please have your developers look into this. As your article says here this is a workaround, but not a good one at all. https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy

The instructions earlier in the thread do not make sense on my Windows 11 workstation. It references registry keys that simply don't exist on my machine, perhaps because the linked instructions are for VDI infrastructure and there is no commensurate documentation for workstations.

There is no "HKCU\Software\IM Providers" key.

There is no "HKCU\Software\Microsoft\office\Outlook" key.

Moreover, adding all of these keys to my workstation didn't solve the problem.

for over a month now, the .msi from the addin has been part of the new teams installation. you can extract it from the installation folder. theoretically, a machine-wide installation is possible. however, this did not work for us.

but what does work: define an applocker exception. then the .msi is automatically installed in the user context when the new teams is executed.

you can find the details in previous posts on this topic.

Why do you suggest going back to Classic teams when Classic teams is no longer available as of October?

The Microsoft co-pilot also suggested this and when I pointed out that classic was discontinued the answer was "oops my bad"

On a Windows Server 2019 setup with RDS users sharing a machine. It doesn't really work to do your steps for each user profile. This sounds very individual base with access to uninstall for each user profile on a local machine.