The following are assumptions that help you determine if you must adjust the hardware requirements shown in the sizing tables based on the hardware needs of your environment.

Additional requirements for the components listed below can be found in their respective sections. View the sizing tables at On-Premises Architecture Sizing for up to 25,000 Devices, On-Premises Architecture Sizing for up to 50,000 Devices, or On-Premises Architecture Sizing for up to 100,000 Devices.

General Assumptions

  • High Availability is easily accomplished in Workspace ONE UEM but affects your requirements. Contact Workspace ONE UEM if you need further assistance, since every deployment is unique and has its own requirements.

  • Support for TLS 1.0, 1.1, and 1.2 is provided.

  • Sizing estimates include allocation for 1 GB of cumulative app storage. Increase the server disk space and DB disk space to account for increased storage (for example, a 5 GB app deployment requires an extra 4 GB disk space for the database and application servers).

  • Sizing estimates include allocation for 1 GB of cumulative content storage for the VMware Content Locker. Increase the server disk space to account for increased storage (for example, 5 GB of content requires an extra 4 GB disk space for the application servers).

  • Servers must be set up in English. Workspace ONE UEM must be set up on an English operating system.

Database Server Hardware Assumptions

Unless otherwise specified, the following assumptions are made regarding server hardware used to host the Workspace ONE UEM database:

  • You can install the Workspace ONE UEM database on physical or virtualized hardware.

    • If installing on virtualized hardware, ensure you are following the VMware and Microsoft best practices for SQL deployments. Also ensure I/O requirements can be met and the overall virtual architecture supports Workspace ONE UEM requirements.

  • If Workspace ONE UEM is to be installed on a shared database server, Workspace ONE UEM must be given its own instance with earmarked resources as defined in the On-Premises Architecture Sizing for up to 5,000 and 25,000 Devices.

Other Workspace ONE UEM Components

The following sections show the hardware assumptions for various Workspace ONE UEM components. They are listed here to give you an idea of what you will need to configure them based on the needs of your deployment. Each component has a separate guide, available at docs.vmware.com, that you can reference for additional requirements and information.

VMware Identity Manager Service Hardware Sizing

The following assumptions are made regarding server hardware used to host the VMware Identity Manager Service. For sizing above the highest amount, contact Workspace ONE UEM.

Number of Users

1,000 to 10,000

10,000 to 25,000

25,000 to 50,000

50,000 to 100,000

CPU cores

3 load-balanced servers with 2 CPU cores

3 load-balanced servers with 4 CPU cores

3 load-balanced servers with 8 CPU cores

3 load-balanced servers with 8 CPU cores

RAM

6 GB each

8 GB each

16 GB each

32 GB each

Hard Disk Space

100 GB each

100 GB each

100 GB each

100 GB each

Database Sizing Increase

When you deploy the VMware Identity Manager Service, you must increase the size of your Workspace ONE UEM database.

Number of Users

1,000 to 10,000

10,000 to 25,000

25,000 to 50,000

50,000 to 100,000

CPU cores

+2 CPU cores

+4 CPU cores

+8 CPU cores

+8 CPU cores

RAM

+4 GB each

+8 GB each

+16 GB each

+32 GB each

Hard Disk Space

+50 GB each

+50 GB each

+100 GB each

+100 GB each

An Intel processor is required. CPU Cores should each be 2.0 GHz or higher.

VMware AirWatch Cloud Connector Server Hardware Sizing

The following assumptions are made regarding server hardware used to host the VMware AirWatch Cloud Connector. For sizing above the highest amount, contact Workspace ONE UEM.

Number of Users

1,000 to 10,000

10,000 to 25,000

25,000 to 50,000

50,000 to 100,000

ACC Requirements

CPU Cores

2 CPU cores

2 load-balanced servers with 2 CPU cores

2 load-balanced servers with 2 CPU cores

3 load-balanced servers with 2 CPU cores

RAM

4 GB

4 GB each

4 GB each

8 GB each

Disk Space

50 GB

50 GB each

50 GB each

50 GB each

The VMware Identity Manager Connector component has the following additional requirements. If you are installing both the ACC and VMware Identity Manager Connector components, add these requirements to the ACC requirements.

Number of Users

1,000 to 10,000

10,000 to 25,000

25,000 to 50,000

50,000 to 100,000

VMware Identity Manager Connector Requirements

CPU Cores

2 load-balanced servers with 4 CPU Cores

2 load-balanced servers with 4 CPU Cores

2 load-balanced servers with 4 CPU Cores

2 load-balanced servers with 4 CPU Cores

RAM

6 GB each

8 GB each

16 GB each

16 GB each

Disk Space

50 GB each

50 GB each

50 GB each

50 GB each

Notes:

  • VMware Enterprise Systems Connector traffic is automatically load-balanced by the AWCM component. It does not require a separate load balancer. Multiple VMware Enterprise Systems Connectors in the same organization group that connect to the same AWCM server for high availability can all expect to receive traffic (a live-live configuration). How traffic is routed is determined by AWCM and depends on the current load.

  • CPU Cores should each be 2.0 GHz or higher. An Intel processor is required.

  • Disk Space requirements include: 1 GB disk space for the VMware Enterprise Systems Connector application, Windows OS, and .NET runtime. Additional disk space is allocated for logging.

Secure Email Gateway Server Hardware Sizing

The following assumptions are made regarding server hardware used to host the Secure Email Gateway (SEG) application.

Classic Platform

SEG

CPU Core

RAM

Notes

SEG without content transformation

2

4 GB

Per 4,000 devices, up to a maximum of 16,000 devices (8 CPU/16 GB RAM) per application server

SEG with content transformation

(Attachment handling, hyperlinks security, tagging, etc.)

2

4 GB

Per 500 devices (250 devices per core), up to a maximum of 2,000 devices (8 CPU/16 GB RAM) per application server

 

Performance varies based on the size and quantity of transforms. These numbers reflect a deployment with a high number of content transforms. Sizing estimates vary based on actual email and attachment usage

Notes for both SEG deployment types:

  • An Intel processor is required. CPU Cores should each be 2.0 GHz or higher.

  • The minimum requirements for a single SEG server are 2 CPU cores and 4 GB of RAM.

  • IIS App Pool Maximum Worker Processes should be configured as (# of CPU Cores / 2).

  • When installing SEG servers in a load balanced configuration, sizing requirements can be viewed as cumulative. For example, a SEG environment requiring 4 CPU Cores and 8GB of RAM can be supported by either:

    • One single SEG server with 4 CPU cores and 8GB RAM.

      or

    • Two load balanced SEG servers with 2 CPU core and 4GB RAM each.

  • 5 GB Disk Space needed per SEG and dependent software (IIS). This does not include system monitoring tools or additional server applications.

V2 Platform

SEG 

CPU Core

RAM

Notes

SEG without content transformation

2

4 GB

Per 8,000 devices, up to a maximum of 32,000 devices (8 CPU/ 16 GB RAM) per application server.

SEG with content transformation (Attachment handling, hyperlinks security, tagging etc.)

2

4 GB

Per 4,000 devices (2,000 devices per core) per application server, up to a maximum of 16,000 devices (8 CPU/16 GB RAM)

Performance varies based on the size and quantity of transforms. These numbers reflect a deployment with a high number of content transforms. Sizing estimates vary based on actual email and attachment usage.

Notes for both SEG deployments types: 

  • An Intel processor is required. CPU Cores should each be 2.0 GHz or higher.

  • The minimum requirements for a single SEG server are 2 CPU cores and 4 GB of RAM.

  • When installing SEG servers in a load balanced configuration, sizing requirements can be viewed as cumulative. For example, a SEG environment requiring 4 CPU Cores and 8GB of RAM can be supported by either:

    • One single SEG server with 4 CPU cores and 8GB RAM.

      or

    • Two load balanced SEG servers with 2 CPU core and 4GB RAM each.

  • 5 GB Disk Space needed per SEG and dependent software. This does not include system monitoring tools or additional server applications.

VMware Tunnel and Unified Content Gateway (Tunnel) Hardware Sizing

The following assumptions are made regarding server hardware used to host the VMware Tunnel. For sizing above the highest amount, contact Workspace ONE UEM.

Hardware Sizing

Use the table to determine the sizing requirements for your deployment. Each column represents the requirements for a deployment up to that number of devices. The columns are not cumulative – each column contains the exact requirements for the listed number of devices.

Number of Devices

Up to 5,000

5,000 to 10,000

10,000 to 40,000

40,000 to 100,000

CPU Cores

1 server with 2 CPU Cores*

2 load-balanced servers with 2 CPU Cores each

2 load-balanced servers with 4 CPU Cores each

4 load-balanced servers with 4 CPU Cores each

RAM (GB)

4

4 each

8 each

16 each

Hard Disk Space (GB)

10 GB for distro (Linux only)

400 MB for installer

~10 GB for log file space**

*It is possible to deploy only a single VMware Tunnel server as part of a smaller deployment. However, consider deploying at least 2 load-balanced servers with 2 CPU Cores each regardless of number of devices for uptime and performance purposes.

**About 10 GB is for a typical deployment. Log file size should be scaled based on your log usage and requirements for storing logs.

AirWatch Content Gateway and Unified Access Gateway (Content Gateway) Hardware Sizing

The following assumptions are made regarding server hardware used to host the AirWatch Content Gateway. For sizing above the highest amount, contact Workspace ONE UEM. Consider deploying Content Gateway on a separate server from the VMware Tunnel, as both have different network and system requirements. If your deployment requires that Content Gateway be installed on the same server as VMware Tunnel, reference the Unified Access Gateway documentation at https://docs.vmware.com/en/Unified-Access-Gateway/index.html.

Hardware Sizing

Use the table to determine the sizing requirements for your deployment. Each column represents the requirements for a deployment up to that number of devices. The columns are not cumulative – each column contains the exact requirements for the listed number of devices.

Requirement

CPU Cores

RAM (GB)

Disk Space

Notes

VM or Physical Server (64-bit)

2 CPU Core (2.0+ GHz)*

*An Intel processor is required.

2 GB+ 

5 GB 

The requirements listed here support basic data query. You may require additional server space if your use case involves the transmission of large encrypted files from a content repository.

Sizing Recommendations

Number of Devices

Up to 5,000

5,000 to 10,000

10,000 to 40,000

40,000 to 100,000

CPU Cores

1 server with 2 CPU Cores*

2 load-balanced servers with 2 CPU Cores each

2 load-balanced servers with 4 CPU Cores each

4 load-balanced servers with 4 CPU Cores each

RAM (GB)

4

4 each

8 each

16 each

Hard Disk Space (GB)

10 GB for distro (Linux only)

400 MB for installer

~10 GB for log file space**

*It is possible to deploy only a single AirWatch Content Gateway server as part of a smaller deployment. However, consider deploying at least 2 load-balanced servers with 2 CPU Cores each regardless of number of devices for uptime and performance purposes.

**About 10 GB is for a typical deployment. Log file size should be scaled based on your log usage and requirements for storing logs.

Email Notification Service Hardware Sizing

The following assumptions are made regarding server hardware used to host the Email Notification Service (ENS) application.

Hardware Sizing - Classic

Table 1.

CPU Cores

RAM

Hard Disk Storage

Notes

2 (Intel processor)

4 GB

10 GB

Per 20,000 users

Hardware Sizing - V2

ENS Server

CPU Core

RAM

Hard Disk Storage

Notes

App Server

2 (2 GHz Intel processor)

16 GB

50 GB

Up to 100,000 users.

Database Server

2 (2 GHz Intel processor)

16 GB

50 GB

Up to 100,000 users.

Reports Storage Requirement

To use the new reports framework, which generates reports with greater reliability and faster download times, you must set up reports storage. For instructions on enabling reports storage in the Workspace ONE UEM Console, see Reports Storage Requirements.

Workspace ONE Intelligence

 

5000 Devices

25,000 Devices

50,000 Devices

100,000 Devices

Servers

1

1

1

1

CPUs

2 (2 GHz Intel processor)

2 (2 GHz Intel processor)

2 (2 GHz Intel processor)

2 (2 GHz Intel processor)

Memory

4GB

8GB

8GB

16GB

Storage

25GB

25GB

25GB

25GB

Adaptiva

Component

Requirement

Operating system

Windows Server 2008+

Processor

Xeon Processor, single quad core (2 GHz Intel processor)

Memory allocation

  • 0 to 5,000 clients - 2048 MB

  • 5,001 to 10,000 clients - 3072 MB

  • 10,001 to 19,999 clients - 5120 MB

  • 20,000 to 49,999 clients - 6144 MB

  • 50,000+ - 8192 MB

Memcached

Component

0-300k devices

300k+ devices

CPU Cores(2 GHz Intel processor)

2

2

RAM

8 GB

16 GB

Dell Factory Provisioning

Factory Provisioning hardware requirements are not necessarily related to the number of devices in your organization. The hardware requirements correlate to the number of concurrent provisioning packages that you request. These hardware requirements assume a maximum package size of 25 GB and a maximum of 3 concurrent packages requested at a time.

Dell Factory Provisioning Service should be installed on a standalone server meeting these requirements.

Table 2. Dell Factory Provisioning Service Server Requirements

Component

3 Packages (25 GB)

Servers

1

CPUs

2 (2 GHz Intel processor)

Memory

6GB (Windows Server)

Storage

100GB

VMware Workspace ONE Airlift

Table 3. Workspace ONE Airlift Server Requirements

Component

Requirement

Servers

1

CPUs

2 (2 Ghz Intel processor)

Memory

4GB

Storage

1GB disk space for the Airlift application, operating system, and .NET core runtime. Consider allocating 5GB of disk space.