Upgrade System Platform
- Last UpdatedSep 25, 2026
- 3 minute read
Before you begin
-
Back up the Galaxy.
-
Verify that the operating system and SQL Server meet version requirements.
-
Install any required prerequisite software (for example, .NET Framework).
-
Verify access to the License Server from all nodes.
-
Upload any applicable runtime changes for critical objects.
-
Ensure there are no active connections to the Galaxy database.
-
Review Important upgrade information.
Upgrade order
Perform the upgrade in the following order:
-
Upgrade prerequisite software (OS and SQL Server).
-
Upgrade the Galaxy Repository (GR) node.
-
Upgrade IDE nodes.
-
Migrate the Galaxy database.
-
Upgrade runtime nodes.
Upgrade procedure
-
Either undeploy the platform, or use the Operations Control Management Console (OCMC) Platform Manager to stop the platform.
If you choose to stop the platform instead of undeploying it, undeploy any WebViewEngines running on the platform before you stop the platform.
-
Exit all System Platform applications, such as:
-
System Platform IDE
-
OCMC
-
AVEVA OMI ViewApps
-
InTouch HMI WindowMaker
-
InTouch HMI WindowViewer
Notes: Web OMI is not supported with the No SMS configuration.
During the upgrade, the following warnings related to vcp.services.onprem.dataaccess are logged when the WebViewEngine is in the deployed state.
If you skip the initial steps to undeploy and exit applications, you may see warning messages related to the Data Access service in the logs after you complete the upgrade and restart the system. The warnings indicate that the application cannot connect to the MxDataProvider service and cannot create an initial runtime data client.
-
-
Run setup.exe to start the setup program. The startup screen appears, followed by the upgrade feature dialog box that lists the products and versions to be upgraded. Review the list and click OK.
If a new version of the .NET Framework is required, the installer installs it first and then resumes setup after a restart.
-
Confirm operating system compatibility, and then select Next.
-
Review the products and components to upgrade. You cannot modify this list during the upgrade. Select Next.
-
Perform any recommended actions, such as backing up your galaxy, and then select Next.
-
If your system uses OI servers, upgrade them now. Galaxy updates begin after the OI server upgrade. If the installer prompts you, select Stop Services.
-
After all services stop, select Next.
-
Review the list of products to be upgraded, and then select Upgrade. Installation begins.
-
After the installation finishes, the Configurator starts. Review and update any required configurations. Some items retain their existing configuration, but you must reconfigure the System Management Server and the Historian, if present.
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, you will need to follow the configuration instructions as described in Galaxy migration to support connected experience.
A Cybersecurity Notice may appear if instances of a Microsoft XML processing library are 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 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.
Results
After you complete the upgrade procedure:
-
System Platform is upgraded to version 2023 R2 SP2.
-
All items are configured in the Configurator.
-
The galaxy can be opened successfully in the IDE.
-
Required services are running.
-
Runtime nodes can communicate with the galaxy.