After you publish an image and create VDI desktop assignments using it, you can make changes to that image and push the changes to all of the VDI desktop assignments that use that image. A typical reason to update an already published image is to install additional third-party applications or other features. You start this workflow in the Horizon Universal Console.

Note: If you are changing the image to update the Horizon Cloud agent-related components, you use a different procedure. See Horizon Cloud Pods - Updating the Agent-Related Software Installed in Your VDI Desktop Assignments, Farms, Publishing Images, and Base VMs and its subtopics.

At a high-level, the workflow to update an in-use image is:

  1. Duplicate the existing image to create an image with the same configuration and a new name. In the duplication process, the system clones the sealed image's virtual machine (VM) to make a new unpublished golden image VM, and lists the new VM on the Imported VMs page.
  2. When you see that the Imported VMs page reports the new VM's agent is active, log in to the VM and make your desired changes to that duplicate VM.
  3. Use Convert to Image to publish that duplicate VM, making it an assignable (sealed) image.
  4. Edit the VDI desktop assignments that are using the original image to use the newly updated duplicate image instead of the original one.

Prerequisites

Verify you have local administrator account credentials to log in to the image and update it. This administrator account is the same one that was used to publish the image using the New Image workflow. See Convert a Configured Image VM to an Assignable Image in Horizon Cloud.

Note: When using the Microsoft Remote Desktop Client as your RDP software to connect to the VM, ensure it is the most up-to-date version. For example, the default RDP software in the Windows 7 operating system is not at a high enough version. The version must be version 8 or higher.

Procedure

  1. Click Inventory and navigate to the image-related page where the image is listed.
  2. Select the check box for the image and click Duplicate.
    In the dialog box, enter a name for the duplicate image. After you enter a new name and click Save, the system clones the sealed image's VM to make a new image VM, and lists the new VM on the Imported VMs page.
    Note: As the system begins the cloning process, the original sealed image goes into Transition status for the first part of the process. After some time, the original sealed image returns to its original state.
  3. Navigate to Inventory > Imported VMs to see when the Imported VMs page reports the new VM's agent is active.
  4. When you see on the Imported VMs page that the new VM's agent is active, use the VM's IP address and your RDP software to connect to the Windows operating system.
    • If the original image was created with a public IP address, the new duplicate VM has a public IP address and you can use that IP address in your RDP software
    • If the original image was not created with a public IP address, the new duplicate VM has an IP that is private in your Microsoft Azure cloud environment, and you must RDP into it by one of these two methods:
      • Using another VM in your Microsoft Azure subscription that does have a public IP address and doing an outbound RDP into the VM.
      • Use your VPN and RDP into the VM over your corporate network
  5. Log in to the Windows operating system using the username and password that was supplied in the Import Image wizard when the image was created.
    If using the local administrator name, enter the username as \username.
  6. In the Windows operating system, perform your intended updates.
    If you are installing additional third-party applications, see the steps described in For a Horizon Cloud Imported VM with a Microsoft Windows Client Operating System — Customize the VM for Your Organization's Needs.
  7. Return to the Imported VMs page, select the check box for that duplicate VM, and click More > Convert to Image.
    The system takes the image, which was duplicated and then updated, through its standard publishing process. The image is displayed on the image-related page where it was listed at the start of this process. When the publishing process is complete, the image is displayed with the Published status.
  8. When you see that the duplicated and updated image is in Published status, edit each VDI desktop assignment that is using the original image to use the new duplicate image instead, the image which now has your changes in it.

Results

When you update a VDI desktop assignment to change its image:

  • Unassigned, powered-off VMs in the assignment are automatically recreated using the new image.
  • Unassigned VMs that are powered on but do not have an active end user connection are automatically recreated with the new image.
  • Unassigned VMs that are powered on and which have an active end user connection, such as those from a floating VDI desktop assignment, are automatically updated with the new image when the end user logs off.
  • Desktop VMs that are mapped to an end user, such as those from a dedicated VDI desktop assignment, are not automatically updated to the new image. To get such an assigned desktop VM updated to use the new duplicate image instead, you must manually unassign that desktop VM. The next time the system goes to power on the desktop VM, it will apply the new image. Then you can manually assign that desktop VM back to a specific end user.

What to do next

When you have updated the VDI desktop assignments that are using the original image and you can determine the original image is no longer needed by your organization, you can use the console to delete the original image. Deleting the original image is a best practice, to prevent other administrators in your organization from using an image that has down-level software.