Skip to end of metadata
Go to start of metadata


This article picks up from the administrator requesting a remote control session through TeamViewer.  It presumes that all device pre-requisites are already met.


We'll usually create a remote session to try to resolve some type of support issue on a remote device. When we begin the remote session with a Windows device, it is important that we know how it behaves on the remote endpoint so that we can assist the end user if need be.


Once the device receives the remote session notification (think of this as an alert to the device to begin a session), the FileWave client will open a new browser tab to prompt for opening of TeamViewer.  

When that notification is acknowledged, the TeamViewer App will open to start a remote session.  Note that if the TeamViewer App is not pre-deployed, there is an option to launch a single use version of TeamViewer.  The single-use version does not require administrative credentials to run.

On first launch the TeamViewer app will prompt the user to accept the EULA.

Once the admin and client devices have both acknowledged the session, the remote device will be prompted to allow the session:

Once this prompt is acknowledged (and the admin session is also launched), then the  session will begin:

Related Content

Unable to render {children}. Page not found: TeamViewer: Creating a new session.

  • No labels