Plantpax Distributed Control System - Templates: User Manual
Plantpax Distributed Control System - Templates: User Manual
Plantpax Distributed Control System - Templates: User Manual
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Summary of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Purpose of this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Before you Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Microsoft Operating System Software Licensing . . . . . . . . . . . . . . . . . . . . 9
PlantPAx Virtual Image Template Catalog Numbers . . . . . . . . . . . . . . . . . 9
Build Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
PlantPAx Virtual Image Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
USB Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 1
Basics of Virtualization Virtual Image Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Choose a Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Install a Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Copy Installer Image to DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Copy Installer Image to USB Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Use a DVD or USB Drive to Start Server. . . . . . . . . . . . . . . . . . . . . . . . 17
Assign an IP Address to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Using a vSphere Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 2
Deploy PlantPAx Virtual Deploy PlantPAx Virtual Image from OVA file . . . . . . . . . . . . . . . . . . . . . 25
Machines Power On the Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Windows Out of Box Experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Initial Windows Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
VMware Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3
VMware ESXi vCenter Server Install a vCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Create a DataCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Add a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Create a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Deploy Your Own Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Optional Virtual Machine Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Initiate Automatic Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Send Commands to Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Set Resource Pool Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 4
Common Windows Configuration Local Administrator User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Toolbar for Programs Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Rename the Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Verify Ethernet Network Adapter Settings. . . . . . . . . . . . . . . . . . . . . . . . . 55
Chapter 5
Configure PlantPAx System Configure the PADC Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Servers Configure the PASS Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configure the SQL Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Install Historian Asset Framework on SQL Server . . . . . . . . . . . . . . . . . . 63
FactoryTalk Historian SE installation media . . . . . . . . . . . . . . . . . . . 64
Specify the FactoryTalk Directory Location. . . . . . . . . . . . . . . . . . . . . 66
Add Local User to the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configure the Historian Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Historian Collective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Additional Historian Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configure the Batch Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Specify FactoryTalk Directory Location . . . . . . . . . . . . . . . . . . . . . . . . 71
Install FactoryTalk Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Install FactoryTalk eProcedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Install FactoryTalk Event Archiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Complete Batch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configure the Asset Management Virtual Server . . . . . . . . . . . . . . . . . . . 77
Configure a Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Specify FactoryTalk Directory Location . . . . . . . . . . . . . . . . . . . . . . . . 78
Create a New Inbound Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Configure FactoryTalk AssetCentre Software. . . . . . . . . . . . . . . . . . . 80
Update FactoryTalk AssetCentre SQL Instance . . . . . . . . . . . . . . . . . 81
Configure the AppServ-OWS/AppServ-EWS Virtual Servers . . . . . . . . 82
Specify the FactoryTalk Directory Location. . . . . . . . . . . . . . . . . . . . . 82
Install PI Builder Excel Add-in for Microsoft Excel . . . . . . . . . . . . . . 83
Configure Remote Desktop Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Remote Desktop Services with FactoryTalk View SE . . . . . . . . . . . . 86
Additional Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configure the VantagePoint Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . 87
Specify the FactoryTalk Directory Location. . . . . . . . . . . . . . . . . . . . . 87
Install VantagePoint Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . 88
Install Microsoft Excel Add-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Chapter 6
PASS-C / OWS ISO Images for PCs Install Pass-C Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Configure Windows Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Ethernet Network Adapter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configure System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Complete SQL server 2019 Installation . . . . . . . . . . . . . . . . . . . . . . . . 100
SQL Registered Server Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Update SQL after Computer Rename . . . . . . . . . . . . . . . . . . . . . . . . . 105
Add New Administrator Login to SQL . . . . . . . . . . . . . . . . . . . . . . . . 105
Delete Old Administrator Login to SQL . . . . . . . . . . . . . . . . . . . . . . . 108
Configure AssetCentre User Account . . . . . . . . . . . . . . . . . . . . . . . . . 109
Install Historian Asset Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4 Rockwell Automation Publication 9528-UM001J-EN-P - June 2022
Verify the AFServers Database and Account . . . . . . . . . . . . . . . . . . . 112
Configure the FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Delete “Unused” Computer Names from Directory. . . . . . . . . . . . . 115
Recreate IIS_IUSRS User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configure FactoryTalk AssetCentre (FTAC) Server . . . . . . . . . . . . . . . . 118
Update FactoryTalk AssetCentre SQL Instance . . . . . . . . . . . . . . . . 119
Configure FactoryTalk Historian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Remove Old Computer Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Install PI Builder Excel Add-in for Microsoft Excel . . . . . . . . . . . . . 120
Additional Historian Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Install VantagePoint Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Install FactoryTalk Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Install FactoryTalk eProcedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Install FactoryTalk Event Archiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Complete Batch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Configure HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Install OWS Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Windows Out of Box Experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Initial Windows Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Configure Windows Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Ethernet Network Adapter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Configure System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Specify FactoryTalk Directory Location . . . . . . . . . . . . . . . . . . . . . . . 136
Configure FactoryTalk View SE Client . . . . . . . . . . . . . . . . . . . . . . . . 137
Configure Services for Historian PIPerfmon . . . . . . . . . . . . . . . . . . 138
Configure FactoryTalk AssetCentre Client . . . . . . . . . . . . . . . . . . . . 139
Appendix A
Software Product keys and Microsoft Product Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Activations Slmgr.vbs Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Rockwell Automation Activation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
FactoryTalk Activation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
This template user manual describes how to leverage virtual image templates
when deploying a virtualized PlantPAx® Distributed Control System (DCS).
PlantPAx virtual image templates are pre-configured, virtual system elements
of your PlantPAx system.
Summary of Changes This publication contains the following new or updated information. This list
includes substantive updates only and is not intended to reflect all changes.
Topic Page
Windows® Server 2016 changed to Windows Server 2019 Various
Rockwell Automation Software release versions updated Various
Install Historian Asset Framework on SQL Server section updated 63
Configure the Batch Virtual Server section updated 71
Virtual image templates are provided for the following PlantPAx system
elements:
• Process Automation System Server (PASS)
• Engineering Workstation (EWS)
• Operator Workstation (OWS)
• SQL Server - AppServ-Info (SQL)
• Process Automation Domain Controller (PADC)
• Historian Server - AppServ-Info (Historian)
• Batch Management Server - AppServ-Batch
• Asset Management Server - AppServ-Asset
• Operator Workstation Application Server - AppServ-OWS
Obtain PlantPAx virtual image templates, PASS-C, and OWS ISO USB devices
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.
vCenter server is optional and enables you to create your own virtual image
templates and increase your ability to manage a virtualized control system.
The end user is responsible for properly licensing a Microsoft OS for each
template deployed. Additional licenses can be purchased from your Microsoft
distributor.
Basics of Virtualization
Virtual Image Templates Rockwell Automation offers virtual image templates as an option to deploy a
virtualized PlantPAx® system. The PlantPAx Virtual Image Templates deliver
all system elements as pre-installed, drop-in virtual machines. The industry
also refers to virtualized system elements as virtual appliances. However, in
this manual, virtual system elements are referred to as virtual image templates
because you can use them to deploy as many virtual appliances as you want.
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.
Choose a Hypervisor
IMPORTANT The following procedures apply only to virtual templates. Skip to Chapter 6 if you’re
deploying a PASS-C or OWS ISO
Depending on the make and model of your host server, the hypervisor
installation files are available directly from the manufacturer's website. These
custom downloadable packages often contain drivers for specialized
hardware. If a customized download is not available from the vendor, you can
download the hypervisor directly from the VMware website.
1. Log in to the vendor or VMware website.
2. Find the support or downloads section and search for hypervisors.
3. Select the latest version of hypervisor that is supported on your server
hardware or choose the version of which you have licensing.
4. Download the hypervisor.
Install a Hypervisor This section describes how to install the VMware vSphere ESXi hypervisor to a
host server. 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).
2. Select the DVD drive where you will write the data, and select Burn.
Select Close when the DVD is completed.
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. Select the optional booting address during the server startup.
4. On the End User License Agreement (EULA) page, read the EULA, and
press F11 to accept the terms of the EULA and continue.
5. Select the disk where you will install the vSphere Hypervisor and press
Enter to continue.
7. Type a root password, retype the password, and press Enter to continue.
9. Remove the DVD or USB device and press Enter to shut down and
restart. The server shutdown takes a few minutes.
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.
For the displays in this section, use the arrow keys on your keyboard to move
between the fields on the pages.
1. After the system restarts, press F2 to Customize System/View Logs.
2. Enter the Login name and password that was created in Use a DVD or
USB Drive to Start Server.
5. Select 'Set static IP address and network configuration' and press the
Space bar. (The presence of a small circle between the parentheses
indicates that this option is selected.) Select the IP address, Subnet Mask,
and default gateway address and enter the appropriate values for your
system and organization.
7. On the System Customization screen, press <Esc> to log out. You have
assigned an IP address to the host server.
Using a vSphere Web Client 1. Open a web browser and type the IP address that you created for the
hypervisor host. A security warning appears the first time that you
connect to the ESXi host server.
2. Select Advanced.
5. Log in to the VMware ESXi Host using the credentials created in Use a
DVD or USB Drive to Start Server. (The default user name is ‘root’.)
6. Select Navigator.
Notes:
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.
Deploy PlantPAx Virtual This section describes the first-time deployment of a PlantPAx virtual image.
Image from OVA file The virtual image can be deployed from a purchased USB drive or from a web
download stored locally on a workstation.
TIP: If the virtual image template is sourced from a USB drive, we advise you to
copy the files to your workstation and use the copies to speed the deployment
process.
The workstation would be the same computer where you’re using the vSphere
Web Client to connect to the host server.
IMPORTANT If you plan to deploy a domain controller, it’s 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.
1. Open a web browser and enter the IP address that you created for the
host server. Enter the user name and password for the EXSi host, and
Select Log in
5. Select the datastore for your configuration and disk files storage..
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.
6. Use defaults for network mapping and disk provisioning, and select
‘Power on automatically.’
IMPORTANT When powering on the virtual machine for the first time, the screen
can remain black for several minutes.
The Windows® Out of Box Experience (OOBE) consists of displays that require
customers to accept the end users license agreement (EuLA), connect to the
internet, log in with or sign up for a Microsoft® Account, and share
information with the OEM.
Complete these steps for the initial configuration of all virtual machines that
were deployed using PlantPAx image templates.
A logon message appears, which prompts you to press Ctrl + Alt + Delete key
combination to unlock'.
1. DO NOT press Ctrl + Alt + Delete for a virtual machine.
2. Instead press Ctrl + Alt + Insert. this is the VMware key combination to
unlock.
3. 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 steps.
1. Select 'Yes' to allow the PC to be discoverable.
If you skipped the product key earlier, another dialog window appears to
remind you that Windows must be activated.
2. In the Product Key window, enter a valid Windows Product Key.
3. Verify that the product key is correct.
30 Rockwell Automation Publication 9528-UM001J-EN-P - June 2022
Chapter 2 Deploy PlantPAx Virtual Machines
4. Select OK in the message window when the product key was installed
successfully.
5. Select OK in the activation window.
6. Activate the key with a KMS server; your company’s or Microsoft’s. See
Appendix A for more licensing information.
VMware Tools
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. Enter the user name and password for the local host, and click Log in.
3. From the Navigator in the left pane, right-click the virtual machine in
which you want to update or install VMware Tools. Select Guest OS and
choose Install VMware Tools.
4. Open Windows Explorer on the virtual machine image that you want to
install VMware Tools.
If you are using the free version of VMware ESXi hypervisor, which doesn't
include a vCenter server, then you can skip chapter 3 and proceed to chapter 4
to continue with Windows server configuration.
While a vCenter server may not be needed with small systems, it is highly
recommended and required with large systems. Following are some of the key
features that a vCenter server provides:
• Single sign-in authentication (Domain controller required)
• Access multiple hosts, all VMs, datastores, and networks from one
console
• Organize inventory objects such as hosts, folders, and clusters into
datacenters
• Create templates for future virtual machine deployments
• Clone existing VMs, even when powered on
• Migrate VMs between hosts and datastores
• View alerts and notifications that are required to help prevent or remedy
the emerging issues
Install a vCenter Server There are two installation types for a vCenter server.
• vCenter Server for Windows® software runs on a Microsoft® Windows
server operating system. This Windows OS can run on a physical
computer or as a virtual machine on a host server.
• vCenter Server Appliance (vCSA) runs as a virtual machine based on
SUSE Linux Enterprise Server 64 bit and comes as an OVF appliance
ready for use.
Perform these steps on the workstation you use to manage your virtual
appliances (templates and machines).
Create a DataCenter A DataCenter is the primary container of inventory objects such as hosts and
virtual machines.
With the creation of the DataCenter, we show 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.
1. In a Web Browser, enter the IP address of the computer where your
vCenter Server is installed.
2. Click vSphere Web Client (Flash).
3. Enter the Username and Password. Use the User name and password
that you created for the vCenter Server.
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]'.
The DataCenter is the primary container of inventory objects such as hosts and
virtual machines.
4. From The VMware vSphere Web Client dialog box, highlight your
vCenter Server, and click 'Create DataCenter'.
5. When prompted, type a name for the new DataCenter (‘New DataCenter’
in our example) and click OK.
Add a Host
The host is the physical server where the virtual image is to be deployed.
1. The New DataCenter is added under the vCenter Server. Highlight the
New DataCenter and select 'Add a Host' to add a host server. The add
host wizard starts.
Assign a license
2. 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.
Create a Template
This section shows how to create your own templates. These templates can be
based off the original PlantPAx® virtual image template and customized into
your own templates.
Start with an existing virtual machine. This VM may receive changes such as
additional software, security patches, and configurations that you plan on
reusing throughout your infrastructure. When you are finished modifying the
VM, it is cloned, and a template is created.
To help prevent VMs from containing duplicate system identifiers, it is
recommended to run Windows SYSPREP on the operating system before
creating a template.
This template can be used to deploy other images. You can store the original
template for safekeeping in case you modify your templates.
1. Right-click the virtual image that you want to clone and choose
Clone>Clone to Template to open the wizard.
TIP: Consider the clone to virtual machine option as a manual method to back up
fully configured and running virtual machines. The cloned image can be stored
on a local or remote VMF5 datastore, or a remote datastore on a Windows server
featuring network file storage (NFS) capability.
Deploy Your Own Template When you have virtual image templates that are loaded into your DataCenter,
you can deploy any number of virtual images from those templates. Additional
deployments can be performed from these new templates.
1. In a Web Browser, enter the IP address of the computer where your
vCenter Server is installed.
2. Click vSphere Web Client (Flash).
3. Enter the Username and Password. Use the User name and password
that you created for the vCenter Server.
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. Select the 'VM Templates in
Folders' tab, then right-click the template that you plan to deploy to a
New Virtual Image. Select 'New VM from This Template'.
5. In the Name box, type a name for the virtual machine. In the Inventory
Location box, select a location to store the new virtual machine.
Format Description
Same format as source Use the same format as the original disks.
Disk storage is allocated immediately in a default thick format. Blocks
Thick Provision Lazy Zeroed containing older data on the storage device are cleared only when the virtual
machine writes new data to the disk for the first time.
Disk storage is allocated immediately in a default thick format where blocks
Thick Provision Eager Zeroed on the physical storage device are formatted with zeros to overwrite any
older data.
Thin Provision Disk storage is allocated on demand as data is written to virtual disks.
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
8. 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.
9. 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.
Optional Virtual Machine To help expedite the use of your virtual machines, consider the following
Interactions options:
• Initiate Automatic Startup on page 43
• Set Resource Pool Priority on page 47
3. Enter the Username and Password. Use the User name and password
that you created for the vCenter Server in Install a vCenter Server. 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.
IMPORTANT Following is the recommended startup 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. FactoryTalk® VantagePoint® server - AppServ-Info (FactoryTalk
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.
3. Enter the Username and Password. Use the User name and password
that you created for the vCenter Server in Install a vCenter Server. 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]'.
5. Type the priority in the Name text box. For example, High Performance.
From the Shares pull-down menu, select 'High' for the CPU and Memory
Resources categories.
6. Repeat step 1 through step 5 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.
The PlantPAx® system servers and workstations (virtual machines) are built on
Microsoft Windows® operating systems that require some basic configuration.
This chapter describes how to set up the new operating systems after the you
power them on for the first time, complete the OOBE initializations and install
VMware Tools.
Local Administrator User The default administrator account is often disabled to harden the operating
Accounts system. 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.
1. Navigate to the Control Panel.
2. Select User Accounts.
3. Select Manage another account.
4. Select ‘Add a user account’ below the Administrator icon.
5. Enter a name for the user that is being added, a password, retype the
password for verification, and a hint to remind you of the password.
6. Select Next, and then Finish on the next dialog box.
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.
12. Log in with the user that was created.
Toolbar for Programs Menu Newer Microsoft operating systems lack the traditional Start Menu that
contains an easily navigated programs menu.
Create a traditional style program menu on the lower right side of the
Windows task bar using the following steps.
When complete, select the double arrow symbol next to Programs on the
task bar and launch a traditional programs menu.
1. Navigate to the Control Panel and choose File Explorer Options.
2. On the View Tab, select ‘Show hidden files, folders, and drives’ and click
OK.
7. Turn off the ‘Set time automatically’ feature in the Date and Time
settings.
2. On the Server Manager window, select Local Server and then click the
computer name.
Verify Ethernet Network The PlantPAx DCS Configuration and Implementation User Manual,
Adapter Settings publication PROCES-UM100 contains configuration information procedures
for Domain or Workgroup infrastructures, such as managing IP addresses and
computer name resolution.
Verify Remote Settings Complete these steps to configure remote settings for a virtual image to allow
remote connections to this computer.
1. Right-click the Windows Start icon and choose System.
2. Select Remote settings.
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.
Verify the Processor Complete these steps to adjust processor scheduling for best performance in
Scheduling Setting the Windows Server operating system.
1. Right-click the Windows Start icon and choose System.
2. Select the Advanced system settings.
3. Select Settings in the Performance section.
4. Choose the Advanced tab.
5. Select Background services in the Processor scheduling section to adjust
for the best performance.
6. Select OK twice.
Notes:
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 (FactoryTalk
VantagePoint)
Configure the PADC Virtual A domain controller is a server that responds to security authentication
Server requests (logging in, checking permissions, and so forth) within the Windows
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.
Once you have completed these tasks, see the PlantPAx DCS Configuration
and Implementation User Manual, publication, PROCES-UM100, for domain
controller configuration procedures, such as:
• Creating a primary domain controller
• Creating an additional domain controller
• Configuring domain controllers
• Creating roles, areas and users
• Configuring group policy management
• Configuring group policies
• PlantPAx user policy objects
Configure the PASS Virtual The Process Automation System Server (PASS) hosts essential software
Server components to run your system. The data, human-interface (HMI), and alarm
servers reside in the PASS.
The PASS hosts the FactoryTalk® Services Platform that provides a set of
common services (such as diagnostic messages, health monitoring services,
and access to real-time data).
Once you have completed these tasks, see the PlantPAx DCS Configuration
and Implementation User Manual, publication, PROCES-UM100, for PASS
configuration procedures, such as:
• Configuring FactoryTalk components
• Configuring HMI, DATA, and ALARM servers
• Redundant PASS considerations
• Configuring runtime security
Configure the SQL Virtual The AppServ-Info (SQL) server is a database that is used to store Process data
Server for FactoryTalk® AssetCentre, FactoryTalk VantagePoint, FactoryTalk Batch,
and FactoryTalk Historian Asset Framework (AF) software programs. FTLinx
and FactoryTalk® Alarms and Events server also use 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 you install a standalone Historian Server with
SQL Express, skip this section and proceed to Configure the
Historian Virtual Server on page 69
IMPORTANT If you install both an Historian and SQL server, Complete VMware
ESXi vCenter Server on both servers before continuing with this
procedure.
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.
Wizard Page Action
Setup Support Rules Select OK once the rules have passed.
• Select Specify a free edition and then select Evaluation from the pull-down menu for a 90-day trial.
Product Key
• Select Enter the product key and type your key to license your software.
License Terms Read the license terms, and select ‘I accept the license terms’
Microsoft® Update Accept Default
Complete Image Rules Select Next once the rules have passed
Select Prepared Features Select Complete a prepared instance of SQL server 2019
Feature Review Review the features to be configured
Instance Configuration Select Default Instance
PolyBase Configuration Select Use this SQL Server as a standalone PolyBase-enabled Instance
Server Configuration Select Default
Reporting Services Configuration Select Reporting Services Native Mode > Install and Configure
Feature Rules Select Next once the rules have passed
Complete Image Process Select Next once Complete
Complete Select Close to complete the wizard
Install Historian Asset Installation of FactoryTalk Historian Asset Framework (AF) software is
Framework on SQL Server required to take advantage of the capabilities. Where the AF software is
installed depends upon whether a Historian Collective will be used and if a
separate SQL server is used.
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.
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 67.
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\8.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. Select No for installing SQL Server 2019 Express. Edit the Database
server name to match the server that was previously installed. Leave
Installation Mode on the default configuration. Select Install.
After the FactoryTalk Service Platform has been installed, now is a good time to
specify the network FactoryTalk Directory location, which is typically on the
PASS.
1. Select the Programs icon and choose Rockwell Software>FactoryTalk
Tools>Specify FactoryTalk Directory Location.
2. Select Yes to allow the application to make changes to the device.
3. In the FactoryTalk Directory Server Location Utility dialog box, Select
Browse (ellipsis '…').
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. Select OK to accept the location.
Add Local User to the SQL The installers for Rockwell Automation software use Windows Authentication
Server instead of SQL Server Authentication. To complete the installation of Rockwell
Automation software in system elements that connect to the SQL server, add a
local administrator account to the SQL server login. These steps are to be
performed regardless if you use a Historian server collective.
1. On the virtual image desktop, click the Programs icon and choose
Microsoft SQL Server Tools 18>Microsoft SQL Server Management
Studio 18.
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
Configure the SQL Virtual Server).
4. Select Connect.
5. In the Object Explorer, right-click Security and choose New>Login.
10. In the Search Results area, select the local administrator account that is
logged in and select 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 SE
Virtual Server server. The template excludes optional features, such as Advanced Server or
Datalink.
Historian Collective
If you are implementing a collective, you must deploy two Historian server
virtual machines. Complete all sections of this manual for each Historian
server.
Once you have completed these tasks, see the PlantPAx DCS Configuration
and Implementation User Manual, publication PROCES-UM100, for Historian
configuration procedures, such as:
• Configuring Servers for a Collective
• Creating a Collective
• Client to server connections
• Historian to FactoryTalk Directory Connection
• Configuring Redundant Node Interfaces
• Configuring PI Performance and PI Buffering
• Configuring Data Collection
• Configuring Historian Asset Framework
When the template is installed, we recommend that you review the FactoryTalk
Historian publication at http://literature.rockwellautomation.com/idc/
groups/literature/documents/in/hse-in025.pdf).
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
Server FactoryTalk eProcedure®, or with Event archiver.
IMPORTANT Browse can be inactive if Network Discovery and File Share are not
enabled.
5. Select OK
6. On the FactoryTalk Directory Server Location Utility dialog box, select
OK to accept the changes.
2. Double-click Setup.exe.
3. When the Setup window displays, select Next.
4. Clear the checkbox for FactoryTalk Event Archiver. Leave FactoryTalk
Batch v15.00 checked.
8. Select Install.
9. On the EULA page, read the license agreement and click 'Accept all'.
Installation takes approximately 15 minutes.
10. Select whether to activate now or later. You must be connected to the
Internet to activate now.
11. Select 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.
1. On the desktop, double-click the shortcut to the Batch Installation file
folder.
2. Double-click Setup.exe.
3. When the Setup window displays, select Customize.
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.
1. On the desktop, double-click the shortcut to the Batch Installation file
folder.
2. Double-click Setup.exe.
3. When the Setup window displays, click Customize.
5. Select Next.
6. Enter your SQL server name. Use the Default Instance, Source Name,
and Include Batch Reports.
7. Select Next.
8. Select Modify once the connection is validated.
9. On the EULA page, read the license agreement and select 'Accept all'.
10. Select Close once the modification is complete. Installation takes
approximately 3 minutes.
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\15.00.00-FTBatch-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
Management Virtual Server plant operations. The AppServ-Asset server provides controller data backup for
disaster recovery, diagnostics, calibration, and real-time monitoring. The
server also audits equipment and network health to improve overall
resource availability.
Configure a Firewall
5. The utility configures the Windows firewall and the firewall is set to a
new state (if different).
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, select Inbound Rules.
4. In the Rule Type dialog box, select Port and then select Next.
5. Select TCP and Specify local ports.
6. Type '1433' as the specific local port.
7. Select Next.
8. Select 'Allow the connection' and then select Next.
9. Make sure that all boxes are checked and select Next.
10. Enter External SQL Connection in the Name field and click Finish.
11. The firewall now permits connections to the external SQL server in a
secure manner.
Configure the AppServ- This section describes procedures for configuring an AppServ-OWS and
OWS/AppServ-EWS Virtual AppServ-EWS. The procedure is the same for both servers.
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).
Complete these steps to specify the network FactoryTalk Directory location for
EWS and OWS workstations.
1. Click the Programs icon and choose Rockwell Software>FactoryTalk
Tools>Specify FactoryTalk Directory Location.
2. Click Yes to allow the application to make changes to the device.
3. 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
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. Select OK to accept the location.
8. Select OK to finalize the location.
Tip: The credentials were configured in Configure the PASS Virtual Server.
PI Builder is a Microsoft Excel® add-in that lets you use Excel to create, view,
and modify PI points and Asset Framework objects in your Historian database.
With PI Builder, you can make bulk tag edits by importing and exporting your
spreadsheet.
All functionality of the prior PI Tag Configurator has been replaced with PI
Builder, which is included with the PI SMT and PI Data Archive setup kits (as
part of the PI AF Client installer).
IMPORTANT This section is not performed for OWS. Proceed to Configure Remote
Desktop Services on page 84.
If Microsoft Excel was installed after the Historian software, the AF Client
features will must be modified to include the PI Builder feature.
1. Run the PI-Server_2018-SP3-Patch-1.exe file included as part of the
installation media in the \Redist\PIServer\ folder.
2. Choose to Modify the installation and click Next.
This architecture is ideal for PlantPAx users that use thin clients as Operator
and Engineering workstations.
The thin client solution is a transparent system that runs applications and
performs data processing and storage functions on a remote computer. This
solution minimizes the amount of information traveling across your network.
While multiple sessions can run on one server, each user can see only their
individual session. Only the user interface is shown on client, user input from
client is redirected over the network to the remote desktop session. User's
desktops are transmitted to clients for display by using terminal emulation
software. Similarly, the software sends command functions such as keyboard
inputs and mouse clicks across the network between the client and the server.
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.
Users can gain access to an RDS over any Transmission Control Protocol/
Internet Protocol (TCP/IP) connection, including the following:
- Remote access
- Ethernet
- Internet
- Wireless
- Wide area network (WAN)
- Virtual private network (VPN)
• Lower cost of ownership: A thin client typically consists only of the
operating system and the Remote Desktop Connection software. RDS
delivers a virtual Windows Server experience from server to clients,
regardless of what operating system the client uses.
• Minimize downtime: Upgrade your entire FactoryTalk View SE
installation with one operation. Because FactoryTalk View SE products
install only on the server side, any future software upgrades are limited
to the server, making software upgrades on clients a thing of the past.
• Improve data security: A FactoryTalk View SE architecture that uses RDS
is less vulnerable to security threats. RDS lets you focus your security
measures on the server because all data is processed on the server, which
you can manage in a secure location.
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
Virtual Server FactoryTalk VantagePoint EMI software. VantagePoint EMI is a powerful web-
based business 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, personal computer, or your mobile phone or
tablet.
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. Select OK.
If Browse is inactive, type the computer name of the virtual machine that is
hosting the FactoryTalk Directory.
7. Select OK to accept the location.
8. Select OK to finalize the location.
11. 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.
12. Select Next.
13. Enter the Domain name, user name for the Domain controller, and
password for the Domain controller in the System/Office User page
14. Select Next.
15. Select Install.
16. Select Finish.
A DOS window opens to finish the configuration. It closes automatically.
8. Select Next.
9. Select Install.
10. Enter the Domain name, user name for the Domain controller, and
password for the Domain controller in the System/Office User page
11. Select Next.
12. The Microsoft Excel software program starts and a VantagePoint
Configuration warning appears.
13. Close Microsoft Excel and click OK in the warning.
This chapter describes how to install and configure physical computers using
the PASS-C server and OWS workstation pre-built ISO images.
The pre-built ISO images contain a Windows® server 2019 operating system
and pre-installed applications. The PASS-C image supports system elements
such as:
• FactoryTalk® Directory
• Data server
• HMI server (one server license only is required)
• Alarm server
• FactoryTalk® Historian
• FactoryTalk® VantagePoint®
• FactoryTalk® AssetCentre
• SQL server
• FactoryTalk® Batch
Install Pass-C Operating The following steps are comparable to a retail Windows server 2019 Standard
System operating system, the difference is the PASS-C ISO image contains additional
pre-installed software.
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. Select Install Now.
9. Select “I accept the license terms”, and click Next.
10. Custom (installation).
If necessary, delete any existing drive partitions and format the drive
location.
12. Select Next. The installation typically takes about an hour. The computer
automatically restarts. You must log on to complete the installation.
13. Enter an Administrator password (for your system).
14. Enter a confirmation password.
Configure Windows Settings 1. Login using the administrator account and password that was created in
the previous step.
2. In the Product Key window, enter a valid Windows Server Product Key
and click OK.
3. Verify that the product key is correct and select Yes.
4. Select 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’.
21. Remove the check mark from the ‘Allow connections only from
computers ...’ box and click Apply.
Configure System Software The PASS-C image contains SQL server 2019 Express instance for use with
Asset Centre and other applications. This is a free edition of SQL Server, with
some limitations, a 10 GB maximum database size, and is intended for small
PlantPAx system applications.
IMPORTANT SQL Server Express has already been installed on this machine. If
you plan to use SQL Express, skip to SQL Registered Server Names. If
you plan to use SQL server 2019 Standard, continue with the next
procedure.
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.
Reporting Services Configuration Select Reporting Services Native Mode > Install and Configure
Feature Rules Select Next once the rules have passed
Complete Image Process Select Next once Complete
Complete Select Close to complete the wizard
Use the Microsoft SQL Server Management Studio to update the registered
server names. This procedure applies to SQL Express and SQL Server.
1. Log in to the computer as Administrator.
2. Navigate to Programs>Microsoft SQL Server Tool 18\Microsoft SQL
Server Management Studio 18 and launch SSMS.
IMPORTANT When using SQLEXPRESS, after you complete the initial connection,
you can change your sa password under Options.
When you change the name of the computer that is running SQL, use the
following procedure to update system metadata for remote connections. This
procedure applies to SQL Express and SQL Server.
1. In SQL Server Management Studio, select 'New Query' from the toolbar.
2. Enter the following code into the SQLQuery*.sql field, replacing old
computer name with the unconnected server name recorded earlier and
supplying the new computer name.
3. Select the 'Execute' button, from the toolbar, to run the query.
4. To verify the update, select 'New Query' from the toolbar and enter the
following code into the SQLQuery*.sql field
Use the SQL Server Management Studio to create a security login for the new
local administrator. This procedure applies to SQL Express and SQL Server.
1. Expand the Security folder and right-click the Logins folder to select New
Login.
2. Select Search.
3. Enter 'computername\administrator' in the object name box and select
Check Names.
7. For the Add Objects dialog, select the last option for the server
COMPUTERNAME\INSTANCE.
9. Select OK
Prior to deleting the old administrator, use the SQL Server Management
Studio to transfer the AssetCentre database ownership to the new
administrator.
1. To transfer AssetCentre database ownership, select ‘New Query’ from the
toolbar.
2. Enter the following code into the SQLQuery*.sql field and replace
<computername> with the current computer name.
3. Click the 'Execute' button to run the query and change ownership.
4. Expand the Security>Logins folder from the SQL Server Management
Studio configuration tree.
5. Right-click on prior or unused Administrator accounts and choose
Delete.
3. Select OK.
4. Close SQL Server Management Studio.
5. Select No for installing SQL Server 2019 Express. Edit the Database
server name to match the server that was previously installed. Leave
Installation Mode on the default configuration. Select Install.
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 Tools 18 >
Microsoft SQL Server Management Studio 18.
IMPORTANT After you complete the initial settings, change your logon and
password settings under Options.
4. Select 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.
2. Select both boxes under configure settings to configure the Network and
Local directories and click Next.
IMPORTANT Step 3 must be done twice. You have to enter a user name and
password for each directory (local and network).
4. Select Close in the summary window once complete.
From the Explorer pane, right-click the User Groups folder and choose
New>Windows-Linked User Group.
4. Select Add.
5. Select Advanced.
Configure FactoryTalk Configure FactoryTalk AssetCentre (FTAC) server settings stored in the
AssetCentre (FTAC) Server FactoryTalk Directory.
1. Navigate Programs>Rockwell Software>FactoryTalk Asset Centre
Server>Server Settings to launch the Server Setting Utility.
2. Enter a user name and password and click OK.
3. Enter the server location by typing the new computer name, then click
Apply.
PI Builder is a Microsoft Excel® add-in that lets you use Excel to create, view,
and modify PI points and Asset Framework objects in your Historian database.
With PI Builder, you can make bulk tag edits by importing and exporting your
spreadsheet.
All functionality of the prior PI Tag Configurator has been replaced with PI
Builder, which is included with the PI SMT and PI Data Archive setup kits (as
part of the PI AF Client installer).
If Microsoft Excel was installed after the Historian software, the AF Client
features will need to be modified to include the PI Builder feature.
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
12. 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.
2. Double-click Setup.exe.
3. When the Setup window displays, select Next.
8. Select Install.
9. On the EULA page, read the license agreement and click 'Accept all'.
Installation takes approximately 15 minutes.
10. Select whether to activate now or later. You must be connected to the
Internet to activate now.
11. Select 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.
1. On the desktop, double-click the shortcut to the Batch Installation file
folder.
2. Double-click Setup.exe.
3. When the Setup window displays, select Customize.
4. Check FactoryTalk eProcedure v15.00 and click Next.
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.
1. On the desktop, double-click the shortcut to the Batch Installation file
folder.
2. Double-click Setup.exe.
3. When the Setup window displays, click Customize.
5. Select Next.
6. Enter your SQL server name. Use the Default Instance, Source Name,
and Include Batch Reports.
7. Select Next.
8. Select Modify once the connection is validated.
9. On the EULA page, read the license agreement and select 'Accept all'.
10. Select Close once the modification is complete. Installation takes
approximately 3 minutes.
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\15.00.00-FTBatch-DVD
• The FactoryTalk Batch Administrator’s Guide is in your template at c:\
Program Files (x86)\Commion Files\Rockwell\Help.
Configure HMI
Once you have completed the previous tasks, see the PlantPAx DCS
Configuration and Implementation User Manual, publication PROCES-
UM100, for PASS configuration procedures, such as:
• Configuring FactoryTalk components
• Configuring HMI, DATA, and ALARM servers
• Redundant PASS considerations
• Configuring runtime security
Install OWS Operating The following steps are comparable to a retail Windows 10 Enterprise 2019
System operating system, the difference is the PASS-C ISO contains additional pre-
installed software.
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.
The Windows Out of Box Experience (OOBE) consists of displays that require
customers to accept the end users license agreement (EuLA), connect to the
internet, log in with or sign up for a Microsoft Account, and share information
with the OEM.
Complete these steps for the initial configuration of all virtual machines that
were deployed using PlantPAx image templates.
A logon message appears, prompting you to press Ctrl + Alt + Delete key
combination to unlock'.
1. DO NOT press Ctrl + Alt + Delete for a virtual machine.
2. Instead press Ctrl + Alt + Insert. This is the VMware key combination to
unlock.
3. 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 steps.
4. Select 'Yes' to allow the PC to be discoverable.
If you skipped the product key earlier, another dialog window appears to
remind you that Windows must be activated.
5. In the Product Key window, enter a valid Windows Server Product Key.
6. Verify that the product key is correct.
7. Select OK in the message window when the product key was installed
successfully.
8. Select OK in the activation window.
Configure Windows Settings 1. Login using the administrator account and password that was created in
the previous step.
2. In the Product Key window, enter a valid Windows Server Product Key
and click OK.
3. Verify that the product key is correct and select Yes.
4. Select 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’.
17. Acknowledge the prompt that changes will take effect on restart.
19. On the Remote tab, select ‘Allow remote connections to this computer’.
21. Remove the check mark from the ‘Allow connections only from
computers ...’ box and click Apply.
IMPORTANT Browse can be inactive if Network Discovery and File Share are not
enabled.
Notes:
This section discusses software activations and licenses that are required for
PlantPAx® virtual templates and ISO images.
Microsoft Product Keys The PlantPAx System 5.0 virtual templates and ISO images utilize Windows
server 2019 Standard and Windows 10 Enterprise LTSB 2019 operating
systems.
Both operating systems initially power on with the Windows Out of Box
Experience (OOBE), where you have the option to enter a product key or skip
to the next step. Subsequent boots prompt to enter a product key that must be
purchased from Microsoft to activate the operating system.
Slmgr.vbs Tool
If you want to do something more advanced like remove a product key, force
an online activation, or extend the activation timer, you need Slmgr.vbs.
Rockwell Automation For continuous use of FactoryTalk® products and other Rockwell Automation®
Activation Files 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
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 7 days. The seven-day grace period provides time to
correct the problem with acquiring activations, without disrupting critical applications. If activation is restored
Software that is not activated within 7 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 2 hours
in Demo mode.
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.
Location of activation server 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.
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
Options for adding activation files to the PASS Infrastructure Configuration User Manual, publication PROCES-UM100.
If the PASS does not have internet access, the activations can be downloaded on another computer with internet
connectivity and then transferred to the PASS.
There are two types of activation files:
Older Flexera (.LIC) non-encrypted files that are supported by older and current software versions that can be
stored locally (C:\Users\Public\Documents\Rockwell Automation\Activations) or on a Flexra USB Dongle.
Activation file types Newer CodeMeter (.wibu) encrypted files that are supported by current and future software versions that can be
stored locally (C:\ProgramData\CodeMeter\CMAct) or on a CM USB Stick.
The FactoryTalk software that is installed in the PlantPAx System 5.0 virtual templates and ISO images are
current versions that compatible with Flexera and CodeMeter activations. CodeMeter is the preferred activation
file type going forward.
Notes:
Technical Support Center Find help with how-to videos, FAQs, chat, user forums, and product notification updates. rok.auto/support
Knowledgebase Access Knowledgebase articles. rok.auto/knowledgebase
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Download firmware, associated files (such as AOP, EDS, and DTM), and access product release rok.auto/pcdc
(PCDC) notes.
Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our
content, complete the form at rok.auto/docfeedback.
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.
Allen-Bradley, ControlFLASH, ControlFLASH PLUS, eProcedure, expanding human possibility, FactoryTalk, PlantPAx, Rockwell Automation, Rockwell Software, RSLinx, RSLogix 5000, RSNetWorx, Studio
5000, Studio 5000 Architect, Studio 5000 Logix Designer, Studio 5000 Logix Emulate, and VantagePoint are trademarks of Rockwell Automation, Inc.
ControlNet and EtherNet/IP are trademarks of ODVA, Inc.
Excel, Microsoft and Windows are trademarks of Microsoft Corporation
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 EEE YÖnetmeliğine Uygundur