Product Documentation

vDisks

Important:

Backup all vDisks before upgrading 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 Citrix Provisioning 7.6.1 or later, you can do an in-place upgrade. Citrix recommends that you use this method if possible. It involves two steps:

  1. Start the client in private or maintenance mode.
  2. Run the target device installer as described in Preparing a master target device for imaging.

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 Citrix Provisioning 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 Citrix Provisioning 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 Citrix Provisioning 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).

Upgrade a vDisk using Hyper-V

If you are upgrading from Citrix Provisioning 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.

Before upgrading using Microsoft Hyper-V, review the following requirements:

  • General Hyper-V knowledge.
  • Hyper-V must be installed (Hyper-V does not need to be installed on the Provisioning Server).

Note:

Hyper-V upgrade does not support vDisks using 16 MB block size. When creating new vDisk images, the block size should be 2 MB or greater.

  1. On a Hyper-V server, uninstall previously installed Provisioning Services software.
  2. Install the newer version of Citrix Provisioning software.
  3. Copy a newly created VHDX file to the Hyper-V server:
    1. Create a new version of the vDisk.
    2. Promote the new version to test mode.
    3. Perform a merge base to test mode.
    4. Copy the VHDX from step c to the Hyper-V server
  4. Create a new virtual machine in the Hyper-V Manager.
  5. During the creation steps, attach the existing newvDisk.vhdx instead of using a new VHDX.
  6. Go into the properties of the newly created Hyper-V virtual machine (Action panel > Settings) and remove the Network adapter. Go to Add Hardware and add the Legacy NIC.
  7. Go to the Legacy NIC and attach it to the physical system’s NIC.
  8. Boot the virtual machine.
  9. Let the system install the new drivers, then reboot if prompted.
  10. Uninstall Citrix Provisioning target device software, then reboot.
  11. Optional: Install Hyper-V’s Integration Services. This is only necessary when the resulting VHDX must be bootable in both physical and virtual systems. While the virtual machine is on, go to Action, then choose Insert Integration Services set up disk, then install.
  12. Install Citrix Provisioning target device software.
  13. Choose to bind Citix Provisioning to the inactive NIC (the physical NIC from the original target device). When installing target device software on NT6.x systems within a multi-NIC environment, all available NICs can be used. Therefore bindcfg.exe is no longer required and no longer installed with target device software.
  14. Shut down the virtual machine.
  15. Go to the virtual machine’s properties (Action panel > Settings), then set it to boot to the legacy NIC first.
  16. Transfer the VHDX (newvDisk.vhdx) back to the Provisioning Server.
  17. From the Citrix Provisioning Console:
    1. Add the VHDX to the Citrix Provisioning database using the Add existing vDisk menu option.
    2. Add the Hyper-V virtual machine to the list of the target devices.
    3. Associate the vDisk with the appropriate target devices.
    4. Set the vDisk to Standard Image Mode
  18. Boot the physical target device (assuming this is set to PXE first), then the Hyper-V virtual machine.

The original vDisk is now upgraded and a common image for the physical and virtual machines has also been created.

Upgrade a vDisk using Reverse Imaging

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 Citrix Provisioning 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 Citrix Provisioning 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 Citrix Provisioning 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.

Manual reverse imaging using P2PVS

When manually performing reverse imaging using P2PVS, consider the following:

  • Boot the PVS target device into the vDisk using private\maintenance mode.
  • Install PVS_UpgradeWizard.exe or PVS_UpgradeWizard_x64.exe from the Upgrade folder of the ISO image of the latest Provisioning Services release to get the latest P2PVS.exe. The upgrade wizard can also be installed with the Provisioning Services meta-installer using the Target Device Installation > Install Upgrade Wizard option.
  • Run P2PVS.exe from the Citrix Provisioning Upgrade Wizard directory (by default, this directory is C:\Program Files\Citrix\Provisioning Services UpgradeWizard).
  • Click the From drop down menu and choose Provisioning Services vDisk and click Next.
  • In the partition screen, select the partitions that will be reverse imaged. All system partitions, regardless of whether they have a drive letter or not, will be used in reverse imaging. Click Next.
  • Click Convert on the last page to begin reverse imaging.

Note:

Reverse imaging for BIOS systems is non-destructive. The partition table of the system will not be altered. Because PVS imaging is blocked base, the partition table of the local hard disk must be the same as those of the vDisk. Important:

Reverse imaging for UEFI systems is destructive. All partitions on the local hard disk will be destroyed and re-created to match those of the 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 Citrix Provisioning 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.

Note:

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 completed properly, the Provisioning Server will not be able to connect with the vDisk.
  9. Uninstall the product software. For details, refer to the section about removing PVS.

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 destination drive letter of the newly created partition (or the original boot HDD partition) as the vDisk. The vDisk should first point to the destination drive 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 thesection about removing PVS.

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.

Upgrade a target vDisk using in-place upgrade

Use the information contained in this article to upgrade a PVS target device vDisk using the in-place upgrade method.

Important:

This upgrade procedure can only be used for Citrix Provisioning target devices using version 7.6.1 and newer. For Provisioning Services 7.6.1 and newer, the target being upgraded must have been installed using the PVS target install method, and not upgraded using binary replacement.

Boot a target device into private image mode or a maintenance version

Use the information in this section to boot a target device in either private image mode, or to boot in maintenance mode.

Tip:

Before booting from private image mode, Citrix recommends that you backup the vDisk before attempting an upgrade.

Boot in private image mode

  1. Shutdown all other devices.

    Image of pvs Upgrade

  2. Set the vDisk that you want to upgrade to private image mode:

    1. Open the vDisk’s properties dialog by right clicking the vDisk, and choose Properties.

    2. From the Access mode group, select Private Image (single device, read/write access):

      Image of pvs Upgrade

      Image of pvs Upgrade

  3. Boot a target device using that vDisk:

Boot in maintenance mode

  1. Right click the standard mode vDisk and choose the option Versions… to open the vDisk Versions screen.

  2. Click the New button (in the upper right portion of the interface) to create a maintenance vDisk version:

    Image of pvs Upgrade

  3. Set a target device that is using that vDisk to maintenance mode by right clicking on the target, then choose the Properties option.

  4. Choose Maintenance from the drop-down menu for the property type:

    Image of pvs Upgrade

  5. Boot a target device using the specified vDisk version.

  6. Choose option 1 from the boot menu that appears when booting the target device:

    Image of pvs Upgrade

  7. The PVS status tray of the device should resemble:

    Image of pvs Upgrade

Tip:

The virtual disk’s name should be followed by a .x where x is greater than or equal to 1 and the extension should be .avhdx or .avhd.

Upgrade PVS target device software

After booting a device into private image mode or a maintenance version, use the information in this section to upgrade the PVS target device software.

To upgrade PVS target device software:

  1. Log into the target device using local administrator login credentials.
  2. Copy the PVS_Device.exe or PVS_Device_x64.exe to the target device.
  3. Right click the installer and choose Run as administrator.
  4. Run the installer and choose all the options as you would install a fresh version.
  5. Click Finish to begin the upgrade.
  6. Shutdown the target device.
  7. Open the vDisk version interface (refer to step 1 above).
  8. Click Promote to promote the vDisk to either a test or production version:

    Image of pvs Upgrade

    Tip

    The New button should be greyed out and inaccessible.

    1. Test version - This should be used to verify the vDisk is fully operational before promoting it to the production version.

    2. Production version - This represents the version used by all users in a full roll out of the vDisk to the production environment.