Create a Managed Group If you have not already, Create a Managed Group We have a guide on this here. Make sure you select a policy under “Assign TeamViewer Policies” if you want a policy on the devices. Managers will be able to see the group and devices contained within it. You can also set their access level and i f they can connect to the device unattended (Easy Access) Create an “Assignment” Assignments are a series of rules for devices to be added to your account. This is used in Managed Devices V2. You can create this here - Give it a name - Select “Managers” (People this will be shared with) - Select the “Managed Groups” (Groups the device will appear in when added) - Policy Select the group you want to inherit the policy from. Create a Custom Host For this method, your Custom Host will only handle the customisations of the interface. When Mass Deploying the assignment, policies and other settings are assigned by your assignment script after inst all. Creating your Host Head to “Design and Deploy” and click the + button and add a new Host. Tip: Custom branding is dynamic. If you deploy the software and then change the branding or colour scheme later, the changes will take effect on your endpoints on the next restart of the software. C ustom settings f or Mass Deployment ( MDv 2) Use Managed Group Assignment – This should be UNchecked for mass deployment Customisations - The example on the left will be what your user sees. You can change colours, logos and test here. Automatically add computers to a group in your contacts list – Leave unchecked (Handled by Assignment script) Allow Customer to Initiate a Service Case (Optional) – This will place a button on the host allowing users to create a support case within Team Viewer. If you want them to contact another way, unchecked this box. More information on service cases can be found here Disclaimer (Optional) – This shows up as a prompt when you make an “attended” connection to a device, the user accepts it before you connect. Permanent Link - NOT GENERALLY USED WITH THIS METHOD. Download MSI - This is only visible to Corporate users and above. You can download the MSI package here. Note: The package has no customisation when download. The instructions must be followed and the package is deployed with a script to get customisations. Configuration ID - This is used during mass deployment. This code is used to download these settings and customisations from the server and applies them to the MSI package. Mass Deploying the Software (Managed Devices V2) You can mass deploy the software using common deployment methods. Creating your deployment script This script controls the behaviour of your install and also allows it to pop up in your list automatically witho ut confirmation. The Deployment with the Configuration ID and Settings (optional) is done first. After this, you assign the device to your account complete with access rules using your assignment token. Install CUSTOMCONFIGID - set the logo and look of the host (the Config ID is created when you create your custom module) SETTINGSFILE (Optional) - imports your reg file including password. You must supply a path to your saved settings file. (More info below) CM D Example msiexec /i "X: \ TeamViewer_Host.msi" /qn CUSTOMCONFIGID = <Config ID> SETTINGSFILE=" PATH \ TO \ MSI \ TeamViewer_Host.msi " Powershell Example Start - Process msiexec.exe - Wait '/i " PATH \ TO \ MSI \ TeamViewer_Host.msi " /qn CUSTOMCONFIGID = <Config ID> ' Assignment More information here Copy your assignment token And use this in your script to assign. Examples: CM D Example "C: \ Program Files (x86) \ TeamViewer \ TeamViewer.exe" assignment -- id <assignment_token> Powershell Example Start - Process - Wait - Filepath "C: \ Program Files (x86) \ TeamViewer \ TeamViewer.exe" - ArgumentLi st "assign ment -- id <assignment_token> " Note: You should be able to provide both the install and assignment command at once as the MSI install will generally complete before the next command runs, but this depends on your platform.