TeamViewer: Windows Client Setup

What

FileWave's TeamViewer integration requires endpoint prerequisites on each supported platform.  In future versions, we may embed some of these prerequisites, 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 prerequisites for Windows client devices for TeamViewer to work seamlessly. (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.) We'll need the following: 

The host version of TeamViewer does not provide the ability for users to control other devices. 

How

FileWave Client

The most recent FileWave client is always included on the FileWave download pages, which you can find here: Downloads

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

TeamViewer

The installer is actioned with scripts configured to ensure the installation is silent, including:

TeamViewer Host MSI download requires an account with TeamViewer.  FileWave includes the MSI within the Fileset, but this should not be exported and redistributed.  FileWave will aim to update the Fileset periodically to include newer versions of TeamViewer.

Choose an embedded TeamViewer Fileset:

Note that you only need one of the below, but we may offer several versions in case you need an older version.

 

TeamViewer Host Windows 15.53.6.0.fileset.zip

 

TeamViewer Host Windows 15.40.8.0.fileset.zip

If there is a need to update before FileWave has provided a newer version, the download of the latest version of TeamViewer Host is only available publicly as an EXE:

If downloading the EXE, a new Fileset should be created using the EXE to upgrade.

Access to the MSI is limited to those with accounts, but if access is available, download the latest MSI.  After downloading the MSI, replace the current 'TeamViewer_Host.msi' with the downloaded version, ensuring the name of the MSI installer matches.

Disassociation of the Fileset will uninstall TeamViewer Host with a pre-uninstallation script.

Customization

The Fileset provided has an example 'tvopt' file, which will customize the installation if left as is.  If no customization is desired, this file may be removed.  Alternatively, it is possible to upload an alternate 'tvpopt; file, preset as desired.

Example file 'example.custom.tvopt' highlighted in the image.  Add a built file into the same directory called 'custom.tvopt' to override this; the 'example.custom.tvopt' may be left behind or removed.

TV_Fileset_Contents.png

Create Custom 'tvopt'

Follow the example instructions below to create a TeamViewer Host custom settings file for enforcement at the time of installation.

The TeamViewer Host app can be customized and secured to:
  * Prevent users from connecting to their own devices remotely. Connections will only be possible via FileWave
  * Blocking users from editing the settings by protecting them with a password.

For example, to secure the TeamViewer Host app and export its settings:

  1. Install the TeamViewer Host component on a test device.

  2. Launch it from the TeamViewer icon in the system tray, edit the settings and set the following options:

    • Security > Random password (for spontaneous access) > Password strength=Disabled (no random password)

    • Advanced > TeamViewer options > Changes require administrative rights on this computer

      • Set Options/Confirm password fields
  3. Click the Export button at the bottom of the Advanced options sections on the right. Save it as 'custom.tvopt'.

    • Check Export user-specific settings as default for all users
  4. Drag the 'custom.tvopt' file into the Fileset within the same directory as the current example file and installer MSI

  5. Test before deploying en masse

TeamViewer also provides guidance here on mass deployment that may be helpful: https://community.teamviewer.com/English/kb/articles/39639-mass-deployment-on-windows


Revision #5
Created 15 June 2023 00:41:00 by Josh Levitsky
Updated 12 June 2024 20:25:27 by Sean Holden