teamviewer for windows install via command line

Please test the above command and reply back with results. The bold part actually comes through as a codeblock for base64 decode (I think) because -SecureParameters will ‘encrypt’ parameters set there (best practice for any API keys, passwords, etc you pass using PSADT). Msiexec /i TeamViewer_host.msi /qn ASSIGNMENTOPTIONS='–alias %COMPUTERNAME% -grant-easy-access -reassign' CUSTOMCONFIGID=“xxxxxx” IMPORTREGFILE=“1” APITOKEN=“xxxxxx-xxxxxxxxxxxxxxxxxxx” This results in msiexec receiving the following string (more or less): With the quotes as I have placed them here, the PSADT script will pass the literal strings in the parameters into a command–where they will then be translated because the outermost quotes themselves don’t pass through. In powershell, double-quotes indicate a string (' '), whereas single-quotes (’ ') indicate a literal string–with single quotes, powershell will not substitute or translate anything within them, regardless if there is syntax written.

Look at your string, notice how you aren’t placing single/double quotes correctly. Using the toolkit, my first draft would be this:Įxecute-MSI -Action Install -Path 'TeamViewer_Host.msi' -Parameters '/qn' -AddParameters 'ASSIGNMENTOPTIONS='–alias %COMPUTERNAME% -grant-easy-access -reassign'' -SecureParameters 'CUSTOMCONFIGID=“xxxxxx” IMPORTREGFILE=“1” APITOKEN=“xxxxxx-xxxxxxxxxxxxxxxxxxx”' -PassThru The last time I wrapped TV was TV12 and before I used PSADT. Execute-Process 2:46:28 PM 18776 (0x4958)Įxecute-MSI -Action Install -Path ‘TeamViewer_Host.msi’ -AddParameters ‘CUSTOMCONFIGID=“xxxxxx” IMPORTREGFILE=“1” APITOKEN=“xxxxxx-xxxxxxxxxxxxxxxxxxx” ’ Consult the Windows Installer SDK for detailed command line help. :: Execution failed with exit code : Invalid command line argument. : : Executing / L * v “ C : WINDOWS Logs Software TeamViewer_Host_Install. With TeamViewer 14 is uses extra parameters that I just can’t seem to get correct.

Teamviewer for windows install via command line