Reference Architecture VM Specifications
This chapter is one of a series that make up the Omnissa Workspace ONE and Horizon Reference Architecture, a framework that provides guidance on the architecture, design considerations, and deployment of Omnissa Workspace ONE and Omnissa Horizon solutions. This chapter provides information about the specifications for the various management servers and connector virtual machines used to validate the reference architecture.
Workspace ONE UEM
Several servers are required to take advantage of all features in an Omnissa Workspace ONE UEM deployment.
AirWatch Cloud Connector Server
Depending on the scale of the environment and the number of devices to be supported, the recommended resources allocated to each Omnissa AirWatch Cloud Connector VM can differ.
The AirWatch Cloud Connector synchronizes Workspace ONE with internal resources such as Active Directory or a Certificate Authority and can be used in both cloud-based and on-premises deployments of Workspace ONE UEM.
Table 1: AirWatch Cloud Connector VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 6 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 100 GB |
Workspace ONE UEM Device Services Server
This server hosts Workspace ONE Device Services, which communicate with end-user devices for device enrollment, application provisioning, delivering device commands, receiving device data, and providing the self-service portal.
Device Service servers are required only in an on-premises deployment of Workspace ONE UEM.
Table 2: Workspace ONE UEM Device Services VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 60 GB |
Workspace ONE UEM Console Services Server
This server hosts the browser-based Workspace ONE UEM Console that administrators use to secure, configure, monitor, and manage their environment.
Console Service servers are required only in an on-premises deployment of Workspace ONE UEM.
Table 3: Workspace ONE UEM Console Services VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 60 GB |
Workspace ONE UEM Memcached Server
Recommended for deployments that include more than 5,000 devices, this cache server stores information from the database to reduce the volume of calls made directly to the database server.
Memcached servers are an optional component in an on-premises deployment of Workspace ONE UEM.
Table 4: Workspace ONE UEM Memcached Server VM Specifications
| Attribute | Specification |
| OS | CentOS 7.4-1708 |
| vCPU | 2 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 60 GB |
Workspace ONE UEM AWCM Server
The AirWatch Cloud Messaging (AWCM) server is used by the AirWatch Cloud Connector to communicate with the Workspace ONE UEM console.
AWCM servers are an optional component in an on-premises deployment of Workspace ONE UEM.
Table 5: Workspace ONE UEM AWCM VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 60 GB |
Workspace ONE UEM API Server
This server hosts the REST (Representational State Transfer) and SOAP (Simple Object Access Protocol) APIs that developers can use to integrate their own applications with Workspace ONE UEM.
API servers are an optional component in an on-premises deployment of Workspace ONE UEM.
Table 6: Workspace ONE UEM API Server VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 60 GB |
SQL Server for Workspace ONE UEM
This database server stores all device and environment data for Workspace ONE UEM and is required only for an on-premises deployment of Workspace ONE UEM.
Table 7: SQL Server for Workspace ONE UEM VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 8 |
| vMemory | 64 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:0 Windows OS 50 GB Scsi0:1 Database Disk 500 GB Scsi0:2 Log Disk 200 GB Scsi0:3 Temp Disk 200 GB |
Workspace ONE Access
Depending on the scale of the environment and the number of devices to be supported, the recommend resources allocated to each an Omnissa Workspace ONE Access and an Omnissa Workspace ONE Access Connector VMs can differ. For this reference architecture, a 50,000-device deployment was considered. See Workspace ONE Access Architecture for guidance on sizing for different numbers of devices.
Workspace ONE Access Connector Server
The Workspace ONE Access Connector is responsible for directory synchronization and authentication between on-premises resources such as Active Directory, Horizon, and the Workspace ONE Access service.
The Workspace ONE Access Connector can be used in both cloud-based and on-premises deployments of Workspace ONE Access.
Table 8: Workspace ONE Access Connector VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:0 Windows OS 100 GB |
Workspace ONE Access Appliance
This server hosts the Workspace ONE Access service, which provides the app catalog, conditional access, and single sign-on.
Workspace ONE Access appliances are required only in an on-premises deployment of Workspace ONE Access.
Table 9: Workspace ONE Access Appliance VM Specifications
| Attribute | Specification |
| OS | Photon OS |
| vCPU | 8 |
| vMemory | 16 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | LSI Logic Parallel |
SQL Server for Workspace ONE Access
This database server stores Workspace ONE Access data and is required only for an on-premises deployment of Workspace ONE Access.
Table 10: SQL Server for Workspace ONE Access VM Specifications
| Attribute | Specification |
| Version | SQL Server |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 16 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:0 Windows OS 100 GB |
Workspace ONE Intelligence
Omnissa Workspace ONE Intelligence is designed to simplify user experience without compromising security. The intelligence service aggregates and correlates data from multiple sources to give complete visibility into the entire environment. Workspace ONE Intelligence requires its own connector server.
Intelligence Collection Service - ETL Connector Server
This server hosts the ETL (Extract, Transform, Load) service responsible for collecting data from the Workspace ONE database and feeding it to the Workspace ONE Intelligence cloud service.
Table 11: Intelligence Collection Service (ETL) Connector VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 100 GB |
Workspace ONE Assist
Omnissa Workspace ONE Assist allows Workspace ONE UEM administrators to remotely access and troubleshoot devices in real time while respecting end-user privacy. Screen-sharing capabilities allow remote devices to screen share and relinquish device controls to an administrator for guided support. Administrators can also access the remote file system and can use run commands to remotely send commands to the device.
Workspace ONE Assist All-in One Server
This server hosts the Core, Application, Portal, and Connection Proctor components on a single server. All Workspace ONE Assist Core Service servers, Connection Proctor servers, and remote management registration details persist and reside in a Microsoft SQL Server database.
Note: You may use the same Microsoft SQL Server that supports your Workspace ONE UEM deployment for your Workspace ONE Assist deployment. For VM specifications, see SQL Server for Workspace ONE UEM.
Table 12: Workspace ONE Assist All-in One Server VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 16 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 70 GB |
Horizon 8
Several servers are required to take advantage of all features in an Omnissa Horizon 8 deployment.
Horizon Connection Server
This server acts as a broker for client connections. It authenticates users through Windows Active Directory and directs the request to the appropriate virtual machine, physical PC, or Microsoft RDSH server.
Table 13: Horizon Connection Server VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 12 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 100 GB |
Horizon Enrollment Server
The enrollment server is required for the Horizon True SSO feature.
Table 14: Horizon Enrollment Server VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 4 |
| vMemory | 12 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 100 GB |
SQL Server for Horizon
SQL Server is used for the Connection Server event database, the Composer database, and the App Volumes database.
Table 16: SQL Server for Horizon VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 2 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:0 Windows OS 50 GB Scsi0:1 Data Disk 50 GB |
App Volumes
For Omnissa App Volumes you deploy a VM that hosts the App Volumes Manager server.
App Volumes Manager Server
Table 17: App Volumes Manager VM Specifications
| Attribute | Specification |
| OS | Windows Server |
| vCPU | 2 |
| vMemory | 8 GB |
| vNICs | 1 |
| Virtual network adapter 1 | VMXNET3 Adapter |
| Virtual SCSI controller 0 | Paravirtual |
| Virtual disk – VMDK (scsi0:x) | Scsi0:1 Windows OS 100 GB |
Summary and Additional Resources
Now that you have come to the end of this chapter, you can return to the reference architecture landing page and use the tabs, search, or scroll to select further chapter in one of the following sections:
- Overview chapters provide understanding of business drivers, use cases, and service definitions.
- Architecture chapters give design guidance on the Omnissa products you are interested in including in your deployment, including Workspace ONE UEM, Access, Intelligence, Workspace ONE Assist, Horizon Cloud Service, Horizon 8, App Volumes, Dynamic Environment Manager, and Unified Access Gateway.
- Integration chapters cover the integration of products, components, and services you need to create the environment capable of delivering the services that you want to deliver to your users.
- Configuration chapters provide reference for specific tasks as you deploy your environment, such as installation, deployment, and configuration processes for Omnissa Workspace ONE, Horizon Cloud Service, Horizon 8, App Volumes, Dynamic Environment Management, and more.
Additional Resources
For more information about VM specifications, you can explore the following resources:
Changelog
The following updates were made to this guide:
| Date | Description of Changes |
| 2024-05-28 |
|
| 2023-07-24 |
|
Author and Contributors
This chapter was written by:
- Graeme Gordon, Senior Staff Architect, Omnissa.
Feedback
Your feedback is valuable. To comment on this paper, either use the feedback button or contact us at tech_content_feedback@omnissa.com.