Upgrade, modify, and repair System Platform

Upgrade to System Platform 2023 R2: You can upgrade to System Platform 2023 R2 SP1 from System Platform 2017 or newer. If you running a version older than System Platform 2017, you must perform an intermediate upgrade to a version that allows a direct upgrade, and then upgrade to System Platform 2023 R2 SP1.

Migration of Application Server galaxies is supported from all versions, beginning with 4.5, and includes System Platform 2012 and later.

Note: System Platform Enterprise 2023, and System Platform 2020 R2 Controlled Releases 1 and 2 (CR1 and CR2) cannot be upgraded or migrated to System Platform 2023 R2.

The upgrade process lets you upgrade only components that were previously installed. You cannot choose to add components that were not already installed, and you cannot deselect components. That is, if a newer version of a component is included on the installation DVD, the previously installed component is automatically upgraded.

After the upgrade is complete, you can add new components or remove existing components, as needed. To enable Operations Control - connected experience, follow the instructions below, and refer to Galaxy migration to support connected experience before you connect to a galaxy.

Important Upgrade Information

• 64-bit operating system required: A 64-bit operating system is required to install System Platform 2023 R2 SP1.

• 64-bit SQL Server required: For components that require SQL Server, such as Application Server and Historian, you must have a 64-bit version of SQL Server installed.

• .NET Framework: System Platform 2023 R2 SP1 requires .NET Framework 4.8. If your system does not have this version or a newer version installed, the .NET Framework will be installed prior to product installation. A restart may be required, after which setup.exe will resume automatically. See System Platform prerequisites for additional information.

• Licensing Change: If you are upgrading from System Platform 2014 R2 SP1,you will need to upgrade first to System Platform 2017 as an intermediate step. You will be changing to the new licensing system. This new "Activated License System" requires a License Server to be hosted on a machine that can be accessed by all nodes in the system. Additional license servers can be installed for more granular licensing management or redundancy.

  Since the License Server is a new component, it is not added during the upgrade process. Upgrade the Galaxy Repository node first, and then use the Modify workflow to add the License Server after the node has been upgraded. See License Installation and Activation for additional information.

  Only one License Server is required per overall system.

  Note: The Galaxy Repository node is the default installation location for the License Server. You can, however, select a different node, or install the License Server on a standalone node, depending on your system size and architecture.

• Network Account: In System Platform 2017 Update 2 and prior releases, the Network Account was a member of the system Administrators group. Starting with System Platform 2017 Update 3, the Network Account was removed from the Administrators group to enhance system security.

  When you upgrade from System Platform 2017 Update 2 or an earlier version, a security warning asks if you want to remove the Network Account from the Administrators group. This is the best option for security. However, you can leave the Network Account as a system administrator, if the account is used by another application and if removing administrator rights will affect that application.

• AVEVA System Monitor: The System Monitor Manager tracks the availability of the License Server and provides email notification of its status to ensure uninterrupted system operations. A System Monitor agent is installed on each node and communicates with the System Monitor Manager if there is an issue with the connection between the System Platform node and the License Server.

  The System Monitor Manager is not automatically added during the upgrade process. To add the System Monitor Manager, upgrade the Galaxy Repository node first, and then use the Modify workflow to add the System Monitor Manager when the upgrade completes. The System Monitor agent is automatically added to each upgraded node. Configure the System Monitor agent on each remote node to point to the System Monitor Manager. See Configure AVEVA System Monitor for additional information.

  Only one System Monitor Manager is required per overall system.

• Application Server: Every redundant Application Server run-time node must use the System Management Server if data is being historized. Redundant nodes have an instance of HCAP running, which is used to synchronize tags and store-and-forward data between redundant AppEngines. As of of System Platform 2023 R2, secure communication is required for HCAP, and thus, redundant nodes will not be able to synchronize data without the SMS.

• InTouch Access Anywhere: If you plan to upgrade System Platform on a computer that has InTouch Access Anywhere Server or InTouch Access Anywhere Gateway installed, you must first uninstall the InTouch Access Anywhere Server or Gateway. After you upgrade System Platform, you can reinstall InTouch Access Anywhere. See Upgrading InTouch Access Anywhere for details.

• Common Platform: The System Management Server, a security component, was added for System Platform 2017 Update 3. If you are upgrading from a prior version that did not have the System Management Server, it is automatically installed on the GR node when you upgrade to System Platform 2023 R2 SP1. There should be only one System Management Server in your System Platform topology, and every node should be configured to point to it. See System Management Server for additional information. If some nodes will not be upgraded, communication with non-upgraded nodes will continue to use legacy communication protocols.

  In multi-galaxy environments, configure only one GR node as the System Management Server, and configure the other nodes to point to it.

  If the System Management Server is not configured for redundant Application Server nodes, there will be data loss, as well as warnings and error messages.

About the Modify Workflow

The upgrade process can only upgrade System Platform components that are already installed on your system. Since upgrading may introduce new components that were not part of prior releases, you need to run setup.exe and launch the Modify option to install new components that may not have been available in prior versions of System Platform. The components that you may need to install through the Modify option include:

• AVEVA System Monitor Manager

• AVEVA License Server

To add components through the Modify option

1. Upgrade the node and configure it.

2. Run the installation program again from the installation DVD (setup.exe).

3. Select the Modify option.

4. Select the component(s) you want to install.

To upgrade a System Platform component

Note: Upgrade the GR node first, followed by remote IDE nodes, and then run-time nodes. See Upgrade an IDE-only node and Upgrade runtime nodes for additional information.

5. Run setup.exe to start the set-up program. The startup screen appears, followed by the upgrade feature dialog box that lists any prerequisites and products and versions to be upgraded. If a new version of the .NET Framework is required, it is installed first and then setup resumes after a restart.

   

   Note: You can only upgrade the products that are already installed, and you will not be able to install additional products during the upgrade process.

6. Confirm your operating system compatibility, then click Next to proceed.

7. A selection list of the products and components to be upgraded is shown. You cannot modify this list. Click Next to proceed.

8. Perform any recommended actions, such as backing up your galaxy, then click Next to proceed.

9. If required, OI servers are upgraded, then galaxy updates begin after the OI servers are upgraded. If prompted, click the Stop Services button to proceed.

10. After all services stop, click Next to proceed.

11. The list of products that will be upgraded is shown. Click Upgrade to begin upgrading your system.

12. After the installation is over, the Configurator starts. Some items that were previously configured retain their configurations, but you will need to reconfigure certain items including the System Management Server and the Historian (if present).

13. Important! If you are upgrading from System Platform 2023 and are using Operations Control - connected experience, and have an existing galaxy that uses the Authentication providers security option with Azure AD, you will need to follow the configuration instructions as described in Galaxy migration to support connected experience.

    Select View Readme for important information about System Platform 2023 R2 SP1, including hardware and software requirements, new features, and known and resolved issues.

    Note: You may see a Cybersecurity Notice that instances of a Microsoft XML processing library were found. For information on removing MSMXML 4.0, see the Microsoft Support web page:
    https://support.microsoft.com/en-us/topic/ms06-061-security-update-for-microsoft-xml-core-services-4-0-sp2-21c429e2-0349-30e5-189a-ca32aea6c2dd

If you a galaxy is deployed, the Galaxy Patcher will start as soon as you connect to the galaxy from the System Platform IDE. Undeployed galaxies are not patched until you connect to them.

Important: Galaxy patching may take several minutes. Do not shut down the node while the patching operation is in progress.