InTouch HMI 2017 Update 3 SP1

InTouch HMI 2017 Update 3 SP1 Readme

Last revision: 5/22/2019

In This Document About This Readme New Features System Requirements InTouch HMI 2017 Update 3 SP1 Product Compatibility InTouch HMI Installation Resolved Issues Known Issues InTouch Documentation Issues InTouch Documentation

About This Readme

This Readme provides information about InTouch HMI 2017 Update 3 SP1 (Version 17.3.100). Readme files from previous releases of InTouch HMI are posted on the Support website.

Important!

When installing System Platform 2017 Update 3 SP1, Operations Integration (OI) Gateway is installed as a hidden feature of InTouch HMI 2017 Update 3 SP1.

• If you previously installed FS Gateway, the System Platform 2017 Update 3 SP1 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 System Platform 2017 Update 3 SP1.
• If your system has an older version of OI Gateway installed, the System Platform 2017 Update 3 SP1 installation will upgrade OI Gateway as a first action. You will need to re-run the System Platform 2017 Update 3 SP1 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 3 SP1 Readme New Features System Requirements InTouch HMI 2017 Update 3 SP1 Product Compatibility InTouch HMI Installation Resolved Issues Known Issues InTouch Documentation Issues InTouch Documentation

Important Information for Microsoft Windows Server 2016 Users

Remote Desktop Services and InTouch HMI

When InTouch HMI 2017 Update 3 SP1 is installed on a Windows Server 2016 computer 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 computer. 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 System Platform 2017 Update 3 SP1.

   Important: You can install the Microsoft update before or after System Platform. However, we recommend installing the Microsoft update before you install System Platform.

How to Find the Latest Product Requirements and Compatibility Information

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

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

New Features

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

System Requirements

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

Hardware Requirements

System Sizing Guidelines

The following table provides guidelines for hardware configurations suitable for System Platform 2017 Update 3 SP1 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
RAM1 (GB)	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

Notes:

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 3 SP1. Refer to the following Microsoft Web pages for Windows and SQL Server hardware requirements:

• Windows Server 2016 System Requirements
• Windows Server 2012 R2 System Requirements
• Windows Server 2012 System Requirements
• Windows 10 System Requirements
• Windows 8.1 System 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 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 System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are three exceptions. System Platform products do not need to be uninstalled when upgrading from:
  • Windows 8 to 8.1
  • Windows 8.1 to 10
  • Windows 2012 to Windows 2012 R2

.Net Notes

• Versions of .NET (other than 4.x versions) can coexist, but all .NET code, including QuickScript.net scripts, run under .NET 4.7.2.

  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 253.127.148.120". 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:

   \\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.

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, Application Server and InTouch HMI 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 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 Application Server is minimal as most Application Server processes run as services. One impact to Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.

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.

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

InTouch HMI View Applications and DDE Support

NetDDE is not supported for InTouchView applications.

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

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

InTouch HMI Support for Windows User Account Control

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

.NET Framework Requirements and Compatibility

IMPORTANT: System Platform 2017 Update 3 SP1 installs .NET 4.7.2 if the currently installed version of .NET is 4.7.1 or lower. If .NET 4.7.2 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to System Platform 2017 Update 3 SP1, 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 System Platform 2017 Update 3 SP1, 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.75.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

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

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.7.2 or higher. Although .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 System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.

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

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

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

What's New in the .NET Framework: http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx

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

Migration Guide to the .NET Framework 4.6 and 4.5: https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29

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

Virtualization Host Support

See the 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 System Platform 2017 Update 3 SP1 components, including InTouch HMI 2017 Update 3 SP1.

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 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 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 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:
  • Upgrade to SQL Server 2014
  • Migrate SQL Server 2000 to SQL Server 2012
  • Migrating to SQL Server 2008 R2
  • Migrating to SQL Server 2008
  • T-SQL scripts to migrate SQL server 2000 user databases to SQL server 2012
  • ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2012
  • ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2008 R2
• 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.

Requirements

The InTouch Access Anywhere Server can be installed as a 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 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 http://technet.microsoft.com/en-us/library/dd883253.aspx.
• 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

InTouch HMI 2017 Update 3 SP1 Product Compatibility

Product Compatibility refers to the ability of a product to work with various versions of other products running on different network nodes. Product Compatibility also refers to the ability of a product to work with various versions of the same product running on different nodes.

Coexistence refers to same-node installation of a product with other products that support the same hardware, operating system, and SQL Server versions. Other products not listed will be covered by System Compatibility Testing unless specifically noted.

In a single-node environment, if you want to install multiple components on a single computer, all components must be at the versions delivered in System Platform 2017.

In a node-to-node environment, components are compatible between the current licensed version and one licensed version back. Refer to the GCS Technology Matrix for more information.

The following table lists products and their compatibility and coexistence with InTouch HMI 2017 Update 3 SP1.

Product	Version	Compatibility	Co-existence
System Platform	4.5	N	N/A
	2012	Y	N/A
	2012 R2	Y	N/A
	2012 R2 P01	Y	N/A
	2012 R2 P02	Y	N/A
	2012 R2 P03	Y	N/A
	2014	Y	N/A
	2014 P01	Y	N/A
	2014 R2	Y	N/A
	2014 R2 P01	Y	N/A
	2014 R2 SP1	Y	N/A
	2017	Y	N/A
	2017 Update 1	Y	N/A
	2017 Update 2	Y	N/A
	2017 Update 3	Y	N/A
InTouch CE	10.1	N	N
Manufacturing Execution System	4.0 SP1	N	N
	4.0 SP2	N	N
	MES 2012 P01-4.5	Y	Y
	MES 2014-5.0	Y	Y
	MES 2014 SP1-5.0.1	Y	Y
InControl™	7.11 SP2 P01	N	N
Manufacturing Execution Module	1	Y	N
Batch Management™ * If you are using Information Server with Batch Management software, upgrading to Information Server 5.6 requires an Batch Management hotfix to maintain compatibility.	10.0 (2012 R2)	N	N
	10.1 (2014)	Y *	Y *
	10.2 (2014 R2)	Y *	Y *
	11.0 (2014 R2 SP1)	Y *	Y *
QI Analyst™	8.0 SP1 P01	N	N
	8.0 SP2	Y	Y
	8.0 SP3	Y	Y
SCADAlarm™	6.0 SP2 P01	N	N
Intelligence	1.5	N	N
	1.5.100 (2012)	Y	Y
	2.0 P01 (2014 R2 P01)	Y	Y
ArchestrA Workflow™	1.5 (2012)	N	N
	1.6 (2012 SP1)	N	N
	1.7 (2012 R2)	N	N
	1.8	N	N
	1.9 (2012 R2 SP1)	N	N
Workflow Management	2014	N	N
	2014 R2	Y	Y
	2014 R2 SP1	Y	Y
Mobile Operator Rounds	5.01	Y	Y
	2014 R2	Y	Y
PEM	2.1 SP1	N	N
Insight (see components below)	1.0
Historian Client Trend	10.6	Y	Y
InTouch	11.x	Y	Y
MRC (Mobile Report Connector)	2014 R2	Y	Y
	2015	Y	Y
Recipe Manager Plus	1.0 (2014)	Y	Y
	1.5 (2014 SP1)	Y	Y
	2.0 (2014 R2)	Y	Y
Citect-VJC	7.2 SP3	Y	Y
	7.3 Latest SP	N	Y
	7.4 SP1	Y	Y
ClearSCADA	CS 2013 R1	N	Y
	CS 2013 R2	N	Y
	CS 2014 R1	N	Y
	CS 2015 R1	Y	Y
Sentinel System Monitor	1.1	Y	Y
Sentinel Agent	1.0	N/A	Y
Sentinel Server	1.0	N/A	N

Supported	Y
Not Supported	N
Not Applicable	N/A

In some cases, InTouch HMI is supported in newer environments than a compatible product. InTouch HMI has been tested for compatibility with a listed product only in the environments that are supported by that particular product.

Related Topics InTouch HMI 2017 Update 3 SP1 Readme About This Readme New Features System Requirements InTouch HMI Installation Resolved Issues Known Issues InTouch Documentation Issues InTouch Documentation

InTouch HMI Installation

For detailed English installation instructions, see the System Platform Installation Guide (WSP_Install_Guide.pdf) or System Platform Installation Help (WSP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed 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 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 Application Server Readme if you are going to install the ArchestrA IDE.

Prerequisites

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 System Platform installation program:

• Windows Installer 4.5
• .Microsoft .NET Framework 4.7.2
• SQL Server 2014 Express SP2

  SQL Server 2014 Express SP2 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 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 System Platform installation prerequisites, see the 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 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 HMI 2017 Update 3 SP1 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
      • AVEVA Enterprise 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 AVEVA Enterprise License Server to make licenses available. The AVEVA Enterprise License Manager manages one or more License Servers.

You use the AVEVA Enterprise 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 AVEVA Enterprise licensing, see the AVEVA Enterprise 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 https://www.wonderware.com/contact/contact-support/ 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 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 Application Server is uninstalled.

Upgrading to Version 2017 Update 3 SP1 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.3.1.

After the hardware and software requirements are met, you can upgrade to InTouch HMI 2017 Update 3 SP1 from the following versions of the InTouch HMI:

• Version 11.1 SP1
• Version 11.1 SP1 P02
• Version 17.0
• Version 17.1
• Version 17.2
• Version 17.3

You can only upgrade System Platform products that are already installed. You cannot install any new 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 System Platform on a computer that has InTouch Access Anywhere Server installed, you must first uninstall the InTouch Access Anywhere Server. Then, upgrade 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 Application Server is installed on the same node as InTouch HMI, both must be upgraded to System Platform Version 17.3.1. You must upgrade 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 Application Server to ensure that all issues reported by the utility are addressed.

Migrating Applications to InTouch HMI 2017 Update 3 SP1 (version 17.3.1)

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

InTouch HMI	From	Upgrade	Node-by-Node Upgrade	Migrate
	7.0	N	N/A	N
	7.1	N	N/A	N
	7.11 P07	N	N/A	Y
	8.0 SP2 P04	N	N/A	Y
	9.0 P03	N	N/A	Y
	9.5 SP1	N	N/A	Y
	10.0 SP2	N	N/A	Y
	10.1 (no SP)	N	N/A	Y
	10.1 SP2	N	N/A	Y
	10.1 SP2 P01	N	N/A	Y
	10.1 SP3	N	N/A	Y
	10.1 SP3 P01	N	N/A	Y
	11.1 SP1	Y	Y	Y
	11.1 SP1 P02	Y	Y	Y
	17.0	Y	Y	Y
	17.1	Y	Y	Y
	17.2	Y	Y	Y
	17.3	Y	Y	Y

Note: For InTouch Version 10.2 and newer, refer to the 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.3.1 with InTouch HMI. InTouch no longer includes SPCPro and will not open or migrate applications containing SPCPro components.

Resolved Issues

InTouch HMI 2017 Update 3 SP1 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	Description
N/A	33129	Occasionally, data on the Trend Client Control would not display on the Web Client, if there was no change to the tag value.
N/A	34341	Alarm columns displayed on the web client could not be resized.
N/A	34454	Occasionally, a warning is logged in the SMC, when a MapApp configured with a symbol is rendered in Runtime.
N/A	34486	FillStyle Animation with more than 16 Truth Table conditions did not show correctly.
L00149925	L00150348	SR 103151389: Alarms from the second page were not appended to the first page after performing the filter operation on the SA-Alarm_HistoryPage symbol.
L00151025	L00151434	SR 103153238: Cyrillic characters in string tags were not handled correctly.
L00151169	L00151556	SR 27811574: On selecting the Historical Alarms in Alarm client, Current Alarms did not display even on Requery.
L00151691	L00151811	SR 38710511: The Trend.GetPenValAtX1("Pen1") function when used directly on an animation, threw an error in runtime.
L00151958	L00152070	SR 103155609: When the AlarmDBLogger is running, and if the AlarmGroup.AlarmEnabled=1, it caused InTouch to freeze for minutes
L00151972	L00152201	SR 51314975: On the Windows 10 operating system, when there were a high number of symbols using GDI objects users wold receive an Windows 10 Limit exceeded error.
L00151937	L00152279	SR 103154595: ArchestrA symbols in a Modern application, were not visible on a NAD clients, when the symbols are called through scripts in a frame window.
L00152138	L00152367	SR 23315257: Renaming an Access Name that had a secondary source failed and threw an error.
L00152285	L00152401	SR 22210505: When a record on the Alarm Control was clicked it displayed an error in the SMC.
L00152451	L00152522	SR 103156771: Trend Client control did not display Historian values in InTouch window when it was changed.
N/A	L00152544	SR 103157856: User could not use the Ctrl+C keyboard shortcut to Copy Expression In Data Change Script.
L00152517	L00152571	SR 57211099: Applying the Filter for Operator = 'NameOfOperator' on the Alarm control did not return any results.
L00152433	L00152610	SR 15318556: When the Trend Client Control is configured with the setting 'Cache ArchestrA Graphics not embedded in InTouch Windows' it did not display the correct Trend when it was closed and opened using the ShowGraphic function.
L00152140	L00152629	If the EnableDisableKeys (1,1,1) function was running in the background and a Logon Dialog box was launched, and the user used a combination of the Control and Windows keys, the user could not use the keyboard to type any details in the logon dialog box.
L00152420	L00152630	SR 63510762: InTouch WindowViewer did not acquire available licenses and disconnected intermittently.
L00152529	L00152672	SR 103157973: Viewing the Alarm Client Control on HD displays caused the custom message to display incorrectly.
L00151117	L00152681	SR 57210984: Application developed at a lower resolution did not run in the full screen of a display with a higher resolution and could not be maximized when 'Always Maximize' and 'Dynamic Resolution' were enabled.
L00151134	L00152682	SR 25315433: An InTouch Frame Window closed if you used the ESC key when the focus was on a combo box or list box embedded with an ArchestrA graphic.
L00151240	L00152683	SR 103154185: Converting SmartSymbol to ArchestrA symbols from InTouch 10.0 to System Platform 2017 Update 2 failed.
L00151204	L00152684	SR 103155321: A large number of analogue entries using the PC Keyboard (Not Intouch Interface Keypad) caused InTouch WindowViewer to crash.
L00151375	L00152685	SR 63211133: Users could not acknowledge an alarm in a Distributed Alarm configuration when the Galaxy was set to Group Security and InTouch HMI was set to ArchestrA security.
L00151771	L00152688	SR 59513650: When a button on a Frame Window was used to launch a keyboard, the keyboard would disappear immediately after the button click was released.
L00151606	L00152689	SR 37511676: The user was unable to enter more than 10 characters for the password while using the ChangePassword() function.
L00151837	L00152690	SR 103155066: for more complex galaxy, it took a long time to fast switch between WindowMaker and WindowViewer.
L00151167	L00152707	SR 63911454: Some dlls were found missing when publishing a Modern application.
L00151201	L00152709	SR 103154062: For an ArchestrA Trend control, when the ‘endtime’ value was configured to a time in the future, the trend did not work, and new data was distorted.
L00151167	L00152707	SR 63911454: Some dlls were found missing when publishing a Modern application.
L00151190	L00152715	SR 77210011: On Windows 10 64 bit and Windows Server 2016 64 bit operating systems, invoking the On Screen Keyboard, using the function StartApp "OSK", did not display the keyboard.
L00151063	L00152719	SR 103151078: Intermittently WindowViewer did not recognize the second monitor.
L00151766	L00152740	SR 37613238: The user received a check in dialog box although there was no change in the appli
L00151826	L00152742	SR 103154038: When using the ShowTopLeftAt() function the window shifted by some pixel.
L00151634	L00152743	SR 103155941: On a Japanese operating system, the user could not use an ArchestrA symbol with a Japanese name on an InTouch window.
L00152600	L00152755	SR 49911001: While using the Delete Used Tags dialog box, multiple selection was difficult as the focus would return to the top of the list after every selection.
L00151757	L00152812	SR 22111451: On opening a graphic with 30 or more Spark lines, the connection timed out and graphic did not populate with data.
L00151390	L00152813	SR 103155394: SR 103156270: The behavior of ComboBox changed after the migration from WSP 2017 Update 1 to Update 2.
L00151003	L00152814	SR 59513412: When a ListBox was inserted in an ArchestrA symbol and then if the Symbol was dropped on an InTouch Frame window, the symbol is resized in both design and runtime.
L00151651	L00152815	SR 103155802: When using the SA_Meter SAL symbol, if PVRangeRangeOptimalMax and PVRangeOptimalMin used a reference in a Data Change script, a Warning message was logged in the SMC.
L00152801	L00152845	SR 103158535: In a specific case, opening a symbol in the IDE, caused the IDE to crash with a System.NullReferenceException error.
L00152745	L00152846	SR 41810589: Entering a 39 Byte seach string in the InTouch Find dialog box crashed WindowMaker.
L00152773	L00152890	SR 103158226: In cases, where the values of the Y-axis in TrendClient, are set to a max length greater than 6 characters, did not appear completely on the TrendClient and were cut off at the start of the numbers.
L00152678	L00152914	SR 14812915: View.exe and AlarmManager were crashing frequently.
L00152880	L00152976	SR 103157196: Using the Show function in a script, the autocomplete displayed an error 'String Expected' although the value 'Tagname.Name' was provided.
L00152827	L00152996	SR 57210992: ArchestrA graphics did not resolve Historical Tag references for all pens after being closed and reopened using the ShowGraphic or ShowSymbol functions.
L00152832	L00152997	SR 41810582: WindowViewer did not work and lost focus when the 'while key down' script ran continuously.
L00153046	L00153116	SR 63912061: The Show Window animation in WindowMaker did not work as expected on Windows 2012 server and Windows 2016 server.
L00152828	L00153151	SR 103158621: The error message in the SMC logs was displayed even when the embedded symbol and the reference in the script was deleted.
L00153102	L00153170	SR 103159139: The AutoComplete feature of the script editor appeared when the Enter key was used with the comments block.
L00153054	L00153234	SR 103158235: The ACK_RTN Time Stamp did not reflect the RTN time but the ACK time.
L00153110	L00153302	SR 103158191: The Tooltip did not work consistently with the ShowGraphic function in Runtime.
L00153176	L00153303	SR 63110119: History Blocks and the configured colors in the Alarm Control Client did not work with the German operating system.
L00153188	L00153304	SR 45511406: SQLSelect command were not working if square brackets are used in the SQL Bind List of InTouch 2017 Update 3.
L00153307	L00153458	SR 63211664: The Quality for the IO-Tag changed when an InTouch Window was opened and closed.
L00153246	L00153459	SR 103159358: Arguments within the Script Editor were highlighted as an error (red line) although the scripts were correct.

Known Issues

This section describes known issues that remain in the release of InTouch HMI 2017 Update 3 SP1.

Change Request	Description

InTouch Documentation Issues

The following table lists corrections to InTouch HMI 2017 Update 3 SP1 documentation.

Item	Location of Change	Existing Documentation	Change

InTouch Documentation

The InTouch product library consists of a set of Portable Document Files (PDF) available in the following location of the Wonderware System Platform DVD:

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

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 book with the Adobe Reader Open command from the File menu. Context-sensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have open on your computer.

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