update an existing vDisk is required
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
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.
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).
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.
Create a new maintenance version
of the vDisk.
Make any necessary updates to the maintenance version.
Promote the new maintenance version to test.
Boot the PvD test device, and then verify updates were
Promote the test version to production.
The following vDisk update scenarios
– An administrator may choose to update a vDisk manually by creating a new
version of that vDisk, and then using a Maintenance device to capture
updates to that version. Manual updates are initiated by selecting the New
button on the vDisk Versions dialog. The Access column on the vDisk
Versioning dialog displays that the newly created version is currently
under maintenance. While under maintenance, this version can only be
accessed and updated by a single Maintenance device. Multiple Maintenance
devices can be assigned to a vDisk. However, only one device can boot and
access that version of the vDisk at any given time. During that time that
Maintenance device will have exclusive read/write access.
– Creating automated updates saves administration time and physical
resources. Updates are initiated on-demand or from a schedule and are
configured using vDisk Update Management. If updating automatically, the Access
column on the vDisk Versioning dialog displays that the newly created
version is currently under maintenance. While under maintenance, this
version can only be accessed and updated by the one Update device to which
it is assigned (only one Update Device exists per vDisk).
Update Management is intended for use with Standard Image Mode vDisks only.
Private Image Mode vDisks can be updated using normal software distribution
tool procedures. Attempting to register a Private Image Mode vDisk for vDisk
Update Management, or switching a vdisk that is already registered, will cause
errors to occur.
– Merging VHD differencing disk files can save disk space and increase
performance, depending on the merge option selected. A merge update is
initiated manually by selecting the Merge button on the vDisk
Versions dialog, or automatically when the maximum vDisk versions
count is reached.
Updating a vDisk Image
This procedure requires that:
A Maintenance device has been assigned to the vDisk being
No version of this vDisk is currently under maintenance.
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.
To create a new version:
the Console, right-click on a vDisk to version within a device collection
or vDisk pool, then select Versions... from the
context menu. The vDisk Versions dialog appears.
Note: Verify that the vDisk is currently not in Private Image mode.
New. The new version displays in the dialog with Access set to Maintenance and the update Type
method set to Manual.
the vDisk from a Maintenance device, install or remove applications, add
patches, and complete any other necessary updates, then shutdown the
Maintenance device. Optionally, test that changes were made successfully.
Note: If booting a Test or Maintenance device, a boot menu displays
that allows the user to select from which vDisk, or version of that vDisk, to
boot from unless the device is a PvD Test device.
on the vDisk, then select the Promote... menu option
from the context menu that appears (for more details on promoting versions
refer to Promoting
to promote this maintenance version into test or directly into production.
If Production is selected, set the availability of this version in
production to be either immediate or scheduled.
OK to promote this version and end maintenance.
Automating vDisk Updates
After the site is configured to use
vDisk Update Management, managed vDisks can be updated using the following
– an administrator selects a managed vDisk to be updated from the Consoles
Run update now menu option (requires that the administrator also manually
start, then stop the Update Device after the update is complete).
following illustrates the basic update process for both scheduled or user
envoked update methods:
The vDisk update process starts either automatically
(scheduled), or when an administrator right-clicks on a managed vDisk,
then selects the Run update now menu option.
Provisioning Services creates a new version (VHD) and
places that version in Maintenance mode (read/write).
The virtual machine boots the assigned vDisk. If this
Scheduled update – vDisk Update Management performs
the boot automatically.
User envoked update – the administrator envokes the
All updates are automatically made and captured in the
new version of the VHD file.
After updating the vDisk, the virtual machine is shut
The vDisk is promoted from Maintenance to either Test
or Production. The availability of the new vDisk version depends on the
Access mode that was selected when the Update Task Wizard was run, or the
mode that is currently selected on the Update Task Properties' Finish tab
(Maintenance, Test, or Production). After this version is made available
in production, target devices will be able to access it the next time they
boot that vDisk.