System 800xA

Installation, Update and Upgrade Getting Started

System Version 6.0

Power and productivity

for a better world™
 System 800xA
Installation, Update and Upgrade Getting Started

System Version 6.0

NOTICE
This document contains information about one or more ABB products and may include a description
of or a reference to one or more standards that may be generally relevant to the ABB products. The
presence of any such description of a standard or reference to a standard is not a representation that
all of the ABB products referenced in this document support all of the features of the described or ref-
erenced standard. In order to determine the specific features supported by a particular ABB product,
the reader should consult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property
in the ABB products described in this document.
The information in this document is subject to change without notice and should not be construed as
a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected, and to communicate
information and data via a secure network. It is the sole responsibility of the system/product owner to
provide and continuously ensure a secure connection between the product and the system network
and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not lim-
ited to, the installation of firewalls, application of authentication measures, encryption of data, installa-
tion of antivirus programs, and so on, to protect the system, its products and networks, against security
breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.
ABB verifies the function of released products and updates. However system/product owners are ulti-
mately responsible to ensure that any system update (including but not limited to code changes, con-
figuration file changes, third-party software updates or patches, hardware change out, and so on) is
compatible with the security measures implemented. The system/product owners must verify that the
system and associated products function as expected in the environment they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any
nature or kind arising from the use of this document, nor shall ABB be liable for incidental or conse-
quential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from
ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized pur-
pose.
The software or hardware described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license. This product meets the require-
ments specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC.

TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.

Copyright © 2003-2016 by ABB.

All rights reserved.

Release: September 2016

Document number: 2PAA111708-600 J
 Table of Contents

About this User Manual

User Manual Conventions .................................................................................................9
Warning, Caution, Information, and Tip Icons ....................................................10
Terminology .........................................................................................................11

Section 1 - Introduction
System Security .............................................................................................................13

Section 2 - System Installation

Overview..........................................................................................................................15
Environment Setup ...............................................................................................16
Node Preparation..................................................................................................16
Create System.......................................................................................................16
Configuration .......................................................................................................16
Deploy .............................................................................................................16
Environment setup ...........................................................................................................16
Prepare Nodes..................................................................................................................17
Create System ..................................................................................................................20
Add System Functions.....................................................................................................21
Add Nodes .......................................................................................................................22
Allocate Node Functions .................................................................................................23
Configure Redundancy ....................................................................................................24
Deploy Configuration ......................................................................................................26
Maintenance ....................................................................................................................28
Expand the System ...............................................................................................28
Remove Deployed Function.................................................................................29

2PAA111708-600 J 5
Table of Contents

Remove Nodes ..................................................................................................... 30

Rename Nodes ..................................................................................................... 30
Prepare Add-ons .................................................................................................. 31
Move a System..................................................................................................... 32
Troubleshooting............................................................................................................... 35
Handle Failed Deployments................................................................................. 35
Extend a Node with Missing Installation Files .................................................... 37
Repair Invalid Media on Node............................................................................. 37
Exclude Nodes ..................................................................................................... 38
Replacing a Node................................................................................................. 39
Diagnostics........................................................................................................... 39

Section 3 - System 800xA Update

Section 4 - System 800xA Upgrade

Appendix A - Prerequisites
Windows Operating System ............................................................................................ 45
Selecting the Windows Operating System........................................................... 46
Considerations for Disks and File System ........................................................... 46
Windows Installation Guidelines ......................................................................... 48
Windows Operating System Updates................................................................... 50
Configuring Network Adapters ................................................................................... 50
Configuring Domain Controller and DNS Server........................................................... 53
Installing base software........................................................................................ 53
Adding Nodes to a Domain ................................................................................. 59
Configuring Users and Groups........................................................................................ 60
New Organizational Unit ..................................................................................... 63
Groups ............................................................................................................ 64
Users, Groups, and Rights Assignments.............................................................. 64
800xA Service User .................................................................................... 68
User Account for Installation ........................................................................... 70
Other Users .......................................................................................................... 70

6 2PAA111708-600 J
 Table of Contents

Adding 800xA Domain Users to the Local Administrator Group .......................71

Operating System Setup Use with 800xA System ......................................................72
Regional and Language Options ..........................................................................73
Enable Write Caching on Hard Disks ..................................................................74
Internet Explorer as Default Browser...................................................................75
Internet Explorer Enhanced Security ...................................................................75
Internet Security Settings for Digital Signature Validation..................................76
Disable Web Browser Popup Blocker ..................................................................76
Disable Show Window Contents While Dragging ...............................................76
Energy Saver and Screen Saver Configuration ....................................................77
Virus Scanning Configuration During Installation and Post Installation .........77
Windows Update Configuration...........................................................................78
Disable Server Manager Startup ..........................................................................78
Hot fix for redundancy with IPSec enabled .........................................................78
Set Date and Time for Batch Servers ...................................................................79
Disable ISATAP Setting .......................................................................................79
Group Policy Management...................................................................................80
Adding Privileges to the 800xA Service User......................................................83
Remote (Thin) Client for the Server Operating System.......................................83
Other Third Party Software .............................................................................................84
Microsoft Office Professional ..........................................................................85
Microsoft Word ................................................................................................85
Microsoft Excel ...........................................................................................86
Crystal Reports.....................................................................................................87
Autocad Integration..............................................................................................89
McAfee Integration ..............................................................................................89
Symantec .............................................................................................................89
Bulk SPL Template ..............................................................................................89
Process Engineering Tool Integration Specific Requirements .............................90
Backup Software ..................................................................................................91

Appendix B - Installation and Configuration Parameters

Acquiring Installation and Configuration Parameters .....................................................93

2PAA111708-600 J 7
Table of Contents

Appendix C - Related Documentation

Appendix D - Installation Media

Installation Media Deliverable ...................................................................................... 103
Node Types.................................................................................................................... 104

Revision History

Index

8 2PAA111708-600 J
 About this User Manual

Any security measures described in this user manual, for example, for user
access, password security, network security, firewalls, virus protection, and so on,
represent possible steps that a user of an 800xA System may want to consider
based on a risk assessment for a particular application and installation. This risk
assessment, as well as the proper implementation, configuration, installation,
operation, administration, and maintenance of all relevant security related
equipment, software, and procedures, are the responsibility of the user of the
800xA System.
This user manual is intended to guide a user to plan and set up the nodes to install
the updates for System 800xA.It describes the flow in different phases for updating
the system.
Unless otherwise noted, the versions of all 800xA Base System and Functional Area
software described in this user manual are the latest release of 800xA 6.0.
This document does not include information on site planning, engineering planning,
software configuration, network design, security measures, tools, maintenance, and
so on that can be found in other 800xA User Manuals. Refer Appendix C, Related
Documentation.

User Manual Conventions

Microsoft Windows conventions as defined in the Microsoft Manual of Style are
normally used for the standard presentation of material when entering text, key
sequences, prompts, messages, menu items, screen elements, and so on.

2PAA111708-600 J 9
Warning, Caution, Information, and Tip Icons About this User Manual

Warning, Caution, Information, and Tip Icons

This user manual includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:

Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

Warning icon indicates the presence of a hazard which could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to
use a certain function.
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.

10 2PAA111708-600 J
 About this User Manual Terminology

Terminology
A complete and comprehensive list of terms is included in System 800xA System
Guide Functional Description (3BSE038018*). The listing includes terms and
definitions that apply to the 800xA System where the usage is different from
commonly accepted industry standard definitions and definitions given in standard
dictionaries such as Webster’s Dictionary of Computer Terms.

Term/Acronym Description
Installation Media A collection of all the files and folders that is required to install and
configure System 800xA. It can be delivered as a zip folder or on a
physical media. For example, an USB drive.
Node Type Defines what software a System node is capable of running.
Examples of Node Types are Server and Client.
Node Option Defines a package of installation files. The files are copied to a
node during the Node Preparation step.
Local Media Repository A folder where installation files for 800xA is stored on System
(LMR) nodes.
Node Preparation Tool A tool used to prepare a computer to be a node in an 800xA
(NPT) system. It checks system requirements and places installation or
update media files on a local disk. It also installs and starts the
System Installer Agent on the node.
System Installer Agent A local service on a computer that installs and configures software
(Agent) based on given commands.
System functions All configurable functions available for the 800xA System.
Node functions Node functions are sub functions of System Functions that can be
placed on nodes in the System.
Configuration A configuration is a set of System Functions, Node Functions and
nodes selected in the Configure System task. It defines where the
functions are installed in the System.
Configure System task A task that can be opened from the 800xA application 'System
Configuration Console'. It lets users configure, install and update
software in the System from a central node.

2PAA111708-600 J 11
Terminology About this User Manual

Term/Acronym Description
Deploy A functionality that executes an installation or update on System
800xA nodes. The software installed or updated during
deployment is decided based on what is configured in the System
Configuration Console (SCC) task Configure System.
System Configuration An application used for configuring System 800xA.
Console (SCC)
800xA Installer account The account used when installing any 800xA software.
800xA Service account The account used by all 800xA services.

12 2PAA111708-600 J
 Section 1 Introduction

Visual Basic Process Graphics (VBPG) is not supported in System 800xA 6.0. It
is mandatory to migrate all VBPG to PG2 graphics before upgrading to System
800xA 6.0. Plan for the migration in advance. The standard VB Graphics system
extensions and other obsolete system extensions will be deleted during Upgrade
and Update process.

System Security
It is very important to have a corporate security policy that is revised on a regular
basis. This is the responsibility of the user of the 800xA System.

Before the installation starts, make sure that Windows firewall is turned ON, and
antivirus software is running on all nodes.
This document does not contain recommendations on system security, users, user
groups, or user roles and permissions. For more information, refer the System
800xA Administration and Security (3BSE037410*), System 800xA Network
Configuration (3BSE034463*), and System 800xA System Planning
(3BSE041389*) documents.

2PAA111708-600 J 13
System Security Section 1 Introduction

14 2PAA111708-600 J
 Section 2 System Installation

Before proceeding with this chapter, make sure that all prerequisites required to
configure an 800xA System are completed, refer Appendix A, Prerequisites.

From System 800xA version 6.0, the installation procedure is automated, and can be
performed almost completely from a single node. This also enables automatic
updates of the System.
Because of this, do not perform installation of 800xA products manually. Manually
installed functions cannot be updated automatically, nor handled in any way by the
Configure System task.
However, there are some products that are not yet part of the automated installation,
and these must be installed according to provided instructions.

Overview
The installation consists of these major steps:

Figure 1. Installation Steps

2PAA111708-600 J 15
Environment Setup Section 2 System Installation

Environment Setup
In this step the Windows environment is configured, and users & groups are created
etc. All these requirements are specified in Appendix A, Prerequisites.

Node Preparation
This step prepares a node with the latest Installation Media and installs a System
Installer Agent. It is performed by running the Setup application from the
Installation Media.
This step must be performed on all nodes.

Create System
An empty 800xA System is created.

Configuration
In this step, the 800xA System's functionality is configured. It is performed by using
the Configure System task to select System Functions, Node Functions and nodes. It
also involves setting up redundancy.

Deploy
Deploy installs a configuration in a System by sending actions to the nodes. This
step is initiated from the Configure System task after the configuration step is
completed.

Environment setup
All prerequisites are defined in detail under Appendix A, Prerequisites. Verify that
they are fulfilled before proceeding to the next step. The steps below are only the
main requirements.
• Configure the network and connect all nodes.
• Set up two Windows user groups: One for 800xA Administrators and one for
normal 800xA Users. They can be created in a Domain or Workgroup.

16 2PAA111708-600 J
Section 2 System Installation Prepare Nodes

• Create an 800xA Installer account. Add it to the above groups, and to the
'Administrators' group in Windows (on domains, add it to 'Domain Admins').
Always use the 800xA Installer account when performing any 800xA software
installation.

• Create an 800xA Service account. Add it to the above groups, and to the
'Administrators' group in Windows (on domains, add it to 'Domain Admins').
This service account is used for running all 800xA services.
• Turn ON the Windows firewall.
• Set up the security policy and antivirus. See System Security on page 13.
• Verify the remaining requirements under Appendix A, Prerequisites.

Prepare Nodes
This will prepare a node with software and install a System Installer Agent, to
prepare it for centralized deployment.
Make sure the name of the node is valid for the system, that is, it does not include
any invalid characters and is no longer than 15 character. For more information
see Windows Installation Guidelines on page 48
• Get a copy of the latest Installation Media. See Installation Media Deliverable
on page 103. 
When preparing the node for an existing system the Installation Media must be
the latest media installed in the system, i.e. it can either be a complete
installation media or an update media.
When running the installation from a network share, it is required that the
installing user has access to the complete share and that it is residing on the same
Domain/Workgroup as the 800xA System to be set up. Also the length of the
actual path must be kept to a minimum. 
The network share path must be a UNC path, for example
\\FileServer\ShareName.
• Log in with the 800xA Installer account.

2PAA111708-600 J 17
Prepare Nodes Section 2 System Installation

• Launch the Node Preparation Tool (NPT) by starting the Setup application that
is available on the root of the Installation Media.

Figure 2. Node Preparation Tool (NPT)

• Enter 800xA Service account credentials, and the groups created in

Environment setup on page 16.

18 2PAA111708-600 J
Section 2 System Installation Prepare Nodes

• Open the Node Options dialog to select what to prepare the node for. Read
more about the Node Options in the Node Types on page 104.

Figure 3. Node Options

• Specify the path that contains all the medias required for the system.
If the complete current system is not represented by one single full media, then all
the separate medias that is, Add-On medias, other update medias and/or older full
media must be made available for preparation of the node. All these medias needs
to be copied to a common location that is specified in the Additional Media text
field.

Figure 4. Media Folder

2PAA111708-600 J 19
Create System Section 2 System Installation

This folder will be searched for different medias and the latest versions of the
functions will be included when preparing the node.
• Read and accept the license agreement.
• Use the Start node preparation command.
This will copy all required installation files for the selected options and install the
System Installer Agent. A progress banner will indicate how far the process has
come.

Figure 5. Progress Banner during preparation of a node

Once completed, installation of base software for the node will proceed. Which
software that is installed at this point is decided by the selection in the Node
Options dialog. This process is indicated by a new progress bar that will disappear
upon completion.
The system might reboot during the preparation.

• If the node is intended to be the primary aspect server, launch the SCC and
proceed with Create System on page 20.
Additional node types and options can be added later by following Expand the
system workflow (see Expand the System on page 28).

Create System
In order to use the functionality of System 800xA a System must be created using
the System Configuration Console (SCC) on the primary aspect server.
• Make sure that the logged in user is the 800xA Installer account.
• Go to the Create System task in the SCC.
• Give the System a name, a description and configure network filtering.

20 2PAA111708-600 J
Section 2 System Installation Add System Functions

• Use the Apply command to create the system.

This will create an empty 800xA System. The process may take a few minutes.
• Once completed, use the Finish command to close the task.
If an error occurs during system creation it is possible to get more information by
using the View log link. One common problem is that the user is not part of the
correct user groups.

Add System Functions

This configures the functions that will be available in the System. This functionality
is available in the Configure System task in the SCC in the 'System Setup' folder.
• Go to System functions tab, and use the Edit functions command to add
desired functions.
• Apply the changes and close the dialog.

Figure 6. Modify System Functions

2PAA111708-600 J 21
Add Nodes Section 2 System Installation

The configured functions are added to the list under the System Functions tab.
• Added functions may have a list of property values. Verify and change these if
required, by using the Edit link.

Figure 7. System Functions Properties

Add Nodes
This will add system nodes to the configuration. This functionality is available in
the Configure System task in the SCC under the 'System Setup' folder.
• Go to System nodes tab, and use the Add node command.
This will open a dialog for adding nodes. The dialog will show a list of nodes that
have been prepared for automatic installation. An animated icon will indicate that
the application is searching for nodes on the network.
• Select a node from the list or enter a name of a node (if it is currently
disconnected).
• Select its Node Types. This defines which functions that can be configured on
the node. Read more about Node Types on page 104.

22 2PAA111708-600 J
Section 2 System Installation Allocate Node Functions

Figure 8. Add Node

Prepared Node Types will be detected automatically on connected nodes.

• Add the node to the configuration.

The node will be added to the list of configured nodes.
It is possible to add multiple nodes at once in the Add node dialog by opening the
Multiple nodes dialog.

Allocate Node Functions

This will add functions to a specific node. This functionality is available in the
Configure System task in the SCC under the 'System Setup' folder.
• Go to System nodes tab, and select a System node in the list.
• Use the Allocate functions command.
This will open a dialog, similar to the one for System Functions, listing all available
node functions for the node.

2PAA111708-600 J 23
Configure Redundancy Section 2 System Installation

• Select desired functions in the dialog.

Figure 9. Allocate application and Service Functions

The configured functions are added to the list of Node Functions on the node.
• Added functions may have a list of property values. Verify and change these if
required by using the Edit properties link.

Configure Redundancy
This configures functional redundancy between System nodes. Having redundant
functions means that if one function on a node stops functioning, its redundant
partner will take over. This is used to ensure that the function is always available
when the System is in production.
This functionality is available in the Configure System task in the SCC under the
'System Setup' folder.

24 2PAA111708-600 J
Section 2 System Installation Configure Redundancy

• Go to System nodes tab, and select a System node in the list.

• Use the Make redundant command.
This will open a dialog for configuring redundancy.
• Select another node in the list. This is the 'redundant node'.
This will show a list of functions that can be redundant between the nodes.
• Select the functions to be redundant.
• Apply the changes and close the dialog.

Figure 10. Redundancy

2PAA111708-600 J 25
Deploy Configuration Section 2 System Installation

The name of the redundant node is now displayed in a separate column next to the
node functions.

Figure 11. Redundant Node

Deploy Configuration
In this step, the configuration will be installed on the System nodes.
This functionality is available in the Configure System task in the SCC under the
'System Setup' folder.
• Use the Deploy system command.
This will open a dialog for monitoring the deployment. All nodes participating in
the deployment are listed. The nodes can be expanded to view the System Functions
that will be installed on them.
• Ensure that there are no reserved entities in the system. Use the Find Tool in the
Plant Explorer Workplace application to identify and release any such items.
• Use the Deploy command in the dialog to start the process.
A progress bar is displayed next to each node and function, showing what is
happening on the node.
Some functions require nodes to be restarted during the deployment. This is
indicated by a small icon for each node.

26 2PAA111708-600 J
Section 2 System Installation Deploy Configuration

If there is a warning message stating that there are missing installation files,
please follow the steps under section Extend a Node with Missing Installation
Files on page 37 to resolve the problem.

Figure 12. Deploy

Hovering a progress bar with the mouse will show the action that is currently
running.

Figure 13. Deploy Progress

Once completed, a message box is displayed saying that the deployment was
successful. This indicates that all actions required to install the configuration was
successfully performed on the nodes.
• Return to the Configure System task by closing the message box.

2PAA111708-600 J 27
Maintenance Section 2 System Installation

Figure 14. Deploy Complete

Maintenance
Expand the System
It is possible to expand the system with new nodes and functions even after the
System has been deployed once.

Add a new node

• Prepare and configure Windows on the node according to the instructions in
Appendix A, Prerequisites.
• Prepare the node (see Prepare Nodes on page 17) using the NPT by starting the
Setup application from the latest media matching the installed system, i.e., if an
update has been performed on the system the media for that update is to be
used.
• Configure node functions on the node (see Allocate Node Functions on page
23).
• Configure redundancy (see Configure Redundancy on page 24).

28 2PAA111708-600 J
Section 2 System Installation Remove Deployed Function

• Use the Deploy system command to install the new node (see Deploy
Configuration on page 26).

Add New System Functions

• Follow the steps in Add System Functions on page 21.
• Use the Deploy system command to install the configuration (see Deploy
Configuration on page 26).

Add New Node Functions

• Follow the steps in Allocate Node Functions on page 23.
• Use the Deploy command from the Node actions... dropdown to install the
functions on the node.

Remove Deployed Function

There is no system support to automatically undo the actions performed during
function deployment, like un-installing the software. There is however support to
remove the stored configuration data related to the function.
When removing a function the Manual Remove command will list all actions
related to a function and it is then up to the user to manually undo them.

Remove System Function

There is no system support to remove a loaded System Extension.

To manually remove a System Function:

• Go to System Functions tab.
• Select the function, open the context menu by right clicking and then use the
Manually Remove command.
• Follow the screen prompts to complete the remove.

Remove Node Function

To manually remove a Node Function:
• Go to System nodes tab, and select a System node in the list.

2PAA111708-600 J 29
Remove Nodes Section 2 System Installation

• Select the Node Function, open the context menu by right clicking and then use
the Manually Remove command.
• Follow the screen prompts to complete the remove.

Remove Nodes
A node may be removed from the system to reduce the system footprint. Once
removed, the node is no longer part of the system.
Removing the node from the system causes all the configuration data related to
the node to be removed as well.
To remove a node:
• Go to System Nodes tab.
• Use the Remove node command from the Node actions… dropdown.
• Follow the screen prompts to complete the node removal.
To add/reconnect a removed node to the system again, the node is considered to
be a new node. That is, the node needs to be restored to its initial state and all the
steps for adding a node, configuring and deploying functions to a new node has to
be performed.
This function is not intended for node problem solving. If that is the case please
refer to Exclude Nodes on page 38 and Replacing a Node on page 39.

Rename Nodes
One or more nodes may be renamed when restoring a backup from a development
or engineering system into a production system or due to some other reason. It is
important that the name stored in the configuration matches the name in the system.
To rename a node:
• Go to System Nodes tab.
• Select the node to rename and open the Properties dialog from the Node
actions… dropdown.
• In the Properties dialog, change the name and press OK.

30 2PAA111708-600 J
Section 2 System Installation Prepare Add-ons

Prepare Add-ons
The definition of an Add-on is a System Function that was not part of the original
media, for example a language pack. Installing an Add-on on an already deployed
system consists of two steps:
• Distributing the Add-on using either manual distribution or centralized
distribution.
• Installing the added Functions following the same steps as when expanding the
system with new functions (see Add New System Functions on page 29 and
Add New Node Functions on page 29).
To distribute an Add-on already part of the system follow the instructions for
Expand the System on page 28 or Replacing a Node on page 39

Centralized preparation
This functionality is available in the Configure System task in the SCC under the
'System Setup' folder.
• Launch the Update wizard using the Updates command.
• In the Locate update media step choose Centralized media distribution and
enter the path to the Add-on Media.

Figure 15. Update System Preparation

• Follow the screen prompts to complete the Add-on distribution.

2PAA111708-600 J 31
Move a System Section 2 System Installation

Manual preparation
Refer to Prepare Nodes on page 17 for manual preparation.

Move a System
It is possible to engineer a System in one environment and then move it to another.
This can be done for various reasons, for example when commissioning a project
after configuring and engineering a System beforehand. This section describes a
workflow for achieving this.
• Create a full System backup of the engineering system's Aspect Directory.
Remember to backup any other configuration settings and files, for example
CBM settings, Saving AC800M OPC configuration etc.
• Export System Installer's 'System Configuration' aspect by using the
Import/Export function in the Plant Explorer Workplace application.
The aspect can be found under the Admin structure in Plant Explorer Workplace. It
is placed on the Domain object with the same name as the System.

Figure 16. Placement of System Configuration aspect

Deploy software for production system

• Prepare an empty Windows as an '800xA Node' by referring the workflow in
section Prepare Nodes on page 17.
Make sure the node on the production system is isolated from the system where
the backup is taken from.
• Create a System, on the aspect server of the production system, with the same
name as in the backup. Follow the workflow under section Create System on
page 20.

32 2PAA111708-600 J
Section 2 System Installation Move a System

This will create a System that will be used temporary while setting up the required
software for the move.
Do not start the Configure System task yet. If it is started and no configuration
aspect is present, an empty one will be created. If this happens, delete that aspect
and the one named 'System Configuration State' and continue to the next step.
• Import the 'System Configuration' aspect, that was exported from the system to
move, by using the Import/Export function in the Plant Explorer Workplace
application. Place it in the location corresponding to the placement in the
previous system.
• Start the Configure System task available in the SCC in the 'System Setup'
folder.
The configuration will contain all previously installed functions and nodes, but they
will all be marked with 'Not deployed' or 'Needs redeploy' in the status fields.
• If the current node has a different name compared to the previous aspect server
in the backup, it can be changed under the Node actions... dropdown menu
under Properties.
If a node appears as 'Invalid', ignore this and proceed.

• Exclude all nodes from the configuration, except for the current node. A
command for this is found under the Node actions... dropdown.
• Restart the SCC and the Configure System task.
When the task is restarted the Deploy dialog is automatically opened with all the
nodes given the old names.
• Abort and Close the Deploy dialog.
• Select the current node in the System Nodes tab and in the Node actions...
dropdown use the Replace node command.
• Follow the screen prompts to complete the replacement.
• Deploy the configuration. Refer the workflow under section Deploy
Configuration on page 26.
If an error occur during the deploy please follow the guidelines in Handle Failed
Deployments on page 35

2PAA111708-600 J 33
Move a System Section 2 System Installation

This will install all required software for the System to be identical to the original
one in the backup. This step is required in order to restore the backup without errors
at a later stage.
Some software may require manual installation, this will be revealed in a coming
step. Therefore, it can be practical to take a backup of the entire node before
proceeding.
• Once the deployment has completed successfully, close the SCC.
• Export both the 'System Configuration' and the ‘System Configuration State’
aspects by using the Import/Export function in the Plant Explorer Workplace
application.
• Start the Configuration Wizard application and select the action System
Administration to stop and then delete the 800xA System.
This will remove the temporary System and thus make room for the System in the
backup.

Restore engineering system backup

In this step the engineering system backup will be restored, and the configuration
created by the deployment in the temporary system will be imported into it.
• Use the Configuration Wizard to restore the backup into function on the new
node.

34 2PAA111708-600 J
Section 2 System Installation Troubleshooting

Once completed, the System running on the new node will be identical to the one
stored in the backup.
• Remove both the 'System Configuration' and the 'System Configuration State'
aspects from the System by using the Plant Explorer Workplace.
• Import both the 'System Configuration' and the 'System Configuration State'
(exported from the temporary System) aspects by using the Import/Export
function in the Plant Explorer Workplace application.
The Configure System task will now 'remember' that only the current node has been
deployed, and that the other nodes are still excluded.
• Use the Configure System task, available in the SCC in the 'System Setup'
folder, to include and replace the remaining nodes again and deploy the
System.
If the name of a node has been changed during the move and later on a node is to
be replaced there might be problem with Service Providers and Service Group
names not matching.
It may require to change the names in the Plant Explorer Workplace.

Troubleshooting
Handle Failed Deployments
During a deployment one or more nodes may fail to perform an action. This will
prevent the deployment from completing. The progress bar will turn red in both the
Deploy dialog, and on the progress banner displayed on the failed nodes.

Logs
Everything that has occurred on the nodes during a deployment or an update is
logged in a special folder by the Agent and the Configure System task.
Once an action has failed it is possible to view details about it by using the Details
link next to the node. In the Details window the user can use the Open Log
command to retrieve the latest log file from the node.

2PAA111708-600 J 35
Handle Failed Deployments Section 2 System Installation

It is also possible to collect all logs from the nodes in the configuration by using the
Diagnostics command (see Diagnostics on page 39).

Retry
It is possible to try correcting the issue and then use the Retry command to perform
the action again.

Manually Resolve
If it is not possible to perform the action using the Retry command, then it may be
possible to manually perform what the action was supposed to do, and then mark the
action as resolved, using the Manually resolve command.
This requires deep knowledge of how the failed function should be installed and
configured.

To manually resolve:
• Perform the failed action manually on the node. The command line can be
found in the Details window.
• Use the Details link next to the failed node in the Deploy dialog.
• Use the Manually resolve command, and follow the screen prompts to
complete.
• Once complete the node will skip the failed action and resume the deployment.
This will happen even if the action has not been performed manually.

Abort Deploy
It is possible to abort an ongoing deployment using the Abort command, solve the
deployment problem, and later start the deployment again. This will resume the
deployment from the point where it was aborted.
If it is important that the deployment completes, then it is possible to exclude the
problematic node from the current deployment by using the Exclude command.
This makes it possible to solve the problem on the node at a later stage. See Exclude
a Node During Deploy on page 38.

36 2PAA111708-600 J
Section 2 System Installation Extend a Node with Missing Installation Files

Replace Node
If none of the above solutions succeeded, the node may have to be reinstalled,
restored or replaced by a completely new node. Follow the procedure described in
Replacing a Node on page 39.

Extend a Node with Missing Installation Files

Some functions in the System requires nodes to be prepared with certain Node
Options to be able to Deploy. E.g. SQL or Oracle. If these options cannot be
detected on the node, deployment will not start.
These can be added at any time using the Node Preparation Tool (NPT).
Follow the steps in Prepare Nodes on page 17 with the exception of the steps below:
• Instead of starting the Setup application run the batch file "RepairLMR.bat".
This will open the NPT in repair mode. The file is located on the media in the
folder ...\Tools\System Installer\Node Preparation Tool on the Installation
Media.
• In the Node Options dialog also select the desired options.
• The last step to perform is the use of Start node preparation command.
The Local Media Repository (LMR) will then be updated with the required files.

Repair Invalid Media on Node

It is possible to repair the Local Media Repository (LMR) to fix inconsistencies.
This can sometimes resolve problems with nodes that are marked 'Invalid' in the
Configure System task.
Follow the steps in Prepare Nodes on page 17 with the exception of the steps below:
• Instead of starting the Setup application run the batch file "RepairLMR.bat".
This will open the NPT in repair mode. The file is located on the media in the
folder ...\Tools\System Installer\Node Preparation Tool on the Installation
Media.
• The last step to perform is the use of Start node preparation command.
The LMR will be rewritten with the required files.

2PAA111708-600 J 37
Exclude Nodes Section 2 System Installation

• If the Configure System task still indicates that there are problems with the
media on the node, some required medias was not copied to the common
location. Make sure that the common folder contains all used media, and repeat
the above steps.

Exclude Nodes
It is highly recommended to try to solve any problem that is preventing a
deployment from completing. However, there may be cases where a deployment
must be completed, even if some nodes may not be fully functional.
Examples of such cases are:
• A node does not reconnect after losing connection
• A software installation has failed and cannot be easily corrected
• Hardware failure
In such cases, the node can be excluded from the deployment. This means that the
node will not be part of any deployments nor updates until it is included again.

Exclude a Node Before Deploy

To exclude a node before deployment:
• Go to the System Nodes tab.
• Select the node to be excluded and use the Exclude/Include command under
the Node actions... dropdown.
• Follow the screen prompts to complete the node exclusion.

Exclude a Node During Deploy

To exclude a node during the deployment:
• Use the Abort command to abort the deployment, and then Close the dialog.
• Go to the System Nodes tab.
• Select the node to be excluded and use the Exclude/Include command under
the Node actions... dropdown.
• Follow the screen prompts to complete the node exclusion.

38 2PAA111708-600 J
Section 2 System Installation Replacing a Node

Replacing a Node
There might be cases when a node needs to be completely reinstalled or be replaced
by a new node. In such cases it is possible to reinstall the node according to the
already saved configuration, using the Replace node command in the Configure
System task.
This workflow can be used to resolve the following issues:
• Nodes that had a hardware failure.
• Nodes that were excluded during an update.
• Replace a node with another machine. E.g. hardware upgrade.
Any configuration or historical data stored locally on the node should be backed
up before restoring the node.

To replace a node:
• Set up a new node with (or restore a faulty node to) a clean Windows
installation. Prepare it according to the instructions in Appendix A,
Prerequisites.
• Make sure the new node has the same computer name and network
configuration as the old node.
• Prepare the node using the Installation media matching the installed system,
that is follow the steps in Prepare Nodes on page 17.
• Go to System Nodes tab in the SCC.
• Select the node to be replaced and in the Node actions... dropdown use the
Replace node command.
• Follow the screen prompts to complete the replacement.
• Use the Deploy system command to install the node with the same
configuration as before.

Diagnostics
This command may be used to collect all the installer logs from all nodes in the
system to be used for deeper problem analysis.
When contacting support the files generated from this command are usually
requested.

2PAA111708-600 J 39
Diagnostics Section 2 System Installation

40 2PAA111708-600 J
 Section 3 System 800xA Update

Updates can be executed using the System Installer as described in the System
800xA 6.0 Update Manual (2PAA114580*).

2PAA111708-600 J 41
 Section 3 System 800xA Update

42 2PAA111708-600 J
 Section 4 System 800xA Upgrade

Upgrades can be executed using the System Installer as described in following

upgrade manuals. Choose the user manual that applies to the system being
upgraded.
• System 800xA 5.1 to 6.0 Upgrade (2PAA111694*)
• System 800xA 5.0 SP2 to 6.0 Upgrade (2PAA111695*)
• System 800xA 4.1 to 5.0 SP2 Upgrade (2PAA113553*)
• System 800xA 3.1 SP2 to 5.0 SP2 Upgrade (2PAA113440*)
A direct upgrade from System Version 3.1 Service Pack 3 to System Version 6.0
is not supported. The System Version 3.1 Service Pack 3 800xA System must be
upgraded to 800xA 5.0 SP2 and then to 800xA 6.0.
A direct upgrade from System Version 4.1 to System Version 6.0 is not supported.
The System Version 4.1 800xA System must be upgraded to 800xA 5.0 SP2 and
then to 800xA 6.0.
VB based Process Graphics are not supported in System 800xA 6.0. The VB
editor is not supported and VBPG graphics can no longer be edited in 800xA 6.0.
It is mandatory to migrate all VB process graphics to PG2 graphics before
upgrading to System 800xA 6.0.
The upgrade instruction contains procedures for upgrade preparation and post
upgrade. Upgrading most Base System and Functional Area software requires
referring back to the installation instruction Create System to install that software.
This does not include information on site planning, engineering planning, software
configuration, network design, security measures, tools, maintenance, and so on that
can be found in other 800xA User Manuals.

2PAA111708-600 J 43
 Section 4 System 800xA Upgrade

44 2PAA111708-600 J
 Appendix A Prerequisites

Before the installation starts, make sure that Windows firewall is turned ON, and
antivirus software is running on all nodes.
The user performing the procedures in this section must be proficient in the use of
Windows Operating Systems. This section may not include detailed procedures
on how to perform the described settings.
There may be differences in accessing the Microsoft Operating System settings
described in this section depending on the selected operating system. It is the
responsibility of the user to consult Microsoft documentation and online help to
accurately make the settings.
Use the System 800xA 6.0 System Planning (3BSE041389*) document to help
plan the requirements, both hardware and software, for the 800xA System.
This section lists the prerequisites required to configure a node for an 800xA
System.
It is recommended to make a full backup of all disks. With such a backup all work
will be saved in the event of a disk crash or other serious malfunction. Make sure
to place proper identification on the backup media or backup files.
Install optional hardware drivers if not supplied by the Windows Operating
System (video card, network adapter, sound card, etc.).

Windows Operating System

This section describes:
• Selecting the Windows Operating System.
• Considerations for Disks and File System.
• Windows Installation Guidelines.
• Windows Operating System Updates.

2PAA111708-600 J 45
Selecting the Windows Operating System Appendix A Prerequisites

Selecting the Windows Operating System

System 800xA 6.0 version runs only on 64-bit (x64) operating systems.
The supported operating systems, service packs, and hot fixes are listed in System
800xA 6.0, 5.1, 5.0, 4.x, 3.1 Third Party Software (3BUA000500). For security
updates refer System 800xA - Third Party Security Updates Validation Status
(3BSE041902). These documents can be found in myABB/My Control System.
The US English version of the operating system is required even if a translation
NLS package for System 800xA is used.
The following conditions affect the decision on which operating system to use:
• Server roles can be allocated to nodes running either a workstation or server
operating system of Windows. Using workstation operating system helps in
keeping the cost down for smaller installations. Refer to the System 800xA 6.0
System Guide Technical Data and Configuration (3BSE041434*) for rules that
apply in selecting the type of Operating System.
• There are limitations on number of nodes used in the system when using the
Workstation Operating System for Server nodes. These limitations depend on
Microsoft licensing rules for the Workstation Operating System. Refer to
System 800xA System Guide Technical Data and Configuration
(3BSE041434*) for the details on the limitations.
• The Windows Operating System may be purchased from any Microsoft
reseller.
• The nodes with pre-installed operating system shall be checked and configured
as per the system 800xA specifications.

Considerations for Disks and File System

There are several factors that may have an impact on 800xA System performance,
for example: where the software is installed, the tendency toward fragmentation.
The following are some recommendations regarding these factors:

46 2PAA111708-600 J
Appendix A Prerequisites Considerations for Disks and File System

Multiple Disks and Partitions

Some types of 800xA servers can use significant disk I/O. Creating partitions that
are hosted by different disks or disk arrays can improve performance for these
servers. Aspect Servers, Connectivity Servers, Information Management Servers
and Batch Servers can benefit from additional partitions when configuration data is
distributed over multiple partitions that are hosted by separate disks or disk arrays.
At least two of these partitions are recommended for Information Management
Servers. See the System 800xA System Guide Technical Data and Configuration
(3BSE041434*) for specific details for Information Management and other server
types.

Installation Directory
It is generally recommended to use the Windows default location, the program files
directory on the boot disk, for installation.
A faster disk subsystem will improve performance.

Defragmenting Disks
The file system must be in a consistent state at all times. Size disks so they will be
25 percent empty for defragmentation purposes. Defragment disks on a regular basis
using the defragmentation software provided with the operating system. Check the
system for fragmented files and defragment them as required:
• On all nodes where trend and history logs reside.
• History Server disks and disks on the Connectivity Servers where trend or
history logs reside as History configuration impacts not only the History Server
disks.
• Extensive use of the Bulk Configuration tool may cause associated disks to
become fragmented.
• Configuration procedures that involve creating, deleting, and then recreating of
a large quantity of objects may cause associated disks to become fragmented.
• Deleting and then creating the Aspect System may cause associated disks to
become fragmented.

2PAA111708-600 J 47
Windows Installation Guidelines Appendix A Prerequisites

Windows Installation Guidelines

Make a fresh installation of the Windows Operating System.
Before adding applicable service packs, it is important that all the latest device
drivers are installed to match the hardware. This is especially important for elite
server hardware with special RAID hard drives and server specific hardware that
requires the latest drivers or drivers not included in the operating system media.
Follow the installation procedure as described in the documentation provided by
Microsoft.
Table 1 indicates the settings specifically required for the 800xA System
installation.

Table 1. Windows Installation Requirements

Step Description
Choosing a partition for It is recommended that all server nodes (Aspect Directory, Connectivity
installing the operating Servers, Applications Servers, etc.) use at least one additional partition for
system. the OperateItData and OperateItTemp folders. For best performance, the
additional partition should be on a separate disk or disk array from the
operating system.
There may be additional disk requirements for Applications Servers. If
installing the Information Management Server function on this node, at
least one additional NTFS partition is needed for storing historical data.
This partition can be the same as the OperateItData and OperateItTemp
partition or be a separate partition. The amount of disks, disk space, and
disk I/O needed for the Information Management node are dependent on
the final configuration for the node.

48 2PAA111708-600 J
Appendix A Prerequisites Windows Installation Guidelines

Table 1. Windows Installation Requirements (Continued)

Step Description
Computer name Make sure the name of the computer does not contain any of the below
invalid characters and do not exceed the count of 15 characters.
Invalid characters:
backslash (\)
slash mark (/)
colon (:)
asterisk (*)
question mark (?)
quotation mark (")
less than sign (<)
greater than sign (>)
vertical bar (|)
comma (,)
tilde (~)
exclamation point (!)
at sign (@)
number sign (#)
dollar sign ($)
percent (%)
caret (^)
ampersand (&)
apostrophe (')
period (.)
parentheses (())
braces ({})
underscore (_)
white space (blank)
back quote (`)
tilde (~)
equal (=)
plus (+)
open brackets ([])
semicolon (;)
Selecting Regional Refer to Regional and Language Options on page 73.
Settings
Time Zone Make sure the Automatically adjust clock for daylight saving changes
check box is enabled (if daylight saving time is used).

2PAA111708-600 J 49
Windows Operating System Updates Appendix A Prerequisites

Windows Operating System Updates

Install Windows hot fixes, and Security Updates approved by ABB (refer to Third
Party Software System 800xA (3BUA000500) and System 800xA Third Party
Security Validation Status (3BSE041902) after installing other third party software.
ABB System 800xA Qualified Security Updates (9ARD183777*) can be used to
install the latest qualified security updates. The tool and the document are accessible
from ABB SolutionBank.
The Windows Operating System Updates (Service Packs, Feature Packs) must be
installed immediately after installing the operating system, and before performing
any other procedures in this instruction.

Configuring Network Adapters

If the Network Adapter supports Receive Side Scaling this feature must be
disabled. Refer to the Network Adapter documentation for information on how to
disable the feature.
Network adapters must be installed and configured to support communication on
the client/server network. This is required on the Domain Server node, and all
800xA System nodes. Typically one network adapter will be provided with the
server or workstation hardware. It may be necessary to install a second network
adapter for redundancy.
All network adapters may be installed and configured at the same time during
system installation; however, the network will not run with redundancy until
Redundant Network Routing Protocol (RNRP) is installed (refer to Product
Installation section for a separate Domain Server node).
If the network adapters are not plug-and-play devices, the installation must be done
manually. If the Windows installation does not include the drivers for the network
adapters the driver software must be installed before the network adapters can be
configured.
The 800xA System relies on TCP/IP as its transport protocol. It is strongly
recommended that TCP/IP is the only protocol in use. If other protocols need to
be installed, make sure that TCP/IP is configured as the primary protocol.

50 2PAA111708-600 J
Appendix A Prerequisites Configuring Network Adapters

Refer to Windows Help > Networking for more information on how to install and
configure TCP/IP network adapters.
Refer to System 800xA Network Configuration (3BSE034463*) for configuration
of DNS.
The following procedure applies to the Workstation Operating System nodes. The
procedure for the Server Operating System nodes may vary from the one shown
here.
To configure the network adapters:
1. Open Windows Control Panel.
2. Double-click Network and Sharing Center to open the Network and Sharing
Center.
3. Click Change Adapter Settings.
4. Right-click on the network adapter and select Properties from the context
menu to open the Connection Properties dialog box.
5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties to open
the Internet Protocol (TCP/IP) Properties dialog box.
6. Select Use the following IP address.
7. Enter the IP address in the IP address and the subnet mask in the Subnet fields
according to the planning done in Installation and Configuration Parameter
Worksheet.
8. Enter the IP address of the default gateway in the Default gateway field (if
required by topology).
9. Enter the IP address of the Primary Domain Server in the Preferred DNS
server field.
10. Enter the IP address of the Secondary Domain Server in the Alternate DNS
server field.
Always specify the Domain Servers with their primary client/server network
addresses. This is true for all network adapters, including the ones for secondary
client/server networks.
11. Repeat for all network adapters in the servers and workstations.
Use the same DNS settings for all network adapters.

2PAA111708-600 J 51
Configuring Network Adapters Appendix A Prerequisites

12. For all interfaces on separate Control Networks three configuration changes
(compared to the default settings) must be done to reduce the amount of traffic
on the Control Network.
a. Disable IPv6 by clearing the check box Internet Protocol Version 6
(TCP/IPv6).
b. Click Properties in the Internet Protocol (TCP/IP) Properties dialog to
open the Advanced TCP/IP settings dialog.
c. Click the DNS tab.
d. Clear the check box Register this connection's addresses in DNS.
e. Click the WINS tab.
f. Select Disable NetBIOS over TCP/IP.
13. Click OK as necessary to save the newly configured values, and then click
Close to close the Connection Properties dialog box.
14. Connect the Ethernet cables. Match each of the icons with its corresponding
Ethernet connector on the server or workstation.
15. Use ping -a from a Windows command prompt to verify the server or
workstation has contact with the Domain Controller:
C:\>ping -a 172.16.40.1
Pinging MM-DC1 [172.16.40.1] with 32 bytes of data:
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Ping statistics for 172.16.40.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

The connection may not work through more than one network adapter before
RNRP is installed.

52 2PAA111708-600 J
Appendix A Prerequisites Configuring Domain Controller and DNS Server

Verify the port speed and duplex configuration on both ends (Network Adapter
and network switch). Refer to System 800xA Network Configuration
(3BSE034463*).
16. Verify the primary Client Server network is bound first for RNRP
configurations.
For Windows 8.1 and Windows Server 2012 Operating Systems: From the
Change Adapter Settings:
a. Use the Alt key to expose the Advanced Settings menu.
b. Select Advanced Settings.
c. Verify the Primary Client Server Network is bound first and the
Redundant Client Server Network is second.
d. Make corrections as needed.
Change of adapter settings are not required for Windows 10 Operating Systems.

17. Disable all unused NIC cards.

The primary NIC card can only have one TCP/IP address. If the card consists
more than one TCP/IP address, RNRP will not function correctly.

Configuring Domain Controller and DNS Server

Installing base software
This section describes how to use the Deploy functionality to install the software
required by ABB for standalone Domain Controllers.
• Prepare the Domain Controller node according to the instructions in Prepare
Nodes on page 17 but under the Node Options dialog in the NPT, select only
“Generic node”.
• Open the Configure System task in the SCC.
• Go to the System Functions tab.
• In the Edit functions dialog, select 'Diagnostics Collection Tool' and apply the
changes.

2PAA111708-600 J 53
Installing base software Appendix A Prerequisites

• Go to the System Nodes tab.

• Add the domain controller node (see Add Nodes on page 22).
• Deploy the configuration (see Deploy Configuration on page 26).
If the Domain Controller uses any network interface in addition to the ones for
the client/server network, the DNS Server need to be configured to only listen to
DNS requests on the client/server network. Perform the following for all Domain
Controllers.
• Open the Interfaces tab under Properties for the DNS Server.
• Make sure that only the IP addresses for the client/server network are
selected.
For an 800xA System installation to be used as a production system, set up a new
Domain Server with a domain specifically for the 800xA System, that will exist
independent of any other corporate domains that may already exist. Follow the
procedure in this section, starting at Active Directory Domain Services on First
Forest Root Domain Controller on page 55.
The following are general recommendations:
• One 800xA System may share the same domain with other 800xA Systems
having the same system versions.
• Generally, it is better to create a new, dedicated domain for an 800xA System
as opposed to reusing an old domain.
• Do not create subdomains and avoid complex solutions.
• Generally, it is not recommended to split two redundant Domain Controllers to
host engineering and production systems on two different locations (i.e.
network islands). Splitting two Domain Controllers will make one of the parts
incomplete since the Flexible Single Master Operations (FSMO) roles and
Global Catalog services are not redundant within Microsoft Windows.
Additional guidelines for setting up the 800xA System domain are provided in
System 800xA Network Configuration (3BSE034463*).
Before setting up a new domain, verify that the server hardware being used as the
Domain Server has the Server Operating System installed. The Workstation
Operating System can not be used for a Domain Controller or DNS server.

54 2PAA111708-600 J
Appendix A Prerequisites Installing base software

Ensure that Internet Protocol Version 4 (TCP/IP V4) is the only protocol
configured on the node.
Create a new domain by setting up a new Domain Controller and DNS server using
the Server Manager.
To set up a new domain, configure the IP addresses of the Domain Server node if
this is not already done.
• Set the IP addresses.
• Set the IP address of this computer as the Preferred DNS Server on the
primary network adapter.
• If using, or planning on using two Domain Servers, set the IP address of the
other Domain Server as the Alternate DNS Server on the primary network
adapter.
• If using a redundant network, use the same DNS settings on the secondary
network adapter.

Active Directory Domain Services on First Forest Root Domain Controller

The following procedure was prepared using Install AD DS on the First Forest Root
Domain Controller as provided by Microsoft at:
http://technet.microsoft.com/en-us/library/hh472162.aspx
The instructions included here are for the preferred method of installing Active
Directory Domain Services (AD DS). Refer to the Microsoft article if planning
on using alternate methods.

Membership in the local Administrator account is the minimum required to

complete this procedure. Details about using the appropriate accounts and group
memberships can be found at:
http://technet.microsoft.com/en-us/library/dn487460.aspx.
To install AD DS:
1. Go to Server Manager.
2. Select Add roles and features.

2PAA111708-600 J 55
Installing base software Appendix A Prerequisites

3. On Before you begin page, click Next.

4. On Select installation type page, select Role-based or feature-based
installation.
5. Click Next.
6. On Select destination server page, click select a server from the pool for
new roles.
7. Select current node, click Next.
8. On Select server roles page, select Active Directory Domain Services (AD
DS) as additional role.
9. Click Add Features on the pop-up to add other AD DS tools.
10. Click Next.
11. On Select features page, Group Policy Management feature is automatically
selected.
12. Click Next.
13. On Active Directory Domain Services page, basic information is displayed
14. Click Next.
15. On Confirm installation selections page, verify and click Install.
16. Click Notification Flag once the installation is complete.
17. Select Promote this server to a domain controller. AD DS configuration
wizard appears.
18. On Deployment Configuration page, select Add a new forest.
19. Enter Root domain name. (For Example: ABB.local)
20. Click Next.
21. On Domain Controller Options page, keep the default values.
22. Enter Directory Services Restore Mode (DSRM) password.
23. Click Next.
24. On DNS Options page, a warning message appears.

56 2PAA111708-600 J
Appendix A Prerequisites Installing base software

25. Ignore and click Next.

26. On Additional Options page, verify NetBOIS name assigned to the domain.
27. Click Next.
28. On Paths page, keep default values and click Next.
29. On Review Options page, verify all the selections made.
30. On Prerequisites Check page, verify all the checks passed.
31. Click Install.

Active Directory Domain Services on Second Forest Root Domain Controller

The following procedure was prepared using Install AD DS on the Second Domain
Controller as provided by Microsoft at:
http://technet.microsoft.com/en-us/library/jj574134.aspx
The instructions included here are for the preferred method of installing Active
Directory Domain Services (AD DS). Refer to the Microsoft article if planning
on using alternate methods.

Membership in the Domain Admins group for the domain in which the second
Domain Controller is being installed is the minimum required to complete this
procedure. Details about using the appropriate accounts and group memberships
can be found at http://technet.microsoft.com/en-us/library/dn487460.aspx.
To install AD DS on a Domain Controller in an existing domain:
1. Go to Server Manager
2. Click Add Roles in the Roles Summary dialog box.
3. Review the information in the Before You Begin dialog box (if necessary) and
click Next.
4. Select the Active Directory Domain Services check box in the Select Server
Roles dialog box and click Next.
5. Review the information in the Active Directory Domain Services dialog box
and click Next.

2PAA111708-600 J 57
Installing base software Appendix A Prerequisites

6. Click Install in the Confirm Installation Selections dialog box.

7. Click Close this wizard and launch the Active Directory Domain Services
Installation Wizard in the Installation Results dialog box.
8. Click Next in the Welcome to the Active Directory Domain Services
Installation Wizard dialog box.
9. Select Existing Forest and Add a domain controller to an existing domain
in the Choose a Deployment Configuration dialog box. Type the name of the
existing domain in the forest and then take the following actions:
a. Select My current logged on credentials or Alternate credentials under
Specify the account credentials to use to perform the installation and
click Set.
b. Provide the user name and password for an account that can install the
additional Domain Controller (it must be a member of the Enterprise
Admins group or the Domain Admins group) in the Windows Security
dialog box and click Next.
10. Select the domain of the new Domain Controller in the Select a Domain dialog
box and click Next.
11. Select a site from the list, or select the option to install the Domain Controller
in the site that corresponds to its IP address in the Select a Site dialog box and
click Next.
12. Make the following selections in the Additional Domain Controller Options
dialog box and click Next.
– DNS Server: This option is selected by default when AD DS integrates
the DNS server service in to the domain so that the Domain Controller can
function as a DNS server (this is the preferred method).
It is recommended that DNS be installed when the Active Directory Domain
Services Installation Wizard is run (keep the default selected), so that the wizard
creates the DNS zone delegation automatically.
– Global Catalog: This option is selected by default. It adds the global
catalog, read-only directory partitions to the Domain Controller, and it
enables global catalog search functionality.
– Read-only domain controller: This option is not selected by default. It
makes the additional Domain Controller read-only. For more information
about read-only domain controllers, refer to:

58 2PAA111708-600 J
Appendix A Prerequisites Adding Nodes to a Domain

http://technet.microsoft.com/en-in/library/jj574152.aspx
13. In Active Directory Domain Services Installation Wizard, navigate to
Additional Option, and in Replicate From select the Domain Node.
14. Use the default locations in the Location for Database, Log Files, and SYSVOL
dialog box and click Next.
15. Type and confirm the restore mode password in the Directory Services Restore
Mode Administrator Password dialog box and click Next.
This password must be used to start AD DS in Directory Service Restore Mode
for tasks that must be performed offline.
16. Review the selections in the Summary dialog box. Click Back if it is necessary
to change any selections.
17. Click Export settings to save the selected settings to an answer file that can be
used to automate subsequent AD DS operations.
18. Type the name for the answer file and click Save.
19. Click Next to install AD DS when the selections are accurate.
20. Click Finish in the Completing the Active Directory Domain Services
Installation Wizard dialog box.
21. A prompt appears asking to restart the server. Select either the Reboot on
Completion check box to restart the server automatically or clear the check
box to restart the server manually to complete the AD DS installation.
System 800xA Network Configuration (3BSE034463*) includes examples of a
correctly configured DNS Server.

Adding Nodes to a Domain

This is required for all member nodes in the 800xA System (not applicable for
single node installations, for example Information Management consolidation node,
or Windows Workgroups). Perform this procedure at each node that needs to be
added to the domain.
This procedure requires an administrator user name and password defined for the
domain. Have this information available before proceeding.
1. Log on to the node as a local administrator.

2PAA111708-600 J 59
Configuring Users and Groups Appendix A Prerequisites

2. Configure the IP address of this node and ensure the DNS server address points
to the IP address of the DNS server.
3. From the desktop, right-click on Start and select System from the context
menu that appears.
4. Select Change Settings.
5. Select the Computer Name tab and click Change.
6. In the Computer Name Changes dialog box, select Domain Controller.
7. Type the name of the domain in the Domain field.
8. Click OK until all dialog boxes are closed.
9. Click Yes when asked to reboot.
Repeat this procedure to add additional nodes to the domain.

Configuring Users and Groups

This section describes how to create the Windows domain users and groups in the
Active Directory on the Domain Server node.
The prerequisites to configure Users and Groups in a Domain:
• Before setting up Industrial IT users and user groups, verify that a domain has
been created by setting up a Domain Controller and DNS server as described in
Configuring Domain Controller and DNS Server on page 53.
• This procedure requires being logged in as domain administrator. A default
domain administrator is created when the Domain Controller and domain is set
up as described in Configuring Domain Controller and DNS Server on page 53.
Refer to System 800xA Administration and Security (3BSE037410*) for detailed
descriptions of users, user groups, and user roles and permissions.
Refer to Users, Groups, and Rights Assignments on page 64 for listings of
mandatory users and user groups for the 800xA System.

60 2PAA111708-600 J
Appendix A Prerequisites Configuring Users and Groups

Since the 800xA System user credential concept is built on Windows domains,
local user accounts must never be created and used on the client nodes. Clients
will always connect to the 800xA System using domain accounts. The only
exception is Windows Workgroups where domains are not used. In these cases all
users and groups are local

For 800xA Systems in a Windows Workgroup all the users and groups shall be
created locally on each node with same user group name, user name and
password.
The following procedure is used to create various domain accounts to be used in
System 800xA. Create two domain accounts with administrator privileges.
The 800xA Service User will be reserved for use by the 800xA System Services.
This account will NOT be used for installation, administration, configuration, or any
other system related procedures.
The 800xA Installer account must be created to complete the 800xA System
software installation and post installation procedures. Create other user accounts for
other 800xA System activities such as Application Engineer, System Engineer, and
Operator.
Define separate accounts and different passwords for the 800xA Service User and
the 800xA Installation User.

Domain Administrator users are powerful for administrative purposes but could
by this also be dangerous from a security perspective. For security reasons the
number of users in the Domain Administrator group should be kept to a
minimum.
The 800xA Service User and 800xA Installation User do not need to be members
of the Domain Administrators group. They both need to be members of the 
Built-in Administrators group on the 800xA System nodes but not on the Domain
Controller, unless it is combined with an 800xA Server.
The 800xA Installation User could be a Domain Administrator but should be set
to passive after the installation of the System. The 800xA Service User should not
be a Domain Administrator and also not a local administrator on the Domain
Controller.

2PAA111708-600 J 61
Configuring Users and Groups Appendix A Prerequisites

The various users and groups required by the 800xA System are described in
Table 2. All groups/users must reside on the 800xA System domain.
This setup may be performed by yourself, or the domain administrator may perform
the setup. In either case, use the guidelines in Table 2, and follow the step-by-step
procedures following Table 2.

Table 2. Domain Groups/Accounts Required by 800xA System

Groups/Users
IndustrialITAdmin Group
IndustrialITUser Group
800xA Service User
Description
Create the IndustrialITAdmin Group. All 800xA System
administrators (including the 800xA Service User) must be
a member of the IndustrialITAdmin group.
Create the IndustrialITUser Group. All 800xA System
users must be a member of the IndustrialITUser group.
Create a new user for 800xA System services. Make this
user a member of the IndustrialITAdmin Group, the
IndustrialITUser Group, and the local administrator group
on every system node.
All 800xA System services will run under this account.
Make the name easy to recognize (for example:
800xAService).
NOTE 1: Creating this user requires being logged in as
domain administrator. Adding this user to the local
administrator group on every system node requires being
logged in as local administrator.
NOTE 2: The 800xA Service User must not be a member
of the Domain Administrator group. These users should be
members of the Built-in Administrators group on the
Domain Controller node.

62 2PAA111708-600 J
Appendix A Prerequisites New Organizational Unit

Table 2. Domain Groups/Accounts Required by 800xA System (Continued)

Groups/Users Description
Installation User Create a user for installing software, and performing
system administration procedures. Make this user a
member of the IndustrialITAdmin Group, the
IndustrialITUser Group, and the local administrator group
on every system node.
NOTE 1: Creating this user requires being logged in as
domain administrator. Adding this user to the local
administrator group on every system node requires being
logged in as local administrator.
Other 800xA System users Create additional users for system configuration and
operation. These users are added to the IndustrialITUser
Group. Refer the System 800xA 6.0 Administration and
Security (3BSE037410*) for more information on user
permissions.

New Organizational Unit

This organizational unit is not mandatory; however, it may be helpful to put all
800xA System groups and users into one container. To create a new unit:
1. Go to:
Administrative Tools > Active Directory Users and Computers
2. In the left pane, right-click on the newly created domain server name, and
select:
New > Organizational Unit
from the context menu that appears.
3. Assign this organization unit the name Industrial IT.

2PAA111708-600 J 63
Groups Appendix A Prerequisites

Groups
This procedure assumes the Industrial IT organization unit has been created.

To create the required groups:

1. Right-click on the Industrial IT folder in the left pane and select:
New > Group
from the context menu that appears.
2. Use the New Object - group dialog box to assign the group a name (for
example, IndustrialITAdmin).
3. Set the Group scope to Global, and the Group type to Security.
4. Perform Step 1 through Step 3 for each of the two required groups:
– IndustrialITAdmin.
– IndustrialITUser.
It is recommended to keep the default names of these groups. Systems with Batch
Management should create the groups with default names IndustrialITAdmin and
IndustrialITUser.

Users, Groups, and Rights Assignments

This topic defines the default User Groups and Users for the 800xA System.
Windows Workgroups set up the same groups and users as a domain. The user rights
are also the same as in a domain, except all domain policies must be defined on each
local node. No additional policies are required for Windows Workgroups.
Ensure that the User Account names do not exceed the 20 character limit.

64 2PAA111708-600 J
Appendix A Prerequisites Users, Groups, and Rights Assignments

User Groups and Users

All users must be members of the IndustrialITUser group if they require the
ability to start a workplace.
Table 3 lists the default User Groups and Users.

Table 3. Default User Groups and Users

Organizational
User Group User Account Description
Unit
Industrial IT IndustrialITAdmin 800xAService 800xA System service account
800xAInstaller 800xA System installer account
Administrator System installer default account
Customer Admin Additional customer administrators
IndustrialITUser 800xAService 800xA System service account
800xAInstaller 800xA System installer account
Operator Default operator 1
Operator2 Default operator 2
Administrator Windows default administrator
account
NOTE: System 800xA does not
require this account and it is
disabled by default. Enable the
account if needed.
Customer Users Additional customer users

2PAA111708-600 J 65
Users, Groups, and Rights Assignments Appendix A Prerequisites

Local Groups and Members on Each Node

Table 4 lists the local and domain User Groups and Users for each system node.

Table 4. Local Groups and Members on Each Node in System

Local Group/User Domain Group/User

Administrators (standard default) 800xAService
800xAInstaller
HistoryAdmin 800xAService
800xAInstaller
Customer Admin (User can add additional domain
users to group to allow administration of Oracle and
Information Management IM Services)
ORA_DBA 800xAService
800xAInstaller
Customer Admin (User can add additional domain
users to group to allow administration of Oracle and
Information Management IM Services)

User Rights Assignment

Table 5 lists the user rights assignment.
In case of an Aspect Server combined with a Domain Controller, create a new
Group Policy Object under the Domain Controller object and configure the
security policies listed in Table 5.
The user rights in the Windows security policies shall be configured in 800xA
System to enable users with right permissions to perform various activities in the
system.
For systems using Domain Controllers the user rights assignment security policies
are to be configured from the below location on the Primary Domain Controller:
1. Go to Control Panel > Administrative Tools > Group Policy Management

66 2PAA111708-600 J
Appendix A Prerequisites Users, Groups, and Rights Assignments

2. Right click Group Policy Management and select Edit...

3. Navigate to Computer Configurations > Policies > Windows Settings >
Security Settings > Local Policies and click User Rights Assignment
For Systems in Workgroup environment configure the user rights assignment
security policies on each node in the below location:
1. Go to Control Panel > Administrative Tools >Local Security Policy.
2. Navigate to Security Settings > Local Policies > User Rights Assignments.
The security policies listed in Table 5 can be configured by performing the
following on each Security policy under User rights Assignment:
1. Double click on the policy
2. Click Add User or Group... button to add the user or groups as per Table 5.
3. Click OK to close the policy.

Table 5. User Rights Assignments

Policy Security Setting

Local Security Policy (each node)
Access this computer from the network IndustrialITUser
Allow log on locally IndustrialITAdmin
Change the system time IndustrialITAdmin
Log on as a batch job 800xAService
800xAInstaller
Log on as a service 800xAService
800xAInstaller
Impersonate a client after authentication SERVICE (Default)
Administrators (Default)
Users that require logover (Process Portal)

2PAA111708-600 J 67
800xA Service User Appendix A Prerequisites

Table 5. User Rights Assignments (Continued)

Policy Security Setting

Additional Local Security Policies on Batch Server
Act as part of operating system 800xAService
Adjust memory quotas for a process
Bypass traverse checking
Replace a process level token
Additional Local Security Policies for Harmony/Melody Servers
Act as part of operating system 800xAService
Generate security audits
Impersonate a Client after Authentication

800xA Service User

Define separate accounts and different passwords for the 800xA Service User and
the 800xA Installing User.

This procedure assumes the Industrial IT organization unit has been created.

Creating this user requires being logged in as domain administrator. Adding this
user to the local administrator group on every system node requires being logged
in as local administrator.
Create the 800xA Service User. This is the user account that all 800xA System
services will run under. Make this new user a member of the following groups:
• IndustrialITAdmin Group
• IndustrialITUser Group
• Local Administrator group on every system node
• Built-in Administrators group on the Domain Controller node.
To create this user:

68 2PAA111708-600 J
Appendix A Prerequisites 800xA Service User

1. Right-click on the Industrial IT organizational unit in the left pane and select:
New > User from the context menu that appears.
2. In the New Object - User dialog box specify the user name and login name.
Make the name meaningful and easy to recognize (for example:
800xAService).
3. Click Next when finished.
4. Specify the user password. Enable the Password never expires check box, and
make sure the password for this user is NEVER CHANGED.
5. Click Next when finished with the password specification.
6. Click Finish in the next dialog box to complete the user specification.
7. Make this user a member of the IndustrialITAdmin Group.
a. Select the Industrial IT organizational unit in the left pane.
b. Right-click on the IndustrialITAdmin group in the right pane and choose
Properties from the context menu that appears (or double-click the group
name).
c. Select the Members tab in the Properties dialog box.
d. Click Add. This displays the Select Users, Contacts, or Computers dialog
box.
e. Select the new user (for example, 800xAService) and click Add.
f. Repeat Step e to add other users to the IndustrialITAdmin group.
g. Click OK when finished.
h. Click OK on the Members tab of the Properties dialog box.
8. Add this user to the Builtin Administrators group on the Domain Controller
node.

2PAA111708-600 J 69
User Account for Installation Appendix A Prerequisites

9. Add this user to the local administrator group on every system node.
In order to limit the abilities of the 800xA Service User, the 800xA Service User
may be included in the Deny Logon Locally policy on every system node.
However, this will prevent logging in as the 800xA Service User on Report
Scheduling Server nodes (Scheduling Server nodes that need to run Excel
reports), on 800xA for Melody and 800xA for Harmony. On these nodes, the
800xA Service User must be logged in to add the DataDirect add-ins to Excel for
this user; to carry out the post installation and configuration of Melody and
Harmony. In such cases, the 800xA Service User may be included in the Deny
Logon Locally policy after adding the add-ins, but not before.

User Account for Installation

Define separate accounts and different passwords for the 800xA Service User and
the 800xA installing User.

Create an administrator account for installing all 800xA System software and
performing all post installation procedures. Follow the procedure for 800xA Service
User on page 68. The only difference is that this account should be configured so
that the password will expire, and will need to be changed periodically.

Other Users
Add other IndustrialIT users and make them members of the IndustrialIT User
Group. Set passwords according to company policy, and change them frequently.
Examples of users who can be members of the IndustrialITUser groups is as shown
in Table 6.
Ensure that the User Account names do not exceed the 20 character limit.

Do not change the 800xAService user passwords.

70 2PAA111708-600 J
Appendix A Prerequisites Adding 800xA Domain Users to the Local Administrator Group

Table 6. Examples for User accounts

User Account Descriptions

ApplicationEng Default application engineer
SystemEng Default system engineer
MaintenanceSup Default maintenance supervisor
MaintenanceEng Default maintenance engineer
MaintenanceTech Default maintenance technician

Adding 800xA Domain Users to the Local Administrator Group

The 800xA Service User and 800xA Installing User accounts defined in the domain
must be added to the local Administrator Group on every node in the domain,
including the Domain Controller node. The different procedures to be followed
depend on the node type:
• Domain Controller Node
• On All Other Nodes

Domain Controller Node

1. Go to Control Panel > Administrative Tools
2. Select Active Directory Users and Computers to launch the Active Directory
Users and Computers dialog box.
3. In the left pane, navigate to:
Active Directory Users and Computers > Domain Name > Built-in
4. Select Administrators in the right pane to launch the Administrators
Properties dialog box.
5. Select the Members tab.
6. Click Add. This opens the Select Users, Computers or Groups dialog box.
7. Click Locations, select the domain in the Locations dialog box and click OK.

2PAA111708-600 J 71
Operating System Setup Use with 800xA System Appendix A Prerequisites

8. Enter the names of the 800xA Service User and Installing User in the text box
and click Check Names.
9. When the dialog box indicates the names have been found, click OK.
10. To finish, click OK in the Administrators Properties dialog box.

On All Other Nodes

1. Log on as a local administrator.
2. From desktop right-click Start and select Computer Management from the
context menu that appears.
3. The Computer Management dialog box appears. In the left pane, navigate to:
Computer Management (Local) > System Tools > Local Users and Groups
> Groups
4. Click Administrators to open the Administrators Properties dialog box.
5. Click Add. This opens the Select Users, Computers or Groups dialog box.
6. Click Locations, select the domain in the Locations dialog box and click OK.
7. Enter the names of the 800xA Service User and Installing User in the text box
and click Check Names.
8. When the dialog box indicates the names have been found, click OK.
9. To finish, click OK in the Administrators Properties dialog box.

Operating System Setup Use with 800xA System

The following procedures should be carried out in domain account with
Administrator rights (For example: 800xAInstaller).
The following settings are required for use with the 800xA System:
• Regional and Language Options
• Enable Write Caching on Hard Disks
• Internet Explorer as Default Browser
• Internet Explorer Enhanced Security

72 2PAA111708-600 J
Appendix A Prerequisites Regional and Language Options

• Internet Security Settings for Digital Signature Validation

• Virus Scanning Configuration During Installation and Post Installation
• Disable Show Window Contents While Dragging
• Energy Saver and Screen Saver Configuration
• Virus Scanning Configuration During Installation and Post Installation
• Windows Update Configuration
• Disable Server Manager Startup
• Hot fix for redundancy with IPSec enabled
• Set Date and Time for Batch Servers
• Disable ISATAP Setting
• Group Policy Management
• Adding Privileges to the 800xA Service User
• Remote (Thin) Client for the Server Operating System

Regional and Language Options

Perform the following procedure to set the regional and language options. These
procedures must be performed for all users on all nodes in the 800xA System.
The procedure differs depending on the operating system. The procedures described
for all other supported operating systems:
1. Open Windows Control Panel.
2. Click Clock, Language, and Region to verify Region and Language
preferences.
3. Click Region and select Formats tab.
4. Select and verify that English (United States) is selected in the Format section.
5. Click Additional settings... to launch the Customize Format dialog box.
6. Verify that the value in the Decimal symbol field drop-down list is a dot (.). If
it is not, change it to a dot (.) and click Apply and then OK.

2PAA111708-600 J 73
Enable Write Caching on Hard Disks Appendix A Prerequisites

7. Click the Administrative tab.

8. Click Change system locale... to launch the Region Settings dialog box.
9. Verify that the value in the Current system locale drop-down list is English
(United States). If it is not, change it to English (United States) and click OK
to return to the Administrative tab of the Region dialog box.
10. Click Copy settings to launch the Welcome Screen and New User Accounts
Settings dialog box.
11. Enable the Welcome screen and system accounts and New User Accounts
check boxes and click OK.
12. Click OK to exit the Region dialog box.
13. Close Windows Control Panel.

Enable Write Caching on Hard Disks

To ensure Aspect Directory integrity, the write cache buffer flushing must be left
enabled in the Microsoft Windows Operating System. Depending on the
configuration, choice of driver, type of hard disks, etc, Windows may allow
disabling the write cache buffer flushing on the hard disks to improve performance.
For data integrity this otherwise performance increasing option must not be used.
System 800xA configuration and application data is stored in the Aspect Directory.
The Aspect Directory is transaction driven and enforces a two-phase-commit
scheme. As part of that scheme it ensures that data is written to disk prior to
considering the transaction complete. This behavior is used by several other third-
party databases.
A flush command is used to ensure that data is written to the disk.It is possible to
configure the disk driver to neglect the flush command. This is normally configured
in the Windows disk drives setting.
A consequence of, for example, a power or hardware failure can be that a flushing is
not performed. Potentially the Aspect Directory can then become inconsistent and
the system will no longer start. Furthermore the data and applications become
impossible to recover.
Refer to Microsoft Knowledge Base article 234656 for more information.
Perform the following procedure on all the Server Operating System hard disks:

74 2PAA111708-600 J
Appendix A Prerequisites Internet Explorer as Default Browser

1. Launch the Computer Management Console.

2. Select Device Manager in the left pane.
3. Select and navigate through Disk drives in the right pane.
4. Right-click the hard drive and select Properties from the context menu to
launch the hard drive properties dialog box.
5. Select Policies tab.
6. Select the Enable write caching on the device check box for Server and
Workstation Operating System.
For Virtual Nodes: Select Better Performance check box to enable write
caching.
7. Click OK.
8. Close the Computer Management Console.
It may be necessary to verify the Enable write caching on the disk check box is
still enabled after rebooting.

Internet Explorer as Default Browser

Currently System 800xA does not support Microsoft Edge, hence on Windows 10
Professional Operating systems follow the steps below to set Internet Explorer as
default browser.
The Internet Explorer must be set as default browser on all the domain accounts.
Perform the following steps:
1. Open Internet Explorer.
2. Click Tools tab to open the Internet Options.
3. Click Programs tab, then click Make Internet Explorer the default browser.
4. This will open Set Default Programs window > select Internet Explorer and
press Set this program as default.
5. Press Ok to close the window.

Internet Explorer Enhanced Security

The Internet Explorer Enhanced Security component must be disabled on all the
Server Operating System nodes.

2PAA111708-600 J 75
Internet Security Settings for Digital Signature Validation Appendix A Prerequisites

Perform the following steps:

1. Open Server Manager.
2. Select Local Server.
3. In Properties, select Internet Explorer Enhanced Security Configuration.
4. Select Off radio button for Administrators and Users.
5. Click OK.

Internet Security Settings for Digital Signature Validation

Perform the following steps on all 800xA nodes:
1. Go to Control Panel.
2. On All Control Panel Items, select Internet Options.
3. In the Internet Properties, click Advanced tab.
4. Scroll to Security and under Security clear the Check for publisher’s
certificate revocation check box.
5. Click Apply and OK.

Disable Web Browser Popup Blocker

Internet Explorer offers web browser popup blocker by default. Disable Popup
Blocker where the thin client portions of the integrated applications (specifically
Asset Optimization) are used, since these applications open child window browsers
to display application data for the user.

Disable Show Window Contents While Dragging

To prevent CPU intensive redrawing of the window, disable the Windows Show
Window Contents while dragging feature.
1. Open This PC.
2. Right-click and select Properties from the context menu to launch the System
Properties dialog box.
3. Select the Advanced System Settings.

76 2PAA111708-600 J
Appendix A Prerequisites Energy Saver and Screen Saver Configuration

4. Click Settings in the Performance frame to launch the Performance Options

dialog box.
5. Select the Visual Effects tab (this should be selected when the dialog box is
launched).
6. Select the Custom option.
7. Clear the Show Window Content while Dragging check box.
8. Click Apply, wait, and then click OK to close the Performance Options dialog
box.
9. Click OK to close the System Properties dialog box.

Energy Saver and Screen Saver Configuration

It is recommended to NOT have any Energy Saving and screen saver functionality
activated on 800xA System nodes (especially operator Workplace Clients), as this
might lead to longer reaction times in case of an emergency. If the server or
workstation BIOS has an Energy Saver configuration, configure it on a node-by-
node basis. The Windows energy saving data is user dependent.
The energy saving setting may be accessed in two ways. The BIOS setup is
available whenever the server or workstation is powered up. It may also be accessed
via Power Options in Windows Control Panel. The screen saver may be turned off in
the Display Properties option in Windows Control Panel.

Virus Scanning Configuration During Installation and Post Installation

The user should make sure that the installation procedure completes without
exposing the computers to malware or malicious network traffic of any sort.
This can only be done by limiting the communication to the system and by
performing separate virus scanning of any portable media or disks before
connecting them to the system nodes during the installation. After completing the
system installation and configuration (post installation) it is recommended to
perform a full virus scan of all computers in the system.
For better performance during 800xA installation and post installation procedures
disable virus scanning software. For virus scanners recommended by ABB for use
with System 800xA refer McAfee Integration on page 89 and Symantec on page 89.

2PAA111708-600 J 77
Windows Update Configuration Appendix A Prerequisites

Windows Update Configuration

Automatic Windows Updates are not recommended for the 800xA node. The
information on service packs, hot fixes are listed in System 800xA 6.0, 5.1, 5.0, 4.x,
3.1 Third Party Software (3BUA000500). For security updates refer System 800xA -
Third Party Security Updates Validation Status (3BSE041902). These documents
can be found in myABB/My Control System.
To disable the automatic updates by setting the Windows Automatic Updates feature
to never check for updates on Windows 8.1 operating systems:
1. Open Windows Update
2. In the left pane, click Change Settings
3. Under Important Updates choose Never check for updates
For Windows 10, automatic updates cannot be disabled. However, upgrades to
Windows 10 machines should be deferred.
To defer upgrades follow the steps below
1. Go to Settings, Update and Security, Windows Updates.
2. Select Advanced Options.
3. Select option Defer Upgrades.

Disable Server Manager Startup

Perform the following procedure to disable Server Manager not to start
automatically.
1. Open Server Manager.
2. Click Manage tab and select Server Manager Properties.
3. Select Do not start Server Manager automatically at logon and click OK.

Hot fix for redundancy with IPSec enabled

For Client Server Network redundancy to work the following hot fix (KB3007072)
needs to be installed on all nodes in an 800xA System. This hot fix is available on
the 800xA media in the following path:
…\3rd_Party_SW\Microsoft\Windows8.1-KB3007072-x64.msu

78 2PAA111708-600 J
Appendix A Prerequisites Set Date and Time for Batch Servers

Set Date and Time for Batch Servers

Batch Primary and Redundant servers require a specific time format for the service
account. All other users on the batch server and other nodes can keep the US -
English defaults.
Perform the following to verify/modify the formats for the <800xA Service
Account> on the batch servers:
1. Login to the <800xA Service Account> on the Primary/Secondary Batch
server.
2. Open Windows Control Panel (Category view).
3. Click Clock, Language, and Region to set the date and time.
4. Click Date and Time, Date and Time dialog appears.
5. Click Change date and time.., to change the date and time.
6. Click OK and Apply to save the changes.
7. Click OK to close the window.
8. Click Region, Region dialog appears. Perform the following to set the formats
for Date and Time:
a. Click the Format tab.
b. The default value for the Short Date format is M/d/yyyy. Change the Short
Date format to MM/dd/yyyy and click Apply.
c. The default Short time format is hh:mm tt. Change the value to HH:mm
and click Apply.
9. Click Apply.

Disable ISATAP Setting

Perform the following procedure on all nodes (800xA or non-800xA) connected on
the same network as the AC 800M Controllers:
1. Open Command prompt with “Run as administrator”.

2PAA111708-600 J 79
Group Policy Management Appendix A Prerequisites

2. At the command line, to check current ISATAP setting, enter:

netsh interface isatap show state
(Probably responds ISATAP State: default)
3. At the command line, to Disable ISATAP, enter:
netsh interface isatap set state disabled

Group Policy Management

The group policy management procedures differ depending on the environment
(domain or Windows Workgroup).

Domain Environment
Perform this procedure before installing 800xA System and Functional Area
software.

Group Policy. This procedure must be performed on the Primary Domain

Controller. It should be performed after all 800xA System nodes have been added to
the domain so that the new Group Policy will replicate out to all nodes in the
selected domain via the active directory. However, if the system is expanded at a
later time, the Group Policy will replicate to the nodes added during the expansion.
1. Open Group Policy Management Console.
Do not modify the default Group Policy Object itself. Create, link and modify a
new Group Policy Object.

2. Navigate to the following in the left pane of the Group Policy Object Editor:
Forest:domain name >Domains >domain name >Group Policy Objects
3. Right-click on Group Policy Objects in the left pane of the Group Policy
Management Console, and select Create a GPO in this domain from the
context menu to open the New GPO dialog box.
4. Type in a name for the new Group Policy Object in the New GPO dialog box;
for example, IntranetName and click OK to return to the Group Policy
Management Console.
5. Right-click on the new Group Policy Object in the left pane of the Group
Policy Management Console, and select Edit from the context menu to open
the Group Policy Object Editor.

80 2PAA111708-600 J
Appendix A Prerequisites Group Policy Management

6. Navigate to the following in the left pane of the Group Policy Object Editor:
User Configuration > Policies > Administrative Templates > 
Windows Components > Internet Explorer > 
Internet Control Panel > Security Page
7. Double-click Turn on automatic detection of intranet, a dialog box appears.
8. Click Disabled and click OK.
9. Double-click Intranet Sites: Include all local (intranet) sites not listed in
other zones, a dialog box appears.
10. Click Enabled and click OK.
11. Double-click Intranet Sites: Include all sites that bypass the proxy server, a
dialog box appears.
12. Click Disabled and click OK.
13. Double-click Intranet Sites: Include all network paths (UNCs), a dialog box
appears.
14. Click Disabled and click OK.
15. Close the Group Policy Object Editor.
16. Reboot the node.

Adding Workstations to the Domain Policy

Perform the following in order to prevent any user from being able to add
workstations to the domain.
1. Open Group Policy Management Console.
2. Navigate to the following:
Forest: Domain Name > Domains > Domain Name > Group Policy
Objects > Default Domain Controllers Policy
3. Right-click Default Domain Controllers Policy and select Edit from
the context menu to launch the Group Policy Management Editor.
4. Navigate to the following:
Default Domain Controllers Policy > Computer Configuration
Policies > Windows Settings > Security Settings > Local Policies >
User Rights Assignment

2PAA111708-600 J 81
Group Policy Management Appendix A Prerequisites

5. In the right pane, double-click Add workstations to domain to launch the

Add workstations to domain Properties dialog box.
6. Select Authenticated Users and click Remove.
7. Click Add User or Group to launch the Add User or Group dialog box.
8. Click Browse to launch the Select Users, Computers, or Groups dialog box.
9. Select the users and/or groups that are to have the authority to add workstations
to the domain and click OK twice to return to the Add workstations to domain
Properties dialog box.
Click Find Now in the Select Users, Computers, or Groups dialog box to display
the available users and groups.
10. Click Apply and then OK to close the dialog box.
11. Close the Group Policy Management Editor.

Windows Workgroup Environment

Perform this procedure before installing 800xA System and Functional Area
software.

Group Policy. This procedure must be performed on every node in the Windows
Workgroup. If the system is expanded at a later time, this procedure must be
performed on each node added during the expansion.
1. Open Local Group Policy Editor.
2. Navigate to the following in the left pane of the Group Policy Object Editor:
User Configuration > Administrative Templates > 
Windows Components > Internet Explorer > 
Internet Control Panel > Security Page
3. Double-click Turn on automatic detection of intranet, a dialog box appears.
4. Click Disabled and click OK.
5. Double-click Intranet Sites: Include all local (intranet) sites not listed in
other zones, a dialog box appears.
6. Click Enabled and click OK.

82 2PAA111708-600 J
Appendix A Prerequisites Adding Privileges to the 800xA Service User

7. Double-click Intranet Sites: Include all sites that bypass the proxy server, a
dialog box appears.
8. Click Disabled and click OK.
9. Double-click Intranet Sites: Include all network paths (UNCs), a dialog box
appears.
10. Click Disabled and click OK.
11. Close Local Group Policy Editor.
12. Reboot the node.

Adding Privileges to the 800xA Service User

This procedure only applies to the following node types. If these node types are not
present in the system this procedure can be skipped.
• 800xA for AC 870P/Melody Configuration Server nodes.
• 800xA for AC 870P/Melody Connectivity Server nodes.
There are some services that run under the 800xA Service User account for the listed
node types. Perform the following procedure to add the proper privileges to the
800xA Service User account.
1. Log off the 800xA Installation User account.
2. Log on the 800xA Service User account.
3. Log off the 800xA Service User account.
4. Log on the 800xA Installation User account.

Remote (Thin) Client for the Server Operating System

Perform the following procedure to install the Terminal Server role service and
configure the Terminal Server to host programs:
1. Go to Server Manager.
2. Select Add roles and features.
3. On Before you begin page, click Next.

2PAA111708-600 J 83
Other Third Party Software Appendix A Prerequisites

4. On Select installation type page, select Role-based or feature-based

installation.
5. Click Next.
6. On Select destination server page, click select a server from the pool for
new roles.
7. Click Next.
8. On Select server roles page, select Remote Desktop Services as additional
role.
If Terminal Services is already installed on the server, the Terminal Services
check box will be selected and dimmed.
9. Click Next.
10. On Select features page, click Next without changing the features.
11. On Remote Desktop Services page, click Next.
12. On Select role services page, select Remote Desktop Licensing role.
If installing the Terminal Server role service on a Domain Controller, a warning
message indicating that Installing the Terminal Server role service on a Domain
Controller is not recommended will appear.
13. Click Add Features and click Next.
14. Verify the added roles and features on Confirm installation selections page
and click Install.
15. Restart the node when the installation is complete.

Other Third Party Software

This section details the installation of other third party software that are required for
the 800xA System.
All 800xA installation must be carried out in 800xA Installer account.

84 2PAA111708-600 J
Appendix A Prerequisites Microsoft Office Professional

Microsoft Office Professional

The 800xA System supports the U.S. English, 32-bit version of the Microsoft
Office Professional 2010 or 2013 or 2016.

Microsoft Word
When installing Microsoft Word it is required to select Office Shared Features
from the Installation Options dialog box and to accept the default subfeatures
under the Office Shared Features selection.
Microsoft Word, which is part of the Microsoft Office Professional suite, must be
installed on all nodes where the following functions will be used:
• Process Graphics (for Reference Documentation Tool)
• Engineering Studio (for Document Manager Functions)
• Control Builder M (for Project Documentation Functions)
This software is available from any Microsoft reseller. Follow the installation
procedure described in the documentation provided by Microsoft.

Macro Security for Microsoft Word

Perform the following procedure for every Industrial IT User on every node, after
installation of Microsoft Word and before continuing installing or working on the
Engineering Platform:
1. Start Microsoft Word.
2. Click the File menu in the left corner.
3. Click Word Options to open the Word Options dialog box.
4. Select Trust Center in the left pane of the Word Options dialog box.
5. Click Trust Center Settings to open the Trust Center.
6. Select Macro Settings in the left pane of the Trust Center.
7. Select Disable all Macros Except Digitally Signed Macros in the right pane
of the Trust Center.
8. Click OK to close the Trust Center.
9. Click OK to close the Word Options dialog box.

2PAA111708-600 J 85
Microsoft Excel Appendix A Prerequisites

10. Repeat this procedure for every Industrial IT User on every node.

Microsoft Excel
When installing Microsoft Excel 2010 or 2013 or 2016 it is required to select
Office Shared Features from the Installation Options dialog box and to accept the
default subfeatures under the Office Shared Features selection.
When installing Microsoft Excel, select the Custom installation. When the
Installation Options dialog box appears. select the Visual Basic for Applications
option under Shared Features.
Open Microsoft Excel and perform the recommended settings, if prompted.
Navigate to File > Options > General, and clear the Show the start screen
when this application starts check box.
Microsoft Excel, which is part of the Microsoft Office Professional suite, must be
installed on all 800xA System nodes where engineering tools or Excel based reports
will be used. This can include the following:
• Process Graphics (for Display Documentation Tool)
• Engineering Studio (for Bulk Data Manager Functions)
• DataDirect - Excel Data Access
• Information Management
• Asset Optimization Server
• Batch Management
• 800xA for Harmony
• 800xA for AC 870P/Melody
This software is available from any Microsoft reseller. Follow the installation
procedure described in the documentation provided by Microsoft.

Initializing Microsoft Excel on the Information Management

Servers
Microsoft Excel must be initialized before the Information Management (IM) server
is deployed to the IM server node. Perform the following steps for the 800xA

86 2PAA111708-600 J
Appendix A Prerequisites Crystal Reports

Service account user on each node with Excel installed that will be used as an IM
server:
1. Login as the 800xA Service User and Open MS Excel
2. Dismiss any start up dialogs and exit MS Excel
If the node is to be used as an Engineering node, follow the procedure listed in
Macro Security for Microsoft Excel.

Macro Security for Microsoft Excel

Perform the following procedure for every Industrial IT User on every node, after
installation of Microsoft Excel and before continuing installing or working on the
Engineering Platform:
1. Start Microsoft Excel.
2. Click the File menu in the left corner.
3. Click Excel Options to open the Excel Options dialog box.
4. Select Trust Center in the left pane of the Excel Options dialog box.
5. Click Trust Center Settings to open the Trust Center.
6. Select Macro Settings in the left pane of the Trust Center.
The macro security setting must be set to Enable all Macros for every Industrial
IT User on every node in the 800xA System if any of the following are true:
• 800xA for Harmony or 800xA for AC 870P/Melody is installed on any node in the
800xA System.
• Engineering templates will be used on any node in the 800xA System.
7. Select Disable all Macros Except Digitally Signed Macros in the right pane
of the Trust Center.
8. Click OK to close the Trust Center.
9. Click OK to close the Excel Options dialog box.

Crystal Reports
Crystal Reports can be used to create reports of System 800xA Data. When used
with the application scheduler, the reports can be automatically executed.

2PAA111708-600 J 87
Crystal Reports Appendix A Prerequisites

Crystal Reports will typically be installed on nodes where the, Information

Manager, node function is allocated. However, it can be installed on any node that
has access to 800xA data reporting interfaces (800xA DataDirect or ODBC). Follow
the procedure to install Crystal Reports.
System 800xA latest release supports Crystal Reports 2013 SP7 or newer versions.
Table 7 lists the installed versions and available builds in the SAP portal.

Table 7. Crystal Report Builds

Build
Crystal reports 2013 SP7 +
Crystal Reports Runtime install
(CRforVS_redist_install_32bit_13_0_16)
Website
It will be available as part of Crystal reports 2013
media.
Download the Crystal Reports Runtime from the
location specified below.
• From the URL
http://scn.sap.com/docs/DOC-7824
• Click 32bit.msi from MSI 32 bit column as
shown in the Figure 17 to install.

Crystal Reports Runtime Install

(CRforVS_redist_install32bit_13_0_16)

Figure 17. Crystal Reports Runtime Install

.NET 3.5
Crystal Reports requires .NET 3.5. Before installing Crystal reports, use the
following files to install .NET3.5. Use Run As Administrator to execute the files.

88 2PAA111708-600 J
Appendix A Prerequisites Autocad Integration

Windows 10:
%ABB800xAMediaRepositoryLocation%\3rd_party_sw\DotNet3_5\Install_DotN
ET3_5_W10.bat

Windows 8.1/Windows 2012R2:

%ABB800xAMediaRepositoryLocation%\3rd_party_sw\DotNet3_5\Install_DotN
ET3_5_W8.bat
The default value for %ABB800xAMediaRepositoryLocation% is
c:\ProgramData\ABB\800xA\MediaRepository. Windows hides c:\ProgramData
by default, but the path can be typed into windows explorer to navigate to this
directory. These files can be run multiple times without negative impact.

Autocad Integration
As a prerequisite to use AutoCAD for Document Manager and Parameter Manger,
install AUTOCAD VBA Enabler by downloading the software from the AutoCAD
website.

McAfee Integration
McAfee VirusScan® Enterprise has been tested and qualified virus scanner that is
used on all System 800xA servers and workstations. Refer to System 800xA
Installing and Configuring McAfee ePO Server (9ARD107543-005), for more
information.
McAfee need not be disabled during installation, however this might impact
Installation performance of 800xA Software.

Symantec
Symantec Endpoint Protection (SEP) has been tested and qualified virus scanner
that is used on all System 800xA servers and workstations. Refer to System 800xA
Using Symantec Endpoint Protection (9ARD119854-002), for more information.

Bulk SPL Template

To work with ABB Engineering Studio BulkSPLTemplate, perform the following:
1. Download and install the following software from Microsoft website:
Microsoft Visual Studio 2010 Tools for Office Runtime (x64).

2PAA111708-600 J 89
Process Engineering Tool Integration Specific Requirements Appendix A Prerequisites

During the VSTO installation following message may be displayed:

Files in use
Some files that need to be updated are in use by the
applications shown below.
Close these applications and click Retry to continue the
installation. Selecting Ignore will result in a reboot at
the end of installation. Select cancel to exit setup.
Click Ignore to complete the installation.
2. If VSTO is not installed before Engineering Studio installation, perform the
following steps:
a. Follow Step 1 to install VSTO.
b. Open Command Prompt as Administrator and execute the following:
"C:\Program Files (x86)\ABB Industrial IT\Engineer IT\Engineering
Studio\Function Designer\bin\BulkSPLbin\BulkSPLInstall.exe"
"C:\Program Files (x86)\ABB Industrial IT\Engineer IT\Engineering
Studio\\"

Process Engineering Tool Integration Specific Requirements

The following are requirements that exist only for Process Engineering Tool
Integration. Before installing Process Engineering Tool Integration software, install
the following prerequisites, if required:
• INtools/SPI: Must be installed on a non-800xA node. If installing the Web
Services component on this node, Microsoft IIS with FrontPage server
extensions must be installed.
• For viewing external CAD drawings, one of the following software
components is required to be installed on the 800xA System node on which the
800xA Client component of Process Engineering Tool Integration is installed:
– DWG TrueView 2015: Recommended to be used for viewing of
AutoCAD files.
The latest version of DWG TrueView 2015 can be downloaded free of charge at
http://www.autodesk.com

90 2PAA111708-600 J
Appendix A Prerequisites Backup Software

Backup Software
It is recommended that a third party backup/restore and/or disk imaging utility be
used to save (and restore if necessary) server and workstation hard drives. A valid
backup insures that the system can be restored.

2PAA111708-600 J 91
Backup Software Appendix A Prerequisites

92 2PAA111708-600 J
 Appendix B Installation and Configuration
Parameters

Acquiring Installation and Configuration Parameters

This section provides guidelines for acquiring the information needed for
installation with regard to network parameters, software keys, and so on. Gather the
required installation media needed to complete the installation, and confirm that all
required hardware is in place and meets the system requirements.
An organization should be in place to manage the domain with assigned
responsibilities and methods handling users and security.
Before installing and configuring (post installation) the 800xA System, there are
several parameters and system settings whose values must be determined and
available. Table 8 provides a worksheet for recording this information. It lists node
types and their applicable parameters, and provides a Value column for recording
the information.

2PAA111708-600 J 93
Acquiring Installation and Configuration Parameters Appendix B Installation and Configuration

For guidelines on parameters related to network and domain setup, refer to System
800xA Network Configuration (3BSE034463*).

Table 8. Installation and Configuration Parameter Worksheet

Node Type Parameter Value

All Nodes 800xA Installer Account name
System Functions
Node Functions
Primary IP address
Secondary IP address
Subnet mask
Node name
Time sync protocols
Time sync role and configuration (per protocol)
RNRP network area, node number, and local flag
PC Nodes DNS Server addresses
AC 800M Primary CPU primary and secondary IP address
Controllers Backup CPU primary and secondary IP address
Tool port IP address
Communication modules
IO modules
Domain Domain name
Server User Groups
Users
Concept of 800xA roles and permissions on system,
structures, and aspect object level
Network adapter type
DNS Server Backup needs IP address of primary
Aspect Affinity - Aspect Server Base Service
Server Affinity - Aspect Server node name of clients
Affinity - node name of redundant Aspect Servers
Network adapter type
Affinity - Connectivity Server Base Service
Affinity - Connectivity Server node name of clients
Affinity - node name of parallel Connectivity Server

94 2PAA111708-600 J
Appendix B Installation and Configuration Parameters Acquiring Installation and Configuration

Table 8. Installation and Configuration Parameter Worksheet (Continued)

Node Type Parameter Value

FIELDBUS HSE Subnet address(es)
Foundation
Connectivity HSE Subnet Id(s)
Server
800xA for AC AF 100 Bus number
100 CI527A Station number
Path to BCD file
IP address for redundant server node (optional)
800xA for Network Group number
Advant MB 300 network number1
Master MB 300 network number2
MB 300 node number
Network interface IP address in PC used for PU410.
Since the RTA unit default IP addresses are
172.16.168.50 and 172.17.168.50, do not
configure network area 10 in the RNRP
client/server topology. If the client server
topology is configured as network area 10, the
default IP address of the RTA unit must be
changed as described in 800xA for Advant
Master Configuration (3BSE030340*).
Connectivity
Network adapter type
Server
(Managed)
IP address
Switches
Disk Image Server IP address
Session names
Backup identities and filenames

2PAA111708-600 J 95
Acquiring Installation and Configuration Parameters Appendix B Installation and Configuration

Table 8. Installation and Configuration Parameter Worksheet (Continued)

Node Type Parameter Value

800xA for Since the RTA unit default IP addresses are
MOD 300 172.16.168.50 and 172.17.168.50, do not
RTA Unit configure network area 10 in the RNRP
client/server topology. If the client server
topology is configured as network area 10, the
default IP address of the RTA unit must be
changed as described in Industrial IT, System
800xA for MOD 300 - RTA Unit PU410 and
PU412 User’s Guide, Technical Data and
Installation Information (3BUA001442*).
800xA for IP addresses of IET Modules
Harmony

800xA for Onet IP address

Melody
Melody Configuration Server Name
800xA for DCI ECC MUX IP address

All Nodes System Functions and Node Functions

96 2PAA111708-600 J
 Appendix C Related Documentation

A complete list of all documents applicable to the 800xA System is provided in

System 800xA Released User Documents (3BUA000263*). This document lists
applicable Release Notes and User Instructions. It is provided in PDF format and is
included on the Release Notes/Documentation media provided with your system.
Released User Documents are updated with each release and a new file is provided
that contains all user documents applicable for that release with their applicable
document number. Whenever a reference to a specific instruction is made, the
instruction number is included in the reference.

Table 9. Related Documentation

Item Where to go... When to go...

[1] System 800xA 6.0 Release Notes New Used for information on the new functions and
Functions and Known Problems known problems that exist at the time of release.
(2PAA111899*)
[2] System 800xA 6.0 Release Notes Used for information on the issues that have been
Resolved Issues (2PAA112277*) fixed at the time of release.
[3] System 800xA System Guide Technical Used to help plan the 800xA System based on
Data and Configuration (3BSE041434*) the configuration rules and node functions.
[4] System 800xA Site Planning Used for site planning, preparation, power
(3BUA000285*) distribution, system grounding, and wiring
practices for an 800xA System control system.
[5] System 800xA System Planning Used as a guideline for the engineering planning
(3BSE041389*) to be used in the early phases of a System 800xA
project.

2PAA111708-600 J 97
 Appendix C Related Documentation

Table 9. Related Documentation

Item Where to go... When to go...

[6] System 800xA Licensing Information Used to know more about the licensing
(2PAA111691*) mechanisms used in System 800xA such as,
obtaining the machine IDs and licenses and
applying the licenses.
[7] System 800xA 6.0 Tools (2PAA101888*) Used to know more about the tools used to
install, configure and verify an 800xA system.
[8] System 800xA Network Configuration Used to plan and setup the network topology.
(3BSE034463*)
[9] System 800xA 6.0 Virtualization Used to gain an overview of System 800xA
(3BSE056141*) virtualization. It helps plan for combining multiple
800xA Server nodes on a single computer.
[10] System 800xA 6.0 Multisystem Used to install, configure, operate and maintain
Integration (3BSE037076*) the 800xA Multisystem Integration system
extension.
[11] System 800xA 6.0 Post Installation Used to carry out the manual post installation
(2PAA111693*) steps of System 800xA.
[12] System 800xA 6.0 Configuration Used to gain an overview on engineering and
(3BDS011222*) configuration workflow steps of the System
800xA in the context of an engineering project.
[13] System 800xA 6.0 Update Manual Used to know more about how to install updates
(2PAA114580*) for System 800xA.
Control
[13] System 800xA Control 6.0 AC 800M Used to get started with the Control Builder
Getting Started (3BSE041880*) Professional for AC800M.
[14] System 800xA Control 6.0 AC 800M Used as a guideline of what to consider when
Planning (3BSE043732*) designing an automation solution using Control
Software for AC 800M, such as memory
consumption, CPU load, and task execution. The
manual also contains advice to programmers
regarding optimization of code.

98 2PAA111708-600 J
Appendix C Related Documentation

Table 9. Related Documentation

Item Where to go... When to go...

AC800M
[15] AC 800M 6.0 AC 800M DriveBus Used for installation and start-up of the CI858
(3BSE079696*) communication interface.
[16] AC 800M 6.0 FOUNDATION Fieldbus Used for configuration of control applications with
HSE (3BDD012903*) FOUNDATION Fieldbus HSE using the CI860
module along with HSE Linking Devices and
Fieldbus Builder FOUNDATION Fieldbus as
FOUNDATION Fieldbus configuration tool.
[17] AC800M 6.0 PROFIBUS DP Installation Used for application notes and advice for wiring
(3BDS009029*) and installation of PROFIBUS networks.
[18] AC 800M 6.0 PROFIBUS DP Used for configuration of the PROFIBUS DP-V1
Configuration (3BDS009030*) in the 800xA control system using
CI854/CI854A/CI854B communication interface.
[19] AC 800M 6.0 PROFINET IO Used to configure PROFINET IO in the 800xA
Configuration (3BDS021515*) control system using the communication interface
CI871.
[20] AC 800M 6.0 Controller Hardware Used to install, configure, operate and perform
(3BSE036351*) the necessary maintenance on all equipment
making up the AC 800M or AC 800M HI
controllers.
[21] AC 800M 6.0 Interfacing SATT I/O Used to install the new hardware required on the
(3BSE042821*) field level, prepare for installation of the new
controller on AC 800M and reuse the old SATT
I/O units.
[22] AC 800M 6.0 Ethernet/IP DeviceNet Used for application notes and procedures
Installation (9ARD000015*) provided for the wiring and installation of
DeviceNet networks.
[23] AC 800M 6.0 IEC 61850 Configuration Used for engineering and configuration of the
for CI868 (9ARD171385*) CI868 IED using Control Builder, IEC 61850
Wizard tool and other third party tool.

2PAA111708-600 J 99
 Appendix C Related Documentation

Table 9. Related Documentation

Item Where to go... When to go...

IO
[24] S900 I/O Manual DTM 6.0 Used for installation and operation of the DTMs
(3BDD010407*) for S900 I/O and control systems.
[25] S900 I/O S and N System with SA920 Used for mounting and installation procedures for
Installation (3BDD010421R0401) S900 I/O System type S and type N.
[26] S900 I/O Manual Installation-Guide S-N- Used for issues related to the installation of the
System SA920 CI920A I/O System S900.
(3BDD010421R0601*)
[27] S900 I/O B-System with SA920 Used for mounting and installation procedures for
Installation (3BDD010432R0401*) I/O System S900 type B.
[28] S900 I/O Manual Installation-Guide B- Used for issues related to the installation of the
System SA920 CI920A I/O System S900 type B.
(3BDD010432R0601*)
[29] S800 I/O Getting Started Used for general installation and configuration
(3BSE020923*) information for the S800 I/O system.
[30] S800 I/O Modules and Termination Units Used for more information on S800 I/O modules
(3BSE020924*) and termination units.
[31] S800 I/O Fieldbus Communication Used for more information on PROFIBUS-DP FCI
Interface for PROFIBUS- in the S800 I/O system.
DP/DPV1(3BSE020926*)
[32] S800 I/O Modules and Termination Units Used to get information on the I/O modules and
with Intrinsic Safety Interface termination units with I.S. interface in the S800
(3BSE020927*) I/O system.
[33] S800 I/O DTM 6.0 (3BSE027630*) Used for instructions for installation and for
operation of the DTMs in S800 I/O.
[34] S200 I/O Hardware (3BSE021356*) Used to install, configure and maintain the S200
I/O system.
[35] S200L I/O Hardware (3BSE021357*) Used to install, configure and maintain Compact
I/O (S200L I/O and I/O 200C units).

100 2PAA111708-600 J
Appendix C Related Documentation

Table 9. Related Documentation

Item Where to go... When to go...

800xA for TRIO
[36] 800xA for TRIO/Genius 6.0 Getting Used to install the CI862 TRIO/Genius Interface,
Started (3BUR002459*) connect TRIO/Genius I/O modules and
considerations to migrate from the MOD 300
control system.
800xA for Advant Master
[37] 800xA for Advant Master 6.0 Used to connect the workplaces to a MasterBus
Configuration (3BSE030340*) 300 control network with connected AC 400
Controller Series, including MasterPiece 200/1,
using 800xA for Advant Master.
800xA for Safeguard
[38] 800xA for Safeguard 6.0 Configuration Used to set up the safety system functionality
(3BNP004848*) (including defining displays, configuring control
parameters etc.) and the safety system
configuration.
Operations
[39] System 800xA Operations 6.0 Used to understand the 800xA Operator
(3BSE036904*) Workplace.
[40] System 800xA 6.0 Snapshot Reports Used to install, set up, configure and maintain the
User Guide (3BSE060242*) 800xA for Snapshot Report system extension.
[41] VideoNet Connect for 800xA User Used to install, configure, and operate the
Manual (2PAA109407*) VideoNet Connect for 800xA product that is a
system extension to the 800xA system.
800xA for AC 100
[42] 800xA for AC 100 6.0 Configuration and Used to configure System 800xA in order to view
Operation (3BDS013989*) and access the Advant Controller 100 Series
objects. Hints for operation and maintenance is
also included in this document.

2PAA111708-600 J 101
 Appendix C Related Documentation

Table 9. Related Documentation

Item Where to go... When to go...

[43] AC 100 OPC Server 6.0 Configuration Used to configure the AC 100 OPC Server,
and Operation (3BDS013988*) configure and build applications for controllers of
AC 100 Series using the AC 100 OPC Server.
Use for information on runtime and maintenance
of the AC 100 OPC Server.
800xA for Freelance
[44] 800xA 6.0 for Freelance Installation Used to install and upgrade the connectivity
(3BDD011810*) software 800xA for Freelance.
800xA History
[45] 800xA History 6.0 Installation Used to install the History components using the
(2PAA107280*) History installer.
800xA Engineering
[46] System 800xA Engineering 6.0 Used to install and configure the Application
Application Change Management Change Management (ACM) server.
(2PAA108438*)
Reference manuals
[47] System 800xA System Alarm Messages Used to find the System Alarms that are
(2PAA114623*) generated when operating an 800xA System.

102 2PAA111708-600 J
 Appendix D Installation Media

Installation Media Deliverable

The System 800xA Installation media is distributed either on a physical media, or
via a zip archive. The physical media is a secure, read-only and tamper proof Solid
State Drive (SSD). A zip archive means downloading one or more zip-files from
myABB/My Control System. The archive have to be un-packaged and stored locally
as described in Readme file included in the media.

Content Usage Source

Physical disk Full 800xA software Installation, Update, Ordered from ABB
(SSD) package Upgrade
Zip archive Partial 800xA software Update Download from myABB/My
package Control System

2PAA111708-600 J 103
Node Types Appendix D Installation Media

Node Types
Node Types (Configure System task) Description
Server The node can configure Server functions.
Client The node can configure Client functions.
Generic Node The node is not prepared to be part of 800xA
System. The amount of functions to be configured on
the node is very limited. This type is typically for e.g.
Domain Controllers, Print Servers and File Servers.

The definition of the Node Types in the Configure System task.

Node Options (NPT) Description

800xA Node The node is prepared to be part of an 800xA System.
Generic Node The node is not prepared to be part of 800xA System. This type is
typically for e.g. Domain Controllers, Print Servers and File Servers.

The definition of the Node Options in the NPT.

Node Options (NPT) Node Types (Configure System task)

800xA Node Server
Client
Generic Node Generic Node

The relation between Node Options (NPT) and Node Types (Configure System task).

104 2PAA111708-600 J
 Revision History

This section provides information on the revision history of this User Manual.
The revision index of this User Manual is not related to the 800xA 6.0 System
Revision.
The following table lists the revision history of this User Manual.

Revision
Description Date
Index
A Published for 800xA System Version 6.0 December 2014
B Added section on Installation process for 800xA System Version 6.0 December 2014
and included information on accessing the System 800xA media
from a virtual machine.
C Added section for information on System Upgrade support in this April 2015
release.
D Moved the Prerequisites section to the Appendix, included the October 2015
update workflow in this release and added the guidelines for
acquiring the information needed for installation with regard to
network parameters, software keys, and so on.
E Added information on System 800xA Media; included a section on October 2015
installing the .NET hotfix and Excluding a node.
F Updated a cross reference in Appendix A Prerequisites January 2016
G Published for 800xA System Version 6.0.2 April 2016
H Published for 800xA System Version 6.0.3 September 2016
I Published for 800xA System Version 6.0.3 September 2016
J Published for 800xA System Version 6.0.3 September 2016

2PAA111708-600 J 105
106 2PAA111708-600 J
 Index
Numerics Adding nodes to domain 59
800xA service user Adding privileges to 800xA service user
Adding privileges 83 83
Backup software 91
A Microsoft Excel 86
Adding 800xA domain users 71 Microsoft Word 85
Adding nodes to domain 59 Miscellaneous Windows setup 72
Adding privileges to 800xA service user 83 Network adapters 50
Automatic updates 78 Remote client 83
Terminal server 83
Users and groups 60
B
Windows 45
Backup software 91
Windows installation guidelines 48
Installation data 93
D Installation planning
Default user groups and users 64 Planning and preparation 93
Defragmenting disks 47 Installation data 93
Disks and file system 46
M
E Microsoft Excel 86
Energy saver 77 Microsoft Word 85
Excel 86
N
F Network adapters 50
File system 46
O
G Other Third Party Software 84
Groups 60
P
I Planning and preparation 93
IE enhanced security configuration 75 Installation data 93
Installation
Directory 47
R
Prerequisites
Remote client 83
Adding 800xA domain users 71

2PAA111708-600 J 107
Index

T
Terminal server 83

U
User groups and users
Default 64
Users 60

W
Windows operating system 45
Installation guidelines 48
Miscellaneous setup 72
Word 85

108 2PAA111708-600 J
Contact us

www.abb.com/800xA Copyright © 2016 ABB.

2PAA111708-600 J
www.abb.com/controlsystems All rights reserved.

Power and productivity

for a better worldTM