Before you run the patch installation program

Before starting the patch installation program, be sure you have completed all of the following:

• Check anti-virus exclusion recommendations. Antivirus software should be implemented as part of a defense-in-depth strategy to secure System Platform. TechNote TN000032662, available from the AVEVA Global Customer Support (GCS) web site, describes important configuration information applicable to antivirus software. Enter your GCS credentials to access the Tech Note.

  https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000032662

• Create known good backups of all Galaxies (both deployed and undeployed). To create a backup of a Galaxy, access the Galaxy Database Manager in the Operations Control Management Console (OCMC). In the OCMC, expand Galaxy Database Manager and select the Galaxy. On the Action menu, select Backup. Follow the prompts to complete the backup operation for each Galaxy.

• If you use a custom branding image file, back it up so you can restore it later. The IDE watermark image file is overwritten during the installation of the System Platform patch. The image file, typically a .png file such as IDEWatermark.png, is located under:

  C:\Program Files (x86)\Common Files\ArchestrA\ApplicationServer\4.1.06000\Branding

• We recommend that you undeploy the platform or stop the platform from the OCMC Platform Manager.

  IMPORTANT! If you choose to stop the platform instead of undeploying it, you must UNDEPLOY any WebViewEngines hosted on the platform before you stop the platform.

• Exit all applications including the System Platform IDE, OCMC, AVEVA OMI ViewApps, InTouch HMI WindowMaker, and InTouch HMI WindowViewer, if installed and running.

• Make sure that any active remote IDE sessions are disconnected from the Galaxy Repository node. This patch requires that you manually shut down certain System Platform-related processes. A reboot may be required. For systems where the IDE is on one node and connects to a remote node with the Galaxy Repository, both the IDE and GR nodes must be at the same version. Ensure the versions are the same by patching all nodes. In general, you should patch the GR node first, then patch run-time nodes.

• We recommend that you stop Historian processes. After stopping the processes, use the OCMC to shut down and disable the Historian. To do so: In the left pane, expand the Historian node to see Historian Groups, then list the groups. Select the group to disable. In the right pane, right-click Management Console and select All Tasks, then Shut down (and disable) historian.

• Make sure the following AVEVA and Microsoft applications are closed:

  Note: If any processes or services are blocking patch installation, the patch install utility will prompt you to close them.

  • InTouch WindowViewer

  • InTouch WindowMaker

  • System Platform IDE

  • Alarm Printer

  • Any applications hosting Alarm Manager (Platform/WindowViewer)

  • Alarm DB Purge/Archive utility

  • Alarm DB Restore utility

  • Alarm Hot Backup Manager utility

  • Alarm DB Logger Manager utility (stop and close)

  • Historical Data Manager utility

  • Recipe Manager utility

  • InTouch Application Manager

  • All instances of InTouch OMI ViewApps

  • All instances of AVEVA OMI VIewApps

  • AVEVA OMI Application Manager

  • AVEVA Configurator utility

  • Operations Control Management Console (OCMC)

  • Microsoft Excel

  • Microsoft Word

  • LogFlagEditor utility

  • Microsoft Management Console (MMC)

    Note: The Control Panel Services window runs in the MMC.

• Unblock the installation media. See Unblock media for details.