Installation Instructions
Original Instructions
Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
Labels may also be on or inside the equipment to provide specific precautions.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
|
Table of Contents |
Preface |
|
Contact Rockwell Automation Technical Support ......................................................................................... |
9 |
Chapter 1 |
|
FactoryTalk View basics |
|
About FactoryTalk View SE............................................................................................................................. |
11 |
Architecture of the FactoryTalk View system.......................................................................................... |
11 |
FactoryTalk View Studio Enterprise ....................................................................................................... |
12 |
FactoryTalk View SE Server..................................................................................................................... |
12 |
FactoryTalk View SE Client...................................................................................................................... |
12 |
FactoryTalk View SE Station ................................................................................................................... |
12 |
FactoryTalk ViewPoint .............................................................................................................................. |
13 |
Stand-alone FactoryTalk Linx Server....................................................................................................... |
14 |
Stand-alone FactoryTalk Directory Server .............................................................................................. |
14 |
FactoryTalk Services Platform ........................................................................................................................ |
14 |
Connectivity ..................................................................................................................................................... |
15 |
Installation package ........................................................................................................................................ |
15 |
Chapter 2 |
|
System requirements |
|
What can I install and run on one server? ..................................................................................................... |
17 |
Review hardware requirements ..................................................................................................................... |
17 |
Review operating system requirements ....................................................................................................... |
18 |
Recommendations for application servers.............................................................................................. |
19 |
Set up the Windows domain or workgroup .................................................................................................. |
19 |
Domain controller requirements ............................................................................................................ |
20 |
Windows workgroup requirements........................................................................................................ |
20 |
About synchronizing time on application computers........................................................................... |
21 |
Set up computers with names to be used in production ............................................................................. |
21 |
Chapter 3 |
|
Pre-installation configuration |
|
Disable Windows automatic updates ........................................................................................................... |
23 |
Configure NICs and switch ports.................................................................................................................. |
23 |
Disable or uninstall third-party firewalls...................................................................................................... |
24 |
Remove Enhanced Security Configuration .................................................................................................. |
24 |
Set up Data Execution Prevention ................................................................................................................ |
24 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
3 |
Table of Contents |
|
Remove unnecessary DCOM networking protocols .................................................................................... |
25 |
Chapter 4 |
|
Install FactoryTalk View |
|
Steps................................................................................................................................................................. |
27 |
Step 1: Prepare for the installation ................................................................................................................ |
27 |
About FactoryTalk Historian Connectivity............................................................................................. |
29 |
Step 2: Start the installation........................................................................................................................... |
29 |
Step 3: Post-installation procedures.............................................................................................................. |
29 |
Specify the Network Directory server location ...................................................................................... |
30 |
Install SE clients in a distributed system...................................................................................................... |
30 |
Modify or uninstall FactoryTalk View............................................................................................................ |
31 |
Chapter 5 |
|
Activate FactoryTalk View software |
|
About FactoryTalk Activation Manager ........................................................................................................ |
33 |
What happens if FactoryTalk View is not activated? ................................................................................... |
33 |
Activation keys for FactoryTalk View software components ...................................................................... |
33 |
Sharing keys among multiple software components ............................................................................ |
34 |
Read-write versus view-only activations ................................................................................................ |
35 |
Chapter 6 |
|
Deploy applications |
|
Step 1: Move the application .......................................................................................................................... |
37 |
Step 2: Move the application’s data server files............................................................................................ |
38 |
Step 3: Renew data server shortcuts and device paths................................................................................. |
38 |
Step 4: Set up additional HMI server properties.......................................................................................... |
38 |
Specify startup components .................................................................................................................... |
39 |
Specify the startup type............................................................................................................................ |
39 |
Set up redundancy.................................................................................................................................... |
39 |
Synchronize redundant HMI servers and projects ............................................................................... |
39 |
Step 5: Set up the FactoryTalk View SE Client.............................................................................................. |
40 |
Create a FactoryTalk View SE Client file ................................................................................................ |
40 |
Lock operators into the run-time environment...................................................................................... |
41 |
Copy existing FactoryTalk View SE Client files ...................................................................................... |
41 |
Step 6: Run the FactoryTalk View SE Client .................................................................................................. |
41 |
Administer deployed applications................................................................................................................. |
42 |
4 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
|
Table of Contents |
Chapter 7 |
|
Upgrade operating network distributed applications |
|
Upgrade a non-redundant network distributed application ...................................................................... |
43 |
Example..................................................................................................................................................... |
44 |
Part 1: Prepare for the upgrade ...................................................................................................................... |
44 |
Step 1: Prepare for the upgrade ............................................................................................................... |
44 |
Log on with administrative rights .................................................................................................... |
44 |
Record the names and passwords of administrative users ............................................................ |
45 |
Perform set-up tasks on application computers.............................................................................. |
45 |
Step 2: Back up the deployed application ............................................................................................... |
45 |
Part 2: Perform upgrade of software components....................................................................................... |
45 |
Step 3: Shut down all client computers................................................................................................... |
45 |
Step 4: Upgrade the FactoryTalk Directory server ................................................................................. |
45 |
Step 5: Upgrade the HMI server .............................................................................................................. |
46 |
Step 6: Upgrade the data server............................................................................................................... |
46 |
Step 7: Upgrade the engineering workstation ....................................................................................... |
46 |
Step 8: Migrate the application ............................................................................................................... |
46 |
Open the application.......................................................................................................................... |
47 |
Verify FactoryTalk Linx shortcuts..................................................................................................... |
47 |
Test the migrated application ........................................................................................................... |
47 |
Step 9: Upgrade all run-time clients........................................................................................................ |
47 |
Step 10: Test the migrated application.................................................................................................... |
48 |
Run the application on upgraded clients ......................................................................................... |
48 |
Verify that the system is functioning as expected........................................................................... |
48 |
Upgrade a redundant network distributed application .............................................................................. |
48 |
Example..................................................................................................................................................... |
49 |
Part 1: Prepare for the upgrade ...................................................................................................................... |
49 |
Step 1: Prepare for the upgrade ............................................................................................................... |
49 |
Log on with administrative rights .................................................................................................... |
49 |
Record the names and passwords of administrative users ............................................................ |
50 |
Perform set-up tasks on application computers.............................................................................. |
50 |
Ensure that the latest application files are on the primary server ................................................. |
50 |
Step 2: Back up the application on Server #1 .......................................................................................... |
50 |
Part 2: Set up a temporary system and perform a partial upgrade............................................................. |
50 |
Step 3: Set up a temporary upgrade system ............................................................................................ |
51 |
Disable HMI and data server redundancy in the original application .......................................... |
52 |
Copy the archive file to Server #2...................................................................................................... |
52 |
Specify Server #2 as the Network Directory location ...................................................................... |
52 |
Restore the application on Server #2 as the primary server ........................................................... |
52 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
5 |
Table of Contents |
|
|
|
Specify Server #2 as the Network Directory location for Workstation #1 ..................................... |
52 |
|
Disable redundancy on Server #2 ..................................................................................................... |
53 |
|
Disable alarm and event history logging.......................................................................................... |
53 |
|
Step 4: Upgrade Server #2 ........................................................................................................................ |
53 |
|
Step 5: Upgrade Workstation #1.............................................................................................................. |
53 |
|
Step 6: Migrate the application................................................................................................................ |
54 |
|
Open the application.......................................................................................................................... |
54 |
|
Verify FactoryTalk Linx shortcuts..................................................................................................... |
54 |
|
Test the migrated application ........................................................................................................... |
54 |
|
Step 7: Upgrade selected run-time clients .............................................................................................. |
55 |
|
Install FactoryTalk View SE Client.................................................................................................... |
55 |
|
Specify Server #2 as the Network Directory location on client computers ................................... |
55 |
|
Step 8: Test the migrated application ..................................................................................................... |
55 |
|
Start Server #2 and wait for it to finish starting.............................................................................. |
56 |
|
Run the migrated application on upgraded clients......................................................................... |
56 |
|
Verify that the system is functioning as expected........................................................................... |
56 |
Part 3: Upgrade remaining clients and restore redundancy ....................................................................... |
56 |
|
|
Step 9: Upgrade remaining client computers ........................................................................................ |
56 |
|
Install FactoryTalk View SE Client.................................................................................................... |
56 |
|
Specify Server #2 as the Network Directory location on client computers ................................... |
57 |
|
Step 10: Upgrade Server #1....................................................................................................................... |
57 |
|
Install FactoryTalk View SE Server on Server #1 ............................................................................. |
57 |
|
Specify Server #2 as the Network Directory for Server #1............................................................... |
57 |
|
Step 11: Restore redundancy and finish upgrading ............................................................................... |
58 |
|
Enable HMI and data server redundancy ........................................................................................ |
58 |
|
Enable alarm and event history logging........................................................................................... |
58 |
|
Confirm the status of primary and secondary servers.................................................................... |
58 |
|
Start all run-time clients.................................................................................................................... |
59 |
Appendix A |
|
|
FactoryTalk View tools and utilities |
|
|
FactoryTalk View tools .................................................................................................................................... |
61 |
|
FactoryTalk tools............................................................................................................................................. |
62 |
|
Appendix B |
|
|
Common upgrade procedures |
|
|
Install product updates .................................................................................................................................. |
65 |
|
Update from the product ............................................................................................................................... |
65 |
|
Update from Rockwell Automation Knowledgebase ................................................................................... |
66 |
|
6 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
|
|
Table of Contents |
Appendix C |
|
Install Microsoft IIS |
|
Manually install IIS......................................................................................................................................... |
67 |
About uninstalling IIS .................................................................................................................................... |
69 |
Appendix D |
|
Use command-line installation |
|
Perform command-line installation .............................................................................................................. |
71 |
Command-line parameters............................................................................................................................. |
71 |
Examples ......................................................................................................................................................... |
74 |
Legal Notices |
|
Legal Notices ................................................................................................................................................... |
77 |
Index |
|
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
7 |
Preface
If you have questions about the product, consult the manuals, Help, or Release Notes.
You can also search for technical notes, application tips, solutions to common problems, and the latest patches from Rockwell Automation Knowledgebase http://rockwellautomation.custhelp.com.
If you cannot find the answer, contact Rockwell Automation Customer Support, using any of these methods:
•Customer support telephone: 1.888.382.1583 or 1.440.646.3434
•Local technical support phone numbers: https://rockwellautomation.custhelp.com/app/phone
•Online support: https://www.rockwellautomation.com/en-us/support.html
Support staff are available Monday to Friday from 8:00 to 17:00 local time (North America only), except on statutory holidays.
When you call, it is recommended that you be at your computer and ready to provide the following information:
•the product serial number and product key.
•the product version number.
•the type of hardware you are using.
•the names of Rockwell Automation products installed on the computer.
•the exact wording of any messages that appeared on your screen.
•a description of what happened and what you were doing when the problem occurred.
•a description of how you tried to solve the problem.
If you are running a FactoryTalk View SE network distributed application, also note:
•how many computers are participating in the network application.
•whether computers on the network are connected using a Windows domain controller or a workgroup.
•which FactoryTalk View SE components are installed on participating computers.
•which computers are running servers (the Network Directory server, HMI servers, data servers, or tag alarm and event servers), and whether the servers are set up with redundancy.
•which computers are running clients (FactoryTalk View SE Client or FactoryTalk View Studio).
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
9 |
Chapter 1
FactoryTalk View basics
FactoryTalk View, including FactoryTalk View Site Edition (SE) and FactoryTalk View Machine Edition (ME), is human-machine interface (HMI) software designed with a common look, feel, and navigation to help speed HMI application development and training time.
FactoryTalk View provides monitoring and control solutions designed to span stand-alone machine-level applications up through supervisory-level HMI applications across a network.
FactoryTalk View Site Edition (SE) is an integrated software package for developing and running human-machine interface (HMI) applications that can involve multiple users and servers, distributed over a network.
A FactoryTalk View SE system is more than the HMI server and clients. It also includes FactoryTalk Services Platform and data communication products such as FactoryTalk Linx and RSLinx Classic.
A network distributed FactoryTalk View SE system consists of several components as shown below.
FactoryTalk View SE network distributed system
This example of a distributed system includes a FactoryTalk Directory server, FactoryTalk View SE server and client, FactoryTalk Linx data server, and FactoryTalk View Studio for application development and configuration.
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
11 |
FactoryTalk View Studio Enterprise is the configuration software for developing and testing FactoryTalk View SE network distributed, network station, local station, and FactoryTalk View ME applications.
FactoryTalk View Studio is the design-time environment for FactoryTalk View that provides the editors and tools you need to develop and test network distributed, network station, and local station human-machine interface (HMI) applications. It contains editors for creating complete applications, and contains client and server software for testing the applications you create.
FactoryTalk View SE Server, also called the HMI server, stores HMI project components (for example, graphic displays) and supplies them to clients. The server also contains a database of tags, and performs historical data logging. FactoryTalk View SE Server has no user interface. Once installed, it runs as a set of headless Windows services that supply information to clients as they request it.
FactoryTalk View SE Client is software for viewing and interacting with FactoryTalk View SE local station, network station, and network distributed applications at run time. Use the FactoryTalk View SE Client Wizard to create client configuration files that can be deployed to client host computers.
FactoryTalk View SE Station is a supervisory HMI software package for enterprise solutions. SE Station is a singlecomputer HMI that can be operated in either a Local or a Network FactoryTalk Directory. There are key differences between View SE Distributed and View SE Station:
•View SE Distributed can share HMI screens and data with multiple clients.
•View SE Station does not allow sharing of HMI screens or data to other View SE Stations.
12 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
FactoryTalk View SE network station system
Several different computers, each hosting a FactoryTalk View SE network station, can use a single FactoryTalk Directory server and a single FactoryTalk Linx communication server. While each network station HMI can access the same controller data, through the shared FactoryTalk Linx server, and the same directory resources through the shared FactoryTalk directory server, they can only access their own HMI data such as graphics, macros, and datalogs.
FactoryTalk View SE local station system
A local station system can include several HMI computers, each with its own FactoryTalk Directory server and data server connection to the controllers.
FactoryTalk ViewPoint is an add-on to FactoryTalk View that provides for a fully scalable, fully animated, read-and- write view of existing Site Edition (SE) and Machine Edition (ME) web applications from a web browser.
A web application consists of graphic displays selected from the FactoryTalk View application, converted for viewing in a web browser, and then published to a FactoryTalk ViewPoint Server (also called the web server).
•For Site Edition applications, the FactoryTalk ViewPoint Server runs on a desktop or server computer.
•For Machine Edition applications, a PanelView™ Plus operator terminal functions as the server.
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
13 |
FactoryTalk Linx is a FactoryTalk Live Data server and can be enabled as a FactoryTalk Alarms and Events server. Your applications use FactoryTalk Linx to communicate with devices such as controllers and I/O scanners.
FactoryTalk Directory provides a central lookup service for a FactoryTalk system so all definitions do not have to exist in a single physical project file. References saved by FactoryTalk Directory are used by FactoryTalk-enabled products and FactoryTalk services to locate definitions when they are needed. It allows clients to locate key configuration information such as system organization, server locations, and policy information. FactoryTalk Directory provides a common address or phone book of factory resources that are shared among FactoryTalkenabled applications in a distributed system.
FactoryTalk Services Platform provides a set of common services (such as diagnostic messages, health monitoring services, and access to real-time data) for all the FactoryTalk products and applications used in a control system.
FactoryTalk Administration Console
FactoryTalk Administration Console is a stand-alone tool for developing, managing, and securing multiple FactoryTalk View applications.
FactoryTalk Directory
The FactoryTalk Directory centralizes access to system resources and names for all FactoryTalk products and components participating in an automated control system.
The FactoryTalk Network Directory manages resources for FactoryTalk View SE network applications, and the FactoryTalk Local Directory manages resources for FactoryTalk View SE local applications.
FactoryTalk Alarms and Events
FactoryTalk Alarms and Events, which installs behind the scenes during FactoryTalk View SE installation, provides system-wide alarm monitoring and control centralized at the FactoryTalk Directory.
To distribute deviceand tag-based alarms in a FactoryTalk View SE application, you can set up FactoryTalk Alarms and Events servers in the application.
FactoryTalk Security
FactoryTalk Security centralizes user authentication and authorization at the FactoryTalk Directory.
FactoryTalk Live Data
FactoryTalk Live Data manages connections between FactoryTalk products and data servers.
14 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
FactoryTalk Diagnostics
FactoryTalk Diagnostics collects and provides access to activity, status, warning, and error messages generated throughout a FactoryTalk system.
FactoryTalk Activation
FactoryTalk Activation services provide a secure, software-based system for activating Rockwell Software products and managing software activation files.
How you plan to obtain data for an application will determine which communications software you install.
You can use FactoryTalk Linx, RSLinx Classic, or other software and devices that support OPC (OLE for Process Control) communications.
Tip: FactoryTalk Linx is automatically installed for FactoryTalk View applications.
FactoryTalk Linx
FactoryTalk Linx is a communication server built around FactoryTalk technology to assist in developing and running your FactoryTalk View SE applications.
For communications with Allen-Bradley local and remote devices, particularly with Logix 5000™ controllers, FactoryTalk Linx is the recommended data communications software for FactoryTalk View applications.
FactoryTalk Linx now allows you to create redundant controller shortcuts and to perform online tasks such as uploading and downloading Logix 5000 files.
RSLinx Classic
RSLinx Classic is a 32-bit communication server that links Allen-Bradley networks and devices to Microsoft Windows applications. These range from device programming and configuration applications to HMI applications, to your own data acquisition applications using Microsoft Office, Web pages, or Visual Basic.
RSLinx Classic also incorporates advanced data optimization techniques and contains a set of diagnostics. RSLinx Classic is an OPC DA (Data Access) Compliant Server and a DDE server.
For example, install and use RSLinx Classic to serve data through DH+ (Data Highway +) networks, to support complex bridging and routing, and to support unsolicited messaging from a controller to RSLinx.
RSLinx Classic also allows you to create alias topic shortcuts, and to perform online tasks such as uploading and downloading RSLogix 5000 files.
The Setup wizard offers the following options for FactoryTalk View SE applications:
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
15 |
•Studio Enterprise
•Site Edition Server
•Site Edition Client
•Site Edition Station
•FactoryTalk ViewPoint SE
•Stand-alone FactoryTalk Linx Server
•Stand-alone FactoryTalk Directory Server
The Setup wizard offers the following options for FactoryTalk View ME applications:
•Studio for Machine Edition
•Machine Edition Station for Windows
•Stand-alone ME Transfer Utility
16 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
Chapter 2
System requirements
This chapter introduces computer and Microsoft Windows support information for a FactoryTalk View SE system, including:
•Review computer hardware requirements on page 17
•Review operating system requirements on page 18
•Set up Windows domain or workgroup on page 19
•Set up computers with names to be used in production on page 21
In a network application, it is possible for a single server computer that meets the recommended requirements to host all of the following components:
•One FactoryTalk View SE Server
•One FactoryTalk Linx data server (which can also be set up as FactoryTalk Alarms and Events device-based alarm server, or also includes the secondary data server)
•One RSLinx Classic server (or some other OPC data server)
•One FactoryTalk Alarms and Events tag-based alarm server
•The FactoryTalk Network Directory
If a network application requires multiple HMI servers, data servers, or alarm servers, to distribute the load, it is recommended that you install the necessary software and run the servers on multiple host computers.
For information about setting up redundant FactoryTalk View SE servers, see FactoryTalk View Site Edition User’s Guide.
Typically, application servers such as FactoryTalk View SE Server, FactoryTalk Alarms and Events, and FactoryTalk Linx will need to be sized with faster CPUs and more RAM than operator or engineering workstations.
You should also specify a hard drive that has enough disk space to provide virtual memory that is at least twice the size of the physical RAM.
The following is a sample specification of computer hardware to run FactoryTalk View SE applications aligned with the hardware used in product development testing.
Type |
Description |
CPU |
RAM |
|
|
|
|
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
17 |
Operator Workstation |
FactoryTalk View SE Client |
Intel® Core™ i5 Standard Power processor |
4 GB |
|
or |
|
|
|
FactoryTalk View SE Station |
|
|
|
|
|
|
Engineering Workstation |
FactoryTalk View Studio Enterprise |
Intel Core i5 Standard Power processor |
8 GB |
|
RSLinx Classic |
|
|
|
FactoryTalk Linx |
|
|
|
Studio 5000 |
|
|
Application Server |
FactoryTalk View SE Server |
Smaller systems: |
4 GB |
|
FactoryTalk View Studio Enterprise |
Intel Core i5 Standard Power processor |
|
|
FactoryTalk Alarms & Events Tag Based Server |
|
|
|
Medium to larger systems: |
8 GB |
|
|
FactoryTalk Linx Data Server with FactoryTalk |
||
|
Quad core Intel Core Xeon family |
|
|
|
Alarms and Events enabled |
|
|
|
processor |
|
|
|
|
|
The choices you make will depend in part on whether the computer is to host an application client or server. You might choose to run operator or engineering workstations in a Windows Server operating system, but that is not required.
Recommended specifications for application servers are not as flexible, because server computers are more likely to host critical components and to handle more of the processing load in a FactoryTalk View SE application.
FactoryTalk View SE is tested on operating systems installed from original Microsoft media only. FactoryTalk View SE runs on the following Windows operating systems:
•Windows® 10 Enterprise* (64-bit)
•Windows 10 Professional* (64-bit)
See the Windows Lifecycle FAQ and Windows as a Service (WaaS) topics on the Microsoft® website for details regarding servicing requirements and other important information.
•Windows 10 Semi-Annual Channel v1803, v1809, v1903, v1909, and v2004
Windows 10 Semi-Annual Channel is governed by the Microsoft Modern Lifecycle Policy. Refer to the Microsoft website for details.
•Windows 10 IoT Enterprise 2016 Long-Term Servicing Channel (LTSC)
Windows 10 Long-Term Servicing Channel is governed by the Microsoft Fixed Lifecycle Policy. Refer to the Microsoft website for details.
•Windows 10 IoT Enterprise 2016 Long-Term Servicing Branch (LTSB) Embedded**
•Windows 10 IoT Enterprise 2019 LTSC
•Windows Server® 2012 Datacenter (64-bit)
•Windows Server 2012 Standard (64-bit)
•Windows Server 2012 R2 Datacenter (64-bit)
•Windows Server 2012 R2 Standard (64-bit)
•Windows Server 2016 Datacenter* (64-bit)
•Windows Server 2016 Standard* (64-bit)
18 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
•Windows Server 2019 Datacenter LTSC (64-bit)
•Windows Server 2019 Standard LTSC (64-bit)
*For more information, see Rockwell Automation Knowledgebase Document ID: IN4493 - Windows 10 Support for the FactoryTalk Suite of Rockwell Software products and IN4718 - Windows Server 2016 Support for the FactoryTalk Suite of Rockwell Software products.
**This operating system is supported with the Allen-Bradley® 61xx family of industrial computers and CompactLogix™ 5480 family of controllers.
For computers hosting application servers (HMI servers, data servers, or Tag Alarm and Event Servers), operating system requirements depend on whether the server will support more or fewer than 10 client connections.
A client can be any of FactoryTalk View SE Client, FactoryTalk View Studio, the FactoryTalk View SE Administration Console, a FactoryTalk Historian SE connector, a FactoryTalk Transaction Manager connector, or another FactoryTalk View SE Server.
For application servers that support:
More than 10 client connections, the recommended operating systems (with the appropriate number of Client Access Licenses installed)
•Windows Server 2012 Datacenter (64-bit)
•Windows Server 2012 Standard (64-bit)
•Windows Server 2012 R2 Datacenter (64-bit)
•Windows Server 2012 R2 Standard (64-bit)
•Windows Server 2016 Datacenter (64-bit)
•Windows Server 2016 Standard (64-bit)
•Windows Server 2019 Datacenter LTSC (64-bit)
•Windows Server 2019 Standard LTSC (64-bit)
10 or fewer client connections, the minimum requirement is
•Windows 10 Enterprise
•Windows 10 Professional
Note: Do not run the primary and secondary servers in a redundant server pair on the computers that have different operating systems. For example, do not run the primary server on a Windows Server 2012 computer and the secondary server on a Windows Server 2016 computer.
The number of computers participating in a FactoryTalk View SE network application determines whether the computers can belong to a Windows domain or a workgroup.
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
19 |
Workgroups can be used only in applications that include 20 or fewer computers. Do not use Windows Workgroups with more than 20 computers, a Windows domain is recommended in that case.
For more information about setting up domains and workgroups, see the document, FactoryTalk View SE Distributed System Design Considerations, attached to Knowledgebase Document ID: IN3416 - FactoryTalk View SE Distributed System Design Considerations.
•A domain controller makes it possible to administer the network and user accounts from a central location. FactoryTalk Security, which manages centralized security services, supports Windows-linked accounts that are managed and authenticated by the Windows operating system, but have separate permissions for accessing the automation system.
•Name resolution is required for the computers to communicate with each other on the network.
•All computers participating in a single FactoryTalk system must be members of the same Windows domain.
•Do not locate the domain controller on the same computer as any FactoryTalk software. Microsoft recommends against third party software being installed on a domain controller.
For network applications consisting of more than 10 computers, the use of a domain controller is strongly recommended, but not required. The following domain controllers are supported:
•Windows Server 2012 Datacenter (64-bit)
•Windows Server 2012 Standard (64-bit)
•Windows Server 2012 R2 Datacenter (64-bit)
•Windows Server 2012 R2 Standard (64-bit)
•Windows Server 2016 Datacenter (64-bit)
•Windows Server 2016 Standard (64-bit)
•Windows Server 2019 Datacenter LTSC (64-bit)
•Windows Server 2019 Standard LTSC (64-bit)
Note: Do not install FactoryTalk Directory, FactoryTalk View SE Server, or any other application software on the same computer as the Windows domain controller. This configuration is not supported.
For network distributed applications consisting of 10 computers or fewer, FactoryTalk View SE can be used in a Windows workgroup network environment.
•Name resolution is required for the computers to communicate with each other on the network.
•Workgroups do not use a domain controller, so central network administration is not available. This means that security and network communications (for example, name resolution) must be handled at each individual computer in the workgroup.
•Each workstation in a workgroup must have the same user accounts, with the same user names and passwords on each machine, for all machines participating in a client-server environment.
•All users in a workgroup should have Administrative rights assigned to them.
20 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
•FactoryTalk Directory provides centralized security services without requiring a Windows Server and domain controller. When setting up security for applications in a Windows workgroup, it is recommended that you use the FactoryTalk Directory user accounts. This simplifies account management, by centralizing security services at the FactoryTalk Directory.
In a networked system, to ensure that time stamps on alarms, historical data, and diagnostics are accurate, it is highly recommended that time synchronization be configured on all application computers.
For more information about synchronizing application computer clocks to an authoritative time server, see
FactoryTalk View SE Design Considerations, attached to Knowledgebase Document ID: IN3416 - FactoryTalk View SE Distributed System Design Considerations.
When you install the FactoryTalk Services Platform with FactoryTalk View SE, the program creates a FactoryTalk account for the current computer, under the Local and Network FactoryTalk Directories.
As a result, if you rename the computer after installing FactoryTalk View SE or when you deploy an application, the FactoryTalk Directory will not recognize the new name.
To avoid this problem, it is recommended that you give the application client and server host computers the names they will use in a production setting, before you install the FactoryTalk View SE software.
Tip: If you must rename a computer and you encounter problems, for assistance, see Knowledgebase Document ID: BF20782 - FactoryTalk View SE: Inability to access FactoryTalk Network Directory after renaming computer (for FactoryTalk View SE network applications), or QA3873 - Renaming a PC with ME/SE Local Security (for FactoryTalk View SE local and ME applications).
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
21 |
Chapter 3
Pre-installation configuration
This chapter guides you through the steps for preparing your computer for installation of the FactoryTalk View SE product and supporting software.
Use the following checklist for preparing the computer for installation:
•Disable Windows automatic updates on page 23
•Manually configure Network Interface Cards and switch ports on page 23
•Disable or uninstall third-party firewalls on page 24
•Remove Internet Explorer Enhanced Security Configuration on page 24
•Set up Data Execution Prevention on page 24 if needed
•Remove unnecessary DCOM networking protocols on page 25
When you install Microsoft Service Pack releases and other Windows operating system updates, you introduce new software that could affect the operation of FactoryTalk View SE components on the computer.
Note: Windows updates should be disabled in all production computers. Updates can cause unexpected behaviors, including shutting down running applications and automatically restarting the computer.
The Network Interface Card (NIC) is the hardware in a computer that lets it connect to other devices on the network. A switch manages traffic on the Ethernet network. Some switches allow ports (physical connections) to be configured individually.
The link speed and duplex settings for network connections can be auto-negotiated (the device determines the best way to communicate), or manually configured (settings are hard coded).
Many NICs also offer a power-saving feature that turns off the network card if it is not being used. This setting sometimes interferes with the ability of the computer to receive data, causing errors such as wireframes, stale data, and other failures. To prevent these errors, disable power saving for your computer’s network interface cards.
For FactoryTalk View SE applications, it is recommended that you use managed switches across the control system network and that you manually configure the same link speed and duplex setting for all network connections into the managed switches.
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
23 |
It is also recommended that you manually configure the managed switch ports, using the same settings. To learn how to configure switch ports, see the product documentation provided with the switches you are using.
For an overview of best practices for connecting devices over a network, see the Ethernet Design Considerations Reference Manual document in the Rockwell Automation Literature Library. (Search for publication ENET-RM002.)
Note: If you are using unmanaged switches, the NIC settings must remain autonegotiated. Connecting an auto-negotiated device to a manually configured device can result in network communication errors and is not recommended.
FactoryTalk View SE is tested and compatible with the built-in Windows firewall. FactoryTalk View SE is not tested with third-party firewalls. We recommend that you not use third-party firewalls because they may cause unexpected results.
Before installing FactoryTalk View SE, disable or uninstall all third-party firewalls on the computer. For details, see the documentation supplied with your firewall product.
Internet Explorer Enhanced Security Configuration (ESC) is a group of default security settings for Windows Server 2012 and Windows Server 2016 that protects servers by limiting the ways users can browse Internet and Intranet Web sites on the computer.
If installed on a computer with FactoryTalk View SE software components, the Internet Explorer ESC can interfere with the ability of FactoryTalk View SE Clients to connect to application servers.
To avoid unexpected behavior, it is recommended that you remove the ESC from computers running FactoryTalk View SE.
To remove ESC in Windows Server 2012 or 2016:
1.On the Windows taskbar, select the Server Manager icon.
2.In the Server Manager Dashboard window, on the left side, click Local Server.
3.On the right side of the Local Server window, under Properties, locate IE Enhanced Security Configuration and click On.
4.In the Internet Explorer Enhanced Security Configuration dialog, select Off to turn off IE Enhanced Security for Administrators and for users, and then click OK.
Data Execution Prevention (DEP) is a Microsoft Windows security feature that is built into the operating system starting with Windows XP and Windows Server 2003. DEP is intended to protect programs and services from viruses and other security threats.
24 |
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
The DEP settings determine which programs and services are covered by DEP protection. On computers running FactoryTalk View SE components, it is recommended that DEP be turned on for essential Windows programs and services only.
To turn on DEP:
1.Open Windows Control Panel, select Control Panel Home > System and Maintenance.
2.Click System.
3.From the list of tasks on the left, select Advanced system settings.
4.In the System Properties dialog box, click the Advanced tab.
5.In the Advanced tab, under Performance, click Settings.
6.In the Performance Options dialog box, click the Data Execution Prevention tab.
7.Select the option, Turn on DEP for essential Windows programs and services only, and then click OK.
If multiple DCOM protocols are installed and configured on the computer, performance of communications in a FactoryTalk View SE system can be adversely impacted. To ensure that DCOM communications function correctly, and do not affect the performance of the system, remove all protocols other than TCP/IP.
To remove unnecessary DCOM protocols:
1.Select Start > Run.
2.In the Run dialog box, type dcomcnfg, and then click OK.
3.In the Component Services tool, expand Component Services, open the Computers folder, right-click My Computer, and then select Properties.
4.Click the Default Protocols tab. If the DCOM Protocols list shows protocols in addition to TCP/IP, remove those unnecessary protocols. For example, remove the protocol Connection-oriented SPX.
Rockwell Automation Publication VIEWSE-IN003R-EN-E - September 2020 |
25 |