These steps are part of the alternative manual method for creating a master virtual machine (VM) for a pod in Microsoft Azure. Manually building a master virtual machine (VM) that conforms to the Horizon Cloud environment's requirements is a multi-step process. You perform most of these steps in the Microsoft Azure portal. You first create and configure a base VM, then install agent-related software components into that base VM, and then configure specific properties for those agent-related components.
Use these steps only if you do not want to use the automated Import Desktop wizard and instead want to manually build the master VM using the Microsoft Azure portal or if you have already manually built a VM using the Microsoft Azure portal and you want to use that VM for your master VM. The recommended automated way to build a master VM for a pod in Microsoft Azure is to use the Import Desktop wizard and its From Microsoft Azure Marketplace option. For details about using the automated wizard, see Create a Master Virtual Machine Automatically from the Microsoft Azure Marketplace.
If you have a VM in Microsoft Azure that you want to use as the master's base VM, you must ensure it conforms to the same criteria as when a base VM is created using the manual steps documented in Create the Virtual Machine Manually in Your Pod in Microsoft Azure. If the VM does not conform to the same criteria, Horizon Cloud cannot consume it to display in the Administration Console and use in the Convert to Image workflow. The following criteria are critical:
Before installing the agent-related software, the base VM must have the Storage - Use managed disk setting set to Yes. If the base VM does not adhere to this setting, Horizon Cloud cannot consume this VM.
The base VM must be in the same Microsoft Azure location as the pod where you want to use that base VM.
The base VM must be put into a specific resource group in your Microsoft Azure subscription. This resource group is one that belongs to the pod where you plan to use that base VM. The resource group is named
vmw-hcs-podID-base-vms, where podID is the pod's UUID identifier.
The base VM must be connected to the same virtual network to which the pod is connected.
The base VM must be connected to the pod's subnet named
The base VM must use an operating system currently supported for use in this Horizon Cloud release. Those operating systems are described in the steps in Create the Virtual Machine Manually in Your Pod in Microsoft Azure.
Do not configure the base VM to use IPv6 IP addresses. The Administration Console will report an IP abnormal alert in the Desktop Health tab for VMs that are based on a master VM that uses IPv6 IP addresses.
To verify your base VM meets that criteria before you start to configure it further, log in to the Horizon Cloud Administration Console, navigate to the Inventory VMs page, and verify your base VM is listed on that page. If it is listed, then that base VM meets the above criteria and you can safely proceed with the remaining configuration steps starting with the topics listed in Prepare the Manually Created Master VM Prior to Installing the Agents.