This lab requires few prerequisites to be met to sucessfully complete the lab. We have preconfigured all the prerequisites for you, there is no action needed from your end.
Following are the resources that are precreated.
There are two precreated resource groups i.e.:
- AD-RG: Resource agroup to create adVnet virtual network.
- Horizon-Network-RG: Resource group to create HZN-Vnet virtual network.
There are two precreated virtual network i.e:
- adVNET: Virtual network to deploy adVM.
- HZN-Vnet: Virtual network for horizon resources.
We have preconfigured the bi-directional peering between virtual networks adVNET and HZN-Vnet. By doing this, the Horizon resources deployed in HZN-Vnet will be able to communicate to adVNET, where Active Directory is deployed.
We have preconfigured the DNS Server, which is required during the Horizon Cloud Service pod deployment. Horizon Cloud Service uses the default Microsoft Azure-provided DNS for the deployment for outbound DNS resolution, but requires Active Directory to resolve the Active Directory domain controllers. The virtual network will support both internal and external name resolution.
Horizon Cloud Service needs a service principal to access and use your Microsoft Azure subscription capacity. A service principal defines the policy and permissions for use of an application in a specific tenant, and is used to grant Horizon Cloud Service permission to access and modify your Microsoft Azure tenant. We have precreated a Service Principal in the lab tenant with Contributor role.
-
Service Principal: Like a certificate, the service principal object defines the policy and permissions for use of an application in a specific tenant, and is used to grant Horizon Cloud Service permission to access and modify your Microsoft Azure tenant
-
Subscription ID: Primary Microsoft Azure billing identifier based on your agreement with Microsoft
-
Directory ID: Your Primary Identifier or Identifiers in Microsoft Azure Active Directory
-
Application ID: An attribute of the Service Principal that securely ties the Horizon Cloud Service control plane to your Microsoft Azure subscription and is used to authorize Horizon Cloud as an application to use your Microsoft Azure capacity
-
Application Key: A one-time-use password that is used to encrypt the service principal.
VMware Horizon Cloud Service require below Resource Providers to be registered in the Azure subscription. We have preregistered these Resource Providers while provisioning the environment; there is no action needed from your end.
- Microsoft.Compute
- Microsoft.Insights
- Microsoft.Network
- Microsoft.Storage
- Microsoft.KeyVault
- Microsoft.Authorization
- Microsoft.Resources
- Microsoft.ResourceHealth
- Microsoft.DBforPostgreSQL
- Microsoft.Sql
Click on the Next button from lower right corner of the guide to move on the next page.