How to deploy TeamViewer Software using SCCM
In this post we will see how to deploy TeamViewer software using SCCM. TeamViewer is an app that allows you to remotely connect to multiple workstations. There are many apps that allow remote control of different systems, but TeamViewer is set up to be extremely accessible, while also being powerful. Whether managing an IT department or just helping your neighbor down the street fix their computer, it is an application worth installing on your system.
TeamViewer MSI is an alternative installation package for the full version of TeamViewer or for TeamViewer Host. TeamViewer MSI is used to deploy TeamViewer via Group Policy (GPO) in an Active Directory domain. TeamViewer MSI is only available with a Corporate license.
Related Posts :-
- How To Deploy OBS Studio Using SCCM
- How To Deploy Adobe Air Silently Using SCCM
- How To Deploy WinRAR Including License Using SCCM
- How to deploy VLC media player using SCCM
- Deploy Microsoft Visio 2013 Viewer Using SCCM
How to deploy TeamViewer Software using SCCM
Download the TeamViewer software. Double click the software and do not click install or next. When you run the software, another executable file and a ini file is extracted. This setup file can be found under current user account appdatalocaltempTeamViewer folder. Copy the TeamViewer_.exe to the folder on the SCCM server. We will use this executable file to install TeamViewer.
Launch the Configuration Manager console, click Software Library, under Application Management right click Applications and click Create Application. Choose Manually specify the application information and click Next.
On the General Information page, specify some information about the application such as Name, Publisher etc. Click Next.
You can specify more information about the TeamViewer application here, the information specified here will be seen by user in the Application Catalog. Click Next.
We will configure the Deployment Type for TeamViewer software. Click on Add. In the General page, choose Type as Script Installer click Manually specify the deployment type information. Click Next
Specify some information about this deployment type and click Next.
For the Content Location, provide the path where the TeamViewer setup file is present. In my case I have copied the setup file to a folder named Team Viewer on SCCM server. The next step is to specify install and uninstall command.
Specify the Installation Program as “TeamViewer_.exe” /S
Specify the Uninstall Program as “%ProgramFiles(x86)%Teamvieweruninstall” /S
Note – In the above commands use /S (uppercase S), lowercase ‘s’ may not work correctly.
Click Next
Detection Method – Detection methods allow the administrator to check if application is already installed. It can also prevent an install of an application if it conflicts with another application that is already installed. In this step you configure the rules to detect whether the application already exists on the client machine. Click Configure rules to detect the presence of this deployment type and click on Add Clause.
On the Detection Rule window, choose Setting Type as File System. Under Specify the file or folder to detect the app, set the following
Type – File
Path – %ProgramFiles(x86)%TeamViewer
File or Folder name – TeamViewer.exe
Click The file system setting must satisfy the following rule to indicate the presence of this application.
Set Property = Version
Operator = Equals
Value = 11.0.63017.0 (This value may vary with the version of TeamViewer that you download. You can get the Value by checking the properties of Teamviewer app).
Click OK and then Next.
Selection the Installation behavior as Install for system if resource is device else install for user, Logon requirement as Whether or not a user is logged on and Installation program visibility to Hidden. Click Next.
For rest of the steps click Next and finally click Close.
Right click the TeamViewer application and click on Distribute Content. After you distribute the application to DP, right click on the TeamViewer software and click on Deploy. Choose the Collection where this application is to be deployed. After few minutes the TeamViewer software can be seen in the Software Center. Select the app and click on Install. The app is downloaded from the DP and installed.
If you want to know what’s going in the background during the software installation, open the AppEnforce.log file on the client computer using CMTrace tool. If the app fails to install you check this file for troubleshooting purpose.
Hi Sir,
Getting exit code 2 stating, the system can’t find the file specified.
In testing environment, it has worked fine but while deploying into pilot, I’m getting this error.
To avoid i have used registry as well and have made many changes with detection method but still same error.
Hi Prajwal. I am following your blog and even this blog to deploy team viewer 13. however deployment status just shows as ‘Already Compliant’ so it looks like it is just detecting but not installing it. my requirement is to install this on all system even it has older version. do you prefer other detection method so that it doesn’t stick to specific version but install it on client system.
Hi Prajwal. I am regularly following up your blog and I am sccm admin too. I followed this and did deployment. however status still shows as ‘Already Compliant’ but it seems it is just detecting but not installing on client system. Is thee any other way you suggest for detection. my requirement is to install TV 13 on all system/user even they have any previous version. I selected as ‘Required’.
you need to manage them by policy from the teamviewer console which also means you need to deploy them with an account assignment
How teamviewer uninstall using sccm 2012?
Isn’t the uninstall command working when you have specified it while configuring app ?.
No, How can remove the teamviewer programs installed on client computers using sccm;?
there seems to be an issue with timing, the app uninstalls but reports a failed status. Appenforce shows that after you click uninstall, it still is able to detect the application, so the detection happens too soon…Then if you click retry it reports OK
So that means the detection method is not working correctly. I didn’t face this issue when i tested the uninstalls. Did you add any other detection methods and test ?.
I’m just having this issue too. Apparently it is because the uninstaller forks another process and quits, so when SCCM do its check, the file is still there; but gets deleted seconds later by this new process. I have worked around it by changing the uninstall program to a .cmd file that runs the uninstall command and then waits for 10 seconds (with a ping), and that worked. Not a clean solution but that will do for a quick fix…
i have same trouble too
Hi Prajwal,
how can i handle the many patches and updates that come with teamviewer? I deployed it as described but when the users update their installations, softwarecenter tries to reinstall the old version and breaks with an error that is visible to the users….
thanks,
Markus
I believe that can done using a script.
Hey mate, just wondering if there is a way to roll out team viewer with pre-configured settings together with account assignment via Config Manager?