In the RDS-enabled base virtual machine (VM), you must configure some DaaS agent properties before Horizon Cloud can convert the VM into an assignable image that can be used in RDSH farms.


  • From the node's summary page in the Horizon Cloud Administration Console, obtain the node's tenant appliance IP address. In the Administration Console, navigate to Settings > Capacity and click on the node's name. On the Summary page, locate the Tenant appliance IP address property and note down that IP address.

    Location of the tenant appliance IP address in the node's Capacity page

  • Verify that the DaaS agent was installed in the base VM as described in Install the VMware Agents in the RDS-Enabled Base Virtual Machine.

  • Verify that the DaaS SSL bootstrap file was downloaded to the VM, as described in Manually Configure the Master Virtual Machine in Microsoft Azure. The file is named image_bootstrap.7z by default.

  • In the base VM's Windows operating system, confirm that you can access the Keytool.exe file in C:\Program Files (x86)\VMware\VMware DaaS Agent\service. Open a command prompt as administrator, navigate to C:\Program Files (x86)\VMware\VMware DaaS Agent\service, and issue the command Keytool.exe -h. If the command returns information about running Keytool to import the bootstrap credentials, you have the required access.


  1. In the Microsoft Azure portal, connect to the base VM and log in to Windows if you are not already connected.
  2. Verify the setting of the DaaS agent's EnableBootstrap registry key is set to 1 (one), and not 0 (zero).
    1. Run regedit.
    2. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware,Inc\VMware DaaS Agent.
    3. Verify the value of the EnableBootstrap key is set to 1 (one).

      If EnableBootstrap key is not set to 1 (one), then modify the key to set it to 1 (one).

  3. Create a registry key for the desktop manager address.
    1. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware,Inc\VMware DaaS Agent.
    2. Add a new string value key named DesktopMgrAddresses.
    3. Set the new key's value to the node's Tenant appliance IP address value that you obtained from the node's details page in the Administration Console.

      New registry key for DaaS agent's tenant appliance IP address

  4. Restart the DaaS agent service.

    The DaaS agent waits for the bootstrap credentials to be imported in the next step.

  5. Import the DaaS SSL bootstrap credentials.
    1. Open a command prompt as administrator and navigate to C:\Program Files (x86)\VMware\VMware DaaS Agent\service.
    2. Run Keytool.exe using the downloaded DaaS SSL bootstrap file (image_bootstrap.7z) as an argument.
      Keytool.exe –f absolute-path-to-bootstrap-file/image_bootstrap.7z

      When prompted, enter the encryption password that you set when you downloaded the DaaS SSL bootstrap file.


      Ensure that step 2 to add the registry key is completed before you run the Keytool utility. If the registry key does not exist, the Keytool command might fail with the message Cannot find the file specified.

      The Keytool utility performs the bootstrap and moves the certificate to the cert folder. If you see a message that the file is successfully decrypted, this step is complete.

  6. Restart the VM to incorporate all of the above changes.

What to do next

At this point, the base VM conforms to the Horizon Cloud environment's requirements to create an assignable image that can be used in an RDSH farm and assigned to users. To confirm that this VM can be converted into an assignable image, in the Horizon Cloud Administration Console, navigate to Inventory > Imported VMs and check that an ACTIVE status is displayed in the DaaS Agent column for this VM.

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.


To access a VM that is running the Horizon agent and DaaS agent, the version of the Remote Desktop Client must be version 8 or later. Otherwise, the connection fails. Using the most up-to-date Remote Desktop Client is recommended.

After the applications are installed, use the New Image workflow to convert the base VM to an assignable image. See Convert a Configured Master Virtual Machine to an Assignable Image.