A PowerShell integration script to synchronize users of Active Directory (AD) groups to a TeamViewer company via REST based API.

Further information can be found in the knowledge base article "Active Directory-Connector".

You can download the AD Connector package from releases page.

The script comes with a configuration interface that can be started by executing the Invoke-Configuration.ps1 PowerShell script in the TeamViewerADConnector directory, or by double-clicking the Configure TeamViewer AD Connector.bat batch file.

The graphical configuration provides the following features:

• Validate the entered TeamViewer API token.
• Show and adapt the synchronization configuration.
• Manually trigger a run of the synchronization.
• Install / uninstall a scheduled task to run the synchronization script automatically.

The graphical configuration requires to be run with elevated user rights to be able to install and uninstall the scheduled task. The script automatically asks for elevated rights (if required).

• Parameter ApiToken:

  The TeamViewer API access token that is used for accessing the TeamViewer company user directory. For more information on how to create such a token please visit: TeamViewer for developers

  The TeamViewer API token requires the following access permissions:

  • User management: Create users, view users, edit users (corresponds to the WebAPI permissions Users.CreateUsers, Users.Read, Users.ModifyUsers)
  • (optional) Account management: View full profile (corresponds to the WebAPI permissions Account.Read, Account.ReadEmail. Used to skip possible deactivation of API token owner.)
  • (optional) Group management: View, create, delete, edit and share groups
  • (optional) User Group management: View, create, delete and edit groups. Required when user group synchronization is enabled.

• Parameter ActiveDirectoryGroups:

  The LDAP identifiers (without the leading LDAP:// protocol scheme) of the AD groups used for the synchronization.

• Parameter UserLanguage:

  The two-letter language identifier used as default language for newly created TeamViewer users. For example it is used to localize the "User Welcome" email.

• Parameter UseDefaultPassword:

  If set to true TeamViewer users will be created with the initial password specified by the DefaultPassword parameter. This parameter cannot be used in conjunction with the UseSsoCustomerId or UseGeneratedPassword parameters.

• Parameter DefaultPassword:

  The initial password used for newly created TeamViewer users.

• Parameter UseSsoCustomerId:

  If set to true TeamViewer users will be created having Single Sign-On (SSO) already activated. Therefore a customer ID needs to be specified in the SsoCustomerId parameter. This parameter cannot be used in conjunction with the UseDefaultPassword or UseGeneratedPassword parameters.

• Parameter SsoCustomerId:

  The TeamViewer Single Sign-On (SSO) customer identifier.

• Parameter UseGeneratedPassword:

  If set to true TeamViewer users will be created with a generated password. The users will receive an email for resetting their password.

• Parameter TestRun:

  If set to true the synchronization will not modify any TeamViewer user resources but instead only log the actions that would have been executed.

• Parameter DeactivateUsers:

  If set to true TeamViewer users that are not member of the selected AD group will be disabled.

• Parameter RecursiveGroups:

  If set to true users of nested AD groups will be included.

• Parameter UseSecondaryEmails:

  If set to true the secondary email addresses configured for an AD user will also be taken into account when trying to map to a TeamViewer user.

• Parameter EnableUserGroupsSync:

  If set to true the script attempts to synchronize the given AD groups and their respective users with the TeamViewer user groups. Those user groups can then be used to configure TeamViewer functionality, for example: Single Sign-On ownership or exclusions. The user groups synchronization step runs after the user sync. This option requires the API token to have additional permissions, see point ApiToken above.

The scheduled task will be created with the specified interval as:

\TeamViewer\TeamViewer AD Connector

Output of the scheduled task is redirected to the configured log file location.

The actual synchronization is done by the Invoke-Sync.ps1 script in the TeamViewerADConnector directory using the following logic:

• Users of the configured AD group that are not yet part of the configured TeamViewer company (identified by the API token) will be created with the specified initial password.
• Users of the configured AD group that are already part of the configured TeamViewer company will be activated and/or updated if the name of the user has been changed or the TeamViewer user is deactivated.
• If configured, users of the TeamViewer company that are not present in the configured AD group will be deactivated.

Identification of users is done based on the email addresses. If configured, the secondary email addresses of AD users are also taken into account for the mapping between AD users and TeamViewer users.

Copyright (c) 2018-2023 TeamViewer Germany GmbH

See file LICENSE.