Skip to end of metadata
Go to start of metadata

What

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.

When/Why

We'll need to meet pre-requisites for Windows client devices for TeamViewer to work seamlessly.  We need the FileWave client to be upgraded to at least 14.6, and we'll want to deploy the TeamViewer application as well.  (Technically the TeamViewer App can be run or installed by the customer, but pre-deploying makes the experience much more seamless and avoids issues with administrative rights, etc.)

How

The most recent FileWave client is always included on the FileWave download pages, which you can find here: https://kb.filewave.com/display/DOW/FileWave+Management+Suite

Remember to always use the client updater fileset to update your clients.  Do NOT push the FileWave client MSI to upgrade Windows clients.

And, the TeamViewer application for Windows can be found here: https://www.teamviewer.com/en-us/download/windows/

Note that the TeamViewer installer is the setup.exe type, not an MSI.  To run the install silently, you'll want to run the exe with a /S option when deploying it through FileWave.  To do this, you'll add a launch argument as shown in this EXAMPLE fileset/payload.

We are including the below fileset/payload as an example only to show the use of the launch argument.  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 64-bit version.


TeamViewer Windows 64 Bit.fileset.zip