Important Information
Before upgrading Parallels Remote Application Server to v22, please review the known issues, terminology updates, software requirements, and license requirements:
- Parallels Remote Application Server v22 Release Notes
- Software requirements
- Microsoft license requirements
- Supported providers for VDI
Note:
- During the upgrade of the Secure Gateways, all tunneled sessions are terminated.
- Until the session host agents, including RD Session Host, Remote PC, and VDI guest agents, are upgraded, it will not be possible to establish new sessions to them. Session hosts that require high availability should be prioritized during Stage 3.
- RD Session Host, Remote PC, and VDI guest agents can be upgraded using the Auto-upgrade functionality where supported.
Upgrade Paths
Direct upgrades from RAS v20.x and v21.x to RAS v22.x are supported.
For RAS v19.x, upgrade to a supported intermediate version before upgrading to RAS v22.x.
Direct upgrade from RAS v16.2 and earlier to RAS v22.x is not supported. Upgrade through the following phases:
- Phase 1: Upgrade from Remote Application Server v16.2 or earlier to v17.
- Phase 2: Upgrade from Remote Application Server v17 to v19.
- Phase 3: Upgrade from Remote Application Server v19 to v20.
- Phase 4: Upgrade from Remote Application Server v20 to v21.
- Phase 5: Upgrade from Remote Application Server v21 to v22.
Upgrade from Version 20.x or 21.x to 22.x
Scenario 1: Single Connection Broker
If your environment includes only one Connection Broker, upgrade directly to version 22.x.
Scenario 2: Multiple Connection Brokers
If your environment includes two or more Connection Brokers and uses RDSH, VDI, or AVD host pools and templates, complete the following steps to prevent data loss:
- On all secondary Connection Brokers, stop the following services:
- Redundancy Service
- Connection Broker Service
- Provider Agent Service
- Upgrade the primary Connection Broker to version 22.x.
- Upgrade each secondary Connection Broker to version 22.x.
- Restart all previously stopped services on each Connection Broker.
- Verify that all services are running correctly across all Connection Brokers.
Stage 1: Upgrade Preparation
- Read the RAS v22 release notes to review all changes, known issues, and added features for the latest version:
- Ensure that your Parallels Remote Application Server license has valid upgrade insurance. Upgrade insurance is not automatically included with a Support contract.
- Take snapshots of environments configured on virtual servers, primarily the server hosting the license server.
- Copy and save the license key activated on the current installation from RAS Console > Licensing.
- Collect additional information about the current Remote Application Server installation from RAS Console > Help > About.
- Export the configuration file and save it to another location.
Stage 2: Upgrade Requirements
- Internet access is required on the Parallels RAS Console server to install the software and activate the license.
- For all upgrades, it is highly recommended to schedule a time when your users are not active on the system.
- Older versions of Parallels Reporting are not compatible with newer versions of Parallels Remote Application Server. You can download the corresponding version of RAS Reporting here.
- Older versions of HALB are not compatible with newer versions of Parallels Remote Application Server. You can download the corresponding version of HALB here.
Stage 3: Upgrade Procedure
-
Start the upgrade from the RAS Console by going to Administration > Settings > Check for Updates > Check Now.
You can also download the installer here.
Run the installer to upgrade the primary Connection Broker. A reboot may be required to complete the installation.
-
After upgrading the primary Connection Broker, upgrade the secondary Connection Brokers, followed by the remaining components.
Once a secondary Connection Broker is upgraded, reboot the server if required.
You can then upgrade the remaining Parallels Remote Application Server agents configured in the farm or site. - Upgrade the Enrollment Server agents and Secure Gateway agents.
- Ensure that all agents are verified and in an OK state.
- Upgrade the templates for RD Session Host, VDI, and AVD. This step requires that the templates be placed in maintenance mode. After the templates are upgraded, guest recreation can be scheduled to clone machines from the updated templates.
- Upgrade static RD Session Hosts, VDI hosts, AVD hosts, and Remote PCs. Hosts that are part of host pools can be upgraded using the Auto-upgrade feature. For more information, click here.
- Upgrading secondary sites:
If you have a multi-site farm:- From the left pane in the RAS Console, select Farm.
- In the list, select the farm, right-click the secondary site, and select Check Agent > Update.
- Once the secondary site is updated, switch to that site and first update the secondary Connection Broker, followed by the remaining components.
Note:
Upon launch, the RAS Console will ask you to specify the farm to which you want to connect.
You may select a farm to which you previously connected or specify the hostname of the licensing Connection Broker. You can use localhost if you are running the RAS Console on the same machine where the RAS Core services are installed.
Stage 4: Final Checks
- Make sure that all servers with Parallels Remote Application Server components have been rebooted if required.
- Log in to the RAS Console and check that all agents are green and verified.
- Log in to the RAS Console and check the license information under Parallels RAS Console > Licensing. Also ensure that the Concurrent UBL information matches the number of user licenses purchased.
Additional Information
If you require support during or after your upgrade, please contact the Parallels Support Team.
Was this article helpful?
Tell us how we can improve it.