- TEAMVIEWER HOST UNATTENDED INSTALL INSTALL
- TEAMVIEWER HOST UNATTENDED INSTALL SOFTWARE
- TEAMVIEWER HOST UNATTENDED INSTALL PASSWORD
You need a teamviewer account for this to work correctly. The steps using Teamviewer 12 (And I will guess future versions) are the following assuming that: It also changed radically on Teamviewer 12. My solution (Done with Teamviewer 12 as of the time of this answer) relied mostly on the server (The one I wanted to control) and very little with the guest (The one that will have all the mighty power of the universe!).
TEAMVIEWER HOST UNATTENDED INSTALL PASSWORD
When TeamViewer is deployed, the exported password will automatically be set as the personal password on all deployed systems.Well it just so happened I was having the SAME EXACT issue.
Store the resultant TeamViewer_Settings.reg file on a network share where your MSI file exists. Check the Export personal password option and enter and confirm a desired personal password to set for each unattended host install. Enter TeamViewer_Settings.reg as the filename and click Save. On a workstation with the same version of TeamViewer installed, select Extras->Options->Advanced->Show Advanced Options->Export options to a *.reg file. reg file, naming it TeamViewer_Settings.reg (the name matters) and storing it in the same share as the TeamViewer MSI deployment installation file. 
Finally, if you want to push a uniform personal password to your deployed unattended host installs (generally not recommended, but sometimes required), you’ll have to do it by exporting a. Start /wait \\SERVER\SHARE\TeamViewer_Assignment.exe -apitoken XXXXXXX-XXXXXXXXXXX -datafile “C:\Program Files (x86)\TeamViewer\AssignmentData.json” -allowEasyAccess=true -devicealias “$” Start /wait msiexec.exe /i \\SERVER\SHARE\Teamviewer_Host-XXXXXXXX.msi /qn Now run the TeamViewer Assignment tool and it should succeed. After complete removal, re-install TeamViewer. Reg delete “HKLM\Software\Wow6432Node\TeamViewer” /f Start “C:\Program Files (x86)\TeamViewer\uninstall.exe” /S REM Uninstall TeamViewer and remove registry entry (needed if re-assigning to a different account) IF EXIST “%VER%” (GOTO :END) ELSE (GOTO :UNINSTALL) Set “VER=C:\users\public\desktop\TeamViewer 13 Host.lnk” REM Check if TeamViewer 13 is already installed (crude test that may not work for everyone). If “%ERRORLEVEL%”=”0” (GOTO :CHECK) ELSE (GOTO :END) Tasklist /FI “IMAGENAME eq TeamViewer.exe” 2>NUL | find /I /N “TeamViewer.exe”>NUL offREM Check for running TeamViewer processes. Here is an example of a script for removing 圆4 versions of older TeamViewer versions: Run a GPO with a script to completely remove TeamViewer first. 
If you’re like me, where the customer used a new TeamViewer ID to sign up for the upgraded version, you’ll need to completely uninstall TeamViewer host on all workstations and then re-install.
TEAMVIEWER HOST UNATTENDED INSTALL INSTALL
Running the Teamviewer_Assignment.exe on an existing install that was upgraded via deployment will yield the following error:Įrror: Assignment failed with: Reading datafile “C:\Program Files (x86)\TeamViewer\AssignmentData.json” failed with: File not found
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. TEAMVIEWER HOST UNATTENDED INSTALL SOFTWARE
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)
