This Administration Guide explains how to use VMware Horizon® Cloud Service™ to administer the pods you have onboarded to the cloud service. Your overall Horizon Cloud tenant environment consists of the VMware-hosted cloud service and your pods deployed into their corresponding capacity environments and connected to the cloud service. To work with your tenant environment's fleet of cloud-connected pods and the desktop-as-a-service features that the service provides, you log in to and use the tenant environment's portal, known as the Horizon Cloud Administration Console.

The VMware Horizon services encompass various deployment modes. This document applies when you are using the Horizon Cloud Administration Console to work with the following items:

  • VMware Horizon® 7 pods that you installed on-premises and then connected to Horizon Cloud
  • VMware Horizon 7 pods that you manually installed in your VMware Cloud™ on AWS SDDC and then connected to Horizon Cloud.
  • Pods in your Microsoft Azure cloud capacity that you automatically deployed and configured using Horizon Cloud

To find out more about all of the various Horizon Cloud deployment modes, see https://www.vmware.com/cloud-services/desktop.html.

For information about how VMware handles information collected through this product, click here: https://www.vmware.com/help/privacy.html

The information in this document describes how to use the Horizon Cloud capabilities after the cloud service is connected to one of the its supported environments: a VMware Horizon 7 pod in VMware Cloud, a VMware Horizon 7 pod on-premises, or a pod in Microsoft Azure. For information on how to connect a supported environment to the cloud service, see the Horizon Cloud Deployment Guide.

Important: This document describes features available in the Administration Console for the current release of the Horizon Cloud Service working with the connected environments. When you have pods that are not yet updated to the currently supported release level, you will not see all of the features that this document describes when those features depend on the latest pod software level. Also, in a particular release, Horizon Cloud might include separately licensed features. The Administration Console reflects the elements related to such features only when your license includes use of such features. When you are not seeing a feature in the Administration Console that you are expecting to see, contact your VMware account representative to verify whether your license entitles your use of that feature.

Document Revision History

This document, Horizon Cloud Administration Guide, is updated with each release of the product or when necessary.

This table provides the update history.

Revision Description
9 JUN 2020 Updates made to align this guide with the June 9, 2020 new items listed in the Release Notes for the service 3.0 release. The regional names that appear in the Welcome email have been updated to use human-friendly names. The following doc topic is also updated to align with that change: DNS Requirements for a Horizon Cloud Pod in Microsoft Azure
27 MAY 2020 Updates made to align this guide with the May 27, 2020 new items listed in the Release Notes for the service 3.0 release.
12 MAY 2020 Updates made to align this guide with the May 12, 2020 service updates listed in the Release Notes for the service 3.0 release. Also corrected entries in the table for agent-related ports and protocols requirements in doc topics Ports and Protocols Requirements for a Horizon Cloud Pod at the September 2019 Release's Manifest or Later and Ports and Protocols Requirements for a Horizon Cloud Pod Deployed Prior to the September 2019 Release.
5 MAY 2020 Added topic About External and Forest Trust Support for Cloud-Connected Pods in Horizon Cloud.
28 APR 2020 The following updates are made to the Administration Guide doc topics.
14 APR 2020 The following updates are made to the Administration Guide doc topics. See also the updated Release Notes for the service 3.0 release.
  • Removed the notes that said the automated Import VM from Marketplace wizard could not be used when the pod is configured with a proxy. The previous limitations that prevented the wizard's use when the pod is configured with a proxy have been addressed.
  • Added a note that even though the pod deployment wizard will display a choice for the Azure Germany cloud environment, support for that choice is discontinued because Microsoft now has German regions in their set of standard global regions and has sunsetted use of their separate Azure Germany cloud environment. See VMware Knowledge Base article 77121.
  • Updated the supported client information for Universal Broker.
17 MAR 2020 Initial version, when the described features were deployed live into production.

This document describes the latest service features.

  • For pods using Microsoft Azure capacity, some of the new features are agnostic to the pod manifest version that is newly made available at the time this service release went live into production, while some of the new features require that new pod manifest version for you to take advantage of those features. See the Release Notes for the service 3.0 release for the pod manifest version that corresponds with this service release and for the list of new features that require that latest pod manifest version.

    For cloud-connected Horizon 7 pods, the latest features correspond to Horizon 7 components at version 7.12 and later, connected to the cloud control plane using Horizon 7 Cloud Connector at version 1.6 and later.

Intended Audience

This document is intended for experienced IT system administrators who are familiar with virtual machine technology and datacenter operations.

Depending on your organization's needs and the type of pod you are working with, you might find it helpful to be familiar with these software products, software components, and their features:

  • VMware Horizon 7
  • VMware Cloud
  • VMware Horizon® 7 Cloud Connector™
  • VMware Unified Access Gateway™
  • VMware Workspace ONE® Access™
  • VMware Horizon® Client™
  • VMware Horizon® HTML Access™
  • Microsoft Azure and its Marketplace
  • Microsoft Active Directory
  • VMware Dynamic Environment Manager™

About the Screenshots Used in This Document

The screenshots typically:

  • Show only that portion of the overall user interface screen that corresponds to the text at which point the screenshot appears, and not necessarily the full user interface.
  • Have blurred areas where appropriate to maintain data anonymity.
Note: Some screenshots are taken at a higher resolution than others, and might look grainy when the PDF is viewed at 100%. However, if you zoom to 200%, those images start to look clear and readable.

Horizon Cloud Community

Use the following communities to ask questions, explore answers given for questions asked by other users, and access links to useful information.

Contacting VMware Support

Contact VMware Support when you need help with your Horizon Cloud environment.

  • You can submit a support request to VMware Support online using your My VMware® account or by phone.
  • KB 2144012 Customer Support Guidelines provides details for getting support depending on the issue encountered.
  • After you have configured at least one cloud-connected pod, you can submit a support request by logging in to the Administration Console and clicking Circle help icon in Administration Console > Support.

VMware Information Experience Glossary

VMware Information Experience provides a glossary of terms that might be unfamiliar to you. For definitions of terms as they are used in VMware technical documentation, go to http://www.vmware.com/support/pubs.