TeamViewer: macOS Client Setup
What
FileWave's TeamViewer integration requires endpoint prerequisites on each supported platform. In future versions, we may embed someMajority of these prerequisites,have been left untouched, but atmay thisbe time,altered, we erred on the side of letting you control the elements. So,allowing slightly more work (if desired) but much greater control.
When/Why
TeamViewer is used to remotely control your clients.clients, You can use TeamViewer when you needproviding access to a device for troubleshooting or assisting a user. TeamViewer for macOS differs from other OSs becausesince it requires a few privacy permissions before allowing TeamViewer to be installed.
How
We'll need to meet prerequisitesPrerequisites for macOS client devices must be met in order for TeamViewer to work seamlessly.
We'll need the:seamlessly:
-
Server and Clients have to be FileWave 14.7+
-
General TeamViewer Prerequisites are met, ensuring that clients are set to allow remote control
-
TCC Profile for TeamViewer Host - Accessibility and Full Admin Access
The below describes installing the TeamViewer Host application. The full TeamViewer application is only necessary for computers wanting to remote into other computers. The Host application is only allowed to accept connections and not initiate them. You can use both, but wethem; highly recommend the Host application.recommended.
(During an attempt to prompt a device for control, users will be prompted to either install or launch a local copy of Teamviewer. Only the TeamViewer Host version can be launched if pre-installed.)
FileWave Client (14.7+)
Remember to always use the client updater Fileset to update FileWave clients. Do NOT push the FileWave client PKG to upgrade macOS clients.
The most recent FileWave client is always included on the FileWave download pages: Downloads
TCC Profile for TeamViewer Host - Accessibility, Screen RecordingAccessibility and Full Admin Access
ScreenBoth Sharing is a service deemed by Apple as user privacy. Hence, users must locallyprofiles enable Screen Sharing on macOS.The profile enables 2 of the 3 permissions TeamViewer Host requires. The 3rd, Screen Recording, is a privacy setting that can not be allowed by anyone other than a local user. Standard Users do not have permissions to allow Screen Recording by default. This option to allow a non-Admin to enable Screen Sharing is enabledavailable in one of the provided Profile.Profiles.
ProfileScreen DownloadSharing (macOSis 11+):a
TeamViewerHost15AllowUser.mobileconfig
service deemed by Apple as user privacy. Hence, users must locally enable Screen Sharing on macOS.
TheOnce Profileallowed, if left enabled, subsequent TeamViewer sessions to that device my be actioned, without user prompting.
Both Profiles have the following settings:
However, one of them allows Screen Recording to be enabled by a non-Admin user:
Each profile contains two payloads: Privacy Settings & Custom Settings
Privacy Settings
The following Security & Privacy settings are allowed/enabled in the provided Profile.
Permissions to allow TeamViewer access rights,rights.
TCC Profile for TeamViewer Host: TCC Profile for TeamViewer Host with Standard |
Custom Settings
Example additional configuration.
The included example settings include:
- Security_Adminrights -- Lock TeamViewer options for Administrator rights
- Security_PasswordStrength -- Password disabled, ensuring access is only via FileWave
TeamViewer Host Fileset
The included Filesets are examples which utilizeutilise a settings file set to installinstal the software silently.
Choose an embedded TeamViewer FilesetFileset: (note
Note that
TeamViewer Host Instal macOS 15.57.3.fileset.zip
|
ConsiderLatest downloadingversion can be downloaded from TeamViewer directly, however, the latestpublic versiondownloadable DMG has an application that instals the software and does not allow for the configuration presented at the time of TeamViewerinstallation; Hostupgrades PKGshould fromoccur theautomatically TeamVieweras website,indicated ifbelow
- macOS TeamViewer Host
After
Fileset Contents:
Installer and Installer Options:
The choices.xml file is configured to instal the .pkg silently. However, the user will be prompted with notifications, since Apple allow users to choose if apps are allowed to control the screen or not.
Requirement Script:
Where software is already installed and services are active, Privacy Settings Profiles installed subsequently require the service of that software to be restarted. This Fileset example includes a Requirement Script that checks for profile installation before activating TeamViewer, preventing the need to restart the TeamViewer Host service.
#!/bin/zsh
found_profile="ml1063.local.5a57bcb9-7293-4cba-a20b-126eb2660b25.Configuration.5a57bcb9-7293-4cba-a20b-126eb2660b25"
while [ $# -gt 0 ]
do
found_profile=$(profiles list all | awk -v search=$1 '$0 ~ search {print $NF}')
if [ ! -z $found_profile ]
then
echo "Found installed profile: $found_profile"
exit 0
else
echo "Did not find $1"
fi
shift
done
exit 1
The 'check_tv_profile.sh' script is designed to recognizerecognise one of the two provided ProfileProfiles and, once installed, allow activation of the Fileset. If Profiles with a different Profile ID are used instead of the onethose supplied, the script settings will require alteration.
- Double click the Fileset
- Select the 'check_tv_profile.sh' (located in a numbered subfolder in /var/scripts/)
SelectChoose'EditGetText'Info > Executable viewReplace
The Launch Arguments show the 'found_profile'two variablepossible withPayload IDs. Add in the IDcorrect of yourFileset Profile (ID canif not using the provided ones.
The two profiles may be founduploaded by double-clicking on the profile.simultaneously. The IDFileset Requirement Script is atable theto bottomidentify ifeither the info window)
Activation Script:
The script in this case is installing the PKG. Note the script allows the specifying of the 'choices.xml' file when ran.
#!/bin/zsh
installer -applyChoiceChangesXML /usr/local/etc/TeamViewer/choices.xml -pkg "/usr/local/etc/TeamViewer/Install TeamViewerHost.pkg" -target /
exit 0
Post-Uninstallation Script:
theThe 'mac_teamviewer_uninstaller.sh' script uninstalls TeamViewer if an association or deployment no longer exists.
Updates
The software should auto update to latest version. The PKG is not publicly accessible. For this reason, FileWave will aim to update the provided Fileset every so often, to include the latest version, but if not yet updated to the latest version, the client should auto update the installed version where the Fileset is still using an older version.
Don't forget to upgrade the full TeamViewer version on the Admin device.