This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Has anyone been able to deploy Microsoft Teams during the OS build task sequence? If so, how?
Given the MSI is Install for User I cant see how it can be done.
Thanks
David Z
Hi,
Thanks for posting in Microsoft Q&A forum.
We recommend that you deploy the package to the computer, so all new users of the machine will also benefit from this deployment. So please change Install behaviour to Install for System to have a try.
The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of the Teams app will be installed in that user's AppData folder. If a user already has the Teams app installed in the AppData folder, the MSI installer will skip the process for that user.
A similar thread for your reference: How to Deploy Microsoft Teams through SCCM
Note: This is non-Microsoft link, just for your reference.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I changed it to 'Install for system'. It installed successfully during the OSD task sequence.
However, the shortcut on the desktop doesnt work. It refers to 'update.exe' within the local profile and that file doesnt exist.
Hi,
Thanks for your reply. Have you change the default install locations? If yes, please try the default location C:\Program Files (x86)\Teams Installer on 64-bit operating systems and C:\Program Files\Teams Installer on 32-bit operating systems.
Thanks and regards,
Simon
When deploying the MSI you cannot change the install location. Besides, there is a Teams Installer under program files. But still logging on does nothing and the shortcut doesnt work.
Hi,
Thanks for your reply.
This is a strange issue. I will do more research, if there is any update, I will let you know. Thanks for your understanding.
Best regards,
Simon
I am going to give this a try:
https://sysmansquad.com/2021/01/26/trigger-teams-installer-for-user-after-machine-wide-installer/
Hi,
Thanks for your reply.
As a support Engineer, we are also responsible for collection customer feedback of product itself and try the best to deliver it to the product team, in order to improve customer experience. About disabling desktop shortcut creation of Windows Teams installation, we will summarize this and try to deliver it to product team, but not guaranteed. Once there is any feedback, we will get back to you at the first time. Thank you for your kind understanding.
Best regards,
Simon
What is happening is that the Teams installer is installed under 'Program Files (x86)', but the autorun registry key is pointing to 'Program Files'. I have put in a support call to MS about this.