Install 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, 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 R2 SP1. 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 R2 and do not require patching.

Workspace feature notification for the OMI and InTouch HMI web clients

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 clients. 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.

OMI web client configuration requirements

If you have, or plan on developing, ViewApps that will be used with the OMI web client, there are two configuration requirements that must be met after installing System Platform:

• You must configure a System Management Server. See Work with Configurator for details.

• You must register System Platform with AVEVA Identity Manager. See Federated Identity Provider for details.

To install System Platform

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.

   • 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 may be 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 R2 SP1 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 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.

   • 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 (unless you select Custom, in which case all other options are ignored). 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 Configuring the Schneider Electric License Server Location for additional information.

   • AVEVA System Monitor. Every node should be configured to point to a single System Monitor Manager. See Configuring the Sentinel System Monitor 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. Click Next to proceed. The verify selection dialog box appears. To make changes to your selections or to change the installation directory, select the Customize Installation check box. You can change your selections to:

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

   • Install other components, such as the InTouch 16-Pen Trend Wizard supplementary component. See step 8 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.

     Important! If you install System Platform to a location other than the default folder, you must set the Access Control List (ACL) for the selected location to avoid file tampering or other malicious activity. Refer to Microsoft's recommendations for setting the ACL for your version of Windows.

6. AVEVA Communication Drivers: The AVEVA Communication Drivers Pack Simulator (SIM) and Gateway are automatically installed when you install Application Server or InTouch HMI. You can also select some of the commonly-used drivers here. If the driver you need is not listed, you can use the Customize installation option to select additional drivers for installation.

   

7. 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

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

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

10. 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 13.

    

11. 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, select 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.

12. 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 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.

13. 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.

    

14. After the installation is over, the dialog box to begin configuration appears.

    

    • To view important information, select View Readme. The Readme describes hardware and software requirements, new features, and known and resolved issues. The dialog remains open; you will still need to select Configure to continue.

    • Select Configure to continue. See Get started with Configurator to complete installation.