Upgrade Deployment from Plant SCADA 2020 R2

The deployment architecture installed with Plant SCADA 2023 and 2023 R2 is no longer compatible with deployment servers running an earlier version. This means:

• You cannot use a 2023 R2 version of Plant SCADA Studio to add projects to a deployment server that is running Plant SCADA 2020 R2 (or earlier).

• You cannot deploy a project from a deployment server running 2023 R2 to a deployment client that is running Plant SCADA 2020 R2 (or earlier).

If you have a distributed system that includes some computers on Plant SCADA 2020 R2 (or earlier), you should retain your existing deployment server to distribute projects to these computers until the roll out of 2023 R2 is complete. You will also need to configure a new deployment server to deploy 2023 R2 projects to any upgraded computers.

Note: If you want to maintain your existing deployment server and client configurations from 2020 R2 (or earlier), you need to confirm that you have a backup of the Plant SCADA \Config folder (for example, C:\ProgramData\AVEVA Plant SCADA 2020 R2\Config) prior to upgrading to version 2023 R2.

Additional steps are required if you are upgrading deployment directly from Citect SCADA 2018 to Plant SCADA 2023 R2. For more information, see Upgrade deployment directly from Citect SCADA 2018 below.

To migrate your deployment configuration from 2020 R2 (or earlier) to a 2023 R2 deployment server.

1. Confirm the System Management Server configuration has been upgraded correctly.

2. In Configurator, confirm that Computer Setup is configured correctly.

3. On Configurator's Deployment Server page, select Import Configuration file from previous version of Deployment Server.

   If this option is not available, you need to close Configurator and delete the following files from Plant SCADA's \Config folder:

   • For a deployment client, delete:

     SE.Asb.Deployment.Node.WindowsService.exe.config

   • For a deployment server, delete:

     SE.Asb.Deployment.Server.WindowsService.exe.config.

     You then need to restart Configurator and attempt step 3 again.

4. Using the browse dialog, locate the deployment server configuration file from your previous version. For example:

   C:\ProgramData\AVEVA Plant SCADA 2020 R2\Config\
   SE.Asb.Deployment.Server.WindowsService.exe.config

5. Open the file.

6. Click the Configure button to complete configuration of the deployment server.

The same steps should be taken for configuration of the new deployment clients.

When you check the Computer Setup settings for a deployment client in Configurator, confirm that the Run the project deployed from the Deployment Server setting is selected, otherwise the deployment client will not appear in Plant SCADA Studio's Deployment view.

Upgrade deployment directly from Citect SCADA 2018

In this scenario, a deployment server from Citect SCADA 2018 will have taken port 443 by default. The following warning message displays if the 2023 R2 System Management Server is also configured with the default port 443.

If this occurs, you need to select Yes to enable the new System Management Server to take over the deployment certificate authority role. This also allows your deployment history to be persisted.

You can then follow the step in the procedure above.

See Also

Install a Deployment Server