VMware Workspace ONE and Horizon Reference Architecture Overview

This chapter is one of a series that make up the VMware Workspace ONE and VMware Horizon Reference Architecture, a framework that provides guidance on the architecture, design considerations, and deployment of Workspace ONE and Horizon solutions. This chapter includes an executive summary, information about VMware reference architectures, an overview of VMware Workspace ONE and VMware Horizon, architectural overviews and diagrams, general multi-site best practices, a list of authors and contributors for the various chapters of the reference architecture, and a changelog.

In subsequent chapters of this book, design guidance is given for each product—with a corresponding architecture chapter devoted to each product—followed by best practices for integrating the components into a complete platform. For validation, we built an example environment. Throughout this book, we listed the design decisions made for this example environment, along with the rationale for each decision and descriptions of design considerations.

Executive Summary

Use this reference architecture as you build services to create an integrated digital workspace that addresses your unique business requirements and use cases. You will integrate the components of VMware Workspace ONE, including VMware Horizon and VMware Horizon Cloud on Microsoft Azure.

Workspace ONE combines identity and mobility management to provide frictionless and secure access to all the apps and data that employees need to do their work, wherever, whenever, and from whatever device they choose. Mobile device and identity services are delivered through VMware Workspace ONE Unified Endpoint Management (UEM), powered by AirWatch, and VMware Workspace ONE Access (formerly called VMware Identity Manager).

Additionally, Workspace ONE integrates with VMware Horizon virtual desktops and published applications delivered through Horizon and Horizon Cloud on Microsoft Azure. This integration provides fast single-sign-on (SSO) access to a Windows desktop or set of Windows applications for people who use the service.

Figure 1: User Workspace with VMware Workspace ONE

The example architecture and deployment described in this guide address key business drivers. The approach taken is, as with any technology solution, to start by defining those business drivers and then identify use cases that need to be addressed. Each use case will entail a set of requirements that need to be fulfilled to satisfy the use case and its respective business drivers.

Once the requirements are understood, the solutions can be defined, and blueprints outlined for the services to be delivered. This step allows you to identify and understand the products, components, and parts that need to be designed, built, and integrated.

Figure 2: Design Approach

To deliver a Workspace ONE and Horizon solution, you build services efficiently from several reusable components. This modular, repeatable design approach combines components and services to customize the end-user experience without requiring specific configurations for individual users. The resultant environment and services can be easily adapted to address changes in the business and use case requirements.

Figure 3: Sample Service Blueprint

This reference architecture underwent validation of design, environment adaptation, component and service build, integration, user workflow, and testing to ensure that all the objectives were met, that the use cases were delivered properly, and that real-world application is achievable.

This VMware Workspace ONE and VMware Horizon Reference Architecture illustrates how to architect and deliver a modern digital workspace that meets key business requirements and common use cases for the increasingly mobile workplace, using Workspace ONE and Horizon.

VMware Reference Architectures

VMware reference architectures are designed and validated by VMware to address common use cases, such as enterprise mobility management, enterprise desktop replacement, remote access, and disaster recovery.

This Workspace ONE and Horizon reference architecture is a framework intended to provide guidance on how to architect and deploy Workspace ONE and Horizon solutions. It presents high-level design and low-level configuration guidance for the key features and integration points of Workspace ONE and Horizon. The result is a description of cohesive services that address typical business use cases.

VMware reference architectures offer customers:

  • Standardized, validated, repeatable components
  • Scalable designs that allow room for future growth
  • Validated and tested designs that minimize implementation and operational risks
  • Quick implementation and reduced costs

This reference architecture does not provide performance data or stress-testing metrics. However, it does provide a structure and guidance on architecting in repeatable blocks for scale. The principles followed include the use of high availability and load balancing to ensure that there are no single points of failure and to provide a production-ready design.

Audience

This reference architecture helps IT architects, consultants, and administrators involved in the early phases of planning, designing, and deploying Workspace ONE, VMware Horizon, and VMware Horizon Cloud Service solutions.

You should have:

  • A solid understanding of the mobile device landscape
  • Deep experience regarding the capabilities and configuration of mobile operating systems
  • Familiarity with device-management concepts
  • Knowledge of identity solutions and standards, such as SAML authentication
  • Understanding of enterprise communication and collaboration solutions, including Microsoft Office 365, Exchange, and SharePoint
  • A good understanding of virtualization, in particular any platform used to host services such as VMware vSphere or Microsoft Azure.
  • A solid understanding of desktop and application virtualization
  • A solid understanding of firewall policy and load-balancing configurations
  • A good working knowledge of networking and infrastructure, covering topics such as Active Directory, DNS, and DHCP

Design Methodology

To ensure a successful Workspace ONE and Horizon deployment, it is important to follow proper design methodology. To start, you need to understand the business requirements, reasons, and objectives for undertaking the project. From there, you can identify the needs of the users and organize these needs into use cases with understood requirements. You can then align and map those use cases to a set of integrated services provided by Workspace ONE and Horizon.

Figure 4: Reference Architecture Design Methodology

A Workspace ONE and Horizon design uses a number of components to provide the services that address the identified use cases. Before you can assemble and integrate these components to form a service, you must first design and build the components in a modular and scalable manner to allow for change and growth. You also must consider integration into the existing environment. Then you can bring the parts together to deliver the integrated services to satisfy the use cases, business requirements, and the user experience.

As with any design process, the steps are cyclical, and any previous decision should be revisited to make sure a subsequent one has not impacted it.

Design Tools

The VMware Digital Workspace Designer is a companion and aid for planning and sizing a Workspace ONE and Horizon deployment, maintaining current VMware best practices and assisting you with key design decisions. The tool is aimed at establishing an initial high-level design for any planned deployment and is intended to complement a proper planning and design process.

The VMware Digital Workspace Topology Tool allows you to create a logical architectural diagram by selecting the Workspace ONE and Horizon components. It generates a diagram that shows the selected components and the links between them. The Topology Tool can also be also launched from the Digital Workspace Designer to automatically create an architectural diagram with the components generated as part of a design. Both tools can be found https://techzone.vmware.com/tools.

Design Decisions

As part of the creation of this reference architecture, full environments are designed, built, and tested. Throughout the chapters of this book, design decisions are listed that describe the choices we made for our implementation.

Table 1: Design Decision Regarding the Purpose of This Reference Architecture

Decision

Full production-ready environments were architected, deployed, and tested.

Justification

This allows the content of this guide, including the design, deployment, integration, and delivery, to be verified, validated, and documented.

Each implementation of Workspace ONE and Horizon is unique and will pose distinct requirements. The implementation followed in this reference architecture tries to address the common use cases, decisions, and challenges that need to be addressed in a manner that can be adapted to differing circumstances.

Workspace ONE and Horizon Overview

VMware Workspace ONE is a simple and secure enterprise platform that delivers and manages any app on any device. Workspace ONE integrates identity, application, and enterprise mobility management while also delivering feature-rich virtual desktops and applications. It is available either as a cloud service or for on-premises deployment. The platform is composed of several components—VMware Workspace ONE UEM (powered by VMware AirWatch), Workspace ONE Access, VMware Horizon, and the Workspace ONE productivity apps, which are supported on most common mobile platforms.

Workspace ONE

Workspace ONE features provide enterprise-class security without sacrificing convenience and choice for end users:

  • Real-time app delivery and automation – Taking advantage of new capabilities in Windows, Workspace ONE allows desktop administrators to automate application distribution and updates. This automation, combined with virtualization technology, helps ensure application access as well as improve security and compliance. Provision, deliver, update, and retire applications in real time.
  • Self-service access to cloud, mobile, and Windows apps – After end users are authenticated through either the Workspace ONE app or the VMware Workspace ONE® Intelligent Hub app, they can instantly access mobile, cloud, and Windows applications with one-touch mobile single sign-on (SSO).
  • Choice of any device, employee or corporate owned – Administrators can facilitate adoption of bring-your-own-device (BYOD) programs by putting choice in the hands of end users. Give the level of convenience, access, security, and management that makes sense for their work style.
  • Device enrollment – The enrollment process allows a device to be managed in a Workspace ONE UEM environment so that device profiles and applications can be distributed and content can be delivered or removed. Enrollment also allows extensive reporting based on the device’s check-in to the Workspace ONE UEM service.
  • Adaptive management – For some applications, end users can log in to Workspace ONE and access the applications without first enrolling their device. For other applications, device enrollment is required, and the Workspace ONE app can prompt the user to initiate enrollment.

Administrators can enable flexible application access policies, allowing some applications to be used prior to enrollment in device management, while requiring full enrollment for apps that need higher levels of security.

  • Conditional access – Both Workspace ONE Access and Workspace ONE UEM have mechanisms to evaluate compliance. When users register their devices with Workspace ONE, data samples from the device are sent to the Workspace ONE UEM cloud service on a scheduled basis to evaluate compliance. This regular evaluation ensures that the device meets the compliance rules set by the administrator in the Workspace ONE UEM Console. If the device goes out of compliance, corresponding actions configured in the Workspace ONE UEM Console are taken.

Workspace ONE Access includes an access policy option that administrators can configure to check the Workspace ONE UEM server for device compliance status when users sign in. The compliance check ensures that users are blocked from signing in to an application or using SSO to the Workspace ONE Access self-service catalog if the device is out of compliance. When the device is compliant again, the ability to sign in is restored.

Actions can be enforced based on the network that users are on, the platform they are using, or the applications being accessed. In addition to checking Workspace ONE UEM for device compliance, Workspace ONE Access can evaluate compliance based on network range of the device, type of device, operating system of the device, and credentials.

  • Unified application catalog – The Workspace ONE Access and Workspace ONE UEM application catalogs are combined and presented on either the Workspace ONE app’s Catalog tab or the VMware Workspace ONE Intelligent Hub app, depending on which is being used.
  • Secure productivity apps - VMware Workspace ONE Boxer, Web, Content, Notebook, People, Verify, and PIV-D Manager – End users can use the included mail, calendar, contacts, browser, content, organization, and authentication capabilities, while policy-based security measures protect the organization from data leakage by restricting the ways in which attachments and files are edited and shared.
  • Mobile SSO – One-touch SSO technology is available for all supported platforms. The implementation on each OS is based on features provided by the underlying OS. For iOS, one-touch SSO uses technology known as the key distribution center (KDC). For Android, the authentication method is called mobile SSO for Android. And for Windows 10, it is called cloud certificate.
  • Secure browsing – Using VMware Workspace ONE Web instead of a native browser or third-party browser ensures that access to sensitive web content is secure and manageable.
  • Data loss prevention (DLP) – This feature forces documents or URLs to open only in approved applications to prevent accidental or purposeful distribution of sensitive information.
  • Resource types – Workspace ONE supports a variety of applications exposed through the Workspace ONE Access and Workspace ONE UEM catalogs, including SaaS-based SAML apps, VMware Horizon apps and desktops, Citrix virtual apps and desktops, VMware ThinApp packaged apps delivered through Workspace ONE Access, and native mobile applications delivered through Workspace ONE UEM.

Workspace ONE Platform Integration

Workspace ONE UEM delivers the enterprise mobility management portion of the solution. Workspace ONE UEM allows device enrollment and uses profiles to enforce configuration settings and management of users’ devices. It also enables a mobile application catalog to publish public and internally developed applications to end users.

Workspace ONE Access provides the solution’s identity-related components. These components include authentication using username and password, two-factor authentication, certificate, Kerberos, mobile SSO, and inbound SAML from third-party Workspace ONE Access systems. Workspace ONE Access also provides SSO to entitled web apps and Windows apps and desktops delivered through either VMware Horizon or Citrix.

Figure 1: Workspace ONE Logical Architecture Overview

Workspace ONE Intelligence

VMware Workspace ONE Intelligence is a service that gives organizations visualization tools and automation to help them make data-driven decisions for operating their Workspace ONE environment.

By aggregating, analyzing, and correlating device, application, and user data, Workspace ONE Intelligence provides extensive ways to filter and reveal key performance indicators (KPIs) at speed and scale across the entire digital workspace environment. After information of interest has been surfaced by Workspace ONE Intelligence, IT administrators can:

  • Use the built-in decision engine to create rules that take actions based on an extensive set of parameters.
  • Create policies that take automated remediation actions based on context.

With Workspace ONE Intelligence, organizations can easily manage complexity and security without compromising a great user experience.

Figure 2: Workspace ONE Intelligence Overview

Horizon

With Horizon, VMware offers simplicity, security, speed, and scale in delivering on-premises virtual desktops and applications with cloud-like economics and elasticity of scale.  With this latest release, customers can now enjoy key features such as:

JMP allows components of a desktop or RDSH server to be decoupled and managed independently in a centralized manner, yet reconstituted on demand to deliver a personalized user workspace when needed. JMP is supported with both on-premises and cloud-based Horizon deployments, providing a unified and consistent management platform regardless of your deployment topology. The JMP approach provides several key benefits, including simplified desktop and RDSH image management, faster delivery and maintenance of applications, and elimination of the need to manage “full persistent” desktops.

  • JMP (Next-Generation Desktop and Application Delivery Platform) – JMP (pronounced jump), which stands for Just-in-Time Management Platform, represents capabilities in VMware Horizon that deliver Just-in-Time Desktops and Apps in a flexible, fast, and personalized manner. JMP is composed of the following VMware technologies:
    • VMware Instant Clone Technology for fast desktop and RDSH provisioning
    • VMware App Volumes for real-time application delivery
    • VMware Dynamic Environment Manager for contextual policy management
  • Just-in-Time Desktops – Leverages Instant Clone Technology coupled with App Volumes to accelerate the delivery of user-customized and fully personalized desktops. Dramatically reduce infrastructure requirements while enhancing security by delivering a brand-new personalized desktop and application services to end users every time they log in.
    • Reap the economic benefits of stateless, nonpersistent virtual desktops served up to date upon each login.
    • Deliver a pristine, high-performance personalized desktop every time a user logs in.
    • Improve security by destroying desktops every time a user logs out.
  • App Volumes – Provides real-time application delivery and management.
    • Quickly provision applications at scale.
    • Dynamically attach applications to users, groups, or devices, even when users are already logged in to their desktop.
    • Provision, deliver, update, and retire applications in real time.
    • Provide a user-writable volume, allowing users to install applications that follow them across desktops.
  • Dynamic Environment Manager – Offers personalization and dynamic policy configuration across any virtual, physical, and cloud-based environment.
    • Provide end users with quick access to a Windows workspace and applications, with a personalized and consistent experience across devices and locations.
    • Simplify end-user profile management by providing organizations with a single and scalable solution that leverages the existing infrastructure.
    • Speed up the login process by applying configuration and environment settings in an asynchronous process instead of all at login.
    • Provide a dynamic environment configuration, such as drive or printer mappings, when a user launches an application.

Horizon Cloud on Microsoft Azure

Horizon Cloud on Microsoft Azure provides customers with the ability to pair their existing Microsoft Azure infrastructure with the Horizon Cloud Service to deliver feature-rich virtual desktops and applications.

Horizon Cloud uses a purpose-built cloud platform that is scalable across multiple deployment options, including fully managed infrastructure from VMware and public cloud infrastructure from Microsoft Azure. The service supports a cloud-scale architecture that makes it easy to deliver virtualized Windows desktops and applications to any device, anytime.

Figure 3: Horizon Cloud Service on Microsoft Azure Overview

Architectural Overview

A VMware Workspace ONE® design uses several complementary components and provides a variety of highly available services to address the identified use cases. Before you can assemble and integrate these components to form the desired service, you first need to design and build the infrastructure required.

The components in Workspace ONE, such as Workspace ONE Access™, VMware Workspace ONE® UEM (powered by VMware AirWatch®), and VMware Horizon® are available as on-premises and cloud-hosted products.

For this reference architecture, both cloud-hosted and on-premises Workspace ONE UEM and Workspace ONE Access are used separately to prove the functionality of both approaches. These are shown in the cloud-based and on-Premises logical architecture designs described in this chapter.

Note that other components, such as VMware Horizon® or VMware Horizon® Cloud Service™ on Microsoft Azure, can be combined with either a cloud-based or an on-premises Workspace ONE deployment.

Workspace ONE Logical Architecture

The Workspace ONE platform is composed of Workspace ONE Access and Workspace ONE UEM. Although each product can operate independently, integrating them is what enables the Workspace ONE product to function.

Workspace ONE Access and Workspace ONE UEM provide tight integration between identity and device management. This integration has been simplified in recent versions to ensure that configuration of each product is relatively straightforward.

Although Workspace ONE Access and Workspace ONE UEM are the core components in a Workspace ONE deployment, you can deploy a variety of other components, depending on your business use cases. For example, and as shown in the figure in the next section, you can use VMware Unified Access Gateway™ to provide the VMware Workspace ONE® Tunnel or VPN-based access to on-premises resources.

For more information about the full range of components that might apply to a deployment, refer to the VMware Workspace ONE UEM documentation.

Cloud-Based Logical Architecture

With a cloud-based architecture, Workspace ONE is consumed as a service requiring little or no infrastructure on-premises.

  • VMware Workspace ONE UEM SaaS tenant – Cloud-hosted instance of the Workspace ONE UEM service. Workspace ONE UEM acts as the mobile device management (MDM), mobile content management (MCM), and mobile application management (MAM) platform.
  • Workspace ONE Access SaaS tenant – Cloud-hosted instance of Workspace ONE Access. Workspace ONE Access acts as an identity provider by syncing with Active Directory to provide single sign-on (SSO) across SAML-based applications, VMware Horizon–based apps and desktops, and VMware ThinApp® packaged apps. It is also responsible for enforcing authentication policy based on networks, applications, or platforms.

Figure 4: Sample Workspace ONE Cloud-Based Logical Architecture

On-Premises Logical Architecture

With an on-premises deployment of Workspace ONE, both Workspace ONE UEM and Workspace ONE Access are deployed in your data centers.

  • VMware Workspace ONE UEM – On-premises installation of Workspace ONE UEM. Workspace ONE UEM consists of several core components, which can be installed on a single server. Workspace ONE UEM acts as the MDM, MCM, and MAM platform.
  • Workspace ONE Access – Acts as an identity provider by syncing with Active Directory to provide SSO across SAML-based applications, VMware Horizon–based applications and desktops, and VMware ThinApp packaged apps. Workspace ONE Access is also responsible for enforcing authentication policy based on networks, applications, or platforms.

Figure 5: Workspace ONE Sample On-Premises Logical Architecture

Common Components

A number of optional components in a Workspace ONE deployment are common to both a cloud-based and an on-premises deployment.

  • AirWatch Cloud Connector (ACC) – Runs in the internal network, acting as a proxy that securely transmits requests from Workspace ONE UEM to the organization’s critical backend enterprise infrastructure components. Organizations can leverage the benefits of Workspace ONE® UEM MDM, running in any configuration, together with those of their existing LDAP, certificate authority, email, and other internal systems.
  • Workspace ONE Access Connector – Performs directory sync and authentication between an on-premises Active Directory and the Workspace ONE Access service.
  • VMware Unified Access Gateway – Virtual appliance that provides secure edge services and allows external access to internal resources.

Horizon Virtual Desktops and Published Applications

Both Horizon and Horizon Cloud Service can be combined and integrated into a Workspace ONE deployment, regardless of whether you use a cloud-based or on-premises deployment.

  • Horizon – Manages and delivers virtualized or hosted desktops and applications to end users.
    • Connection Servers – Broker instances that securely connect users to desktops and published applications running on VMware vSphere® VMs, physical PCs, blade PCs, or RDSH servers. Connection Servers authenticate users through Windows Active Directory and direct the request to the appropriate and entitled resource.
    • Horizon Administrative Console – An administrative console that allows configuration, deployment, management, and entitlement of users to resources.
  • Horizon Cloud Service – A multi-tenant, cloud-scale architecture that enables you to choose where virtual desktops and apps reside: VMware-managed cloud, BYO cloud, or both.
    • Horizon Cloud Control Plane – A control plane that VMware hosts in the cloud for central orchestration and management of VDI desktops, RDSH-published desktops, and RDSH-published applications. Because VMware hosts the service, feature updates and enhancements are consistently provided for a software-as-a-service experience.
    • Horizon Cloud Administration Console – The cloud control plane also hosts a common management user interface, which runs in industry-standard browsers. This console provides IT administrators with a single location for management tasks involving user assignments to and management of VDI desktops, RDSH-published desktops, and RDSH-published applications.
    • Horizon Cloud pod – VMware software deployed to a supported capacity environment, such as Microsoft Azure cloud. Along with access to the Horizon Cloud Administration Console, the service includes the software necessary to pair the deployed pod with the cloud control plane and deliver virtual desktops and applications.

General Multi-site Best Practices 

There are numerous ways to implement a disaster recovery architecture, but some items can be considered general best practices.

Components That Must Always Run with a Primary Instance

Even with an active/active usage model across two data centers, meaning that the service is available from both data centers without manual intervention, one of the data centers may hold the primary active instance for some services, while the second site holds a secondary passive instance. The following components must run with a primary instance in a given site: 

  • On-premises Workspace ONE UEM
  • On-premises Workspace ONE Access
  • User profile and data shares containing VMware Dynamic Environment Manager™ (formerly called User Environment Manager) user data
  • Microsoft Active Directory flexible single master operations (FSMO) roles, specifically, Primary Domain Controller (PDC) Emulator, because it is required to make changes to domain-based DFS namespaces
  • Microsoft SQL Server Always On availability groups (if used)

Be sure to secure those resources that are primary and secondary by nature or that cannot be failed over automatically. Procedures must be put in place to define the steps required to recover these resources.

For this reference architecture design, we chose to place the primary availability group member in Site 1 as well as all AD FSMO roles on a domain controller. We made this choice because we had a good understanding of the failover steps required if either Site 1 or Site 2 failed.

Component Replication and Traveling Users

Use Workspace ONE and Horizon components to create effective replication strategies and address the needs of users who travel between sites:

  • Create a disaster plan up front that defines what a disaster means in your organization. The plan should specify whether you require a 1:1 mapping in terms of resources, or what portion of the workforce is required to keep the organization operational.
  • Understand what user data will need to be replicated between sites to allows users to be productive. The quantity, speed, and frequency of replication will affect the time it takes to present a complete service to a user from another site.
  • Replicate Horizon desktop and server (RDSH) golden image templates between sites to avoid having to build the same templates on both sites. You can use a vSphere content library or perform a manual replication of the resources needed across the whole implementation.
  • With Horizon, use Cloud Pod Architecture and avoid using a metro-cluster with VMware vSAN™ stretched cluster unless you have a persistent desktop model in the organization that cannot easily be transformed into a nonpersistent-desktop use case.
  • With regard to initial user placement, even with a traveling worker use case, a given user must be related to user profile data (Dynamic Environment Manager user data), meaning that a relationship must be established between a user account and a data center. This also holds true when planning how users in the same part of the organization (such as sales) should be split between sites to avoid an entire function of the company being unable to work should a disaster strike.
  • For a traveling worker use case, where Dynamic Environment Manager is used to control the user profile data, VMware recommends that FlexEngine be used whenever possible in combination with folder redirection. This keeps the core profile to a minimum size and optimizes login times in the case where a profile is loaded across the link between the two data centers.
  • Use Microsoft SQL Server failover cluster instances and Always On availability groups for on-premises Workspace ONE UEM and Workspace ONE Access where possible. This is not required for VMware vCenter Server®, the Connection Server event database, and VMware vSphere® Update Manager™.

Authors and Contributors

This book was originally written and recently updated by:

  • Graeme Gordon is a Senior Staff End-User-Computing (EUC) Architect in End-User-Computing Technical Marketing, VMware.
  • Andreano Lanusse is a Staff End-User-Computing (EUC) Architect in End-User-Computing Technical Marketing, VMware.
  • Caroline Arakelian is a Senior Technical Marketing Manager in End-User-Computing Technical Marketing, VMware.
  • Chris Halstead is a Senior Staff End-User-Computing (EUC) Architect in End-User-Computing Technical Marketing, VMware.
  • Christina Minihan is a Senior Technical Marketing Architect in End-User-Computing Technical Marketing, VMware.
  • Daniel Berkowitz is a Senior End-User-Computing (EUC) Architect in in End-User-Computing Field Engineering, VMware.
  • Donal Geary is a Reference Architect Engineer in End-User-Computing Technical Marketing, VMware.
  • Hilko Lantinga is a Staff End User Computing Architect in End-User-Computing Technical Marketing, VMware.
  • Josh Spencer is a Senior Product Line Manager, End User Computing, VMware.
  • Justin Sheets is a Senior Technical Marketing Architect in End-User-Computing Technical Marketing, VMware.
  • Karim Chelouati is a Senior Product Marketing Manager, VMware.
  • Mike Erb is a Senior Solution Architect in End-User-Computing Field Engineering, VMware.
  • Peter Bjork is a Principal End-User-Computing (EUC) Architect, VMware.
  • Pim van de Vis is a Senior Solutions Architect in End-User Computing, VMware.
  • Rick Terlep is a Senior Technical Marketing Architect in End-User-Computing Technical Marketing, VMware.
  • Roger Deane is VMware alumni.
  • Sascha Warno is a Staff End User Computing Architect in End-User-Computing Technical Marketing, VMware

The following people contributed to content in previous guides whose content has been subsumed into this book:

  • Adarsh Kesari, Staff Solutions Engineer in End-User-Computing, VMware
  • Camilo Lotero, Senior Solution Engineer in End-User-Computing, VMware
  • Shardul Navare, Senior Technical Marketing Architect in End-User-Computing Technical Marketing, VMware

To comment on this paper, contact VMware End-User-Computing Technical Marketing at euc_tech_content_feedback@vmware.com.

Changelog

The following updates were made to this book:

DATE

CHANGES

2021-11-29
2021-09-30

Horizon Control Plane Services Architecture

Horizon Cloud on Microsoft Azure Architecture

Workspace ONE Assist Architecture

2021-07-20
2021-07-14
  • Added extra detail to Horizon Use Cases on combining access to Windows and Linux applications while using a macOS device.
2021-06-01
  • Fixed diagram and details in the Multi-Site Design section of Horizon Cloud on Microsoft Azure Architecture
2021-05-25
2021-05-21
  • Added link in App Volumes Architecture to guide on database best practices.
  • Corrected Storage heading in App Volumes Architecture to make it a level one heading.
  • Added details relative to feature enhancements for Universal Broker added on 20 May 2021.
2021-05-06
2021-04-02
  • Added content on configuration of Universal Broker and Multi-Cloud Assignments to Horizon Configuration chapter and re-ordered content on Cloud Pod Architecture configuration.
2021-04-01
2021-01-27
  • Updated section on load balancing for App Volumes to include more up-to-date settings. Added link to the VMware NSX Advanced Load Balancer (Avi) guide on how to implement.
2020-12-17
2020-12-16

2020-11-18

2020-07-01

Workspace ONE UEM

  • Added a new section, “BYOD and Mobile Application Management (MAM),” to the Workspace ONE Architecture chapter.
  • Added a new section, “Using Intelligent Hub and Workspace ONE Apps on Devices That Are Not Fully Managed,” to Workspace ONE UEM Configuration.

Workspace ONE Intelligence

  • Added information about risk analytics.
  • Updated app analytics with information about the Workspace ONE Intelligence SDK.

Unified Access Gateway

  • Updated sizing guidance.
  • Recommend using Per-App Tunnel instead of Tunnel Proxy.

Horizon Cloud Service on Microsoft Azure

  • Greatly expanded the “Network Design” section, with multiple scenarios and network diagrams to describe how Horizon Cloud Service on Microsoft Azure supports the Microsoft Azure network architectures, including the Hub-spoke network topology.
  • Rewrote the “Scalability and Availability” section.
  • Added a new section, “Single-Site Design.”

Dynamic Environment Manager

  • Updated Dynamic Environment Manager from version 9.6 to 9.11.
  • Added a new chapter on Dynamic Environment Manager Configuration.

App Volumes

  • Updated App Volumes from version 2.x to App Volumes 4.
  • Added a new section, “Replicate Application Packages and Reconstruct Relationships and Entitlements,” to App Volumes Configuration.

Environment infrastructure

  • Added information about the VMware NSX Advanced Load Balancer (formerly Avi Vantage by Avi Networks).

Platform integration

  • Updated Workspace ONE Access integration details for some products
  • Added a new chapter, “Horizon Control Plane.”

2020-04-29

  • Updated Workspace ONE Access to version 20.01 and the Workspace ONE Access Connector to version 19.03. Previously, both used version 3.x.

2020-03-10

 

  • Removed mention of Windows mandatory profiles from the Service Integration Design chapter. This feature does not work reliably when used with Windows 10 version 1809 and later.

2020-02-27

  • New architecture chapter for VMware Workspace ONE Assist
  • Unified Access Gateway additions:
  • Support for Secure Email Gateway (SEG)
  • New XL sizing option for SEG
  • SAML authentication for Horizon
  • Add HA for ETL Connector for Workspace ONE Intelligence
  • Rename VMware Identity Manager to Workspace ONE Access
  • Rename User Environment Manager to Dynamic Environment Manager

What’s Next

Now that you have come to the end of this chapter, you can return to the landing page and search or scroll to select your next chapter in one of the following sections:

  • Overview chapters provide understanding of business drivers, use cases, and service definitions.
  • Architecture chapters explore the products you are interested in including in your platform, including Workspace ONE UEM, Workspace ONE Access, Workspace ONE Assist, Workspace ONE Intelligence, Horizon, App Volumes Dynamic Environment Manager, and Unified Access Gateway.
  • Integration chapters cover the integration of components and services you need to create the platform capable of delivering what you want.
  • Configuration chapters provide reference for specific tasks as you build your platform, such as installation, deployment, and configuration processes for Horizon, App Volumes, Dynamic Environment Management, and more.

Filter Tags

Horizon Workspace ONE Document Reference Architecture Overview Design