InTouch 2012 R2 (10.6) Classic Install Guide
InTouch 2012 R2 (10.6) Classic Install Guide
InTouch 2012 R2 (10.6) Classic Install Guide
1.
1.
2.
2.
1.
1.
1.
2.
2.
1.
2.
1.
2.
3.
4.
5.
6.
7.
3.
1.
4.
5.
6.
7.
8.
3.
4.
5.
Pre-Requisites
System Requirements
Hardware Requirements by Installation Size
Auxiliary Hardware Requirements
Alternative Authentication Using Smart Cards
Using Multiple Network Interface Cards
Operating System, .NET Framework, and Virtualization Requirements
Summary of Requirements for ArchestrA System Platform 2012 R2
Operating System Notes Common to Wonderware Products
ActiveX Controls Behavior on Windows 7 and Windows 2008 R2
Operating Systems
Configuring Remote Alarm Retrieval Queries When Running Windows
Vista, Windows 7, or Windows Server 2008 R2
Wonderware InTouch HMI and Alarm DB Logger
Terminal Services Behavior in Windows Server 2008 Operating
Systems
Wonderware InTouch HMI 2012 R2 (v10.6) with Windows Vista,
Windows 7, and Windows Server 2008 R2
Wonderware InTouch HMI 2012 R2 (v10.6) View Applications and
DDE Support
Wonderware InTouch HMI 2012 R2 (v10.6) Support for Windows User
Account Control
.NET Framework Requirements and Compatibility
Alarm Client and Trend Client Prerequisites
Performing the InTouch HMI Installation
Installing Your Wonderware Product License
Antivirus Software Exclusions
Modifying, Repairing, or Removing the InTouch HMI
Upgrading to Version 10.6 from an Earlier Version of the InTouch HMI
Licensing
Validation of Solution
Related Videos
INSTALLATION GUIDE
Description
Step by step installation of Wonderware's InTouch software version 10.6.
Pre-Requisites
Important!
FactorySuite Gateway (FS Gateway) 3.0 is installed as a hidden feature of InTouch HMI
2012 R2 (v10.6) in an ArchestrA System Platform 2012 R2 installation.
If you originally installed FS Gateway 2.0 SP1 without any other InTouch products,
then upgrading ArchestrA System Platform 2012 to ArchestrA System Platform 2012 R2 will
upgrade FSGateway to version 3.0.
If you originally installed FS Gateway 2.0 SP1 as part of ArchestrA System Platform
2012 with InTouch 10.5, you must uninstall FS Gateway before upgrading ASP 2012 to R2.
System Requirements
Hardware Requirements by Installation Size
The following table lists the hardware requirements for the ArchestrA System Platform 2012
R2 software based on the size of the installation.
Windows 7 and Windows Server 2008 R2 operating systems and SQL Server
versions impose hardware requirements that may exceed the minimum requirements for
Wonderware Application Server 2012 R2 (v3.6). If you intend to install ArchestrA System
Platform 2012 R2 on a computer running Windows 7, Windows Server 2008 R2, or
supported SQL Server versions, see the following Microsoft Web sites for hardware
requirements:
o
o
o
www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx
www.microsoft.com/windows/windows-7/get/system-requirements.aspx
msdn.microsoft.com/en-us/library/ms143506.aspx#EE32
See the following section for specific auxiliary hardware requirements.
If you are using multiple network interface cards (NICs), you must configure certain settings
for the firewall or else a remote node cannot connect to the Galaxy Repository node.
A connection is a term used to define a network interface card (NIC), its settings and the
settings of whatever the NIC is connected to. Under certain circumstances, the connection
on your computer can change if, for example, the IP address on your network card
changes. Your computer's connection can be affected by external factors. During computer
startup, and each time a connection changes, the operating system goes through an
"Identifying" process to determine which profile should be assigned to the connection.
A profile is a collection of firewall settings that can be applied to a connection. There are
three profiles currently defined in the operating system: Domain, Public, and Private.
The Domain profile is active only when the computer can authenticate with a
domain controller on all active interfaces such as LAN, wireless, and VPN. The domain
profile may be more or less restrictive than the other two profiles depending on network
security policies.
The Private profile is active whenever the network type for all active network
connections on the computer are identified as private networks. The private profile typically
is used in a more trusted environment and is less restrictive than the public profile to allow
for network discovery.
The Public profile is active in all other circumstances. The public profile typically is
more restrictive than the private profile because the computer often is connected to the
Internet in an insecure location. Network discovery and remote access are disabled rather
than explicitly blocking specific traffic. Firewall exceptions and rules can be created on any
or all of these profiles.
This is important because the OS Configuration utility and the Firewall utility apply their
firewall exceptions to the Domain and Private profiles only.
As previously noted, you can specify which profile you want assigned to a connection as
long as that connection is not a Domain connection. This is done through the "Network and
Sharing Center". Click the Network icon located on the right side of the task bar and then
click one of the networks that are shown. You can change a connection from a Public
profile to a Private profile. The firewall calls these settings "Profiles" but the network calls
them "Location types."
On computers using dual NICs, the first NIC is normally connected to the domain and is
assigned the Domain profile automatically. Windows typically assigns the second NIC the
Public profile.
The first issue is that your entire computer (all connections) is restricted to the most
restrictive of the profiles assigned to any connection. So if the second connection was
assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or
Firewall utilities will be allowed. The exceptions were set for Domain and Private only, not
Public. You must set the second connection to the Private profile for any of the firewall
exceptions to work. You want the active profile on the message exchange (MX) NIC to be
the profile opened by OS Configuration.
1.
2.
3.
4.
The second issue is that it appears that a restart of your computer, or even a restart of a
computer to which you are connected, can change your connection back to the Public
profile. Once again the firewall exceptions will not be effective. You'll have to change the
connection back to the Private profile after each restart or a restart of the connected
computer.
To avoid these NIC issues and prevent the Identifying process from taking place on a
connection and changing the assigned profile, certain items must be present in the
definition of the connection. Follow these rules and procedures:
If you have only one NIC, no action is required. The profiles and firewall rules are
automatic.
To configure two NICs, do the following:
If the second NIC is not physically connected to anything (that means no wire in it),
no action is required. The profiles and firewall rules are automatic.
If the second NIC is connected, it MUST be configured. Follow the rules for
configuring a normal redundancy setup provided in the Wonderware Application Server
User's Guide and the accompanying online help.
Assign the NIC an IP address, subnet mask and gateway address. Typically, these
addresses are internal, non-routable addresses. For example, 192.168.1.xx and
10.x.x.x are common addresses of this type.
A NIC acting as Redundancy Message Channel (RMC) does not require a default
gateway. Otherwise, the gateway can be the same as the IP address. Vista and
Windows Server 2008 will identify this NIC and assign it a Private profile.
If you do not configure the second NIC, Vista and Windows Server 2008 will assign a
profile of Public to this
NIC and cause all of the Wonderware product firewall
exceptions to be deactivated on all NICs.
Set a security policy so that Windows Vista and Windows Server 2008 do not re-set
the RMC NIC to a Public profile on rebooting the system or changing the IP address. To
make the Private profile setting persistent, do the following:
Enter and run this command: SECPOL.MSC. The Local Security Settings menu
appears.
Supported
Not Supported
Notes:
The entry for Application Server applies to the ArchestrA IDE (Development Node)
and ArchestrA Run time (Application Node).
The Galaxy Repository (GR Node) can run on a client Windows operating system
only in a single-node scenario.
Development and application nodes are considered to be clients of the server GR
node.
Other .NET Framework versions can coexist, but all scripts in objects run in .NET
Framework 4.0. For more information about .NET Framework requirements and
compatibility, see .NET Framework Requirements and Compatibility
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.
1.
2.
Terminal Services
Operating Systems
Behavior
in
Windows
Server
2008
In a change from Windows Server 2003, Windows Server 2008 no longer supports 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, Session 0 is no
longer an interactive session, and is reserved only for Windows services. Windows Server
2008 treats all remote connections as remote RDP sessions regardless of /console, /admin,
or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the
Terminal Server Console session.
In another aspect of Terminal Services behavior, InTouch HMI functions such as
TSEGetClientID() can return a null value when running on Windows 2008 SP2 and
Windows 2008 R2 operating systems 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
Terminal Server. You must install the "Terminal Server" role for Windows 2008 SP2 or the
"Remote Desktop Host" role for Windows 2008 R2 in order for TSEGetClientId() and other
related functions to work properly.
1.
2.
3.
4.
5.
1.
2.
3.
4.
5.
6.
Running in a Session - Refers to the tag value of the application running in the
session.
ArchestrA Graphic referencing InTouch:Tag1:
Running on the Console - Refers to the tag value of the application running on the
console.
Running in a Session - Refers to the tag value of the application running in the
session.
InTouch Graphic referencing Galaxy:InTouchViewApp_001.Tag1:
Running on the Console - Refers to the tag value of the application running on the
console.
Running in a Session - Refers to the tag value of the application running on the
console.
Notes:
Windows Vista does not support a dedicated single-node server configuration that
runs one or more databases for an Wonderware InTouch HMI system.
If a computer runs Windows Vista as part of an InTouch HMI system, it cannot be
configured to be both an InTouch HMI and ArchestrA alarm provider. The computer running
Windows Vista can be either an InTouch HMI or an ArchestrA alarm provider, but not both
simultaneously.
Wonderware InTouch HMI 10.6 does not support the following functions on these
operating systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and
SendKeys().
If
Recipe
Manager
is
started
using
the
path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator on
Windows Vista or later operating systems.
The InTouch Extensibility Toolkit might need to be started by right-clicking and
selecting Run As Administrator on Windows Vista or later operating systems to function
properly.
The onscreen keyboard options have changed for the Windows 7 and Windows
Server 2008 R2 operating systems.
Hovering to select from the Windows keyboard does not work in the Windows 7
Professional and Windows Server 2008 R2 Standard operating systems.
Wonderware
InTouch
HMI
Applications and DDE Support
2012
R2
(v10.6)
View
Windows Vista and Windows Server 2008 do not support NetDDE 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.
Windows Server 2003 and Windows XP Pro still support NetDDE.
In ArchestrA Symbols, InTouch:tagname is still a valid method of referring to an InTouch
tag on a local node.
Virtualization Support
SQL Server 2008 does not automatically create the BUILTIN\Administrators role delivered
in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application
Server 2012 R2 (v3.6) installation process will create the necessary operating system user
group (aaAdministrators) as well as the necessary SQL Server role. This automated
process will provide the rights required to allow operations within the Galaxy Repository
without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group
must be present and enabled. If you accidentally delete the aaAdministrators group from
the Windows operating system, you can run either of two options to restore it:
Run the Change Network Utility from the Windows Start menu.
Run the aaConfig SQL Utility from the Windows Start menu.
If you accidentally delete the aaAdministrators group from the SQL Server security logins,
you must run the aaConfig SQL Utility to restore it. Refer to the Wonderware Application
Server User's Guide, About ArchestrA User Accounts, for further information and
procedures about restoring the aaAdministrators group.
Component
Detailed Steps
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.
2.
3.
4.
5.
1.
2.
6.
1.
When the installation prompts you to verify your selection, you have the opportunity to customize
your installation.
If you choose InTouch Run Time Only, the following will be installed:
InTouch sample applications
Additional InTouch Supplemental Components: InTouch SPC Pro and InTouch
16 pen trend
2.
If you chose InTouch Development and Run Time, you can add the following
components:
7.
8.
1.
2.
3.
9.
4.
2.
3.
4.
Browse the installation DVD, select the ARCHESTRA.LIC file, and click Open.
The Destination Computer for Installation dialog box appears. Type the domain and computer
names.
5.
The ArchestrA License Manager copies the ARCHESTRA.LIC file to the C:\Program
Files\Common Files\ArchestrA\License folder on the selected computer.
Now you can start creating InTouch applications. The next section explains how to manage an application
from the ArchestrA IDE.
<InTouch
Application
folder
path>
C:\Documents and Settings\All Users\Application Data\ArchestrA\
<SMCLoggerStoragefilepath>.
The
default
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\
SQL Server database files of type:
.mdf
.ldf
including:
is:
Note:
Ensure that the subfolders of the listed directories are also excluded. Specify folder names accordingly if
you are using a 64-bit operating system. For example, the program file's root directory in a 64-bit operating
system is C:\Program Files (x86)\... and the application data root directory in a 32-bit operating system is
C:\ProgramData\...
3.
4.
Note: The name of the Uninstall/Change button varies depending on the Windows operating system
installed on your computer.
o
o
o
o
o
10.2
10.5
10.5 P01
You can only upgrade ArchestrA System Platform products that are already installed and you will not be
able to install new products within the ArchestrA System Platform that have an upgrade process. The
installed components that need to be upgraded are selected and disabled. You can neither clear these
check boxes nor select more components during the upgrade.
To upgrade from a previous version of the InTouch HMI
1.
2.
Insert the DVD into your DVD-ROM drive. Run setup.exe to start the set-up program.
The upgrade feature dialog box appears.
Follow the prompts to complete the upgrade.
Migrating Applications to
WonderwareInTouchHMI
Version 10.6
You can migrate applications from the following earlier versions of InTouch HMI to version 10.6:
o
o
o
o
o