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.

Table 1: AirWatch Cloud Connector VM specifications

Omnissa Access (formerly 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 Access and 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.

Omnissa Access Connector server

The Omnissa Access Connector is responsible for directory synchronization and authentication between on-premises resources such as Active Directory, Horizon, and the Access service.

The Access Connector can be used in both cloud-based and on-premises deployments of Omnissa Access.

Table 8: Access Connector VM specifications

Omnissa Access appliance

This server hosts the Access service, which provides the app catalog, conditional access, and single sign-on. Access appliances are required only in an on-premises deployment of Access.

Table 9: Access appliance VM specifications

SQL Server for Omnissa Access

This database server stores Omnissa Access data and is required only for on-premises deployments of Access.

Table 10: SQL Server for Omnissa Access VM specifications

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. The ETL Connector Server is only required when connecting an on-premises deployment of Workspace ONE UEM with Intelligence.

Table 11: Intelligence Collection Service (ETL) Connector VM specifications

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

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

Horizon Enrollment server

The enrollment server is required for the Horizon True SSO feature.

Table 14: Horizon Enrollment Server VM specifications

SQL Server for Horizon 8

SQL Server is used for the Connection Server event database, the Composer database, and the App Volumes database.

Table 16: SQL Server for Horizon 8 VM specifications

App Volumes

For Omnissa App Volumes you deploy a VM that hosts the App Volumes Manager.

App Volumes Manager server

Table 17: App Volumes Manager VM specifications

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:

• Product documentation
• Omnissa knowledge base

Changelog

The following updates were made to this guide:

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.