New: Improved usability for multi-tab display in the session window. Informational banners in the desktop client regarding managed device limits can now be dismissed Thanks to Adam Arruda and Niv Schwager for sharing the required info to enable this feature :-) Raw XML is also attached to this post for use in a different profile/deployment method.- Change log not available for this version Device should connect and you will have full Remote Control access from the PC including file transfer. Press the confirmation button on the device side to confirm that remote access should be allowed.ĥ. Run the TeamViewer PC client ( I used the PortableApps version at TeamViewer Portable (remote PC support and screen-sharing) | ) and enter the client iD to connect.Ĥ.

Run the TeamViewer QuickSupport app and (provided the required ports are open on your network), the client ID should be displayed on screen.ģ. Preconfigure an internet connection, run StageNow and scan the barcode below:Ģ. To simplify deployment of the required TeamViewer client and the XML required to enable it, the SN barcode below will deploy and enable the client on any Oreo Zebra device which has a preconfigured internet connection.ġ. This service is enabled via the Service Access Action/Allow caller feature of AccessMgr CSP as detailed here Access Manager - Zebra Technologies Techdocs and requires a caller signature to be specified for the calling app (in this case the TeamViewer client). This uses the new Event Injection service which was added in Oreo and provides a method for third party apps to implement remote control without requiring app signing by Zebra.

With the release of Oreo OS for SD6 based products, we have the ability to support full remote control of our devices via TeamViewer which is a feature that has been requested many times over the past few years.

Global Solution Centers - Testing Services.

Images teamviewer qs screen