That’s because it only installs on the next login! The ‘stub’ has deployed successfully, but the user based install has not initiated. We also saw similar ‘confusing’ behaviour for the user – the install runs and succeeds, but no Teams installed. Firstly, we haven’t used Install for User – seems more sensible to Install for System if it is machine wide and essentially just stages the install? MS documentation is a little vague here in my opinion. We have just started looking at this and I think there a couple of ‘gotchas’ to consider. Thanks for all you have done for the MECM community. I subscribe to your emails and they have been very helpful. Microsoft is pretty smart, they probably have all of this covered, but it is something to be aware of. In any case we will have to wait some months to see if the Teams machine-wide installer gets updated and if it does how does it interact (if at all) with the current updated user instances?
Using the information from Microsoft and a script they created as a way to completely uninstall teams from all users on a machine, our wrapper can be used with the MECM Application “Repair” to completely remove all user instances of the teams and the Teams machine-wide installer and then install the latest version of the Teams Machine Wide installer. Our teams package was created using the PowerShell Application Tool Kit wrapper.
If we update the Teams machine-wide installer in MECM a couple of times a year and use it for new installs only then if Microsoft supports it for at least 3 years our lease replacements will solve the problem(if there is one) as they will just go away. This is a very remote scenario I suppose. He will click on the Teams icon on the desktop and invokes the machine-wide installer, which by now is at least a year old, it will probably work just fine, but will not support any new features unless it starts auto updating, which it should as long as Microsoft supports that version of the Machine-wide installer. But lets say a year or two from now the user leaves the company and a new user logs in. That will work just fine, automatic updates for the users install. The machine wide installer does not get updated by Office 365 ProPlus update as far as I have observed, nor does it need to since at that point the user has clicked on the teams icon on the desktop and the teams machine wide installer has installed into the users profile the same version which WILL get updated using Office 365 ProPlus update. Click CLOSE to finish the deploy MS Teams using SCCMĪnoop, You are correct the teams machine-wide install for new builds works well, we have deployed it in our enterprise successfully, although I used a file version detection method.Create a deployment alert when the threshold is higher than the following: Disabled.Create a deployment alert when the threshold is lower than the following: Disabled.