Search
Fasttrack Global

Unattended installation of TeamViewer

This page shows how to deploy the free or licensed version of TeamViewer (Full or Host) by repackaging it into Group Policy or SCCM deployable Windows Installer (MSI) format, without using unreliable snapshots. Repacking with FastTrack Automation Studio also adds a new and exciting feature to Group Policy deployments: You can add launch conditions to prevent installation on some computers in the Group Policy OU or container.

Whether you already have TeamViewer deployed to some computers or not, you can use FastTrack to keep track of TeamViewer IDs on your network. Refer to the bottom for more.

Download FastTrack Automation Studio
Informa GLS Telenor Maersk Goodyear Kawasaki Disney Department of Commerce NOAA

Starting the repackaging wizard

The first step is to start the EXE-to-MSI wizard (also known as Deployment Package Wizard). If you started in App Factory mode, this is one of the main icons. If you are in Scripting Mode, switch to App Factory mode in the top menu. If you are using the MSI edition, you will see an EXE-to-MSI icon in the top menu.
App Factory EXE to MSI Generator
On the second page of the wizard, the type of output package must be selected. Here we must select TeamViewer Full or TeamViewer Host in the list. There are templates for TeamViewer, Avast, AVG, MalwareBytes and Microsoft Security Essentials, but you can repack any type of installation using the top two options, which is explained further down this page. The templates options are basically just expanded versions of the generic EXE-to-MSI, which is the first option in the list.

The current setup file for the full version (Viewer and Host) must be downloaded from the front page of www.teamviewer.com and placed in the working directory that you specify as the setup file directory. The wizard will look for a file starting with "TeamViewer_Setup" in this directory, as the setup file is by default named this and may be appended by a language string.

If you need to repackage the Host-only version, you can download the setup file here. For host-only, the wizard will look for a file starting with "TeamViewer_Host" in the working directory.

TeamViewer MSI package

Including license key, password and other settings (optional)

You can include an optional TeamViewer settings registry file. If you do not do this, you will be using the free version. To create a reg file with settings and/or a license key, open TeamViewer on a reference computer and select Options in the Extras menu. Under Advanced, select "Export options to a *.reg file"

TeamViewer settings export

If you need to deploy a TeamViewer license, make sure to check "Export license key", as shown below. Once the options *.reg file is saved to disk, close TeamViewer and go back to the wizard and enter the newly exported file in the "Settings file (optional)" textbox.

TeamViewer settings export

If you are repackaging the host-only version, it works the same way, except that there are fewer options. The options windows is opened by clicking the gear icon, as shown below.

TeamViewer settings export

Launch conditions

Clicking next in the wizard will show launch conditions, which allows you to not install TeamViewer under certain conditions. This means that you can deploy the package to an entire OU or container in your Active Directory with Group Policies and avoid having it install on for example servers and virtual machines.

TeamViewer MSI package

The first page lets you block on hardware and operating system. The second launch condition page lets you block based on Active Directory information:

Active Directory launch conditions in an MSI file

To understand how launch conditions can actually work with Group Policies, we have to look at what the wizard does. There are generally four scenarios with FastTrack Automation Studio to create MSI files, as shown below. What we are doing here is using the option to the left. The MSI that wraps around the TeamViewer setup file is always installed, but it does not do anything other than register as an program in the Windows programs list, if it hits a launch condition blocking. This means that from the point view of Group Policies or SCCM, the installation is always successful and will therefore never try to resend the MSI file. This is why there was also an option on the first page to use a setup MSI file inside the controller MSI, because then you can let the controller MSI always install, but only install the setup MSI on certain conditions, essentially allowing you to deploy all your software to all computers using Group Policies.

MSI types

Clicking next in the wizard after launch conditions will ask you for name of the output MSI file. This is the controller MSI file that contains the TeamViewer installer. On success, the complete page is shown. Notice how it displays a script that you can open in Scripting Mode and edit. Essentially the wizard does nothing more than compiling this script and your TeamViewer setup file an MSI file. If you are not happy with the installation script or your need to expand it with, say licensing information, you can just open and edit the template script in Scripting Mode and save it to the same folder as the TeamViewer setup file. You are now using the third box in the drawing above, where you build your own custom MSI package. This is explain in a more detail at the bottom. Note that if you used launch conditions, you will notice that conditions were inserted at the top of the script, which is why it is a good idea to let the wizard create a template script, in case you need to extend or modify the functionality.

TeamViewer MSI package

That's it! You now have an MSI file that will install TeamViewer unattended, which you can now assign as a software installation to Group Policy. As a general advice for Group Policy MSI deployment, you should check the uninstall option, to make sure that your MSI file will uninstall on all machines, if you remove the GPO MSI package.

If you are using a trial version of FastTrack Automation Studio, the package will only deploy to 5 computers, as this is what the trial edition allows - the rest will behave similar to launch conditions, where the setup exe is not executed. You can get a license from $259 here at our store. You can use the MSI edition, if you only need Teamviewer deployment. If you want to use other FastTrack Automation Studio features also, the Enterprise edition is recommended. Similar articles exist for Avast, MalwareBytes, AVG and Microsoft Security Essentials.

Expanding the script

If you need to modify or expand the script generated by the wizard, you must check the "Create a new script using the above template" on the last page of the wizard and save it to the same folder as your TeamViewer setup exe file. Once you have modified the script to your needs, you must use the "Compile to MSI" option in the top menu.

Creating MSI file from project

The MSI generation wizard will open, as shown below. Please make sure that:
  • You check "Include additional files from my project folder inside the MSI file".
  • You check "Defer installation".
  • When you get to the page to select additional files inside the MSI file, make sure to check your TeamViewer setup exe file.
  • If you exported TeamViewer options, make sure you include the two reg files that the wizard created in your setup folder.
Malwarebytes MSI installation properties

Keeping track of TeamViewer IDs using FastTrack Inventory

Once you have deployed TeamViewer to a number of computers, you need to know which computer has which TeamViewer ID. You can collect TeamViewer IDs using FastTrack Inventory, where the TeamViewer ID is a part of the standard inventory collection. If we go back to the wizard, there was a checkmark named SkyBox (SkyBox is the cloud-based version):

TeamViewer ID Inventory

If you click this, inventory data is collected after installation, including the TeamViewer ID. Once you take inventory, you can simply click "Inventory" in the App Factory and select "Access My Cloud Inventory" in the drop-down. You are now taken to your account at SkyBox, where you can look up your computers. On the detail page of a computer, you will find the TeamViewer ID, as shown below. If you need to do on-site service for clients and/or servers, you can print the QR barcode and attach to the server. Then you can scan the barcode with a cell phone and get the inventory page for that server. For a description of taking inventory by other means than an MSI package, refer to the FastTrack Inventory page.

TeamViewer Inventory

Keeping track of TeamViewer IDs using a central XML file

Another approach is to use a central XML file, which gives you the advantage to be able to make a small utility for yourself that will automatically convert an internal computer name to the TeamViewer ID and start a session. The key to do it is to use the TeamViewerID function in FastTrack, which returns the TeamViewer ID on the local machine. One way to do it is to expand the MSI package script (see further up) and simply log it to a central file on install. This line added to the script after install will write the TeamViewer to one central XML file:

WriteXMLValue \\AcmeServer\data$\TeamViewerIDs.xml,Clients/[ComputerName],[TeamViewerID]

The XML file is assumed to be located on a share named data$ on a server named AcmeServer and the WriteXMLValue command will overwrite any existing value that might exist. A better approach, however, is to build a standard TeamViewer package and then collect TeamViewer IDs in a FastTrack Logon Script. You can just include the above script line anywhere in the logon script. This will give you the advantage of getting all TeamViewer IDs for all computers on the network, not only the ones repackaged by FastTrack.

Converting computer name to IDs automatically

Once you have a central XML file in place, you can write a small converter script for yourself. All we have to do is to look up a computer in the XML file and use that to start TeamViewer. This simple script asks you for a computer name and starts TeamViewer using the ID from the XML file and it assumes that the remote password for all computers is "1234". You can leave out the last parameter with the password to have TeamViewer ask for password instead.

Set Computer = [Input Computer name?]

LaunchTeamViewer [XMLValue \\AcmeServer\data$\TeamViewerIDs.xml,Clients/[Var Computer]],[EncryptPassword 1234]

TeamViewer UI

Rating: 8 out of 10

"Faster than the rest"

"We found the FastTrack syntax to be more transparent and easier to learn than Microsoft's PowerShell – the editor in particular provided good support in this regard. Scripting mode offers a large number of options from the command set through to simple output of graphical elements, which cannot be realized at all with PowerShell or other solutions or only with a significantly greater level of effort."

"Anyone wanting to tackle the many hurdles in everyday admin and especially anyone for whom logon scripts and client automation is a priority will benefit from the variety of functions offered by FastTrack."

Rating: 5 out of 5

"Use this as a replacement for VBScript and PowerShell"

"It's easy to include attractive GUI elements in FastTrack scripts, beyond the basic dialog boxes and text input that VBScript offers ... Another powerful feature is the ability to distribute scripts as Windows Installer (.msi) or standard .exe files. Although interesting in its own right, this ability results in a much more intriguing capability: to repackage -- or wrap -- software installers as .msi files without using snapshots. If you've ever created an .msi installer file from before-and-after system snapshots, for use with a software distribution system such as Group Policy or System Center Configuration Manager (SCCM), then you know how hit-and-miss the results can be."
Review in English Review in German
Read full review
Outlook Signature Generation

Outlook Signatures

Visually build mass-deployable MSI format Outlook signatures. More
Zero Touch Thin PC

Tired of Desktop Authority?

Use FastTrack instead for cheaper desktop preparation. More
Graphical Logon Scripts EXE to MSI

Graphical Logon Scripts

Build graphical logon scripts for advanced desktop preparation. More

EXE to MSI

Deploy TeamViewer, Malwarebytes, Avast, AVG with GPO/SCCM. More
FastTrack Inventory

Inventory in the Cloud

Save on licenses using a cloud-based inventory. More
Laptop Backups

Laptop and PST Backups

Utilize the world's fastest synchronizer for backups. More

Deploy all your software with Group Policies!
FastTrack enables conditional deployments - check this for more

Download FastTrack Automation Studio Buy FastTrack Automation Studio
Informa GLS Telenor Maersk Goodyear Kawasaki Disney Department of Commerce NOAA