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 Android client devices for TeamViewer to work seamlessly.  We'll need the FileWave companion app to be upgraded to at least 14.6, and we'll want to deploy the TeamViewer Quicksupport and add-on applications as well.  

ComponentInstall?Notes
Android EMM Companion App (FW Client App)
  • Yes
Auto-deployed
TeamViewer QuickSupport App (Google Play Store)
  • Yes

Details, which can be deployed as a FileWave fileset: Play Store App - TeamViewer QuickSupport.fileset.zip

TeamViewer Add-On (Google Play Store)
  • Yes
The add-on is required for device control (typing, screen clicks, etc)...and is specific to each type of Android device, reference the article linked to from the How section below for specifics about best practices for deployment

FW Client App must be able to both resolve the server DNS name and reach the server, since communication from this App is direct to server, not via Google.  Without this communication, the version of FW Client will not be updated on the server and the option to 'Open Remote Session' will be greyed out.

How

Reference the following article for deployment best practices and how-to for TeamViewer for Android: TeamViewer: Android QS/Add-On Deployment Best Practice



  • No labels