Remote Management allows you to connect to end-user devices remotely to aid in troubleshooting and maintenance. Remote Management installs on to a Windows server and acts as a go-between for the AirWatch Console and the end-user device.

Remote Management Basics

AirWatch supports two versions of Remote Management. Remote Management v3.0 is part of the AirWatch installer for on-premises customers and already configured for SaaS customers. Remote Management v4.x is a premium upgrade that requires a specific SKU purchased from VMware. Remote Management v4.x is faster and easier to use than v3.0. Contact AirWatch Support for more information on upgrading to Remote Management v4.x.

Saas customers do not need to take additional steps to use either version of Remote Management. On-premises customers must install Remote Management onto a dedicated Windows server.

Remote Management v4.x

Remote Management v4.x allows you to take control of end-user devices remotely as if the device as in your hand. You can view the screen, select buttons, input keystrokes, and more during your remote session. Remote Management v4.x uses HTML 5 instead of Java to widen browser support and improve usability. Remote Management v4.x requires a dedicated server to handle the communication between the AirWatch Console and end-user devices. Saas customers do not need to take additional steps to use this version of Remote Management. On-premises customers must install Remote Management onto a dedicated Windows server.

For more information, see Introduction to Remote Management v4.x.

Remote Management v3.0

Remote Management v3.0 allows you to control end-user devices remotely using a Java-based platform. This platform allows you to view the screen, select buttons, manage files, and more during your remote session. Remote Management v3.0 requires a browser that supports the Java platform and a dedicated server. Saas customers do not need to take additional steps to use this version of Remote Management. On-premises customers must install Remote Management onto a dedicated Windows server.

For more information, see Introduction to Remote Management v3.0.