TeamViewer QuickSupport is a small utility that can be launched without administrator rights or installation and used to allow someone with TeamViewer installed on their computer to provide remote support instantly. TeamViewer QuickSupport can be customized using modules that contain your own logo and text, which makes it perfect for businesses and companies that would like to give personal notes to their customers. The customization is done using the TeamViewer Management Console.
Whereas both TeamViewer QuickSupport and TeamViewer QuickJoin are meant as one-off solutions, TeamViewer Host is used for around-the-clock remote monitoring and server maintenance. It can be installed on an unlimited number of computers and devices and customized using the TeamViewer Management Console.
To make sure your data and your privacy are safe, we at FileHorse check all software installation files each time a new one is uploaded to our servers or linked to remote server. Based on the checks we perform the software is categorized as follows:
There are some reports that this software is potentially malicious or may install other unwanted bundled software. These could be false positives and our users are advised to be careful while installing this software.
It's very likely that this is software is malicious or contains unwanted bundled software. Users are advised look for alternatives for this software or be extremely careful when installing and using this software.
anchor apple generic and identifier "com.teamviewer.TeamViewerQS" and (certificate leaf[field.1.2.840.1136126.96.36.199.9] /* exists */ or certificate 1[field.1.2.840.1136188.8.131.52.6] /* exists */ and certificate leaf[field.1.2.840.1136184.108.40.206.13] /* exists */ and certificate leaf[subject.OU] = H7UGFBUGV6)
anchor apple generic and identifier "com.teamviewer.TeamViewer" and (certificate leaf[field.1.2.840.1136220.127.116.11.9] /* exists */ or certificate 1[field.1.2.840.113618.104.22.168.6] /* exists */ and certificate leaf[field.1.2.840.113622.214.171.124.13] /* exists */ and certificate leaf[subject.OU] = H7UGFBUGV6)
anchor apple generic and identifier "com.teamviewer.TeamViewerHost" and (certificate leaf[field.1.2.840.1136126.96.36.199.9] /* exists */ or certificate 1[field.1.2.840.1136188.8.131.52.6] /* exists */ and certificate leaf[field.1.2.840.1136184.108.40.206.13] /* exists */ and certificate leaf[subject.OU] = H7UGFBUGV6)
Jamf recommends the client Mac download the TeamViewer QuickSupport application during the remote support session. This requires no prior software installation. However, you can pre-install either the TeamViewer or TeamViewer Host application using the following procedure.
I'm wondering if it is possible to install TeamViewer using some terminal command. I know that I can install it using homebrew, but is not the result that I want since a lot of other, probably (for the user) useless packages, will be installed on their systems.
However, if you use autopkg you can just add my repo and create an override of the TeamViewerHostCustom download, pkg, or munki recipe. This will allow you to download the TeamViewer Host module for the desired major version. Despite the config ID being written to the filename, in my testing with munki this unfortunately does not cause this ID to be written as an attribute to the TeamViewer Host app as part of the installation.
If you happen to manage several different host module configurations in your or multiple organizations, you might consider creating different pkginfo files referencing your installer which uses the above postinstall script to write the desired extended attribute.
In Windows you can choose to just run the executable without installing it but I don't see this option in the Mac installer.You can run the TV Quicksupport module on the host on Mac without installing but I am asking about the controlling side.Before I have used TV via a web browser but this option appears to have been deprecated now.Thank you.
So, before installing TeamViewer, manually or remotely via Jamf Pro, and even if you plan to use TeamViewerQS, make sure to push a profile with the corresponding PPPC payload to your endpoints!
Depending whether or not the full TeamViewer (Host) is installed, the end user can launch it or choose to download the QS version. Once loaded, the following popup will appear when the admin requests to connect:
TeamViewer is a remote access application, meaning it allows you to connect to and manipulate another device, so long as you know the log-in information provided when TeamViewer is installed on that device. Simply put, if you install it on your desktop and your phone, you can access your desktop from your phone with the ID and password you're given when you set it up.
If you require the ability to remotely access a device without that device having to approve your request, we've already detailed setting up unattended access in TeamViewer, along with an in-depth installation guide for Windows. We've also discussed installing TeamViewer on Linux, as the different distributions make installation slightly different.
Connecting to your Android phone from your PC will allow you to uninstall apps, kill processes, transfer files, copy to the clipboard, and take screenshots. You'll have access to the device's settings and everything that entails, including the ability to change Wi-Fi settings, update the OS, and view important device information.
The viewer must match the Take Control engine installed on the Take Control host. For example, if the device requiring assistance(host) uses the Take Control (N-able) engine, the device providing assistance (viewer) must use the Take Control (N-able) engine.
When you provide support to a mixed environment of Take Control (TeamViewer) and Take Control (N-able) installations, you must have both Take Control Viewer versions installed on the devices providing assistance.
Take Control (TeamViewer) and TeamViewer cannot co-exist on the same device. If a TeamViewer host is detected during the installation of Take Control (TeamViewer), there is the option to Replace Existing TeamViewer Installation with Take Control in the device's Summary tab.
Finally, by using the same TeamViewer account on the host and guest machines, you can more easily connect to your Mac and other remote computers by name. From TeamViewer on your Windows PC, click the option for Computers & Contacts. From here, you can now see each connected computer and double-click the one to which you want to connect (Figure I).
The first thing we did was download the latest TeamViewer Host version for Mac from TeamViewer's website and imported it into Munki by using the "munkiimport" command. Once this was completed we performed an install by adding it to a developer manifest to test the installation which was successful. Once installed we then configured TeamViewer just the way we liked it such as the password, updates, etc. Once completed, we determined that TeamViewer stores all of its settings in the following file:
Munki allows for you to perform pre-install, post-install and post-uninstall scripts. This meant that these settings could be written to the PLIST file during the install with the "defaults write" command. The passwords in TeamViewer are stored in the following:
From this information we now have the the correct information to insert the passwords as they are data fields and data fields require hexadecimal in Mac OS X. We can now build the Munki package to install TeamViewer with our settings.
After performing vigorous trial and error I was able to determine in order for the passwords to be inserted into TeamViewer via an installation script they must be there BEFORE the install takes place. This means that we will take advantage of Munki's preinstall_script. With the pre_install script I was able to apply the passwords and access the systems after the install was completed. We still however were lacking the customization to really make this product like the Windows version.
The last thing we needed to do was change the logo in the host version, change the title, and the text to match the Windows side as well as disable the ability to close the host client. The following files require modification in order to achieve this:
To replace these files I created a DMG file called TeamViewerCOE.dmg which is The College of Education's own branding for TeamViewer that contained modified versions of these files. Once the DMG was created I created a Munki pkginfo that would allow me to copy these files into TeamViewer after the install as this DMG was marked as an Update for TeamViewer which means that my customizations will install after TeamViewer so if an update for TeamViewer Host is added to Munki, then my customizations will still be applied to the new version. Changing the logo is pretty self explanatory however here are the pieces you will need to edit in the other files:
Once these changes have been made you can package the modified files in a DMG and have it update every time the TeamViewer Host is installed which will add your branding and customization to the product performing a real deployable version. The last piece however that I have yet been able to figure out with the product itself is how to report the IDs back to your Corporate License. For the time being PSU has IBM Endpoint Manager which I have worked with the Windows System Administrator to create an Analyses job that will look at the plist file after TeamViewer is launched on the remote system for the ID as the ID is placed in the PLIST file. Since we don't want personal TeamViewer IDs, we also added in the install script a PLIST entry that says it was installed by EDUC which we also look for when scanning for the IDs. This portion is still manual but may not be for long. I have also had many conversations with TeamViewer and they have indicated that the next version (9) may possibly have a deployable version for Mac so you would not need to perform any of this. If you have any questions please feel free to let me know. Here are my final PKGInfo files for both the TeamViewer Host install and the additional settings. You will see under the uninstall_script that I remove our customized PLIST file which I highly recommend. 2b1af7f3a8