InTouch HMI 2017 UPDATE 1 Readme

About This Readme

This Readme provides information about InTouch HMI 2017 UPDATE 1 (Version 17.1.000). Readme files from previous releases of Wonderware InTouch HMI are posted on the Schneider Electric Software Global Customer Support (GCS) website.


When installing System Platform Version 2017 UPDATE 1, Operations Integration (OI) Gateway is installed as a hidden feature of InTouch HMI 2017 UPDATE 1.

  • If you previously installed FS Gateway, the WSP 2017 UPDATE 1 installation will remove FS Gateway, preserve your existing FS Gateway configuration, and port your configuration to a new instance of OI Gateway, retaining the FS Gateway name. Existing FS Gateway configurations that use OPC access will not be impacted.
  • OI Gateway will be installed as part of Wonderware System Platform 2017 UPDATE 1.
  • If your system has an older version of OI Gateway installed, the WSP 2017 UPDATE 1 installation will upgrade OI Gateway as a first action. You will need to re-run the WSP 2017 UPDATE 1 installation to install other components.

For more information about OI Gateway installation, upgrade, and uninstall, see the System Platform Installation Guide, “InTouch HMI Requirements and Prerequisites” section, “Installing OI Gateway and Modifying FS Gateway Installations” topic.

Related Topics

InTouch HMI 2017 UPDATE 1 Readme

New Features in InTouch HMI 2017 UPDATE 1

System Requirements

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

InTouch Documentation Issues

InTouch Documentation

Important Information for Microsoft Windows 2016 and InTouch HMI

When InTouch HMI 2017 UPDATE 1 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.


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

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

    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 InTouch HMI 2017 UPDATE 1

InTouch 2017 UPDATE 1 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 2017 UPDATE 1.

InTouch Web Client

The InTouch Web Client provides access to running InTouch HMI application using any major HTML5 web browser from a server or client computer. No special hardware or software are needed to support the Web Client. Users simply use their web browser to show a log on page to authenticate themselves and view a running InTouch application in read only mode.

A single user can access the Web Client if it is unlicensed. Multiple concurrent users can access the Web Client after it is licensed.

For more information on the InTouch Web Client, see Viewing InTouch Application Graphics in a Web Browser (ITWebBrowser.pdf) in your Wonderware installation location. The typical installation location is: C:\Program Files (x86)\Wonderware\InTouch.

Cross Reference Utility

The standard InTouch Cross Reference utility has been significantly enhanced to include ArchestrA symbols in an application’s standard InTouch tag cross reference list. A cross reference search for ArchestrA symbols can be conducted by the criteria shown below, which will be included as part of the Cross Reference utility’s InTouch Tag Use.

  • Custom property with reference to an InTouch tag
  • Animation with direct reference to an InTouch tag
  • Client script with direct reference to an InTouch tag
  • Embedded symbols’ reference to an InTouch tag
  • Attribute references in ArchestrA or Situational Awareness Library symbols to an InTouch tag

Script Editor Search and Replace Utility

The InTouch Script Editor has been enhanced with a Find and Replace utility to search a script based upon an entered search string. The Find utility includes a set of options to search by string case, conduct a directional search, or only search within a selected area of the script. The Find utility also includes the capability to select a type of search, including wildcard and regular expression searches.

System Requirements


This section describes the hardware and software requirements to support Wonderware System Platform 2017 UPDATE 1 products, including InTouch HMI 2017 UPDATE 1.

Related Topics

InTouch HMI 2017 UPDATE 1 Readme

About This Readme

New Features in InTouch HMI 2017 UPDATE 1

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

InTouch Documentation Issues

InTouch Documentation

Hardware Requirements

Hardware Requirements

System Sizing Guidelines

The following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2017 UPDATE 1 software based on the size of the installation. These guidelines are subject to the limitations of your Windows operating system.

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

Hardware Requirement

Small Installation (1 – 25K I/O per Node)

Medium Installation (25k – 50k I/O per Node)

Large Installation (More than 50k I/O per Node)

CPU Cores (Minimum)1

Greater than or equal to 2

Greater than or equal to 4

Greater than or equal to 8


Greater than or equal to 4

Greater than or equal to 8

Greater than or equal to 16

Storage (GB) 2

Greater than or equal to 30

Greater than or equal to 500

Greater than or equal to 1000

Network (Mbps)

Greater than or equal to 100

Greater than or equal to 1000

Greater than or equal to 1000


1 In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.

2 Minimum amount of storage needed to provide sufficient capacity for 1 week @ max frequency.

Hardware Requirements Notes

Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for InTouch HMI 2017 UPDATE 1. Refer to the following Microsoft Web pages for Windows and SQL Server hardware requirements:

Auxiliary Hardware Requirements

This section describes any optional hardware requirements beyond the specific hardware requirements discussed earlier in this Readme.

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, .NET Framework, and Virtualization Requirements

This section describes additional details about the supporting software for an InTouch HMI system.

Software Requirement Notes

Windows Operating System Notes

  • Windows versions 8.1, and 10 support touch screen gestures. If the user swipes in from the right edge of a touch screen with a finger gesture, a set of Windows charms appears, which includes Search, Share, Start, Devices, and Settings. Moving the mouse cursor to the upper-right corner of a screen also shows the Windows charms for non-touch screens.

    Showing the set of charms is a standard feature of Windows versions 8.1, and 10 that cannot be disabled by software for a touch screen. As a result, operators can access these Windows charms and possibly unlock a dedicated touch screen view node.

  • Newer operating system Service Packs (SPs) than those listed do not block the installation of Wonderware 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 in which Wonderware System Platform products are installed on up to five nodes. For a system with more than five nodes, 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 an 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 scripts, run under .NET 4.5.1.

    For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility .

  • .NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist.

Operating System Notes Common to Wonderware Products

ActiveX Controls Behavior on Supported Windows Operating Systems

Due to the Data Execution Prevention (DEP) feature of Windows 7 and later operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behavior in InTouch 2017 UPDATE 1 either in WindowMaker or WindowViewer. For more information, refer to Tech Note 922: “Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)” available from the Wonderware Technical Support web site.

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 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”. The indicated IP address will be unique to your alarm-providing node. Note the IP address for 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:


    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.

Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers

Starting with Microsoft Windows Vista, the operating system imposes “Session 0 Isolation” as a security enhancement. All Windows services and associated programs are required to run in Session 0, and no GUI applications are allowed to run in Session 0.

Prior to Windows Vista, Wonderware Application Server and InTouch WindowViewer ran in the same Windows session. Session 0 Isolation requires that Application Server and WindowViewer run in separate Windows sessions. Alarms that are reported by the Galaxy are handled by the Session 0 instance of Alarm Manager (AlarmMgr), which is now different from the Console Session instance of AlarmMgr that handles InTouch alarms. A simple alarm query in an InTouch alarm display such as

\InTouch!$System \Galaxy!Area_001

is now serviced by two separate instances of AlarmMgr — one running in the Console Session for InTouch, another running in Session 0 for the Galaxy.

This behavior, and related behaviors and error messages resulting from the Windows operating system Session 0 changes, along with procedures to configure the Distributed Alarm System to support alarms from both InTouch and Application Server on the same computer node running with Windows Vista and later operating systems, are described in detail in TechNote 988, “AlarmMgr Support for InTouch and AppServer on Windows Vista and Later”. You can download this TechNote from the Schneider Electric Software Global Customer Support (GCS) website.

Remote Desktop Services (Terminal Services) Behavior in Windows Server Operating Systems

Windows Server 2008 R2 and later Windows versions 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 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server 2008 and later, all remote connections are treated 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 Remote Desktop (Terminal Server Console) session.

In another aspect of Remote Desktop Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value with InTouch running in a remote desktop (RDP) client session. The cause of this behavior is that the relevant roles are not installed on the RDP client. You must install the “Remote Desktop Host” role in order for TSEGetClientId() and other related functions to work properly.

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.

Wonderware Application Server and InTouch HMI detect when the application is running in the console. In Windows Server, it implies that the application was started by a user physically at the machine. However, this behavior may require you to disable the group policy that enables Fast User Switching.

Wonderware software detects when an application is running in the console. All remote connections are treated as a remote RDP session by Windows Server, regardless of /console or /admin switches in the mstsc connection.

To disable fast user switching through the Group Policy interface

  1. Click Start and then Run. The Run dialog box appears.
  2. Enter gpedit.msc and click OK. The Group Policy dialog box appears.
  3. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon.
  4. Set Hide Entry Points for Fast User Switching to Enabled. Enabling this policy hides the Switch User option in the Logon interface, the Start menu, and the Task Manager.
  5. On the File menu, click Exit to close the Group Policy dialog box.

By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.

Wonderware InTouch HMI 2017 Operating System Notes

  • Windows client (starting with Windows 7) do not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
  • The EnableDisableKeys() function writes to the Windows registry to enable or disable some keys on the host computer running an application in WindowViewer. For security purposes, Windows 7 and later versions of Windows prevent Standard or Power users from writing to the registry. Windows Administrators can write to the registry if not disabled by local domain security policies.

    You can configure local Windows security policies that work in conjunction with the EnableDisablekeys() script function to regulate the user’s access to keys in a running InTouch application.

  • As of Wonderware System Platform 2014, a computer running Windows 7 or later operating systems can be configured as both an InTouch and an Application Server alarm provider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems.

    The following InTouch legacy script functions do not operate on 64-bit versions of Windows: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().

  • If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator on Windows 7 or later operating systems.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows 7 or later operating systems to function properly.
  • The onscreen keyboard options have changed, beginning with Windows 7 and Windows Server 2008 R2 operating systems.
  • Hovering to select from the Windows keyboard does not work in supported versions of Windows operating systems.

Wonderware InTouch HMI 2017 View Applications and DDE Support

NetDDE is not supported for InTouchView applications.

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

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

Wonderware InTouch HMI 2017 Support for Windows User Account Control

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

.NET Framework Requirements and Compatibility

IMPORTANT: Wonderware System Platform 2017 UPDATE 1 installs .NET 4.5.2 if the currently installed version of .NET is 4.5 or lower. If .NET 4.5.1 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2017 UPDATE 1, 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 1, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.5.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

Wonderware System Platform 2017 UPDATE 1 leverages Microsoft .NET Framework 4. The Wonderware System Platform installation program will install .NET 4.5.2 if your system uses version 4.5 or lower. No change is made if your system uses .NET 4.5.1 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. Wonderware System Platform 2017 UPDATE 1 will use .NET 4.5.1, 4.5.2, or later.

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.5.1 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to Wonderware System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.

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

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

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

What’s New in the .NET Framework:

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

Migration Guide to the .NET Framework 4.6 and 4.5:

.NET Framework 4 Migration Issues:

Virtualization Host Support

See the Schneider Electric Global Customer Support (GCS) Technology Matrix for supported virtualization environments.

Related Topics

System Requirements

Hardware Requirements

SQL Server Requirements

InTouch Access Anywhere Requirements

SQL Server Requirements

SQL Server Requirements for All Wonderware Components

See the GCS Technology Matrix for SQL Server requirements for Wonderware System Platform 2017 UPDATE 1 components, including InTouch HMI 2017 UPDATE 1.

Note: Match SQL Server version (32- or 64-bit) to operating system version.

We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program, especially if you expect Wonderware Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.

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, and then resume the installation.

Considerations for SQL Server

  • Alarm DB Logger To use the Alarm DB Logger, you must set the default SQL Server authentication mode from Windows-based to Mixed Mode.
  • SQL Server Configuration Rights: While installing Wonderware System Platform, configuration changes to SQL Server are required. If the installer does not have SQL Server administrative rights, the proper configuration of SQL Server may not be applied. A post-install aaConfig SQL utility enables you to verify if the SQL configuration has been performed.
  • 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 computer’s 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. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore initializes, and the progress dialog box quickly displays 100% completion of restoring the database, but the Galaxy .cab restore operation does not actually complete, and no Galaxy Repository is created. When you start the IDE, the Galaxy is blank.
  • 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 version installation. For more information and helpful procedures, see the following Microsoft references:
  • SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 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 to restore the aaAdministrators group.

Considerations for SQL Server Express

  • SQL Server Express is supported for use on a Galaxy Repository node and recommended for use only with small systems.
  • If you plan to modify an InTouch HMI installation which has SQL Server Express installed, then add Wonderware Application Server with full SQL Server, you must install the full SQL Server prior to modifying the InTouch HMI installation or installing Wonderware Application Server.
  • If you plan to use SQL Server Express with Wonderware Information Server and Wonderware on the same node, the following limitations apply:
    • Install Wonderware Information Server first with the SQL Server Express default instance name set to “SQLEXPRESS”. Then, install Wonderware InTouch HMI. This scenario will work without issues because each component uses a dedicated instance of SQL Server Express.
    • If you install InTouch HMI first, the Wonderware System Platform installer silently installs and configures SQL Server Express. Installing Wonderware Information Server will fail during configuration with an error message 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 is limited to the lesser of one CPU socket or four processor cores.
  • For InTouch HMI installations, the Wonderware System Platform installer installs SQL Server Express, if these conditions are met:
    • No other SQL Server elements are 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.
    • The installation program includes an option to not install SQL Server on an InTouch development computer. When the option is selected, it prevents SQL Server from being installed. Clear this option to automatically install SQL Server on a development computer.

Related Topics

System Requirements

Hardware Requirements

Operating System, .NET Framework, and Virtualization Requirements

InTouch Access Anywhere Requirements

InTouch Access Anywhere Requirements

The following sections describe the requirements to run Wonderware InTouch Access Anywhere Server and supported browsers. For detailed information, see the Wonderware InTouch Access Anywhere documentation.

You can determine the version of InTouch Access Anywhere Server installed on a computer using Programs and Features from the Windows Control Panel.


The InTouch Access Anywhere Server can be installed as a Wonderware System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional component installed on a separate computer within a network DMZ.

The following requirements must be met before you install the InTouch Access Anywhere Server or a Secure Gateway.

  • Wonderware InTouch Access Anywhere server must be installed on a 64-bit version of Windows that is supported by InTouch HMI 2012 R2 (version 10.6) or later.
  • Wonderware InTouch Access Anywhere must be installed on the same RDP Server computer as Wonderware InTouch HMI 2012 R2 (version 10.6) or later.
  • Remote Desktop (RDP) must be enabled and properly configured on the host computer. For information and guidance, see Tech Note 782, “Installing Remote Desktop Services on Windows 2008 Server R2 for Wonderware Products”. You also can refer to
  • 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 consumed per browser session. It will be released when InTouch is closed by InTouch Access Anywhere.
  • Per-Device licenses are not supported.

Supported InTouch Access Anywhere Browsers

Wonderware InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5-compliant web browser. Browsers validated to support Wonderware InTouch Access Anywhere include the following:

  • Apple Safari
  • Google Chrome
  • Microsoft Edge
  • Microsoft Internet Explorer
  • Mozilla Firefox
  • Opera

Functionally Compatible Browsers

Older versions of the listed browsers are functionally compatible with InTouch Access Anywhere. You may be able to use the following older versions of these browsers, but specific behaviors are unknown because no formal testing has been done with InTouch Access Anywhere.

  • Apple Safari versions 5 and 6
  • Google Chrome versions 11-27
  • Microsoft Internet Explorer versions 7 and 8.
  • Mozilla Firefox versions 4-21
  • Opera versions 11-14

You are strongly encouraged to upgrade to one of the supported browser versions listed in Browsers Tested with WindowViewer. For a complete list of considerations to run an InTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide.

Related Topics

System Requirements

Hardware Requirements

Operating System, .NET Framework, and Virtualization Requirements

SQL Server Requirements

Wonderware InTouch HMI Installation

For detailed English installation instructions, see the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf) or Wonderware System Platform Installation Help (WSP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed Wonderware InTouch HMI Getting Started Guide booklet that is included in the installation package. This booklet is provided for all supported languages.

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

Installing Wonderware InTouch HMI

The major decision you must make when you install InTouch HMI is whether to install the InTouch development and run-time components, or the run-time components alone. The installation program guides you in selecting the features you want, verifying or modifying your selections, installing prerequisite software, and then installing InTouch HMI and the ArchestrA IDE if you chose to install development components.

What You Need to Install InTouch HMI

You must have the following materials ready to install InTouch HMI:

  • Installation DVD.
  • Computer that meets the hardware and software requirements listed in this Readme.

    Important: Use the hardware and software requirements listed in the Wonderware Application Server Readme if you are going to install the ArchestrA IDE.


The installation program analyzes the software installed on your computer and lists any required software that is not installed.

Note: At the start of the installation, the prerequisites check is system-specific rather than product-specific.

The following prerequisites, if not already present on your system, will be installed by the Wonderware System Platform installation program:

  • Windows Installer 4.5
  • Microsoft .NET Framework 4.5.2
  • SQL Server 2014 Express SP1

    SQL Server 2014 Express SP1 is installed automatically if either of the following conditions are met:

    • No version of SQL Server is installed on the host computer.
    • You select only InTouch Development and Runtime during the Wonderware System Platform installation. You must not select any Application Server components. When you select InTouch Development and Runtime, a Galaxy Repository will be installed for you.

The installation program installs both system-specific and product-specific prerequisites. You do not have to exit from the installation program to install the prerequisite software. For more information about Wonderware System Platform installation prerequisites, see the Wonderware System Platform Installation Guide.

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 InTouch HMI 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 with network privileges if InTouch 2017 UPDATE 1 will be installed on a multi-node system
  • User account in which the password cannot be changed.
  • User account that is a member of the local Administrators group.

After you install the InTouch HMI, you can use the ArchestrA Change Network Account utility to change or recreate the ArchestrA user account. This utility is accessible from the Start menu in the Wonderware Common folder after you install InTouch. 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 recreate 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.

Performing the InTouch HMI Installation

Before you start installing InTouch HMI, you should have a clear idea whether you want to develop, deploy, and publish your own applications, or require only the InTouch run time, to run applications already created and deployed.

The following procedure will guide you through the installation, with information specific to the InTouch HMI.

To install the InTouch HMI

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Using Windows Explorer, manually start the installation by double-clicking setup.exe on the DVD.
  3. Follow the prompts to start the installation and install system prerequisites, as necessary.

    The installation program prompts you to select an installation type: either product-based selection or installation by computer roles. As you are only installing InTouch HMI, click the product-based selection as your installation type.

  4. Choose the components you want to install.
    1. If you choose InTouch Run Time Only, the following will be installed:
      • InTouch Run Time
      • InTouch documentation
      • Alarm DB Logger
      • OI Gateway (as a silent installation)
      • Application Server Bootstrap
      • ArchestrA Data Store
      • InTouch Supplemental Components: InTouch Recipe Manager, InTouch SQL Access, and Symbol Factory

      Note: The 16 Pen Trend supplementary component is not installed by default. You must select the Customize Installation option and select 16 Pen Trend from the product list to install it as part of the InTouch HMI installation procedure.

      • License Manager
      • Client Components
      • Server Components
    2. If you choose InTouch Development and Run Time, the following will be installed:
      • All items listed under step a in these instructions.
      • InTouch Development
      • Application Server (Bootstrap, IDE, and Galaxy Repository)
      • InTouch demo applications
      • Schneider Electric License Server
  5. When the installation prompts you to verify your selection, select Customize Installation if you want to add or remove components of your InTouch installation.
  6. After you verify and customize your selection, you are prompted to select the language you want to install. English is selected by default, but you can choose another supported language from the list.
  7. Follow the subsequent installation steps to:
    1. Accept the End User License Agreement.
    2. Create a new ArchestrA user account, or specify an existing account.
    3. Install any prerequisite software components not yet installed on the computer.
    4. The installation proceeds to completion. You must restart the computer after completing the installation.

Activating Your InTouch License

Wonderware enforces the use of its products with a software license. InTouch uses the Schneider Electric License Server to make licenses available. The Schneider Electric License Manager manages one or more License Servers.

You use the Schneider Electric License Manager interface to make licenses available to InTouch. First, import the entitlement XML file received upon purchase of the license. Then, select which licenses on the entitlement to activate on the License Server. After activation, the license becomes available to WindowMaker or WindowViewer upon start up. The license is released when InTouch is shut down.

InTouch will run in Demo Mode if it cannot consume a valid license at start up time.

To install Schneider Electric licensing, see the Schneider Electric Licensing Guide.

Antivirus Software Exclusions

Antivirus software should be implemented as part of a defense-in-depth strategy to secure your industrial control systems.

Visit to get the latest information on antivirus software recommendations.

Modifying, Repairing, or Removing the InTouch HMI

To modify, repair, or remove a product

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Access the Windows Control Panel and select the Programs and Features option. The list of software installed on your computer appears.
  3. Select the InTouch component, and then click the Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.
  4. Follow the prompts to modify, repair, or remove InTouch. The name of the Uninstall/Change button varies depending on the version of Windows installed on your computer.

    Note: Modern applications can no longer be created, edited, or run after Wonderware Application Server is uninstalled from the same computer that also hosts InTouch run time and development components. Modern applications no longer work because the Galaxy Repository required for Modern applications is removed when Wonderware Application Server is uninstalled.

Upgrading to Version 2017 UPDATE 1 from an Earlier Version of InTouch HMI

Upgrading refers to installation on a computer that already has a previous version. An upgrade removes the previous version of InTouch HMI and installs Version 17.1.

After the hardware and software requirements are met, you can upgrade to Wonderware InTouch HMI 2017 UPDATE 1 from the following versions of the InTouch HMI:

  • Version 10.2
  • Version 10.5
  • Version 10.6
  • Version 10.6 P01
  • Version 10.6 P02
  • Version 10.6 P03
  • Version 11.0
  • Version 11.0 P01
  • Version 11.1
  • Version 11.1 P01
  • Version 11.1 SP1

You can only upgrade Wonderware System Platform products that are already installed. You cannot install any new Wonderware System Platform products by an upgrade process.

To upgrade from a previous version of the InTouch HMI

  1. Insert the DVD into your DVD-ROM drive. Run setup.exe to start the set-up program. The upgrade feature dialog box appears.
  2. Follow the prompts to complete the upgrade.

Upgrade Notes

  • Important Note: If you plan to upgrade Wonderware System Platform on a computer that has InTouch Access Anywhere Server installed, you must first uninstall the InTouch Access Anywhere Server. Then, upgrade Wonderware System Platform and finally reinstall InTouch Access Anywhere Server.
    Back up any custom configuration of the installed instance of InTouch Access Anywhere before you uninstall it.
  • InTouch Development (WindowMaker) is now installed with support for ArchestrA graphics. This includes the ArchestrA Integrated Development Environment (IDE), Bootstrap, Galaxy Repository (GR), and FS Gateway.
  • If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to System Platform Version 17.1. You must upgrade Wonderware Application Server before upgrading InTouch HMI.
  • If you are using managed InTouch applications with ArchestrA Symbols from Application Server 3.1 SP3 or earlier, run the ArchestrA Symbol Analysis and Repair Utility before installing Wonderware Application Server to ensure that all issues reported by the utility are addressed.

Migrating Applications to Wonderware InTouch HMI 2017 UPDATE 1 (v17.1)

Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to InTouch HMI 2017 UPDATE 1 that were developed with earlier versions of InTouch HMI shown in the following table:

InTouch HMI



Node-by-Node Upgrade










7.11 P07




8.0 SP2 P04




9.0 P03




9.5 SP1




10.0 SP2




10.1 (no SP)




10.1 SP2




10.1 SP2 P01




10.1 SP3




10.1 SP3 P01




Note: For InTouch Version 10.2 and newer, refer to the Wonderware System Platform migration table. InTouch cannot be installed or upgraded as a single product since Version 10.2. Therefore all installed products on a node must be upgraded at the same time.

SPCPro was a Statistical Process Control (SPC) utility available with InTouch HMI prior to Version 11.0. SPCPro is no longer supported by InTouch HMI. We recommend that that you migrate your SPCPro databases to the latest version of QI Analyst if you still use SPCPro with InTouch. QI Analyst provides support for the latest versions of operating systems and databases.

QI Analyst also includes a utility to migrate your SPCPro database to a QI Analyst database, leaving the existing SPCPro database intact. Please contact your local Wonderware sales representative for further information.

Important Note: We strongly recommend that you migrate your current SPCPro databases to QI Analyst before installing System Platform Version 17 with InTouch HMI. InTouch no longer includes SPCPro and will not open or migrate applications containing SPCPro components.

Resolved Issues

InTouch HMI 2017 UPDATE 1 includes corrections for the issues listed in the following table. These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column shows other subsequent change requests that are related to the original change request.

Original Change Request

Related Change Requests



SR 103135536: ImportGraphicFromXml failed when using output generated from ExportGraphicToXml




SR 103138524: InTouch applications showing showing historical data from the Alarm Client obtained from History Blocks would become non-operational if the regional setting of the application was changed during run time.




SR 34211525: Displaying a window containing a complex ArchestrA symbol for the first time in a running application took as long as four seconds to fully load.



SR 41010477: Attribute values shown in a popup ArchestrA graphic were lost when the application language was switched during run time.




SR 41810464: When an event script was imported and configured to point to an existing tag in the application, the tag could still be deleted. When the tag was deleted, an assertion error was logged in WindowViewer.




SR 41810465: In InTouch 11.1 SP1 for Simplified Chinese in a Terminal Services environment, all remote clients read from the C:\Windows directory for the InTouch.INI file rather than the user directory.




SR 52314664: When an ArchestrA graphic was configured with Orientation and Point animations, changing the .Angle property directly would offset the Orientation coordinates of the graphic. This would cause the Orientation to rotate around the graphic’s center of mass rather than the center of the object.




When operator and verifier signatures were recorded for a Verified Write from WindowViewer, only the Verifier timestamp would appear in the Comment column of the Alarm Database Events table.






The font size of text included with an ArchestrA graphic became progressively smaller each time the graphic was redisplayed. In this case, the quality status of the graphic changed and no text style was assigned to the Quality Status indicator.





SR 48310017: In InTouch 2014 R2 SP1 with hotfix L00141399 installed, text associated with an Embedded Alarm Client symbol did not have smooth lines when embedded in an InTouch window with another instance of the symbol or in front of text.




SR 47410450: On a system with hotfix L00143289 installed, when the Alarm Database was restored using the Alarm DB Restore utility, new alarms were getting duplicated in the AlarmMaster table.






SR 41810471: When a Memory Real tag was used in an InTouch window and the window was imported into another InTouch application already containing the tag and the “Use existing tag” option was selected upon import, the “Delete unused tag” option was not disabled. This caused an assertion error in WindowViewer.


SR 103143878: When using SQLInsertPrepare,SQLInsertExecute,SQLInsertEnd functions with MSAccess database the the date string inserts correctly, but not the time string. Using the same database using SQLInsert inserts the date time correctly.




In the Japanese language version of InTouch, WindowMaker would become non-operational when the same object was copied and pasted between two windows multiple times in a short period.




SR 103144075: Tag names were truncated at the first 32 characters when returned by the GetXmlCurrentAlarms and the GetXmlCurrentAlarms2 methods




SR 48911553: For InTouch running on a Windows Server 2012 R2 Operating System, when a User Input animation was configured for an ArchestrA Graphic to call the Keypad at run time, the keys would slowly appear one row at a time.




SR 103144160: When the wwStringFromTime() script function was executed immediately after the StringChar() function, a blank log message would appear for wwStringFromTime(). When the execution order was reversed, a blank log message would appear for StringChar().




SR 48911552: A software button that invoked a string keypad remained in the pressed position even after closing the keypad.




SR 103143009: When InTouch was running on a system where an Operations Integration ABCIP version 6.1 server was used to communicate with Application Server, it was possible to write back to the configured PLC using a memory integer tag that contained a float value outside of the defined range. This was causing the returned value to be inaccurate.



SR 51810550: An ArchestrA symbol with the ShowGraphic() Topmost property applied was overridden after the symbol was opened for the second time and graphic caching was enabled.




SR 103144254: When the Embedded Alarm Client display language was set to French, alarm queries returned data very slowly.




SR 48911586: The Title Bar background color was always white in the Distributed Alarm Display during run time regardless of the configured color.



SR 49910570: When the InTouch.ini MouseMustBeOnObjectForOnKeyUp property was set to True, InTouch did not recognize when a mouse was hovering over a graphic foreground area if the user had previously clicked the mouse over the background area of a graphic.




SR 103143844: When InTouch was running on a computer with SQL Server 2012 installed and the application was published from the Integrated Development Environment, script functions used to read and write data to and from the SQL Server did not work automatically.


SR 10418331: Importing an existing Quick Function from another application with modified scripts was unsuccessful and the message “Quick Function might be in use…)” appeared.although the Overwrite button was available. The imported Quick Function had the same arguments and data type. Only the script body was modified.




SR 103144344: When double-byte characters were used in an alarm comment, the Alarm DB Logger inserted an invalid alarm comment after the first logged event.



SR 103145169: Recipe Manager was used to switch language tags from “Current Language for non-Unicode programs” to Simplified Chinese. After InTouch 2014 R2 SP1 was applied, the language tags could no longer be switched.



SR 40218658: Pan and Zoom controls disappeared from a window during run time if the user changed the displayed graphic programmatically.


An Embedded Alarm Control did not show alarms from a secondary server in an alarm hot backup pair configuration after a failover resulted from the primary server being shut down.



SR 103145245: Users could not acknowledge an UNACK-RTN alarm record in Alarm Viewer control. When a tag value returns to normal, the tag alarm should be equal to 0 and the unack_RTN message should no longer appear on the Alarm View control.



SR 103145675: The Tab key became non-operational after the user selected a button associated with the EnableDisableKey function and pressed the Ctrl+Alt+Del key combination.



SR 41810485: Individual objects inside Wizard objects were not listed in printed output of a print window request after Wonderware System Platform 2014 Patch 01 was applied to a Japanese version of InTouch.



Operator comments written during a verified write operation were truncated in the WWALMDB database record.



A transaction roll back occurred after attempting to restore the A2ALMDB alarm database using the InTouch DBRestore facility because of missing alarm records.



The X and Y axes changed on a trend pen chart although the Chart.Freeze property had been set to True, which should have prevented the chart from being changed.




The ArchestrA Trend Client control sometimes showed incorrect values immediately after opening the window containing the Trend control. The trend curve was not drawn correctly, especially if the window with the trend control was opened, closed, and then reopened.



A Japanese version of WindowMaker would become non-operational if the user attempted to copy and paste an object between two windows using standard Windows keyboard shortcuts (Ctrl + C and Ctrl + V).



SR 17115431: InTouch applications became non-operational if two or more print requests were simultaneously queued to a printer by a script containing the PrintWindow() method.



SR 41810490: After applying hot fix L00136099, the printed output of an InTouch window did not list the individual graphics contained within Wizard Objects.



SR 51313192: After placing the Alarm Client control to Historical Alarms and Events mode, the default query was blank. The default query cannot be overwritten with the AlarmClient.QueryFilters.DefaultFilter.FilterCriteria function at run time.



Modern applications could not be migrated from InTouch 2014 SP1 Patch 02 to InTouch 2017.




An embedded SA_Target Graph symbol did not show updated custom property values during run time when the symbol’s ShowLabels Wizard Option was set to False.


SR 43612359: The Windows MSXML4.0 file in a software product represents a well known security vulnerability. Removing the MSXML4.0 file from an installed instance of InTouch HMI will prevent WindowMaker from opening.



SR 48710314: The Embedded Alarm Control (EAC) retrieved and displayed alarm records from the Alarm database v_NewAlarmEventHistoryInternal table much more slowly than the legacy InTouch Alarm Control.



SR 57210451: Archestra symbols containing Blink and Visibility animations were set to be hidden when the containing window was initially displayed. The symbols would become visible if the window was minimized and then maximized.


SR 45511275: The images in the InTouch HMI Visualization Guide did not match the updated Classic View and Project View in InTouch WindowMaker.



SR 103145868: When the Region was set to South Africa and Language set to English South Africa, InTouch HMI would throw an error “Not enough memory for window”.



SR 103146031: In InTouch 2017, the addition of the multi monitor configuration settings to the win.ini file did not enable multi monitor (2x screens 1920×1080)



SR 103144818: An archestra graphic with multiple grouped elements are animated to move horizontally. Over time the graphics start moving on the vertical axis, although there are no vertical animations.



SR 103143905: When using the cross reference utility to look for a quick function within an action “on mouse over” script, no results are returned.

Known Issues

This section describes known issues that remain in the release of InTouch HMI 2017 UPDATE 1.

Change Request



In the Embedded Alarm Client, when executing a filter in WindowViewer that contains three or more grouping operations, an error will display stating that the filter is not valid.

Workaround: Use a query for the same grouping logic and add “Provider” and “Group” to satisfy the query definition for a current alarm.


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


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

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

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


In a Windows 8.1 32-bit Operating System, an attempt to connect to a Galaxy from the IDE or open an InTouch Modern application in WindowMaker will not succeed while creation of another Galaxy or Modern application is in progress.

Workaround: Wait for the Galaxy or Modern application to finish being created before launching the IDE or WindowMaker.


In an InTouch Modern application, when a client control embedded in a symbol is overridden by a client control of a different version, the updated client control will not be reflected upon the initial close and restart of WindowViewer.

Workaround: Restart WindowMaker after importing the newer version of the client control.

When a script function library is imported into an InTouch Modern application and an action script from the library is used on a symbol and the imported script library is then overridden by a library of the same version but different method logic, the action script used in the symbol will fail to execute at runtime.

Workaround: Update the symbol thumbnail of the symbol containing the script before switching to runtime.


InTouch applications have the capability to run on the same computer as Wonderware System Platform 2017 ViewApps. However, to run both applications on the same computer, the InTouch application must be launched before a Wonderware System Platform 2017 ViewApp .


In a system with a large number of alarms that are rapidly changing state, applying an ArchestrA Alarm Control filter by name, value or state does not reduce the Alarm Manager or WindowViewer CPU consumption. Alarm Manager and WindowViewer will consume the same amount of CPU as before the filter was applied. The “CurrentValue” and “Quality” sorting columns do not work.

Workaround: To reduce CPU consumption, apply a provider, group or priority filter.


The InfoAppTitle method returns an empty string for Internet Explorer.

Workaround: Use Google Chrome.


Angled connector lines do not maintain horizontal and vertical orientation with 90 degree angles to each other when placed in a symbol whose dimensions exceed 1280 by 1280 pixels. Instead, a connector will revert to a straight line between connection points beyond the 1280 by 1280 pixel boundary.


When using a non-default SQL port: If the primary Historian server is down during a restart of WindowViewer, trend updates are delayed by approximately 25 seconds. This is a one-time delay after WindowViewer restarts.


After changing the SQL port of the Historian node and restarting Historian, the ArchestrA Trend Client (RT Trend) does not reconnect to Historian.

Workaround: Restart the instance of WindowViewer hosting the Trend client.


After switching between default and custom SQL ports for Dual Historian, on a machine where the ArchestrA Trend Client (RT Trend) is used and is configured by scripting, only the real time trend displays, not the Historian trend.

Workaround: Delete the servers.xml file typically found at the following location: C:\Users\<user-name>\AppData\Local\Wonderware\ActiveFactory\servers.xml.


Connecting to a SQL database in Microsoft Windows 8 or Windows 10 operating systems, when a non-default port is configured for SQL, results in an error message that a connection to the server is not available.

Workaround: Disable (shut down) the firewall on Windows 8 and Windows 10 operating system machines.


Migrating a Galaxy which has an InTouchViewApp with embedded Historian Client controls from Wonderware System Platform versions 2012R2 or 2014R2 to version 2014R2 Service Pack 1, results in errors logged in the Logger.

Workaround: Before migrating the InTouch application, delete the previous version Historian Client controls that exist in the Galaxy. Import the newer version controls.

Leave a Reply

Your email address will not be published. Required fields are marked *

8 + 2 =