9528 Um001 - en P PDF
9528 Um001 - en P PDF
9528 Um001 - en P PDF
Original Instructions
PlantPAx Virtualization
Version 4.6
Important User Information
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.
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).
Preface
Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Microsoft Operating System Software Licensing . . . . . . . . . . . . . . . . . 10
PlantPAx Virtual Image Template Catalog Numbers. . . . . . . . . . . . . 10
Build Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 1
Basics of Virtualization Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Download a Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Install a Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Copy Installer Image to DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Copy Installer Image to USB Drive . . . . . . . . . . . . . . . . . . . . . . . . . 21
Use a DVD or USB Drive to Start Server . . . . . . . . . . . . . . . . . . . . 22
Assign an IP Address to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Using a vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 2
Deploy the PlantPAx Virtual Deploy a Virtual Image Template for the First Time . . . . . . . . . . . . . 33
Image Templates Power Up the Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Install VMware Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Create a Template for Future Virtual Machine Deployments . . . . . 43
Create a vCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Create a Template from an Existing Virtual Image . . . . . . . . . . . 54
Deploy Additional Virtual Images From a Local Template. . . . . . . . 64
Convert a Virtual Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Download the vCenter Converter Standalone Software. . . . . . . 69
Install the Converter Standalone Software . . . . . . . . . . . . . . . . . . . 70
Convert a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Optional Virtual Machine Interactions . . . . . . . . . . . . . . . . . . . . . . . . . 77
Initiate Automatic Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Send Commands to Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Set Resource Pool Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Chapter 3
Server Initial Configuration Configure Microsoft Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Windows Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Administrative Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Create an Administrator User Account . . . . . . . . . . . . . . . . . . . . . 89
Configure Programs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Rename the Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Verify Ethernet Network Adapter Settings . . . . . . . . . . . . . . . . . . 94
Verify Remote Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 4
Configure the Servers Configure Server Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configure the PADC Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configure the PASS Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configure the SQL Virtual Server / Historian AF. . . . . . . . . . . . . . . 102
Install SQL Server 2012 Standard. . . . . . . . . . . . . . . . . . . . . . . . . . 102
Install Historian Asset Framework on SQL Server. . . . . . . . . . . 106
Add Local User to the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configure the Historian Virtual Server. . . . . . . . . . . . . . . . . . . . . . . . . 113
Historian Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Install SQL Server Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configure the Batch Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Configure the Asset Management Virtual Server . . . . . . . . . . . . . . . . 132
Configure the AppServ-OWS/AppServ-EWS Virtual Servers. . . . 137
Configure the VantagePoint Virtual Server . . . . . . . . . . . . . . . . . . . . . 144
Chapter 5
Workstation Common Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Configuration Configure Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Configure Programs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Standard Workstation Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 156
Rename the Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Configure Ethernet Network Adapter Settings. . . . . . . . . . . . . . 157
Configure Remote Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Adjust the Processor Scheduling Setting . . . . . . . . . . . . . . . . . . . . 158
EWS / OWS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Chapter 6
Configure PASS-C / OWS ISO Install PASS-C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Configure Windows Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Verify Ethernet Network Adapter Settings . . . . . . . . . . . . . . . . . 167
Configure System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Install SQL Server 2012 Standard. . . . . . . . . . . . . . . . . . . . . . . . . . 169
Adjust SQL Server Express Settings . . . . . . . . . . . . . . . . . . . . . . . . 174
Install Historian Asset Framework . . . . . . . . . . . . . . . . . . . . . . . . . 179
Configure the FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . 184
Configure FactoryTalk AssetCentre (FTAC) . . . . . . . . . . . . . . . 188
Configure FactoryTalk Historian . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Configure FactoryTalk VantagePoint . . . . . . . . . . . . . . . . . . . . . . 193
Install OWS ISO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Appendix A
Activation Considerations Use FactoryTalk Activations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Notes:
Define and
Install Prep Develop Operate
Procure
• Selection Guide • Virtualization User Manual • Infrastructure User Manual • Application User Manual • Verify and Troubleshoot User Manual
PROCES-SG001 9528-UM001 PROCES-UM001 PROCES-UM003 PROCES-UM004
Summary of Changes
• PlantPAx virtual image templates, PASS-C, and OWS ISO USB devices
are obtained by the following methods:
– Media - Order a physical copy of the virtual image template. End user
is responsible for the proper Microsoft® licensing.
– Electronic Software Delivery (ESD) - Download an electronic copy
of the virtual image template from the Product Compatibility and
Download Center (PCDC) website. When you download the
PASS-C or OWS ISO, you receive an ISO file that you can use to
create a bootable device.
• Virtual servers require Microsoft OS License Keys for Windows Server
operating systems.
• Virtual workstations require a Microsoft OS License Key for Windows
operating systems.
TIP Remote Desktop Services uses its own method of licensing clients
that log on to Remote Desktop Services servers. This method is
separate from licensing for the Windows Server family of operating
systems. Therefore, AppServ-OWS and AppServ-EWS Remote
Desktop Connections must receive a valid license. This license is
issued by a Remote Desktop Licensing Server before they can log on
to a Remote Desktop Session Host or Connection Broker.
For licensing of these components, contact your Microsoft
distributor.
Microsoft Operating System Each server or workstation instance that is deployed from a template, bootable
device, or ISO needs its own Microsoft operating system license and Rockwell
Software Licensing Automation software licenses.
The end user is responsible for properly licensing a Microsoft OS for each
template deployed. Additional licenses can be purchased from your Microsoft
distributor.
PlantPAx Virtual Image Table 1 lists the catalog numbers for PlantPAx virtual image templates.
Template Catalog Numbers
Table 1 - Virtual Image Templates on USB Devices
Virtual Template Cat. No. Description
PASS 9528-PASSVTENM USB device contains the virtual image template for the PASS. The end user is responsible for acquiring the appropriate Microsoft OS
license for Server 2016. All required Rockwell Automation software is pre-installed but not activated.
EWS 9528-EWSVTENM USB device contains the virtual image template for the EWS. The end user is responsible for acquiring the appropriate Microsoft OS
license for Windows 10. All required Rockwell Automation software is pre-installed but not activated.
OWS 9528-OWSVTENM USB device contains the virtual image template for the OWS. The end use is responsible for acquiring the appropriate Microsoft OS
license for Windows 10. All required Rockwell Automation software is pre-installed but not activated.
AppServ-OWS, AppServ-EWS 9528-APPXWSENM USB device contains the virtual image template for AppServ-OWS and AppServ-EWS. The end user is responsible for acquiring the
appropriate Microsoft OS license for Server 2016. All required Rockwell Automation software is pre-installed but not activated. You also
must purchase the appropriate Windows CAL from a Microsoft distributor.
IMPORTANT: Each client needs an RDS CAL license.
AppServ-Info (Historian) 9528-APPHISENM USB device contains the virtual image template for AppServ-Info (Historian). The end user is responsible for acquiring the appropriate
Microsoft OS license for Server 2016. All required Rockwell Automation software is pre-installed but not activated.
AppServ-Asset 9528-APPASMENM USB device contains the virtual image template for AppServ-Asset. The end user is responsible for acquiring the appropriate Microsoft
OS license for Server 2016. All required Rockwell Automation software is pre-installed but not activated.
AppServ-Info (SQL) 9528-APPSQLENM USB device contains the virtual image template for AppServ-Info (SQL). The end user is responsible for acquiring both the appropriate
Microsoft OS license for Server 2016 and Microsoft SQL server.
AppServ-Info (VantagePoint) 9528-APPVTPENM USB device contains the virtual image template for AppServ-Info (VantagePoint). The end user is responsible for acquiring the
appropriate Microsoft OS license for Server 2016. Most required Rockwell Automation software is pre-installed but not activated. The
FactoryTalk VantagePoint software is not pre-installed for your convenience. For details, see the PlantPAx Virtualization User Manual,
publication 9528-UM001.
AppServ-Batch 9528-APPBATENM USB device contains the virtual image template for AppServ-Batch. The end user is responsible for acquiring the appropriate Microsoft
OS license for Server 2016. Most required Rockwell Automation software is pre-installed but not activated. The FactoryTalk Batch
software is not pre-installed.
Domain controller 9528-PADCVTENM USB device contains the virtual image template for a Domain controller. The end user is responsible for acquiring the appropriate
Microsoft OS license for Server 2016. You also must purchase the appropriate Windows CAL from a Microsoft distributor.
Build Details Table 3 lists the system build details for each PlantPAx virtual image template.
Table 3 - System and Software Requirements
Element Category Description
Process Automation Operating system Microsoft® Windows Server 2016 Standard
System Server (PASS)
Rockwell Automation® software • FactoryTalk® Services Platform
– FactoryTalk Services platform software, version 6.11.00
– FactoryTalk Activation Manager software, version 4.03.03
– FactoryTalk Linx software, version 6.11.00
• FactoryTalk View Site Edition Client software, version 11.00.00
• FactoryTalk View Site Edition Server software, version 11.00.00
• FactoryTalk View Studio Enterprise software, version 11.00.00
• FactoryTalk Alarm and Event software, version 6.11.00
• FactoryTalk Diagnostics software, version 6.11.00
• FactoryTalk Historian SE Live Data Interface, version 6.00.00
• Rockwell Automation ® Windows Firewall Configuration Utility, version 1.00.12
Engineering Operating system Microsoft Windows 10
Workstation (EWS)
Rockwell Automation software • FactoryTalk Services Platform
– FactoryTalk Services Platform software, version 6.11.00
– FactoryTalk Linx software, version 6.11.00
– RSLinx® Classic software, version 4.11.00
– FactoryTalk Activation Manager software, version 4.03.03
• FactoryTalk View Site Edition Client software, version 11.00.00
• FactoryTalk View Site Edition Server software, version 11.00.00
• FactoryTalk View Studio Enterprise software, version 11.00.00
• FactoryTalk Alarm and Event software, version 6.11.00
• FactoryTalk Diagnostics software, version 6.11.00
• RSLogix 5000® Professional software, versions 20.05.00
• Studio 5000 Logix Designer ® application, versions 31.01.00, 24.02.00
• Studio 5000 Architect Software, version 4.00.00
• RSNetWorx™
– RSNetWorx for EtherNet/IP™ software, version 28.00.00
– RSNetWorx for ControlNet® software, version 28.00.00
– RSNetWorx for DeviceNet® software, version 28.00.00
• FactoryTalk AssetCentre
– FactoryTalk AssetCentre Client software, version 9.00.00
• FactoryTalk Historian SE Management Tools, version 6.00.00
• Studio 5000® Logix Emulate™, version 31.01.00
• ControlFLASH Plus™ software, version 2.00.00
• ControlFLASH software, version 15.01.00
• Rockwell Automation Windows Firewall Configuration Utility, version 1.00.12
Additional third-party software • LOOP-PRO TUNER (Rockwell Automation Edition) software, version 1.9
• Microsoft SQL Server 2012 SP4 Management Tools
• Microsoft SQL Server 2012 SP4 Client Connectivity
Operator Workstation Operating system Microsoft Windows 10
(OWS)
Rockwell Automation software • FactoryTalk Services Platform
– FactoryTalk Services Platform software, version 6.11.00
– FactoryTalk Linx software, version 6.11.00
– RSLinx Classic software, version 4.11.00
– FactoryTalk Activation Manager software, version 4.03.03
• FactoryTalk Diagnostics software, version 6.11.00
• FactoryTalk View Site Edition Client software, version 11.00.00
• FactoryTalk Alarm and Event software, version 6.11.00
• FactoryTalk AssetCentre Client software, version 9.00.000
• Rockwell Automation Windows Firewall Configuration Utility, version 1.00.12
Process Automation Operating system Microsoft Windows Server 2016 Standard
Domain Controller
(PADC)
Table 4 lists the system build details for PlantPAx USB devices.
Table 4 - Build Details for USB Devices
Element Category Description
PASS-C (consolidated) Operating system Microsoft Windows Server 2016 Standard
Rockwell Automation software • FactoryTalk Services Platform
– FactoryTalk Services platform software, version 6.11.00
– FactoryTalk Activation manager software, version 4.03.03
– FactoryTalk Linx software, version 6.11.00
– RSLinx Classic software, version 4.11.00
• FactoryTalk View Site Edition Client software, version 11.00.00
• FactoryTalk View Site Edition Server software, version 11.00.00
• FactoryTalk View Studio Enterprise software, version 11.00.00
• FactoryTalk Alarm and Event software, version 6.11.00
• FactoryTalk Diagnostics software, version 6.11.00
• FactoryTalk Historian SE Live Data Interface, version 6.00.00
• Rockwell Automation Windows Firewall Configuration Utility, version 1.00.12
• FactoryTalk Historian SE software, version 6.00.00
• FactoryTalk AssetCentre Server, version 9.00.00
• FactoryTalk AssetCentre Client, version 9.00.00
• Studio 5000 Logix Designer®, version 31.01.00
• Studio 5000 Logix Designer, version 24.02.00
• RSLogix 5000, version 20.05.00
• VantagePoint® System Server, version 8.10.00
• ControlFLASH software, version 15.01.00
• ControlFLASH Plus software, version 2.00.00
Additional software Microsoft SQL Server Express 2012 SP4 Advanced (includes Management Studio)
Operator Workstation Operating system Microsoft Windows 10
(OWS ISO)
Rockwell Automation software • FactoryTalk Services Platform
– FactoryTalk Services platform software, version 6.11.00
– FactoryTalk Linx software, version 6.11.00
– RSLinx Classic software, version 4.11.00
– FactoryTalk Activation manager software, version 4.03.03
• FactoryTalk Diagnostics software, version 6.11.00
• FactoryTalk View Site Edition Client software, version 11.00.00
• FactoryTalk Alarm and Event software, version 6.11.00
• FactoryTalk AssetCentre Client, version 9.00.00
• Rockwell Automation Windows Firewall Configuration Utility, version 1.00.12
Additional Resources These documents contain information about related products from
Rockwell Automation that can provide additional guidance when deploying
the virtual image templates.
Resource Description
PlantPAx Distributed Control System Reference Manual, Details the application rules for implementing a
publication PROCES-RM001 PlantPAx system.
PlantPAx Distributed Control System Selection Guide, Provides procurement information for a
publication PROCES-SG001 PlantPAx system.
Product Certifications website, http://www.ab.com Provides declarations of conformity, certificates, and
other certification details.
FactoryTalk Historian SE Installation and Configuration Provides information on how to install, secure,
Guide, publication HSE-IN025 configure, use, and troubleshoot
FactoryTalk Historian SE.
PlantPAx Distributed Control System Infrastructure Provides screen facsimiles and step-by-step
Configuration, publication PROCES-UM001 procedures to configure infrastructure components for
your system requirements.
PlantPAx Distributed Control System Application Provides the steps necessary to start development of
Configuration, publication PROCES-UM003 your PlantPAx Distributed Control System.
Knowledgebase Answer ID 32715 - Cannot add/change Provides details about the problem of adding/
pens in trend from SE client on Terminal Server at changing pens in trend from SE client on Terminal
https://rockwellautomation.custhelp.com/app/answers/ Services.
detail/a_id/32715
You must have a TechConnectSM license to view this
document.
Knowledgebase Answer ID 496679 - FAQ: FactoryTalk Provides information on how to use the FactoryTalk
Historian SE: MDB to AF Preparation Wizard at Historian SE MDB to AF Preparation wizard.
https://rockwellautomation.custhelp.com/app/answers/
detail/a_id/496679
You must have a TechConnect? license to view this
document.
Knowledgebase Answer ID 567658 - Using FactoryTalk Provides information on how to use FactoryTalk View
View SE with Windows 2008 R2 Remote Desktop Services - SE with Microsoft Windows 2008 R2 Remote Desktop
Getting Started white paper at Services.
https://rockwellautomation.custhelp.com/app/answers/
detail/a_id/567658
You must have a TechConnect license to view this
document.
Knowledgebase Answer ID 60585 - FactoryTalk Historian Provides information on how to implement a
SE Collective Manager Error - Error Writing Server at collective for FactoryTalk SE Historian.
https://rockwellautomation.custhelp.com/app/answers/
detail/a_id/60585
You must have a TechConnect license to view this
document.
Notes:
Basics of Virtualization
The virtual image templates help to reduce validation costs and initial
engineering time, enhance scalability, simplify upgrades, and patch management.
Only one copy of the virtual image templates is needed for a project.
Flexibility and ease of deployment are key when designing a virtual infrastructure.
Both intangibles are a part of the PlantPAx system.
Figure 1 contains the topics that are described in this chapter. See the page
number or click the links for quick access to specific information.
Start
Download a Hypervisor
See page 19
Install a Hypervisor
See page 20
Download a Hypervisor
IMPORTANT The following procedures apply only to virtual templates. Skip to Chapter 6 if
you are deploying a PASS-C or OWS ISO
TIP We are using VMware vSphere as an example, you can use other hypervisors
for this procedure.
Install a Hypervisor This section describes how to install the VMware vSphere hypervisor to a host
server. The hypervisor, which is also known as ESXi, is used to manage the
resources of your server to enable deployment of virtual images. To install the
hypervisor on your server, we recommend that you copy the installer image (.iso)
to a DVD. If desired, you can also copy the installer image (.iso) to a USB drive
(at least 1 GB).
TIP We are using VMware vSphere Hypervisor as an example, but you can use
other hypervisors with this procedure.
Complete these steps to copy the hypervisor installer image (.iso) to a DVD.
1. Right-click the downloaded installer image and choose Burn disk image.
2. Select the DVD drive to write the data, and click Burn.
IMPORTANT Before starting this procedure, make sure that the USB drive has enough space
on it to hold the 'ISO' file.
Complete these steps to copy the hypervisor installer image (.iso) to a USB drive.
When you start the server, make sure to choose the DVD or USB drive that
contains the installer image as the booting address. Complete these steps to install
the ESXi (hypervisor).
1. Insert the DVD or USB drive into the host physical server.
2. Choose the optional booting address during the server startup.
5. Select the disk to install the vSphere Hypervisor and press Enter
to continue.
7. Type a root password, retype the password, and press Enter to continue.
A message appears when the system scans for information. This scan can
take a few minutes.
8. Press F11 to Install.
You must assign an IP address to the host so that it is on the desired network and
can communicate with the client workstations. For example, you can deploy a
virtual image template in this server remotely from another workstation on the
same network.
TIP For the screens in this section, use the arrow keys on your keyboard to move
between the fields on the pages.
Using a vSphere Web Client After the ESXi (hypervisor) is installed, the simplest way to connect directly to
one host server is with a vSphere Web Client. If you have multiple ESXi hosts, we
recommend that you configure a vCenter Server that offers additional
functionality. Through the vSphere Web Client, you can add, delete, and manage
the virtual machines on your infrastructure.
TIP This section describes how to use a web browser for vSphere software, version
6.0 or later. The following steps are similar for the vSphere Client application,
which you use to interface ESXi 6.0 or earlier.
This section explains how to activate your vSphere license. The vSphere Web
Client resides on a computer that is being used to connect to the server where the
virtual templates are deployed. You can use any web browser with these steps. A
Firefox browser is shown with our examples.
To use a vSphere Web Client, for the first time, complete these steps.
1. Open a web browser and type the IP address that you created for the
hypervisor host.
Use the IP address that you entered for step 7 on page 25.
A security warning appears the first time that you connect to the ESXi
host server.
2. Click Advanced.
9. Click the Licensing tab, then choose Assign license under Actions.
10. Type your license key and click Check license.
A virtual machine acts independently and has its own resource allocation from
the host. You interact with virtual machines as if they are on a dedicated
workstation with their own physical resources.
Figure 2 contains the topics that are described in this chapter. See the page
number or click the links for quick access to specific information.
Start
Optional VM Interactions
See page 77
See
Chapter 3
Deploy a Virtual Image This section describes how to deploy a virtual image for the first time. The virtual
image can be deployed from the USB drive that is shipped or from a storage
Template for the First Time location on a workstation. This workstation is the computer that you are using to
connect to the server you plan to use as the host server. The deployment
procedure is applicable to all PlantPAx virtual templates.
This procedure must be followed every time a virtual image template is deployed
for the first time into your system.
IMPORTANT If you plan to deploy a domain controller, it is recommended that the domain
controller is the first element that is deployed in the system. The PADC
template facilitates future activities, such as creating your own virtual image
templates and deploying virtual images to your system at your convenience.
To deploy a virtual image template for the first time, complete these steps.
TIP Before deploying a virtual image from a virtual image template, we advise you
to copy the virtual image template to your local hard disk drive. Copy the
template to save time during the deployment process.
1. Open a web browser and type the IP address that you created for the
host server.
2. Type the user name and password for the EXSi host, and click Log in.
4. Click ‘Deploy a virtual machine from an OVF or OVA file’ and click Next.
6. Select the datastore for your configuration and disk files storage.
7. Click Next.
IMPORTANT There are two main formats for storing virtual images: OVF (open
virtual format) and OVA (open virtual appliance). Our templates are for
appliances, which are self-contained virtual system elements. VMware
software labels the wizard ‘OVF Template’ but ignore because your
PlantPAx Virtual Image Templates in the OVA format are suitable for
this procedure.
8. Use defaults for network mapping and disk provisioning, and click ‘Power
on automatically.’
9. Click Next.
To power up a virtual image template for the first time, complete these steps.
1. Open a web browser and type the IP address that you created for the
host server.
2. Type the user name and password for the local host, and click Log in.
IMPORTANT When powering up the virtual machine for the first time, the screen can remain
black for several minutes.
The VMware vSphere Client software has better graphic performance with the
VMware Tools SVGA driver installed. The VMware Tools package also supports
required shared folders and drag-and-drop features.
IMPORTANT Images that are shown in this section are VMware vSphere software,
version 6.5.
1. Open a web browser and type the IP address that you created for the
host server.
2. Type the user name and password for the local host, and click Log in.
The VMware ESXi window appears.
3. From the Navigator in the left pane, right-click the virtual machine in
which you want to update or install VMware Tools.
5. Open Windows Explorer on the virtual machine image that you want to
install VMware Tools.
8. When the VMware Tools Setup Welcome window appears, click Next
to continue.
9. On the setup screen, click Complete and then click Next to continue.
11. When the VMware Tools Setup popup window appears, click Finish.
12. To restart your virtual image and complete the VMware Tools Install
Process, click Yes.
Create a Template for Future This section shows how to create a template within a datacenter by using a
previously deployed virtual image. A virtual machine is cloned, and the clone
Virtual Machine becomes a template. This template can be used to deploy other images. You can
Deployments store the original template for safekeeping in case you modify your templates.
IMPORTANT A datacenter is the primary container of inventory objects such as hosts and
virtual machines. From the datacenter, you can add and organize inventory
objects. Typically you add hosts, folders, and clusters to a datacenter.
A vCenter server can contain multiple datacenters. Larger organizations can
use multiple datacenters to represent organizational units in their enterprise.
Inventory objects can interact within datacenters, but interaction across
datacenters is limited. For example, you can move a virtual machine with
vMotion technology across hosts within a datacenter but not to a host in
another datacenter.
Before cloning the virtual image, configure a vCenter server. A vCenter server
provides centralized management of virtualized hosts and virtual machines from
one console. It gives administrators visibility into the configuration of the critical
components of a virtual infrastructure—all from one place.
IMPORTANT The workstation that you use to connect to and configure your host server can
act as your vCenter server.
On the workstation you use to manage your virtual appliances (templates and
machines), complete these steps.
TIP The steps to download the vCenter server software are similar to the
steps used to download Hypervisor, see Download a Hypervisor on
page 19.
2. Start the vCenter Server Appliance 6.5 installer. Choose vCenter Server
6.5 appliance>vcsa-ui-installer>win32>installer.exe.
5. Check I accept the terms of the license agreement and then click Next.
7. Enter the ESXi host information of the location where the vCenter server
appliance is deployed, and enter the host credentials. Click Next
to continue.
9. Enter the name for the appliance and set the root password. Click Next to
continue.
10. Select the deployment size for your environment. Click Next to continue.
11. Select the datastore where the VCSA appliance will be stored. Click Next
to continue.
12. Configure the networking for the VCSA appliance. Click Next to
continue.
IMPORTANT Put the IP address that is used in both the DNS forward and reverse lookup
zones.
13. Verify that the configuration is correct on the summary dialog box and
then click Finish.
16. Select the Time synchronization mode and enable SSH access.
18. Configure Single Sign On (SSO) by typing a domain name, password and
site name. Click Next to continue.
20. Verify that the configuration is correct on the summary dialog box and
then click Finish.
This procedure shows you how to make a copy of a virtual image and turn it into
a template for future deployments.
IMPORTANT The images that are shown in this section are VMware vSphere Client software,
version 6.5.
3. Enter the Username and Password. Use the User name and password that
you created for the vCenter Server in step 18 on page 52. Click Login.
IMPORTANT The user name consists of the vCenter Single Sign-On user name plus '@' plus
the Domain name.
In our example, the user name is '[email protected]'.
Create a Datacenter
The Datacenter is the primary container of inventory objects such as hosts and
virtual machines.
1. From The VMware vSphere Web Client dialog box, highlight your
vCenter Server, and click 'Create Datacenter'.
2. When prompted, type a name for the new datacenter (‘New Datacenter’ in
our example) and click OK.
Add a Host
The host is the virtual machine where the virtual image is deployed.
1. The New Datacenter is added under the vCenter Server. Highlight the
New Datacenter and click 'Add a Host' to add a host server.
2. The 'Add Host' window appears. In the Name and location step, type the
host IP address, and click 'Next'. See step 7 on page 47.
3. In the 'Connection Settings' step, type the User name and Password. The
Username and Password were created in step 7 on page 47. Click 'Next'.
4. Verify that the settings are correct on the Host summary dialog box and
then click Next.
5. Assign a License.
a. If using the trial license that came with the VMware vSphere
Hypervisor, click the default Evaluation License and click next.
7. In the VM location step, select the Datacenter that you created, and click
Next.
IMPORTANT Because a vCenter server can manage multiple host servers, make sure to
create/select the proper datacenter and host server where the virtual machines
reside.
These organizational features help improve your understanding of your
infrastructure and help with the management of servers.
8. Verify that the configuration is correct in the Ready to complete dialog box
and then click Finish.
9. The Host is added under the datacenter. The Navigator section of the
vSphere Web Client window now includes the vCenter server
(VRTXvCenter), the Datacenter (New Datacenter), and the Host
(172.18.1.13) as shown in the following image.
1. Right-click the virtual image that you want to clone and choose
Clone>Clone to Template.
2. Type a name for the new template, select a location, and click Next.
3. Select a host location to store the new template and click Next.
4. Select the disk format, storage policy, and the hypervisor that manages the
resources of the server that hosts this template. See Table 5 for disk format
options. Click Next.
Deploy Additional Virtual When you have virtual image templates loaded into your datacenter, you can
deploy any number of virtual images from those templates. Additional
Images From a Local deployments can be performed from these new templates.
Template
Complete these steps to deploy additional virtual images.
3. Enter the Username and Password. Use the User name and password that
you created for the vCenter Server in step 18 on page 52. Click Login.
IMPORTANT The user name consists of the vCenter Single Sign-On user name plus '@' plus
the Domain name.
In our example, the user name is '[email protected]'.
4. From the left side of the vSphere Web Client window, highlight your
vCenter Server, then select the 'VMs' tab.
5. Select the 'VM Templates in Folders' tab, then right-click the template that
you plan to deploy to a New Virtual Image.
8. In the Inventory Location box, select a location to store the new virtual
machine and click Next.
IMPORTANT When you clone a virtual machine or deploy a virtual machine from a
template, you can customize the guest operating system of the virtual
machine. Customizing guest operating systems can help prevent
conflicts if virtual machines with identical settings are deployed.
You can specify the customization settings when you launch the Guest
Customization wizard during the cloning or deployment process
11. The 'Ready to Complete' step appears. Select one of the following to verify
settings:
• If there is incorrect information, click Back to correct the information.
• If the information is correct, click Finish.
IMPORTANT The process of deploying a virtual machine from a template can take up to 30
minutes. The time that is required is largely dependent on the size of the hard
disk drive of the template you are using to deploy a virtual machine.
12. You can view the status of the task by finding 'Clone virtual machine' in
Recent Tasks at the bottom of the window. When the status = Completed,
the cloning is finished.
Convert a Virtual Image This section describes how to use the vCenter Converter Standalone tool as an
alternative to deploy a virtual machine into your host server. The tool is not
required for this procedure but it is a free tool that lets you deploy virtual
machines into your host server.
If you do not own a copy of VMware Workstation or vSphere Client and you
wish to deploy a virtual machine into your host server, you must install the
vCenter Converter Standalone software. Install the software on the workstation
you use to connect to and configure your host server. If you intend to use vCenter
Converter Standalone software to create a virtual image of a physical computer,
you must install the tool on the machine that you are virtualizing. For more
information on how to use the tool for different procedures,
see http://www.vmware.com/products/converter.
2. Click Next.
3. Click ‘I agree to the terms in the License Agreement’, and click Next.
The vCenter Converter Standalone software installs VMware Tools to let you
customize the guest operating system. For example, you can change the host name
or network settings.
3. Click browse to navigate to the location of the virtual image that you want
to convert, choose the file, and click Next.
4. On the Destination System window, type the IP address, User name, and
Password of the server where the virtual machine is being deployed to after
conversion.
5. Click Next.
7. Type the name that you want for this virtual machine and click Next.
9. Select the virtual machine version from the pull-down, and click Next.
Optional Virtual Machine To help expedite the use of your virtual machines, consider the following options:
Interactions • Initiate Automatic Startup on page 77
• Set Resource Pool Priority on page 83
To program the host server to start your virtual machines automatically, complete
these steps.
3. Enter the Username and Password. Use the User name and password that
you created for the vCenter Server in step 18 on page 52. Click Login.
IMPORTANT The user name consists of the vCenter Single Sign-On user name plus '@' plus
the Domain name.
In our example, the user name is '[email protected]'.
4. Select the Host Server, then select the Configure Tab, then select VM
Startup/Shutdown. On the VM Startup/Shutdown window, click 'Edit'.
5. Check 'Automatically start and stop virtual machines with the system'.
Click the (Up Arrow) to move the desired Virtual Machine host server
from the Manual Startup category up to the Automatic Startup category.
You can select additional images and click the Up Arrow or Down Arrow
to determine the startup order as shown in the following image. A
sequential number order appears.
6. When you are satisfied with the Startup order, click OK.
7. The Virtual Machines are now configured for Automatic Startup as shown
in the following screen capture.
IMPORTANT Following is the recommended start-up order for the typical system
elements of a virtual PlantPAx system.
1. Process Automation Domain Controller - PADC
2. SQL server - AppServ-Info (SQL)
3. Process Automation System Server - PASS
4. Engineering Workstation Application Server (AppServ-EWS)
5. Redundant Process Automation System Server - PASS
6. Batch Management Server (AppServ-Batch)
7. Operator Workstation Application Server (AppServ-OWS)
8. Historian server - AppServ-Info (Historian)
9. VantagePoint server - AppServ-Info (VantagePoint)
10. Asset Management server (AppServ-Asset)
11. Level 3 devices and computers
You can also send shutdown and restart commands directly to the host server via
the vSphere Web Client.
1. On the vSphere Web Client window, right-click a host server and choose
either Shut Down or Reboot.
2. In the confirmation window, type a reason for the Shut Down or Reboot
and click OK or Cancel.
You can set the priority of the resource allocation that your virtual machine
requires from the host server. The allocation of CPU and memory resources
depends on performance needs. A virtual machine can be grouped for High
Performance, Normal Performance, or Low Performance depending on its
performance needs.
IMPORTANT For more information and resource pool priority recommendations for servers
and workstation, see Resource Pool Allocation in the PlantPAx System
Reference Manual, publication PROCES-RM001.
3. Type the User name and Password. Use the User name and password that
you created for the vCenter Server.
4. Click Login.
IMPORTANT The user name consists of the vCenter Single Sign-On user name plus '@' plus
the Domain name.
In our example, the user name is '[email protected]'.
6. Type the priority in the Name text box. For example, High Performance.
7. Click the Shares pull-down menu and select 'High' for the CPU and
Memory Resources categories.
8. Click OK.
9. Repeat step 1 through step 7 for each virtual machine depending if the
priority is High Performance, Normal Performance, or Low Performance.
The priority types appear in the tree for the host server.
10. Drag and drop virtual machines to the Resource Pool that matches the
needs and intended use. Settings for that resource pool are assigned.
Notes:
If you plan to deploy a domain controller, we recommend that you configure the
domain controller before any other system element.
Virtual templates are available for the following PlantPAx server system elements:
• Process Automation Domain Controller - PADC
• Process Automation System Server - PASS
• SQL Server - AppServ-Info (SQL)
• FactoryTalk® Historian Server - AppServ-Info (Historian)
• FactoryTalk Batch Management Server - AppServ-Batch
• FactoryTalk Asset Management Server - AppServ-Asset
• Operator Workstation Application Server - AppServ-OWS
• Engineer Workstation Application Server - AppServ-EWS
• FactoryTalk VantagePoint® Server - AppServ-Info (VantagePoint)
The required Rockwell Automation® software for each virtual server is included
and pre-installed in the virtual image templates, but not activated. See
Activation Considerations on page 201 for activation procedures.
IMPORTANT Perform this procedure on all servers before configuring the system elements.
If you already own individual product activations, these activations can also be
used to activate the virtual image templates.
Configure Microsoft Complete these steps to configure Microsoft Windows Server 2016 settings for
your virtual servers.
Windows Server
Windows Server
1. From a web browser, enter the IP address of the computer where your host
server is installed.
2. Type the user name and password for the host server, and click Login. The
VMware ESXi window appears.
3. From the Navigator in the left pane, right-click the virtual machine that
you want to configure, and select Power>Power On.
4. Right-click the virtual machine again, and select Console>Launch Remote
Console.
5. Choose the appropriate location, language, and keyboard settings and click
Next.
6. On the EULA dialog box, read the license terms and click ‘Accept’.
7. Type a password for administrator, retype the password to verify, and click
‘Finish.’
IMPORTANT Even though ‘Press Ctrl + Alt + Delete …’ is displayed on the screen, you must
press Ctrl + Alt + Insert to access the virtual machine. The sequence 'Ctrl + Alt
+ Del' is reserved for the terminal from where you connect to the server that
hosts the virtual machine.
8. Press Ctrl+Alt+Insert.
9. Type the Administrator password that you created and Press Enter.
If you see the Other-User logon, type 'Administrator', type the
administrator password that you created and Press Enter. Wait until you
see the network message in the following step.
Administrative Server The following procedures help manage who has access to the server and login
privileges. Complete these procedures on all virtual servers to be deployed.
Configuration
We suggest that you create an Administrator user account for each user that
requires administrative privileges. This safeguards server corruption by restricting
access to the default administrative account, and creates a backup of critical
system information. Each user can be delegated a separate user account with
password protection.
Complete the steps on the system computers to group folders under ‘Programs’
on the taskbar. When complete, you can access Windows and Rockwell Software®
folders by clicking the symbol next to Programs on the task bar.
The result is a custom menu with easy access to Rockwell Software conveniently
located on the Windows taskbar.
5. Click Domain, type the name of your domain, and click OK.
IMPORTANT We recommend that you restart your computer so that these changes take
effect.
Complete these steps to configure remote settings for a virtual image to allow
remote connections to this computer.
3. In the Remote Assistance Section at the top of the window, verify that the
checkbox to ‘Allow Remote Assistance connections to this computer’ is
not checked.
4. In the Remote Desktop Section, click the ‘Allow remote connections to
this computer’ box.
5. Click OK.
Complete these steps to adjust processor scheduling for best performance in the
Windows Server operating system.
If you plan to deploy a domain controller, we recommend that you configure the
domain controller before any other system element.
Virtual templates are available for the following PlantPAx server system elements:
• Process Automation Domain Controller - PADC
• Process Automation System Server - PASS
• SQL Server - AppServ-Info (SQL)
• FactoryTalk® Historian Server - AppServ-Info (Historian)
• FactoryTalk Batch Management Server - AppServ-Batch
• FactoryTalk Asset Management Server - AppServ-Asset
• Operator Workstation Application Server - AppServ-OWS
• Engineer Workstation Application Server - AppServ-EWS
• FactoryTalk VantagePoint® Server - AppServ-Info (VantagePoint)
The required Rockwell Automation® software for each virtual server is included
and pre-installed in the virtual image templates, but not activated. See
Activation Considerations on page 201 for activation procedures.
Configure Server Templates Figure 3 contains the topics for the virtual servers that are described in this
section. The PADC server must be deployed first.
See the page number or click the links for quick access to specific information.
Start
Configure the PADC Virtual Server Configure the Batch Virtual Server
See page 99 See page 124
See Appendix A
Configure the PADC Virtual A domain controller is a server that responds to security authentication requests
(logging in, checking permissions, and so forth) within the Windows server
Server domain. A domain grants you access to a number of network resources (such as
applications and printers) with the use of one user name and password
combination.
The PlantPAx system uses a domain controller to store user account information,
authenticate users, enforce security policies and best networking practices such as
automatic network address assignment. Domain authentication is recommended,
whether it’s an existing domain or a new one.
Once you have completed these tasks, see the PlantPAx Distributed Control
System Infrastructure Configuration User Manual, publication
PROCES-UM001, for domain controller configuration procedures.
Configure the PASS Virtual The Process Automation System Server (PASS) hosts essential software
components to run your system. The data, human-interface (HMI), and alarm
Server servers reside in the PASS.
You must designate a PASS server for the FactoryTalk Directory. The directory
centralizes the settings and administration of Rockwell Automation software
components across multiple virtual machines.
The required Rockwell Automation software for the PASS system element is
included and pre-installed in the PASS virtual image template, but not activated.
To activate each PASS image, purchase an activation license. See Table on
page 10 for catalog numbers.
The following procedure describes how to designate the PASS server as the host
of the FactoryTalk Directory. The directory server manages applications that can
exist on multiple clients and servers on separate virtual machines on the
PlantPAx system.
IMPORTANT You must have a user name and password with Administrator privileges to
specify the FactoryTalk Directory location. Use the same user name and
password for all FactoryTalk installations on the PlantPAx system.
1. On the virtual image desktop, click the Programs icon and choose
Rockwell Software>FactoryTalk Tools>FactoryTalk Directory
Configuration Wizard.
2. Type your password and click Next.
3. In the FactoryTalk Directory Configuration Wizard page, check the
following:
• Configure the FactoryTalk Network Directory
• Configure the FactoryTalk Local Directory
4. Click Next.
Configuring the local and network FactoryTalk Directories can take up to
30 seconds to process the request.
IMPORTANT In the next step, you are creating the credentials as you type them in.
Remember these credentials for later use. Use the Administrator User
Account credentials that were created in Create an Administrator User
Account on page 89.
Deleting the old computer name keeps the FactoryTalk Directory up-to-date
with current computer names. This deletion also makes sure that applications do
not attempt to communicate with computers that are no longer in the
FactoryTalk Directory.
4. Right-click all computer names except the one you created and choose
Delete.
5. Click Yes when a message appears and asks you to verify that you want to
delete the computer name.
6. If you use the Local Directory, repeat step 1 through step 5 and make sure
to select Local in step 2.
7. When finished, exit the FactoryTalk Administrator console.
8. Restart your computer.
Configure the SQL Virtual The AppServ-Info (SQL) server is a database that is used to store Process data for
FactoryTalk AssetCentre, FactoryTalk VantagePoint, and FactoryTalk Batch
Server / Historian AF software programs. The FactoryTalk Alarm and Event server also uses the SQL
database.
IMPORTANT Use this procedure if you are installing SQL Standard on this server and are
either installing a separate Historian server or are not using a Historian server.
If installing a standalone Historian Server with SQL Express, skip this section
and proceed to Configure the Historian Virtual Server on page 113.
IMPORTANT If installing both a Historian and SQL server, Complete chapter 3 Server Initial
Configuration on both servers before continuing with this procedure.
1. On the virtual image desktop, click the Programs icon and choose
Microsoft SQL Server 2012>Configuration Tools>Complete SQL
Server 2012 Installation.
IMPORTANT For the remainder of the installation, default selections are shown and
we do not recommend any changes. Some PlantPAx configurations
require these default selections. We recommend accepting the
defaults, prove the system, and make changes later. Corresponding
notice is provided where exceptions to this configuration are
considered for changing now. Otherwise, simply click Next on the
following screen captures to complete the process.
9. Use the default name of your SQL server instance and click Next.
TIP Change the server name only if you're planning another SQL instance
on this machine. Observe the SQL instances are addressed by their
<MachineName>\<InstanceName> combination.
10. Use defaults and click Next for the Feature Review step.
11. Click Default Instance and click Next for the Instance Configuration step.
12. Use defaults and click Next for the Server Configuration step.
13. Select Mixed mode then enter and confirm the password. Specify the SQL
Server administrators. At least one must be chosen either by clicking ‘Add
Current User’ or ‘Add.’ Click Next.
TIP Additional SQL administrators can be added, if necessary. Click Help for
clarifications.
14. Specify which users have administrative privileges for Analysis Services. At
least one must be chosen either by clicking ‘Add Current User’ or ‘Add.’
Click Next.
The procedures in this section apply only if you plan to do the following:
• Use FactoryTalk Historian Asset Framework in your PlantPAx system
• Install Asset Framework Server on the SQL Server
IMPORTANT If you are not installing Asset Framework on the SQL Server, not deploying a
Historian server, or installing a standalone Historian or you can skip this
section. Proceed to Add Local User to the SQL Server on page 111.
IMPORTANT The installation files are not included in the SQL Server template. The
installation files for services platform are located in the Historian template in
c:\install files\6.00.00\FTHistorian\SE-DVDDL. If Historian is already deployed
on the network, access the installation files through the network. Otherwise,
the Historian template can be downloaded from the Product Compatibility and
Download Center (PCDC) at
http://compatibility.rockwellautomation.com/Pages/home.aspx.
7. Clear all software products except for FactoryTalk Services Platform and
click Install.
IMPORTANT Even though ‘Press Ctrl + Alt + Delete …’ is displayed on the screen,
you must press Ctrl + Alt + Insert to access the virtual machine. The
sequence 'Ctrl + Alt + Del' is reserved for the terminal from where you
connect to the server that hosts the virtual machine.
Complete these steps on the SQL server to specify the network FactoryTalk
Directory location.
IMPORTANT Browse can be inactive if Network Discovery and File Share are not turned on. If
Browse is inactive, type the computer name of the virtual machine that is
hosting the FactoryTalk Directory.
6. Navigate the network to find the computer name of the server (typically
PASS) that is hosting the FactoryTalk Directory services. Click OK.
7. Click OK to accept the location.
8. Click OK to finalize the location.
IMPORTANT The installation files are not included in the SQL Server template. The
installation files are in the Historian template in c:\install
files\6.00.00\FTHistorian\SE-DVDDL. If Historian is already deployed on the
network, access the installation files through the network. Otherwise, the
Historian template can be downloaded from the Product Compatibility and
Download Center (PCDC) at
http://compatibility.rockwellautomation.com/Pages/home.aspx.
10. Type a period (.) for the 'Database Server name' and click Next
11. Click Install to start the installation process. If a security prompt opens,
click Run to allow the process to continue.
12. Close the Release Notes, then click Finish to close the wizard.
13. Click Exit to close the Historian Installation window.
1. On the virtual image desktop, click the Programs icon and choose
Microsoft SQL Server 2012>SQL Server Management Studio.
2. On the Connect to Server dialog box, log in to the 'sa' account with SQL
Server Authentication.
3. Type the password that you created during the SQL installation (see
page 104).
4. Click Connect.
10. In the Search Results area, select the local administrator account that is
logged in and click OK.
The ‘object name’ area on the Select User or Group dialog box is
populated.
Configure the Historian This template represents a base installation of a FactoryTalk Historian server. The
template excludes optional features, such as Advanced Server or Datalink.
Virtual Server
We recommend that you install Asset Framework (AF) software on the SQL
server. Instructions are included in the SQL server section (see page 102).
If the AF software cannot be installed on the SQL server, see the FactoryTalk
Historian SE Installation and Configuration Guide for more information on
locating your Asset Framework Server. The guide is available on the Historian
server at C:\Program Files (x86)\Common Files\Rockwell\Help.
If you cannot install AF software on the SQL Server or another computer, and
want to install on the Historian computer, then you are creating a standalone
Historian server.
For high availability of your Historian server, install two FactoryTalk Historian
servers and configure the FactoryTalk Historian SE system to store and write
identical data on each server. Together, this set of servers is called a FactoryTalk
Historian Server Collective.
The server collective receives data from one or more interfaces and responds to
requests for data from one or more clients. When one server becomes unavailable,
another server that contains the same data responds to requests for that data.
If you are implementing a collective, you must deploy two Historian servers.
Complete all sections of this manual for each Historian server. For more
information on a server collective, see the PlantPAx Distributed Control System
Infrastructure User Manual, PROCES-UM001.
Historian Configuration
IMPORTANT During the configuration of the Historian server, a User Account Control
window asks if you want to allow a program to make changes to the computer.
Click Yes.
6. Click Browse (ellipsis '…') and navigate the network to find the computer
name of the server (typically PASS) that is hosting the FactoryTalk
Directory services.
IMPORTANT Browse can be inactive if Network Discovery and File Share are not active.
Manually type the name of the server if necessary.
Delete the old Historian server name to keep the PI SDK up-to-date with current
computer names. Complete these steps.
TIP The first time the PI SDK is run, it can take several minutes to complete the
startup and show a display.
3. In the server pane, right-click any old Historian server name (other than
your recently created computer) and choose 'Remove selected Server'.
4. Click Yes.
5. Close the utility.
IMPORTANT If you are installing a standalone historian server, proceed with the next
section. If you are installing a Historian server with Historian Asset Framework
on a separate server, skip to Complete Historian Configuration on page 123.
IMPORTANT Proceed with this section only if you plan to implement a standalone
Historian server.
IMPORTANT For more information on installing Microsoft SQL Server 2016 Express,
refer to the FactoryTalk Historian Installation and Configuration Guide.
We recommend that you use the default settings during the
installation of Microsoft SQL Server Express.
9. Read the license agreement, accept the terms, and click next.
10. Clear the checkbox for Microsoft updates and click next.
11. Click next in the product update page.
12. Click Next on the Install Rules page.
13. Clear the checkbox for R Services on the features page. Leave the default
option for the rest of the features. Click Next.
TIP R Services are not required but can be installed if an Internet connection is
available.
17. Select Install and Configure for Reporting Services Configuration. Click
Next.
18. Click Close once the installation is complete. Installation takes
approximately 15 minutes.
IMPORTANT Proceed with this section only if you plan to implement a standalone Historian
server.
11. Click Next to accept ‘.\sqlexpress’ as the default Database Server Name.
IMPORTANT During the installation process, the Release Notes display in a separate
window. The installation process is not complete until you close the
Release Notes window.
13. Close the Release Notes, and click Finish to close the wizard.
IMPORTANT See the pages that are referenced in the FactoryTalk Historian SE Installation
and Configuration Guide, publication HSE-IN025A:
• Verify that Historian Services are Running
• Verify that Historian Server is Updating Data for Default Tags
• Prepare PI MDB to AF Synchronization
• Create Security Mappings
• Adding the Server to the FactoryTalk Directory Connection
• Assigning License Activations to the Historian Server
Configure the Batch Virtual This section provides procedures to install FactoryTalk Batch independently,
with FactoryTalk eProcedure, or with Event archiver.
Server
Before configuring the server, complete the following tasks:
• Chapter 2 Deploy the PlantPAx Virtual Image Templates on page 31.
• Chapter 3 Server Initial Configuration on page 87.
1. On the virtual image desktop, click the Programs icon and choose
Rockwell Software>FactoryTalk Tools>Specify FactoryTalk Directory
Location.
2. In the FactoryTalk Directory Server Location Utility dialog box, click
Browse (ellipsis '…').
IMPORTANT Browse can be inactive if Network Discovery and File Share are not
enabled.
5. Click OK
2. Double-click Setup.exe.
3. When the Setup window displays, click Next.
10. Select whether to activate now or later and click Next. You must be
connected to the Internet to activate now.
11. Click Close.
The eProcedure® template lets you step through the process of creating and
commanding a batch. You can view equipment or procedures for batches running
within the plant.
IMPORTANT You must have FactoryTalk Batch installed on the server to complete the
following procedure.
Complete these steps to install the FactoryTalk Event Archiver to insert batch
record data.
IMPORTANT You must have FactoryTalk Batch installed on the server to complete the
following procedure.
5. Click Next.
6. Type your SQL server name. Use the Default Instance, Source Name, and
Include Batch Reports.
7. Click Next.
8. Click Modify once the connection is validated.
9. On the EULA page, read the license agreement and click 'Accept all'.
10. Click Close once the modification is complete.
1. On the virtual image desktop, click the Programs icon and choose
Rockwell Software>FactoryTalk Tools>Windows Firewall Configuration
Utility.
2. If the firewall has not been enabled, the following dialog box can open.
Click Yes to enable the fire wall and continue.
At this point, the FactoryTalk Batch virtual server is ready for use. Review the
Installation Guide for FactoryTalk Batch, publication BATCH-IN002.
For these procedures, see the Batch Installation Guide (‘Configure Batch Server
to run in a Workgroup’) and the eProcedure manual.
• The FactoryTalk Batch Installation Guide is in your template at C:\Install
Files\Batch Installation Software\13.00.02-FTBatch-ePro-MatMgr-DVD
• The FactoryTalk Batch Administrator’s Guide is in your template at c:\
Program Files (x86)\Commion Files\Rockwell\Help.
Configure the Asset An asset management server (AppServ-Asset) helps to manage and maintain
plant operations. The AppServ-Asset server provides controller data backup for
Management Virtual Server disaster recovery, diagnostics, calibration, and real-time monitoring. The server
also audits equipment and network health to improve overall
resource availability.
Configure a Firewall
IMPORTANT Before proceeding, there must be a connection between this computer and the
computer where the FactoryTalk Directory resides. There must also be a
connection between this computer and the SQL server.
1. On the virtual image desktop, click the Programs icon and choose
RockwellSoftware>FactoryTalk Tools>Windows Firewall Configuration
Utility.
2. If the firewall has not been enabled, the following dialog box can open.
Click Yes to enable the firewall and continue.
1. On the virtual image desktop, click the Programs icon and choose
Rockwell Software>FactoryTalk Tools>Specify FactoryTalk Directory
Location.
2. In the FactoryTalk Directory Server Location Utility dialog box, click
Browse (ellipsis '…').
IMPORTANT Browse can be inactive if Network Discovery and File Share are not
enabled.
5. Click OK
6. On the FactoryTalk Directory Server Location Utility dialog box, click
OK to accept the changes.
There must be an inbound rule that allows a connection through the firewall to
the AppServ-Info (SQL) server.
1. On the virtual image desktop, click the Programs icon and choose
Administrative Tools>Windows Firewall with Advanced Security.
2. In the Windows Firewall with Advanced Security, click Inbound Rules.
3. Right-click Inbound rules and select New Rule.
4. In the Rule Type dialog box, click Port and then click Next.
5. Select TCP and Specify local ports.
6. Type '1433' as the specific local port.
7. Click Next.
8. Select 'Allow the connection' and then click Next.
9. Make sure that all boxes are checked and click Next.
10. Type External SQL Connection in the Name field and click Finish.
The firewall now permits connections to the external SQL server in a
secure manner.
IMPORTANT Before proceeding, there must be a connection between this computer and the
computer where the FactoryTalk Directory resides. There must also be a
connection between this computer and the SQL server.
1. Open the Server Setup shortcut on the desktop and run the
FTAssetCentre.DBInstaller.exe file.
2. Type the name of the SQL server in the server section. Log in with the ‘sa’
user account created when installing the SQL server.
3. Click Start.
4. Type a password for the AssetCentreUser account. Click OK.
5. Click YES to acknowledge creating the new user.
6. Open the Server Setup shortcut on the desktop and run the
FTAssetCentre.AosCatalogImport.exe file.
Configure the AppServ-OWS/ This section describes procedures for configuring an AppServ-OWS and
AppServ-EWS. The procedure is the same for both servers.
AppServ-EWS Virtual Servers
Application servers for EWS and OWS allow multiple instances of EWS and
OWS workstations to be deployed by using Microsoft Remote Desktop Services
(RDS).
IMPORTANT If you already own individual product activations, these activations also can be
used to activate the instances of these virtual image templates you deploy.
Each instance requires its own Rockwell Automation license and Microsoft
license.
IMPORTANT To complete this procedure, a PASS server must be configured on your system.
The workstation being configured must have an established connection with
the PASS server.
Complete these steps to specify the network FactoryTalk Directory location for
EWS and OWS workstations.
Complete these steps on the SQL server to specify the network FactoryTalk
Directory location.
IMPORTANT Browse can be inactive if Network Discovery and File Share are not turned on.
6. Navigate the network to find the computer name of the server (typically
PASS) that is hosting the FactoryTalk Directory services. Click OK.
If Browse is inactive, type the computer name of the virtual machine that is
hosting the FactoryTalk Directory.
7. Click OK to accept the location.
TIP The credentials were configured in Configure the FactoryTalk Directory on the
PASS on page 99.
IMPORTANT This section is not performed for OWS. Proceed to Configure Remote Desktop
Services on page 141.
IMPORTANT Microsoft Excel 2010 SP2 or later must be installed before continuing.
1. On the single-server image, click the PIAF setup folder shortcut on the
desktop.
2. Double-click the setup file. PI-AF-Services_2017-R2A_.exe
3. Click Next.
4. Check the box for PI Builder and make sure that all other boxes are
cleared.
5. Click Next.
6. Click Install to accept the defaults and begin installation.
7. Click Reboot once the installation is finished.
This architecture is ideal for PlantPAx users that use thin clients as Operator and
Engineering workstations.
IMPORTANT A valid FactoryTalk activation is still required for each instance of the OWS and
EWS that is in use.
Users, with the proper credentials, can log in into the AppServ-OWS and
AppServ-EWS and run the desired application.
One Rockwell Automation software activation key is required for each remote
desktop session.
Additional Services
IMPORTANT You can add additional role services to your server depending on your specific
deployment of RDS and connectivity needs. These added services can add
additional configuration beyond which this base RDS has been configured for.
TIP Remote Desktop Services uses its own method of licensing clients that log on
to Remote Desktop Services servers. This method is separate from licensing for
the Windows Server family of operating systems. Therefore, AppServ-OWS and
AppServ-EWS Remote Desktop Connections must receive a valid license. This
license must be issued by a Remote Desktop Licensing Server before they can
log on to a Remote Desktop Session Host or Connection Broker.
For volume licensing of these components, contact your Microsoft distributor.
Configure the VantagePoint AppServ-Info can be configured as a decision support tool by using FactoryTalk®
VantagePoint EMI software. VantagePoint EMI is a powerful web-based business
Virtual Server intelligence solution that is designed specifically for industrial environments with
premier Logix integration. VantagePoint EMI integrates all data into one
information management and decision support system by connecting to your
Logix controllers, OPC data sources, Historians, and SQL/Oracle Databases.
With an AppServ-Info (VantagePoint) system element in your PlantPAx DCS,
you can access your production data from anywhere including your shop floor
devices, PC, or your mobile phone or tablet.
IMPORTANT To complete this procedure, a PASS server must be configured on your system.
The workstation being configured must have an established connection with
the PASS server.
Complete these steps on the server to specify the network FactoryTalk Directory
location.
IMPORTANT Browse can be inactive if Network Discovery and File Share are not turned on.
6. Navigate the network to find the computer name of the server (typically
PASS) that is hosting the FactoryTalk Directory services. Click OK.
If Browse is inactive, type the computer name of the virtual machine that is
hosting the FactoryTalk Directory.
7. Click OK to accept the location.
8. Click OK to finalize the location.
TIP The credentials were configured in Configure the FactoryTalk Directory on the
PASS on page 99.
7. Read the License Agreement, click 'I accept the terms in the License
Agreement’, and click Next.
8. Click Express on the 'Choose Setup Type' page.
A warning appears if you have not installed Microsoft Excel.
9. Click OK.
10. In the Database Connection Information page, type the name of the SQL
server, click SQL Server, and type credentials for the database.
IMPORTANT Type the password that you created when completing the SQL Server
installation when deploying the SQL Server template.
8. Click Next.
9. Click Install.
10. Type the Domain name, user name for the Domain controller, and
password for the Domain controller in the System/Office User page
11. Click Next.
The Microsoft Excel software program starts and a VantagePoint
Configuration warning appears.
12. Close Microsoft Excel and click OK in the warning.
A series of VantagePoint server configurations are performed. You return
to the VantagePoint Manager window when the configurations are done.
13. Click Finish.
Notes:
IMPORTANT The configuration procedures for the Engineering Workstation (EWS) and
Operator Workstation (OWS) are similar even though these PlantPAx system
elements operate differently.
The OWS supports operator interaction and control of the process through a
human machine interface (HMI).
The required Rockwell Automation® software for each virtual server is included
and pre-installed in the virtual image templates, but not activated. See
Activation Considerations on page 201 for activation procedures.
IMPORTANT If you own individual product activations, these activations can be used to
activate the virtual image templates.
During the configuration of EWS and OWS stations, you can encounter a User
Account Control window that asks if you want to allow a program to make
computer changes. Click Yes to continue.
Before You Begin You must have deployed your template from a USB drive or from a local template
before performing the following procedures. If you deploy a virtual image
template into your system, see Chapter 2 on page 31 for details.
Configure Microsoft Windows Complete these steps to configure Microsoft Windows settings for the EWS and
OWS workstations.
1. From a web browser, enter the IP address of the computer where your host
server is installed.
2. Type the user name and password for the host server, and click Login.
The VMware ESXi window appears.
3. From the Navigator in the left pane, right-click the virtual machine that
you want to configure, and select Power>Power On.
4. Right-click the virtual machine again, and select Console>Launch Remote
Console.
7. Next you are asked if you want to add a second keyboard layout. Choose
‘Add layout’ if you want a second keyboard layout. Otherwise, click ‘Skip.’
Complete the steps on the system computers to group folders under ‘Programs’
on the taskbar. When complete, you can access Windows and Rockwell Software®
folders by clicking the Programs symbol on the task bar.
The result is a custom menu with easy access to Rockwell Software conveniently
on the Windows taskbar.
Standard Workstation The following procedures apply to EWS and OWS workstations.
Configuration
Rename the Computer
You have the option of giving the computer another name than the one assigned
during configuration of the Windows settings. Or, you can add the workstation
to a domain by performing these steps.
5. Select Domain and type a domain name or Workgroup (default) and type
a workgroup name.
6. Click OK.
Complete these steps to adjust processor scheduling for best performance in the
Windows 10 operating system.
TIP The configuration is the same from this point forward for both server and
workstation-based EWS and OWS.
For small and medium systems, this option provides for multiple system
elements to be on the same physical server. Thus the elements are consolidated
on the PASS, which is referred to as PASS-C to differentiate from a traditional
PASS server. We suggest that your system not have more than 2000 I/O points
for this consolidated server.
IMPORTANT The USB device contains a bootable installation of a PASS-C server or OWS
workstation.
A purchase of a PASS-C or OWS ISO includes an Electronic Software Delivery
(ESD) version available for download from the Product Compatibility and
Download Center. The ESD is one file (.ISO type) which can be used to create
your own bootable device. Typical bootable devices that you can create are
DVDs and USB storage devices. We do not provide procedures for creating
bootable devices. Several third-party resources are available (for example,
PowerISO, RUFUS, and so on) for purchase.
Figure 4 lists the topics to configure a PASS-C server. You must complete the
tasks in the order listed.
See the page number or click the links for quick access to specific information.
Start
Install PASS-C
Configure FactoryTalk AssetCentre
See page 161
See page 188
YES NO
SQL Express? Configure FactoryTalk VantagePoint
See page 193
1. Make sure that your computer is capable of booting from a USB drive.
Enter the BIOS Setup as the computer is powering on (typically by
pressing the F2 key). Make sure that the Boot options include booting
from a USB device.
2. Shut down the computer and connect the USB drive.
3. Turn on the computer. While the computer is powering on, strike the
F12 key to open the boot options screen.
4. Select the USB device containing the PASS-C installation.
5. On the Windows Setup dialog box, select your options from the
pull-down menus.
6. Click Next.
7. Enter the product key or Click I don’t have a product key.
8. Click Install Now.
9. Click “I accept the license terms”, and click Next.
10. Click Custom (installation).
Configure Windows Settings This section describes how to configure the Windows server to enhance
system performance.
1. Login using the administrator account and password that was created in
the previous step.
2. In the Product Key window, type a valid Windows Server Product Key
and click OK.
3. Verify that the product key is correct and click Yes.
4. Click OK in the message window when the product key was installed
successfully.
5. Install any required drivers for your hardware (graphics, Ethernet,
chipset, and so on).
6. Right-click the windows start icon and select ‘System’.
16. Select ‘Turn on DEP for essential Windows programs and services only’
and click Apply.
17. Acknowledge the prompt that changes will take effect on restart.
21. Remove the check mark from the ‘Allow connections only from
computers ...’ box and click Apply.
Complete these steps to verify the speed, duplex, and power management
settings for the Ethernet adapter.
IMPORTANT For the remainder of the installation, default selections are shown and we
do not recommend any changes. Some PlantPAx configurations require
these default selections. Best practice is to accept the defaults, prove the
system, and make changes later. Corresponding notice is provided where
exceptions to this configuration are considered for changing now.
Otherwise, simply click Next on the following screen captures to complete
the process.
7. Use the default name of your SQL server instance and click Next.
IMPORTANT Change the server name only if you're planning another SQL instance on this
machine. Observe the SQL instances are addressed by their
<MachineName>\<InstanceName> combination.
8. Use defaults and click Next for the Feature Review step.
9. Click Default Instance and click Next for the Instance Configuration
step.
10. Use defaults and click Next for the Server Configuration step.
11. Select Mixed mode then enter and confirm the password. Specify the
SQL Server administrators. At least one must be chosen either by
clicking ‘Add Current User’ or ‘Add.’ Click Next.
IMPORTANT Additional SQL administrators can be added, if necessary. Click Help for
clarification.
12. Specify which users have administrative privileges for Analysis Services.
At least one must be chosen either by clicking ‘Add Current User’ or
‘Add.’ Click Next.
IMPORTANT Do not perform the following procedure, Adjust SQL Express Settings, if you
just installed SQL Server Standard. Skip to installing Historian Asset
Framework.
IMPORTANT Do Not perform this procedure if you just completed installing SQL Server
Standard. Skip to Install Historian Asset Framework on page 179.
1. Log in as Administrator.
2. Navigate to Programs>Microsoft Server 2012>SQL Server
Management Studio.
3. Enter the server name.
The Server name is <ComputerName>\SQLEXPRESS.
Where <ComputerName> = the computer name set in Configure
Windows Settings on page 163.
4. Log on by using the ‘sa’ account and Rockwell1 as the password.
IMPORTANT After you complete the initial settings, change your logon and
password settings under Options.
5. Click Connect.
IMPORTANT The old Administrator account contains the old computer name and must be
deleted. Perform the following steps to delete the existing account and
create a new account.
We must add the Administrator account by using the new computer name.
3. Type ‘administrator’ in the object name box and click Check Names.
4. Verify that the user is successfully verified, and click OK.
9. Click OK.
3. Click OK.
4. Close SQL Server Management Studio.
The procedures in this section apply only if you plan to do the following:
• Use FactoryTalk Historian Asset Framework in your PlantPAx® system
• Install Asset Framework Server on the Server
10. Type a period (.) for the 'Database Server name' if using SQL standard. If
you are using SQL Express, type .\sqlexpress and click Next.
Figure 6 - SQLEXPRESS
11. Click Install to start the installation process. If a security prompt opens,
click Run to allow the process to continue.
IMPORTANT At the end of the installation process, the Release Notes display in a separate
window. The installation process is not complete until you close the Release
Notes window.
12. Close the Release Notes, then click Finish to close the wizard.
13. Click Exit to close the Historian Installation window.
Complete these steps to verify that the Historian AF database and user group
were added to your computer.
1. Click the Programs icon and choose Microsoft SQL Server 2012>SQL
Server Management Studio.
IMPORTANT After you complete the initial settings, change your logon and
password settings under Options.
4. Click Connect.
5. From the SQL Server Management Studio configuration tree, expand
the Databases folder and verify that PIFD appears in the list.
6. Expand the Security\Logins folder and verify that the AFServers user
group was added.
IMPORTANT Step 3 must be done twice. You have to enter a user name and
password for each directory (local and network).
1. Navigate to
Programs>Rockwell Software>FactoryTalk Administration Console.
2. Select Network (directory) and click OK.
3. Expand System>Computers and Groups>Computers in the explorer
pane.
From the Explorer pane, right-click the User Groups folder and choose
New>Windows-Linked User Group.
13. Verify that the user group is correct, and click OK.
1. Navigate to
Programs>Rockwell Software>FactoryTalk Asset Centre Server>Server
Settings.
2. Type a user name and password and click OK.
3. Type the new computer name and click Apply.
4. Click OK.
Run FTAC repair to update FTAC with the new computer name.
1. Open the Server Setup folder on the desktop and run the
FTAssetCentre.DbInstaller.exe.
2. Type a period (.) for the server name if using SQL Server Standard, or
type “.\sqlexpress” if using SQL Server Express.
3. Log in by using the ‘sa’ and the password for your SQL server and click
Start.
5. If prompted to create a new user, click yes, and follow the prompts.
6. Open the Server Setup folder on the desktop and run the
FTAssetCentre.AosCatalogImport.exe
7. Restart your computer.
1. Navigate to:
Programs>Rockwell Software>FactoryTalk Historian SE>FactoryTalk
Historian SE System>AboutPI-SDK
2. In the left pane, click Connections, right-click the old server names, and
choose Remove selected Server.
3. Close PI-SDK utility.
PI Builder lets you import and export FactoryTalk Historian points and Asset
Framework objects to and from a Microsoft Excel Add-in spreadsheet.
IMPORTANT Microsoft Excel 2010 SP2 or later 32-bit software must be installed for these
procedures.
3. Click Next.
4. Leave the defaults checked and check the box for PI Builder.
5. Click Next.
6. Click Modify to begin installation.
7. Click Close.
IMPORTANT See the pages that are referenced in the FactoryTalk Historian SE Installation
and Configuration Guide, publication HSE-IN025A:
• Verify that Historian Services are Running
• Verify that Historian Server is Updating Data for Default Tags
• Prepare PI MDB to AF Synchronization
• Create Security Mappings
• Adding the Server to the FactoryTalk Directory Connection
• Assigning License Activations to the Historian Server
10. If you are using SQL 2012 Standard, accept the defaults and click Next.
If you are using SQL Express, enter “.\sqlexpress” for the server and then
click Next.
11. If you have a local user account that is specified for VantagePoint, type
the user name in the prompt. Use the computer name as the domain. If
you do not have a local user account, select Local Account and a user is
created.
15. Wait for the installation to complete. A popup window appears that
informs you the configuration is still running. It closes automatically.
16. Click Exit on the Vantage Point Installer.
17. Restart your computer.
Install OWS ISO Complete these steps to install the OWS ISO.
1. Make sure that your computer is capable of booting from a USB drive.
Enter the BIOS Setup as the computer is powering on (typically by
pressing the F2 key). Make sure that the Boot options include booting
from a USB device.
2. Shut down the computer and connect the USB drive.
3. Turn on the computer. While the computer is powering on, strike the
F12 key to open the boot options screen.
4. Select the USB device containing the OWS ISO installation.
5. On the Windows Setup dialog box, select your options from the
pull-down menus.
6. Click Next.
7. Click Install Now.
8. Click “I accept the license terms”, and click Next.
9. Click Custom (installation).
Notes:
Activation Considerations
Use FactoryTalk Activations For continuous use of FactoryTalk® products and other Rockwell Automation®
software products, computers running the software must have access to activation
files. FactoryTalk Activation software provides a secure, software-based system
for activating Rockwell Automation software products and managing software
activation files. With FactoryTalk Activation software, there is no need for a
physical master disk or any physical media. Instead, activation files are generated
and distributed electronically.
Consideration Details
Software that is not activated If the components you have installed cannot be activated, for example, because the activation server is unavailable,
then the software continues to run for up to seven days. The seven-day grace period provides time to correct the
problem with acquiring activations, without disrupting critical applications. If activation is restored within seven days,
normal operations resume. If activation is not restored, the grace period expires. After the grace period expires, if you
restart the components and activation remains unavailable, the software runs for two hours in Demo mode.
Location of activation server Activations for Rockwell Automation software can be stored local to the system element containing the Rockwell
Automation software in question or remotely depending on your preferences and needs. Typically critical system
elements keep their activations locally in case the connection with the remote activation location is lost. If you want to
remotely activate Rockwell Automation software in non-critical system elements consider storing them in a system
element with uninterrupted connection to your PlantPAx® DCS. Keep in mind the information in Consideration section
“Software that is not activated” when using a remote location for activations.
Options for adding activation files to the PASS To make concurrent floating activations available to activation clients, first you must download the activation files to
the activation server computer, from the Rockwell Automation Activation window.
If the PASS has internet access, see ‘Open Activation Manager’ in the PlantPAx Distributed Control System Infrastructure
Configuration User Manual, publication PROCES- UM001.
If the PASS does not have internet access, the activations can be downloaded on a different computer with internet
connectivity and then transferred to the PASS.
Protect activation files Activation files are simple text files that must have a .lic extension.
As long as the .lic extension is retained, you can copy or rename an activation file without harming it. However,
tampering with text inside the activation file can disable your Rockwell Software products.
If an activation file is damaged or deleted, contact Rockwell Automation Technical Support.
For safekeeping, keep an original set of your activation files on back-up media. Use descriptive names for the files, so
that you can identify them later, and copy them back to the appropriate computers.
Activation files are locked to the Host IDs of the computers (or dongles) that need them. Activation fails for Rockwell
Software products on a computer where the specified Host ID is not recognized by the activation file.
With FactoryTalk Activation software, there is no need for a physical master disk
or any physical media. Instead, activation files are generated and distributed
electronically.
Use Windows License Keys This procedure enables you to enter your Product key and activate your
Microsoft license. This procedure is also compatible with Windows and
Windows Server.
Complete these steps to enter your product key to activate the Microsoft
Windows operating system.
2. At the command prompt, type 'slmgr /ipk <Product key>' and press Enter
to add your volume license key.
3. Click OK when a dialog box appears informing you that the product key
installed successfully.
4. At the command prompt, type 'slmgr /ato' and press Enter to activate
Windows.
5. Click OK when a dialog box appears informing you that the product
activated successfully.
For definitions of terms not listed here, refer to the Allen-Bradley Industrial
Automation Glossary, publication AG-7.1.
application server (AppServ) The application server (AppServ) is a server in addition to the Process
Automation System Server (PASS) that is typically a FactoryTalk® Directory
client of the PASS. Examples are AppServ-Batch for a FactoryTalk Batch
application or AppServ-History for an Historian application.
Asset Framework Historian Asset Framework (AF) is a key component of the FactoryTalk
Historian System that allows organization of data with context, such as the
physical assets such as equipment, devices, and processing units that exist in a
plant.
datastore Represents a storage location for virtual machine files. A storage location can be a
virtual machine file system volume, a local file system path, or a directory on
Network Attached Storage.
distributed control system (DCS) A specially designed control system for complex and large applications in
industrial processes wherein the control elements of the system are distributed
geographically throughout the plant. In a DCS, a hierarchy of controllers is
connected by communication networks for command and monitoring.
engineering workstation (EWS) The engineering workstation (EWS) provides system configuration,
development, and maintenance functions of the PlantPAx® system. The EWS
contains development software, including FactoryTalk View SE Studio and
Studio 5000 Logix Designer®.
ESXi hypervisor Also called a ‘bare metal’ hypervisor, this virtual software is on top of the
resources of a host server when the server does not have an operating system
installed.
FactoryTalk directory software FactoryTalk Directory software defines were system data is stored for access.
FactoryTalk Directory software provides a common address book of factory
resources that are shared among FactoryTalk-enabled products.
guest OS The operating system of the virtual machine. The guest OS is one of the
components of the virtual image.
historical data Historical data is data that is used for the long term analysis of past operation.
host OS The operating system of the host server. Servers without operating systems
leverage an ESXi hypervisor to manage its resources and allocate them to the
virtual machines that need them.
host server A physical server whose hardware resources are distributed to provide for the
needs of the virtual machines deployed in it. Also called a hardware host.
hypervisor A program that lets multiple operating systems share resources from a single
hardware host; also called a virtual machine manager. The hypervisor manages
the host processor and resources, allocating what is needed to each virtual
machine to make sure they cannot negatively impact each other.
hypervisor client A program that lets you remotely connect to a host server with a hypervisor from
any workstation. From the hypervisor client, you can create, deploy, copy, and
edit your virtual machines. When a hypervisor client connects to a vCenter
server, additional features include management of your virtual machines.
old computer name The term ‘old computer name’ is used to refer to the computer name of the
virtual machine prior to your changes. This reference could be the factory default
computer name of the virtual machines or a computer name set by your
organization. Once the computer name is changed, the previous computer name
becomes the ‘old computer name’.
operator workstation (OWS) The operator workstation (OWS) provides the graphical view and interface into
the process. The workstation is a client of either a PASS or AppServ-HMI.
PlantPAx Distributed Control The PlantPAx system has all the core capabilities expected in a world-class
System distributed control system (DCS). The system is built on a standards-based
architecture by using Integrated Architecture® components that enable
multi-disciplined control and premier integration with the Rockwell
Automation® intelligent motor control portfolio.
Process Automation System Server The Process Automation System Server (PASS) is the core PlantPAx system
(PASS) server allowing central administration throughout the PlantPAx system. The
PASS is a required component.
RSLinx software RSLinx® software is the communication driver (data server) for computer-based
programs to access information in Rockwell Automation controllers. There is
RSLinx Classic software and RSLinx Enterprise software. FactoryTalk View SE
software uses RSLinx Enterprise software to directly access tags in a controller.
server Software component that serves data to an application (for example, data server).
Typically, server software components are installed on server-class computers.
virtualization Virtualization is the abstracting of the operating system from the hardware to
enable multiple virtual machines on a single piece of hardware.
Notes:
Technical Support Center Knowledgebase Articles, How-to Videos, FAQs, Chat, https://rockwellautomation.custhelp.com/
User Forums, and Product Notification Updates.
Local Technical Support Phone Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-
Numbers now.page
Direct Dial Codes Find the Direct Dial Code for your product. Use the http://www.rockwellautomation.com/global/support/direct-dial.page
code to route your call directly to a technical support
engineer.
Literature Library Installation Instructions, Manuals, Brochures, and http://www.rockwellautomation.com/global/literature-library/
Technical Data. overview.page
Product Compatibility and Download Get help determining how products interact, check http://www.rockwellautomation.com/global/support/pcdc.page
Center (PCDC) features and capabilities, and find associated
firmware.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete the How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/
documents/du/ra-du002_-en-e.pdf.
Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.
Allen-Bradley, ControlFLASH Plus, eProcedure, FactoryTalk, Integrated Architecture, PlantPAx, Rockwell Automation, Rockwell Software, RSLinx, RSLogix, RSLogix 5000, RSNetWorx, Studio 5000 Architect, Studio 5000 Logix Designer,
and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400