This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 16%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EU%3C/text%3E%3C/svg%3E)
Hi everyone,
Lately we are receiving multiple complaints from users who are not able to start Teams (path doesn't exist).
Instead of installing Teams for these users one by one, we would like to deploy Teams (machine-wide) via GPO.
I already downloaded the Teams Machine-wide installer (msi) and created a new GPO, added the msi to new package in software installation, but unfortunately after applying the GPO to the pc, Teams won't get installed.
Is there any way to deploy Teams through GPO (perhaps with help of a Powershell script)?
Thanks in advance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 80%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Hi,
Yes, it's possible to deploy teams through powershell script :
msiexec /i "\Teamsfilepath\Teams_windows_x64.msi" OPTIONS="noAutoStart=true"
You can create powershell script and add it as Startup/Shutdown scripts through GPO.
Please don't forget to mark helpful answer as accepted
Hi @Thameur-BOURBITA
Thanks for your reply.
I created a powershell script with the code that you mentioned and added it to a Startup GPO.
On one test machine I ran the powershell script manually and after giving permission it installs the Machine-Wide installer (I can see it under Programs in Control Panel and it creates the Teams installer folder in Program Files).
However, on another test machine I waited for the GPO/script to do it's work, but nothing happens on that machine (rebooted it several times).
I tried adding /qn ALLUSERS=1 to the code, so now my code is:
msiexec /i "\\Domain\NETLOGON\Teams_windows_x64.msi" /qn ALLUSERS=1 OPTIONS="noAutoStart=true"
Is this code (still) correct after the changes to it?
I think ALLUSERS=1 is not mandatory. You can keep /qn to launch the installation without GUI.
Please don't forget to mark helpful answer as accepted
@Thameur-BOURBITA I removed ALLUSERS=1 and kept /qn. However, it the GPO/script still does not apply automatically. When I run the script manually, everything is good and the Machine-Wide installer is installed in Program Files.
Do you know what the issue could be that it doesn't run automatically?
Can you add logging flag /l*v C:\temp\teams_install.log to get more details about the error ?
***Please don't forget to mark helpful answer as accepted ***
@Thameur-BOURBITA I added the code you mentioned in the script, but it doesn't create a log file.
When I run the script manually, in the Event Viewer I see an error event saying:
Product: Teams Machine-Wide Installer -- Error 1303. The installer has insufficient privileges to access this directory: C:\Program Files (x86)\Teams Installer. The installation cannot continue. Log on as adminstrator or contact your system administrator.
However, I am logged in as a domain admin while running the script manually.
I found Microsoft article about how run teams msi through powershell, you can follow it.
I think the you don't run the power-shell script as administrator access issue :
Bulk install Teams using Windows Installer (MSI)
Bulk install Teams using Windows Installer (MSI)
Hi @Uhmazing34
Regarding the GPO, if you choose to launch the script or MSI during the Startup , the network may not be available on the workstation to access on the share where you will put the MSI file.
I suggest you to set all your computer through GPO or registry key to wait for the network to be fully initialized at startup and the group policy will be applied in the background after the network becomes available. I suggest to enable this settings then retry to deploy MSI through GPO :
Always wait for the network at computer startup and logon
Please don't forget to mark helpful answer as accepted*
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back.
Hi, thank you for your comments.
Instead of running the script at startup, I set up the GPO as a scheduled (immediate) task.
Via this way it places the installer under Program Files (x86), so it seems to work correctly.
I just haven't managed to get to the point where it also automatically installs Teams for users who do not have Teams installed yet. For now, I have sent out a manual instruction so the users will have to click manually on the Teams.exe file in the Teams installer folder, after which Teams installs succesfully.
Hi @Uhmazing34
Glad to hear that.
Scheduled task is also a good idea to launch the script, because it's use a system account with full control on the machine and you don't need network to access on MSI share
Please don't forget to mark helpful answer as accepted if your problem is resolved
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
