Provisioning Services supports upgrading to the latest product version from versions starting with 7.6 LTSR.
Before attempting to upgrade a Provisioning Services farm:
- Select a maintenance window that has the least amount of traffic
- Back up the Provisioning Services database
- Back up all vDisks
Mirror if you are in a high-availability scenario; for more information, see Database Mirroring. No special action is required during the upgrade once mirroring is set up.
When upgrading Provisioning Services, consider the following:
- Upgrade to the latest licensing server. Note the following when upgrading the license server:
- License servers are backward compatible and provide the latest security fixes.
- If necessary, upgrade individual licenses. New Provisioning Services features require that the Citrix license have a minimum subscription advantage (SA) date.
- Back up the Provisioning Services database. While Citrix always tests to ensure a successful database upgrade, unforseen circumstances may arise. Citrix strongly recommends that you backup the database prior to upgrading.
- Back up the Provisioning Services vDisk. Citrix recommends that you backup the vDisk prior to upgrading. This is only necessary if you plan to use reverse imaging with private images.
- When running the installer to update either the server or console components, if an older version of Provisioning Services is detected both components are automatically updated.
Upgrading Provisioning Services requires local administrator privileges.
Upgrade the environment
To upgrade from a previous Provisioning Services farm, complete the following procedures:
- Upgrade the first Provisioning Server, which upgrades the Provisioning Services database.
- Upgrade Consoles. The Console is a separate executable that can be installed on upgraded servers (PVS_Console.exe or PVS_Console_64.exe). Citrix recommends upgrading Provisioning Services server and console software at the same time for each Provisioning Server system in the farm. Remote Consoles can be upgraded at any time.
- Upgrade the remaining Provisioning Servers within the farm.
- Upgrade vDisks.
If you are upgrading a Provisioning Services vDisk within a XenDesktop deployment, upgrade the Provisioning Services master target device software before upgrading the XenDesktop VDA software.
The Upgrade Wizard includes the following utilities:
- The UpgradeAgent.exe runs on the target device to upgrade previously installed product software.
- The UpgradeManager.exe runs on the Provisioning Server to control the upgrade process on the target device.
Upgrading at a glance
The information in this section provides step-by-step guidance for upgrading Provisioning Services components. For server upgrade information, see the serverarticle. For information about upgrading vDisks, see thevDisksarticle.
Upgrade the server and console
Follow these steps to upgrade the server and console:
Run the server and console executables to initiate the upgrade process automatically. Citrix recommends that you upgrade the console first, followed by the server.
To keep the Provisioning Services farm and target devices running during the upgrade process, use the rolling server upgrade procedure.This process upgrades one PVS server at a time.
The rolling server upgrade performs an upgrade on one server at a time.
While the PVS server is upgraded, it cannot service any PVS target device. As a result of this limitation, ensure that the remaining PVS servers in the farm have the ability to support the PVS target devices (clients) during the failover process while the server is being upgraded.
To perform the rolling upgrade, update the first PVS server in the farm:
a. Open the services MSC file (services.msc) and halt the Citrix PVS Stream Service. This causes all PVS targets connected to this PVS server to failover to other PVS servers in the farm. Once finished, upgrade the PVS server and console components.
b. Upgrade the PVS database. This will only have to be done once. There are two ways to do this:
- Use dbScript.exe to generate the SQL script (choose the option to upgrade database and enter the name of the dB) and then use that script in SQL Management or SQL command line to upgrade the PVS database.
- Use configuration wizard to upgrade the PVS database; when using this method, consider:
- The PVS configuration wizard automatically starts when the Finish button is selected once the PVS server is successfully upgraded.
- Use the default settings so that the PVS configuration wizard uses the previously configured settings. On the Farm Configuration page, select the option ‘Farm is already configured’. After all configuration information is entered, review the information on the Finish page; click Finish to being configuring the PVS server. At this point, the PVS database is not configured; a message appears indicating that the database will now be upgraded. Click OK to confirm the message to upgrade the database.
- Verify that all PVS services have started using services.msc; boot a target device to confirm that it can connect to the PVS server.
Upgrade remaining PVS servers
After upgrading the first PVS server, upgrade the remaining PVS servers in the farm:
Open the services MSC file (services.msc) and halt the Citrix PVS Stream Service. This causes all PVS targets connected to this PVS server to failover to other PVS servers in the farm. Once finished, upgrade the PVS server and console components.
Once the server is successfully upgraded, the PVS configuraiton wizard starts automatically after clicking Finish. The PVS database is only updated after the FIRST PVS server has been upgraded.
Use the default settings. The PVS configuration wizard uses the previously configured settings. On the Farm Configuration page, make sure that the option ‘Farm is already configured’ is selected. After all configuration information is entered, review the information on the Finish page; click Finish to being configuring the PVS server.
Repeat these steps to finish upgrading all remaining PVS servers in the farm.
Rebalance PVS clients
After upgrading and configuring all PVS servers, Citrix recommends that you rebalance all PVS clients (target devices) with the farm. To rebalance PVS clients:
- Start the PVS console and log into the PVS farm.
- Navigate to the Servers tab.
- Highlight all the PVS servers that were recently upgraded, right click to expose a contextual menu.
- Select Rebalance clients.
Upgrade the PVS target device
Provisioning Services supports three methods of upgrading target devices:
- In-place upgrade
- Direct VHD\VHDX boot
- Manual upgrade using reverse imaging
Citrix strongly recommends that you backup the vDisk if versioning is not used in the upgrade process.
When using Provisioning Services target installers:
- If the system is running PVS version 7.6.2 (7.6 CU1) or a newer target device, run the new PVS target installer (the same version installed on the target device); this effectively allows the installer to take care of the upgrade.
- If the system is running PVS version 7.6.1 or earlier target devices, uninstall the old PVS target device software, reboot, then install the new PVS target device version.
For in-place upgrades, a maintenance version of the vDisk is interchangeable with the private image. However, Citrix recommends that you take advantage of the PVS versioning to perform an in-place upgrade.
To perform an in-place upgrade:
- Create a maintenance version of the vDisk.
- Using the PVS console, navigate to the device’s properties and set the device type to Maintenance.
- In the Boot menu, select option 1 to boot a client into vDisk mode using the maintenance version.
- Log into Windows and run the new PVS target device installer; install the software in its entirety, as if you would perform a full installation. The target device installer performs the upgrade; do not run the imaging wizard. Reboot the target device when prompted.
- Once Windows has loaded, log into the system and verify that the target device software is the expected version by viewing the PVS status tray. Note that the PVS status tray may be hidden by Windows. To find it, click the up arrow in the on the staus tray icon.
- Shutdown the PVS target device.
- If versioning is invoked, use the PVS console to promote the maintenance version to test version functionality. Verify the new version and promote it to the production version when it is deemed production quality. Roll this version out to users by rebooting all the target devices using this vDisk.
Upgrading using VHD\VHDX boot
When using method to upgrade a target device, consider:
- XenServer only supports .vhd
- Hyper-V 2012 and 2008 R2 only supports .vhd
- Hyper-V 2012 R2 and 2016 supports both .vhd and .vhdx
Obtain the .vhdx file. Consider:
- If the vDisk does not have a version, copy the .vhdx file to the Hyper-V server or import the file to XenServer using XenCenter (Files>Import).
- If the vDisk has a version, perform a base merge and create a .vhdx file in maintenance mode.
Perform a direct VHD boot using XenServer:
a. Copy the .vhd file to a system running XenCenter and import the file to XenServer using Files>Import.
b. Create a VM using the imported .vhd file. Refer to the ‘Importing and Exporting VMs’ section of the XenServer documentation for more information.
c. Boot the VM.
d. Upgrade the target device software. Refer to the information at the beginning of this section for using the PVS target device installers.
Perform a direct VHD\VHDX boot using Hyper-V:
Copy the .vhdx file to the Hyper-V server, or
Create a new Hyper-V VM using the “Use an existing virtual hard disk” and point to the .vhdx file. Refer the following links for creating VMs in Hyper-V. For Hyper-V 2012 R2 and 2016, ensure that the generation of the VM matches those of the vDisk:
- Generation 1 = traditional BIOS VMs and systems
- Generation 2 = UEFI VMs and systems
For Hyper-V 2016 environments:
For Hyper-V 2012 and 2012 R2:
For Hyper-V 2008 R2 and 2008 R2 Sp1:
Boot the VM.
Upgrade the target device software. Upgrade the target device software. Refer to the information at the beginning of this section for using the PVS target device installers.
Copy the .vhdx.vhd file back to the vDisk store location where it was originally located:
- If the .vhdx.vhd file is taken from a based merge version, the file is ready for testing and verification.
- If the file is copied from the base vDisk, import the vDisk into the PVS database using the Add or import Existing vDisk option which is run from the vDisk Pool\Store level in the PVS Console.
Upgrading using manual reverse imaging with P2PVS
Use the information in this section to upgrade PVS using reverse imaging with P2PVS.
The table below illustrates supported upgrade methods:
|Reverse imaging method||Xen tools||VM tools||Hyper-V compatibility||NIC driver||Windows 10 upgrade||Anti-virus updates||Firewall/Network security software|
|P2PVS reverse imaging||x||x||x||x||x||x||x|
|VHD boot from hypervisor||x||x||x||x|
|Direct VHD boot||x||x||x||x||x||x|
Boot the PVS target device into the vDisk using private\maintenance mode.
Install PVS_UpgradeWizard.exe of PVS_UpgradeWizard_x64.exe from the Upgrade folder of the ISO image; this folder is located in the latest Provisioning Services release area (containing the latest P2PVS.exe file). The upgrade wizard can also be installed through the PVS meta-installer using the Target Device Installation > Install Upgrade Wizard option.
Run P2PVS.exe from the PVS upgrade wizard directory; by default, this file is located in C:\Program Files\Citrix\Provisioning Services Upgrade Wizard.
Click the From drop down menu to choose the PVS vDisk. Click Next.
In the partition screen, select the partitions that will undergoe reverse imaging. 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 final page to being reverse imaging.
When using reverse imaging, consider:
- reverse imaging for BIOS systems is non-destructive. The partition table of the system is not altered. Because PVS imaging is blocked base, the partition table of the local hard disk must be the same as those of the vDisk.
- 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.
Once reverse imaging finishes, reboot the VM from hard diskk without network booting.
Upgrade the target device. Refer to the information at the beginning of this section for more information.
Image the OS to vDisk again. You can accomplish this by creating a new vDisk or using the existing one.
Using reverse imaging to upgrade Windows 10 machines
To upgrade a Windows 10 image using reverse imaging:
- Create a target device with a virtual hard disk that is the same size or bigger than the vDisk.
- Network boot (PXE/ISO) the VM into the vDisk using maintenance version or private image mode.
- If the vDisk is using Provisioning Services 7.15.x or older, install PVS_UpgradeWizard.exe or PVS_UpgradeWizard\x64.exe from the Upgrade folder of the ISO image representing the latest Provisioning Services release to get the latest P2PVS.exe file. 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 Provisioning Services target device\ Upgrade Wizard directory; by default, this directory is C:\Program Files\Citrix\Provisioning Services, or C:\Program Files\Citrix\Provisioning Services Upgrade Wizard, respectively.
- 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.
- Once reverse imaging has successfully completed, set the VM to boot from HDD and reboot the VM.
- Uninstall the Provisioning Services target device.
- Shutdown the VM.
The amount of free space in the c:\ partition. Some used space can be freed up by deleting the Windows.old folder in C:. Refer to the Windows Support page for more information.
- Judging by the free space on the C:\ partition, increase the size of the VM’s hard disk if needed.
If this operating system is Windows 10 1607 (code name Redstone 1 or Anniversary Update), Windows 10 update will create another system partition after the C:\ partition. At this time, it is not possible to increase the size of C:\ partition.
- Boot the VM. Please note the local admin of the VM and remember the local admin password.
- Run Windows 10 update to upgrade Windows 10.
- You may have to use rlocal admin credentials to log in since the Windows 10 upgrade process can impact active directory.
- Rejoin the VM to active directory if needed.
- Install new drivers and more Windows updates if needed.
- Once updates are done, install Provisioning Services target device software.
- Use the Imaging Wizard or P2PVS to create a new vDisk. The old vDisk can be used if the size of the VM’s virtual hard disk has not been increased in step 11.