It is often necessary to update an existing vDisk so that the image contains the most current software and patches. Each time the vDisk is to be updated, a new version of that vDisk is created (VHD file) to capture the changes without changing the base vDisk image.
Updating a vDisk involves the following:
- Create a new version of the vDisk, manually or automatically.
- Boot the newly created version from a device (Maintenance device or Update device), make and save any changes to the vDisk, then shut-down the device.
- Promote the new version to Production.
The following illustrates the general promotion of a vDisk update:
The availability of the updated version depends on the current promotion of that version (Maintenance, Test, or Production), and the type of device attempting to access it (Maintenance Device, Update Device, Test Device, or Production Device).
If updating a device that uses a personal vDisk image, ensure compatibility in your production environment using this procedure:
Note: Updating images for devices that use a personal vDisk, must be done on a virtual machine that does not have a personal vDisk attached. Otherwise, updates are saved to the personal vDisk image rather than the virtual machine image.