installation, update and upgrade getting started · system800xa...

System 800xAInstallation, Update and Upgrade Getting Started

System Version 6.0

System 800xAInstallation, Update and UpgradeGetting Started

System Version 6.0

Document Number: 2PAA111708-600Document Revision: L

Release: November 2017

NOTICE

This document contains information about one or more ABB products and may include a descriptionof or a reference to one or more standards that may be generally relevant to the ABB products. Thepresence of any such description of a standard or reference to a standard is not a representation thatall of the ABB products referenced in this document support all of the features of the described orreferenced 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 propertyin the ABB products described in this document.

The information in this document is subject to change without notice and should not be construed asa 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 communicateinformation and data via a secure network. It is the sole responsibility of the system/product owner toprovide and continuously ensure a secure connection between the product and the system networkand/or any other networks that may be connected.

The system/product owners must establish and maintain appropriate measures, including, but notlimited to, the installation of firewalls, application of authentication measures, encryption of data,installation of antivirus programs, and so on, to protect the system, its products and networks, againstsecurity breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data orinformation.

ABB verifies the function of released products and updates. However system/product owners areultimately responsible to ensure that any system update (including but not limited to code changes,configuration 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 thatthe 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 ofany nature or kind arising from the use of this document, nor shall ABB be liable for incidental orconsequential 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 fromABB, and the contents thereof must not be imparted to a third party nor used for any unauthorizedpurpose.

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 therequirements specified in EMC Directive 2014/30/EU and in Low Voltage Directive 2014/35/EU.

TRADEMARKS

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

Copyright © 2004-2017 by ABB.All rights reserved.

Table of Contents

1 About this User Manual91.1 User Manual Conventions ........................................................................................

91.1.1 Warning, Caution, Information, and Tip Icons ..........................................

2 Introduction112.1 System Security ......................................................................................................

3 System Installation133.1 Overview ..................................................................................................................

133.1.1 Environment Setup ....................................................................................

143.1.2 Node Preparation .......................................................................................

143.1.3 Create System ............................................................................................

143.1.4 Configuration .............................................................................................

143.1.5 Deploy .......................................................................................................

143.2 Environment setup ....................................................................................................

153.3 Prepare Nodes ..........................................................................................................

183.4 Create System ...........................................................................................................

193.5 Add System Functions .............................................................................................

203.6 Add Nodes ................................................................................................................

213.7 Allocate Node Functions ..........................................................................................

223.8 Configure Redundancy .............................................................................................

243.9 Deploy Configuration ...............................................................................................

263.10 Maintenance .............................................................................................................

263.10.1 Expand the System ....................................................................................

273.10.2 Remove Deployed Function ......................................................................

283.10.3 Remove Nodes ...........................................................................................

283.10.4 Rename Nodes ...........................................................................................

2PAA111708-600 L 5

Table of Contents

293.10.5 Prepare Add-ons ........................................................................................

303.10.6 Move a System ..........................................................................................

343.11 Troubleshooting ........................................................................................................

343.11.1 Handle Failed Deployments ......................................................................

353.11.2 Extend a Node with Missing Installation Files ..........................................

363.11.3 Repair Invalid Media on Node ..................................................................

363.11.4 Exclude Nodes ...........................................................................................

373.11.5 Replacing a Node .......................................................................................

383.11.6 Diagnostics ................................................................................................

4 System 800xA Update

5 System 800xA Upgrade

Appendix A Prerequisites43A.1 Windows Operating System .....................................................................................

44A.1.1 Selecting the Windows Operating System ...............................................

44A.1.2 Considerations for Disks and File System .................................................

45A.1.3 Windows Installation Guidelines ...............................................................

47A.1.4 Windows Operating System Updates .......................................................

47A.2 Configuring Network Adapters ...............................................................................

51A.3 Configuring Domain Controller and DNS Server ....................................................

51A.3.1 Installing base software .............................................................................

56A.3.2 Adding Nodes to a Domain .......................................................................

57A.4 Configuring Users and Groups .................................................................................

60A.4.1 New Organizational Unit ...........................................................................

60A.4.2 Groups ......................................................................................................

61A.4.3 Users, Groups, and Rights Assignments ...................................................

65A.4.4 800xA Service User ................................................................................

66A.4.5 User Account for Installation ...................................................................

67A.4.6 Other Users ................................................................................................

67A.4.7 Adding 800xA Domain Users to the Local Administrator Group .............

69A.5 Operating System Setup Use with 800xA System ..................................................

69A.5.1 Regional and Language Options ................................................................

6 2PAA111708-600 L

Table of Contents

70A.5.2 Enable Write Caching on Hard Disks ........................................................

71A.5.3 Internet Explorer as Default Browser ........................................................

72A.5.4 Internet Explorer Enhanced Security .........................................................

72A.5.5 Internet Security Settings for Digital Signature Validation .......................

72A.5.6 Disable Web Browser Popup Blocker .......................................................

73A.5.7 Disable Show Window Contents While Dragging ....................................

73A.5.8 Energy Saver and Screen Saver Configuration .........................................

74A.5.9 Virus Scanning Configuration During Installation and Post Installation ..

74A.5.10 Windows Update Configuration ................................................................

75A.5.11 Enable the Change Sharing Options for Different Network Profiles ........

75A.5.12 Disable Server Manager Startup ................................................................

75A.5.13 Hot fix for redundancy with IPSec enabled ...............................................

75A.5.14 Set Date and Time for Batch Servers ........................................................

76A.5.15 Disable ISATAP Setting ............................................................................

76A.5.16 Group Policy Management ........................................................................

80A.5.17 Adding Privileges to the 800xA Service User ...........................................

80A.5.18 Remote (Thin) Client for the Server Operating System ...........................

81A.6 Other Third Party Software ......................................................................................

81A.6.1 Microsoft Office Professional .................................................................

81A.6.2 Microsoft Word .........................................................................................

82A.6.3 Microsoft Excel ......................................................................................

84A.6.4 Crystal Reports ..........................................................................................

85A.6.5 Autocad Integration ...................................................................................

85A.6.6 McAfee Integration ....................................................................................

86A.6.7 Symantec ..................................................................................................

86A.6.8 Bulk SPL Template ....................................................................................

86A.6.9 Process Engineering Tool Integration Specific Requirements ..................

87A.6.10 Backup Software ........................................................................................

87A.6.11 Microsoft Updates .....................................................................................

Appendix B Acquiring Installation andConfiguration Parameters

2PAA111708-600 L 7

Table of Contents

Appendix C Related Documentation

Appendix D Installation Media101D.1 Installation Media Deliverable .................................................................................

101D.2 Node Types ...............................................................................................................

Appendix E Revision History

INDEX

8 2PAA111708-600 L

Table of Contents

1 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, representpossible steps that a user of an 800xA System may want to consider based on arisk 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 installthe 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 Areasoftware 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, andso on that can be found in other 800xA User Manuals. Refer Appendix C.

1.1 User Manual ConventionsMicrosoft Windows conventions as defined in theMicrosoft Manual of Style arenormally used for the standard presentation of material when entering text, keysequences, prompts, messages, menu items, screen elements, and so on.

1.1.1 Warning, Caution, Information, and Tip IconsThis user manual includesWarning, Caution, and Information where appropriateto point out safety related or other important information. It also includesTip to pointout useful hints to the reader. The corresponding symbols should be interpreted asfollows:

2PAA111708-600 L 9

1 About this User Manual 1.1 User Manual Conventions

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

Warning icon indicates the presence of a hazard which could result in personalinjury.

Caution icon indicates important information or warning related to the conceptdiscussed in the text. It might indicate the presence of a hazard which could resultin 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 touse a certain function.

AlthoughWarning hazards are related to personal injury, and Caution hazards areassociated with equipment or property damage, it should be understood that operationof damaged equipment could, under certain operational conditions, result in degradedprocess performance leading to personal injury or death. Therefore, fully complywith allWarning and Caution notices.

10 2PAA111708-600 L

1 About this User Manual 1.1 User Manual Conventions

2 Introduction

Visual Basic Process Graphics (VBPG) is not supported in System 800xA 6.0. Itis mandatory to migrate all VBPG to PG2 graphics before upgrading to System800xA 6.0. Plan for the migration in advance. The standard VB Graphics systemextensions and other AC 800M Classic library system extensions will be deletedduring Upgrade and Update process.

2.1 System SecurityIt is very important to have a corporate security policy that is revised on a regularbasis. This is the responsibility of the user of the 800xA System.

Before the installation starts, make sure that Windows firewall is turned ON, andantivirus software is running on all nodes.

This document does not contain recommendations on system security, users, usergroups, or user roles and permissions. For more information, refer the System 800xAAdministration and Security (3BSE037410*), System 800xANetwork Configuration(3BSE034463*), and System 800xA System Planning (3BSE041389*) documents.

2PAA111708-600 L 11

2 Introduction 2.1 System Security

12 2PAA111708-600 L

3 System Installation

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

From System 800xA version 6.0, the installation procedure is automated, and can beperformed almost completely from a single node. This also enables automatic updatesof the System.

Because of this, do not perform installation of 800xA products manually. Manuallyinstalled functions cannot be updated automatically, nor handled in any way by theConfigure 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.

3.1 OverviewThe installation consists of these major steps:

Figure 3.1: Installation Steps

3.1.1 Environment SetupIn this step the Windows environment is configured, and users & groups are createdetc. All these requirements are specified in Appendix A.

2PAA111708-600 L 13

3 System Installation 3.1 Overview

3.1.2 Node PreparationThis step prepares a node with the latest Installation Media and installs a SystemInstaller Agent. It is performed by running the Setup application from the InstallationMedia.

This step must be performed on all nodes.

3.1.3 Create SystemAn empty 800xA System is created.

3.1.4 ConfigurationIn this step, the 800xA System's functionality is configured. It is performed by usingthe Configure System task to select System Functions, Node Functions and nodes. Italso involves setting up redundancy.

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

3.2 Environment setupAll prerequisites are defined in detail under Appendix A. Verify that they are fulfilledbefore 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 fornormal 800xA Users. They can be created in a Domain or Workgroup.

• 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 softwareinstallation.

• 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.

14 2PAA111708-600 L

3 System Installation 3.2 Environment setup

• Turn ON the Windows firewall.

• Set up the security policy and antivirus. See System Security on page 11.

• Verify the remaining requirements under Appendix A.

3.3 Prepare NodesThis will prepare a node with software and install a System Installer Agent, to prepareit for centralized deployment.

Make sure the name of the node is valid for the system, that is, it does not includeany invalid characters and is no longer than 15 character. For more informationsee Windows Installation Guidelines on page 45

• Get a copy of the latest Installation Media. See Installation Media Deliverableon page 101.When preparing the node for an existing system the Installation Media must bethe latest media installed in the system, i.e. it can either be a complete installationmedia or an update media.

When running the installation from a network share, it is required that the installinguser has access to the complete share and that it is residing on the sameDomain/Workgroup as the 800xA System to be set up. Also the length of theactual 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.

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

2PAA111708-600 L 15

3 System Installation 3.3 Prepare Nodes

Figure 3.2: Node Preparation Tool (NPT)

• Enter 800xA Service account credentials, and the groups created in Environmentsetup on page 14.

• Open the Node Options dialog to select what to prepare the node for. Read moreabout the Node Options in the Node Types on page 101.

16 2PAA111708-600 L


Figure 3.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, thenall the separate medias that is, Add-On medias, other update medias and/or olderfull media must be made available for preparation of the node. All these mediasneeds to be copied to a common location that is specified in the Additional Mediatext field.

Figure 3.4: Media Folder

This folder will be searched for different medias and the latest versions of the functionswill be included when preparing the node.

• Read and accept the license agreement.

2PAA111708-600 L 17


• Use the Start node preparation command.

This will copy all required installation files for the selected options and install theSystem Installer Agent. A progress banner will indicate how far the process has come.

Figure 3.5: Progress Banner during preparation of a node

Once completed, installation of base software for the node will proceed. Whichsoftware that is installed at this point is decided by the selection in theNode Optionsdialog. This process is indicated by a new progress bar that will disappear uponcompletion.

The system might reboot during the preparation.

• If the node is intended to be the primary aspect server, launch the SCC andproceed with Create System on page 18.

Additional node types and options can be added later by following Expand thesystem workflow (see Expand the System on page 26).

3.4 Create SystemIn order to use the functionality of System 800xA a System must be created usingthe 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.

• 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.

18 2PAA111708-600 L

3 System Installation 3.4 Create System

If an error occurs during system creation it is possible to get more information byusing the View log link. One common problem is that the user is not part of thecorrect user groups.

3.5 Add System FunctionsThis configures the functions that will be available in the System. This functionalityis available in the Configure System task in the SCC in the 'System Setup' folder.

• Go to System functions tab, and use theEdit functions command to add desiredfunctions.

• Apply the changes and close the dialog.

Figure 3.6: Modify System Functions

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 ifrequired, by using the Edit link.

2PAA111708-600 L 19

3 System Installation 3.5 Add System Functions

Figure 3.7: System Functions Properties

3.6 Add NodesThis will add system nodes to the configuration. This functionality is available in theConfigure 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 thathave been prepared for automatic installation. An animated icon will indicate that theapplication is searching for nodes on the network.

• Select a node from the list or enter a name of a node (if it is currentlydisconnected).

• Select its Node Types. This defines which functions that can be configured onthe node. Read more about Node Types on page 101.

20 2PAA111708-600 L

3 System Installation 3.6 Add Nodes

Figure 3.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 theMultiple nodes dialog.

3.7 Allocate Node FunctionsThis will add functions to a specific node. This functionality is available in theConfigure 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 availablenode functions for the node.

• Select desired functions in the dialog.

2PAA111708-600 L 21

3 System Installation 3.7 Allocate Node Functions

Figure 3.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 ifrequired by using the Edit properties link.

3.8 Configure RedundancyThis configures functional redundancy between System nodes. Having redundantfunctions means that if one function on a node stops functioning, its redundant partnerwill take over. This is used to ensure that the function is always available when theSystem is in production.

This functionality is available in the Configure System task in the SCC under the'System Setup' folder.


• Use theMake redundant command.

This will open a dialog for configuring redundancy.

22 2PAA111708-600 L

3 System Installation 3.8 Configure 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 3.10: Redundancy

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

2PAA111708-600 L 23

3 System Installation 3.8 Configure Redundancy

Figure 3.11: Redundant Node

3.9 Deploy ConfigurationIn this step, the configuration will be installed on the System nodes.


• Use the Deploy system command.

This will open a dialog for monitoring the deployment. All nodes participating in thedeployment are listed. The nodes can be expanded to view the System Functions thatwill be installed on them.

• Ensure that there are no reserved entities in the system. Use the Find Tool in thePlant 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 happeningon the node.

Some functions require nodes to be restarted during the deployment. This isindicated by a small icon for each node.

If there is a warning message stating that there are missing installation files, pleasefollow the steps under section Extend a Node with Missing Installation Files onpage 35 to resolve the problem.

24 2PAA111708-600 L

3 System Installation 3.9 Deploy Configuration

Figure 3.12: Deploy

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

Figure 3.13: Deploy Progress

Once completed, a message box is displayed saying that the deployment wassuccessful. This indicates that all actions required to install the configuration wassuccessfully performed on the nodes.

• Return to the Configure System task by closing the message box.

2PAA111708-600 L 25

3 System Installation 3.9 Deploy Configuration

Figure 3.14: Deploy Complete

3.10 Maintenance

3.10.1 Expand the SystemIt is possible to expand the systemwith new nodes and functions even after the Systemhas been deployed once.

Add a new node

• Prepare and configure Windows on the node according to the instructions inAppendix A.

• Prepare the node (see Prepare Nodes on page 15) using the NPT by starting theSetup application from the latest media matching the installed system, i.e., if anupdate 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 page21).

• Configure redundancy (see Configure Redundancy on page 22).

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

26 2PAA111708-600 L

3 System Installation 3.10 Maintenance

Add New System Functions

• Follow the steps in Add System Functions on page 19.

• Use the Deploy system command to install the configuration (see DeployConfiguration on page 24).

Add New Node Functions

• Follow the steps in Allocate Node Functions on page 21.

• Use the Deploy command from the Node actions... dropdown to install thefunctions on the node.

3.10.2 Remove Deployed FunctionThere is no system support to automatically undo the actions performed during functiondeployment, like un-installing the software. There is however support to remove thestored configuration data related to the function.

When removing a function theManual Remove commandwill list all actions relatedto 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 theManually Remove command.

• Follow the screen prompts to complete the remove.

Remove Node Function

To manually remove a Node Function:


• Select the Node Function, open the context menu by right clicking and then usetheManually Remove command.

2PAA111708-600 L 27


• Follow the screen prompts to complete the remove.

3.10.3 Remove NodesA node may be removed from the system to reduce the system footprint. Onceremoved, the node is no longer part of the system.

Removing the node from the system causes all the configuration data related tothe 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 tobe a new node. That is, the node needs to be restored to its initial state and all thesteps for adding a node, configuring and deploying functions to a new node hasto be performed.

This function is not intended for node problem solving. If that is the case pleaserefer to Exclude Nodes on page 36 and Replacing a Node on page 37.

3.10.4 Rename NodesOne or more nodes may be renamed when restoring a backup from a development orengineering system into a production system or due to some other reason. It isimportant 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 Nodeactions… dropdown.

• In the Properties dialog, change the name and press OK.

28 2PAA111708-600 L


3.10.5 Prepare Add-onsThe definition of an Add-on is a System Function that was not part of the originalmedia, for example a language pack. Installing an Add-on on an already deployedsystem consists of two steps:

• Distributing the Add-on using either manual distribution or centralizeddistribution.

• Installing the added Functions following the same steps as when expanding thesystem with new functions (see Add New System Functions on page 27 and AddNew Node Functions on page 27).

To distribute an Add-on already part of the system follow the instructions forExpand the System on page 26 or Replacing a Node on page 37

Centralized preparation


• Launch the Update wizard using the Updates command.

• In the Locate update media step choose Centralized media distribution andenter the path to the Add-on Media.

Figure 3.15: Update System Preparation

2PAA111708-600 L 29


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

Manual preparation

Refer to Prepare Nodes on page 15 for manual preparation.

3.10.6 Move a SystemIt 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 projectafter configuring and engineering a System beforehand. This section describes aworkflow 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 CBMsettings, Saving AC800M OPC configuration etc.

• Export System Installer's 'System Configuration' aspect by using theImport/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 3.16: Placement of System Configuration aspect

Deploy software for production system

• Prepare an empty Windows as an '800xA Node' by referring the workflow insection Prepare Nodes on page 15.Make sure the node on the production system is isolated from the system wherethe backup is taken from.

30 2PAA111708-600 L


• Create a System, on the aspect server of the production system, with the samename as in the backup. Follow the workflow under section Create System onpage 18.

This will create a System that will be used temporary while setting up the requiredsoftware for the move.

Do not start the Configure System task yet. If it is started and no configurationaspect is present, an empty one will be created. If this happens, delete that aspectand the one named 'System Configuration State' and continue to the next step.

• Import the 'System Configuration' aspect, that was exported from the system tomove, by using the Import/Export function in the Plant Explorer Workplaceapplication. Place it in the location corresponding to the placement in the previoussystem.

• Start theConfigure System task available in the SCC in the 'System Setup' folder.

The configuration will contain all previously installed functions and nodes, but theywill 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 serverin the backup, it can be changed under theNode actions... dropdownmenu underProperties.

If a node appears as 'Invalid', ignore this and proceed.

• Exclude all nodes from the configuration, except for the current node. A commandfor 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 thenodes 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 sectionDeploy Configurationon page 24.

2PAA111708-600 L 31


If an error occur during the deploy please follow the guidelines in Handle FailedDeployments on page 34

This will install all required software for the System to be identical to the originalone in the backup. This step is required in order to restore the backup without errorsat a later stage.

Some software may require manual installation, this will be revealed in a comingstep. Therefore, it can be practical to take a backup of the entire node beforeproceeding.

• 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 Workplaceapplication.

• Start the Configuration Wizard application and select the action SystemAdministration to stop and then delete the 800xA System.

This will remove the temporary System and thus make room for the System in thebackup.

Restore engineering system backup

In this step the engineering system backup will be restored, and the configurationcreated by the deployment in the temporary system will be imported into it.

• Use the Configuration Wizard to restore the backup into function on the newnode.

32 2PAA111708-600 L


Figure 3.17: Configuration Wizard - Restore

Once completed, the System running on the new node will be identical to the onestored 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/Exportfunction in the Plant Explorer Workplace application.

The Configure System task will now 'remember' that only the current node has beendeployed, and that the other nodes are still excluded.

• Use theConfigure 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 tobe replaced there might be problem with Service Providers and Service Groupnames not matching.

It may require to change the names in the Plant Explorer Workplace.

2PAA111708-600 L 33


3.11 Troubleshooting

3.11.1 Handle Failed DeploymentsDuring a deployment one or more nodes may fail to perform an action. This willprevent the deployment from completing. The progress bar will turn red in both theDeploy 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 loggedin 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 Detailslink next to the node. In theDetailswindow the user can use theOpen Log commandto retrieve the latest log file from the node.

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

Retry

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

Manually Resolve

If it is not possible to perform the action using the Retry command, then it may bepossible to manually perform what the action was supposed to do, and then mark theaction as resolved, using theManually resolve command.

This requires deep knowledge of how the failed function should be installed andconfigured.

To manually resolve:

• Perform the failed action manually on the node. The command line can be foundin the Details window.

• Use the Details link next to the failed node in the Deploy dialog.

• Use theManually resolve command, and follow the screen prompts to complete.

34 2PAA111708-600 L

3 System Installation 3.11 Troubleshooting

• 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 thedeployment problem, and later start the deployment again. This will resume thedeployment from the point where it was aborted.

If it is important that the deployment completes, then it is possible to exclude theproblematic node from the current deployment by using the Exclude command. Thismakes it possible to solve the problem on the node at a later stage. See Exclude aNode During Deploy on page 37.

Replace Node

If none of the above solutions succeeded, the node may have to be reinstalled, restoredor replaced by a completely new node. Follow the procedure described in Replacinga Node on page 37.

3.11.2 Extend a Node with Missing Installation FilesSome functions in the System requires nodes to be prepared with certainNode Optionsto be able to Deploy. E.g. SQL or Oracle. If these options cannot be detected on thenode, 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 15 with the exception of the steps below:

• Instead of starting the Setup application run the batch file "RepairLMR.bat". Thiswill 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.

2PAA111708-600 L 35


3.11.3 Repair Invalid Media on NodeIt is possible to repair the Local Media Repository (LMR) to fix inconsistencies. Thiscan sometimes resolve problemswith nodes that are marked 'Invalid' in theConfigureSystem task.

Follow the steps in Prepare Nodes on page 15 with the exception of the steps below:

• Instead of starting the Setup application run the batch file "RepairLMR.bat". Thiswill 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.

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

3.11.4 Exclude NodesIt is highly recommended to try to solve any problem that is preventing a deploymentfrom completing. However, there may be cases where a deployment must becompleted, 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 thenode 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 theExclude/Include command under theNode actions... dropdown.

• Follow the screen prompts to complete the node exclusion.

36 2PAA111708-600 L


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.


• Select the node to be excluded and use theExclude/Include command under theNode actions... dropdown.

• Follow the screen prompts to complete the node exclusion.

3.11.5 Replacing a NodeThere might be cases when a node needs to be completely reinstalled or be replacedby a new node. In such cases it is possible to reinstall the node according to the alreadysaved configuration, using theReplace node command in theConfigure 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 backedup before restoring the node.

To replace a node:

• Set up a new node with (or restore a faulty node to) a cleanWindows installation.Prepare it according to the instructions in Appendix A.

• Make sure the new node has the same computer name and network configurationas the old node.

• Prepare the node using the Installation mediamatching the installed system, thatis follow the steps in Prepare Nodes on page 15.

• Go to System Nodes tab in the SCC.

• Select the node to be replaced and in the Node actions... dropdown use theReplace node command.

• Follow the screen prompts to complete the replacement.

2PAA111708-600 L 37


• Use theDeploy system command to install the node with the same configurationas before.

3.11.6 DiagnosticsThis commandmay be used to collect all the installer logs from all nodes in the systemto be used for deeper problem analysis.

When contacting support the files generated from this command are usuallyrequested.

38 2PAA111708-600 L



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

2PAA111708-600 L 39


40 2PAA111708-600 L


Upgrades can be executed using the System Installer as described in following upgrademanuals. 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.0is not supported. The System Version 3.1 Service Pack 3 800xA System must beupgraded 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 andthen to 800xA 6.0.

VB based Process Graphics are not supported in System 800xA 6.0. The VB editoris not supported and VBPG graphics can no longer be edited in 800xA 6.0. It ismandatory to migrate all VB process graphics to PG2 graphics before upgradingto 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 backto the installation instruction Create System to install that software.

This does not include information on site planning, engineering planning, softwareconfiguration, network design, security measures, tools, maintenance, and so on thatcan be found in other 800xA User Manuals.

2PAA111708-600 L 41


42 2PAA111708-600 L

Appendix A Prerequisites

Before the installation starts, make sure that Windows firewall is turned ON, andantivirus software is running on all nodes.

The user performing the procedures in this section must be proficient in the useofWindows Operating Systems. This section may not include detailed procedureson how to perform the described settings.

There may be differences in accessing the Microsoft Operating System settingsdescribed in this section depending on the selected operating system. It is theresponsibility of the user to consult Microsoft documentation and online help toaccurately make the settings.

Use the System 800xA 6.0 System Planning (3BSE041389*) document to helpplan the requirements, both hardware and software, for the 800xA System.

This section lists the prerequisites required to configure a node for an 800xASystem.

It is recommended to make a full backup of all disks. With such a backup all workwill be saved in the event of a disk crash or other serious malfunction. Make sureto place proper identification on the backup media or backup files.

Install optional hardware drivers if not supplied by theWindows Operating System(video card, network adapter, sound card, etc.).

A.1 Windows Operating SystemThis section describes:

• Selecting the Windows Operating System .

• Considerations for Disks and File System.

• Windows Installation Guidelines.

• Windows Operating System Updates .

2PAA111708-600 L 43

A Prerequisites A.1 Windows Operating System

A.1.1 Selecting the Windows Operating SystemSystem 800xA 6.0 version runs only on 64-bit (x64) operating systems.

The supported operating systems, service packs, and hot fixes are listed in System800xA 6.0, 5.1, 5.0, 4.x, 3.1 Third Party Software (3BUA000500). For security updatesrefer 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 NLSpackage 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 serveroperating system of Windows. Using workstation operating system helps inkeeping the cost down for smaller installations. Refer to the System 800xA 6.0System Guide Technical Data and Configuration (3BSE041434*) for rules thatapply in selecting the type of Operating System.

• There are limitations on number of nodes used in the system when using theWorkstation Operating System for Server nodes. These limitations depend onMicrosoft licensing rules for theWorkstation Operating System. Refer to System800xA System Guide Technical Data and Configuration (3BSE041434*) for thedetails 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 configuredas per the system 800xA specifications.

A.1.2 Considerations for Disks and File SystemThere are several factors that may have an impact on 800xA System performance,for example: where the software is installed, the tendency toward fragmentation. Thefollowing are some recommendations regarding these factors:

Multiple Disks and Partitions

Some types of 800xA servers can use significant disk I/O. Creating partitions thatare hosted by different disks or disk arrays can improve performance for these servers.Aspect Servers, Connectivity Servers, Information Management Servers and BatchServers can benefit from additional partitions when configuration data is distributedover multiple partitions that are hosted by separate disks or disk arrays. At least two

44 2PAA111708-600 L


https://myportal.abb.com/home

of these partitions are recommended for Information Management Servers. See theSystem 800xA System Guide Technical Data and Configuration (3BSE041434*) forspecific details for Information Management and other server types.

Installation Directory

It is generally recommended to use the Windows default location, the program filesdirectory 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 be25 percent empty for defragmentation purposes. Defragment disks on a regular basisusing the defragmentation software provided with the operating system. Check thesystem 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 historylogs reside as History configuration impacts not only the History Server disks.

• Extensive use of the Bulk Configuration tool may cause associated disks tobecome fragmented.

• Configuration procedures that involve creating, deleting, and then recreating ofa large quantity of objects may cause associated disks to become fragmented.

• Deleting and then creating the Aspect System may cause associated disks tobecome fragmented.

A.1.3 Windows Installation GuidelinesMake a fresh installation of the Windows Operating System.

Before adding applicable service packs, it is important that all the latest devicedrivers are installed to match the hardware. This is especially important for eliteserver hardware with special RAID hard drives and server specific hardware thatrequires the latest drivers or drivers not included in the operating system media.

Follow the installation procedure as described in the documentation provided byMicrosoft.

2PAA111708-600 L 45


Table A.1 indicates the settings specifically required for the 800xA Systeminstallation.

Table A.1: Windows Installation Requirements

DescriptionStep

Make sure the name of the computer does not contain any of the belowinvalid 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 (;)

Computer name

Refer to Regional and Language Options on page 69.Selecting RegionalSettings

46 2PAA111708-600 L


Table A.1: Windows Installation Requirements(Continued)

DescriptionStep

Make sure theAutomatically adjust clock for daylight saving changescheck box is enabled (if daylight saving time is used).

Time Zone

It is recommended that all server nodes (Aspect Directory, ConnectivityServers, Applications Servers, etc.) use at least one additional partitionfor the OperateItData and OperateItTemp folders. For best performance,the additional partition should be on a separate disk or disk array fromthe operating system.

Choosing a partition forinstalling the operatingsystem.

There may be additional disk requirements for Applications Servers. Ifinstalling the Information Management Server function on this node, atleast one additional NTFS partition is needed for storing historical data.This partition can be the same as the OperateItData and OperateItTemppartition or be a separate partition. The amount of disks, disk space, anddisk I/O needed for the Information Management node are dependent onthe final configuration for the node.

A.1.4 Windows Operating System UpdatesInstall Windows hot fixes, and Security Updates approved by ABB (refer to ThirdParty Software System 800xA (3BUA000500) and System 800xA Third Party SecurityValidation Status (3BSE041902) after installing other third party software.ABB System800xA Qualified Security Updates (9ARD183777*) can be used to install the latestqualified security updates. The tool and the document are accessible from ABBSolutionBank.

The Windows Operating System Updates (Service Packs, Feature Packs) must beinstalled immediately after installing the operating system, and before performingany other procedures in this instruction.

A.2 Configuring Network AdaptersIf the Network Adapter supports Receive Side Scaling this featuremust be disabled.Refer to the Network Adapter documentation for information on how to disablethe feature.

Network adapters must be installed and configured to support communication on theclient/server network. This is required on the Domain Server node, and all 800xA

2PAA111708-600 L 47

A Prerequisites A.2 Configuring Network Adapters

System nodes. Typically one network adapter will be provided with the server orworkstation hardware. It may be necessary to install a second network adapter forredundancy.

All network adapters may be installed and configured at the same time during systeminstallation; however, the network will not run with redundancy until RedundantNetwork Routing Protocol (RNRP) is installed (refer to Product Installation sectionfor a separate Domain Server node).

If the network adapters are not plug-and-play devices, the installation must be donemanually. If the Windows installation does not include the drivers for the networkadapters the driver software must be installed before the network adapters can beconfigured.

The 800xA System relies on TCP/IP as its transport protocol. It is stronglyrecommended that TCP/IP is the only protocol in use. If other protocols need tobe installed, make sure that TCP/IP is configured as the primary protocol.

Refer to Windows Help > Networking for more information on how to install andconfigure TCP/IP network adapters.

Refer to System 800xA Network Configuration (3BSE034463*) for configurationof DNS.

The following procedure applies to theWorkstation Operating System nodes. Theprocedure for the Server Operating System nodes may vary from the one shownhere.

To configure the network adapters:

1. Open Windows Control Panel.

2. Double-click Network and Sharing Center to open the Network and SharingCenter.

3. Click Change Adapter Settings.

4. Right-click on the network adapter and select Properties from the context menuto open the Connection Properties dialog box.

5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties to openthe Internet Protocol (TCP/IP) Properties dialog box.

6. Select Use the following IP address.

48 2PAA111708-600 L


7. Enter the IP address in the IP address and the subnetmask in the Subnet fieldsaccording to the planning done in Installation and Configuration ParameterWorksheet.

8. Enter the IP address of the default gateway in the Default gateway field (ifrequired by topology).

9. Enter the IP address of the Primary Domain Server in the Preferred DNS serverfield.

10. Enter the IP address of the Secondary Domain Server in the Alternate DNSserver field.

Always specify the Domain Servers with their primary client/server networkaddresses. This is true for all network adapters, including the ones for secondaryclient/server networks.

11. Repeat for all network adapters in the servers and workstations.

Use the same DNS settings for all network adapters.

12. For all interfaces on separate Control Networks three configuration changes(compared to the default settings) must be done to reduce the amount of trafficon 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 openthe Advanced TCP/IP settings dialog.

c. Click the DNS tab.

d. Clear the check box Register this connection's addresses in DNS.

e. Click theWINS tab.

f. Select Disable NetBIOS over TCP/IP.

13. ClickOK as necessary to save the newly configured values, and then clickCloseto close the Connection Properties dialog box.

14. Connect the Ethernet cables. Match each of the icons with its correspondingEthernet connector on the server or workstation.

15. Use ping -a from aWindows command prompt to verify the server or workstationhas contact with the Domain Controller:

2PAA111708-600 L 49


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




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 beforeRNRP is installed.

Verify the port speed and duplex configuration on both ends (Network Adapterand network switch). Refer to System 800xA Network Configuration(3BSE034463*).

16. Verify the primary Client Server network is bound first for RNRP configurations.

ForWindows 8.1 andWindows Server 2012 operating systems: From theChangeAdapter Settings:

Change of adapter settings are not required for Windows 10 and Windows Server2016 Operating Systems.

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 RedundantClient Server Network is second.

d. Make corrections as needed.

17. Disable all unused NIC cards.

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

50 2PAA111708-600 L


A.3 Configuring Domain Controller and DNS Server

A.3.1 Installing base softwareThis section describes how to use the Deploy functionality to install the softwarerequired by ABB for standalone Domain Controllers.

• Prepare the Domain Controller node according to the instructions in PrepareNodes on page 15 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 thechanges.


• Add the domain controller node (see Add Nodes on page 20).

• Deploy the configuration (see Deploy Configuration on page 24).

If the Domain Controller uses any network interface in addition to the ones forthe client/server network, the DNS Server need to be configured to only listen toDNS requests on the client/server network. Perform the following for all DomainControllers.

– 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 newDomain Server with a domain specifically for the 800xA System, that will existindependent of any other corporate domains that may already exist. Follow theprocedure in this section, starting at Active Directory Domain Services on First ForestRoot Domain Controller on page 52.

The following are general recommendations:

• One 800xA Systemmay share the same domainwith other 800xA Systems havingthe same system versions.

• Generally, it is better to create a new, dedicated domain for an 800xA Systemas opposed to reusing an old domain.

2PAA111708-600 L 51

A Prerequisites A.3 Configuring Domain Controller and DNS Se

• Do not create subdomains and avoid complex solutions.

• Generally, it is not recommended to split two redundant Domain Controllers tohost engineering and production systems on two different locations (i.e. networkislands). Splitting two Domain Controllers will make one of the parts incompletesince the Flexible Single Master Operations (FSMO) roles and Global Catalogservices are not redundant within Microsoft Windows.

Additional guidelines for setting up the 800xA System domain are provided inSystem 800xA Network Configuration (3BSE034463*).

Before setting up a new domain, verify that the server hardware being used as theDomain Server has the Server Operating System installed. The WorkstationOperating System can not be used for a Domain Controller or DNS server.

Ensure that Internet Protocol Version 4 (TCP/IP V4) is the only protocol configuredon the node.

Create a new domain by setting up a new Domain Controller and DNS server usingthe Server Manager.

To set up a new domain, configure the IP addresses of the Domain Server node if thisis not already done.

• Set the IP addresses.

• Set the IP address of this computer as the Preferred DNS Server on the primarynetwork adapter.

• If using, or planning on using two Domain Servers, set the IP address of the otherDomain Server as the Alternate DNS Server on the primary network adapter.

• If using a redundant network, use the sameDNS settings on the secondary networkadapter.

Active Directory Domain Services on First Forest Root Domain Controller

The following procedure was prepared using Install AD DS on the First Forest RootDomain 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 ActiveDirectory Domain Services (AD DS). Refer to the Microsoft article if planningon using alternate methods.

52 2PAA111708-600 L


Membership in the local Administrator account is the minimum required tocomplete this procedure. Details about using the appropriate accounts and groupmemberships 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.

3. On Before you begin page, click Next.

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

5. Click Next.

6. On Select destination server page, click select a server from the pool for newroles.

7. Select current node, click Next.

8. On Select server roles page, select Active Directory Domain Services (ADDS) 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 automaticallyselected.

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. SelectPromote this server to a domain controller.ADDS configuration wizardappears.

18. On Deployment Configuration page, select Add a new forest.

19. Enter Root domain name. (For Example: ABB.local)

2PAA111708-600 L 53


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.

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 DomainController 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 ActiveDirectory Domain Services (AD DS). Refer to the Microsoft article if planningon using alternate methods.

Membership in the Domain Admins group for the domain in which the secondDomain Controller is being installed is the minimum required to complete thisprocedure. Details about using the appropriate accounts and group membershipscan 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) andclick Next.

54 2PAA111708-600 L


4. Select the Active Directory Domain Services check box in the Select ServerRoles dialog box and click Next.

5. Review the information in the Active Directory Domain Services dialog box andclick Next.

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

7. Click Close this wizard and launch the Active Directory Domain ServicesInstallation Wizard in the Installation Results dialog box.

8. ClickNext in theWelcome to the Active Directory Domain Services InstallationWizard dialog box.

9. Select Existing Forest and Add a domain controller to an existing domain inthe Choose a Deployment Configuration dialog box. Type the name of the existingdomain in the forest and then take the following actions:

a. SelectMy current logged on credentials or Alternate credentials underSpecify the account credentials to use to perform the installation andclick Set.

b. Provide the user name and password for an account that can install theadditional Domain Controller (it must be a member of the Enterprise Adminsgroup or the Domain Admins group) in the Windows Security dialog boxand click Next.

10. Select the domain of the new Domain Controller in the Select a Domain dialogbox and click Next.

11. Select a site from the list, or select the option to install the Domain Controller inthe site that corresponds to its IP address in the Select a Site dialog box and clickNext.

12. Make the following selections in the Additional Domain Controller Optionsdialog box and click Next.

• DNS Server: This option is selected by default when AD DS integrates theDNS server service in to the domain so that the Domain Controller canfunction as a DNS server (this is the preferred method).

It is recommended that DNS be installed when the Active Directory DomainServices Installation Wizard is run (keep the default selected), so that the wizardcreates the DNS zone delegation automatically.

2PAA111708-600 L 55


• Global Catalog: This option is selected by default. It adds the global catalog,read-only directory partitions to the Domain Controller, and it enables globalcatalog search functionality.

• Read-only domain controller: This option is not selected by default. Itmakes the additional Domain Controller read-only. For more informationabout read-only domain controllers, refer to:

http://technet.microsoft.com/en-in/library/jj574152.aspx

13. In Active Directory Domain Services InstallationWizard, navigate toAdditionalOption, and in Replicate From select the Domain Node.

14. Use the default locations in the Location for Database, Log Files, and SYSVOLdialog box and click Next.

15. Type and confirm the restore mode password in the Directory Services RestoreMode Administrator Password dialog box and click Next.

This password must be used to start AD DS in Directory Service Restore Modefor tasks that must be performed offline.

16. Review the selections in the Summary dialog box. Click Back if it is necessaryto change any selections.

17. Click Export settings to save the selected settings to an answer file that can beused 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. ClickFinish in the Completing the Active Directory Domain Services InstallationWizard dialog box.

21. A prompt appears asking to restart the server. Select either the Reboot onCompletion check box to restart the server automatically or clear the check boxto restart the server manually to complete the AD DS installation.

System 800xA Network Configuration (3BSE034463*) includes examples of acorrectly configured DNS Server.

A.3.2 Adding Nodes to a DomainThis is required for all member nodes in the 800xA System (not applicable for singlenode installations, for example Information Management consolidation node, or

56 2PAA111708-600 L


Windows Workgroups). Perform this procedure at each node that needs to be addedto the domain.

This procedure requires an administrator user name and password defined for thedomain. Have this information available before proceeding.

1. Log on to the node as a local administrator.

2. Configure the IP address of this node and ensure the DNS server address pointsto the IP address of the DNS server.

3. From the desktop, right-click on Start and select System from the context menuthat 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.

A.4 Configuring Users and GroupsThis section describes how to create the Windows domain users and groups in theActive 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 hasbeen created by setting up a Domain Controller and DNS server as described inConfiguring Domain Controller and DNS Server on page 51.

• This procedure requires being logged in as domain administrator. A defaultdomain administrator is created when the Domain Controller and domain is setup as described in Configuring Domain Controller and DNS Server on page 51.

Refer to System 800xA Administration and Security (3BSE037410*) for detaileddescriptions of users, user groups, and user roles and permissions.

2PAA111708-600 L 57

A Prerequisites A.4 Configuring Users and Groups

Refer to Users, Groups, and Rights Assignments on page 61 for listings ofmandatory users and user groups for the 800xA System.

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. Clientswill always connect to the 800xA System using domain accounts. The onlyexception is Windows Workgroups where domains are not used. In these casesall users and groups are local

For 800xA Systems in a Windows Workgroup all the users and groups shall becreated 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 inSystem 800xA. Create two domain accounts with administrator privileges.

The 800xA ServiceUser will be reserved for use by the 800xA System Services. Thisaccount will NOT be used for installation, administration, configuration, or any othersystem related procedures.

The 800xA Installer account must be created to complete the 800xA System softwareinstallation and post installation procedures. Create other user accounts for other800xA System activities such as Application Engineer, System Engineer, andOperator.

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

Domain Administrator users are powerful for administrative purposes but couldby this also be dangerous from a security perspective. For security reasons thenumber 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 membersof the Domain Administrators group. They both need to be members of theBuilt-in Administrators group on the 800xA System nodes but not on the DomainController, unless it is combined with an 800xA Server.

The 800xA Installation User could be a Domain Administrator but should be setto passive after the installation of the System. The 800xA Service User should notbe a Domain Administrator and also not a local administrator on the DomainController.

The various users and groups required by the 800xA System are described in TableA.2. All groups/users must reside on the 800xA System domain.

58 2PAA111708-600 L


This setup may be performed by yourself, or the domain administrator may performthe setup. In either case, use the guidelines in Table A.2, and follow the step-by-stepprocedures following Table A.2.

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

DescriptionGroups/Users

Create the IndustrialITAdmin Group. All 800xA Systemadministrators (including the 800xA ServiceUser) must bea member of the IndustrialITAdmin group.

IndustrialITAdmin Group

Create the IndustrialITUser Group. All 800xA System usersmust be a member of the IndustrialITUser group.

IndustrialITUser Group

Create a new user for 800xA System services. Make thisuser a member of the IndustrialITAdmin Group, theIndustrialITUser Group, and the local administrator groupon every system node.

800xA Service User

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 asdomain administrator. Adding this user to the localadministrator group on every system node requires beinglogged in as local administrator.NOTE 2: The 800xA Service User must not be a memberof the Domain Administrator group. These users shouldbe members of the Built-in Administrators group on theDomain Controller node.

2PAA111708-600 L 59


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

DescriptionGroups/Users

Create a user for installing software, and performing systemadministration procedures. Make this user a member ofthe IndustrialITAdmin Group, the IndustrialITUser Group,and the local administrator group on every system node.

Installation User

NOTE 1: Creating this user requires being logged in asdomain administrator. Adding this user to the localadministrator group on every system node requires beinglogged in as local administrator.

Create additional users for system configuration andoperation. These users are added to the IndustrialITUserGroup. Refer the System 800xA 6.0 Administration andSecurity (3BSE037410*) for more information on userpermissions.

Other 800xA System users

A.4.1 New Organizational UnitThis organizational unit is not mandatory; however, it may be helpful to put all 800xASystem 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.

A.4.2 GroupsThis 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:

60 2PAA111708-600 L


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 BatchManagement should create the groups with default names IndustrialITAdmin andIndustrialITUser.

A.4.3 Users, Groups, and Rights AssignmentsThis 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 rightsare also the same as in a domain, except all domain policies must be defined on eachlocal node. No additional policies are required for Windows Workgroups.

Ensure that the User Account names do not exceed the 20 character limit.

User Groups and Users

All users must be members of the IndustrialITUser group if they require the abilityto start a workplace.

Table A.3 lists the default User Groups and Users.

2PAA111708-600 L 61


Table A.3: Default User Groups and Users

DescriptionUser AccountUser GroupOrganizationalUnit

800xA System service account800xAServiceIndustrialITAdminIndustrial IT

800xA System installer account800xAInstaller

System installer default accountAdministrator

Additional customer administratorsCustomer Admin

800xA System service account800xAServiceIndustrialITUser

800xA System installer account800xAInstaller

Default operator 1Operator

Default operator 2Operator2

Windows default administratoraccount

Administrator

NOTE: System 800xA does notrequire this account and it isdisabled by default. Enable theaccount if needed.

Additional customer usersCustomer Users

Local Groups and Members on Each Node

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

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

Domain Group/UserLocal Group/User

800xAServiceAdministrators (standard default)

800xAInstaller

62 2PAA111708-600 L


Table A.4: Local Groups and Members on Each Node in System(Continued)

Domain Group/UserLocal Group/User

800xAServiceHistoryAdmin

800xAInstaller

Customer Admin (User can add additional domainusers to group to allow administration of Oracle andInformation Management IM Services)

800xAServiceORA_DBA

800xAInstaller

Customer Admin (User can add additional domainusers to group to allow administration of Oracle andInformation Management IM Services)

User Rights Assignment

Table A.5 lists the user rights assignment.

In case of an Aspect Server combined with a Domain Controller, create a newGroup Policy Object under the Domain Controller object and configure the securitypolicies listed in Table A.5.

The user rights in theWindows security policies shall be configured in 800xA Systemto enable users with right permissions to perform various activities in the system.

For systems using Domain Controllers the user rights assignment security policiesare to be configured from the below location on the Primary Domain Controller:

1. Go to Control Panel > Administrative Tools > Group Policy Management

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 inWorkgroup environment configure the user rights assignment securitypolicies 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.

2PAA111708-600 L 63


The security policies listed in Table A.5 can be configured by performing the followingon 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 A.5.

3. Click OK to close the policy.

Table A.5: User Rights Assignments

Security SettingPolicy

Local Security Policy (each node)

IndustrialITUserAccess this computer from the networkAuthenticated Users

IndustrialITAdminAllow log on locallyAdministrators (Default)IndustrialITUsers ( can be configured based onthe need. Example : On wokplaces its needed,on Server nodes it depends on the site specificneeds who is needed to login locally).

IndustrialITAdminChange the system time

800xAServiceLog on as a batch job800xAInstaller

800xAServiceLog on as a service800xAInstaller

SERVICE (Default)Impersonate a client after authenticationAdministrators (Default)Users that require logover (Process Portal)

Additional Local Security Policies on Batch Server

800xAServiceAct as part of operating system

Adjust memory quotas for a process

Bypass traverse checking

Replace a process level token

Additional Local Security Policies for Harmony/Melody Servers

64 2PAA111708-600 L


Table A.5: User Rights Assignments(Continued)

Security SettingPolicy

800xAServiceAct as part of operating system

Generate security audits

Impersonate a Client after Authentication

A.4.4 800xA Service UserDefine separate accounts and different passwords for the 800xA Service User andthe 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 thisuser to the local administrator group on every system node requires being loggedin as local administrator.

Create the 800xA ServiceUser. This is the user account that all 800xA System serviceswill 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:

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 NewObject - User dialog box specify the user name and login name.Makethe 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, andmake sure the password for this user is NEVER CHANGED.

2PAA111708-600 L 65


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 chooseProperties from the context menu that appears (or double-click the groupname).

c. Select theMembers tab in the Properties dialog box.

d. Click Add. This displays the Select Users, Contacts, or Computers dialogbox.

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 theMembers tab of the Properties dialog box.

8. Add this user to the Builtin Administrators group on the Domain Controller node.

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 Usermay be included in theDeny Logon Locally policy on every system node. However,this will prevent logging in as the 800xA ServiceUser on Report Scheduling Servernodes (Scheduling Server nodes that need to run Excel reports), on 800xA forMelody and 800xA for Harmony. On these nodes, the 800xA Service User mustbe logged in to add the DataDirect add-ins to Excel for this user; to carry out thepost installation and configuration of Melody and Harmony. In such cases, the800xA ServiceUser may be included in theDeny Logon Locally policy after addingthe add-ins, but not before.

A.4.5 User Account for InstallationDefine separate accounts and different passwords for the 800xA Service User andthe 800xA installing User.

Create an administrator account for installing all 800xA System software andperforming all post installation procedures. Follow the procedure for 800xA Service

66 2PAA111708-600 L


User on page 65. The only difference is that this account should be configured sothat the password will expire, and will need to be changed periodically.

A.4.6 Other UsersAdd other IndustrialIT users and make themmembers of the IndustrialIT User Group.Set passwords according to company policy, and change them frequently. Examplesof users who can be members of the IndustrialITUser groups is as shown in TableA.6.

Ensure that the User Account names do not exceed the 20 character limit.

Do not change the 800xAService user passwords.

Table A.6: Examples for User accounts

DescriptionsUser Account

Default application engineerApplicationEng

Default system engineerSystemEng

Default maintenance supervisorMaintenanceSup

Default maintenance engineerMaintenanceEng

Default maintenance technicianMaintenanceTech

A.4.7 Adding 800xA Domain Users to the Local Administrator GroupThe 800xA Service User and 800xA Installing User accounts defined in the domainmust be added to the local Administrator Group on every node in the domain, includingthe Domain Controller node. The different procedures to be followed depend on thenode type:

• Domain Controller Node

• On All Other Nodes

Domain Controller Node

1. Go to Control Panel > Administrative Tools

2PAA111708-600 L 67


2. Select Active Directory Users and Computers to launch the Active DirectoryUsers 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 Propertiesdialog box.

5. Select theMembers 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.

8. Enter the names of the 800xA Service User and Installing User in the text boxand 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 thecontext 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 boxand 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.

68 2PAA111708-600 L


A.5 Operating System Setup Use with 800xA SystemThe following procedures should be carried out in domain account withAdministrator 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

• 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

• Enable the Change Sharing Options for Different Network Profiles

• 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

A.5.1 Regional and Language OptionsPerform the following procedure to set the regional and language options. Theseprocedures must be performed for all users on all nodes in the 800xA System.

The procedure differs depending on the operating system. The procedures describedfor all other supported operating systems:

2PAA111708-600 L 69

A Prerequisites A.5 Operating System Setup Use with 800xA Sy

1. Open Windows Control Panel.

2. ClickClock, Language, andRegion 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 (.). Ifit is not, change it to a dot (.) and click Apply and then OK.

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 OKto return to the Administrative tab of the Region dialog box.

10. Click Copy settings to launch the Welcome Screen and New User AccountsSettings dialog box.

11. Enable theWelcome screen and system accounts and New User Accountscheck boxes and click OK.

12. Click OK to exit the Region dialog box.

13. Close Windows Control Panel.

A.5.2 Enable Write Caching on Hard DisksTo ensure Aspect Directory integrity, the write cache buffer flushing must be leftenabled in theMicrosoftWindowsOperating System. Depending on the configuration,choice of driver, type of hard disks, etc, Windows may allow disabling the write cachebuffer 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 thetransaction 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 toconfigure the disk driver to neglect the flush command. This is normally configuredin the Windows disk drives setting.

70 2PAA111708-600 L


A consequence of, for example, a power or hardware failure can be that a flushing isnot performed. Potentially the Aspect Directory can then become inconsistent andthe system will no longer start. Furthermore the data and applications becomeimpossible to recover.

Refer to Microsoft Knowledge Base article 234656 for more information.

Perform the following procedure on all the Server Operating System hard disks:

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 launchthe hard drive properties dialog box.

5. Select Policies tab.

6. Select the Enable write caching on the device check box for Server andWorkstation Operating System.

For Virtual Nodes: Select Better Performance check box to enable writecaching.

7. Click OK.

8. Close the Computer Management Console.

It may be necessary to verify the Enable write caching on the disk check box isstill enabled after rebooting.

A.5.3 Internet Explorer as Default BrowserCurrently System 800xA does not support Microsoft Edge, hence on Windows10 Professional Operating systems follow the steps below to set Internet Exploreras 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 clickMake Internet Explorer the default browser.

2PAA111708-600 L 71


4. This will open Set Default Programs window > select Internet Explorer andpress Set this program as default.

5. Press Ok to close the window.

A.5.4 Internet Explorer Enhanced SecurityThe Internet Explorer Enhanced Security component must be disabled on all theServer Operating System nodes.

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.

A.5.5 Internet Security Settings for Digital Signature ValidationPerform 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 theCheck for publisher’s certificaterevocation check box.

5. Click Apply and OK.

A.5.6 Disable Web Browser Popup BlockerInternet Explorer offers web browser popup blocker by default. Disable Popup Blockerwhere the thin client portions of the integrated applications (specifically AssetOptimization) are used, since these applications open child window browsers todisplay application data for the user.

72 2PAA111708-600 L


A.5.7 Disable Show Window Contents While DraggingTo prevent CPU intensive redrawing of the window, disable the Windows ShowWindow Contents while dragging feature.

1. Open This PC.

2. Right-click and select Properties from the context menu to launch the SystemProperties dialog box.

3. Select the Advanced System Settings.

4. Click Settings in the Performance frame to launch the Performance Optionsdialog box.

5. Select the Visual Effects tab (this should be selected when the dialog box islaunched).

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 dialogbox.

9. Click OK to close the System Properties dialog box.

A.5.8 Energy Saver and Screen Saver ConfigurationIt is recommended to NOT have any Energy Saving and screen saver functionalityactivated on 800xA System nodes (especially operator Workplace Clients), as thismight lead to longer reaction times in case of an emergency. If the server orworkstation BIOS has an Energy Saver configuration, configure it on a node-by-nodebasis. The Windows energy saving data is user dependent.

The energy saving setting may be accessed in two ways. The BIOS setup is availablewhenever the server or workstation is powered up. It may also be accessed via PowerOptions inWindows Control Panel. The screen saver may be turned off in the DisplayProperties option in Windows Control Panel.

2PAA111708-600 L 73


A.5.9 Virus Scanning Configuration During Installation and PostInstallation

The user should make sure that the installation procedure completes withoutexposing the computers to malware or malicious network traffic of any sort.

This can only be done by limiting the communication to the system and byperforming separate virus scanning of any portable media or disks beforeconnecting them to the system nodes during the installation. After completing thesystem installation and configuration (post installation) it is recommended toperform a full virus scan of all computers in the system.

For better performance during 800xA installation and post installation proceduresdisable virus scanning software. For virus scanners recommended by ABB for usewith System 800xA refer McAfee Integration on page 85 and Symantec on page86.

A.5.10 Windows Update ConfigurationAutomatic Windows Updates are not recommended for the 800xA node. Theinformation 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 canbe found in myABB/My Control System.

To disable the automatic updates by setting the Windows Automatic Updates featureto never check for updates on Windows 8.1 operating systems:

1. OpenWindows 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 toWindows 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.

74 2PAA111708-600 L



A.5.11 Enable the Change Sharing Options for Different Network ProfilesPerform the following to enable the following parameters on all the nodes:

1. Go to Control Panel.

2. Change to Large Icons view.

3. Click Network & Sharing Center.

4. Click Change Advance Sharing Settings.

5. Select the following in Private or Public or Domain profiles:

• Turn on network discovery in the Network Discovery pane.

• Turn on file and printer sharing in the File and printer sharing pane.

A.5.12 Disable Server Manager StartupPerform the following procedure to disable Server Manager not to start automatically.

1. Open Server Manager.

2. ClickManage tab and select Server Manager Properties.

3. Select Do not start Server Manager automatically at logon and click OK.

A.5.13 Hot fix for redundancy with IPSec enabledFor Client Server Network redundancy to work the following hot fix (KB3007072)needs to be installed on all Windows 8.1 and Windows Server 2012 R2 nodes in an800xA System. This hot fix is available on the 800xA media in the following path:

…\3rd_Party_SW\Microsoft\Windows8.1-KB3007072-x64.msu

A.5.14 Set Date and Time for Batch ServersBatch Primary and Redundant servers require a specific time format for the serviceaccount. All other users on the batch server and other nodes can keep the US - Englishdefaults.

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).

2PAA111708-600 L 75


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 formatsfor Date and Time:

a. Click the Format tab.

b. The default value for the Short Date format is M/d/yyyy. Change the ShortDate format to MM/dd/yyyy and click Apply.

c. The default Short time format is hh:mm tt. Change the value to HH:mm andclick Apply.

9. Click Apply.

A.5.15 Disable ISATAP SettingPerform the following procedure on all nodes (800xA or non-800xA) connected onthe same network as the AC 800M Controllers:

1. Open Command prompt with “Run as administrator”.

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

A.5.16 Group Policy ManagementThe group policy management procedures differ depending on the environment(domain or Windows Workgroup).

Domain Environment

Perform this procedure before installing 800xA System and Functional Areasoftware.

76 2PAA111708-600 L


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 domainso that the new Group Policy will replicate out to all nodes in the selected domainvia the active directory. However, if the system is expanded at a later time, the GroupPolicy 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 anew 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 PolicyManagement Console, and selectCreate a GPO in this domain from the contextmenu 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 PolicyManagement Console.

5. Right-click on the new Group Policy Object in the left pane of the Group PolicyManagement Console, and select Edit from the context menu to open the GroupPolicy 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 otherzones, a dialog box appears.

10. Click Enabled and click OK.

11. Double-click Intranet Sites: Include all sites that bypass the proxy server, adialog box appears.


2PAA111708-600 L 77


13. Double-click Intranet Sites: Include all network paths (UNCs), a dialog boxappears.


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 workstationsto 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 thecontext 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 RightsAssignment

5. In the right pane, double-click Add workstations to domain to launch the Addworkstations 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 workstationsto the domain and click OK twice to return to the Add workstations to domainProperties dialog box.

Click Find Now in the Select Users, Computers, or Groups dialog box to displaythe available users and groups.

10. Click Apply and then OK to close the dialog box.

78 2PAA111708-600 L


11. Close the Group Policy Management Editor.

Windows Workgroup Environment

Perform this procedure before installing 800xA System and Functional Areasoftware.

Group Policy. This procedure must be performed on every node in the WindowsWorkgroup. If the system is expanded at a later time, this procedure must be performedon each node added during the expansion.

1. Open Local Group Policy 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.


5. Double-click Intranet Sites: Include all local (intranet) sites not listed in otherzones, a dialog box appears.

6. Click Enabled and click OK.

7. Double-click Intranet Sites: Include all sites that bypass the proxy server, adialog box appears.


9. Double-click Intranet Sites: Include all network paths (UNCs), a dialog boxappears.


11. Close Local Group Policy Editor.

12. Reboot the node.

2PAA111708-600 L 79


A.5.17 Adding Privileges to the 800xA Service UserThis procedure only applies to the following node types. If these node types are notpresent 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 listednode types. Perform the following procedure to add the proper privileges to the 800xAService 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.

A.5.18 Remote (Thin) Client for the Server Operating SystemPerform the following procedure to install the Terminal Server role service andconfigure 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.

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

5. Click Next.

6. On Select destination server page, click select a server from the pool for newroles.

7. Click Next.

8. On Select server roles page, select Remote Desktop Services as additionalrole.

If Terminal Services is already installed on the server, the Terminal Services checkbox will be selected and dimmed.

9. Click Next.

80 2PAA111708-600 L


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 warningmessage indicating that Installing the Terminal Server role service on a DomainController is not recommended will appear.

13. Click Add Features and click Next.

14. Verify the added roles and features onConfirm installation selections page andclick Install.

15. Restart the node when the installation is complete.

A.6 Other Third Party SoftwareThis section details the installation of other third party software that are required forthe 800xA System.

All 800xA installation must be carried out in 800xA Installer account.

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

A.6.2 Microsoft WordWhen installing Microsoft Word it is required to select Office Shared Featuresfrom the Installation Options dialog box and to accept the default subfeaturesunder the Office Shared Features selection.

Microsoft Word, which is part of the Microsoft Office Professional suite, must beinstalled 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)

2PAA111708-600 L 81

A Prerequisites A.6 Other Third Party Software

This software is available from any Microsoft reseller. Follow the installationprocedure described in the documentation provided by Microsoft.

Macro Security for Microsoft Word

Perform the following procedure for every Industrial IT User on every node, afterinstallation of Microsoft Word and before continuing installing or working on theEngineering Platform:

1. Start Microsoft Word.

2. Click the File menu in the left corner.

3. ClickWord 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. SelectMacro Settings in the left pane of the Trust Center.

7. Select Disable all Macros Except Digitally Signed Macros in the right paneof the Trust Center.

8. Click OK to close the Trust Center.

9. Click OK to close the Word Options dialog box.

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

A.6.3 Microsoft ExcelWhen installing Microsoft Excel 2010 or 2013 or 2016 it is required to selectOffice Shared Features from the Installation Options dialog box and to accept thedefault subfeatures under the Office Shared Features selection.

When installing Microsoft Excel, select the Custom installation. When theInstallation Options dialog box appears. select the Visual Basic for Applicationsoption 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 whenthis application starts check box.

82 2PAA111708-600 L


Microsoft Excel, which is part of the Microsoft Office Professional suite, must beinstalled on all 800xA System nodes where engineering tools or Excel based reportswill 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 installationprocedure 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) serveris deployed to the IM server node. Perform the following steps for the 800xA Serviceaccount 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 MacroSecurity for Microsoft Excel.

Macro Security for Microsoft Excel

Perform the following procedure for every Industrial IT User on every node, afterinstallation of Microsoft Excel and before continuing installing or working on theEngineering 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.

2PAA111708-600 L 83


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. SelectMacro Settings in the left pane of the Trust Center.

The macro security setting must be set to Enable all Macros for every IndustrialIT 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 nodein 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 paneof the Trust Center.

8. Click OK to close the Trust Center.

9. Click OK to close the Excel Options dialog box.

A.6.4 Crystal ReportsCrystal Reports can be used to create reports of System 800xAData. When used withthe application scheduler, the reports can be automatically executed.

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 accessto 800xA data reporting interfaces (800xADataDirect or ODBC). Follow the procedureto install Crystal Reports.

System 800xA latest release supports Crystal Reports 2013 SP7 or newer versions.Table A.7 lists the installed versions and available builds in the SAP portal.

Table A.7: Crystal Report Builds

WebsiteBuild

It will be available as part of Crystal reports 2013media.

Crystal reports 2013 SP9 +Crystal Reports Runtime install(CRforVS_redist_install_32bit_13_0_19) 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 A.1 to install.

84 2PAA111708-600 L


http://scn.sap.com/docs/DOC-7824

http://scn.sap.com/docs/DOC-7824

Figure A.1: Crystal Reports Runtime Install

.NET 3.5

Crystal Reports requires .NET 3.5. Before installing Crystal reports. Use Run AsAdministrator to execute the files.

Windows 10:

%ABB800xAMediaRepositoryLocation%\3rd_party_sw\DotNet3_5\Install_DotNET3_5_W10.bat

Windows 8.1/Windows 2012R2:

%ABB800xAMediaRepositoryLocation%\3rd_party_sw\DotNet3_5\Install_DotNET3_5_W8.bat

The default value for %ABB800xAMediaRepositoryLocation% isc:\ProgramData\ABB\800xA\MediaRepository. Windows hides c:\ProgramDataby default, but the path can be typed into windows explorer to navigate to thisdirectory. These files can be run multiple times without negative impact.

A.6.5 Autocad IntegrationAs a prerequisite to use AutoCAD for Document Manager and Parameter Manger,install AUTOCAD VBA Enabler by downloading the software from the AutoCADwebsite.

A.6.6 McAfee IntegrationMcAfee VirusScan® Enterprise has been tested and qualified virus scanner that isused on all System 800xA servers and workstations. Refer to System 800xA Installingand Configuring McAfee ePO Server (9ARD107543-005), for more information.

McAfee need not be disabled during installation, however this might impactInstallation performance of 800xA Software.

2PAA111708-600 L 85


A.6.7 SymantecSymantec Endpoint Protection (SEP) has been tested and qualified virus scanner thatis used on all System 800xA servers and workstations. Refer to System 800xA UsingSymantec Endpoint Protection (9ARD119854-002), for more information.

A.6.8 Bulk SPL TemplateTo work with ABB Engineering Studio BulkSPLTemplate, perform the following:

1. Download and install the following software fromMicrosoft website:MicrosoftVisual Studio 2010 Tools for Office Runtime (x64).

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 thefollowing 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\EngineeringStudio\FunctionDesigner\bin\BulkSPLbin\BulkSPLInstall.exe" "C:\ProgramFiles (x86)\ABB Industrial IT\Engineer IT\Engineering Studio\\"

A.6.9 Process Engineering Tool Integration Specific RequirementsThe following are requirements that exist only for Process Engineering ToolIntegration. Before installing Process Engineering Tool Integration software, installthe following prerequisites, if required:

• INtools/SPI:Must be installed on a non-800xA node. If installing the WebServices component on this node,Microsoft IIS with FrontPage server extensionsmust be installed.

86 2PAA111708-600 L


• For viewing external CAD drawings, one of the following software componentsis required to be installed on the 800xA System node on which the 800xA Clientcomponent of Process Engineering Tool Integration is installed:

– DWGTrueView 2015: Recommended to be used for viewing of AutoCADfiles.

The latest version of DWG TrueView 2015 can be downloaded free of charge athttp://www.autodesk.com

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

A.6.11 Microsoft UpdatesInstall KB4034661 from 3rd_Party_SW\Microsoft on the media on Windows 10LTSB 2016/Windows 10 IoT LTSB 2016/Windows Server 2016.

2PAA111708-600 L 87


http://www.autodesk.com

88 2PAA111708-600 L

Appendix B Acquiring Installation andConfiguration Parameters

This section provides guidelines for acquiring the information needed for installationwith regard to network parameters, software keys, and so on. Gather the requiredinstallation media needed to complete the installation, and confirm that all requiredhardware is in place and meets the system requirements.

An organization should be in place to manage the domain with assignedresponsibilities and methods handling users and security.

Before installing and configuring (post installation) the 800xA System, there areseveral parameters and system settings whose valuesmust be determined and available.Table B.1 provides a worksheet for recording this information. It lists node types andtheir applicable parameters, and provides a Value column for recording theinformation.

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

2PAA111708-600 L 89

B Acquiring Installation and C

Table B.1: Installation and Configuration Parameter Worksheet

ValueParameterNode Type

800xA Installer Account nameAll Nodes

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 localflag

DNS Server addressesPC Nodes

Primary CPU primary and secondary IP addressAC 800MControllers Backup CPU primary and secondary IP address

Tool port IP address

Communication modules

IO modules

Domain nameDomainServer User Groups

Users

Concept of 800xA roles and permissions onsystem, structures, and aspect object level

Network adapter type

Backup needs IP address of primaryDNS Server

90 2PAA111708-600 L


Table B.1: Installation and Configuration Parameter Worksheet(Continued)


Affinity - Aspect Server Base ServiceAspectServer Affinity - Aspect Server node name of clients

Affinity - node name of redundant AspectServers

Network adapter type

Affinity - Connectivity Server Base Service

Affinity - Connectivity Server node name ofclients

Affinity - node name of parallel ConnectivityServer

HSE Subnet address(es)FIELDBUSFoundationConnectivityServer

HSE Subnet Id(s)

AF 100 Bus number800xA forAC 100 CI527A Station number

Path to BCD file

IP address for redundant server node (optional)

2PAA111708-600 L 91




Network Group number800xA forAdvantMaster MB 300 network number1

MB 300 network number2

MB 300 node number

Network interface IP address in PC used forPU410.Since the RTA unit default IP addresses are172.16.168.50 and 172.17.168.50, do notconfigure network area 10 in the RNRPclient/server topology. If the client servertopology is configured as network area 10, thedefault IP address of the RTA unit must bechanged as described in 800xA for AdvantMaster Configuration (3BSE030340*).

Network adapter typeConnectivityServer

IP address(Managed)Switches

Server IP addressDisk Image

Session names

Backup identities and filenames

Since the RTA unit default IP addresses are172.16.168.50 and 172.17.168.50, do notconfigure network area 10 in the RNRPclient/server topology. If the client servertopology is configured as network area 10, thedefault IP address of the RTA unit must bechanged as described in Industrial IT, System800xA for MOD 300 - RTA Unit PU410 andPU412 User’s Guide, Technical Data andInstallation Information (3BUA001442*).

800xA forMOD 300RTA Unit

92 2PAA111708-600 L




IP addresses of IET Modules800xA forHarmony

Onet IP address800xA forMelody Melody Configuration Server Name

ECC MUX IP address800xA forDCI

System Functions and Node FunctionsAll Nodes

2PAA111708-600 L 93


94 2PAA111708-600 L

Appendix C Related Documentation

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

Table C.1: Related Documentation

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

Used for information on the new functions andknown problems that exist at the time of release.

System 800xA 6.0 Release Notes NewFunctions and Known Problems(2PAA111899*)

[1]

Used for information on the issues that have beenfixed at the time of release.

System 800xA 6.0 Release NotesResolved Issues (2PAA112277*)

[2]

Used to help plan the 800xA System based onthe configuration rules and node functions.

System 800xA System Guide TechnicalData and Configuration (3BSE041434*)

[3]

Used for site planning, preparation, powerdistribution, system grounding, and wiringpractices for an 800xA System control system.

System 800xA Site Planning(3BUA000285*)

[4]

Used as a guideline for the engineering planningto be used in the early phases of a System 800xAproject.

System 800xA System Planning(3BSE041389*)

[5]

Used to know more about the licensingmechanisms used in System 800xA such as,obtaining the machine IDs and licenses andapplying the licenses.

System 800xA Licensing Information(2PAA111691*)

[6]

2PAA111708-600 L 95

C Related Documentation

Table C.1: Related Documentation(Continued)


Used to knowmore about the tools used to install,configure and verify an 800xA system.

System 800xA 6.0 Tools (2PAA101888*)[7]

Used to plan and setup the network topology.System 800xA Network Configuration(3BSE034463*)

[8]

Used to gain an overview of System 800xAvirtualization. It helps plan for combining multiple800xA Server nodes on a single computer.

System 800xA 6.0 Virtualization(3BSE056141*)

[9]

Used to install, configure, operate and maintainthe 800xA Multisystem Integration systemextension.

System 800xA 6.0 MultisystemIntegration (3BSE037076*)

[10]

Used to carry out the manual post installationsteps of System 800xA.

System 800xA 6.0 Post Installation(2PAA111693*)

[11]

Used to gain an overview on engineering andconfiguration workflow steps of the System 800xAin the context of an engineering project.

System 800xA 6.0 Configuration(3BDS011222*)

[12]

Used to know more about how to install updatesfor System 800xA.

System 800xA 6.0 Update Manual(2PAA114580*)

[13]

Control

Used to get started with the Control BuilderProfessional for AC800M.

System 800xA Control 6.0 AC 800MGetting Started (3BSE041880*)

[13]

Used as a guideline of what to consider whendesigning an automation solution using ControlSoftware for AC 800M, such as memoryconsumption, CPU load, and task execution. Themanual also contains advice to programmersregarding optimization of code.

System 800xA Control 6.0 AC 800MPlanning (3BSE043732*)

[14]

AC800M

Used for installation and start-up of the CI858communication interface.

AC 800M 6.0 AC 800M DriveBus(3BSE079696*)

[15]

96 2PAA111708-600 L




Used for configuration of control applications withFOUNDATION Fieldbus HSE using the CI860module along with HSE Linking Devices andFieldbus Builder FOUNDATION Fieldbus asFOUNDATION Fieldbus configuration tool.

AC 800M 6.0 FOUNDATION FieldbusHSE (3BDD012903*)

[16]

Used for application notes and advice for wiringand installation of PROFIBUS networks.

AC800M 6.0 PROFIBUS DP Installation(3BDS009029*)

[17]

Used for configuration of the PROFIBUS DP-V1in the 800xA control system usingCI854/CI854A/CI854B communication interface.

AC 800M 6.0 PROFIBUS DPConfiguration (3BDS009030*)

[18]

Used to configure PROFINET IO in the 800xAcontrol system using the communication interfaceCI871.

AC 800M 6.0 PROFINET IOConfiguration (3BDS021515*)

[19]

Used to install, configure, operate and performthe necessary maintenance on all equipmentmaking up the AC 800M or AC 800M HIcontrollers.

AC 800M 6.0 Controller Hardware(3BSE036351*)

[20]

Used to install the new hardware required on thefield level, prepare for installation of the newcontroller on AC 800M and reuse the old SATTI/O units.

AC 800M 6.0 Interfacing SATT I/O(3BSE042821*)

[21]

Used for application notes and proceduresprovided for the wiring and installation ofDeviceNet networks.

AC 800M 6.0 Ethernet/IP DeviceNetInstallation (9ARD000015*)

[22]

Used for engineering and configuration of theCI868 IED using Control Builder, IEC 61850Wizard tool and other third party tool.

AC 800M 6.0 IEC 61850 Configurationfor CI868 (9ARD171385*)

[23]

IO

Used for installation and operation of the DTMsfor S900 I/O and control systems.

S900 I/O Manual DTM 6.0(3BDD010407*)

[24]

Used for mounting and installation procedures forS900 I/O System type S and type N.

S900 I/O S and N System with SA920Installation (3BDD010421R0401)

[25]

2PAA111708-600 L 97




Used for issues related to the installation of theI/O System S900.

S900 I/O Manual Installation-GuideS-N-System SA920 CI920A(3BDD010421R0601*)

[26]

Used for mounting and installation procedures forI/O System S900 type B.

S900 I/O B-System with SA920Installation (3BDD010432R0401*)

[27]

Used for issues related to the installation of theI/O System S900 type B.

S900 I/O Manual Installation-GuideB-System SA920 CI920A(3BDD010432R0601*)

[28]

Used for general installation and configurationinformation for the S800 I/O system.

S800 I/OGetting Started (3BSE020923*)[29]

Used for more information on S800 I/O modulesand termination units.

S800 I/OModules and Termination Units(3BSE020924*)

[30]

Used for more information on PROFIBUS-DP FCIin the S800 I/O system.

S800 I/O Fieldbus CommunicationInterface forPROFIBUS-DP/DPV1(3BSE020926*)

[31]

Used to get information on the I/O modules andtermination units with I.S. interface in the S800I/O system.

S800 I/OModules and Termination Unitswith Intrinsic Safety Interface(3BSE020927*)

[32]

Used for instructions for installation and foroperation of the DTMs in S800 I/O.

S800 I/O DTM 6.0 (3BSE027630*)[33]

Used to install, configure and maintain the S200I/O system.

S200 I/O Hardware (3BSE021356*)[34]

Used to install, configure and maintain CompactI/O (S200L I/O and I/O 200C units).

S200L I/O Hardware (3BSE021357*)[35]

800xA for TRIO

Used to install the CI862 TRIO/Genius Interface,connect TRIO/Genius I/O modules andconsiderations to migrate from the MOD 300control system.

800xA for TRIO/Genius 6.0 GettingStarted (3BUR002459*)

[36]

800xA for Advant Master

98 2PAA111708-600 L




Used to connect the workplaces to a MasterBus300 control network with connected AC 400Controller Series, including MasterPiece 200/1,using 800xA for Advant Master.

800xA for Advant Master 6.0Configuration (3BSE030340*)

[37]

800xA for Safeguard

Used to set up the safety system functionality(including defining displays, configuring controlparameters etc.) and the safety systemconfiguration.

800xA for Safeguard 6.0 Configuration(3BNP004848*)

[38]

Operations

Used to understand the 800xA OperatorWorkplace.

System 800xA Operations 6.0(3BSE036904*)

[39]

Used to install, set up, configure and maintain the800xA for Snapshot Report system extension.

System 800xA 6.0 Snapshot ReportsUser Guide (3BSE060242*)

[40]

Used to install, configure, and operate theVideoNet Connect for 800xA product that is asystem extension to the 800xA system.

VideoNet Connect for 800xA UserManual (2PAA109407*)

[41]

800xA for AC 100

Used to configure System 800xA in order to viewand access the Advant Controller 100 Seriesobjects. Hints for operation and maintenance isalso included in this document.

800xA for AC 100 6.0 Configuration andOperation (3BDS013989*)

[42]

Used to configure the AC 100 OPC Server,configure and build applications for controllers ofAC 100 Series using the AC 100 OPCServer. Usefor information on runtime and maintenance of theAC 100 OPC Server.

AC 100 OPC Server 6.0 Configurationand Operation (3BDS013988*)

[43]

800xA for Freelance

Used to install and upgrade the connectivitysoftware 800xA for Freelance.

800xA 6.0 for Freelance Installation(3BDD011810*)

[44]

800xA History

2PAA111708-600 L 99




Used to install the History components using theHistory installer.

800xA History 6.0 Installation(2PAA107280*)

[45]

800xA Engineering

Used to install and configure the ApplicationChange Management (ACM) server.

System 800xA Engineering 6.0Application Change Management(2PAA108438*)

[46]

Reference manuals

Used to find the System Alarms that are generatedwhen operating an 800xA System.

System 800xA System Alarm Messages(2PAA114623*)

[47]

100 2PAA111708-600 L


Appendix D Installation Media

D.1 Installation Media DeliverableThe System 800xA Installation media is distributed either on a physical media, orvia a zip archive. The physical media is a secure, read-only and tamper proof SolidState Drive (SSD). A zip archive means downloading one or more zip-files frommyABB/My Control System. The archive have to be un-packaged and stored locallyas described in Readme file included in the media.

Table D.1: Installation Media Deliverable

SourceUsageContent

Ordered from ABBInstallation, Update,Upgrade

Full 800xA softwarepackage

Physical disk(SSD)

Download frommyABB/My ControlSystem

UpdatePartial 800xA softwarepackage

Zip archive

D.2 Node TypesTable D.2: Node Types in the Configuration System task

DescriptionNode Types (Configure System task)

The node can configure Server functions.Server

The node can configure Client functions.Client

The node is not prepared to be part of 800xA System.The amount of functions to be configured on the nodeis very limited. This type is typically for e.g. DomainControllers, Information Management - IM DesktopTools, Print Servers and File Servers.

Generic Node

2PAA111708-600 L 101

D Installation Media D.1 Installation Media Deliverable




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

Table D.3: Node Options in the NPT

DescriptionNode Options (NPT)

The node is prepared to be part of an 800xA System.800xA Node

The node is not prepared to be part of 800xA System. This type istypically for e.g. Domain Controllers, Information Management - IMDesktop Tools, Print Servers and File Servers.

Generic Node

The definition of the Node Options in the NPT.

Table D.4: Relation between Node Options and Node Types

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

Server800xA Node

Client

Generic NodeGeneric Node

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

102 2PAA111708-600 L

D Installation Media D.2 Node Types

Appendix E 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 SystemRevision.

The following table lists the revision history of this User Manual.

DateDescriptionRevisionIndex

December2014

Published for 800xA System Version 6.0A

December2014

Added section on Installation process for 800xA SystemVersion 6.0 and included information on accessing theSystem 800xA media from a virtual machine.

B

April 2015Added section for information on System Upgrade supportin this release.

C

October 2015Moved the Prerequisites section to the Appendix, includedthe update workflow in this release and added theguidelines for acquiring the information needed forinstallation with regard to network parameters, softwarekeys, and so on.

D

October 2015Added information on System 800xA Media; included asection on installing the .NET hotfix and Excluding a node.

E

January 2016Updated a cross reference in Appendix A PrerequisitesF

April 2016Published for 800xA System Version 6.0.2G

September2016

Published for 800xA System Version 6.0.3H

September2016

Published for 800xA System Version 6.0.3I

2PAA111708-600 L 103

E Revision History

DateDescriptionRevisionIndex

September2016

Published for 800xA System Version 6.0.3J

November2017

Published for 800xA System Version 6.0.3.1L

104 2PAA111708-600 L

E Revision History

IndexNumerics

800xA service userAdding privileges, 80

AAdding 800xA domain users, 67Adding nodes to domain, 57Adding privileges to 800xA service user, 80Automatic updates, 74

BBackup software, 87

DDefault user groups and users, 61Defragmenting disks, 45Disks and file system, 44

EEnergy saver, 73Excel, 83

FFile system, 44

GGroups, 57

IIE enhanced security configuration, 72InstallationDirectory, 45PrerequisitesAdding 800xA domain users, 67Adding nodes to domain, 57

Adding privileges to 800xA serviceuser, 80Backup software, 87Microsoft Excel, 83Microsoft Word, 81Miscellaneous Windows setup, 69Network adapters, 48Remote client, 80Terminal server, 80Users and groups, 57Windows, 43Windows installation guidelines, 45

Installation data, 89Installation planningPlanning and preparation, 89Installation data, 89

MMicrosoft Excel, 83Microsoft Word, 81

NNetwork adapters, 48

OOther Third Party Software, 81

PPlanning and preparation, 89Installation data, 89

RRemote client, 80

2PAA111708-600 L 105

Index

TTerminal server, 80

UUser groups and usersDefault, 61

Users, 57

WWindows operating system, 43Installation guidelines, 45Miscellaneous setup, 69

Word, 81

106 2PAA111708-600 L

Index