Create a response file

Response files consist of an install section and a configurator section. See Response file samples for examples that you can use after making minor edits.

Install section

The Install section defines the items that would be selected through the GUI installation dialog windows. These include:

• Root installation directory. The default path is C:\Program Files (x86).

  • FeatureForm.SInstallDir=C:\Program Files (x86)

• The Network Account (name and password), used for inter-node and inter-product communications.

  • AdminUserForm.SUserName=NetworkAccount

  • AdminUserForm.SPassword=Password123

• For upgrade only, whether or not to remove Administrator privileges from the Network Account.

  • RemoveArchestraUser.RemoveA2AFromAdmin=true

• Other settings (not included in Response File Samples; add these manually if needed):

  • AdminUserForm.SDomainName=YourDomain

  • AdminUserForm.SEnhancedSecurity=True/False

    • If True, the Network Account is NOT added to the system Administrators group.

    • If False, the Network Account is added to the system Administrators group.

• Acknowledgement of change to installation behavior:

  • OutOfSupportRedistConsentForm.SRedistConsent=false

    Setting the parameter to true indicates that you acknowledge this information. If the parameter is left at its default, installation fails. See Response file entry to acknowledge installation change information (redistributable libraries) for more information.

• Acknowledgement that a patch may be required for AVEVA Manufacturing Execution System and AVEVA Recipe Management to ensure compatibility with System Platform:

  • CompatibilityAlert.SProductCompatibilityConsent=false

    Setting the parameter to true indicates that you acknowledge this information. If the parameter is left at its default, installation fails. See Response file entry to acknowledge compatibility requirement for more information.

• The components and related requirements that will be installed. You can specify by inclusion or exclusion:

  • Install by inclusion example:

    FeatureForm.SFeatureList=AVEVA System Platform.ASBRuntime,Application Server.Bootstrap,Application Server.IDE

  • To specify products by exclusion, first add ALL products with an inclusion statement, then list the ones that should be left out.
    Install by exclusion example:

    FeatureForm.SFeatureList=ALL

    FeatureForm.SExcludeFeatureList=InTouch Access Anywhere Secure Gateway.SecurityServer_Files,InTouch Access Anywhere Authentication

• Use the following language setting when installing System Platform on a non-English operating system:

  • Example:

    LanguageForm.Language=French

    Other options are German, Japanese, and Simplified Chinese.

Configurator section

The configurator section defines the components that would be configured through the Configurator GUI. These include the following:

• Common Platform. Entries to configure the Common Platform components:

  • System Management Server (SMS), which includes:

    • Certificate management

    • Common Platform ports

    • Security settings for SuiteLink and Network Message Exchange (NMX)

  • Authentication Provider (Azure AD)

  • License Mode, which gives you three options:

    • Perpetual

    • Flex mode

    • AVEVA Operations Control. If you select this, you also have the option of enabling connected experience.

      See Response file entries to configure the Common Platform for more information.

• Industrial Graphics Server. See Response file entries to configure the Industrial Graphic Server for more information.

• AVEVA Historian. See Response file entries to configure Historian for more information.

• AVEVA Enterprise Licensing Manager. See Response file entries to configure the License Server for more information.

• AVEVA System Monitor Manager. See Response file entries to configure System Monitor Manager for details.