There is a known issue with the MicrosoftTeamsMeetingAddinInstaller.msi that is baked into the new Teams client. Microsoft have full details of this issue here: https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#teams-meeting-add-in.
Symptoms
You can confirm you’re experiencing this issue by checking the installation logs that are stored at:
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs\tma_addin_msi.txt.
The error will read something like:
Info 1625. This installation is forbidden by system policy. Contact your system administrator.
Cause
As per the Microsoft article:
“This error is caused by GPOs affecting Windows Installer. This includes DisableUserInstalls, DisableMSI, or AppLocker policies based on Publisher rule conditions, or a RuleCollection for MSI installs.”
Resolution
There are two ways to resolve this issue. You can either exclude the installer path from the relevant GPOs as covered in the Microsoft article linked above, or you can script the installation as an account that will not be blocked. I’m going to cover the second solution in this post, as this won't involve making any potentially security-implicating changes to the environment.
Using Nerdio Manager for MSP (NMM), we can configure a scripted action that will install the add-in for us, however, you can manually install it by running the script locally using an account with administrator privileges or by running the .MSI from the GUI. In this post, I’ll demonstrate using NMM to automate this for us.
Create a new scripted action within NMM using the ‘SCRIPT EXECUTION MODE’ of ‘Combined’ and use the following script:
The script isn’t too complex, and the comments generally cover what’s happening, but let’s quickly break down exactly what this script is doing:
The first block, running lines 3 – 7:
- This is confirming that the account the script is running as has administrator rights. If running this as a scripted action, it will be running as system and will have administrator rights.
The second block, running lines 9 – 14:
- This is verifying that new Teams is installed and saving the Teams version to the variable $NewTeamsPackageVersion.
The third block, running lines 16 – 23:
- This is determining what path the .MSI should be stored at by injecting the value of the $NewTeamsPackageVersion into the standard path that the Teams app is saved at.
- It also retrieves and saves the version of the Teams Meeting add-in .MSI to the variable $TMAVersion.
The fourth block, running lines 25 – 27:
- This brings everything together and initialises the $TargetDir variable, which is where the add-in will be installed.
- It also configures the relevant parameters for the .MSI installation.
The final block, running lines 29 – 32:
- Begins the .MSI installation.
Quick note: if you’re using scripted actions to both install new Teams and to fix the add-in, make sure you run the install Teams action first. If new Teams isn’t installed on the device, the above script will fail.
Troubleshooting
Here are some further steps that can be taken if the issue persists through the above steps.
Verify that the meeting add-in is installed:
- Check installed programs via either control panel or the settings app.
- Confirm that ‘Microsoft Teams Meeting Add-in for Microsoft Office’ is installed.
Assuming the add-in is installed, force Teams to re-register with the add-in:
- Restart the Teams desktop client.
- Sign out and then sign in to the Teams desktop client.
- Restart the Outlook desktop client.
Further troubleshooting advice available from Microsoft here: https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/meetings/resolve-teams-meeting-add-in-issues.
Comments (5 comments)