For a node in Microsoft Azure, you can use the Import Desktop wizard to create the master virtual machine (VM) using an operating system image from the Microsoft Azure Marketplace. In the process, the VM is automatically configured with the elements and agents required to conform to the Horizon Cloud environment's requirements.
About this task
By default, the automated process installs those Horizon agent custom setup options for an RDS host that are supported for use in the Horizon Cloud environment. If you want to change the default selections, expand the Advanced Options section in the Import Desktop - Marketplace window and set the toggles according to your needs.
Before running the wizard, ensure that the image name you plan to use was not previously used for a master VM in your Horizon Cloud environment. For example, if a master image was converted into an assignable image so that it is listed on the Images page, do not use the same name for a new master image. Due to a known issue in this release, if you enter the same name, the system will fail to create the VM in Microsoft Azure, but no error message or notification is displayed to you in the Administration Console.
- In the Horizon Cloud Administration Console, click and then click Import.
- In the Import Desktop window, click From Marketplace.
- Select the destination location and node for the desktop.
After you select a location, the choices in the Node list are filtered to show the nodes available in the selected location.
- Select the details for the base VM.
Select the Microsoft Windows server operating system to use for the base RDS-enabled VM.Note:
This drop-down menu takes a few moments to populate the entries.
If you want to have GPU acceleration in your RDS desktops, select 2012-R2-Datacenter which is Microsoft Windows Server 2012 R2. In this release, GPU is not supported in Microsoft Windows Server 2016 due to a limitation in the Horizon Agent.
Select a server VM specification. The choices correspond to those VM specifications in the Microsoft Azure Marketplace that are supported for use in the Horizon Cloud node.Note:
The Standard_NV6 choice is only available in some Microsoft Azure regions.
If you select the Standard_NV6 choice, you must log into the VM's operating system and install the supported NVIDIA graphics drivers in the resulting master image VM to get the GPU capabilities of the Microsoft Azure NV6 VM. You install the drivers after the VM is created and the Imported VMs page shows the DaaS agent is active.
If you want to have GPU acceleration in your RDS desktops, select the Standard_NV6 choice and ensure the 2012-R2-Datacenter choice is selected for the OS.
Select the Active Directory domain that you want configured in the base VM.
Enable Public IP Address
Set this toggle to Yes to configure a public IP address for this master VM. When set to Yes, the VM gets both a private IP address and a public one.
When this toggle is set to No, the VM is configured with only a private IP address in your Microsoft Azure environment.
- Provide administration details.
Type the admin username that you want for the VM's local administrator account. This username will be used for the local admin account to access the VM's operating system, and also used during the convert to image process. This username can be a maximum of 15 characters in length, must not end in a period ("."), and must not be one of the admin user names that are not allowed when creating a VM in Microsoft Azure.Important:
Ensure you can remember this local administrator account information (the username and password that you specify in the Password field), or that you write it down so you can retrieve the information later. You will need these credentials when you want to add any third-party applications to this master image and when performing the New Image workflow to publish this master image to the system.
Type the password that you want for that administrator account. The password must adhere to the Microsoft Azure password rules:
Must not be one of the admin account passwords that are not allowed when creating a VM in Microsoft Azure
Must be 12 - 123 characters in length and meet three out of the following four complexity requirements:
Contain a lowercase character
Contain an uppercase characters
Contain a digit
Contain a special character, such as (!@#$%/^&*)
Re-type the password
Do you have a Windows Server License
To confirm that you have an applicable Windows Server License for the one you selected as the OS, set this toggle to Yes and check the check box that appears.
- In the Name field, provide a name for the master VM and an optional description.
Do not enter a name that was previously used for a master VM that has been converted into an assignable image in your Horizon Cloud environment. For example, if a master image was converted into an assignable image so that it is listed on the Images page, do not enter the same name here. Due to a known issue, the VM creation process will fail silently if you reuse a name that is already listed on the Images page. The system will not create the VM in Microsoft Azure, however, an error message does not appear in the Administration Console.
The name must adhere to the following rules:
It cannot contain an underscore character (_).
It can have only alphanumeric characters and the hyphen.
The name must start with an alphabetic character (not a number).
The name cannot end with a hyphen (-).
- To change the Horizon agent features that will be installed in the master VM, use the toggles in the Advanced Options section.
By default, all of the listed Horizon agent features are installed. When the option's toggle is set to Yes, the corresponding agent feature is installed in the master VM.
Enable Flash MMR
Provides the ability to redirect Flash multimedia content that is streamed to the remote desktop to stream directly to the client computer and decoded on the client system, for performance optimization. The client system plays the media content, offloading the demand on the RDS desktop.
3D support in RDSH
Provides 3D graphics support to applications that run on the RDS desktop.
MMR for Terminal Services
Provides the ability to redirect multimedia content that is streamed to the remote desktop to stream directly to the client computer and decoded on the client system, for performance optimization. The client system plays the media content, offloading the demand on the RDS desktop.
Client Drive Redirection
Allows Horizon Client users to share local drives with their RDS desktops and applications.
Skype for Business
Provides the ability to use the RDS desktops to make optimized audio and video calls with Skype for Business.
Webcam Support (Real Time Audio Video RTAV)
Redirects webcam and audio devices that are connected to the users' client systems so that those devices can be used on the remote desktop.
Lets users authenticate with smart cards when they use the PCoIP or Blast Extreme display protocol.
Allows users to print to any printer available on their client computers, without installing additional drivers.
Redirects scanning and imaging devices that are connected to the users' client systems so that they can be used on the remote desktop or application.
Gives users access to locally connected USB flash drives and hard disks in the RDS desktops and applications.Note:
For guidance on using USB redirection securely, see the View Security guide. For example, you can use group policy settings to disable USB redirection for specific users.
Allows Horizon Client to determine which URLs should be handled by the remote desktop or application instead of being opened by the users' client system, and open those URLs using the remote desktop or application.
For additional details about the various Horizon agent options used for an RDS host, see Horizon Agent Custom Setup Options for an RDS Host in the VMware Horizon® 7 product documentation.
- Click Import.
The system begins creating and configuring the master VM. When the VM is created in the node, it is listed on the Imported VMs page. Use the refresh icon to see the latest set of VMs on the page. Even though the VM is listed on the page after several minutes, the master VM is not ready to for installing applications or drivers until its DaaS agent is shown as active on the Imported VMs page. It can take as long as 30 minutes for the agent status to get to the active state.
When creating an image in Microsoft Azure China cloud, the process can take up to two (2) hours to complete. The process is subject to geographic network issues that can cause slow download speeds as the binaries are downloaded from the cloud control plane.
What to do next
Customize the image's Windows operating system, including configuring things like wallpapers and installing the applications you want this RDS-enabled VM to provide to your end users. If you enabled a public IP address for the VM, you can connect to the created VM by using the IP address displayed on the Imported VMs page in an RDP client like Microsoft Remote Desktop Connection. For details, see Customize the Guest Windows Operating System of the Master Image Virtual Machine.
If you selected the Standard_NV6 server model, you must log into the VM's server operating system and install the supported NVIDIA graphics drivers to get the GPU capabilities of the Microsoft Azure NV6 VM. You install the drivers after the VM is created and the Imported VMs page shows the DaaS agent is active. See Install NVIDIA Graphics Drivers in an NV6 Server Model Master Image.
If you want to use User Environment Manager, you must log into the VM's server operating system and manually install the User Environment Manager agent, which is named FlexEngine. See Install the User Environment Manager Agent in the Master Image Virtual Machine.