FileWave's TeamViewer integration requires endpoint pre-requisites on each supported platform.  In future versions, we may embed some of these pre-requisites, but at this time we erred on the side of letting you control the elements.  So, slightly more work, but much greater control.


We'll need to meet pre-requisites for macOS client devices for TeamViewer to work seamlessly.  We'll need the:

  • FileWave server to be upgraded to at least 14.7 (14.6 is permitted but was a technical preview)

  • FileWave client to be upgraded to at least 14.7 (14.6 is permitted but was a technical preview and unattended access won't be present)

  • TeamViewer full client installed where you run FileWave Admin or WebAdmin

  • And we'll most likely want to pre-deploy the TeamViewer or TeamViewer Host application as well. Most customers will want to use TeamViewer Host.

  • Finally, we'll want to deploy a profile to pre-accept that TeamViewer can interact with the device screen (similar to Observe Client and other screen viewing tools).

When thinking about if you want to use TeamViewer or TeamViewer Host the most important thing is if you want to remove the possibility that devices could initiate a remote session to another device. For a school, they might not want students to be able to create remote sessions. TeamViewer Host is an application that can only receive connections to be controlled, but not control another device. 

During an attempt to control a device, 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

The most recent FileWave client is always included on the FileWave download pages, which you can find here: https://fwkb.atlassian.net/wiki/spaces/DOW/overview

Remember to always use the client updater Fileset to update your clients.  Do NOT push the FileWave client PKG to upgrade macOS clients.


Consider making a Fileset Group.  The group will contain the following two Filesets and is designed to set up TeamViewer Host.

Profile - TCC Fileset for TeamViewer Host allowing Privacy Access rights for Accessibility and Full Admin Access:

This profile will allow you to enable 2 of the 3 permissions that TeamViewer Host needs. Screen Recording is a permission that can not be allowed by anyone but the user. You can, however, give a Standard User the rights to allow Screen Recording (macOS 11+).

TCC Profile for TeamViewer Host

↓ macOS

TCC Profile for TeamViewer Host (Including Standard User Screen Recording Allowance)

Alternatively below is a profile that allows a Standard User to enable Screen Recording for TeamViewer App (requires macOS 11+):

↓ macOS

These profiles have the same profile identifier, which is used to determine if the Profile is already installed during installation.  Only upload one of these Profiles at any one time. If prompted the following 'Another Fileset already has the same profile payload identifier', do not accept.  Remove the matching profile from FileWave and then upload this one.

We are including the below Fileset/payload as an example only to show the use of the settings file.  You'll always want to download the most recent version of TeamViewer yourself at the link above for your own installer.  That said, this is a fully functioning Fileset for the TeamViewer Host application.

PKG - Install TeamViewerHost.pkg

To put the latest TeamViewer Host PKG in this Fileset you should download the installer from TeamViewer, and then right-click the installer app and Show Contents which will reveal the Install TeamViewerHost.PKG file. Edit the example Fileset below and add the PKG installer to /usr/local/etc/TeamViewer/ and replace the one in the Fileset.

This Fileset example includes the below Requirement Script that checks for the profile from the TCC Fileset. This way TeamViewer Host won't install until that profile is present.

1 2 3 4 5 6 7 8 9 10 #!/bin/zsh profile_id="ml1063.lan.30916554-5d82-4d52-a86d-3cd457330717.Configuration.30916554-5d82-4d52-a86d-3cd457330717" found_profile=$(profiles list all | awk -v search=$profile_id '$0 ~ search {print $NF}') if [ -z $found_profile ] then echo "Did not find $profile_id" exit 1 fi echo "Found installed profile: $found_profile" exit 0

The Fileset also includes this script which makes the installation silent for TeamViewer Host and hides the Wizard that would normally appear after the install. 

1 2 3 #!/bin/zsh installer -applyChoiceChangesXML /usr/local/etc/TeamViewer/choices.xml -pkg "/usr/local/etc/TeamViewer/Install TeamViewerHost.pkg" -target / exit 0

Install TeamViewer Host

↓ macOS

Associate the Fileset Group to devices.  A requirement script ensures the Teamviewer Profile is installed prior to installing the TeamViewer software. TeamViewer also provides guidance here on mass deployment that may be helpful: https://community.teamviewer.com/English/kb/articles/50739-mass-deployment-on-macos