Note: Backup all vDisks before attempting to upgrade to a newer product version.
Upgrading vDisks involves installing the new version of the Provisioning Services target device software on the vDisk image.
If you are upgrading from Provisioning Services 7.6.1 or later, you can do an in-place upgrade. Citrix recommends that you use this method if possible. It involves only two steps:
- Start the client in private or maintenance mode.
- Run the target device installer as described in Installing Provisional Services software on a master target device.
If you have to upgrade from versions earlier than 7.6.1, the following vDisk upgrade methods are supported:
- Upgrading vDisks using Hyper-V. If you are upgrading from Provisioning Services 6.x to 7.1 or 7.6, this inline upgrade method is recommended because it is faster than re-imaging, and uses the least amount of storage.
- Upgrading vDisks by re-imaging. If neither of the other two methods of upgrading vDisks are viable in your implementation, select from one of the following re-imaging upgrade methods:
- Versioned vDisk Upgrade – If upgrading vDisks from Provisioning Services 6.x to 7.1 or 7.6, use this vDisk upgrade method if the Upgrading vDisks using Hyper-V method cannot be used. This method re-images to a maintenance version of the vDisk, allowing production devices to continue running and booting from the production version of the vDisk. After the upgraded version of the vDisk is promoted to production, target devices will boot or reboot from the upgraded vDisk version.
- Automated Inline Upgrade– if upgrading vDisks from Provisioning Services 5.1.x, 5.6.x, or 6.x to 7.1 or 7.6, use this method if the Upgrading vDisks using Hyper-V or Versioned vDisk Upgrade methods cannot be used. This method uses the Upgrade Wizard and Upgrade Manager to automate some of the steps included in the Manual vDisk Upgrade method.
- Manual vDisk Upgrade – if upgrading from 5.1.x, 5.6.x, or 6.x to 7.1 or 7.6, using this vDisk upgrade is recommended only if the Upgrading vDisks using Hyper-V or Versioned vDisk Upgrade methods cannot be used, or the Automated Inline Upgrade method fails. It may also be considered if multiple partitions exist on the vDisk and the same system and machine are available for re-imaging (the hard disk drive does not need to be the same).