Both SaaS and On-Premises customers must meet minimum requirements before using Workspace ONE Assist.

General Requirements

SaaS customers must meet only the general requirements listed here.

Requirements Minimum
Supported Browsers for Admins Latest version of Google Chrome, Firefox, Safari, or Edge. Only Chrome supports the File Manager feature.
Workspace ONE ™ UEM version Workspace ONE UEM 9.2 or later with the ARM add-on.

Hardware Requirements (for On-Premises Servers)

In addition to the general requirements, on-premises customers must also meet the hardware requirements.

Table 1. Workspace ONE Assist Server (On-Premises Server)
Hardware Minimum
CPUs 2.4 GHz Processors, 4 Logical Processors, 2 CPUs, 2 Core 2x2 or 4 physical depending on machine type, virtual machine, or physical.
Memory 16 GB
Hard Drive IOPS 200
Hard Drive Space 100 GB for OS drive
Table 2. Workspace ONE Assist Database Server (for On-Premises Server)
Hardware Minimum
CPUs 2.4 GHz Processors, 4 Logical Processors, 2 CPUs, 2 Core 2x2 or 4 physical depending on the machine type, virtual machine, or physical.
Memory 16 GB
Hard Drive IOPS 200
Hard Drive Space

200 GB for databases

Table 3. Bandwidth
Hardware Minimum
Average Remote Session Requirement 1 MB/per minute (17 kbps)

On-Premises Hardware Scaling Requirements

Use the following requirements as a basis for creating an effective Workspace ONE Assist system that scales to your on-premises environment.

These requirements do not include network equipment such as load balancers or monitoring servers. All the arrangements presented here offer a high system availability in active and passive modes.

# Devices /

# of Concurrent Remote Sessions /

# of Concurrent Enrollments

Core Server

(all in one)

DB Server CP Server CAP Server

Less than 1000 /

Up to 50 sessions /

5 enrollments per sec

1 server (2 CPUs, 32 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Express (if DB is on the same server).

1 server, optional (2 CPUs, 8 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Express.

n/a n/a

1000–10,000 /

Up to 50 sessions /

5 enrollments per sec

1 server (2 CPUs, 32 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Standard (if DB is on same server).

1 server, optional (2 CPUs, 8 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Standard.

n/a n/a

10,000–100,000 /

Up to 50 sessions /

5 enrollments per sec

1 server (2 CPUs, 32 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

1 server, optional (2 CPUs, 16 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Standard.

n/a n/a

100,000–500,000 /

Up to 100 sessions /

20 enrollments per sec

n/a

SQL cluster (2 CPUs, 32 GB RAM, 250 GB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Standard.

2 servers (4 CPUs, 16 GB RAM, 250 GB HDD:

* Windows 2012 or 2016 w/GUI.

2 servers (4 CPUs, 32 GB RAM, 250 GB HDD:

* Windows 2012 or 2016 w/GUI.

500,000–1 million /

Up to 200 sessions /

40 enrollments per sec

n/a

SQL cluster (4 CPUs, 32–64 GB RAM, 1 TB HDD):

* Windows 2012 or 2016 w/GUI.

* MS SQL 2012–2016 Standard.

4 servers (8 CPUs, 16 GB RAM, 250 GB HDD:

* Windows 2012 or 2016 w/GUI.

4 servers (8 CPUs, 32 GB RAM, 250 GB HDD:

* Windows 2012 or 2016 w/GUI.

On-Premises Software Requirements

Ensure that you meet the following software requirements to run Workspace ONE Assist.

SaaS and On-Premises Device Software Requirements

For a full listing of platform-specific software requirements for devices, see Supported Platforms and Configure End-User Devices.

On-Premises Installation Software Requirements

Table 4. Workspace ONE Assist Server
Requirement Description
Operating System Microsoft Windows Server 2019 (w/GUI), 2016 (w/GUI), or 2012 R2.
Software

Microsoft .NET Framework 4.7.2

Server Roles *
  • Application Server.
  • Web Server IIS.
Features **
  • .NET Framework 4.7 Features.
    • .NET Framework 4.7.2
    • ASP .NET 4.7.
    • WCF Services.
      • HTTP Activation.
      • Message Queuing (MSMQ) Activation.
      • Named Pipe Activation.
      • TCP Activation and TCP Port Sharing.
  • Message Queuing Services.
  • Windows Process Activation Service.
    • Process Model.
    • .NET Environment 3.5.
    • Configuration APIs.

* For medium and multiple server deployments, these roles are not required on the Connection Proctor (CP) Servers. The ONLY software requirement on Connection Proctor (CP) servers is .NET Framework 4.7.2 or newer.

Table 5. Workspace ONE Assist Database
Requirement Description
Operating System
  • Microsoft Windows Server 2019, 2016, or 2012 R2.
Software
  • MS SQL Server of any of the following versions.
    • 2012 Standard
    • 2014 Standard or Enterprise
    • 2016 Standard or Enterprise
    • 2017 Standard or Enterprise
    • Express 2012 or later (only for deployments with less than 2000 devices)
  • MS SQL Management Studio 17 (only when SQL Server Express 2012 or later is used).
  • Microsoft .Net Framework 4.7
  • Microsoft SQL Server Management Objects (SMO) DLL

Database Settings Created Automatically During Installation

You must have a server admin account (or equivalent) for these elements to auto-create when you install Workspace ONE Assist.

Note: Each of these elements are created on the Database Server automatically when the installer runs.
Server Roles
  • Sysadmin.
  • Bulkadmin.
  • Dbcreator.
User Mapping
  • Dbowner.
  • Dbbackupoperator.
  • SQLAgent dependent.
  • serverGroup dependent.
Users

Apdbuser

Server role: Db_creator.

Database role: Db_owner for all aetherpal user databases. On MSDB, database role to create SQL jobs.

[SQLAgentOperatorRole]

[SQLAgentReaderRole]

{SQLAgentUserRole]

Apadminuser

Server role: Db_creator, to create multitenant databases.

Database role: Db_owner for all aetherpal user databases. On MSDB, database role to create SQL jobs.

[SQLAgentOperatorRole]

[SQLAgentReaderRole]

{SQLAgentUserRole]

Domain Name Service

Domain Name Service is optional for on-premises multiple server deployments of Workspace ONE Assist. Domain Name Service is NOT required on single-server deployments (App+Core+Portal+CP).

In multiple server deployments, the Workspace ONE Assist server requires a forward lookup zone and three DNS records within the forward lookup zone. These records enable devices to communicate properly with the components within the Workspace ONE Assist server. The forward lookup zone, the host record, and service records all must point to the Workspace ONE Assist server.

Requirement Description
Forward Lookup Zone

Create a forward lookup zone that points to your Workspace ONE Assist server.

The forward lookup zone must be named.

controlplane.aetherpal.internal
Host (A) Record

The Host (A) Record must be named the following.

admin
  • If the Workspace ONE Assist Server is behind a load balancer, then the Host (A) Record must point to the internal IP address of the VIP (also known as Virtual IP) for the load balanced pool.
  • If the Workspace ONE Assist server is not behind a load balancer, then the Host (A) Record must point to the Workspace ONE Assist Server IP address.
Service Coordinator Service Records
  • Record type: SRV.
  • Domain: controlplane.aetherpal.internal
  • Service: _svc.
  • Protocol: _tcp.
  • Priority: 0
  • Weight: 0
  • Port number: 8870
  • Host Offering this service: admin.controlplane.aetherpal.internal

Custom Lookup Zone

You can use a custom Forward Lookup Zone with the Domain Name Service in place of the prescribed zone above. Full instructions on entering a custom lookup zone are provided in steps 11 and 14 of the Advanced (Custom) Installation of Workspace ONE Assist. See Advanced (Custom) Installation of Workspace ONE Assist.