Tutorial 1 - 2 min activityVMware Horizon Cloud Service on Microsoft Azure 1.6
Tutorial 2 - 4 min activityTechnical Introduction and Features
Tutorial 3 - 5 min activityComponents and Architecture
Tutorial 4 - 15 min activityA: Setting Up
Tutorial 5 - 12 min activityB: Deploying a Horizon Cloud Service Node
Tutorial 6 - 14 min activityC: Creating an Image
Tutorial 7 - 15 min activityD: Deploying a Farm
Tutorial 8 - 21 min activityE: Assigning Resources to Users
Tutorial 9 - 5 min activityExploring Monitoring and Analytics
Tutorial 10 - 6 min activityExploring VMware User Environment Manager
Tutorial 11 - 6 min activitySummary and Additional Resources
A: Setting Up
A: Setting Up
These prerequisites exercises help you prepare your environment for best use of Horizon Cloud Service on Microsoft Azure. The exercises are sequential and build upon one another, so make sure to complete each exercise in this section before going to the next.
First, you verify that your environment meets the basic prerequisites. Next, you create a new virtual network (VNet), one of the prerequisite Microsoft Azure components. You must bring your own Microsoft Azure IaaS capacity, and configure the Microsoft Azure prerequisites for the Horizon Cloud Service deployment. You set up network ranges based on previously provided CIDR blocks, select Active Directory options, complete VNet bi-directional peering, DNS configuration, and so on. Subsequent sections describe how to deploy the Horizon Cloud Service node on Microsoft Azure, and finally to create a farm where your end users can access applications and shared desktops, and assign dedicated and floating desktops.
Exercise A1: Reviewing the Workflow
Before you start, it is a good idea to review the workflow and tasks involved. You can use the navigation tool on the left to jump to each section:
- Verify that your environment meets the prerequisites listed in VMware Horizon Cloud Service on Microsoft Azure Requirements Checklist.
- See Deploying a Horizon Cloud Service Node
- Prepare the Microsoft Azure for node deployment.
- Deploy the node.
- See Creating an Image
- Register Active Directory domain.
- Configure a master image.
- Install applications in the master image.
- Convert the master image into an assignable image.
- See Deploying a Farm
- Create an RDSH farm to provide session desktops which you can assign to users and groups.
- Create a second RDSH farm to provide remote desktops which you can assign to users and groups.
- Create a CNAME record in your DNS server.
- See Assigning VDI Desktops
- Assign a dedicated desktop.
- Assign a floating desktop.
- See Explore Horizon Cloud Service Monitoring and Analytics
- Explore the reports and analytics functionality.
- See Explore VMware User Environment Manager
- Explore the integration with User Environment Manager and capabilities.
After you finish reviewing the workflow, verify that your environment meets all prerequisites, and then proceed to the next exercise to configure the VNet.
Exercise A2: Creating the VNet
You can deploy a Horizon Cloud Service node to an existing virtual network (VNet), or create a new VNet. But before you create a VNet, verify that your environment meets the prerequisites listed in VMware Horizon Cloud Service on Microsoft Azure Requirements Checklist. For more information, see Getting Started with VMware Horizon Cloud Service on Microsoft Azure.
This exercise describes how to create a new VNet where Active Directory services are available. Microsoft Azure automatically creates the necessary subnets in the VNet using CIDR blocks that you provide. Horizon Cloud Service automates machine creation and domain join operations, and requires access to a VNet with AD services. A set of resource groups in your Microsoft Azure capacity is also automatically created. Resource groups organize the assets that the environment needs, such as virtual subnets and virtual machines (VMs) for the Unified Access Gateway, RDS-enabled server images, RDSH farms, and so on.
1. Log in to Microsoft Azure
- Log in to your existing Microsoft Azure deployment.
- Make sure to use a subscription that provides IaaS capacity.
2. Add a New Virtual Network
- In the navigation bar on the left, select Virtual Networks.
- Click Add to create a VNet.
3. Provide Data for New VNet
- In the Create Virtual Network pane, provide the following information:
- Name: Enter a name to distinguish this VNet from others.
- Address space: Accept the default, or enter an address range.
- Subscription: Select from the drop-down menu.
- Resource group: Select an existing resource group, or create a new one when the virtual network is created.
- The value should not be empty: Create a new resource group or use an existing one.
- Location: From the drop-down menu, select the region where you plan to deploy the Horizon Cloud Service node.
- Subnet Name: Accept the default. Horizon Cloud Service automates the creation of the necessary subnets using the CIDR blocks previously provided.
- Address range: Accept the default.
- Service endpoints: Accept the default.
- In the lower right corner, click Create.
- Wait until the creation process is complete, and the VNet is created.
For more information, see Getting Started with VMware Horizon Cloud Service on Microsoft Azure, and click Horizon Cloud Service on Microsoft Azure > 1.6 > Preparing to Deploy a Horizon Cloud Node into Microsoft Azure > Configure the Required Virtual Network in Microsoft Azure.
After creating the VNET, proceed to the next section to configure bi-directional VNET peering.
Exercise A3: Configuring VNet Peering (Optional)
In this exercise, you use Microsoft Azure to configure bi-directional peering. You should configure VNet-to-VNet peering only if the following is true:
- You created a new VNet that does not have an AD VM inside it
- You are not using Express Route for VNet peering
- You are not using VPN for express route peering
In this tutorial, it is assumed that another VNet is in the same region as the AD/DNS server, to which you are peering for access to those services.
1. Peering Connects the Horizon Cloud Service VNet on Microsoft Active Directory
- Select the Virtual Networks pane.
- Select a network.
- Click Peering.
- In the third pane on the right, verify that the peer is not yet connected.
2. Add Peering Details
- In the Add peering pane, provide the required information:
- Name: Enter a name to distinguish this action from others.
- Virtual network deployment model: Select the Resource manager option.
- Subscription: Select your subscription.
- Virtual network: Click Choose a virtual network, and select your VNet.
- Allow virtual network access: Verify that Enabled is selected.
- Click OK.
3. VNet Peering Is Connected
- Locate the third pane.
- Verify that VNet peering is now connected.
4. VNet Peering Overview Details
- Locate the second pane.
- Click Overview to display additional details in the third pane.
For more information, see the Getting Started with VMware Horizon Cloud Service on Microsoft Azure guide.
After you finish configuring the VNet, proceed to the next exercise to configure the DNS server.
Exercise A4: Configuring the DNS Server
Now that the VNet is configured, your next step is to configure the DNS, which is required during the Horizon Cloud Service node 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. You must set the virtual network to support both internal and external name resolution.
1. Microsoft Azure DNS Supports Name Resolution
- In the navigation bar on the left, click Virtual networks.
- Select the virtual network you want to use for your node.
- Click DNS servers to display the DNS server settings.
2. Configure DNS Before Deploying the Horizon Cloud Service Node
- In the upper right, select the Custom option.
- Add the address of the DNS server to use for name resolution.
For more information, see Getting Started with VMware Horizon Cloud Service on Microsoft Azure .
After you finish configuring the DNS server, proceed to the next exercise to create an authentication key for the service principal.
Exercise A5: Creating a Service Principal Authentication Key
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. When you register a Microsoft Azure AD application, the service principal is also created. For more information, see Create the Required Service Principal by Creating an Application Registration.
In addition to the service principal, you must generate an authentication key and assign the Contributor role to the service principal at the subscription level.
1. Service Principal Settings
- Locate the service principal details window.
- Click Settings to open the Settings menu.
2. Authentication Key Required to Deploy the Horizon Cloud Service Node
- In the Settings menu, click Keys.
3. Authentication Key Security Policy
- In the Keys menu, provide the following information:
- Description: Enter a description of 16 characters or fewer, such as
- Expires: Set the duration of the key, based on your security policy. You can set the expiration to Never expires, or you can set a specific time frame.
- Caution: If you set a specific time frame, make sure to refresh the key before it expires, and enter the new key into the subscription information in the Horizon Cloud Service Administration Console. If the key expires without doing this, the associated node stops because Horizon Cloud Service cannot detect it.
- Value: Keep the Keys window open until you have copied and saved the key value.
- Description: Enter a description of 16 characters or fewer, such as
- Click Save.
4. Copy and Save the Authentication Key Because Irretrievable Later
- Copy the unique key value.
- Save the value securely, because you cannot retrieve it later.
After you finish creating an authentication key for the service principal, proceed to the next exercise to assign a role to the service principal.
Exercise A6: Assigning the Contributor Role to the Service Principal
The next step is to assign the contributor role to the service principal at the subscription level.
1. Make Note of the Subscription ID
- In the navigation bar on the left, select Subscriptions.
- Click the name of the subscription.
- Copy and save the subscription ID to use when you deploy the node.
2. Add Permissions
- Click Access control (IAM).
- Click Add to display the Add permissions window.
3. Add Permissions Information
- In the Add permission window, provide the following information:
- Role: From the drop-down menu of built-in roles, select Contributor.
- Assign access to: From the drop-down menu, select Azure AD user, group, or application.
- Select: Search for and select the service principal by the name you gave it earlier.
- Click Save.
4. Save the Service Principal
- Click your service principal to select it
- Click Save.
After you finish assigning a role to the service principal, proceed to the next section to verify the required resource providers.
Exercise A7: Verifying Required Resource Providers
Verify that your subscription includes the registered resource providers that the node requires.
- In the navigation bar on the left, select Virtual machines, and click the name of the subscription used with this node.
- In the subscription menu, click Resource providers.
2. Verify That Required Resource Providers Are Registered
In the Status column, verify that the following resource providers have a Registered status, and if they do not, register them:
Microsoft.Compute microsoft.insights Microsoft.Network Microsoft.Storage
3. Verify Subscription-Based Values Required for Deployment
- In the navigation bar on the left, click Azure Active Directory > Manage .
- In the second pane, click Properties.
In the third pane, verify that you have the four subscription-based values required during node deployment:
- Subscription ID
- Azure Active Directory ID
- Application ID
- Application key value
For more information, see Getting Started with VMware Horizon Cloud Service on Microsoft Azure.
After you finish creating and configuring the service provider and verified that you have the subscription-related values required for deployment, proceed to the next section to deploy the Horizon Cloud Service node.