This documentation page describes how you can resize specific, individual VDI desktops that already exist in a VDI dedicated desktop assignment.
Starting with service release 2204, you can edit an existing assigned dedicated VDI desktop to change its VM model, its disk size, and its disk type. To have use of this feature, the pod must be running that release's manifest version or later.
This feature is typically used in the following scenarios:
- In their already assigned desktops, some of the assignment's end users have CPU, memory, or disk type needs that are different from the assignment's VM configuration.
- The VDI dedicated assignment itself used a VM model and disk type and size, and it had existing desktops, and then the assignment itself was subsequently edited to use a different VM model or a different disk type or disk size. In this scenario, the already existing desktops would remain using the assignment's original VM model or disk configuration until you individually edit those desktops to match the assignment's new VM configuration.
Notes about this feature:
- Editing a specific VDI desktop means changing the Azure VM model, disk size, or disk type used in that desktop's underlying virtual machine.
- After a specific desktop in a VDI dedicated desktop assignment is edited, the overall assignment in which that desktop resides is considered a mixed type of assignment.
- The overall assignment continues to use its specified VM settings. As a result, if you later increase the number of desktops in that VDI dedicated desktop assignment, any new VDI desktops created from the assignment expansion will receive the assignment's VM settings.
- This feature is supported for use with single-session Windows 10 and Windows 11 operating systems.
- Use with the following operating systems is unsupported: Windows 7 and multi-session Windows operating systems. (Please note that in Horizon Cloud for Microsoft Azure deployments, multi-session Windows operating systems are used in farms. This feature is in context of a VDI dedicated desktop assignment. Therefore, there would not be an expectation that this feature would be supported for such multi-session systems, because those multi-session systems are not used for VDI dedicated desktop assignments.)
- Using ZRS disk types with this feature is currently unsupported. The ZRS (Zone Redundant Storage) option is in limited preview in the Microsoft Azure cloud. Editing desktops that are configured with the ZRS disk type might fail. Editing desktops to switch from a non-ZRS disk type to a ZRS disk type might fail.
- On the VDI dedicated desktop assignment's Desktops tab in the console, the Model column displays the Azure VM model used for the assignment's desktops. From that Model column, you can see which individual desktops are using a VM model different from the other desktops.
The VDI desktop must be in the powered-off state before you can use the Edit action on it.
Ensure that the assignment's power management policy will not hinder your ability to power off the VDI desktop. If the power management policy is set to ensure the desktops are powered on, then as you power off the VDI desktop to edit it, the system will automatically attempt to power it back on. If needed, temporarily adjust the power management policy to allow you to power off the VDI desktop and edit it. Then when the system activity of updating the desktop is finished, revert the assignment's power management policy back to its previous state.
- In the Horizon Universal Console, navigate into the details of the VDI dedicated desktop assignment in which the desktop resides and select its Desktops tab.
- Power off the desktop if it is not already off.
- Select the powered-off desktop and click
- Select a new VM model or change the disk type or size.
Note: The ZRS disk type is currently unsupported for use with this feature. Selecting the ZRS type might fail.
- Click Save.
What to do next
If you temporarily adjusted the power management policy to allow you to power off the VDI desktop for editing it, revert the assignment's power management policy back to its previous state.
Increasing the disk size might require guest OS operations on the desktop's underlying VM For more information, see Required Actions When the Disk Size is Increased.