Search
Fasttrack processor

Unattended installation of TeamViewer

This page presents a solution to deploying TeamViewer unattended by repackaging it into Windows Install (MSI) format. The problem with Group Policy deployment is that the installation of TeamViewer is not in MSI format, which is a requirement. This page will go through how to convert the installation to MSI format without using unreliable snapshots. Read on below for a step-by-step repackaging guide.

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.

A similar article for MalwareBytes is available here and here for one on Avast.

Download FastTrack Automation Studio
GLS Telenor Informa Maersk Goodyear Kawasaki Disney Department of Commerce AJG NOAA
Note that this page demonstrates how to deploy the free version of TeamViewer through Group Policies. This version is only allowed for personal use. If you use TeamViewer for non-personal use, you must activate a license key on each computer or expand the MSI package to include licensing information.

The first step is to start the EXE-to-MSI wizard (also known as the 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 in the list. There are templates for TeamViewer, Avast and MalwareBytes, but you can repack any type of installation using the top two options, which is explained further down this page. These three templates are basically just expanded versions of the generic EXE-to-MSI, which is the first option in the list.

The current setup file must be downloaded from www.teamviewer.com and place it 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.

TeamViewer MSI package

Clicking next will show launch condition options. This allows you to not install TeamViewer on certain computers, such as servers. 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
Avast 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.

Note that 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 $399 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 are available. Click here for an article on installing MalwareBytes unattended and here for one on Avast.

Install software through GPO
Setting uninstall option for software through GPO
FastTrack Automation Studio MSI Edition
Automation Studio - MSI Edition
Automated TeamViewer deployment
$399
Buy now

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. Make sure that you check "Include additional files from my project folder inside the MSI file". When you get to the page to select additional files inside the MSI file, make sure to check you TeamViewer setup exe file.

Malwarebytes MSI installation properties
Outlook Signature Generation

Outlook Signatures and Profiles

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

Tired of Desktop Authority?

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

Graphical Logon Scripts

Build graphical logon scripts with your logo for advanced desktop preparation. More

EXE to MSI

Mass-deploy TeamViewer, Malwarebytes, Avast and others with GPO or SCCM. More
FastTrack Inventory

Inventory in the Cloud

Save on unnecessary licenses. Set up a cloud-based inventory. More
Laptop Backups

Laptop and PST Backups

Utilize the world's fastest synchronizer for replication and laptop backups. More

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

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