Advanced Remote Management (ARM) uses multiple components to facilitate the communication between admins and end-user devices.

The core components are as follows.


The database handles system and tenant configuration, operations, and logging such as the accrual of historical device enrollment data.

Core Services

The Core Services component provides service discovery and auxiliary services for the ARM solution through Web services and Windows services. These services include the following.

  • Management Entity (ME) – Windows service that provides an in-memory datastore for admin and management Web service, which provides the operational end point to the system.
  • AetherPal Tool Controller Service (ACS) – Acts as a gateway service that maintains a consistent socket connection between the Admin Web Portal and the Connection Proctor. It is instrumental in supporting HTML5 Web portal.
  • Service Coordinator (SVC) – This Windows service is responsible for coordinating communication between various elements within the system. It provides the communication to the database and is responsible for the discovery of all other Remote Management Tool services. All ARM Tool services register with this service. Service coordinator service is installed on an Application (App) Server.
  • Data Tier Proxy (DTP) – This Windows service works with the Service Coordinator. It serves as the gateway for all services to reach the Service Coordinator service to communicate with Remote Management Tool databases. Data Tier Proxy service is installed on the App Server.
  • Data Access Proxy (DAP) – This Web service is responsible for a proper communication of all Web services. It serves a similar purpose as the Data Tier Proxy service and is installed on the App server.

Portal Services

The Portal Services component handles the administrative and management services for ARM. The Management Website is installed as part of the portal services component and consists of the following.

  • Anchor Web Service – provides a single point of entry for all devices for enrollment and authentication services during a session. The Anchor service comprises of the following components.
    • Device Registration: Before enrollment, devices are required to register themselves with this service.
    • Device Enrollment: Enrolls registered devices with the system.
    • Software Update: Devices connect to this service to request client updates. If an update is available, the service provides the appropriate client download link. This component also manages various client packages in the system.
    • Device Management: When the enrolled device detects a change, this service provides an interface with which to update its parameters in the ARM Tool such as MDN.
    • Admin Anchor: Provides the administration component for the Anchor service.

T10 Interface

The T10 interface is the part of the Management website under Portal Services that defines an integration portal between AirWatch and the ARM server.

The T10 interface uses Representational State Transfer (REST) communication with a JavaScript Object Notation (JSON) payload. The T10 interface allows AirWatch to make a mobile device eligibility call.

The T10 interface can also start a remote support session using the ARM tool and delete the device from the ARM system.

Application Services

Messaging Entity (MSG) is a core Windows service that provides the means for the ARM tool to send out SMS messages to the device via API or direct communication with a messaging gateway, such as Google Cloud Messaging (GCM), or any proprietary SMSC aggregator.

Connection Proctor

The Connection Proctor component uses the Windows Connection Proctor service to manage device connections to the ARM server. The component also simultaneously handles multiple requests for sessions.