End of Support Life for Remote Management 1.0 and legacy Android Remote Control

At the end of this calendar year (December 31, 2016), AirWatch will be officially ending the support life of the legacy Android Remote Control product and it will be removed from the Google Play Store. This product was the first generation of solutions for remotely accessing a device. This solution, however, offered limited features from a troubleshooting and maintenance stand point, and due to the increasing obsolescence of the technology used, it also has security and performance gaps that have been addressed in later generations of products.

In addition, future releases of the AirWatch Console will no longer support Remote Management 1.0 for currently supported RM platforms (Windows Mobile, Mac OSX, QNX, Windows Desktop, and Android) due to technical obsolescence related to the encryption methods utilized and associated security concerns.  Any devices running Remote Management 1.0 will no longer be able to utilize Remote Management in future AirWatch console releases.

Remote Management 2.1, which was released with AirWatch 8.2, now offers web socket support and fully utilizes HTTP/HTTPS and SSL. This is consistent with current technology and industry standards and offers better security and improved performance.

 

Implications for Customers

Environments using Android Remote Control:

  • AirWatch recommends that in preparation for the official end of support life of this product and removal of the application from the Play Store on December 31, 2016, customers currently utilizing this product for remote control purposes start transitioning to Remote Management 2.1.

 

SaaS environments using Remote Control:

  • The Remote Management software and server configuration has already been setup and enabled.  
  • Administrators can navigate to Device Settings > Device & Users > Android > Agent Settings, find the Remote Management section and enable Web Sockets for the mode.
  • Users will need to uninstall the Remote Control service from existing devices
  • Administrators will need to upload the Remote Management client service to the console as an internal application.
  • Once the Remote Management client is successfully installed on the device the Remote Management option will appear in the Device Details page of the AirWatch console for those devices.

 

On-Premise environments using Remote Control:

  • The Remote Management software and server configuration will need to be installed and configured in your environment. The recommended solution is to stand up a dedicated server for Remote Management.  
  • Administrators can navigate to Device Settings > Device & Users > Android > Agent Settings, find the Remote Management section and enable Web Sockets for the mode.
  • Users will need to uninstall the Remote Control service from existing devices
  • Administrators will need to upload the Remote Management client service to the console as an internal application.
  • Once the Remote Management client is successfully installed on the device the Remote Management option will appear in the Device Details page of the AirWatch console for those devices.
  • If you would like to schedule work with our deployments team on this configuration, please reach out to your Account Executive.

 

Environments utilizing Remote Management 1.0:

  • In future versions of the AirWatch console, the Inbound, Outbound, and Direct Connect Tunnel options available under Device Settings > Devices & Users > [Platform] > Agent Settings > Remote Management will be deprecated along with the associated password setting. This is consistent with VMware’s effort to ensure we are using the most updated and secure technologies.
  • Customers who upgrade to future AirWatch console releases and are using Remote Management 1.0 with one of the above Tunnel modes will need to perform the following changes:
    • Navigate to Device Settings > Device & Users > Android > Agent Settings, find the Remote Management section and enable Web Sockets for the mode.
    • Users will need to uninstall the Remote Management client from existing devices
    • Upload the Remote Management client service to the console as an internal application.
    • For SaaS-based customers, the Remote Management Server will already be installed and available
    • For on-premise customers that elect to upgrade to the next AirWatch console release, Remote Management 2.1 will need to be installed in your environment.
  • If you would like to schedule work with our deployments team on this configuration, please reach out to your Account Executive.

 

 

Support Contact Information

If you have additional questions or concerns, please contact Account Services & Support or submit a support ticket through myAirWatch. 

Have more questions? Submit a request

0 Comments

Article is closed for comments.