What about the organizations that block per-user installs with this policy:
Prohibit User Installs (admx.help)
In the case where orgs block user based msi installs, this automated install per user of the meeting addin is blocked. The orgs that have done this are not going to suddenly reverse course and remove this policy just to allow the teams meeting addin to install, and update on whatever cadence MS decides.
And, any mention of installing this manually as a per-machine install with ALLUSERS=1 is just asking for trouble. Sure - it might work right now, but the plugin will never auto-update this way. You'll always be waiting for that first set of tickets to start getting generated that it's not working, to find out you need to separately push another update to the addin MSI again. (This is why MS made it per-user after all... so they could update it along with teams at whatever cadence they deem fit).
What's the real way out here?
Registry key when blocked:
| Registry Hive |
HKEY_LOCAL_MACHINE |
| Registry Path |
Software\Policies\Microsoft\Windows\Installer |
| Value Name |
DisableUserInstalls |
| Value Type |
REG_DWORD |
| Value |
1 |