Wonderware System Platform 2017 Update 2 Readme PDF

11/13/2018 Wonderware System Platform 2017 Update 2 Readme
Wonderware System Platform 2017 Update 2 Readme

Last revision: 5/10/2018
This document contains important information about Wonderware System Platform 2017 Update 2. This update of Wonderware System Platform 2017 includes enhancements to the
software development kit (SDK), and additional features and enhancements for the component products of Wonderware System Platform.
Supported Wonderware System Platform Versions for Product Upgrade

You can upgrade directly to Wonderware System Platform 2017 Update 2 from the following versions:
Wonderware System Platform 2017 Update 1
Wonderware System Platform 2017
Wonderware System Platform 2014 R2 SP1 with Patch 01 and/or Patch 02
Wonderware System Platform 2014 R2 SP1
Note that all existing products must be upgraded to the same version.
Supported Wonderware System Platform Versions for Migration

You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.,) to Wonderware System Platform Update 2, as long as the content was created in
one of the following product versions:
System Platform: Version 4.5 or newer
Application Server: Version 2.5 or newer
InTouch HMI: Version 7.11 P07 or newer
Historian Server: Version 9.0 P02 or newer
FS Gateway: Version 1.5 or newer
Server-based Licensing
Wonderware System Platform 2017 Update 2 continues to utilize the server-based licensing subsystem introduced in Wonderware System Platform 2017. This new licensing
subsystem provides centralized license management, and replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.
If you are upgrading from Windows Server 2014 R2 SP1 (with or without patches), you must first install and configure a license server node, and activate the licenses to ensure
continuous plant operation. The license server is typically installed on the Galaxy Repository node, but you can use a dedicated license server. See the "License Installation and
Activation" section of the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf), located at the root of the DVD.
InTouch OMI
Wonderware System Platform 2017 introduced 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. Key features added for Update 1 included a Software Development Kit (SDK) to allow
programmatic additions to InTouch OMI. New features, including the ShowContent API, have been added to the SDK for Update 2. Help for the SDK can be accessed from the Start
Menu, under Wonderware Documentation.
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 Update 2 (v17.2)
Wonderware InTouch HMI 2017 Update 2 (v17.2)
Wonderware Historian Server 2017 Update 2 (v17.2)
Wonderware Historian Client 2017 Update 2 (v17.2)
The Wonderware InTouch Access Anywhere Version 17.2 Readme file is included at the end of this Readme.
In This Document
Important Information for Microsoft Windows 2016 and InTouch HMI
How to Find the Latest Product Requirements and Compatibility Information
New Features in Wonderware System Platform 2017 Update 2
Web Help Display and Video Playback
System Requirements and Guidelines
Wonderware System Platform Installation
Wonderware System Platform Upgrade and Migration
Licensing Information
Antivirus Software
Resolved Issues
Known Issues
Documentation
Wonderware InTouch Access Anywhere Version 17.2 Readme
Important Information for Microsoft Windows 2016 and InTouch HMI

https://www.logic-control.com/datasheets/1/System_Platform_2017_Update2_ReadMe.html 1/19
When InTouch HMI 2017 Update 2 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 using 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 Update 2.
Important: You can install the Microsoft update before or after Wonderware System Platform. However, we recommend installing the Microsoft update before you install
Wonderware 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. After you log in, you can filter search results by product name and the release/version.
The GCS Product Hub contains Readme files, videos, and product downloads from previous product releases.
The GCS Technology Matrix is a searchable database that contains the latest product information. Enter the product name in the search bar, then select the current release to
view:
Product Information: version name, number, release date, etc.
Product Notes: key release information, new features, and updates
OS Compatibility: list of compatible Windows and Windows Server versions
Database Compatibility: list of compatible SQL Server and other database product versions
Virtualization Compatibility: list of compatible virtualization software products and versions
Product Coexistence: list of products that can be installed on the same computer
Product Compatibility and Interoperability: list of products that can operate together and communicate with each other through a common message protocol
New Features in Wonderware System Platform 2017 Update 2

System Platform 2017 Update 2 adds a number of new features and product enhancements, and extends support for the latest versions of Microsoft products including the .NET
Framework 4.7.1. Among the enhancements provided by this latest .NET version are about 200 new APIs and run-time performance improvements. See the GCS Technology Matrix for
more information about supported Microsoft products.
New features and product enhancements include:
New Features in InTouch OMI Update 2

Runtime Preview
InTouch OMI now provides a preview session, which enables you to quickly assess changes in a running ViewApp without deploying the Galaxy. A preview launches immediately and
runs in a separate window to show the current content being edited. A preview is similar to the fast switch feature in InTouch WindowMaker. A preview session can be kept open while
editing a ViewApp. When you save changes made to a ViewApp, the preview refreshes to show the updated content.
User-Friendly Names for Assets and Navigation

A running ViewApp typically shows objects as navigation items that appear by their assigned Galaxy names in the navigation model. Galaxy names may not be intuitive or easily
understood by operators. Objects can be assigned more understandable friendly names.
Friendly names are assigned as values of object attributes from the Model view of the ArchestrA IDE. The friendly name, also referred to as an alias, appears in the navigation model of a
ViewApp in the ViewApp or Layout editors.
Rearrange Navigation Items

You can drag and drop navigation items to different locations within a navigation hierarchy. This lets you to create a more accurate model of your plant or other physical environment by
rearranging the order and relationship of subordinate and sibling navigation nodes, and/or provide more natural navigation for your InTouch OMI ViewApps.
ViewApp Namespaces
ViewApp Namespaces allow you to add custom attributes that can be shared among all InTouch OMI ViewApp instances in a Galaxy. Each ViewApp Namespace can contain up to
10,000 custom attributes, and you can add as many namespaces as needed to support data sharing among all running InTouch OMI ViewApps. This includes running multiple instances
of a single ViewApp. You can configure attribute values for each ViewApp individually, even though the attributes are shared by all the InTouch OMI ViewApps in the Galaxy.
ShowContent() Scripting Function and API Call

The ShowContent() scripting function and API call let you place symbols or layouts into specific panes within an InTouch OMI layout, either through scripting or programmatically.
ShowContent() is similar to the existing ShowGraphic() function, but extends its functionality for InTouch OMI ViewApps. With the addition of ShowContent, the run-time behavior of the
ShowGraphic function has been modified to work identically in InTouch OMI and InTouch HMI ViewApps. In previous InTouch OMI releases, ShowGraphic loaded modeless popup
windows into a pane. Now, ShowGraphic will correctly load a graphic configured to load in a modeless window in InTouch OMI ViewApps. See Issue 988079 under InTouch OMI Issues
for additional information.
Quality and Status Icons in the Navigation Tree

A quality status icon for the Alarm Adorner attribute is displayed at the right of, and aligned with, alarm aggregation counts for an area object in the Navigation Tree. The quality status
icon for the Alarm Adorner uses icons that are globally configured for the status element. The status icon for the Alarm Adorner is shown below the area object, even if the Alarm Adorner
is not visible. The icon indicates if the Alarm Adorner attribute has a configuration error, or has uncertain or bad quality.
New Features in InTouch HMI 2017 Update 2

InTouch HMI 2017 Update 2 provides support for the latest versions of Microsoft products and includes several new features. Refer to the GCS Technology Matrix for the list of supported
Microsoft products. The following section summarizes the major features introduced in InTouch HMI 2017 Update 2.
Alarm DB Utilities and Controls Support Windows Authentication

The following InTouch Alarm DB utilities now support Windows Authentication in addition to SQL Server authentication.
Alarm DB Logger Manager
Alarm DB Purge-Archive
Alarm DB Restore
The following InTouch Alarm Controls now support Windows Authentication in addition to SQL Server authentication.
Alarm DB View Control
Alarm Pareto Control
InTouch Web Client Enhancements

There are major improvements in the InTouch Web Client from the InTouch HMI 2017 Update 1 release.
Enhanced Workflow for InTouch Web Client testing
WindowMaker has now Fast Switch capabilities to go from WindowMaker directly to the InTouch Web Client speeding up development and testing.
Major improvements in graphics visualization, including support for the following:
Transparency color for FillColor
Rotation on Group/Embedded Symbol
Blink Animation and Style blinking
Gradient Color for FillColor and LineColor
Three color gradients
Vertical and Horizontal Percentage Fill and UnFill Animation
Setting Max, Min, Max Percentage and Min Percentage with reference
Pattern Brush and Outline for Element Style
Gradient Color for Line, Outline and ElementStyle
Chord Elements
Writing data to Custom Property using the Slider animation
Configuration of Quality and Status Indicators on elements
Status Control
Internalization Support
Improvements to the InTouch Web Client interface
Support for mobile devices
Support for major browsers
Support for pan and zoom gestures
Performance improvements
InTouch Script Functions now available in the ArchestrA Graphic Editor script editor
A selected list of InTouch script functions are now part of the ArchestrA Graphic Editor script editor and can be used within the System Platform IDE.
Non-Administrative users can now open Managed Applications

Users without administrative privileges can now launch WindowMaker via ArchestrA IDE for Managed applications.
WindowViewer OS Shutdown Event Handling

WindowViewer is now aware of operating system shutdown events. This allows WindowViewer to promptly release an activated license back to a License Server when detecting the
operating system is ending a Remote Desktop Session.
NAD Notification Reminder

A dialog box reminds a WindowMaker user to notify clients when attempting to close WindowMaker if changes have not been notified.
Frame Windows supports ShowGraphic script with ability to set Custom Property
Frame windows can now include ShowGraphic scripts that can set the Custom Property of an ArchestrA object.
New Features in Wonderware Historian 2017 Update 2

The Wonderware Historian 2017 Update 2 (version 17.2.000) includes these features:
Improved handling of future data
New and improved Wonderware Historian InSight features, including:
Ability to add comments (annotations) to content
iPad support
New and updated language support
New Features in Wonderware Historian Client 2017 Update 2

The Wonderware Historian Client 2017 Update 2 (version 17.2.000) includes:
New Alarm and Event overlay for Trend
When you use Wonderware Historian Client Trend to view tags from Wonderware Application Server, you'll see any associated alarms and events as part of your trend. When you
hover over an event icon or alarm highlight, you'll see its details.
Web Help Display and Video Playback
Web Help - Browser-based User Assistance
Web help components have been delivered in this release. Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and
searchable user assistance including standard web browser navigation and tutorial videos.
Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. To open the help, use
one of the following methods (depending on the editor/UI you are using):
Press F1 from the ViewApp editor, Screen Profile editor, or Layout editor.
From the System Platform IDE, select an object or symbol name and:
press Ctrl+F1, or
right-click, then select Help from the short-cut menu.
Open web help from its installed location:
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\NGX\index.htm
Browser Requirements and Recommendations

Internet Explorer is recommended. You can also view web help Firefox. If you use Firefox, you may need to install and use an IE rendering extension (for example, IE Tab) to ensure that
video content is shown.
Microsoft Edge will not load help content, unless you use the "Open with Internet Explorer" option in the Edge browser.
Chrome and Chromium-based browsers, such as Vivaldi, will not load help content unless you install and use an IE-rendering extension (for example, IE Tab).
Browser Permissions for Displaying Web Help

Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog
requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal
navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.
You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the
Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your
specific browser.
Playback of Tutorial Videos

The web help may contain a number of brief tutorial videos. To play these videos, you must have Microsoft Media Player installed on your local machine. In Windows Server operating
systems, you must enable the "Desktop Experience" feature using Server Manager.
Internet Explorer (or IE-rendering in other browsers) may be required for viewing video content. If using a browser other than Internet Explorer without IE rendering enabled, videos may
not be visible.
InTouch OMI SDK Web Help

When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The
browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.
To open the SDK help from its installed location, go to:
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\OMISDKHelp\index.html
To open the SDK help from the start menu, go to:
Start > Wonderware Documentation > InTouch OMI SDK Help
InTouch OMI SDK Web Help

When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The
browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.
To open the SDK help from its installed location, go to:
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\OMISDKHelp\index.html
To open the SDK help from the start menu, go to:
Start > Wonderware Documentation > InTouch OMI SDK Help
System Requirements and Guidelines

Hardware Requirements Notes
Operating System, Firewall, .NET Operating System and Software Requirements for Operating System Notes: Common for Wonderware .NET Framework Requirements
Framework, and Virtualization Notes Wonderware System Platform 2017 Update 2 Products and Compatibility
Windows Operating System Notes Operating System Notes: Wonderware InTouch HMI Considerations for SQL Server
2017 Update 2
.Net Notes Considerations for SQL Server
Operating System Notes: Wonderware Application Express
SQL Server Notes
Server
Virtual Environment Notes
Operating System Notes: Wonderware Historian
Firewall Notes Server
Operating System Notes: Wonderware Historian
Client
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 Update 2.
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 Update 2 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
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
Operating System and Software Requirements for Wonderware System Platform 2017 Update 2
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.
Minimum Required Operating System Version
Product
Client OS (x86 and x64) Server OS (x64 only)
Wonderware Application Server

Windows 8.1 Professional Windows Server 2012
Wonderware InTouch
Windows 10 Version 1607 (Embedded or Data Center)
Wonderware Historian
Wonderware System Platform 2017 Update 2 web clients

The following web clients are included with Wonderware System Platform 2017 Update 2:
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,000 I/O per system):
Any operating system, database, and virtualization software supported by Application Server.
Exceptions: None.
Medium installation (25,000 to 50,000 I/O per system):
Any operating system supported by Application Server.
Exceptions: 32-bit versions of Windows 8.1 are not supported (64-bit versions are supported).
Any database software supported by Application Server.
Exceptions: SQL Express-SSMSE versions are not supported.
Any virtualization software supported by Application Server.
Exceptions: None
Large installation (50,000 to 400,000 I/O per system):
Only Windows Server operating systems (for example, Windows Server 2016) supported by Application Server.
Client operating systems, such as Windows 8.1 and Windows 10, are not supported for large installations.
Any standard or enterprise version of database software supported by Application Server.
Exceptions: SQL Server Express-SSMSE versions are not supported.
Any virtualization software supported by Application Server
Exceptions: None
Windows Operating System Notes

Newer operating system Service Packs (SPs) than those listed do not block the installation of 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.

The following virtualization software and cloud-based virtual environments are supported for Wonderware System Platform 2017 Update 2:
Hyper-V 5 and newer (version is based on the operating system utilized)
Both Gen 1 and Gen 2 VMs are supported
Windows 10 and Windows Server 2016 support Versions 7 and 8
VMWare VSphere 6.0, including HA/DR
VMWare Clients, including Horizon - Application Virtualization
Cloud Virtualization - Azure
VMWare Workstation, Version 11 and higher
Firewall Notes
In order to establish communication with other components and services on the network, Wonderware System Platform (WSP) and ArchestrA Service Bus (ASB) services require certain
network ports to be opened in the Windows Firewall. Typically, these ports are automatically opened for the Windows Firewall during installation. However, if the Windows Firewall
service is disabled or not running at the time of installation, or if an alternative firewall is in use, you will need to manually open the appropriate network ports in the firewall. For more
information about port configuration, see "Configuring ArchestrA Service TCP Ports" in the Wonderware Application Server User Guide (filename: IDE.pdf).
Operating System Notes: Common for Wonderware Products
ActiveX Controls Behavior on Supported Windows Operating Systems

Due to the Data Execution Prevention (DEP) feature in Windows operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host, or will behave unpredictably
in InTouch, either in WindowMaker or WindowViewer.
The ActiveX controls and error message, along with solutions to resolve the behavior, are described in detail in TechNote 522, "Some ActiveX Controls NOT Supported in InTouch 2012
R2 (Version 10.6)". You can download this TechNote from the Schneider Electric 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 Update 2
Wonderware InTouch HMI 2017 Update 2 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.
Wonderware InTouch HMI 2017 Update 2 does not support the following legacy script functions on 64-bit systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and
SendKeys().
If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator.
The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator to function properly.
The onscreen keyboard options were changed for Windows 7 and Windows Server 2008 R2. Although these operating systems are supported for Wonderware System Platform
2017 Update 2, these changes apply to the currently-supported operating systems.
Hovering to select from the Windows keyboard does not work in currently-supported operating systems.
Wonderware InTouch HMI 2017 Update 2 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 Update 2 Support for Windows User Account Control
Wonderware System Platform 2017 Update 2 with InTouch HMI 2017 Update 2 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 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
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 Update 2 installs .NET 4.7.1 if the currently installed version of .NET is lower. If .NET 4.7.1 or later is installed, no change is made to
the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2017 Update 2, 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 Update 2, 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.7.1. We also recommend you test the upgrade in a staging system prior to upgrading your production system.
Wonderware System Platform 2017 Update 2 leverages the Microsoft .NET Framework 4.7.1. 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 Update 2 will use .NET 4.7.1 or later.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.7.1 or higher. Although .NET Framework 4.7.1 is highly
compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts. These changes may also affect .NET controls developed with .NET
3.5.
In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream
decoder in .Net 4.5 and later. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:
What's New in the .NET Framework: http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx
What's obsolete in the .NET Framework Class Library: https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx
Migration Guide to the .NET Framework 4.7, 4.6 and 4.5: https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29
.NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29
Considerations for SQL Server

SQL Server is required for Application Server, InTouch, and Historian Server. We recommend that you install and configure the supported SQL Server version before you begin the
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
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 SP2 is automatically installed for when you install for InTouch, Application Server, or the Historian, if, at time of installation, no other SQL Server elements
are installed on the computer.
If you plan to use SQL Server Express with Wonderware Information Server and 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 SP2.
Installing Wonderware InTouch HMI first, which silently installs and configures SQL Server 2014 Express with Tools SP2, and then installing Wonderware Information Server
will not allow Wonderware Information Server to work. In this case, during the Wonderware Information Server configuration, an error message will appear in the
Configuration Utility stating: "SQL Server client components not found." To work around this issue, configure Wonderware Information Server to use an instance of SQL
Server Express (or a non-Express edition) on a remote node.
The computing capacity of SQL Server Express 2014 with Tools SP2 is limited to the lesser of one CPU socket or four processor cores.
For InTouch HMI-only installations, the Wonderware System Platform installer will automatically install SQL Server Express 2014 with Tools SP2 if these conditions are met:
No version of SQL Server is installed on the computer at the time of installation.
You select only the InTouch Development and Runtime 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 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 Update 2

Installing Wonderware System Platform 2017 Update 2 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 Update 2, install Recipe Manager Plus first. Wonderware System Platform
2017 Update 2 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

You can upgrade directly to Wonderware System Platform 2017 Update 2 from the following versions of Wonderware System Platform:
Wonderware System Platform 2017 Update1
Wonderware System Platform 2017
Wonderware System Platform 2014 R2 SP1 P02
Wonderware System Platform 2014 R2 SP1 P01
Wonderware System Platform 2014 R2 SP1
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 Update 2 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 Update 2 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.
Running both InTouch HMI and InTouch OMI in a Session on an RDS Server
In Wonderware System Platform 2017 Update 2, running both InTouch HMI and InTouch OMI in a session on an RDS Server will attempt to acquire two (2) Supervisory Client Server
(unlimited) licenses instead of one (1).
If you have purchased a Supervisory Client Server license (unlimited RDP sessions on a single server) and then run both InTouch HMI and InTouch OMI simultaneously, there can be
issues acquiring the server license due to differences in how the license is handled between the two. The order of startup will impact the results.
This behavior is seen in only a limited number of instances, only when you have purchased a Subscription license. If you do see this behavior, change the order of InTouch HMI and
InTouch OMI startup.
If this behavior continues, contact Schneider Electric Software Global Customer Support (GCS), describe the behavior, and request a temporary license, typically valid for 60-days.
InTouch OMI and InTouch HMI ViewApp license reservation Device Name for Client Devices,
RDP Servers, and Users
License Reservation
Reserving a license for a specific device ensures a license will be available for that specific device whenever it is needed, regardless of the number of devices connected to the system.
Keep in mind, each license can only be reserved to a single device, so if the device names are unknown ahead of time, it's better to not use reservations and instead allow the licenses to
be acquired on a first-come, first-serve basis.
User-based License Reservation

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

When reserving a Supervisory Client license for a specific device, the Device Name needs to be the name of the computer running the InTouch HMI/OMI ViewApp. In the case where the
ViewApp is running inside of a Remote Desktop Session, on an RDS (aka: Terminal Server), then the Device Name needs to follow this naming pattern:
<RDSHostName>-<RDPClientName>-<index>
where RDSHostName is the name of the Remote Desktop Server (aka: RDS or Terminal Server), and RDPClientName is the name of the PC running the RDP client software, and
"index" is 1, unless there will be multiple RDP sessions from a single client machine, in which case the index should be incremented (starting at 1) for each reservation for that specific
RDP client, up to the total number of RDP sessions from that specific RDP client.
Reservation Examples
Situation: A computer with a hostname of "ControlRoomA" runs InTouch OMI
Device Name: "ControlRoomA"
Situation: A computer with a hostname of "ControlRoomB" running a single Remote Desktop Client (RDP), connecting to the Remote Desktop Server (aka: Terminal Server) with a
hostname of "PrimaryRDS"
Device Name: "PrimaryRDS-ControlRoomB-1"
Situation: Two computers with hostnames "SupervisorPC1" and "LineMgrA", respectively, each running a single Remote Desktop Client (RDP) connecting to the Remote Desktop
Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Names:
License Reservation 1: "PrimaryRDS-SupervisorPC1-1"
License Reservation 2: "PrimaryRDS-LineMgrA-1"
Situation: A computer with a hostname of "ExecutiveDesktop" running four (4) Remote Desktop Clients (RDPs), connecting to the Remote Desktop Server (aka: Terminal Server) with a
hostname of "PrimaryRDS"
Device Names:
License Reservation 1: "PrimaryRDS-ExecutiveDesktop-1"
Antivirus Software
Antivirus Software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems. TechNote TN2865, available from the Schneider Electric
Software Global Customer Support (GCS) web site, lists important information about antivirus software. Enter your GCS credentials to access the Tech Note.
https://softwaresupportsp.schneider-electric.com/#/okmimarticle/docid/tn2865
Resolved Issues
This section documents important resolved issues broadly categorized as Wonderware System Platform-level issues. This list is not comprehensive. Additional resolved issues are
documented in the product-specific Readme files.
778585 Mouse events stopped working after launching a ViewApp. This was caused by an issue in the .NET Framework that was patched in .NET 4.5.2.
Wonderware System Platform uses .NET 4.7.1 and thus this issue no longer applies.
787270 Installation of Wonderware System Platform was slow compared to previous versions.
797324 The Source type in the Map settings was locked if the type had been set to Overlay and then a Source type was selected that did not support
Overlay.
932024 Arrays in InTouch OMI ViewApps, when viewed in non-English locales could be hard to read because a comma was used as the list separator as
well as the decimal separator.
932052 After upgrading one of the nodes in a multi-galaxy environment to Wonderware System Platform 2017 Update 1, some ASB services did not
deploy immediately.
933098 After objects were imported, the imported objects did not always show the complete set of thumbnails for linked symbols. A message, "Graphic
Not Available" was sometimes displayed in place of the thumbnail.
1001979 In rare circumstances, the Configurator ServerConfig.xml file became corrupted and license configuration was blocked.
L00146989, SR 103148987, SR 103149093: License Server IDs changed even when the server was running, and even though the server had not been
L00147842 renamed. This issue has been resolved in the Schneider Electric License Manager, and detailed documentation of server renaming and resetting
license IDs has been added to the help.
L00148338 SR 63910122: Switching Windows in InTouch WindowViewer with active Dynamic Resolution Conversion (DRC) was slower when compared with
the native resolution.
L00148347 SR 103149542: After upgrading from WSP 2014 to WSP 2017 Update 1, the text on the ArchestrA Editor Combo Box control became distorted
when viewed in WindowViewer.
L00148422 SR 63210486: For InTouch 2017 Update 1, the AlarmComment language switching did not work in the ArchestrA AlarmClient.
L00148598 SR 63210414: For InTouch 2017 Update 1, the ArchestrA TrendClient occassionally did not show the historical value the first time.
L00148693 SR 24517300: The ShowTopLeftAt(x,y) function did not move a window up beyond (0,0) of the window to cover the menu bar.
Known Issues
The following important known issues are listed by their assigned CR or reference number in ascending order. Additional known issues are documented in the product-specific Readme
files.
Installation and Uninstallation Issues
ArchestrA Service Bus and Multi-Galaxy Communication Issues
InTouch OMI Issues
Map App/Mobile Access Issues
Application Server Issues
InTouch HMI Issues
InTouch Access Anywhere Issues
Historian Issues
Licensing Issues
ArchestrA Alarm Control Issues
Installation and Uninstallation Issues

796068 On a Galaxy Repository, uninstalling Wonderware Application Server results in restoring the ArchestrA User credentials to the registry.
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.
931629 If a Wonderware System Platform component is removed through the Control Panel ("Install/Uninstall Programs" applet), rather than by running
the Wonderware System Platform installation program (Setup.exe), errors messages will be logged, exception messages such as "FileNotFound"
will be displayed, and Application Server deployment will no longer be successful.
Workaround: Use the "Modify" workflow, as described in the Wonderware System Platform Installation Guide.
1. Insert the Wonderware System Platform installation DVD and run Setup.exe.
2. Select the "Modify" option.
3. Select or clear the components you want to add or remove and click Next.
4. When the Verify Change dialog appears, click Modify.
5. Click Finish when the changes are complete.
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:
1. Navigate to the Hosts file on Node1. In Windows 7 and Windows 2008 R2 operating systems, the Hosts file typically can be found at
C:\Windows\System32\Drivers\Etc\.
2. Open the Hosts file in Notepad. In Windows 7 and Windows 2008 R2 systems, you should right click the Notepad executable, and click
Run as Administrator, then open the Hosts file from inside Notepad.
Alternatively, you can click Start, then click Run, then enter the following command in the text box:
notepad c:\Windows\System32\Drivers\Etc\Hosts.
3. Edit the Hosts file:
a. Enter the IP address for Node2.
b. On the same line as the IP address, provide a node (computer) name.
c. Enter IP addresses and node (computer) names for each node identified by IP address to be unpaired.
4. Save and close the Hosts file. You should now be able to unpair the galaxies.
L00123474 Writing from InTouch to a remote galaxy using indirect tags can fail for some of the remote references. Object Viewers on two different nodes
may show different values for the same reference. You can avoid this issue by deactivating Advanced Communication Management in the IDE.
Additionally, if you use the same indirect tag with scripting more than one time, you can modify your scripts to set the indirect tag's name property
to an empty string after the loop completes. For example, in the following script snippet, you would add the line highlighted with bold text:
IF bRunScript THEN
FOR tagval = 1 TO 3
indirect.Name = "Testtag" + Text(tagval, "0");
IF indirect.Value > 4 THEN

indirect.Value = 0;
ELSE
indirect.Value = indirect.Value + 1;
indirect.Value = indirect.Value + 1;
ENDIF;
NEXT;
indirect.Name = "";
ENDIF;
L00133534 Undeploying a galaxy with Object Viewer active will cause Object Viewer to shut down with an informational message that requires
acknowledgement (click OK) to complete the shutdown. In a multi-galaxy configuration, with Object Viewer open, undeploying a paired Galaxy,
then redeploying the galaxy without properly shutting down Object Viewer, can cause ASB services to fail to reconnect to the redeployed galaxy.
To avoid this condition, click OK to shut down Object Viewer before redeploying the galaxy.
L00139918 Uninstalling Wonderware InBatch versions 10.2 or 11.0 installed on a 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.
InTouch OMI Issues

1010622 When the child of a custom navigation node includes a reference to an asset and the asset is undeployed, an "uncertain" Quality and Status
indicator is displayed for the custom navigation node. This behavior is different than asset node behavior, which does not show Quality and
Status alarms in the parent node when the asset referenced by a child node is undeployed. There is no impact to the running ViewApp and no
workaround. This is simply a difference in behavior between the two types of nodes.
1010182 In an InTouch OMI ViewApp, touch gestures to do not function the same way on slide-in panes as in the main window. The touch gestures
affected include pan & zoom, multi-touch gestures, and hierarchy navigation.
Workaround: If possible, use a pointing device, such as a mouse, instead of using touch gestures on InTouch OMI ViewApps that contain slide-
in panes.
1004542 Error messages are displayed in the Logger when creating a Galaxy if a fully qualified domain name is used when adding the ArchestrA Network
Account user name. A fully qualified name is one that includes a separator, for example, Wonderware.com.
Workaround: Do not use fully qualified domain names when adding the ArchestrA Network Account. For example, use Wonderware instead of
Wonderware.com.
1003341 In some cases, especially when font size for the navigation breadcrumb is reduced, the Alarm Adorner will overlap the down arrow symbol. This
is a visual issue only and does not affect functionality. The down arrow will continue to function normally.
999299 When an InTouch OMI ViewApp is deployed or Preview has been selected, but the ViewApp window is closed before all panes have been
populated with their contents, multiple warnings are logged. These warning messages are related to task cancellation, ArgumentOutOfRange,
and failure to dispose.
Workaround: The logger messages can be ignored. To avoid this situation, wait until all content has loaded before closing the ViewApp window.
988079 If you upgrade or migrate from version 2017 or 2017 Update 1 to 2017 Update 2, and have an InTouch OMI ViewApp that uses the
ShowGraphic scripting method,modeless windows will behave differently at run time in this version of InTouch OMI.
Old behavior: a modeless window called by ShowGraphic was displayed in an InTouch OMI pane.
New behavior: a modeless window called by ShowGraphic is now be displayed in a modeless popup window. A new scripting method,
ShowContent, has been added. Use ShowContent to load a graphic or layout into a pane. Use ShowGraphic to load a graphic into a
modeless or modal popup window. Note that the modal windows called by ShowGraphic will continue to behave the same way as in
previous releases (a modal popup window is displayed).
Missing After upgrading or migrating an InTouch OMI ViewApp from 2017 to 2017 Update 1, a warning message states that the NavTree entity could not
NavTree be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.”
Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading to Wonderware System Platform 2017 Update 1:
1. Open the ViewApp or Layout that shows the warning.
2. In the ViewApp or Layout editor, look in the Actions list for all references to “NavTree.” An icon showing “Content not available” will be
displayed for these references.
3. To see the entire action list for a ViewApp, toggle the Actions for Primary switch to show Actions for Home (does not apply to the
Layout editor).
4. Replace the NavTree object with the new NavTreeControl.
a. Search for NavTreeControl under the Toolbox tab.
b. Drag the NavTreeControl onto the pane to replace the NavTree.
5. Confirm that you want to replace the content, then save the ViewApp or Layout and close the editor.
6. Verify Layouts and ViewApps no longer show any warnings related to the NavTree.
7. Deploy the ViewApp.
Workaround 2: To replace references to NavTree when importing packages from Wonderware System Platform 2017:
1. Launch the IDE and open the “Find” dialog.
2. Search for “NavTree” using the default search settings.
If the package file contains the obsolete NavTree object, it will be listed in the search results.
3. Double-click the NavTree search result, which will select the NavTree object in the Graphic Toolbox.
4. Delete the NavTree object from the Graphic Toolbox.
5. Use Workaround 1 to replace the NavTree object with the new NavTreeControl object.
774717 When an InTouch OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under
certain circumstances the application may stop responding:
InSightApp
MapApp
WWWebAppControls
Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running
the ViewApp on 1080p monitors, do not attempt to span multiple monitors.
777504 The GetCPQuality() scripting method is not supported in InTouch OMI. If used in a ViewApp, it always returns quality = 0 (bad quality).
781006 If an invalid custom property is added to a symbol, no warning is logged in the System Management Console, even though no value is displayed
for the custom property.
781620 The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are
not rendered correctly.
784470 Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp.
784474 A tooltip may partially cover the element with which it is associated in the deployed ViewApp.
787192 When OSGroup security mode is used, the VerifiedWrite dialog is not displayed when you modify the value of a VerfiedWrite attribute from a
combobox, if you first attempted to perform the VerifiedWrite without having the correct security credentials.
789857 When an element style animation is configured with both a fill color and a blink color, the blink animation and color remain when an element style
override is applied that specifies only a fill color and has the blink check box deselected.
Workaround: Set the initial state without blink, then apply overrides as needed with blink enabled.
789958 On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing
between items, which can make it harder to read object names.
794383 When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is
shown at run time (private values should not be shown). Similar situations occur when:
An override values for a custom property that is later made private. The override is also shown at run time.
An override is applied to a custom property, and later the custom property is locked (can no longer be overridden). When the ViewApp is
redeployed, the override value is still shown.
Workaround: Manually validate the outermost symbol and then deploy the ViewApp.
Map App / Mobile Access Issues

797198 If the unfill color is set to a gradient in an Unfill animation with an animation fill style, and the fill style animation is changed, it changes the unfill
color property.
797226 If the expression type is set to string in the truth table for fill color animation, the fill style does not change when the value changes.
Application Server Issues

933752 Starting the IDE can take up to a minute if the node on which it is running is not connected to the internet.
Root Cause: To enhance security and reliability, Wonderware System Platform will validate certificates. Windows then performs a check to see if
the certificate has been revoked. Without an internet connection, Windows waits until the timeout for this check has been reached before allowing
the IDE to start.
Workaround 1 (preferred): This method changes the default timeout for the certificate check.
1. Open the Local Security Policy settings (enter "Local Security Policy" in the Start Menu search bar).
2. Select Public Key Policies.
3. Under Object Type, right-click on Certificate Path Validation Settings.
4. Select the Network Retrieval tab.
5. Set the both "Default retrieval timeout settings" to 1 second, or to the value you prefer. Typically, both URL retrieval and path validation
cumulative retrieval require only milliseconds to complete.
6. Save the new settings and exit.
Workaround 2: This method disables checks for revoked certificates.
1. From the Control Panel or Internet Explorer, open Internet Options.
2. Select the Advanced tab and scroll down to Security.
3. Uncheck the option, "Check for publisher's certificate revocation."
4. Save the new settings and exit.
Workaround 3: This method installs the certificates that the operating system is attempting to validate onto the local machine. Once installed
locally, the operating system will no longer need to access the network to retrieve them.
1. Locate any DLL or EXE file from Schneider Electric Software.
2. Right-click on the file and select Properties.
3. Select the Digital Signature tab.
4. Select the SE certificate from the list.
5. Select View Certificate.
6. On the the dialog that appears, select Install Certificate and follow the prompts to install the certificate on the local machine.
7. Locate the file Flxcore.dll and repeat steps 2 through 6 for it. By default, this file is located in:
C:\Program Files (x86)\Common Files\ArchestrA\Licensing Framework\License API2
InTouch HMI Issues

The following known issues are in addition to those documented in the InTouch HMI Readme.
1024217 When InTouch has been configured use the Distributed Name Manager to centralize the definition of Alarm Queries, there are some instances
where the queries will not be copied over correctly during the configuration of the EAC. Impacted applications will display a blank EAC rather than
the expected list of alarms. This issue affects Standalone, Modern, and Managed InTouch applications when the Distributed Name Manager is
configured with Alias Names and Hot Backup.
Workaround: To resolve the problem, open the Distributed Name Manager and manually copy the alarm queries to the affected EAC instance.
InTouch Access Anywhere Issues

The following known issues are in addition to those documented in the InTouch Access Anywhere Readme.
L00144565 Installing InTouch Access Anywhere through the Modify workflow can cause various issues related to uninstalling the product at a later time.
These include:
1. Registry keys to store the InTouch Access Anywhere installation path are not created. As a result, if you try to uninstall InTouch Access
Anywhere later, the uninstall operation will not complete.
2. You may not be able to launch an InTouch View.exe application after uninstalling, and then reinstalling, InTouch Access Anywhere.
Workarounds:
For issue #1 (registry keys not created), do the following:
1. Add registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\ITAA\ITAAServer
2. Create a string value under the new registry key named InstallLocation, and specify the ITAA install location for its value. For example:
C:\Program Files (x86)
For issue #2 (unable to launch InTouch View.exe application), do the following:
1. Uninstall InTouch Access Anywhere.
2. Restart the computer.
3. Re-install InTouch Access Anywhere.
Historian Issues
924302 When installing Historian along with any other component, and the other component requests a system restart, if you restart immediately after
closing out the Configurator, a number of warnings may appear in the logger from the Historian services. This is caused by a timing issue.
The warning messages can be safely ignored because they do not affect the configuration of the Historian, and do not have any effect on the
system during or after the system restart.
931966 When using silent install to upgrade Historian to Wonderware System Platform 2017 Update 1 from a version that set a default password for SQL
Server users, warning messages are logged that alert you to set new passwords for various system users after the Configurator runs. Your
system will continue to operate normally without resetting the passwords, but changing the passwords will increase system security.
Licensing Issues
779958 When the same license is acquired on both a local node and in an RDP session that originates from the same node, the License Manager may
not show all the licenses that have been acquired. This occurs even though the licenses are counted properly on the license server. The license
count that you see applies only to the node you are viewing. Thus, once you reach your maximum number of licenses, you will not be able to
acquire additional licenses, even though the license manager may indicate that more licenses are available.
793643 If you have not set a default browser, and you install 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 Update 2 Documentation
Wonderware Application Server 2017 Update 2 Documentation
Wonderware Historian Server 2017 Update 2 Documentation
Wonderware Historian Client 2017 Update 2 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 Update 2 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 Update 2 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 Update 2 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 Update 2 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 Version 17.2 Readme

Last revision: 5/10/2018
About This Readme

This Readme provides information about Wonderware InTouch Access Anywhere 17.2.
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 Version 17.2 provides the following new features and enhancements:
Windows multi-touch gesture redirection
InTouch Access Anywhere supports Windows multi-touch gesture redirection. All multi-touch gestures are redirected natively into the Windows session for use by an InTouch
application running inside an Access Anywhere session.
Multi-touch gesture redirection is enabled using the Access Where Toolbar button and by setting parameter values in the config.js and gestureConfig.js files.
Possible supported multi-touch gestures include the following:
Multi-touch Gesture Application Action
Two finger swipe up Scroll up
Two finger swipe down Scroll down
Two finger swipe left None
Two finger swipe right None
Two finger tap Double mouse click
Three finger swipe up None
Three finger swipe down None
Three finger swipe left Arrow right
Three finger swipe right Arrow left
Three finger tap Toggle keyboard

Single Sign On (SSO) support
SSO is a session/user authentication process that permits a user to enter one name and password to view an InTouch application immediately without entering a
username/password on each InTouch Access Anywhere Server. SSO is implemented using the FORM POST method in which users enter their password and username on an
HTML form submitted to the SSO server.
Additional InTouch Access Anywhere installation configurations
The Authentication Server can be installed on the same computer as the Secure Gateway or on a separate computer.
The Secure Gateway and Authentication Server can be installed on a computer running 32/64 bit Windows 10 Professional or Enterprise (Version 1607 and later).
The Authentication Server, Secure Gateway, and Access Anywhere Server can be installed on a single computer running a Windows Server operating system.
Prevent InTouch applications from appearing on the InTouch Access Anywhere Server Start page
Administrators can prevent InTouch applications from automatically appearing on the Start page list of viewable applications by adding the following entry to the intouch.ini file of
the application:
[InTouch]
ITAAAccessCode=0
Start menu Force Virtual Keyboard option
The Force Virtual Keyboard option enables users to always enter data by using a device virtual keyboard while an application is running. The Force Virtual Keyboard option
provides values Yes, No, and Auto. The default is Auto.
Start menu Force Touchscreen option
The Force Touchscreen option enables users to always interact with an application using touch gestures. The Force Touchscreen option provides values Yes, No, and Auto.
The default is Auto.
Add custom screen resolutions for InTouch applications
Administrators can enter a custom screen resolution to the AppList.xslt file located on the InTouch Access Anywhere Server. The custom screen resolution appears when users
select Application Resolution as the value of Display Options from the Start page.
<select id="resolution">
<option value="browser" selected="selected">STR_FIT_TO_BROWSER_WINDOW
</option>
<option value="screen">STR_FIT_TO_SCREEN_FULL_SCREEN</option>
<option value="640,480">STR_640_X_480</option>
<option value="3840,2160">STR_UHD</option>
<select>
For a complete list of resolved issues in this release, see the Resolved Issues section of the 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.
No InTouch Access Anywhere Server can be updated by installing Version 17.2 on a computer currently hosting an earlier version.
Important: All existing instances of InTouch Access Anywhere components must be removed from the computer before installing Version 17.2. InTouch Access Anywhere Servers
cannot be modified or repaired using Version 17.2.
The computer that will host the Wonderware InTouch Access Anywhere Server must be running one of the following 64-bit versions of Windows Server:
Windows 2012 Data Center (Not Standard Edition)
Windows 2012 R2 Standard and Data Center
Windows 2016 Standard and Data Center
You must install InTouch Access Anywhere Secure Gateway on a computer running one of the following versions of Windows:
Windows 10 Professional or Enterprise (Version 1607 or later)
Note: Windows 10 does not support .NET 4.5.2. .NET 4.6 and later must be installed for Windows 10 support.
Windows 2012 Data Center (Not Standard Edition)

Windows 2012 R2 Standard and Data Center
Windows 2016 Standard and Data Center
.NET Framework 4.5.2 Full Installation or later must be installed on the host computer if you are completing a stand-alone installation of InTouch Access Anywhere
Note: If you are installing InTouch Access Anywhere from Wonderware System Platform 2017 Update 2, .NET 4.7.1 must be installed on the host computer.
You must have an InTouch 2012 R2 TSE (RDS) or newer license activated. When InTouch is launched by InTouch Access Anywhere, this RDS license will be acquired per
browser session. The license is released when the InTouch application running within the RDS session is closed.
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.
Important Security Requirement: Securely Deploying InTouch Access Anywhere

Direct access to the InTouch Access Anywhere Secure Gateway over the Internet is not supported. Accessing the Secure Gateway by means of a VPN tunnel for all remote connections
is recommended.
Browsers
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
Firefox version 38 and later
Safari version 5 and later
Chrome version 12 and later
Opera version 11 and later
Important: Only the browser versions listed above have been tested on the specified hardware platforms (PCs, tablets and Smart Phones). No testing has been done on HTML5
browsers running on other devices not included in the above list (SmartTVs, eBook Readers, or game consoles).
Functionally Compatible Browsers

Certain versions of the browsers listed above, such as:
Firefox versions less than 6
Safari versions less than 5
Chrome versions less than 12
Opera versions less than 11
are in theory functionally compatible with InTouch Access Anywhere. While you may be able to use these versions of the web browsers with InTouch Access Anywhere, specific
behaviors are unknown because no formal testing has been conducted.
Browsers: Important Notes

Although Wonderware InTouch Access Anywhere supports the listed browsers, you should review the Known Issues and Behaviors section of this Readme for issues specific to each
browser.
Mobile Devices
Run-time interactions with InTouch applications are different on mobile devices than on traditional desktop computers. For example:
Touch gestures perform some of the tasks that a mouse would do on a desktop or laptop, but not all mouse events have an equivalent touch gesture.
Many mobile devices have built-in software keyboards instead of physical keyboards, which do not have keys such as F1-F12, CTRL, and ALT.
When using InTouch Access Anywhere to remotely view and interact with your applications, it is important to be aware of the behavior differences among devices, operating systems,
and browsers. For the best user experience, you should become familiar with the touch interfaces in the devices you will use, and factor these differences into the design of your InTouch
applications. For example:
Input animations do not need to invoke the InTouch or Windows operating system keyboards as mobile devices typically have their own.
Existing InTouch applications that make use of mouse events and keys or key combinations without a supported equivalent in a touch environment may require you to modify your
application to use alternate supported methods.
Resolved Issues
This section lists defects resolved with this release of InTouch Access Anywhere.
Defect Number Description
542896 Firefox: Values entered using the InTouch keyboard appear twice.
When connecting to the InTouch Access Anywhere Server through the Secure Gateway, the Tool Box displays icons for both PC and
658661
Mobile devices at the same time.
Internet Explorer 10: When connecting to the InTouch Access Anywhere through the Secure Gateway, the web tab icon displays as
665727
the default Internet Explorer icon instead of the green InTouch Access Anywhere icon.
L00133687 Internet Explorer 10, Safari 8: Playsound() works with Chrome, Opera, and Firefox, but not with Internet Explorer 10 or Safari 8.
Internet Explorer: When accessing the InTouch Access Anywhere Server through an RDP desktop session, user input animations
542851 using the Windows operating system keyboard do not start the keyboard. The recommended workaround is to use the device's built-
in keyboard.
Internet Explorer 10 on WinRT in a touch environment: A mouse cursor may disappear after using the Surface keyboard to enter
218943
data. As a workaround, use touch gestures in place of mouse inputs.
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
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
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), which are located at the root of CD installation disc.
InTouch Access Anywhere Product Documentation Name File Name
Wonderware InTouch Access Anywhere User Guide ITAA_UserManual.pdf
Wonderware InTouch Access Anywhere Server Administrator Manual ITAA_Server_AdminManual.pdf
Wonderware InTouch Access Anywhere Secure Gateway Administrator Manual ITAA_Gateway_AdminManual.pdf

You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:
http://www.adobe.com/products/acrobat/readstep2.html.
After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a PDF with the Adobe Reader Open command
from the File menu.
Avantis | Contact Us | Industry Software Suites | OASyS | SimSci | SimSuite | Skelta | Wonderware
Copyright © 2018 AVEVA Group Plc. All rights reserved.
The Schneider Electric industrial software business and AVEVA have merged to trade as AVEVA Group plc, a UK listed company. The Schneider Electric and Life is On trademarks are owned by Schneider Electric and are being
licensed to AVEVA by Schneider Electric.

Wonderware System Platform 2017 Update 2 Readme PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Wonderware System Platform 2017 Update 2 Readme PDF

Hochgeladen von

Copyright:

Verfügbare Formate

11/13/2018 Wonderware System Platform 2017 Update 2 Readme

Wonderware System Platform 2017 Update 2 Readme

Supported Wonderware System Platform Versions for Product Upgrade

Supported Wonderware System Platform Versions for Migration

Readme Files for Other Products in this Release

Important Information for Microsoft Windows 2016 and InTouch HMI

How to Find the Latest Product Requirements and Compatibility Information

New Features in Wonderware System Platform 2017 Update 2

New Features in InTouch OMI Update 2

User-Friendly Names for Assets and Navigation

Rearrange Navigation Items

ShowContent() Scripting Function and API Call

Quality and Status Icons in the Navigation Tree

New Features in InTouch HMI 2017 Update 2

Alarm DB Utilities and Controls Support Windows Authentication

InTouch Web Client Enhancements

Non-Administrative users can now open Managed Applications

WindowViewer OS Shutdown Event Handling

NAD Notification Reminder

New Features in Wonderware Historian 2017 Update 2

New Features in Wonderware Historian Client 2017 Update 2

Web Help Display and Video Playback

Browser Requirements and Recommendations

Browser Permissions for Displaying Web Help

Playback of Tutorial Videos

InTouch OMI SDK Web Help

InTouch OMI SDK Web Help

System Requirements and Guidelines

Third-Party Application Prerequisites

Hardware Requirements Notes

Windows 8.1 System Requirements

SQL Server requirements

Wonderware Historian Hardware Guidelines

Alternative Authentication Using Smart Cards

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

Minimum Required Operating System Version

Minimum Required Operating System Version

Wonderware Application Server

Wonderware System Platform 2017 Update 2 web clients

System Requirements by installation size

Windows Operating System Notes

SQL Server Notes

Virtual Environment Notes

Operating System Notes: Common for Wonderware Products

ActiveX Controls Behavior on Supported Windows Operating Systems

Configuring Remote Alarm Retrieval Queries

Terminal Services Behavior in Windows Server Operating Systems

Operating System Notes: Wonderware InTouch HMI 2017 Update 2

Operating System Notes: Wonderware Application Server

Using Wonderware Application Server with Supported Windows Operating Systems

Wonderware Application Server and User Account Control Level

Operating System Notes: Wonderware Historian Server

Operating System Notes: Wonderware Historian Client

.NET Framework Requirements and Compatibility

What's obsolete in the .NET Framework Class Library: https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx

.NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29

Considerations for SQL Server

Considerations for SQL Server Express

Additional SQL Server Notes for Wonderware Application Server

Third-Party Application Prerequisites

Wonderware System Platform Installation

Before Installing Wonderware System Platform 2017 Update 2

About the ArchestrA User Account