Product Documentation

Servers

In a Citrix Provisioning farm, the database is upgraded at the same time that the first Provisioning Server is upgraded. After upgrading the database and the first server in the farm, you can upgrade the remaining servers within the farm. While the first Provisioning Server is being upgraded, some administrative features may not be available. Citrix recommends closing all Consoles until the upgrade is complete in order to avoid failed operations. When upgrading a server, the Console component is also upgraded.

Note:

The Upgrade Wizard must be installed and run in a folder that does not contain surrogate pair characters (Unicode code point after 0x10000).

Upgrading the first Provisioning Server

To upgrade:

  1. To upgrade the server and database, run the new version of the server software on the server, then select the “Automatically close and attempt to restart applications” option. If this option is not selected and a “File in use” screen displays, select the “Do not close applications option.”
  2. Install the Console on this server or on a server that will be used to manage the farm. For details on installing the Console, refer to Installing Provisioning Services Server Software.
  3. In the Configuration Wizard (if the wizard does not start automatically after completing the product installation, start it now), select the option to join a farm that is already configured. Running the wizard starts the services. For details, refer to the instructions on how to join an existing farm in Configuration Wizard Tasks.

Upgrading remaining Provisioning Servers in the farm

Complete the same procedure that was performed on the first server on each of the remaining servers in the farm.

Tip:

The database upgrade is ignored because the database was upgraded when the first server was upgraded.

Rolling server upgrade

To keep Citrix Provisoning components running during an upgrade, use the rolling server upgrade process. This process upgrades one PVS server at a time.

Tip:

When upgrading a PVS server, it cannot service any PVS target device. Due to this constraint, ensure that the remaining PVS servers in the environment support PVS client failover from the upgraded PVS server.

To perform the rolling server upgrade, update the first PVS server in the farm:

  1. 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.
  2. Upgrade the PVS database. This process only needs to be done one time. There are two ways to upgrade the database:

    a. Use dbScript.exe to generate a SQL script (select the option to upgrade the database and enter the name associated with it), then use the script in SQL Management or the SQL command line to upgrade the PVS database.

    b. Use the configuration wizard to upgrade the PVS database. Consider the following:

    The PVS configuration wizard automatically starts when the Finish button is selected once the PVS server has been successfully upgraded.

    Use the default settings. This ensures that the PVS configuration wizard retains the settings from the previous instance. On the Farm Configuraiton page, ensure that the option Farm is already configured is selected. After all configuration information is collected, review the information on the Finish page and click Finish to begin configuring the PVS server. At this point, if the PVS database has not been upgraded, a message appears indicating that the database will be upgraded. Click OK.

    Verify that all PVS services have started as intended using services.msc and boot a target device to confirm connectivity to the PVS server.

    After upgrading the first PVS server in the farm, upgrade all other PVS servers:

  3. Open the services MMC file (services.msc) and stop the Citrix PVS Stream Service. This causes most (if not all) of the PVS target devices connected to this PVS server to failover to the PVS server that has just been upgraded; run the new PVS server and console executables to upgrade the PVS server and console components.

  4. The PVS configuration wizard automatically starts after clicking Finish once the PVS server has been successfully upgraded.

    Note:

    The PVS database is only updated by the first PVS server.

  5. Use the default settings. This ensures that the PVS configuration wizard retains the settings from the previous instance. On the Farm Configuraiton page, ensure that the option Farm is already configured is selected. After all configuration information is collected, review the information on the Finish page and click Finish to begin configuring the PVS server.

  6. Repeat steps 1-3 to upgrade all other PVS servers in the farm after upgrading the first PVS server.