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 iOS/iPadOS mobile devices for TeamViewer to work seamlessly.  We'll need the new FileWave Kiosk IPA* deployed, and we'll probably want to push out the TeamViewer QuickSupport application as well.  (Technically the TeamViewer QS App can be run or installed by the customer, but pre-deploying makes the experience much more seamless and avoids issues with licenses, etc.)

Note:  Many of you probably currently only employ the webclip version of the Kiosk, but TeamViewer will only work with the IPA version of the kiosk because we must have an application on the device that can receive a push notification.  The IPA can be downloaded from the main FileWave download page.

How

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

The TeamViewer QuickSupport app can be found in the iTunes app store here, and of course you'll want to buy licenses (a free app) through your ASM or ABM portal before attempting to distribute.

Both of the above can be pushed like any normal Apple MDM fileset/payload in the native or web administrator consoles.

Note: Although the deployment of these apps is simple, and you'll probably eventually want to deploy both to all devices, it is ALWAYS best practice to test on a smaller set of devices initially before you deploy en masse.