Installing System Platform

IMPORTANT! We strongly recommend that you log into Windows as a user with administrative privileges when launching setup.exe. Once all selected System Platform products are installed and configured, you can use a lower-privileged account to operate the system.

If you use a standard user account with temporary administrator credentials instead of an administrator account to run setup.exe, a registry flag associated with the temporary administrator account may remain after the system prompts for a mid-installation restart. This flag is used to notify the operating system that setup should resume the next time that particular user logs into the system. Since product installation may have already completed the next time the user logs in, the "modify" setup screen appears instead. If this occurs, simply cancel the modify setup screen. This scenario, if it occurs, will only happen once, since the registry flag will be cleared. This will not affect the products or their installation.

You can select a product-based or a role-based installation for your computer.

Note: Prerequisites are installed as part of product installation and not in a separate workflow.

Compatibility Alert

If AVEVA™ Manufacturing Execution System or certain versions of AVEVA™ Recipe Management are detected on the node, you will be prompted during installation to apply a patch to the products to ensure compatibility with System Platform 2023. The patch is required for:

• Manufacturing Execution System 6.2.0. Older versions must be updated to version 6.2 and then patched.

• Recipe Management 4.5.0 and 4.6.0. These two most recent versions must be patched. Versions prior to 4.5 are compatible with System Platform 2023 and do not require patching.

Workspace Feature Notification for the OMI and InTouch HMI Web Client

The AVEVA Historian search and elastic search features are installed to support the Workspace feature for the Operations Management Interface (OMI) and InTouch HMI Web Client. Workspace is available if you are using Flex licensing. Therefore, after installation, you may see AVEVA Historian listed as a Windows program, even if you did not install the Historian. Do not uninstall Historian. You can use the Modify workflow to restore the Historian search and elastic search features if you inadvertently uninstalled Historian.

To install System Platform

Note: Use these instructions to install System Platform Enterprise 2023 as well as System Platform 2023. System Platform Enterprise provides additional cloud-based capabilities and is supplied separately, on a different DVD.

1. Insert the DVD into your DVD-ROM drive. Navigate to the root directory of the DVD and run setup.exe. Depending on your computer's security settings, Windows User Access Control may ask for permission to run the installation program. Allow it to run, and the startup screen appears.

   If your computer is configured to allow AutoRun, setup.exe may start immediately after inserting the DVD.

   • If the operating system is not supported, you are blocked from continuing. A 64-bit operating system is required. For additional information about supported operating systems, see Supported Operating Systems for System Platform 2023.

   • If the operating system is supported, basic installation requirements are checked. .NET Framework 4.8 is installed if it or a later version is not already present.

     Note: You are prompted to restart your computer after the .NET Framework is installed. You may need to manually restart the setup program. If the .NET Framework does not install successfully, see System Platform Prerequisites for additional information.

2. You are prompted to manually confirm that your operating system is compatible with System Platform. Refer to the System Platform Readme (for a list of compatible operating systems, as of the System Platform 2023 release), or the Technology Matrix in the AVEVA Global Customer Support website (for an updated list of compatible operating systems, including newly-released Windows versions).

   Note: This compatibility check helps to ensure that installation is not blocked for compatible Windows versions released after the System Platform release, under Microsoft's Long-Term Servicing Channel (LTSC) and Semi-Annual Channel (SAC).

   

3. After some automatic configuration occurs, the select installation mode dialog box appears. Select one of the following options

   • Product Based Selection: For information about product-based installation, see About Product-Based Installation.

     If you select the Product Based Selection option, the product based installation dialog box appears. Select the product(s) you want to install on the node.

     If you are installing any of the InTouch Access Anywhere options available under Product-Based Installation, see Install InTouch Access Anywhere.

   • AVEVA System Platform Computer Roles: For information bout role-based installation, see About Role-Based Installation.

     If you select the System Platform Computer Roles option, the role based installation dialog box appears. Select the role(s) you want to install on the node.

   You can select multiple products or roles. All the selected components will be installed together. If you are installing InTouch Access Anywhere Secure Gateway, it should be installed by itself, without any other System Platform components on the same node.

4. When you select the Galaxy Repository for installation, the following components are automatically selected for installation and cannot be deselected:

   • Platform Common Services Framework. The PCS Framework includes a System Management Server, used for establishing a trust relationship between machines. See Configuring the System Management Server for additional information.

   • AVEVA Enterprise Licensing Framework. Every node should be configured to point to a single License Server. See AVEVA Enterprise License Server Configuration for additional information.

   • AVEVA System Monitor. Every node should be configured to point to a single System Monitor Manager. See AVEVA System Monitor Configuration for additional information.

     Note: If you have multiple Galaxy Repository nodes, the Configurator lets you select which node(s) to use for the above components at the end of installation. See Configure System Platform components for more information.

5. After you have made your product or role selections and click Next, an important notification appears.

   The notification screen describes important security-related changes in this release of System Platform related to third-party components that are installed to support System Platform. Components that are near or beyond their official support dates are not installed, unless you explicitly choose to install them. These changes have been implemented to improve System Platform security.

   

6. Click Next to proceed. The verify selection dialog box appears.

   • To make changes to your selections or to install out-of-support components, select the Customize Installation check box. You can change your selections to:

     • Install the out-of-support components if you are migrating a project with custom-built executable components that leverage these components (NOT RECOMMENDED). See step 7 for additional information.

     • Select Communication Drivers as needed. See step 8 for additional information.

     • Install other components, such as the InTouch 16-Pen Trend Wizard supplementary component. See step 9 for additional InTouch information.

     • Remove components from a node in multi-node Application Server configurations, such as the IDE or Galaxy Repository.

   • To proceed with your selections without making any changes, click Next.

7. Optional installation of out-of-support assemblies: Security updates include the removal of certain assemblies from Microsoft and other third-parties that have reached their end-of-life and are now out of support. Installing these assemblies may increase your security risk. Some assemblies have been removed completely as they are no longer needed to support System Platform installation. Other assemblies and executables, listed in the following table, are still included with the installation media. You are given the option to install the following assemblies if needed to support custom-built objects that you may be migrating to the new system. Select the checkbox to install them.

   

   Important: Do not install these components unless absolutely required. Instead, AVEVA recommends that you recompile any custom components using the latest redistributable libraries, and/or contact vendor for up-to-date versions.

   Redistributable Description	Folder/Assembly Name
   Microsoft SQL Server 2012 Management Objects SP2 (11.2.5058.0)	SQL2012SP2FeaturePack\ SharedManagementObjects.msi (x64 and x86 versions) SQL2012SP2FeaturePack\ SQLSysClrTypes.msi (x64 and x86 versions)
   Microsoft Visual C++ 2008 Redistributable	VC90SP1/vcredist_x86.exe
   Microsoft Visual C++ 2010 Redistributable	VC10SP1/vcredist_x64.exe VC10SP1/vcredist_x86.exe

   Note: You can locate these assemblies on the installation DVD under the InstallFiles\OutOfSupportRedist folder. If you select the option to install them now, they will be automatically installed during the installation process.

   Important: Installation of out-of-support assemblies is NOT recommended.

   Instead of installing the out-of-support assemblies, we recommend that you use currently-supported software versions to rebuild any custom ApplicationObjects or applications. You may elect to install these out-of-support components if you will be migrating a project that contains:

   • Custom ApplicationObjects built with the Application Object Toolkit

   • Remote Response Objects

   • The discontinued ApplicationObjects $FieldReference or $Switch

   • Custom script libraries or custom .NET controls built with these out-of-support components

   • Any other component that leverages the out-of-support assemblies

     Note: If you do not install the out-of-support assemblies and import objects that have dependencies on them, you may see errors from the aaPim and WWPackageServer components while importing the objects.

8. Optional installation of AVEVA Communication Drivers: When you select Application Server or InTouch HMI for installation, the AVEVA Communication Drivers Pack Simulator (SIM) and Gateway are also selected for installation. Select Customize Installation and then scroll down to add any other drivers that you need.

   

9. If you have selected any InTouch HMI features, the language selection dialog box appears. Select the language for your InTouch HMI installation. The InTouch language versions are supported only for the matching operating system language. For example, the German version of the InTouch HMI is only supported on the German operating system. InTouch HMI language options are:

   • English

   • French

   • German

   • Japanese

   • Simplified Chinese

10. Click Next. The End User License Agreement dialog box appears.

11. Review the license. Click I have read and accept the terms of the license agreement(s), and then click Agree.

12. If the products or roles you selected require it, the Off Node Communications (Network Account) dialog box appears.

    Note: If a Network Account for off-node communications is NOT required (for example, if you are only installing Historian Client), you will be prompted to click Install. If this is the case, skip to step 18.

    

13. Specify a new or pre-existing Network Account for off-node communications. This account is used for encrypted communication between different System Platform nodes and software components. See Network account for more information.

    • To select an existing account, clear the Create Local Account check box. When you clear the check box, the Domain/Local Machine text box displays the default domain name. Specify a different domain/local machine name if necessary. Then, enter the user name and password for the existing Network Account. Click Next to complete the Network Account setup.

    • To create a new account, click the Create Local Account check box if not already selected. By default, the Domain/Local Machine box displays your computer name. Then, enter a user name and password.

    • Network Accounts must meet the following requirements:

      • The account must have a permanent password that does not expire.

      • The account must have a password that cannot be changed.

        Note: If necessary, you can change the Network Account credentials through the Change Network Account utility. The Start Menu includes a shortcut to the utility. It is listed under the AVEVA folder.

14. If the products or roles you selected require Microsoft SQL Server, and a supported version of SQL Server is not already installed, you will be prompted to select either:

    • Install SQL Server Express and continue installation. If you select this option, SQL Server Express is installed and then System Platform installation proceeds automatically.

      Caution: If you select SQL Server Express, System Platform will automatically grant you (the logged in user) SQL sysadmin privileges. This level of access is required to proceed with SQL Server Express installation. You will retain sysadmin privileges even after installation. If you need to remove sysadmin privileges from the logged in account, be sure to create a sysadmin account first.

    • Exit installation and install a supported SQL Server version. If you select this option, the System Platform installer exits. Manually install SQL Server, and then restart the System Platform installer.

      System Platform for medium and large installations includes a separate DVD with a full version of SQL Server 2019 Standard. However, you can install any supported version of SQL Server. See the AVEVA Global Customer Support (GCS) Technology Matrix for a list of supported SQL Server versions.

15. A list of missing prerequisite components (if any) and the System Platform products to be installed are displayed.

    Note: Any prerequisites required for the products selected for installation will be listed above the list of products and components. The prerequisites will be installed first, and the product and components will be installed immediately after installation of the prerequisites has finished. If you elected to install SQL Server Express, it will be installed along with any other prerequisites.

    Click Install to proceed. The progress bar appears.

    

16. After the installation is over, the installation completed dialog box appears.

    

    • Select View Readme for important information, including hardware and software requirements, new features, and known and resolved issues.

    • Select Configure to continue. See Configure System Platform components for the final steps to complete installation.