Knowledge Base

Back to support overview

We recommend using specific command lines to deploy TeamViewer successfully on your devices.

In this article, we will show you our recommended command lines and explain the meaning of each parameter.

This article applies to Corporate and Tensor license holders who want to deploy TeamViewer (version 15 or newer) on their Windows devices.

Recommended command lines

Important note: Please make sure to replace [your_xxx] with your own values.

Command line for the TeamViewer Host

start /wait MSIEXEC.EXE /i "PATH_TO_MSI_FILE\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=YOUR_CUSTOM_CONFIG_ID ASSIGNMENTID=YOUR_ASSIGNMENT_ID 

Command line for the TeamViewer Full client

start /wait MSIEXEC.EXE /i "PATH_TO_MSI_FILE\TeamViewer_Full.msi" /qn CUSTOMCONFIGID=YOUR_CUSTOM_CONFIG_ID ASSIGNMENTID=YOUR_ASSIGNMENT_ID

Note: If a custom Host configuration ID is used with the assignment parameter and includes a rollout configuration:

  • The device is managed via the assignment parameter.
  • A second assignment pop-up appears due to rollout setup.
    • Accepting or declining changes nothing — the device stays managed.
    • Avoid using rollout setup with assignment to prevent confusion.

Main parameters

We will explain here the parameters we used in our recommended command lines:

msiexec.exe /i

Installs the package.

/qn

Allows the silent installation.

“PATH_TO_MSI_FILE\TeamViewer_Host.msi”

Defines the installation path.

Note: It can also be on a network path.

ASSIGNMENTID=YOUR_ASSIGNMENT_ID

Assigns the device or endpoint to your tenant or company profile.

CUSTOMCONFIGID=xxxxxx

Applies your module's customization.

Note: This only applies to the TeamViewer Host.

SETTINGSFILE=”YOURPATH\yourfilename.tvopt”

Imports TeamViewer options.

For more information, please read the following article:

Export settings for deployment

Note: The value must be a valid absolute local path or a path to a network share. 

Don't use this parameter in combination with IMPORTREGFILE.

ENABLEOUTLOOKPLUGIN=true or false

Controls the de-/activation of the Outlook plugin

true: The TeamViewer Outlook plugin is activated after installation (default)

false: The TeamViewer Outlook plugin is deactivated after the installation

INSTALLSECURITYKEYREDIRECTION= 0 or 1

Installs a virtual device driver required for the security key redirection feature that allows the use of smart cards and fido-based devices through a TeamViewer session

0: Does not install the driver (Default)

1: Installs the driver

Desktop Shortcut

It will prevent the desktop shortcuts from being installed.

msiexec /i "Path\To\TeamViewer.msi" /qn ADDLOCAL=ALL REMOVE=f.DesktopShortcut

Note: If you deployed the TeamViewer Host in the past using the MSI file with the option DESKTOPSHORTCUTS=0, and now want to get rid of the shortcut, use the following command:

msiexec /i "Path\To\TeamViewer.msi" /qn REMOVE=f.DesktopShortcut

Install the TeamViewer VPN

Install the TeamViewer VPN driver with the following parameter:

INSTALLVPN=1

Error codes

Error code
Description
Problem/solution

1

Invalid command line arguments

You seem to have misspelled or used a wrong command.  Check your command and try again.

2

Signature verification error

-

3

Product not installed

TeamViewer is not installed. Install TeamViewer before doing an assignment.

4

Service config - access failed

// ComAPI

The assignment configuration could not be verified against the TeamViewer Cloud. Please try again later.

400

(40 under Linux/FreeBSD)

MDv2Assignment - invalid argument

There seems to be an error in the command line syntax or an invalid assignment ID is used. Please check your overall command line syntax and verify that the copied assignment ID is a valid configuration from the Management Console.

 401

 (41 under Linux/FreeBSD)

MDv2Assignment - service not running

The assignment can't be done because TeamViewer is not running properly. Please verify that the TeamViewer service is running.

402

 (42 under Linux/FreeBSD)

MDv2Assignment - service incompatible version

The TeamViewer service is incompatible with the executed TeamViewer client version. It seems that the installation wasn't completed properly. Please check the installation and if necessary re-install TeamViewer again.

403

 (43 under Linux/FreeBSD)

MDv2Assignment - not online

The TeamViewer client could not connect to the TeamViewer cloud in order to assign your device. Please check if the client is online and if your internet connection works properly and re-try the assignment. Consider using the retries option on the command line interface if that happens frequently.

404

 (44 under Linux/FreeBSD)

MDv2Assignment - already running

Another assignment process is already running. Please check the status of that assignment. You can do that for example by checking if the device is already registered as a managed device in the Management Console.

405

 (45 under Linux/FreeBSD)

MDv2Assignment - timeout

Your assignment attempt was timed out. Please try again. Consider increasing the timeout on the command line interface in case this happens frequently and/or the network is unstable e.g. mobile ones.

406

 (46 under Linux/FreeBSD)

MDv2Assignment - failed

Your assignment failed due to unknown reasons. Please save your logs and contact support.

407

 (47 under Linux/FreeBSD)

MDv2Assignment - access denied

You don't have the necessary permission to execute an assignment. Ensure that your user has local administrator rights.

408

(48 under Linux/FreeBSD)

MDv2Assignment - Denied by policy

The TeamViewer policy active on this device prevents removing the existing assignment state. Please disable the policy in the Management Console.

Note: Reassigning implicitly removes the existing state and is therefore also denied.

409
(49 under Linux/Free BSD)

MDv2Assignment - Device already managed

The device is already assigned to your company with the same assignment ID.