If systems already have TeamViewer installed (either deployed or manually installed), you won’t be able to use the TeamViewer assignment tool to assign newly deployed unattended host installs (where the newest version was just installed over an existing version) to a new or different TeamViewer account.Start /wait msiexec.exe /i \\SERVER\SHARE\TeamViewer_Host-idcXXXXXXX.msi /qn What finally worked consistently for me was this simple batch script (where XXXXXXX is your deployment ID):.But after finding that most of my deployments failed with %%2 and %%1274 even after adding a 30 second delay to Computer Configuration > Policies > Administrative Templates > System > Group Policy > Startup policy processing wait time, I decided i had wasted enough time troubleshooting this method and found the script method to work much better. I tried the GPO software installation package method first because it’s one of the recommended ways to deploy the TeamViewer MSI via the official deployment documentation on P7.Deploy GPO using a batch script or powershell instead and save yourself the aggravation of troubleshooting why some workstations won’t install the package.
Don’t try to deploy your customized TeamViewer unattended host MSI application via the GPO software installation package method in Active Directory.Here’s what I’ve learned after looking at several forum posts: So I’ve been playing with deploying TeamViewer 13 unattended host for several hours today and have reached the conclusion that the deployment documentation is just grossly inadequate.
0 kommentar(er)
