System Platform 2017 Update 3 SP1

Материал из archestra.info
Перейти к: навигация, поиск

System Platform 2017 Update 3 Service Pack 1 (SP1) Readme

System Platform 2017 Update 3 Service Pack 1 (SP1) Readme

Last revision: 5/31/2019

This document contains important information about System Platform 2017 Update 3 SP1. This version of System Platform includes a number of security enhancements and new features for the component products of System Platform.

In This Document

Included in This Release

About This Release

Important Information for Highly Secured Environments (TLS 1.2 Exclusively)

How to Find the Latest Product Requirements and Compatibility Information

New Features in System Platform 2017 Update 3 SP1

Web Help Display and Video Playback

System Requirements and Guidelines

System Platform Installation

System Platform Upgrade and Migration

Licensing Information

Antivirus Software

Resolved Issues

Known Issues

Documentation

Documentation Issues

InTouch Access Anywhere Version 2017 Update 3 SP1 Readme

Included in This Release

Program Name

Version

AVEVA Enterprise License Manager

3.5.10000

AVEVA Enterprise License Server

3.5.10000

AVEVA Enterprise Licensing Platform

3.5.10000

InSight Publisher

4.1.000

Platform Common Services 4.3.3

4.3.19135.1

Sentinel Agent Install Manager 1.1 SP1

1.1.100

Sentinel Manager 1.1 SP1

1.1.100

Wonderware Application Server 2017 UPDATE 3 SP1

17.3.100

Wonderware Historian 2017 UPDATE 3 SP1

17.3.100

Wonderware Historian Client 2017 UPDATE 3 SP1

17.3.100

Wonderware InTouch 2017 UPDATE 3 SP1

17.3.100

Wonderware InTouch Access Anywhere Server 2017 Update 3 SP1

17.3.100

Wonderware InTouch Access Anywhere Secure Gateway 2017 Update 3 SP1

17.3.100

Wonderware Operation Integration – Core Communications Driver (G-3.0 Series)

6.0.0

Wonderware Operations Integration – Supervisory Gateway Communications Driver (G-3.0 Series)

6.0.0

About This Release

Changelog: System Platform 2017 Update 3 SP1

Change Description

Add new document and image viewer apps for InTouch OMI (NEW)

Add credential management to Application Server and InTouch OMI ViewApp security (NEW)

Fix line thickness and symbol rendering in InTouch OMI (parity with InTouch HMI)

Miscellaneous bug fixes

Incorporate InTouch HMI and Application Server hot fixes

Add options to Sentinel for monitoring license status and sending alerts (NEW)

Add option to Sentinel for changing user groups (NEW)

Supported System Platform Versions for Product Upgrade

You can upgrade directly to System Platform 2017 Update 3 SP1 from the following versions:

  • System Platform 2017 Update 3
  • System Platform 2017 Update 2
  • System Platform 2017 Update 1
  • System Platform 2017
  • System Platform 2014 R2 SP1 with Patch 01 and/or Patch 02
  • System Platform 2014 R2 SP1

Note that all existing products must be upgraded to the same version.

Supported System Platform Versions for Migration

You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.,) to System Platform 2017 Update 3 SP1, as long as the content was created in one of the following product versions:

  • System Platform: Version 4.5 or newer
  • Application Server: Version 2.5 or newer
  • InTouch HMI: Version 7.11 P07 or newer
  • Historian Server: Version 9.0 P02 or newer
  • FS Gateway: Version 1.5 or newer

Server-based Licensing

System Platform 2017 Update 3 SP1 continues to utilize the server-based licensing subsystem introduced in System Platform 2017. This new licensing subsystem provides centralized license management, and replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.

If you are upgrading from Windows Server 2014 R2 SP1 (with or without patches), you must first install and configure a license server node, and activate the licenses to ensure continuous plant operation. The license server is typically installed on the Galaxy Repository node, but you can use a dedicated license server. See the "License Installation and Activation" section of the System Platform Installation Guide (WSP_Install_Guide.pdf), located at the root of the DVD.

Readme Files for Other Products in this Release

To access individual product Readme files, insert the System Platform installation DVD and navigate to the applicable folder under the InstallFiles directory. Review the known and resolved issues contained in each Readme file for the component products updated for this release:

Product

Version

Location on Installation DVD

Application Server 2017 Update 3 SP1

17.3.1

InstallFiles/CD-ApplicationServer/Readme.html

InTouch HMI 2017 Update 3 SP1

17.3.1

InstallFiles/CD-Intouch/Readme.html

Historian Server 2017 Update 3 SP1

17.3.1

InstallFiles/CD-Historian/Readme.html

Historian Client 2017 Update 3 SP1)

17.3.1

InstallFiles/CD-HistorianClient/Readme.html

Sentinel 1.1 SP1

1.1.1

InstallFiles/CD-SentinelManager/Readme.html

To view the InTouch Access Anywhere Readme (included at the end of this readme), click on the following link :

Important Information for Highly Secured Environments (TLS 1.2 Exclusively)

Affected Systems

This information is applicable to a small subset of highly secured environments, in which operating systems and supporting networks have been configured to enable TLS 1.2 and where TLS 1.0 and 1.1 have been purposefully disabled. In these rare instances, some additional configuration is required to ensure that System Platform will work as expected.

System Platform 2017 Update 3 SP1 includes various measures to strengthen security, including the ability to leverage the latest version of transport layer security (TLS 1.2), provided that TLS 1.2 it has been enabled and configured in the host operating system.

As of the System Platform 2017 Update 3 SP1 release date, Microsoft Windows Server 2016 does not support TLS 1.2 by default. You must enable it by applying Microsoft updates and several manual edits to the system registry. The tasks of applying all Microsoft updates and editing the system registry must be completed before you install System Platform 2017 Update 3 SP1. These instructions also apply to any other software products that support TLS 1.2. Follow the instructions listed below.

If you are required to enable TLS 1.2 and disable TLS 1.0 and TLS 1.1:

  1. Before installing System Platform 2017 Update 3 SP1 on a Windows Server 2016 computer, make sure that your computer is up to date by downloading and installing all applicable Microsoft updates.
  2. If required by the updates, restart your computer.
  3. Edit the system registry. The .REG file shown below sets registry keys to their safest values.
    For additional information about these registry changes, see https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#configuring-security-via-the-windows-registry.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]

    "SystemDefaultTlsVersions"=dword:00000001

    "SchUseStrongCrypto"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]

    "SystemDefaultTlsVersions"=dword:00000001

    "SchUseStrongCrypto"=dword:00000001

  4. Restart your computer to ensure that all changes take effect.
  5. Install System Platform 2017 Update 3 SP1.

How to Find the Latest Product Requirements and Compatibility Information

For important information about this product release, go to the AVEVA Global Customer Support (GCS) web site. Information on the GCS web site includes product requirements, compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.

  • The GCS Product Hub contains Readme files, videos, and product downloads from previous product releases.
  • The GCS Technology Matrix is a searchable database that contains the latest product information. Enter the product name in the search bar, then select the current release to view:
    • Product Information: version name, number, release date, etc.
    • Product Notes: key release information, new features, and updates
    • OS Compatibility: list of compatible Windows and Windows Server versions
    • Database Compatibility: list of compatible SQL Server and other database product versions
    • Virtualization Compatibility: list of compatible virtualization software products and versions
    • Product Coexistence: list of products that can be installed on the same computer
    • Product Compatibility and Interoperability: list of products that can operate together and communicate with each other through a common message protocol

New Features in System Platform 2017 Update 3 SP1

New features contained in the products that comprise System Platform 2017 Update 3 SP1 are outlined below.

New Features in InTouch OMI Update 3 SP1

Document and Image Viewer Apps

Four new Viewer Apps have been added to InTouch OMI. When these apps are integrated in an InTouch OMI ViewApp, the ViewApp can display Microsoft Word documents, PDF documents, Excel spreadsheets, and images.

  • DocViewerApp: The DocViewerApp shows a Word document in read-only mode within a pane of a ViewApp. Documents can be searched, and the view can be enlarged or reduced in size.
  • PDFViewerApp: The PDFViewerApp shows a PDF document within a pane of a ViewApp. Documents can be searched, rotated, the view can be enlarged or reduced, and selected content can be copied to the clipboard.
  • SpreadsheetViewerApp: The SpreadsheetViewerApp shows an Excel spreadsheet in read-only mode within a pane of a ViewApp. The spreadsheet view can be enlarged or reduced in size.
  • ImageViewerApp: The ImageViewerApp shows an image in read-only mode within a pane of a ViewApp. Images can be flipped horizontally or vertically, or rotated, and the view of the image can be enlarged or reduced in size.

Credential Management

InTouch OMI ViewApps can use security credentials created in Application Server to gain access to third-party data where Windows OS credentials are not recognized, and/or to provide a method to automatically load a particular data set for specified users.

Line Thickness and Symbol Rendering

In prior releases, rounded rectangles and the line thickness of symbol elements did not always render the same at run time in an InTouch OMI ViewApp as they appeared during design/configuration. These elements will now be rendered at run time to appear the same as they do at design time.

New Features in Application Server 2017 Update 3 SP1

Credential Management

Application Server lets you create security credentials for use in InTouch OMI ViewApps. These credentials can be used to gain access to third-party data where Windows OS credentials are not recognized, and/or to provide a method to automatically load a particular data set for specified users.

Application Server User Guide

The Application Server User Guide includes concepts and instructions for use of the AVEVA Telemetry Server. The Telemetry Server is a separate product, not yet released, and is not included on the System Platform 2017 Update 3 SP1 installation DVD. We will provide information about the Telemetry Server in the context of upcoming releases.

New Features in InTouch HMI 2017 Update 3 SP1

InTouch HMI 2017 Update 3 SP1 includes a number of hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products. No new features have been introduced in this release.

New Features in Historian 2017 Update 3 SP1

Multi-Tier Replication Support

The Historian supports multi-tier replication. Data originating at tier 1 can be replicated to tier 2, then again to tier 3, and so on. Replication from tier 1 to tier two can be simple or summary replication. Replication beyond tier 2 is simple replication.

New Sentinel Features for System Platform Update 3 SP1

New options for license monitoring and alerts have been added to Sentinel.

  • Option to monitor the License Server grace period and receive alerts when the grace period is expiring within 14 days, 7 days, and 24 hours.
  • Option to monitor the License Server and receive alerts when licenses are expiring within 30 days, 7 days, and 24 hours.
  • Option to add, edit, and delete existing local or domain user groups as users.

Web Help Display and Video Playback

Web Help - Browser-based User Assistance

Web help components have been delivered in this release. Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.

Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. To open the help, use one of the following methods (depending on the editor/UI you are using):

  • Press F1 from the ViewApp editor, Screen Profile editor, or Layout editor.
  • From the System Platform IDE, select an object or symbol name and:
    • press Ctrl+F1, or
    • right-click, then select Help from the short-cut menu.
  • Open web help from its installed location:

    C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\NGX\index.htm

Browser Requirements and Recommendations

Internet Explorer is recommended. You can also view web help Firefox. If you use Firefox, you may need to install and use an IE rendering extension (for example, IE Tab) to ensure that video content is shown.

  • Microsoft Edge will not load help content, unless you use the "Open with Internet Explorer" option in the Edge browser.
  • Chrome and Chromium-based browsers, such as Vivaldi, will not load help content unless you install and use an IE-rendering extension (for example, IE Tab).

Browser Permissions for Displaying Web Help

Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.

You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your specific browser.

Playback of Tutorial Videos

The web help may contain a number of brief tutorial videos. To play these videos, you must have Microsoft Media Player installed on your local machine. In Windows Server operating systems, you must enable the "Desktop Experience" feature using Server Manager.

Internet Explorer (or IE-rendering in other browsers) may be required for viewing video content. If using a browser other than Internet Explorer without IE rendering enabled, videos may not be visible.

InTouch OMI SDK Web Help

When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.

  • To open the SDK help from its installed location, go to:

    C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\OMISDKHelp\index.html

  • To open the SDK help from the start menu, go to:

    Start > Wonderware Documentation > InTouch OMI SDK Help

InTouch OMI SDK Web Help

When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.

  • To open the SDK help from its installed location, go to:

    C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\OMISDKHelp\index.html

  • To open the SDK help from the start menu, go to:

    Start > Wonderware Documentation > InTouch OMI SDK Help

System Requirements and Guidelines

Hardware Requirements Notes

 

 

 

Operating System, Firewall, .NET Framework, and Virtualization Notes

Operating System and Software Requirements for System Platform 2017 Update 3 SP1

Windows Operating System Notes

.Net Notes

SQL Server Notes

Virtual Environment Notes

Firewall Notes

Operating System Notes: Common for Wonderware Products

Operating System Notes: InTouch HMI 2017 Update 3 SP1

Operating System Notes: Application Server

Operating System Notes: Historian Server

Operating System Notes: Historian Client

 

.NET Framework Requirements and Compatibility

Considerations for SQL Server

Considerations for SQL Server Express

Third-Party Application Prerequisites

 

 

 

Related Topics

System Platform 2017 Update 3 Service Pack 1 (SP1) Readme

Included in This Release

About This Release

Important Information for Highly Secured Environments (TLS 1.2 Exclusively)

How to Find the Latest Product Requirements and Compatibility Information

New Features in System Platform 2017 Update 3 SP1

Web Help Display and Video Playback

System Platform Installation

System Platform Upgrade and Migration

Licensing Information

Antivirus Software

Resolved Issues

Known Issues

Documentation

Documentation Issues

InTouch Access Anywhere Version 2017 Update 3 SP1 Readme

System Sizing Guidelines

The following table provides guidelines for hardware configurations suitable for System Platform Version 17 software based on the size of the application. These guidelines are subject to the limitations of your Windows operating system, and if applicable, to the SQL Server edition (Express, Standard, or Enterprise). See the AVEVA GCS Technology Matrix for supported versions of Windows operating systems and SQL Server.

  • The Intel Itanium 2 processor is not supported.
  • We recommend 1280 x 1024 as the minimum display resolution for engineering tools such as the Integrated Development Environment (IDE).
  • A Windows Server operating system is required for large installations with more than 50,000 I/O per node.
  • SQL Server Express is not supported for installations with more than 25,000 I/O per node (small installations only).

Application

Level

CPU Cores

RAM

HD Space

Screen Resolution

Network Speed

Server Nodes: for Historian Server, Galaxy Repository (GR node), Application Server IDE, AppEngine host

Small Application
(1 - 25K I/O per Node)

Minimum

2

2 GB

100 GB

1024 x 768

100 Mbps

Recommended

4

4 GB

200 GB

1920 x 1080

1000 Mbps

Medium Application
(25k - 50k I/O per Node)

Minimum

4

8 GB

200 GB

1024 x 768

1000 Mbps

Recommended

8

12 GB

500 GB

1920 x 1080

1000 Mbps

Large Application
(> 50k I/O per Node)

Minimum

8

16 GB

500 GB

1024 x 768

1000 Mbps

Recommended

16

24 GB

1000 GB

1920 x 1080

Dual 1000 Mbps

Thin Client Node

RDP clients, ITAA, mobile devices

Minimum

1

512 MB

N/A

800 x 600

100 Mbps

Recommended

2

2 GB

N/A

1280 x 1024

100 Mbps

Client Node

WindowViewer, ViewApp, Historian Client, Remote IDE

Minimum

2

1 GB

100 GB

1024 x 768

100 Mbps

Recommended

4

4 GB

200 GB

1920 x 1080

1000 Mbps

Thin Client-Server Node

RDS, ITAA Server
Supports up to five remote sessions

Basic RDS - Minimum

4

8 GB

200 GB

1024 x 768

1000 Mbps

Basic RDS - Recommended

8

12 GB

500 GB

1920 x 1080

1000 Mbps

Large RDS - Minimum

8

16 GB

500 GB

1024 x 768

1000 Mbps

Large RDS - Recommended

16

24 GB

1000 GB

1920 x 1080

Dual 1000 Mbps

All-In-One Node

All products on a single node
1,000 I/O maximum

Minimum

4

8 GB

200 GB

1280 x 1024

100 Mbps

Recommended

6

12 GB

500 GB

1920 x 1080

1000 Mbps

Server node type applies to Historian Server, Galaxy Repository node, and nodes hosting AppEngines.
In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.

Supported and Recommended Node Hardware Types

Product

Server Node

Thin Client- Server Node

Client Node

Thin Client

All-In-One

Application Server

Galaxy Repository

Preferred

Supported

Supported

No

Supported

Application Engine

Preferred

Supported

Supported

No

Supported

IDE

Preferred

Supported

Supported

RDP

Supported

ViewApp Runtime

Supported

Supported

Preferred

ITAA/RDP

Supported

InTouch Standalone

WindowMaker (No Modern Apps)

Supported

Supported

Preferred

RDP

Supported

WindowMaker (with Modern Apps)

Preferred

Supported

Supported

RDP

Supported

WindowViewer / InTouch ViewApp (runtime only)

Supported

Supported

Preferred

ITAA/RDP

Supported

InTouch for System Platform

WindowMaker (with Managed Apps)

Preferred

Supported

Supported

RDP

Supported

WindowViewer / InTouch ViewApp (runtime only)

Supported

Supported

Preferred

ITAA/RDP

Supported

InTouch Access Anywhere

InTouch Access Anywhere Server

Supported

Preferred

No

No

Supported

InTouch Access Anywhere Client (HTML5 Browser)

Browser

Browser

Browser

Browser

Browser

InTouch Access Anywhere Secure Gateway

Supported

No

No

No

No

Historian

Historian Server

Preferred

Supported

Supported

No

Supported

Historian InSight Client

Browser

Browser

Browser

Browser

Browser

Historian Client (Active Factory)

Supported

Supported

Preferred

RDP

Supported

Support Components

OI Gateway

Preferred

Supported

Supported

No

Supported

AVEVA Enterprise Licensing - Server

Preferred

Supported

Supported

No

Supported

AVEVA Enterprise Licensing - Manager

Preferred

Supported

Supported

No

Supported

AVEVA Enterprise Licensing - Manager Client

Browser

Browser

Browser

Browser

Browser

Hardware Requirements Notes

Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for System Platform 2017 Update 3 SP1. Refer to the following Microsoft Web sites for Windows and SQL Server hardware requirements.

Windows requirements

SQL Server requirements

Historian Hardware Guidelines

  • Historian is not supported on cluster hardware.
  • Do not use the Historian computer as a domain controller.
  • If you are running the Historian on a virtual server, the Historian must have adequate CPU, network, memory, and disk I/O resources at all times. Overloading the virtual server leads to unpredictable behavior.

For system sizing examples, see the System Platform Installation Guide.

Alternative Authentication Using Smart Cards

  • Smart Card: Raak Technologies C2-40 Mini Driver Smart Card
  • Smart Card Reader: OK 3021 USB Smart Card Readers

Operating System, Firewall, .NET Framework, and Virtualization Notes

Operating System and Software Requirements for System Platform 2017 Update 3 SP1

The latest product information for each System Platform product is listed in the Global Customer Support GCS Technology Matrix. Each link includes:

  • General information about the selected product, such as the version number and release date
  • Operating system requirements
  • Microsoft SQL Server requirements
  • Virtualization software compatibility
  • Information about interoperability (which Wonderware products a specific product works with)
  • Information about coexistence (which Wonderware products can be installed on the same node)

Minimum Required Operating System Version

The following table shows the minimum operating system for each product. See the GCS Technology Matrix for a list of all supported operating systems.

Product

Minimum Required Operating System Version

Client OS (x86 and x64)

Server OS (x64 only)

Application Server

Windows 8.1 Professional

Windows 10 Version 1607 (see note, below)

Windows Server 2012 (Embedded or Data Center)

InTouch

Historian

Important: Microsoft support for Windows 10 Version1607 ended earlier this year, and support for Version 1709 ends October 8, 2019. For more information, see the Windows lifecycle fact sheet (https://support.microsoft.com/en-in/help/13853/windows-lifecycle-fact-sheet). Regardless of which operating system you are using, we recommend that you download and install the latest Microsoft updates to enhance security and ensure product compatibility.

System Platform 2017 Update 3 SP1 Web Clients

The following web clients are included with System Platform 2017 Update 3 SP1:

  • InTouch Access Anywhere Client (HTML5 Browser)
  • Historian InSight Client
  • AVEVA Enterprise Licensing - Manager Client

The client programs listed above can be used with most common web browsers. Compatible browsers include:

  • Microsoft Internet Explorer 11
  • Microsoft Edge
  • Firefox (version 38 and higher)
  • Safari (version 5 and higher)
  • Google Chrome (version 12 and higher)
  • Opera (version 11 and higher)

System Requirements by installation size

Small installation (1 to 25,000 I/O per system):

  • Any operating system, database, and virtualization software supported by Application Server.
    • Exceptions: None.

Medium installation (25,000 to 50,000 I/O per system):

  • Any operating system supported by Application Server.
    • Exceptions: 32-bit versions of Windows 8.1 are not supported (64-bit versions are supported).
  • Any database software supported by Application Server.
    • Exceptions: SQL Express-SSMSE versions are not supported.
  • Any virtualization software supported by Application Server.
    • Exceptions: None

Large installation (50,000 to 400,000 I/O per system):

  • Only Windows Server operating systems (for example, Windows Server 2016) supported by Application Server.
    • Client operating systems, such as Windows 8.1 and Windows 10, are not supported for large installations.
  • Any standard or enterprise version of database software supported by Application Server.
    • Exceptions: SQL Server Express-SSMSE versions are not supported.
  • Any virtualization software supported by Application Server
    • Exceptions: None

Windows Operating System Notes

  • Newer operating system Service Packs (SPs) than those listed do not block the installation of AVEVA products. A warning message may appear during the installation process.
  • The Galaxy Repository (GR Node) can run on a client Windows operating system in a configuration with up to five remote nodes. For an environment with more than five remote nodes, or with more than one GR node, the Galaxy Repository must be installed on a computer running a Windows Server operating system.
  • Development and application nodes are considered to be clients of the server GR node.
  • When the operating system is upgraded on a computer, existing System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are three exceptions. System Platform products do not need to be uninstalled when upgrading from:
    • Windows 8 to 8.1
    • Windows 8.1 to 10
    • Windows 2012 to Windows 2012 R2

.Net Notes

  • Versions of .NET (other than 4.x versions) can coexist, but all .NET code, including QuickScript.net scripts, run under .NET 4.7.2 or higher. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility.
  • .NET 3.5 must be enabled to allow various SQL Server versions and the System Platform Management Console (SMC) to run.

SQL Server Notes

When installing SQL Server, use the program version (32 or 64-bit) that matches the operating system.

Upgrading SQL Server with Wonderware products installed is supported.

Virtual Environment Notes

The following virtualization software and cloud-based virtual environments are supported for System Platform 2017 Update 3 SP1:

  • Hyper-V 5 and newer (version is based on the operating system utilized)
    • Both Gen 1 and Gen 2 VMs are supported
    • Windows 10 and Windows Server 2016 support Versions 7 and 8
  • VMWare VSphere 6.0 and 6.5, including HA/DR
  • VMWare Clients, including Horizon - Application Virtualization
  • Cloud Virtualization - Azure
  • VMWare Workstation, Version 11 and higher

Firewall Notes

In order to establish communication with other components and services on the network, System Platform and ArchestrA Service Bus (ASB) services require certain network ports to be opened in the Windows Firewall. Typically, these ports are automatically opened for the Windows Firewall during installation. However, if the Windows Firewall service is disabled or not running at the time of installation, or if an alternative firewall is in use, you will need to manually open the appropriate network ports in the firewall. For more information about port configuration, see "Configuring ArchestrA Service TCP Ports" in the Application Server User Guide (filename: IDE.pdf).

Operating System Notes: Common for Wonderware Products

ActiveX Controls Behavior on Supported Windows Operating Systems

Due to the Data Execution Prevention (DEP) feature in Windows operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host, or will behave unpredictably in InTouch, either in WindowMaker or WindowViewer.

The ActiveX controls and error message, along with solutions to resolve the behavior, are described in detail in TechNote 522, "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)". You can download this TechNote from the AVEVA Global Customer Support (GCS) website.

Configuring Remote Alarm Retrieval Queries

The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on currently-supported Windows and Windows Server operating systems.

When InTouch WindowViewer is started and generates alarms from an interactive Windows or Windows Server desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.

This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.

To configure the AlarmViewer's alarm query

  1. After starting InTouch WindowViewer (alarm provider), open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120". The indicated IP address will be unique to your alarm-providing node. Note the IP address for use in Step 2.
  2. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for "nodename" below and substituting your IP address noted in the previous step:

    \\nodename:ip_address\intouch!$system

    where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.

  3. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.
Terminal Services Behavior in Windows Server Operating Systems

Windows Server 2008 R2 and later operating systems no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 R2 and later operating systems, Session 0 is no longer an interactive session, and is reserved only for Windows services. Windows Server 2008 R2 and later operating systems treat all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.

This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. The impact to Application Server is minimal as most Application Server processes run as services. One impact to Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.

Refer to the InTouch HMI Readme for further information about InTouch HMI applications running in the Terminal Server Console.

If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session.

Operating System Notes: InTouch HMI 2017 Update 3 SP1

InTouch HMI 2017 Update 3 SP1 with Supported Windows Operating Systems
  • Windows client (8.1 and 10) operating systems do not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
  • A computer running Windows 8.1 or Windows 10 can be configured as both an InTouch and an Application Server alarm provider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers.
  • InTouch HMI 2017 Update 3 SP1 does not support the following legacy script functions on 64-bit systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
  • If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator to function properly.
  • The onscreen keyboard options were changed for Windows 7 and Windows Server 2008 R2. Although System Platform 2017 Update 3 SP1 does not support these operating systems, these changes apply to the currently-supported operating systems.
  • Hovering to select from the Windows keyboard does not work in currently-supported operating systems.
InTouch HMI 2017 Update 3 SP1 View Applications and DDE Support

NetDDE is not supported for InTouchView applications.

By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.

In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag on a local node.

InTouch HMI 2017 Update 3 SP1 Support for Windows User Account Control

System Platform 2017 Update 3 SP1 with InTouch HMI 2017 Update 3 SP1 supports User Account Control-enabled operations on run-time nodes.

Operating System Notes: Application Server

  • The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of Microsoft operating systems: English, Japanese, Simplified Chinese, German, and French. The Galaxy Repository is also supported by the English, Japanese, Simplified Chinese, German, and French versions of Microsoft SQL Server.
  • Upon installation, the selected language and regional settings must match those of the intended operating locale and must use the collation of SQL Server that matches the operating system locale.
Using Application Server with Supported Windows Operating Systems

This section describes specific behaviors and restrictions when using the supported versions of Windows and Windows Server operating systems with Application Server.

  • The DDESuiteLink Client connection to the local Operations Integration (OI) Server (DAServer) using Local DDE is supported ONLY when the OI Server is configured as "Not a Service" and activated from its executable file or launched from InTouch. On Windows and Windows Server operating systems, Local DDE is NOT supported when the OI Server is activated in the System Management Console (SMC).
  • For toolkits such as the ArchestrA Object Toolkit, GRAccess Toolkit, and MXAccess Toolkit to function properly on Windows 8.1 and later operating systems, you may need to start the toolkit by right-clicking on the file and then clicking Run As Administrator.
Application Server and User Account Control Level

Application Server supports User Account Control-enabled operations. Starting the IDE requires elevated privileges.

Operating System Notes: Historian Server

Scenarios involving remote node communication fail if the Historian node is using the Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012 operating system.

For example:

  1. When you log in as a local administrator on a computer and try to add a remote Historian node (a second node with the Historian installed) using the network account from the Management Console, the status of the remote Historian node is not reflected correctly.
  2. Test the connection from a Historian node using the operating system to a remote tier-2 historian. The following error message is shown: "Test Connection to replication server () failed: cannot connect to Tier-1 replication service (error 0x80004005: Unspecified error)"
  3. Replication to the remote tier-2 historian fails.
  4. Although a remote IDAS service starts successfully, errors and warnings stating "Failed to get IDAS configuration version..." and "Unable to start data acquisition" are logged. This problem occurs if the ArchestrA user account is a local user. If the ArchestrA user account is a domain user, then this problem does not occur.

Workaround:

  1. Open a command prompt and run the following command:

    cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

    This sets LocalAccountTokenFilterPolicy registry entry value to 1. In doing so, an elevated token for the user is generated.

  2. Restart the system.

Operating System Notes: Historian Client

User Account Control can be enabled when the Historian Client application is running as non-administrator.

.NET Framework Requirements and Compatibility

IMPORTANT: System Platform 2017 Update 3 SP1 leverages the Microsoft .NET Framework 4.7.2. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. System Platform 2017 Update 3 SP1 will use .NET Framework 4.7.2 or later.

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.7.2 or higher. Although the .NET Framework 4.7.2 is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts. These changes may also affect .NET controls developed with .NET 3.5.

In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5 and later. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:

BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());

To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:

What's New in the .NET Framework:

http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx

What's obsolete in the .NET Framework Class Library:

https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx

Migration Guide to the .NET Framework 4.7, 4.6 and 4.5:

https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29

.NET Framework 4 Migration Issues:

http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29

Considerations for SQL Server

SQL Server is required for Application Server, InTouch, and Historian Server. We recommend that you install and configure the supported SQL Server version before you begin the System Platform installation program. If you select SQL Server Express during System Platform installation, it will be installed automatically (applicable to small installations only).

The System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.

Other considerations are:

  • Alarm DB Logger: To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.
  • SQL Server Configuration Rights: While installing InTouch HMI for System Platform, if the logged-on user performing the installation is not a SQL Server administrator, the Config SQL dialog box appears and requests SQL Server administrator credentials.
  • Maximum Server Memory: After installing SQL Server, use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately 65% of the total available RAM. By default SQL Server does not clamp this setting. The System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.
  • Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. Attempting such a restore results in an error message.
  • The MSSQL Server user account is not supported for the SQL Server 2012 Service. Instead, configure SQL Server to run as the local system or Network Service account. Named instances are not supported.
  • Migrating SQL Server Versions: You can migrate a SQL Server database to a later version from any of two prior versions. For example, you can migrate to SQL Server 2012 from SQL Server versions 2008 or 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate step. For more information and helpful procedures, see the following Microsoft references:
  • SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Application Server installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:
    • Run the Change Network Utility from the Windows Start menu.
    • Run the aaConfig SQL Utility from the Windows Start menu.

    If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Application Server User's Guide, "About ArchestrA User Accounts", for further information and procedures about restoring the aaAdministrators group.

Considerations for SQL Server Express

  • SQL Server Express is supported for use on an InTouch, Application Server, or Historian node, recommended for use only in small or development configurations. SQL Server 2014 Express with Tools SP2 is automatically installed for when you install for InTouch, Application Server, or the Historian, if, at time of installation, no other SQL Server elements are installed on the computer.
  • If you plan to use SQL Server Express with Wonderware Information Server and InTouch HMI on the same node, the following limitations apply:
    • Installing Wonderware Information Server first, using the MS SQL Express default instance name set to "SQLEXPRESS", and then installing InTouch HMI will work without issue. Note that in this scenario, each component uses a dedicated instance of SQL Server 2014 Express with Tools SP2.
    • Installing InTouch HMI first, which silently installs and configures SQL Server 2014 Express with Tools SP2, and then installing Wonderware Information Server will not allow Wonderware Information Server to work. In this case, during the Wonderware Information Server configuration, an error message will appear in the Configuration Utility stating: "SQL Server client components not found." To work around this issue, configure Wonderware Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.
    • The computing capacity of SQL Server Express 2014 with Tools SP2 is limited to the lesser of one CPU socket or four processor cores.
  • For InTouch HMI-only installations, the System Platform installer will automatically install SQL Server Express 2014 with Tools SP2 if these conditions are met:
    • No version of SQL Server is installed on the computer at the time of installation.
    • You select only the InTouch Development and Runtime System Platform installation option. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.

Additional SQL Server Notes for Application Server

  • If multiple versions of SQL Server are installed, the one used as the Galaxy Repository must be the default instance. Named instances are not supported.
  • The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the computer's physical memory.
  • TCP/IP must be enabled on the computer hosting a SQL Server database. The TCP/IP protocol setting can be verified from the SQL Server Network Configuration under SQL Server ConfigurationManager.
  • To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.

Third-Party Application Prerequisites

For Historian Client:

  • Microsoft Office is an optional prerequisite. If you install Office after installing Historian Client, the Historian Client add-ins do not appear in the list of Office add-ins. Run the Historian Client installation program and repair the installation to load the Office add-ins.
  • When you perform a custom installation of Microsoft Office (32-bit), you must install Office Shared Features and Office Tools so that the Historian add-ins for Workbook or Report can be loaded. Note: Make sure that you are not using the Microsoft Office 64-bit version.

System Platform Installation

For detailed installation instructions in English, see the System Platform Installation Guide (WSP_Install_Guide.pdf) or System Platform Installation Help (WSP_Install_Guide.chm). This guide supersedes the separate installation guides for the individual products. The Installation Guide pdf file is located in the root directory of the System Platform installation DVD. The Installation Help chm file is located in the InstallFiles directory of the installation DVD.

The information provided in this Readme file and the InTouch Readme file supersedes the InTouch HMI Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.

Before Installing System Platform 2017 Update 3 SP1

  • Installing System Platform 2017 Update 3 SP1 on a computer used as a domain controller is not supported. For more information, see http://technet.microsoft.com/library/Cc966456.
  • Some Wonderware products released prior to System Platform 2017 Update 3 SP1 must be installed BEFORE you install System Platform, if the product will be installed on the same node as System Platform. These are:
    • Alarm Adviser (2014 R2 SP1 and prior versions)
    • Intelligence (2014 R3 and prior versions)
    • Recipe Manager Plus (Update 1 and prior versions)
    • Skelta BPM 2017 R2 (Update 1 and prior versions)

About the ArchestrA User Account

The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an ArchestrA environment. You must specify the same user account on every node when you install the System Platform components for the first time on computers that communicate with each other.

WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.

  • If the ArchestrA user account has not previously been configured, you will be prompted to configure it during the System Platform installation. You must specify a user name, password, and domain.
  • If you use an existing user account, it must have a permanent password that does not expire, and the password cannot be changed.

After you install a System Platform component, you can use the ArchestrA Change Network Account utility to change or re-create the ArchestrA user account. The Start menu contains a shortcut to the utility. It is under the Wonderware Utilities folder.

You must have Administrator privileges to use the Change Network Account utility. For more information, see the Change Network Account utility help

Note: If you re-create the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.

Sentinel Installation and Configuration

We highly recommend the following Sentinel installation and configuration sequence. For more information and details, please see “Configuring the Sentinel Agent" and "Configuring the Sentinel Manager” in the System Platform Installation Guide.

  1. Install System Platform.
  2. Start the Configurator:
    1. Configure AVEVA Enterprise Licensing Platform > AVEVA Enterprise License Server
    2. Configure Common Platform > System Management Server
    3. Configure Sentinel System Monitor > Sentinel Manager
    4. Configure Sentinel System Monitor > Alert Email Server
    5. Configure the remaining product plug-ins.
    6. Restart your system.

Re-Connecting to System Management Server after Hardware Replacement or VM Restoration

If you connect a machine to the System Management Server and then later replace the machine due to hardware failure, or restore the VM to a state prior to that connection without first disconnecting the machine from the System Management Server, you will not be able to reconnect that same machine to the System Management Server.

Cause:

To protect the security of the system, the System Management Server uniquely identifies each machine that connects to it. If an intruder attempts to pretend to be that machine (spoofing) and re-registers with that machine’s name, the System Management Server will detect the mismatched identity and reject the suspected intruder’s registration.

Solution:

  • Before replacing a connected machine, and/or restoring the connected VM to a pre-connected state, run the Configurator on that machine and disconnect it from the System Management Server.
  • If that is not possible (i.e., the machine is no longer available due to hardware failure), then you will need to remove the connection information on the System Management Server manually:

    After attempting to reconnect the machine, the logger will contain the warning:

    “ArchestrA.CertificateManager: Please un-register the device <device name> from management server. Use the (Remove-AsbDevice) script to remove the device registration”

    The PowerShell command will remove the machine’s connection information from the System Management Server. We recommend that you contact your support team, or Global Customer Support (GCS), for assistance with executing this command.

System Platform Upgrade and Migration

You can upgrade directly to System Platform 2017 Update 3 SP1 from System Platform 2014 R2 SP1 or later.

Upgrading is defined as installing a newer version of the software when a previous version of the software exists. An upgrade is possible when the system requirements (operating system, SQL Server, .NET Framework) are met. The upgrade process will properly remove or uninstall the previous software version and install the new version. For versions older than the current and previous licensed versions, only the latest service pack or patch versions are tested. For distributed systems, some products must be upgraded in a particular order. For more information, see upgrade information for each product in the System Platform Installation Guide.

The earliest versions of Windows that support System Platform 2017 Update 3 SP1 are:

  • Windows 8.1, Professional or Enterprise Editions
  • Windows Server 2012, Embedded or Datacenter Editions (Standard Edition is not supported)

See the GCS Technology Matrix for complete information about operating system that you can use with System Platform 2017 Update 3 SP1 products.

IMPORTANT! Back up any relevant application configuration files or databases before you start an upgrade or migration.

Licensing Information

Once installed, a link to the AVEVA Enterprise License Manager can be found in the \AVEVA folder on the Start menu.

It can also be accessed by pointing your browser to the following URL:

http://<nodename>/AELicenseManager

where <Nodename> is localhost or the name of the node where the AVEVA Enterprise License Manager is installed.

License Server

The AVEVA Enterprise License Server can be installed separately from the AVEVA Enterprise License Manager.

Running both InTouch HMI and InTouch OMI in a Session on an RDS Server

In System Platform 2017 Update 3 SP1, running both InTouch HMI and InTouch OMI in a session on an RDS Server will attempt to acquire two (2) Supervisory Client Server (unlimited) licenses instead of one (1).

If you have purchased a Supervisory Client Server license (unlimited RDP sessions on a single server) and then run both InTouch HMI and InTouch OMI simultaneously, there can be issues acquiring the server license due to differences in how the license is handled between the two. The order of startup will impact the results.

This behavior is seen in only a limited number of instances, only when you have purchased a Subscription license. If you do see this behavior, change the order of InTouch HMI and InTouch OMI startup.

If this behavior continues, contact AVEVA Software Global Customer Support (GCS), describe the behavior, and request a temporary license, typically valid for 60-days.

InTouch OMI and InTouch HMI ViewApp License Reservation Device Name for Client Devices, RDP Servers, and Users

License Reservation

Reserving a license for a specific device ensures a license will be available for that specific device whenever it is needed, regardless of the number of devices connected to the system. Keep in mind, each license can only be reserved to a single device, so if the device names are unknown ahead of time, it's better to not use reservations and instead allow the licenses to be acquired on a first-come, first-serve basis.

User-based License Reservation

In the AVEVA Enterprise License Manager license reservation page it is possible to mark a license to be reserved to a specific user. While the reservation page allows this particular configuration, it's important to know that neither InTouch OMI nor InTouch HMI ViewApps support user-based license reservations. The end-result will be the inability for the software to acquire the license reserved. Therefore, only use device-based reservations for Supervisory Client licenses.

Device-based License Reservation

When reserving a Supervisory Client license for a specific device, the Device Name needs to be the name of the computer running the InTouch HMI/OMI ViewApp. In the case where the ViewApp is running inside of a Remote Desktop Session, on an RDS (aka: Terminal Server), then the Device Name needs to follow this naming pattern:

<RDSHostName>-<RDPClientName>-<index>

where RDSHostName is the name of the Remote Desktop Server (aka: RDS or Terminal Server), and RDPClientName is the name of the PC running the RDP client software, and "index" is 1, unless there will be multiple RDP sessions from a single client machine, in which case the index should be incremented (starting at 1) for each reservation for that specific RDP client, up to the total number of RDP sessions from that specific RDP client.

Reservation Examples

Situation: A computer with a hostname of "ControlRoomA" runs InTouch OMI

Device Name: "ControlRoomA"

Situation: A computer with a hostname of "ControlRoomB" running a single Remote Desktop Client (RDP), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"

Device Name: "PrimaryRDS-ControlRoomB-1"

Situation: Two computers with hostnames "SupervisorPC1" and "LineMgrA", respectively, each running a single Remote Desktop Client (RDP) connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"

Device Names:

  • License Reservation 1: "PrimaryRDS-SupervisorPC1-1"
  • License Reservation 2: "PrimaryRDS-LineMgrA-1"

Situation: A computer with a hostname of "ExecutiveDesktop" running four (4) Remote Desktop Clients (RDPs), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"

Device Names:

  • License Reservation 1: "PrimaryRDS-ExecutiveDesktop-1"
  • License Reservation 2: "PrimaryRDS-ExecutiveDesktop-2"
  • License Reservation 3: "PrimaryRDS-ExecutiveDesktop-3"
  • License Reservation 4: "PrimaryRDS-ExecutiveDesktop-4"

AVEVA Enterprise Licensing Support for High Availability (HA) and Disaster Recovery (DR) in Virtual Environments

Virtual Environments: License Servers are supported in virtual environments. However, under certain circumstances, such as transferring a license from one virtual environment to another, the License Server may interpret the transfer as an improper move and therefore go into grace period.

High Availability: License Servers in a High Availability virtual environment are supported in specific topologies. Basic redundancy topologies are described in the AVEVA Enterprise Licensing online help.

Disaster Recovery: License Servers in a Disaster Recovery virtual environment will go into a grace period during DR activities. This is because DR activities are similar to an improper move of licenses and will trigger a grace period.

To avoid a grace period trigger in a DR virtual environment, we recommend that you run the License Server outside the virtualized DR environment and use a redundant License Server configuration through the functionality built into the License Server software. Another option is to purchase Disaster Recovery licenses at a discounted rate and establish a backup License Server with these additional licenses.

In all environments, we recommend you install and run the Sentinel System Monitor to monitor licensing functionality and view alerts on issues such as a License Server going into grace period.

Hyper-V Virtual Environment

High Availability (HA) in a Hyper-V virtual environment does not activate licensing grace period during a failover as monitored environmental variables do not change.

Disaster Recovery (DR) in a Hyper-V virtual environment activates a licensing grace period as monitored environmental variables do change.

VMWare Virtual Environment

High Availability (HA) in a VMWare virtual environment does not activate licensing grace period during a failover as monitored environmental variables do not change.

Disaster Recovery (DR) in a VMWare virtual environment activates a licensing grace period as monitored environmental variables do change.

Antivirus Software

Antivirus Software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems. TechNote TN2865, available from the AVEVA Global Customer Support (GCS) web site, lists important information about antivirus software. Enter your GCS credentials to access the Tech Note.

https://softwaresupportsp.schneider-electric.com/#/okmimarticle/docid/tn2865

Resolved Issues

See the product-specific Readme files for resolved issues.

Known Issues

The following important known issues are listed by their assigned CR or reference number in ascending order. Additional known issues are documented in the product-specific Readme files.

Installation and Uninstallation Issues

796068          

On a Galaxy Repository, uninstalling Application Server results in restoring the ArchestrA User credentials to the registry.

804308

While installing System Platform 2017 on a remote node using an RDP session, you may lose your RDP connection if the Windows Firewall Service is stopped and Startup Type=Manual. If you are unable to reconnect, try the following:

  • If you have another form of Desktop access, such as physical access to the node or virtual access using VM hosting tools, you can use that access to confirm that the installation was successful. The last installation step will ask you to restart. When the node restarts, the RDP access should resume working normally.
  • If you do not have Desktop access, forcibly restart the node (data loss may occur), which will allow RDP to reconnect. Then, run the installation again.

931629

If a System Platform component is removed through the Control Panel ("Install/Uninstall Programs" applet), rather than by running the System Platform installation program (Setup.exe), errors messages will be logged, exception messages such as "FileNotFound" will be displayed, and Application Server deployment will no longer be successful.

Workaround: Use the "Modify" workflow, as described in the System Platform Installation Guide.

  1. Insert the System Platform installation DVD and run Setup.exe.
  2. Select the "Modify" option.
  3. Select or clear the components you want to add or remove and click Next.
  4. When the Verify Change dialog appears, click Modify.
  5. Click Finish when the changes are complete.

1120630

A Modify operation on InBatch 2017 fails when InBatch 2017 or earlier is installed before System Platform 2017 Update 3.

Workaround: Install System Platform 2017 Update 3 first, then install InBatch.

1135229 1157116

If InBatch 2014 R3 or InBatch 2014 R3 SP1 is installed on the same node as System Platform 2017 or 2017 Update 1, upgrading to System Platform Update 3 SP1 may result in a compatibility issue that stops the IDE from working.

Workaround: Upgrade InBatch to version 2017 or later before upgrading to System Platform 2017 Update 3 SP1. InBatch 2017 and later versions are compatible with System Platform 2017 Update 3 SP1.

ArchestrA Service Bus/PCS and Multi-Galaxy Communication Issues

L00123462

In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name (computer machine name). Unpairing galaxies identified by IP address fails when NetBIOS and DNS solutions are unavailable. Where your galaxies are identified by IP address, you must create a temporary host file to map the IP addresses as hostnames for purposes of unpairing.

For example, Node1 and Node2 are identified by IP address and are paired. To unpair them, do the following:

  1. Navigate to the Hosts file on Node1. In Windows 7 and Windows 2008 R2 operating systems, the Hosts file typically can be found at C:\Windows\System32\Drivers\Etc\.
  2. Open the Hosts file in Notepad. In Windows 7 and Windows 2008 R2 systems, you should right click the Notepad executable, and click Run as Administrator, then open the Hosts file from inside Notepad.
    Alternatively, you can click Start, then click Run, then enter the following command in the text box:
    notepad c:\Windows\System32\Drivers\Etc\Hosts.
  3. Edit the Hosts file:
    1. Enter the IP address for Node2.
    2. On the same line as the IP address, provide a node (computer) name.
    3. Enter IP addresses and node (computer) names for each node identified by IP address to be unpaired.
  4. Save and close the Hosts file. You should now be able to unpair the galaxies.

L00123474

Writing from InTouch to a remote galaxy using indirect tags can fail for some of the remote references. Object Viewers on two different nodes may show different values for the same reference. You can avoid this issue by deactivating Advanced Communication Management in the IDE. Additionally, if you use the same indirect tag with scripting more than one time, you can modify your scripts to set the indirect tag's name property to an empty string after the loop completes. For example, in the following script snippet, you would add the line highlighted with bold text:

 

IF bRunScript  THEN

    FOR tagval = 1 TO 3
      indirect.Name = "Testtag" + Text(tagval, "0");
    
        IF indirect.Value > 4  THEN
                indirect.Value  = 0;
            ELSE
                indirect.Value  = indirect.Value  + 1;
                indirect.Value  = indirect.Value  + 1;
            ENDIF;      
    NEXT;
      indirect.Name = "";

ENDIF;

L00133534

Undeploying a galaxy with Object Viewer active will cause Object Viewer to shut down with an informational message that requires acknowledgement (click OK) to complete the shutdown. In a multi-galaxy configuration, with Object Viewer open, undeploying a paired Galaxy, then redeploying the galaxy without properly shutting down Object Viewer, can cause ASB services to fail to reconnect to the redeployed galaxy. To avoid this condition, click OK to shut down Object Viewer before redeploying the galaxy.

L00139918

Uninstalling Wonderware InBatch versions 10.2 or 11.0 installed on a System Platform 2014R2 SP1 system results in a failure to connect to ArchestrA Service Bus (ASB) services. If you uninstall either of these InBatch versions then cannot connect to ASB services, run a repair on System Platform 2014R2 SP1 using Windows' Add/Remove Programs utility.

L00141660

In a system with two GR nodes, attempting to connect from the IDE on one node to a Galaxy on the second GR node does not succeed, and the IDE shuts down.

Workaround: Pair the GR nodes before trying to connect to the Galaxy on the other node. See "Working with Multiple Galaxies > Setting Up a Multi-Galaxy Environment" in the Application Server User Guide for information about configuring multi-Galaxy pairing.

1116282

In a very small set of multi-galaxy (MGC) environments, communications between some System Platform subscribers and a system service they subscribe to may not be secure. In these circumstances, communications still occur, but may not be secure. If all the following elements exist in an MGC topology, communications may occur over an insecure channel:

  • Galaxies are installed across multiple domains.
  • Multi-Galaxy Communication (MGC) is used.
  • One of the following subscribers is on one domain and the MxDataProvider service to which it is subscribed is on another domain:
    • WindowViewer
    • Object Viewer
    • An AppEngine that has input extensions on another galaxy

Workaround:

To ensure that communications are always secure, update the config files as follows.

  1. Locate aaEngine.exe.config and view.exec.config in the ArchestrA\Framework\Bin directory.
  2. Add the following to the <runtime> section of each file:

    <AppContextSwitchOverrides value="Switch.System.IdentityModel.DisableMultipleDNSEntriesInSANCertificate=false" />

  3. Create the config file aaObjectViewer.exe.config in the ArchestrA\Framework\Bin directory.
  4. Add the following text to aaObjectViewer.exe.config:

    <configuration>

    <runtime>

    <AppContextSwitchOverrides value=
    "Switch.System.IdentityModel.DisableMultipleDNSEntriesInSANCertificate=false" />

    </runtime>

    </configuration>

1111134 1121155

In some circumstances, when using the Configurator to configure the System Management Server, you may be prompted to enter your user credentials. This may happen if the logged-in user does not belong to the aaAdministrators or Administrators OS group. If you are a member of either of these groups, enter your user name as DomainName\UserName. The logged-in user should be a direct member of the aaAdministrators or Administrator group. Using the credentials for a user that belongs to nested groups is not supported. That is, you cannot use credentials that belong to a group that is part of aaAdministators or Administrators.

If you are not a member of aaAdministrators or Administrators on the local machine, you can obtain configuration privileges for another OS group by editing the file appsettings.json, and adding the name of the OS group to the file. The full path for this file is:
C:\Program Files (x86)\AVEVA\Platform Common Services\Management Server\appsettings.json.

To add an OS group to the file, add the new OS group after "aaAdminstrators."

"AppSettings": {

"AllowGroups:: [

"aaAdministrators",

"insert new group name here"

]

1161407

With only run-time components of System Platform Update 3 or Update 3 SP1 already installed, the following error is encountered when installing InBatch 2014 R3SP1, Batch Management 2017, or RMP 2018 SP1: "Error 1603 A newer version of Archestra Service Bus Framework 4.2.2 is already installed."

Workaround:

  1. Install InBatch/Batch Management/RMP first and then install System Platform 2017 Update3 or Update3 SP1. You will be prompted to upgrade ASB Framework and Licensing,
  2. Once this is complete, rerun System Platform installation to add products and components.

Alternate workaround:

If you choose to install System Platform 2017 Update3 or 2017 Update3 SP1 first, then:

  • Select and install GR components (not just run-time components), and then install InBatch/Batch Management/RMP.

InTouch OMI Issues

1160616

If an admin user logs in, launches a ViewApp, and then logs off the system while leaving the ViewApp running, registry keys are unloaded in the profile of the user account. This results in continuous errors from CheckPointFileServer in the logger similar to: ""INVALID HRESULT LINE765 File CheckPointFile.cpp hResult 80003fa after logging off and logging on as different users (non-admin)."

Cause: This is a known Microsoft issue. This problem typically occurs after an administrator uses a service account to log in to the server for an interactive session, and then logs off. For example, an administrator may log in to a Web Front End (WFE) server by using the farm account, and then log off. This activity forces the registry keys to be unloaded in the profile of that account, and makes the keys unavailable for future use. Microsoft recommends using either of the following workarounds to resolve this issue. For more information, see:
https://docs.microsoft.com/en-us/sharepoint/support/server-admin/800703fa-illegal-operation-error

https://blogs.msdn.microsoft.com/distributedservices/2009/11/06/a-com-application-may-stop-working-on-windows-server-2008-when-the-identity-user-logs-off/

Workaround 1: Do not log in to the server for interactive sessions by using a service account.

Workaround 2: Disable the related Windows User Profile Service feature as follows:

  1. Open the Group Policy editor (Gpedit.msc) on the affected server.
  2. Open the UserProfiles folder in the following path:

    Computer Configuration > Administrative Templates > System > UserProfiles
  3. Locate the "Do not forcefully unload the user registry at user logoff" setting.
  4. Change the setting to Enabled.

L00150114

SR59513303: TheGetCPTimeStamp() scripting method, when used in an InTouch OMI action or named script within a symbol, does not return the timestamp at run time. Instead, it returns characters for the timestamp format, such as "mm/dd/yyyy hh:mm:ss." No errors or warnings will appear in the logger. This is similar to issue 777504, listed below.

Workaround: Use the GetCPTimeStamp() method in an object script instead of a symbol script.

1100582

Switching languages during run time while using multi-content panes that use locale-specific scripting calls can sometimes result in errors in the logger.

Workaround: Restart the ViewApp after switching the run-time language. This action fully resolves the issue with no loss of functionality.

988079

If you upgrade or migrate from version 2017 or 2017 Update 1, and have an InTouch OMI ViewApp that uses the ShowGraphic scripting method, modeless windows will behave differently at run time in this version of InTouch OMI.

  • Old behavior: a modeless window called by ShowGraphic was displayed in an InTouch OMI pane.
  • New behavior: a modeless window called by ShowGraphic is now be displayed in a modeless popup window. A new scripting method, ShowContent, has been added. Use ShowContent to load a graphic or layout into a pane. Use ShowGraphic to load a graphic into a modeless or modal popup window. Note that the modal windows called by ShowGraphic will continue to behave the same way as in previous releases (a modal popup window is displayed).

Missing NavTree

After upgrading or migrating an InTouch OMI ViewApp from 2017 to 2017 Update 1, a warning message states that the NavTree entity could not be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.”

Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading to System Platform 2017 Update 1:

  1. Open the ViewApp or Layout that shows the warning.
  2. In the ViewApp or Layout editor, look in the Actions list for all references to “NavTree.” An icon showing “Content not available” will be displayed for these references.
  3. To see the entire action list for a ViewApp, toggle the Actions for Primary switch to show Actions for Home (does not apply to the Layout editor).
  4. Replace the NavTree object with the new NavTreeControl.
    1. Search for NavTreeControl under the Toolbox tab.
    2. Drag the NavTreeControl onto the pane to replace the NavTree.
  5. Confirm that you want to replace the content, then save the ViewApp or Layout and close the editor.
  6. Verify Layouts and ViewApps no longer show any warnings related to the NavTree.
  7. Deploy the ViewApp.

Workaround 2: To replace references to NavTree when importing packages from System Platform 2017:

  1. Launch the IDE and open the “Find” dialog.
  2. Search for “NavTree” using the default search settings.

    If the package file contains the obsolete NavTree object, it will be listed in the search results.

  3. Double-click the NavTree search result, which will select the NavTree object in the Graphic Toolbox.
  4. Delete the NavTree object from the Graphic Toolbox.
  5. Use Workaround 1 to replace the NavTree object with the new NavTreeControl object.

     

774717           

When an InTouch OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under certain circumstances the application may stop responding:

  • InSightApp
  • MapApp
  • WWWebAppControls

Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running the ViewApp on 1080p monitors, do not attempt to span multiple monitors.

777504

The GetCPQuality() scripting method is not supported in InTouch OMI. If used in a ViewApp, it always returns quality = 0 (bad quality). This is similar to issue L00150114, listed above.

781006

If an invalid custom property is added to a symbol, no warning is logged in the System Management Console, even though no value is displayed for the custom property.

781620

The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are not rendered correctly.

784470

Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp.

784474

A tooltip may partially cover the element with which it is associated in the deployed ViewApp.

787192

When OSGroup security mode is used, the VerifiedWrite dialog is not displayed when you modify the value of a VerfiedWrite attribute from a combobox, if you first attempted to perform the VerifiedWrite without having the correct security credentials.

789857

When an element style animation is configured with both a fill color and a blink color, the blink animation and color remain when an element style override is applied that specifies only a fill color and has the blink check box deselected.

Workaround: Set the initial state without blink, then apply overrides as needed with blink enabled.

789958

On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing between items, which can make it harder to read object names.

794383

When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is shown at run time (private values should not be shown). Similar situations occur when:

  • An override values for a custom property that is later made private. The override is also shown at run time.
  • An override is applied to a custom property, and later the custom property is locked (can no longer be overridden). When the ViewApp is redeployed, the override value is still shown.

Workaround: Manually validate the outermost symbol and then deploy the ViewApp.

Map App / Mobile Access Issues

797198           

If the unfill color is set to a gradient in an Unfill animation with an animation fill style, and the fill style animation is changed, it changes the unfill color property.

797226

If the expression type is set to string in the truth table for fill color animation, the fill style does not change when the value changes.

Application Server Issues

933752

Starting the IDE can take up to a minute if the node on which it is running is not connected to the internet.

Root Cause: To enhance security and reliability, System Platform will validate certificates. Windows then performs a check to see if the certificate has been revoked. Without an internet connection, Windows waits until the timeout for this check has been reached before allowing the IDE to start.

Workaround 1 (preferred): This method changes the default timeout for the certificate check.

  1. Open the Local Security Policy settings (enter "Local Security Policy" in the Start Menu search bar).
  2. Select Public Key Policies.
  3. Under Object Type, right-click on Certificate Path Validation Settings.
  4. Select the Network Retrieval tab.
  5. Set the both "Default retrieval timeout settings" to 1 second, or to the value you prefer. Typically, both URL retrieval and path validation cumulative retrieval require only milliseconds to complete.
  6. Save the new settings and exit.

Workaround 2: This method disables checks for revoked certificates.

  1. From the Control Panel or Internet Explorer, open Internet Options.
  2. Select the Advanced tab and scroll down to Security.
  3. Uncheck the option, "Check for publisher's certificate revocation."
  4. Save the new settings and exit.

Workaround 3: This method installs the certificates that the operating system is attempting to validate onto the local machine. Once installed locally, the operating system will no longer need to access the network to retrieve them.

  1. Locate any DLL or EXE file from AVEVA Software, LLC.
  2. Right-click on the file and select Properties.
  3. Select the Digital Signature tab.
  4. Select the SE certificate from the list.
  5. Select View Certificate.
  6. On the dialog that appears, select Install Certificate and follow the prompts to install the certificate on the local machine.
  7. Locate the file Flxcore.dll and repeat steps 2 through 6 for it. By default, this file is located in:
    C:\Program Files (x86)\Common Files\ArchestrA\Licensing Framework\License API2

1157633  

As a result of security enhancements in System Platform 2017 Update 3 SP1, ArchestrA object scripts are unable to connect to SQL Server.

Workaround:

  1. Connect to SQL Server Management Studio.
  2. In Object Explorer, select Security > Logins.
  3. Select and right-click <NodeName>\aaAdministrators from the Logins list and open Properties.
  4. In the "Database role membership" window, add the following database roles:
    • db_datareader
    • db_datawriter
  5. Click OK.

 

 

1173359

A Build operation using the Application Object Toolkit 2014 (AOT) with System Platform Update 3 SP1 does not succeed.

Workaround: Do the following before building the object:

  1. Install the 4.7.1 .NET Developer Pack on the same system with Application Server and AOT.
  2. In Visual Studio, set the AOT Object Editor target Framework to 4.7.1.

InTouch Access Anywhere Issues

The following known issues are in addition to those documented in the InTouch Access Anywhere Readme.

L00144565

Installing InTouch Access Anywhere through the Modify workflow can cause various issues related to uninstalling the product at a later time. These include:

  1. Registry keys to store the InTouch Access Anywhere installation path are not created. As a result, if you try to uninstall InTouch Access Anywhere later, the uninstall operation will not complete.
  2. You may not be able to launch an InTouch View.exe application after uninstalling, and then reinstalling, InTouch Access Anywhere.

Workarounds:

For issue #1 (registry keys not created), do the following:

  1. Add registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\ITAA\ITAAServer
  2. Create a string value under the new registry key named InstallLocation, and specify the ITAA install location for its value. For example:
    C:\Program Files (x86)

For issue #2 (unable to launch InTouch View.exe application), do the following:

  1. Uninstall InTouch Access Anywhere.
  2. Restart the computer.
  3. Re-install InTouch Access Anywhere.

Historian Issues

924302

When installing Historian along with any other component, and the other component requests a system restart, if you restart immediately after closing out the Configurator, a number of warnings may appear in the logger from the Historian services. This is caused by a timing issue.

The warning messages can be safely ignored because they do not affect the configuration of the Historian, and do not have any effect on the system during or after the system restart.

931966

When using silent install to upgrade Historian to System Platform 2017 Update 1 from a version that set a default password for SQL Server users, warning messages are logged that alert you to set new passwords for various system users after the Configurator runs. Your system will continue to operate normally without resetting the passwords, but changing the passwords will increase system security.

Licensing Issues

779958

When the same license is acquired on both a local node and in an RDP session that originates from the same node, the License Manager may not show all the licenses that have been acquired. This occurs even though the licenses are counted properly on the license server. The license count that you see applies only to the node you are viewing. Thus, once you reach your maximum number of licenses, you will not be able to acquire additional licenses, even though the license manager may indicate that more licenses are available.

793643

If you have not set a default browser, and you install System Platform with AVEVA Enterprise licensing selected, clicking the AVEVA Enterprise License Manager shortcut does not open the License Manager in the browser as it should. Instead, the shortcut opens in Windows Explorer. From Windows Explorer, you cannot open License Manager (the OK button is inactive).

Workaround: Follow the instructions for your operating to set the default browser, and then open the AVEVA Enterprise License Manager from the shortcut, or:

Open your browser and copy the shortcut link, http://localhost/AELicenseManager, directly into the browser's address bar.

Sentinel Issues

6306

Email alerts cannot be sent through secured SMTP.

7123

Domain User Groups can be added in the Sentinel Manager User configuration area successfully, but users of an added domain group cannot log in to the application.

7211

In the Configurator, under Sentinel System Monitor > Sentinel Manager > Advanced, changes made to the default HTTP or HTTPS ports are not retentive.

Workaround: On the Sentinel Manager and all machines being monitored:

  1. Stop the Sentinel agent and SAIM service.
  2. In the registry, navigate to HKLM > Software > WOW6432Node > Wonderware > ArchestrA > Plugins > Sentinel System Monitor > Sentinel Manager.
  3. Change the “SslPort” port key to the desired port.
  4. Restart the agent and SAIM. Also make sure both the services are in automatic startup mode.

7294

Following platform undeploy, the Runtime Data Provider shuts down. On redeploy of the platform, the Runtime Provider does not restart and resume monitoring until the Galaxy is rediscovered.

Workaround: Following redeploy of a platform, manually rediscover the Galaxy (in the Galaxy Diagram area). Alternatively, stop and restart the Sentinel Agent Service.

ArchestrA Alarm Control Issues

If you create a filter for a history block query that results in no matches, "Not Connected" appears in the status bar and a warning is logged to the ArchestrA Logger. The status bar should show "Connected" even though no matches are returned.

Documentation

The System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the System Platform DVD:

InstallFiles\CD-ApplicationServer\UserDocs

InstallFiles\CD-Historian\UserDocs

InstallFiles\CD-HistorianClientUserDocs

InstallFiles\CD-Intouch\UserDocs

To view the documentation, you must first download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.

You can also access online Help systems from within the software.

Common Components and Utilities User Documentation

  • System Platform Installation Guide. This guide provides information on installing the System Platform, including hardware and software requirements and migration instructions.
  • Log Viewer User's Guide. Explains how to use the Log Viewer utility to determine system diagnostics.
  • Log Flag Editor Utility Guide. Explains how to turn on and off certain diagnostics logging messages.

InTouch HMI 2017 Update 3 SP1 Documentation

  • InTouch HMI Concepts and Capabilities Guide. Describes all of the features and main concepts in the InTouch HMI without going too deep into the technical and procedural details.
  • InTouch Modern Application Guide. Describes the tasks to manage Modern applications from Application Manager and configure Modern applications from WindowMaker.
  • The InTouch HMI Application Management and Extension Guide. Describes how to create and manage InTouch applications locally and in a network environment.
  • InTouch HMI Data Management Guide. Describes how to work with data items in the InTouch HMI and connect your application to the physical devices in your plant environment.
  • InTouch HMI Visualization Guide. Describes how to develop the graphical operator interface of an InTouch application.
  • InTouch HMI SmartSymbols Guide. Describes how to create reusable templates for graphic symbols that can save you a lot of engineering time and effort.
  • InTouch HMI and ArchestrA Integration Guide. Describes how to integrate the InTouch HMI and ArchestrA technology to develop more robust applications that use richer graphics.
  • InTouch HMI Alarms and Events Guide. Describes how to configure alarms for your data items, how to view and acknowledge alarms, and how to use the alarm clients and utilities supplied with the InTouch HMI.
  • InTouch HMI Scripting and Logic Guide. Describes how to write scripts in the InTouch HMI to automate common tasks and processes. This guide includes a reference of the InTouch scripting language and functions.
  • InTouch HMI Supplementary Components Guide. Describes software components that you can optionally install and use with the InTouch HMI.

Application Server 2017 Update 3 SP1 Documentation

  • Application Server User's Guide. Explains configuring and deploying Application Server applications.
  • Creating and Managing ArchestrA Graphics User's Guide. Explains how you create and manage graphical symbols using the ArchestrA Symbol Editor within the Integrated Development Environment (IDE).
  • Application Server Scripting Guide. Reference for the scripting language in Application Server.
  • Object Viewer User's Guide. Explains how to acquire run-time data using the Object Viewer.
  • Guide to the ArchestrA Alarm Control. Explains how to configure the alarm control (client) to show current and historical alarms and events in a grid.
  • Guide to the ArchestrA Trend Client. Explains how to configure a chart to trend real-time data values.
  • Platform Manager User's Guide. Explains how to start and stop system components.
  • Galaxy Database Manager User's Guide. Explains how to backup and restore the Galaxy database.
  • InTouch HMI and ArchestrA Integration Guide. Explains how you can use the ArchestrA Integrated Development Environment (IDE) to manage InTouch HMI applications so that you can use symbols you create in the ArchestrA Symbol Editor.
  • InTouch OMI Help. Explains how you can use the InTouch Operations Management Interface (OMI) to create visual applications (ViewApps) that incorporate the functionality needed by both operational and information technology teams in a production environment. Access to this help is available by pressing F1 when using the ViewApp, Layout, Screen Profile, or External Content editors. These editors are launched through the Application Server IDE.

Historian Server 2017 Update 3 SP1 Documentation

  • Historian Concepts Guide. Provides an overview of the entire Historian system and describes each of the subsystems in detail.
  • Historian Administration Guide. Describes how to administer and maintain an installed Historian, such as, configuring data acquisition and storage, managing security, configuring replication, and monitoring the system.
  • Historian Database Reference. Provides documentation for all of the Historian database entities, such as, tables, views, and stored procedures.
  • Historian Glossary. Provides definitions for terms used throughout the documentation.

Historian Client 2017 Update 3 SP1 Documentation

  • Historian Client Software User's Guide. Describes how to use stand-alone applications, Microsoft Office add-ins, and ActiveX and .NET controls to retrieve and display data.

Documentation Issues

This section lists important System Platform documentation corrections. For documentation corrections for individual System Platform products, see the individual product Readme files.

Item

Location of Change

Existing Documentation

Change

1

ArchestrA Scripting Guide (Scripting.pdf)

"IF ... THEN ... ELSEIF ... ELSE ... ENDIF" section, page 112

ArchestrA IDE Help (IDE.chm)

"IF ... THEN ... ELSEIF ... ELSE ... ENDIF" topic under Creating Scripts

In the syntax description, semicolons are shown after THEN, ELSEIF, and ELSE.

Remove the semicolons that follow THEN, ELSEIF, and ELSE. Corrected text reads:

IF <Boolean_expression> THEN

[statements];

[ { ELSEIF

[statements] } ];

[ ELSE

[statements] ];

ENDIF;

InTouch Access Anywhere Version 2017 Update 3 SP1 Readme

Last revision: 5/31/2019

About This Readme

This Readme provides information about Wonderware InTouch Access Anywhere Update 3 SP1, Version 17.3.100.

Wonderware InTouch Access Anywhere Overview

InTouch Access Anywhere™ provides remote access to InTouch™ applications with an HTML5 Web browser running on a desktop computer or a mobile device. Any Web browser that supports HTML5 can be used as the client to view InTouch applications running on a remote desktop server. InTouch Access Anywhere enables you to select an InTouch application from a list and view it running in WindowViewer.

The InTouch Access Anywhere installation media provides the following:

  • InTouch Access Anywhere Server: Enables you to view remote InTouch applications hosted on Terminal Servers with an HTML5-compliant web browser running on mobile devices or a desktop.
  • InTouch Access Anywhere Secure Gateway: Optional server that provides secure remote connections from clients running on unsecured networks to internal network resources. The Secure Gateway provides authentication and authorization services as well as data encryption.

Requirements, Browsers, and Mobile Devices

This section summarizes InTouch Access Anywhere installation requirements, supported browsers, and considerations for viewing InTouch applications on mobile devices. For more detailed information, see the Wonderware InTouch Access Anywhere Documentation

Installation Requirements

The following list describes the prerequisites to install the InTouch Access Anywhere Server or Secure Gateway.

  • InTouch Access Anywhere Server cannot be updated by installing Update 3 SP1 on a computer currently hosting an earlier version.

    Important: All existing instances of InTouch Access Anywhere components must be removed from the computer before installing Update 3 SP1. Earlier versions of InTouch Access Anywhere Servers cannot be modified or repaired using Update 3 SP1.

  • The computer that will host the InTouch Access Anywhere Server must be running one of the following 64-bit versions of Windows Server:
    • Windows 2012 Data Center (Not Standard Edition)
    • Windows 2012 R2 Standard and Data Center
    • Windows 2016 Standard and Data Center
  • You must install InTouch Access Anywhere Secure Gateway on a computer running one of the following versions of Windows:
    • Windows 10 Professional or Enterprise (Version 1607 or later)

      Note: Windows 10 does not support .NET 4.5.2. .NET 4.6.2 and later must be installed for Windows 10 support.

    • Windows 2012 Data Center (Not Standard Edition)
    • Windows 2012 R2 Standard and Data Center
    • Windows 2016 Standard and Data Center
  • .NET Framework 4.6.2 Full Installation or later must be installed on the host computer if you are completing a stand-alone installation of InTouch Access Anywhere.

    Note: If you are installing InTouch Access Anywhere from System Platform 2017 Update 3 SP1, the installer verifies the current, installed versions of .NET on the computer. When only earlier versions of .NET are detected, the installer automatically updates the computer to .NET 4.7.2.

  • You must have an InTouch 2012 R2 TSE (RDS) or newer license activated. When InTouch is launched by InTouch Access Anywhere, this RDS license will be acquired per browser session. The license is released when the InTouch application running within the RDS session is closed.
  • InTouch Access Anywhere Server and Wonderware InTouch HMI must be installed on the same Windows Server computer where the RDS Server Role is enabled. For detailed instructions, refer to the InTouch Access Anywhere Server Administrator Manual.

    Per-Device RDS licenses are not supported.

Important Security Requirement: Securely Deploying InTouch Access Anywhere

Direct access to the InTouch Access Anywhere Secure Gateway over the Internet is not supported. Accessing the Secure Gateway by means of a VPN tunnel for all remote connections is recommended.

Browsers

InTouch Access Anywhere can be accessed from smart phones, tablets, and laptop computers that provide an HTML5-compliant web browser.

Browsers Tested with InTouch Access Anywhere

Browsers verified to work with InTouch Access Anywhere include the following:

  • Microsoft Edge
  • Microsoft Internet Explorer 11
  • Firefox version 38 and later
  • Safari version 5 and later
  • Chrome version 12 and later
  • Opera version 11 and later

    Important: Only the browser versions listed above have been tested on the specified hardware platforms (PCs, tablets and Smart Phones). No testing has been done on HTML5 browsers running on other devices not included in the list shown above (SmartTVs, eBook Readers, or game consoles).

Functionally Compatible Browsers

Certain versions of the browsers listed above, such as:

  • Microsoft Internet Explorer 10
  • Firefox versions less than 6
  • Safari versions less than 5
  • Chrome versions less than 12
  • Opera versions less than 11

are in theory functionally compatible with InTouch Access Anywhere. While you may be able to use these versions of the web browsers with InTouch Access Anywhere, specific behaviors are unknown because no formal testing has been conducted.

Browsers: Important Notes

Although Wonderware InTouch Access Anywhere supports the listed browsers, you should review the Known Issues and Behaviors section of this Readme for issues specific to each browser.

Mobile Devices

Run-time interactions with InTouch applications are different on mobile devices than on traditional desktop computers. For example:

  • Touch gestures perform some of the tasks that a mouse would do on a desktop or laptop, but not all mouse events have an equivalent touch gesture.
  • Many mobile devices have built-in software keyboards instead of physical keyboards, which do not have keys such as F1-F12, CTRL, and ALT.

When using InTouch Access Anywhere to remotely view and interact with your applications, it is important to be aware of the behavior differences among devices, operating systems, and browsers. For the best user experience, you should become familiar with the touch interfaces in the devices you will use, and factor these differences into the design of your InTouch applications. For example:

  • Input animations do not need to invoke the InTouch or Windows operating system keyboards as mobile devices typically have their own.
  • Existing InTouch applications that make use of mouse events and keys or key combinations without a supported equivalent in a touch environment may require you to modify your application to use alternate supported methods.

Resolved Issues

This section lists defects resolved with this release of InTouch Access Anywhere.

Defect Number

Description

L00150532

The Display setting 'Open browser links on client (URL redirection)' did not work as expected.

Known Issues and Behaviors

This section describes known issues and platform/browser-specific behaviors in InTouch Access Anywhere. The issues are grouped by areas affected by the issue. Workarounds are provided when available. You can also refer to the InTouch Access Anywhere user documentation for more information.

Wonderware InTouch Access Anywhere Documentation

Wonderware InTouch Access Anywhere product documentation is provided as a set of Portable Document Files (PDF), which are located at the root of CD installation disc.

InTouch Access Anywhere Product Documentation Name

File Name

Wonderware InTouch Access Anywhere User Guide

ITAA_UserManual.pdf

Wonderware InTouch Access Anywhere Server Administrator Manual

ITAA_Server_AdminManual.pdf

Wonderware InTouch Access Anywhere Secure Gateway Administrator Manual

ITAA_Gateway_AdminManual.pdf

You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.

After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a PDF with the Adobe Reader Open command from the File menu.

Copyright © 2019 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us