After you have updated the image used by a dedicated VDI desktop assignment, you can update the assignment on the Assignments page to update the assigned desktops in the assignment.
A best practice is to edit the assignment and remove any configured power management schedules to eliminate the chance a power-change operation will occur while the agent update tasks are running.
- Navigate to the Assignments page by clicking Assignments.
On the Assignments page, a blue dot appears next to the name of any dedicated VDI desktop assignment for which an update applies. If you point at a blue dot, a pop-up box displays indicating the new version of the Horizon Agents Installer available for that assignment.
The following screenshot illustrates that an agent update is available for the assignment named la24dedsales.
Hold your pointer over that blue dot to see what updates are available.
- Select the check box next to the image you want to update.
- Click Update Agent.
The Agent Update wizard appears.
- In the Software step, select the update version you want to use from the drop-down list.
Note: For assignments using Microsoft Windows 7 you must select Horizon Agent Installer 20.3.x.
- (Required) In the Available VMs to Users field, specify the percentage of desktop VMs in the assignment that you want powered on and available to end users during the update process.
Important: If you do not need desktops available, type a zero (0). You must specify a value for Available VMs to Users, even when you do not care about having desktop VMs available to users during the update process.This value determines how many desktop VMs will be accessible to users over the time the system performs the update on the assignment. This setting is useful for a desktop assignment with a small number of desktops, less than 30 desktops or a few multiples of 30 (like 60 or 90), because it can ensure a higher percentage of a small-sized pool is available as the system goes through updating the desktops. For examples, see How the Agent Update Feature Works for Dedicated VDI Desktop Assignments.
Setting a higher availability percentage results in an adjustment to the number of desktops in the batch of currently updating VMs. When updating the assignment, the system updates a batch of VMs in parallel. By default, the system uses 30 VMs for each batch until the remaining number of VMs to update is less than 30. At that point, the final batch is for those remaining VMs. Because it takes approximately 30-45 minutes to fully update a VM, even though a set of VMs is getting updated in parallel, that set of update-in-progress VMs is unavailable for that amount of time.
This option has less effect when the assignment has many desktops, where the system's maximum default 30 VMs per batch is a small percentage of the assignment's total number of desktops.
- (Optional) To have the system skip those desktops that have logged-in users (active or disconnected session) or conflicting tasks running, activate the Skip VMs with Logged-in User toggle.
- (Optional) Activate the Enable Rollback toggle to have the system create a rollback copy before the agent update is performed and keep that copy for seven days. If the agent update fails on a VM, you then have an opportunity to roll back to the previous agent version for that VM during that seven-day window. For more information, see What to do next at the end of these steps.
Note: Although the rollback window is set at seven days by default, you can request that VMware change this setting for you.
- (Required) For Failure Threshold, enter the number of VMs for which the agent update is allowed to fail before the update process is stopped. This prevents mass failures from occurring.
The default value is the one you configured inNote: When the update process stops due to failed VM updates, you might observe a number of failed VMs that is higher than the threshold you set. This can occur for a variety of reasons. For multi-pod assignments, this can occur because the system applies the threshold setting per pod rather than per assignment.
- (Optional) To have the system automatically retry any of skipped VMs, activate the Retry Skipped VMs toggle.
- (Optional) In the Job Timeout field, specify the time period over which you want the system to continue automatically trying to update the skipped VMs.
The Job Timeout field sets the number of minutes that the system retries updating the skipped VMs. Every 30 minutes, the system tries to update the skipped VMs until it reaches the end of this time period or until all of the assignment's desktop VMs have been updated.
You can enter a value that ranges from 120 minutes (2 hours) to 1440 minutes (24 hours). The default value is 720 minutes (12 hours).
- If this is a multi-cloud assignment, you can select the pods to update under Select Pods to Update. Pods with manifest version lower than 2632 have a warning icon next to the pod name with hover text saying that Roll Back and Failure Threshold are not supported for that pod.
- Click Next.
- (Optional) In the Command Line step, add any command-line options that might be relevant for this update on the image.
The wizard displays a message that indicates whether command-line options are available for the specified update.
- Click Submit.
- A message displays at the top of the page indicating that the update has started.
- The system updates the agent-related components on the desktop VMs in the dedicated VDI desktop assignment.
You can view the progress of the update task by selecting Monitor > Activity.
What to do next
Go to the Assignments - VDI Desktops page and see if updates were successful. If updates failed for some VMs in an assignment, there is a visual indicator next to the assignment name as shown below.
If you have enabled rollback when performing the agent update, you can roll back each failed VM to the previous agent version on the Desktops tab of the assignment detail page. For more information about actions you can perform on the assignment detail page, see Managing Assignments Provisioned By Horizon Cloud Pods in Microsoft Azure.