Workspace ONE Assist 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. The Workspace ONE Assist system is composed of eight databases.

  • ApAdmin – Maintains all the system configurations, tenant (customer) configuration, management information, system administration data, and server instrumentation data. There is only one ApAdmin database for all tenants.
  • APOps (2) – Maintains data required for the operations of the system such as device enrollment, Access Control List’s (ACL), groups, users, zones, and so on. You have one template APOps database and one for the tenant with the GUID.
  • APReports (2) – Contains historical data of device enrollment, session, audit, report views, and so on. You have one template APReports database and one for the tenant with a GUID.
  • APJournal (2) – Contains aggregated information on the tenant necessary to construct various reports. You have one template APJournal database and one for the tenant with a GUID.
  • APPublic – Contains pre-enrollment information on devices and multiple database jobs. There is only one APPublic database for all tenants.

Core Services

The Core Services component provides service discovery and auxiliary services for the Workspace ONE Assist 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.
  • 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 Workspace ONE Assist 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 Workspace ONE Assist. The Management Website is installed as part of the portal services component and consists of the following.

  • AetherPal Tool Controller Service (ACS) – Acts as a gateway service that maintains a consistent socket connection between the RS web console and the Connection Proctor.
  • Management Web Site (ADM/ANC) – IIS Service that hosts the RS web console for managing and remoting into devices. Anchor service responsible for mobile device registration. Also, it contains the System Admin Service (SAS) admin web portal for accessing and administering the tool and defining tenant and service configuration.
    • T10 Interface – The T10 Interface is part of the Management website and it defines an integration portal between Workspace ONE UEM and the Workspace ONE Assist server.
      • The T10 interface uses Representational State Transfer (REST) communication with a JavaScript Object Notation (JSON) payload. The T10 interface provides Workspace ONE UEM with the ability to make a mobile device eligibility call.
      • The T10 interface can also start a remote support session using the Workspace ONE Assist tool and delete the device from the Workspace ONE Assist system.

Application Services

Messaging Entity (MSG) – a core Windows service that provides the means for the Workspace ONE Assist tool to send out SMS messages to the device by way of API or direct communication. This communication is accomplished with a messaging gateway, such as Google Cloud Messaging (GCM), or any proprietary SMSC aggregator.

The remaining application services are installed by default but are not used by Workspace ONE Assist directly. As such, these services can be disabled if you prefer.

  • ZVC Services (ZVC) – Windows service used for GuideMe feature. ZVC Service helps with versioning and authoring management. Workspace ONE Assist does not require this auxiliary service. After installation, these services can be disabled in Windows services.
  • KB Service (KB) – Windows service used for GuideMe feature. This service help process content for delivery and publishing. This is an auxiliary service that is not required by the Workspace ONE Assist application for most use cases. Once installed, these services can be disabled in Windows services.

Connection Proctor

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