Use this page only when you have a first-generation Horizon Cloud environment and you are going to onboard a Horizon pod to that environment.
Attention: Use this page solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.
As of August 2022, Horizon Cloud is generally available and has its own Using Horizon Cloud documentation set available here.
An indication of which environment you have, Horizon Cloud or first-gen, is the pattern that appears in the browser's URL field after you log in to your environment and see the Horizon Universal Console label. For a Horizon Cloud environment, the console's URL address contains a portion like /hcsadmin/. The first-gen console's URL has a different section (/horizonadmin/).
Important: When you are a Horizon Plus subscriber, don't use this page to onboard your pods. When you are a Horizon Plus subscriber, to obtain use of those features that are licensed under the Horizon Plus subscriptions, you must onboard those Horizon deployments to the next-generation control plane. This page's contents here are solely for the first-generation control plane.
Horizon Plus subscribers, see this page about Horizon Plus for the initial steps to onboard to the next-generation control plane and start deploying the Horizon Edge.
Introduction
Complete the following tasks to prepare your Horizon 8 pod's components for onboarding the pod to the first-generation Horizon Cloud control plane. Ensure that the requirements are satisfied as described in the following sections to complete a successful onboarding.
Note: As of this writing, first-generation Horizon Cloud supports those versions of Horizon 8 that are within General Support (versions as reflected in the Omnissa Lifecycle Matrix). The names Horizon 8 pod and Horizon pod are used interchangeably in the first-gen documentation to mean those supported versions of Horizon Connection Server types of pods.
Checklist Audience
This checklist is primarily for clean-slate, greenfield, Horizon Cloud customer accounts that have never had a pod onboarded to their tenant environment prior to the service release in May 2023.
Some of the requirements listed in the following sections are the ones needed for successfully onboarding a Horizon pod for the purposes of using a subscription license with the pod. Some requirements are those needed for the key tasks that are performed after that initial onboarding to enable the use of Horizon Cloud Control Plane services with the pod.
For reference, the high-level workflow of cloud-connecting a Horizon pod is described in Onboarding a Horizon Pod to Horizon Cloud Control Plane.
Horizon Cloud Control Plane Requirements
| ☐ | Active Customer Connect account to log in to the Horizon Cloud control plane. |
| ☐ | Valid Horizon Universal License. |
Horizon Pod and Horizon Cloud Connector Requirements
| ☐ | Using the latest Horizon Cloud Connector version provides for the highest level of platform stability. In the Interoperability Matrix, locate the version of your Horizon 8 deployment and use the latest version of the Horizon Cloud Connector that is compatible with that Horizon 8 version. Then, to use the latest cloud services and features with the cloud-connected pod, your pod must be running the most currently available version of the Horizon 8 pod software. Important: The use case of connecting a replicated instance of a Horizon Connection Server to the cloud plane is unsupported. When you have a Horizon Connection Server instance that is already connected to the cloud plane, and then you replicate that Horizon Connection Server instance and attempt to connect that replicated instance to the cloud plane, unexpected results will occur. |
| ☐ | As of this writing, for new deployments, it is strongly recommended to use Horizon Cloud Connector version 2.4.1 or later. Versions earlier than the latest version 2.4.1 should not be used for new deployments because they will not contain the latest fixes and improvements.
To use the latest cloud services and features with the cloud-connected pod and have the latest security fixes, it must be running the most current Horizon Cloud Connector version.
The Horizon Cloud Connector appliance deployment procedure uses:
|
| ☐ | Resource requirements for the Horizon Cloud Connector virtual appliance. The resource requirements depend on the deployed Horizon pod's architecture: all-in-SDDC or federated architecture. The lists below reflect which versions are currently supported for new deployments for each design.
|
| ☐ | Active Directory user mandated in the pod-onboarding process, when pairing the Horizon Cloud Connector with the pod's Connection Server. This Active Directory user must have the pod's predefined Administrators role on the root access group, as displayed in the pod's Horizon Console in Global Administrators View > Role Permissions > Administrators. In other words, the Active Directory user specified for the pod-onboarding process is a super user for that pod, as described in the Horizon 8 documentation's Horizon Administration guide that is applicable for your pod's software version. |
Active Directory Domains - Optional for Horizon 8 Pods Unless You Need Full Console and Cloud-Plane Services Beyond Licensing
Tip: As described in the first-gen Administration Guide page Active Directory Domain Registration, you can omit Active Directory domain registration and your cloud-connected Horizon pod deployments will continue to receive licensing. Keep in mind that until at least one domain is configured, except for a few features available from the console's Getting Started page, most of console will remain locked and unavailable.
When using the console to register your cloud-connected Horizon pods' Active Directory domains, ensure you fulfill the following requirements.
Note: If your tenant's first pod is a Horizon Connection Server type of pod, when you use the console to register the Active Directory domain, you can choose to skip entering domain-join account information and the cloud-plane services for such pods will work fine.
However, if you choose to skip entering domain-join account information and then later add a Horizon Cloud pod deployment to this same tenant and you plan to have that pod provision resources for end users in the previously registered Active Directory domain, you must remember to configure the domain-join information after deploying that pod. The console does not automatically notify you that the domain-join information is unconfigured after you deploy a Horizon Cloud pod, and provisioning end-user resources from that pod will require domain-join information. Refer to the Horizon Cloud pod checklist for domain-join requirements for such pods.
| ☐ | Supported Microsoft Windows Active Directory Domain Services (AD DS) domain functional levels:
|
| ☐ | All cloud-connected pods in the same Horizon Cloud tenant must have line-of-sight to the same set of Active Directory domains at the time you onboard those pods to the cloud control plane. This line-of-sight requirement applies not only to additional Horizon pods that you subsequently onboard to your pod fleet after the first one, but also to Horizon Cloud pods deployed into Microsoft Azure using the same cloud tenant. |
| ☐ |
Domain bind account.
|
| ☐ |
Auxiliary domain bind account — cannot use the same account as above.
|
| ☐ | Active Directory groups
|
DNS, Ports, and Protocols Requirements
| ☐ | Specific ports and protocols are required both for onboarding a Horizon pod to Horizon Cloud and for ongoing operations of the pod with the Horizon Cloud Connector paired with that pod, and Horizon Cloud Connector with the Horizon Cloud control plane. See DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod. |
Universal Broker
When using the console to configure Universal Broker for your tenant, ensure you fulfill the items from the following table that are applicable to your desired options. For full details, see Configure Universal Broker.
| ☐ | Outbound communications from the pod's paired Horizon Cloud Connector must resolve and reach specific DNS names using specific ports and protocols. This is required for Universal Broker configuration and ongoing operations. See Horizon Pods - Port and Protocol Requirements for Universal Broker. |
| ☐ | Depending on the types of end-user connections you want to provide for:
|
| ☐ | Optional: A custom FQDN that your end users will use to access the Universal Broker service and the certificate based on that FQDN. If you want to use the system-provided brokering FQDN, a custom FQDN is not required. |
| ☐ | Optional. When you want Universal Broker to enforce two-factor authentication, pods must have an external Unified Access Gateway configured for two-factor authentication to an authentication server. Universal Broker passes the authentication request to Unified Access Gateway, which communicates with the authentication server, and then relays the response back to Universal Broker. That external Unified Access Gateway configuration requires the following items:
|
Licensing for the Microsoft Windows Operating Systems
Horizon Cloud does not provide any guest operating system licensing required for use of Microsoft Windows operating systems that you use in the course of using the Horizon Cloud workflows. You, the customer, have the responsibility to have valid and eligible Microsoft licenses that entitle you to create, perform workflows on, and operate the Windows-based desktop VMs and RDSH VMs that you choose to use in your Horizon Cloud tenant environment. The required licensing depends on your intended use.
| ☐ | Licensing for one or more of the following types: Microsoft Windows 7, Microsoft Windows 10 |
| ☐ | Licensing for one or more of the following types: Microsoft Windows Server 2012 R2, Microsoft Server 2016, Microsoft Server 2019 |
| ☐ | Microsoft Windows RDS Licensing Servers — for high availability, redundant licensing servers are recommended |
| ☐ | Microsoft RDS User or Device CALs or both |
Esta página foi útil?