System Platform 2017

Wonderware System Platform Version 2017 Readme

Last revision: 5/8/2017

This document contains important information about Wonderware System Platform Version 2017. This release of Wonderware System Platform includes a new integrated HMI and visualization module, along with new features and enhancements for the component products of Wonderware System Platform.

All New! Server-based Licensing

Wonderware System Platform 2017 utilizes a new server-based licensing subsystem that provides centralized license management. This replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.

If you are upgrading an existing installation to Wonderware System Platform 2017, 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 Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf), located at the root of the DVD.

All New! InTouch OMI

Wonderware System Platform 2017 introduces InTouch OMI, the first Operations Management Interface to leverage both Human Machine Interface (HMI) and Supervisory Control and Data Acquisition (SCADA) systems and deliver a next generation visualization experience.

InTouch OMI extends traditional HMI and SCADA applications to deliver a convergence platform for both Operational Technology (OT) as well as Information Technology (IT).

One key aspect of InTouch OMI is its ability to automatically assemble applications based on a data model, resulting in minimal engineering and manageability that has not previously been available.

InTouch OMI enables the first industrial application that will deliver a tailored and contemporary experience to any environment or device, including control rooms, industrial panels, desktops, laptops, tablets and phones.

Readme Files for Other Products in this Release

To access individual product Readme files, insert the Wonderware System Platform installation DVD and click on the link. Review the known and resolved issues contained in each Readme file for the following component products are updated for this release:

• Wonderware Application Server 2017
• Wonderware InTouch HMI 2017
• Wonderware Historian Server 2017
• Wonderware Historian Client 2017

The Wonderware InTouch Access Anywhere Readme file is included at the end of this Readme.

In This Document Important Information for Microsoft Windows 2016 How to Find the Latest Product Requirements and Compatibility Information New Features in Wonderware System Platform 2017 Web Help Display and Video Playback System Requirements and Guidelines Wonderware System Platform Installation Wonderware System Platform Upgrade and Migration Licensing Information Antivirus Software Exclusions Known Issues Documentation Wonderware InTouch Access Anywhere 2017 Readme

Important Information for Microsoft Windows 2016

When Wonderware System Platform is installed on a Windows Server 2016 system with Remote Desktop Services enabled, WindowViewer will fail to launch. WindowMaker cannot be closed unless shut down via the Task Manager.

Workaround:

1. Download and install the latest Microsoft Windows update KB3194798 on the Windows 2016 system. This Windows update is located at the following URL:

   http://www.catalog.update.microsoft.com/Search.aspx?q=KB3194798

2. After installation of the update is complete, restart the system and install Wonderware System Platform 2017.

   Important: The Microsoft update can be installed before or after Wonderware System Platform is installed. However, it is recommended that you install the update prior to installing System Platform.

How to Find the Latest Product Requirements and Compatibility Information

For important information about this product release, go to the Schneider Electric Software Global Customer Support (GCS) web site. Information on the GCS web site includes product requirements, compatibility, as well as downloads from previous releases. Once 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 Interoperability: list of products that can communicate with each other through a common message protocol

New Features in Wonderware System Platform 2017

System Platform Version 2017 provides a number of significant new features and product enhancements.

Enhanced Product Integration

System Platform Version 2017 provides a tighter level of integration between its component products. This improved integration between components increases usability, functionality, and performance.

Enhanced Security

System Platform Version 2017 is more secure than ever. Security enhancements have been added to this release of Wonderware System Platform and its component products.

Centralized License Management

All products included with Wonderware System Platform 2017 now leverage the server-based Schneider Electric Licensing System.

InTouch Operations Management Interface

InTouch OMI ViewApp

The InTouch OMI ViewApp, an advanced visualization HMI component, is now integrated into Wonderware System Platform to provide enhanced visualization, graphics management, and other functions and capabilities. Features include:

• Built-in navigation
• Integrated security
• Single Sign-On service
• Global tabs
• Support for Multi-Touch screens
• Preservation of run-time changes
• SCADA playback
• Support for 4K monitors
• Support for multiple monitors
• Switch between different form factors during run time

Note: In this release, InTouch OMI ViewApps do not automatically populate the InTouch Access Anywhere applications list.

Resolution Independence for Displays

InTouch Operations Management Interface eliminates the need to configure run-time graphic elements for specific screen resolutions and configurations. Multiple form factors (including (phones and tablets), screen resolutions, aspect ratios, and multi-monitor displays can be used, and content will automatically resize to fit the target screen.

Support for Touch-Enabled Displays

The InTouch OMI ViewApp supports touch and multi-touch gestures, such as pan, zoom, swipe, close, and double-tap. Automatic detection of touch-screen devices is built-in.

New Features in Wonderware Application Server 2017

Object Wizards

Object Wizards constitute a new user interface in the IDE Object Editor that lets you associate attributes, symbols, and scripts within a configurable template. Through the Object Wizard interface, users configure instances by simply answering a series of prompts or questions, thus reducing the amount of product knowledge and training required.

Object Wizards are flexible and can reduce the need for a deep object derivation tree, and can also reduce the overall number of unrelated templates that are needed. The result is fewer templates to manage and increased scalability.

Multiple symbol configurations,including symbols that contain their own wizards, can be added to a single template. Symbols in the Graphic Toolbox can be linked to objects, rather than being embedded in the objects. With Object Wizards, attributes, scripts, and symbols can be flagged to only propagate to derived instances that require them, thus providing leaner run-time objects.

Link Symbols in the Graphic Toolbox to Objects

Instead of embedding symbols into each individual object, you can link symbols in the Graphic Toolbox to multiple objects. This provides centralized control, since changes applied to the symbol automatically propagate to each object with which the symbol is linked. Symbols that include a Symbol Wizard, such as those in the Situational Awareness Library, can be maintained more easily, without the need for duplication, or the management issues that can arise from having to manage many similar symbols.

Pop-Up Editors with Integrated Web Help

The Application Server IDE includes several new editors for creating InTouch OMI ViewApps, Screen Profiles, Layouts, and Assets. Each editor opens automatically when you select the applicable object for editing. Web help, including videos, can be accessed through the editor by pressing F1. See Web Help Display and Video Playbackfor details.

New Features in InTouch HMI 2017

InTouch 2017 provides support for the latest versions of Microsoft products and includes new run-time and development-environment features. Run-time features are designed to improve usability, IT compliance, and connectivity. Development features are designed to improve engineering efficiency and usability.

Run-Time Features and Enhancements

• Pan and Zoom
• Enhanced Events and Alarms Client Control
• Improved performance!
• More extensive filtering and sorting capabilities
• Improved default settings
• Ability to run WindowViewer as a service
• OI Gateway – OPC UA connectivity
• Can be used with new visualization technology (InTouch HMI and InTouch OMI in the same Galaxy)

Development-Environment Features and Enhancements

• New InTouch Script Editor (for Classic, Modern, and Managed InTouch)
• Application Target Resolution (for Classic, Modern, and Managed InTouch)
• Application Templates (for Modern and Managed InTouch)
• Window Templates (for Modern and Managed InTouch)
• "Frame-type" Windows (for Modern and Managed InTouch)
• Thumbnail refresh (for Modern and Managed InTouch)
• Script DLL Import (new for Modern InTouch)
• Control DLL Import (new for Modern InTouch)

New Licensing Technology

• Activation-based – no more dongles!
• Centralized license management
• Incremental capabilities
• Reservation capabilities

New Features in Wonderware Historian 2017

Enhanced auto-summary system

Provides fast data retrieval, even for long data periods

Alarm and Events replication

This version includes replication support to on-premises tier-2 servers or Wonderware Online InSight.

Cyber-security improvements

The requirements for using Admin privileges are reduced.

Support for SQL Server instances

Support has been added to allow Historian Clients to use a SQL Server instance to connect to the Historian.

Updates for Wonderware Historian InSight

• Dashboard enhancements (customization and auto-refresh
• Ability to plot discrete tags
• Pan and zoom in line charts
• Multi-axis and stacked tags mode in line charts

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.

System Requirements and Guidelines

Hardware Requirements Notes
Operating System, Firewall, .NET Framework, and Virtualization Notes	Operating System and Software Requirements for Wonderware System Platform 2017 Windows Operating System Notes .Net Notes SQL Server Notes Virtual Environment Notes Firewall Notes	Operating System Notes: Common for Wonderware Products Operating System Notes: Wonderware InTouch HMI 2017 Operating System Notes: Wonderware Application Server Operating System Notes: Wonderware Historian Server Operating System Notes: Wonderware Historian Client	.NET Framework Requirements and Compatibility Considerations for SQL Server Considerations for SQL Server Express
Third-Party Application Prerequisites

Hardware Requirements Notes

Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for Wonderware Application Server 2017. Refer to the following Microsoft Web sites for Windows and SQL Server hardware requirements.

Windows requirements

• Windows Server 2016 System Requirements
• Windows Server 2012 R2 System Requirements
• Windows Server 2012 System Requirements
• Windows 10 System Requirements

  Note: Wonderware System Platform 2017 is not supported on Windows 10 versions prior to version 1607 (Anniversary update; OS build 14393).

• Windows 8.1 System Requirements

SQL Server requirements

• Hardware and Software Requirements for Installing SQL Server 2016
• Hardware and Software Requirements for Installing SQL Server 2014
• Hardware and Software Requirements for Installing SQL Server 2012

Wonderware Historian Hardware Guidelines

• Wonderware Historian is not supported on cluster hardware.
• Do not use the Wonderware Historian computer as a domain controller.
• If you are running the Wonderware 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 Wonderware 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

• Firewall Notes
• Operating System Notes: Common for Wonderware Products
• Operating System Notes: Wonderware InTouch HMI 2017
• Operating System Notes: Wonderware Application Server
• Operating System Notes: Wonderware Historian Server
• Operating System Notes: Wonderware Historian Client
• .NET Framework Requirements and Compatibility
• Virtual Environment Notes

Operating System and Software Requirements for Wonderware System Platform 2017

The latest product information for each Wonderware 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)
Wonderware Application Server	Windows 8.1 Professional Windows 10 Version 1607	Windows Server 2012 (Embedded or Data Center)
Wonderware InTouch
Wonderware Historian
Schneider Electric Licensing
Wonderware InTouch Access Anywhere	Server OS is required

Wonderware System Platform 2017 web clients

The following web clients are included with Wonderware System Platform 2017:

• InTouch Access Anywhere Client (HTML5 Browser)
• Historian InSight Client
• Schneider Electric Software 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,0000 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 Schneider Electric Software 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 Wonderware System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are three exceptions. Wonderware 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.5.1 or higher. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility.
• .NET 3.5 is installed to support various SQL Server versions and the System Platform Management Console (SMC).

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 Wonderware System Platform 2017:

• Hyper-V (version is based on the operating system utilized)
• VMWare VSphere 6.0, including HA/DR
• VMWare Clients, including Horizon - Application Remoting
• Cloud Virtualization - Azure
• VMWare Workstation, Version 11 and higher

Firewall Notes

In order to establish communication with other components and services on the network, Wonderware System Platform and ArchestrA Service Bus (ASB) Services require certain network ports to be opened in the Windows Firewall. Typically, this is automatically done during the Wonderware System Platform installation. However, if the Windows Firewall is enabled at time of installation or if an alternative firewall is in use during installation, 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 Wonderware Application Server User's Guide.

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 2017, 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 Schneider Electic Software 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 Wonderware Application Server is minimal as most Wonderware Application Server processes run as services. One impact to Wonderware Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware 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 Wonderware 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: Wonderware InTouch HMI 2017

Wonderware InTouch HMI 2017 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 on Windows Vista and Later Operating Systems.
• Wonderware InTouch HMI 2017 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. These changes also apply to currently-supported operating systems.
• Hovering to select from the Windows keyboard does not work in currently-supported operating systems.

Wonderware InTouch HMI 2017 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.

Wonderware InTouch HMI 2017 Support for Windows User Account Control

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

Operating System Notes: Wonderware 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 Wonderware 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 Wonderware 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.

Wonderware Application Server and User Account Control Level

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

Operating System Notes: Wonderware 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 Wonderware Historian node (a second node with the Wonderware 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: Wonderware Historian Client

When the Wonderware Historian Client application is running on Microsoft Windows 7, Windows Server 2008 R2, and later operating systems, User Account Control can be enabled and running as non-administrator.

.NET Framework Requirements and Compatibility

IMPORTANT: Wonderware System Platform 2017 installs .NET 4.5.2 if the currently installed version of .NET is 4.5 or lower. If .NET 4.5.1 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2017, we strongly recommended that you:

• Back up your applications
• Familiarize yourself with the changes introduced by Microsoft in the .NET Framework
• Review your .NET scripts and .NET controls for any required changes

After upgrading to Wonderware System Platform 2017, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.5.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.  

Wonderware System Platform 2017 leverages Microsoft .NET Framework 4. The Wonderware System Platform installation program will install .NET 4.5.2 if your system uses version 4.5 or lower. No change is made if your system uses .NET 4.5.1 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware 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. Wonderware System Platform 2017 will use .NET 4.5.1, 4.5.2, or later.  

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.5.1 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to Wonderware System Platform 2014. 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. 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.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 Wonderware System Platform installation program. If you select SQL Server Express during Wonderware System Platform installation, it will be installed automatically (applicable to small installations only).

The Wonderware 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 Wonderware 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 Wonderware 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:
  • Upgrade to SQL Server 2016
  • Upgrade to SQL Server 2014
  • Upgrade to SQL Server 2012
  • Migrate SQL Server 2000 to SQL Server 2012
  • T-SQL scripts to migrate SQL server 2000 user databases to SQL server 2012
  • ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2012
• 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 Wonderware 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 Wonderware 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 SP1 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 Wonderware 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 Wonderware InTouch HMI will work without issue. Note that in this scenario, each component uses a dedicated instance of SQL Server 2014 Express with Tools SP1 .
  • Installing Wonderware InTouch HMI first, which silently installs and configures SQL Server 2014 Express with Tools SP1, 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 SP1 is limited to the lesser of one CPU socket or four processor cores.
• For InTouch HMI-only installations, the Wonderware System Platform installer will automatically install SQL Server Express 2014 with Tools SP1 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 Wonderware System Platform installation option. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.

Additional SQL Server Notes for Wonderware 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 Wonderware Historian Client:

• Microsoft Office is an optional prerequisite. If you install Office after installing Wonderware Historian Client, the Historian Client add-ins do not appear in the list of Office add-ins. Run the Wonderware Historian Client installation program and repair the installation to load the Office add-ins.
• When you perform a custom installation of Microsoft Office 2010 or Microsoft Office 2013 (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 2013 (64-bit) version.

Wonderware System Platform Installation

For detailed installation instructions in English, see the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf) or Wonderware 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 Wonderware System Platform 2014 R2 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 Wonderware System Platform 2017

• Installing Wonderware System Platform 2017 on a computer used as a domain controller is not supported. For more information, see http://technet.microsoft.com/library/Cc966456.
• If Recipe Manager Plus will be installed on the same computer as Wonderware System Platform 2017, install Recipe Manager Plus first. Wonderware System Platform 2017 is installed with the latest version of ArchestrA Service Bus (ASB).

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 Wonderware 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 Wonderware System Platform installation. You must specify a user name, password, and domain.

If you choose to use an existing user account, it should meet the following requirements:

• User account with a permanent password that does not expire.
• User account in which the password cannot be changed.
• User account that is a member of the local Administrators group.

After you install a Wonderware System Platform component, you can use the ArchestrA Change Network Account utility to change or re-create the ArchestrA user account. This utility is located in the Common folder after you install InTouch HMI. You must have Administrator privileges on the computer to make changes with 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.

Wonderware System Platform Upgrade and Migration

If you have Wonderware System Platform 2014 R2 SP1, you can upgrade directly to Wonderware System Platform 2017. No other versions are supported for a direct upgrade. If you have a prior version, you must upgrade to Wonderware System Platform 2014 R2 SP1 first.

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 Wonderware System Platform Installation Guide.

The earliest versions of Windows that support Wonderware System Platform 2017 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 for Wonderware System Platform 2017 products.

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

Licensing Information

Once installed, the Schneider Electric License Manager can be found in the \Schneider Electric folder on the Start menu.

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

http://<nodename>/SELicenseManager

<Nodename> is the name of the node where Schneider Electric License Manager is installed.

License Server

The Schneider Electric License Server can be installed separately from the Schneider Electric License Manager.

Antivirus Software Exclusions

Antivirus Software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems.

Please visit https://www.wonderware.com/contact/contact-support/ to get the latest information on Antivirus Software recommendations.

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.

• .NET Issues
• Installation and Uninstallation Issues
• ArchestrA Service Bus and Multi-Galaxy Communication Issues
• InTouch OMI Issues
  • Map App / Mobile Access Issues
• InTouch HMI Issues
• InTouch Access Anywhere Issues
• Licensing Issues
• ArchestrA Alarm Control Issues

.NET Issues

778585

After launching a ViewApp from the Runtime Manager, mouse events stop working (the mouse freezes). This is due to an issue in the .NET Framework. Microsoft has issued a patch for .NET 4.5.2 that fixes this issue. Updating to .NET 4.6.1 or a later version also fixes the issue. Workaround: To apply the Microsoft roll-up patch to .the NET 4.5.2 framework, go to: https://support.microsoft.com/en-us/help/3026376/hotfix-rollup-3026376-offline-installer-for-the-.net-framework-4.5,-4.5.1,-and-4.5.2-on-windows-vista-sp2,-windows-7-sp1,-windows-8,-windows-8.1,-windows-server-2008-sp2,-windows-server-2008-r2-sp1,-windows-server-2012,-and-windows-server-2012-r2 The issue can also be resolved by editing the registry. For details, go to: https://support.microsoft.com/en-us/help/2987845/mouse-may-become-unresponsive-after-you-launch-an-app-v-application

Installation and Uninstallation Issues

784340	After uninstalling Wonderware Application Server and Wonderware InTouch products from a Galaxy Repository node, disk cleanup does not remove parts of the file structure. In addition, you can no longer launch the System Management Console (aaSMC) or the Log Viewer (aaLogviewer) to monitor the GR. The empty folder structure "C:\Program Files (x86)\ArchestrA\Framework\Bin" remains after the uninstall. Workaround: Manually delete the empty file structure.
787270	On certain systems, and in some situations, the file transfer portion of the Wonderware System Platform 2017 installation may require more time when compared to a similar installation of Wonderware System Platform 2014 R2 SP1.
796068	On a Galaxy Repository, uninstalling Wonderware Application Server results in restoring the ArchestrA User credentials to the registry.
799793	On certain systems the Microsoft scheduled maintenance tasks may interfere with the installation process of Wonderware System Platform 2017. The symptoms will include long periods (30+ minutes) of inactivity from the installer, or possibly a failed installation due to time outs.
804308	While installing Wonderware 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.

ArchestrA Service Bus 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: 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\. 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. Edit the Hosts file: Enter the IP address for Node2. On the same line as the IP address, provide a node (computer) name. Enter IP addresses and node (computer) names for each node identified by IP address to be unpaired. 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;
L00123475	When configuring user-configurable ArchestrA Services - ASBGRBrowsing service, ASBMxDataProvider service, and ASBAuthorization service - it is important not to assign the same port number to two instances of a service on the same node. However, it can occur that while creating instances of a service and assigning them to the same node, that the system can erroneously assign a duplicate port number by default. The main symptom of this error is that you do not see a remote galaxy where expected, such as in a list of available galaxies in the Galaxy Browser. As a first step in troubleshooting this problem, do the following: Open the Configure ArchestrA Services utility. Note the port number of the ASBGRBrowsing service instance for the missing galaxy. Compare this to the port numbers of other ASBGRBrowsing service instances assigned to the same node. If you find a service instance with a duplicate port number on the same node: Undeploy the browsing service of the missing galaxy. Change the port number to a unique number for that node. Redeploy the browsing service instance.
L00125223	If you create galaxies on separate nodes, with Wonderware System Platform 2014 (or later) IDE installed on one node and Wonderware System Platform 2012 R2 IDE installed on a second node, then pair them for multi-galaxy communication, you will be able to browse galaxy attributes from the 2014 (or later) IDE to the 2012 R2 IDE, but not from the 2012 R2 IDE to the 2014 (or later) IDE. Installing Wonderware System Platform 2012 R2 Patch 01 on the second node resolves the issue.
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 Wonderware 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 Wonderware 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.
677473	Warnings are logged from the IOMBLSService when different operations are performed in the ViewApp editor and ArchestrA IDE. Operations that cause warnings to be logged include: Configuring security and creating different roles and users after adding multiple custom navigation hierarchies that use a NavBar or NavTree. Changing from an ISA-type Galaxy to a default Galaxy (and from default to ISA). Modifying a screen profile that contains a NavBar or NavTree. Note: The warnings are caused by a failed call (UnregisterFilter). However, there is no significant impact on functionality, and other filters are unaffected.

InTouch OMI Issues

745498	Accessing array-wide properties of an array type object attribute, without the proper use of the empty subscript syntax may fail when the script’s object and the referenced object are on different engines. Workaround: Even though the script editor allows incorrect syntax, always use the proper syntax when accessing array-wide properties. For example: Me.MyArrayAttribute[].Quality will work correctly, whereas Me.MyArrayAttribute.Quality may fail.
763263	Occasionally, a lasso gesture with a mouse to select one or more elements shown on the Graphic Editor canvas does not follow the user's mouse track. Instead, the lasso is offset from the mouse track.
765642	A secured write cannot be used to change an attribute value of a symbol when a ViewApp's security mode is changed during run time. When the user logs in again after the ViewApp's security mode has been changed, secured writes fail when changing from Galaxy to OS User based and OS Group based to OS User based security. Workaround: Secured writes can be restored by redeploying the WinPlatform object after switching security modes.
766162	An Embedded Alarm Client control fails to show alarms when the name of the alarm query begins with the node name of the computer running an InTouch OMI ViewApp.
767601	An InTouch OMI ViewApp containing three or more Embedded Alarm Client controls increases CPU usage on the computer running the ViewApp to approximately 70 percent.
768332	The Query Filters, Requery, and Reset options do not consistently appear in the Embedded Alarm Client control's shortcut menu while a ViewApp is running.
772872	Sending keys for UserInput animation of a symbol produces several behavioral issues: The state of a toggle button symbol does not return to the resting state after sending keys. The button symbol remains in the pressed state after keys are sent. Sending a Tab key for UserInput animation does not move the focus to the next field in a data entry symbol.
772892	Local Galaxy updates to a ViewApp halt for about 15 seconds when its paired Galaxy node is restarted.
773181	Continuous null reference exceptions appear in the SMC log when the DataPlayback service is undeployed while a ViewApp is running in historical Playback mode.
773633	During run time, the initial value of a check box graphic is empty indicating a False value although the default value of the check box was set to True during design time.
774419	In the ViewApp editor, imported packages do not correctly inherit the child navigation item’s Auto Fill mode.
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.
774892	When two layouts have configured each other as pane content, at runtime there is no warning or error in the logger to indicate to the user why the layouts show an empty pane.
775165	In some instances, when an object’s owned graphic is embedded inside another graphic, and the contained name of the object is changed, the Graphic Editor may display “Graphic not Available”, but at runtime the graphic will be displayed correctly.
776083	The SetCustomPropertyValue method from the button action script does not set a value to DateTime Picker.
776529	When a text style Element Style is applied to a symbol and then removed while the ViewApp is running, the symbol's text style does not revert to the default Element Style. Instead, the symbol's text still shows the Element Style that was applied to the symbol.
777023	After changing the attribute overrides of a deployed DI object, with more than 20,000 attributes, the attribute validation will fail, even though attribute syntax for the remaining attributes beyond 20,000 is correct. Workaround: Re-deploy the DI Object to clear up this problem.
777504	The GetCPQuality() scripting method is not supported in InTouch OMI. If used in a ViewApp, it always returns quality = 0 (bad quality).
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.
784206	A Value Display animation with the expression GetItem() or GetItemData() of a Simple ComboBox cannot get a value, when the 'index' parameter for the function is a custom property such as: "GetItem(cp_Index)", cp_Index is valid CP and default value is 0. However, it will work if you use an expression with a constant value such as: "GetItem(1)"
784344	References from a graphic embedded in another graphic may resolve incorrectly when the SetCustomPropertyValue action script is used to change the embedded graphic to a different owning object.
784461	When an action script includes an integer-type custom property for quality that is referenced by a display animation, the display animation shows the default value of the custom property instead of the quality value.
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.
785040	If a Symbol Wizard option hides a custom property, and the hidden custom property is referenced by a visible (non-hidden) custom property, all animations that reference the visible custom property will be shown as initializing, and the visible custom property's quality status does not get .updated.
785220	Changing the TimePeriod for the TrendPen at run time stops the TrenPen from working, and it cannot start restart.
785561	If custom property contains a divide by 0 error, multiple warnings are logged when the application is launched initially, and again whenever the divide by 0 error occurs (instead of logging a single divide by 0 error).
786293	A specific combination of graphic elements, when imported into a Galaxy, will cause a "System Out Of Memory Exception" to be logged in the System Management Console (SMC). However, functionality is not affected. The combination of graphic elements are a curve configured with an arrow anchor, plus some (but not all) height/width combinations.
786745	A warning is logged in the System Management Console (SMC) when you try to save a symbol: If it contains an action script and The action script is configured with a string custom property and The string custom property has the value "null" assigned to it.
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.
787432	The Wonderware Application Manager does not automatically refresh to show the latest edited time. Workaround: To see the latest edited time, press F5, or select View > Refresh.
787438	When you start the Layout editor from the ViewApp editor, and then save and close the Layout editor, the ViewApp editor is moved to the background, behind the IDE.
789583	On French language operating systems, element style animations are not applied when a float data type is used in the Truth Table. Workaround: Use double data type instead of float.
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.
794573	If the System Platform IDE is minimized, and a popup editor (for example, the Layout editor) is active, if the IDE displays a modal window, such as a Save dialog, you cannot select the IDE from the taskbar to move it and the modal window in front of the popup editor. Workaround: Move the other editor out of the way.
795918	An ASBService warning message is logged if Wonderware Application Server is uninstalled while a galaxy is deployed. Workaround: Undeploy any deployed galaxies before uninstalling Application Server.
797816	In some cases, Historian Client will cause a View.exe process to continue to run even after all ViewApp windows are closed. Workaround: Use Task Manager to end the View.exe process.
798264	After upgrading or migrating a multi-node system to Wonderware System Platform 2017, and then deploying a ViewApp, the ViewApp does not connect to one or more nodes. Workaround: From the System Platform IDE, open the Configure ArchestrA Services window (Galaxy > Configure > ArchestrA Services). Select ArchestrA.ASBMxDataProviderService.2.0 and press Ctrl + N to create a new service. Rename the new service with the pattern Default_<GalaxyName>_MxDataProvider. (Insert the name of the galaxy in place of <GalaxyName>.) Assign the new service to the affected node and click Update. Press Ctrl + D to deploy the service.
799693	In some instances, when a button graphic is configured to launch a modal dialog, the button may continue to appear pressed (indented) even after the modal dialog is dismissed. This is only a cosmetic issue. The button will continue to work as expected. Workaround: Move the mouse over the button and it will return to its correct visual state.

Map App / Mobile Access Issues

792363	Dispose and null reference warnings are logged in the System Management Console from the Graphic cache manager component which is being used by MobileAccessTask process.
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 the unfill color property.
797201	If a Line Style animation is used, the line pattern always follows the Line Pattern property and does not change with changes to the animation value.
797226	If the expression type is set to string in truth table for fill color animation, the fill style does not change when the value changes.
797313	If the animation for a radiobutton is disabled, the disabled symbols do not display as disabled.
797324	If you change the Source type in Map Settings to a type that supports Overlay type maps, and set the map type to Overlay, and if you then switch to a Source type that does not support Overlay, the map type remains set to Overlay and cannot be changed. Workaround: Change the Source type to a type that supports Overlay, and reset the type to Base map. Then, change the Source to the desired source.
797328	If an unsupported shape is added to a symbol, and the symbol is configured in the Map App, the message that the shape is not supported is shown twice in the logger after you deploy the ViewApp containing the Map App.

InTouch HMI Issues

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

L00139557	When using a non-default SQL port: In Runtime with multiple EACs configured, database connections may fail with a "Timeout expired" warning (see full text below) appearing in the SMC. Error Message: Open() in DCMConnection failed: 'Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.' Workaround: Perform a manual refresh on the EAC control to re-establish the connection.
L00139560	When using a non-default SQL port: If the primary Historian server is down during a restart of WindowViewer, trend updates are delayed by approximately 25 seconds. This is a one-time delay after WindowViewer restarts.
L00139681	After changing the SQL port of the Historian node and restarting Historian, the ArchestrA Trend Client (RT Trend) does not reconnect to Historian. Workaround: Restart the instance of WindowViewer hosting the Trend client.
L00139786	After switching between default and custom SQL ports for Dual Historian, on a machine where the ArchestrA Trend Client (RT Trend) is used and is configured by scripting, only the real time trend displays, not the Historian trend. Workaround: Delete the servers.xml file typically found at the following location: C:\Users\<user-name>\AppData\Local\Wonderware\ActiveFactory\servers.xml.
L00139789	Connecting to a SQL database in Microsoft Windows 8 or Windows 10 operating systems, when a non-default port is configured for SQL, results in an error message that a connection to the server is not available. Workaround: Disable (shut down) the firewall on Windows 8 and Windows 10 operating system machines.
L00139813	Deploying an InTouchViewApp with a fully qualified file name exceeding 260 characters results in errors logged in the Logger and client controls not copied to the destination location. A fully qualified file name is one that prefixes the file name with the drive letter and directory path. The fully qualified file name must not exceed 260 characters, and the directory name must not exceed 248 characters. These are Windows operating system limitations.
L00139833	Migrating a Galaxy which has an InTouchViewApp with embedded Historian Client controls from Wonderware System Platform versions 2012R2 or 2014R2 to version 2014R2 Service Pack 1, results in errors logged in the Logger. Workaround: Before migrating the InTouch application, delete the previous version Historian Client controls that exist in the Galaxy. Import the newer version controls.
676670	Screen Profiles, which are only for use with , appear in the Galaxy Browser within InTouch WindowMaker.
783666	The ZoomPercent property in Named Script expression box does not get evaluated at runtime when it is used without an element. For example: ZoomPercent >= 200 does not get evaluated at runtime Workaround: Use the ZoomPercent property of an element instead. For example, Button01.ZoomPercent >= 200

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: 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. 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: Add registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\ITAA\ITAAServer 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: Uninstall InTouch Access Anywhere. Restart the computer. Re-install InTouch Access Anywhere.

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 Wonderware System Platform 2017 with Schneider Electric licensing selected, clicking the Schneider Electric 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 Schneider Electric License Manager from the shortcut, or: Open your browser and copy the shortcut link, http://localhost/SELicenseManager, directly into the browser's address bar.

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 Wonderware System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the Wonderware System Platform DVD:

\Wonderware System Platform\CD-ApplicationServer\UserDocs\English

\Wonderware System Platform\CD-Historian-x64\UserDocs\English

\Wonderware System Platform\CD-HistorianClients\HistorianClient\Docs

\Wonderware System Platform\CD-Intouch\UserDocs\English

\Wonderware System Platform\CD-WIS\UserDocs\English

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
• Wonderware InTouch HMI 2017 Documentation
• Wonderware Application Server 2017 Documentation
• Wonderware Historian Server 2017 Documentation
• Wonderware Historian Client 2017 Documentation

Common Components and Utilities User Documentation

• Wonderware System Platform Installation Guide. This guide provides information on installing the Wonderware 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.
• Invensys License Manager Guide. Explains how to install and manage product licenses.
• Wonderware ArchestrA Protocol Guide. Explains background information on the main protocols used between components of Wonderware products.

Wonderware InTouch HMI 2017 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.

Wonderware Application Server 2017 Documentation

• Wonderware Application Server User's Guide. Explains configuring and deploying Wonderware 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).
• Wonderware Application Server Scripting Guide. Reference for the scripting language in Wonderware 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.
• Wonderware 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.

Wonderware Historian Server 2017 Documentation

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

Wonderware Historian Client 2017 Documentation

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

Wonderware InTouch Access Anywhere 2017 Readme

Last revision: 5/8/2017

Related Topics Wonderware System Platform Version 2017 Readme Important Information for Microsoft Windows 2016 How to Find the Latest Product Requirements and Compatibility Information New Features in Wonderware System Platform 2017 Web Help Display and Video Playback System Requirements and Guidelines Wonderware System Platform Installation Wonderware System Platform Upgrade and Migration Licensing Information Antivirus Software Exclusions Known Issues Documentation

About This Readme

This Readme provides information about Wonderware InTouch Access Anywhere 17.0.

Wonderware InTouch Access Anywhere Overview

Wonderware® InTouch Access Anywhere™ provides remote access to Wonderware 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. Wonderware 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 Wonderware 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.

New Features and Enhancements InTouch Access Anywhere

InTouch Access Anywhere 2017 Version 17.0

New Features and Enhancements:

• Security enhancements have been added to this release to address a number of security vulnerabilities in the previous release of InTouch Access Anywhere Secure Gateway, 2014 R2 SP1b. See the InTouch Access Anywhere Secure Gateway Security Settings section of this Readme for details.
• An updated InTouch Access Anywhere user interface including start and configuration pages

  Note: If you have customized the InTouch Access Anywhere start page, you will need to reapply these customizations. It is recommended to document these customizations before upgrading.

• Touch feedback for applications running on touch devices
• Capability to view Wonderware System Platform 2017 ViewApps

  Note: In a mixed product environment in which InTouch applications run on the same computer as Wonderware System Platform 2017 ViewApps, WindowViewer must be started before the ViewApp to be able to view both types of applications with InTouch Access Anywhere.

• Support for Windows Server 2016 operating system
• User documentation updates improve clarity and completeness

For a complete list of resolved issues, see the Resolved Issues section of this Readme.

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.

• The computer that will host the Wonderware InTouch Access Anywhere Server must be running a 64-bit version of Windows Server supported by InTouch 2012 R2 or later.

  Note: InTouch Access Anywhere Server does not support embedded editions of the Windows Operating System.

• 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 session is closed.
• Wonderware 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.

• You must have the InTouch Access Anywhere Secure Gateway installed on a computer running Windows Server 2012 R2 Standard or newer Operating System.
• The InTouch Access Anywhere Server and Secure Gateway must be installed on separate computers.

Important Security Requirement: Securely Deploying InTouch Access Anywhere

Direct access to the InTouch Access Anywhere Secure Gateway over the Internet is not supported. We recommend that you access the Gateway via a VPN tunnel for all remote connections.

Browsers

Wonderware 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 Wonderware InTouch Access Anywhere include the following:

• Microsoft Edge
• Microsoft Internet Explorer 11
• Firefox version 47
• Safari version 8
• Chrome version 51
• Opera version 38

  Important: Please be aware that only the browsers in the above list have been tested in the specified hardware platforms (PCs, tablets and Smart Phones). No testing has been done with HTML5 browsers nor other devices not included in the above list (SmartTVs, eBook Readers, game consoles, etc.).

Functionally Compatible Browsers

Certain versions of the above listed browsers, such as:

• Microsoft Internet Explorer 10
• Firefox versions 6 and higher
• Safari versions 5 and higher
• Chrome versions 12 and higher
• Opera versions 11 and higher

are in theory functionally compatible with InTouch Access Anywhere. While you may be able to use them, specific behaviors are unknown as these browser versions have not been tested.

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.

Defect Number	Description
L00132897	SR 103131461: Open InTouch Access Anywhere sessions would disconnect and return to the server logon page after short periods of time.
L00140226	SR103138586: When running ITAA Server 11.1 SP1, the system could consume large amounts of system resources, specifically RAM, and the server could become unresponsive.
L00141682	Some program files may not be automatically deleted after uninstalling InTouch Access Anywhere Access Anywhere Server and Secure Gateway.
L00143602	[Documentation] The procedure in the InTouch Access Anywhere Secure Gateway Administrator Manual that described how to configure the Secure Gateway to host one or more Access Anywhere Servers was unclear. The procedure did not clearly state that the list of InTouch applications does not populate in the Server log on page automatically when connecting to the Access Anywhere Server through the Secure Gateway.
L00143600	[Documentation] In the InTouch Access Anywhere Server Administrator Manual, an additional step was listed in the pre-installation procedure for Windows Server 2012/Windows Server 2012 R2 that was not required to configure settings.
L00142893	[Documentation] A statement regarding devices not tested with supported browsers was missing from the InTouch Access Anywhere documentation.
L00143599	[Documentation] In the InTouch Access Anywhere Secure Gateway Administrator Manual, the recommended install location for the Authentication Server was not clearly stated and the accompanying diagram did not provide clarification.
L00140602	SR 103142714: Access Anywhere 2014 R2 SP1 introduced cross-site scripting protection, which was causing an error when Access Anywhere is called from an IFrame.

Known Issues and Behaviors

This section describes known issues and platform/browser-specific behaviors in Wonderware 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.

Areas Affected	Issues and Behaviors
All Operating Systems	Firefox: Values entered using the InTouch keyboard appear twice. TFS542896.
	When connecting to the InTouch Access Anywhere Server through the Secure Gateway, the Tool Box displays icons for both PC and Mobile devices at the same time. TFS 658661
	Internet Explorer 10: When connecting to the InTouch Access Anywhere through the Secure Gateway, the web tab icon displays as the default Internet Explorer icon instead of the green InTouch Access Anywhere icon. TFS 665727
	When connecting to the InTouch Access Anywhere Secure Gateway Configuration Portal, the time format does not display correctly. This behavior only applies to Japanese and Simple Chinese operating systems. L00144578
	When an InTouch application is published in a localized character path, InTouch Access Anywhere will fail to launch the application. This behavior only applies to Japanese and Simple Chinese operating systems. L00144579
Internet Explorer 10, Safari 8	Internet Explorer 10, Safari 8: Playsound() works with Chrome, Opera, and Firefox, but not with Internet Explorer 10 or Safari 8. L00133687.
Internet Explorer on Windows RT Operating System	Internet Explorer: When accessing the InTouch Access Anywhere server through an RDP desktop session, user input animations using the Windows operating system keyboard do not start the keyboard. The recommended workaround is to use the device's built-in keyboard. TFS542851.
	Internet Explorer 10 on WinRT in a touch environment: A mouse cursor may disappear after using the Surface keyboard to enter data. As a workaround, use touch gestures in place of mouse inputs. TFS218943.
Windows 2008 R2 64 bit	InTouch Access Anywhere Secure Gateway files cannot be repaired by the install program.L00141680
	The "InTouch Access Anywhere Server Configuration" form may extend beyond the bottom the screen and cannot be resized to fit the resolution 1240x768. L00141668
Windows Server 2016	When WindowViewer is minimized, the minimized window will disappear and cannot be relaunched. L00144577

Wonderware InTouch Access Anywhere Documentation

Wonderware InTouch Access Anywhere product documentation is provided as a set of Portable Document Files (PDF):

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.

InTouch Access Anywhere Secure Gateway Security Settings

As part of the security improvements delivered in this release, InTouch Access Anywhere Secure Gateway is now configured to be secured by default and requires further configuration after the product is installed. You can also configure the security settings back to the same levels as in previous releases (not recommended).

The security settings are described in InTouch Access Anywhere Secure Gateway Administrator Manual (ITAA_Gateway_AdminManual.pdf), in the following sections:

• Whitelist Security on Page 26
• Configure Session Cookie Timeout on page 28
• Configuring the Origin Header Parameter for Whitelist Security on page 28
• Manually Configure a Trusted Certificate on page 37
• Configure the Secured Port and SSL Certificate on page 36

TargetHostWhitelistAllowedIPv4Addresses and certificate trust must be configured before using the InTouch Access Anywhere Secure Gateway. If you do not configure TargetHostWhitelistAllowedIPv4Addresses with the white listed systems, connections to the InTouch Access Anywhere Server through the InTouch Access Anywhere Secure Gateway will fail. You will get the following error message:

"Gateway: Target Host access is not allowed for address <IP Address>."

If you do not configure the certificate trust, you will be prompted with a certificate error if the Access Anywhere Server's certificate is not recognized on the Gateway node.