Product Documentation

Upgrading vDisks by reverse imaging

Mar 08, 2017
Upgrade by re-imaging only if neither of the other two methods of upgrading vDisks (in-place upgrade from version 7.6.1 and later, or upgrading using Hyper-V) is viable in your implementation.
The re-imaging upgrade method that you choose will depend on your existing Provisioning Services implementation and network requirements.

Versioned vDisk upgrade

This vDisk upgrade method can be selected when upgrading vDisks from 6.x to the latest version of the target device software. 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.

Upgrade prerequisites include:

  • Upgrading all Provisioning Servers
  • Upgrading Provisioning Services Consoles
  • Creating a backup copy of the vDisk
To upgrade, complete the procedure that follows.
  1. Boot the Maintenance device from the managed vDisk while in Maintenance mode.
  2. From the product installation directory, run P2PVS.exe to reverse image using volume-to-volume imaging. Select the vDisk as the source and the hard disk drive (HDD) as the destination. If your destination partition is on any partition other than partition 1, you must edit the boot.ini or bcedit partition settings before rebooting from the HDD.
  3. Reboot the Maintenance device from the HDD (do not PXE boot).
  4. On the Maintenance device, uninstall 6.x target device software, and then install the latest version of the target device software.
  5. Run the Provisioning Services Imaging Wizard to create a new vDisk image, create the target device if it does not already exist, and assign the vDisk to the target device.
  6. Test streaming the new vDisk image by booting a Maintenance or Test device from the upgraded vDisk.

About reverse imaging on UEFI VMs

Reverse imaging can be used to update antivirus and malware definitions, however, UEFI cannot perform this task as BIOS can perform it. 

When reverse imaging UEFI VMs, consider the following:

  • Reverse imaging UEFI VMs can only be done manually using P2PVS.exe, using either:
    • GUI
    • Command line

Important

When using reverse imaging on UEFI VMs, consider that the process is destructive, all data will be lost as a result. 

Automated inline upgrade

Use the Automated vDisk Upgrade method when upgrading from 5.1.x, 5.6.x, or 6.0 to 6.1, and the Hyper-V upgrade method cannot be used. This upgrade method takes an existing vDisk and converts it to the current product version using the Upgrade Wizard and Upgrade Manager.
 
Prerequisites:
  • All Provisioning Services Consoles have been upgraded.
  • All Provisioning Servers have been upgraded.
  • A copy of the vDisk has been created prior to upgrading.

Automated Inline vDisk upgrades require that the vDisk is offline to target devices until the vDisk upgrade completes. To avoid vDisks being offline, create a clone of the vDisk and use it for the upgrade process. Then, after the upgrade completes, target devices can be migrated to the upgraded vDisk.

  1. On the master target device or maintenance device, depending on the target device platform, run either PVS_UpgradeWizard.exe or PVS_UpgradeWizard_x64.exe.
  2. Copy UpgradeManager61.exe from the Provisioning Services 6.1 Target Device product installation directory into the installation directory of the Provisioning Server.  The default product installation directory is C:\Program Files\Citrix\Provisioning Services.
  3. On the Provisioning Server, run UpgradeManager61.exe.
  4. On the master target device, run UpgradeConfig.exe from the Windows Start menu shortcut or from the product installation directory:
    1. Specify a local account with Administrator privilege to AutoLogon. This local account cannot have an empty password.
    2. Specify a local partiton to which reverse imaging will clone data. The original hard drive that the vDisk was cloned from is recommended.
      Note: If this is a new hard drive, use the manual upgrade method to initialize the hard drive.
    3. Specify the Provisioning Server IP address and a user account and password to connect to UpgradeManager. This account cannot have an empty password.
    4. Click OK.
    5. UpgradeConfig preforms a sanity check on various parameters. If everything passes, the UpgradeConfig exits, and then reboots the machine to start the upgrade script.
    6. The machine will reboot several times, and then display a message to indicate that the script has successfully completed.

Hinweis

AutoLogon clears when the upgrade completes. If AutoLogon is wanted for vDisk deployment, setup AutoLogon as necessary.

Upgrading vDisks manually

Use the manual upgrade as a universal approach to upgrading vDisks, or if any of the following are true:

  • The vDisk has gone through a number of modifications in Private Image mode
  • The original hard drive is no longer available

The manual upgrade method includes completing the following tasks:

  1. Image the vDisk back to the master target device's hard drive.
  2. Install the latest product software on the master target device.
  3. Image the target device’s hard drive onto the vDisk file.
  4. Boot from the vDisk.

Image back to master target device's hard drive

There are two procedures that allow you to image a vDisk back to a hard drive. The procedure you select depends on the state of the disk drive you are imaging to. You can image back to the original hard drive from which the vDisk was created; this is the recommended method. Alternatively, you can image back using an unformatted, uninitialized hard disk drive.

Image back to the original hard drive from which the vDisk was created

  1. Boot from the vDisk in Private or Shared Image Mode.
  2. From Windows Administrative Tools, select the Computer Management menu option. The Computer Management window appears.
  3. In the tree, under Storage, select Disk Management.
  4. Note the partition letter of the active partition of the original hard disk. If new, format the disk before continuing.
  5. Run the Image Builder utility on the target device. This utility is located at \Program Files\Citrix\Provisioning Services\P2PVS.exe.
  6. Specify the drive letter of the newly created partition (or the original boot HDD partition) as the Destination Drive. The destination drive should point to the vDisk first partition by default.
  7. Proceed cloning the hard drive image to the vDisk Destination Drive.
  8. To connect the vDisk to the Provisioning Server, from the Console, set the target device to boot from the hard drive, then PXE boot the target device. If this step is not completely properly, the Provisioning Server will not be able to connect with the vDisk
  9. Uninstall the product software (for details, refer to Uninstall Product Software) .

Image back using an unformatted, uninitialized hard-disk drive

  1. Boot from the vDisk in Private Image Mode.
  2. From Windows Administrative Tools, select the Computer Management menu option. The Computer Management window appears.
  3. In the tree, under Storage, select Disk Management.
  4. Create a new primary partition, as the first partition, assign a drive letter to it, and then format the partition.
  5. Right-click on the newly created partition, then choose Mark Partition as Active.
  6. Delete the boot.ini.hdisk file from the root of the vDisk.
  7. Run the Image Builder utility on the target device. This utility is located at \Program Files\Citrix\Provisioning Services\P2PVS.exe.
  8. Specify the drive letter of the newly created partition (or the original boot HDD partition) as the Destination Drive. The destination drive should point to the vDisk first partition by default.
  9. Clone the hard drive image to the vDisk Destination Drive.
  10. To connect the vDisk to the Provisioning Server, from the Console, set the target device to boot from the hard drive, then PXE boot the target device. If this step is not completed correctly, the Provisioning Server will not be able to connect with the vDisk.
  11. Uninstall the product software (for details, refer to Uninstall Product Software).

Install master target device software

Complete the following steps to install the latest product software on the Master Target Device.

  1. Run the new Provisioning Server Target Device installer on the target device.
  2. PXE boot the target device.

Image the hard drive

Complete the following steps to image the target device’s hard drive onto the vDisk file:

  1. Run the Image Builder utility on the target device. This utility is located at \Program Files\Citrix\Provisioning Services\P2PVS.exe.
  2. Specify the drive letter of the newly created partition (or the original boot HDD partition) as the Destination Drive. The destination drive should point to the vDisk first partition by default.
  3. Clone the hard drive image to the vDisk Destination Drive.

Boot from the vDisk

Using the Console, set the target device on the Provisioning Server to boot from vDisk, then reboot the target device. The new target device should now be running the new vDisk image.