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 and Edge support the File Manager and Clipboard features. |
| Omnissa 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.
| 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 |
| 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 |
| 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 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) * MS SQL 2014–2022 Express (if DB is on the same server). | 1 server, optional (2 CPUs, 8 GB RAM, 250 GB HDD): * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI). * MS SQL 2014–2022 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 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) * MS SQL 2014–2022 Standard/Enterprise (if DB is on same server). | 1 server, optional (2 CPUs, 8 GB RAM, 250 GB HDD): * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) * MS SQL 2014–2022 Standard/Enterprise(SQL Always ON is supported) | 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 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) | 1 server, optional (2 CPUs, 16 GB RAM, 250 GB HDD): * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) * MS SQL 2014–2022 Standard/Enterprise (SQL Always ON is supported) | 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 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) * MS SQL 2014–2022 Standard/Enterprise (SQL Always ON is supported) | 2 servers (4 CPUs, 16 GB RAM, 250 GB HDD: * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) | 2 servers (4 CPUs, 32 GB RAM, 250 GB HDD: * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (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 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) * MS SQL 2014–2022 Standard/Enterprise (SQL Always ON is supported) | 4 servers (8 CPUs, 16 GB RAM, 250 GB HDD: * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (w/GUI) | 4 servers (8 CPUs, 32 GB RAM, 250 GB HDD: * Windows 2016 (w/GUI), 2019 (w/GUI), 2022 (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
| Requirement | Description |
|---|---|
| Operating System | Microsoft Windows Server 2022 (w/GUI), 2019 (w/GUI), 2016 (w/GUI). |
| Software | Microsoft .NET Framework 4.8 |
| Server Roles * |
|
| Features ** |
|
* 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.8 or newer.
| Requirement | Description |
|---|---|
| Operating System |
|
| Software |
|
Databases and 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:
- The server admin equivalent user is required only during installation.
- Each of these elements are created on the Database Server automatically when the installer runs.
| User Mapping | Dbowner |
| Users | Apdbuser Database role: Db_owner for all Assist user databases. Apadminuser Database role: Db_owner for all Assist user databases. Note: Apdbuser/Apadminuser name can be changed or customized during database installation. |
| 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. ApPublic Contains pre-enrollment information on devices. There is only one ApPublic database for all tenants. APOps (template DB), Apops_<UUID> (Database Apops_<UUID> is created based on the APOps - template DB) Maintains data required for the operations of the system such as device enrollment, Access Control List’s (ACL), groups, users, zones, and so on. There is one template APOps database and one for the tenant with the GUID. APReports (template DB), Apreports_<UUID> (Database Apreports _<UUID> is created based on APReports - template DB) Contains historical data of device enrollment, session, audit, report views, and so on. There is one template APReports database and one for the tenant with a GUID. ApJournal (template DB), Apjournal_<UUID> (Database Apjournal _<UUID> is created based on ApJournal - template DB) Contains aggregated information on the tenant necessary to construct various reports. There is one template APJournal database and one for the tenant with a GUID. But this is not actively used for on-prem customers. |
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 the 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. |
| Host (A) Record |
The Host (A) Record must be named the following.
|
| Service Coordinator Service Records |
|
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.
Was this page helpful?