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 are not available. Citrix recommends closing all Citrix Provisioning consoles until the upgrade is complete to avoid failed operations. When upgrading a server, the console component is also upgraded.
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
Uninstall Citrix Provisioning server version 1808 before installing version 1811.
- 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.
- Install the Citrix Provisioning console component on this server or on a server used to manage the farm. For details on installing the console, refer to Installing Citrix Provisioning server software.
- In the Configuration Wizard, 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 Citrix 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.
The database upgrade is ignored because the database was upgraded when the first server was upgraded.
Rolling server upgrade
To keep Citrix Provisioning components running during an upgrade, use the rolling server upgrade process. This process upgrades one provisioning server at a time.
When upgrading a provisioning server, it cannot service any target device. Due to this constraint, ensure that the remaining provisioning servers in the environment support client failover from the upgraded server.
To perform the rolling server upgrade, update the first provisioning server in the farm:
- Open the Services snap-in (services.msc) in the MMC and halt the Citrix Provisioning Stream Service. This process causes all targets connected to this provisioning server to fail over to other servers in the farm. Once finished, upgrade the provisioning server and console components.
Upgrade the Citrix Provisioning database. This process is 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 provisioning database.
b. Use the configuration wizard to upgrade the provisioning database. Consider the following:
The Citrix Provisioning configuration wizard automatically starts when the Finish button is selected once the provisioning server has been successfully upgraded.
Use the default settings. These settings ensure that the configuration wizard retains the settings from the previous instance. On the Farm Configuration 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 provisioning server. At this point, if the provisioning database has not been upgraded, a message appears indicating that the database is upgraded. Click OK.
Verify that all Citrix Provisioning services have started as intended using services.msc and boot a target device to confirm connectivity to the provisioning server.
After upgrading the first provisioning server in the farm, upgrade all other servers:
Open the Services snap-in (services.msc) in the MMC and stop the Citrix Provisioning Stream Service. This process causes most (if not all) of the target devices connected to this provisioning server to fail over to the server that has been upgraded. Run the new server and console executables to upgrade the server and console components.
The configuration wizard automatically starts after clicking Finish once the provisioning server has been successfully upgraded.
The provisioning database is updated by the first provisioning server.
Use the default settings. These settings ensure that the configuration wizard retains the settings from the previous instance. On the Farm Configuration 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 provisioning server.
- Repeat steps 3–5 to upgrade all other provisioning servers in the farm after upgrading the first server.