Migration Users Guide

EXPERION HS
RELEASE 511
Migration User's Guide

EHDOC-X248-en-511A
August 2019
Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be
used solely for the purpose submitted, and no part of this document or its contents shall be
reproduced, published, or disclosed to a third party without the express permission of Honeywell
International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a purpose and makes no express
warranties except as may be stated in its written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The
information and specifications in this document are subject to change without notice.
Copyright 2019 - Honeywell International Sàrl
-2-
Contents 3
Chapter 1 - ABOUT THIS GUIDE 7
1.1 Special Terms 7
1.2 Revision History 8
Chapter 2 - BEFORE YOU BEGIN 9
2.1 Experion system migration 9
2.1.1 About Experion HS 9
2.2 Migration applications and tools 9

2.2.1 About Experion Migration Storage Node (EMSN) 10
2.2.2 Experion Software Installation Server (ESIS) 11
2.2.3 Migration Application 11
2.3 Migration planning 11

2.3.1 Choosing the migration method 11
2.3.2 Develop a migration plan 12
2.3.3 Develop a migration timetable 13
2.3.4 Review hardware upgrades 13
2.3.5 Review software requirements 13
2.3.6 EMSN space requirements 13
2.3.7 Considerations for Local Windows groups and local user accounts 14
2.3.8 Migrating other Honeywell products and applications 15
2.3.9 Migrating non-Experion third-party applications 16
Chapter 3 - GETTING STARTED WITH MIGRATION 17

3.1 Migration considerations 17
3.2 Getting the latest software and documentation updates 17
3.2.1 To download the latest software and documentation updates 17
3.3 Time synchronization during migration 18

3.3.1 Planning time topology during migration 18
3.3.2 Time check on system before you start migration 18
3.4 HMIWeb Display Builder and HMIWeb custom displays 18

3.4.1 Migrating Display Builder displays 19
3.4.2 Migrating HMIWeb custom displays 19
3.5 Restoring Excel data exchange 19

3.6 Considerations for canceling the migration 19
Chapter 4 - PERFORMING THE MIGRATION 20
4.1 Complete the pre-migration tasks 20
-3-
4.1.1 Creating a disk image of the hard drive 20
4.1.2 Performing system backup 20
4.1.3 Verifying the Windows manger account passwords 21
4.1.4 Verifying the latest Experion software updates 21
4.1.5 Performing MasterLogic Backup 22
4.1.6 Verifying the communication network 22
4.1.7 Running the Checkdisk utility 22
4.1.8 Calculating the disk space 23
4.1.9 Recording Windows network configuration settings 23
4.1.10 Acknowledging all process and system alarms 23
4.1.11 Disabling file replication before migration 24
4.1.12 Creating a shared folder on the EMSN 24
4.1.13 Checking the synchronization status 25
4.1.14 Disabling antivirus software 25
4.1.15 Setting up an ESIS repository 26
4.2 Migrating ServerB or non-redundant server 27

4.2.1 Close Windows applications 27
4.2.2 Migrating an Experion server 27
4.2.3 Guidelines for naming Experion HS servers 31
4.2.4 Installation considerations 31
4.2.5 Turning off the Windows automatic updates option 32
4.2.6 Setting the display resolution 32
4.2.7 Configuring visual effects for increased performance 32
4.2.8 Customizing the power options 33
4.2.9 Disabling automatic disk defragmentation 33
4.2.10 Turning off Windows Defender 33
4.2.11 Disabling the fast user switching option 34
4.2.12 Disabling the antivirus services and applications 34
4.2.13 Completing the Experion node migration 34
4.2.14 Re-enabling the antivirus software 35
4.2.15 Defragmenting the hard disk 36
4.2.16 Setting up time synchronization 37
4.2.17 Updating custom setup files 37
4.2.18 Updating display files 38
4.2.19 Restoring Windows network configuration settings 38
4.2.20 Updating the Quick Builder database 38
4.3 Migrating SCADA Clients 39

-4-
4.3.2 Migrating an Experion HS SCADA Client 39
4.3.3 Guidelines for naming SCADA Client 42

4.3.17 Considerations after migrating a SCADA Client 47
4.4 Migrating ServerA 48

4.4.1 Migrating remaining SCADA Clients 48
4.4.3 Migrating an Experion server 48
4.4.15 Proceeding with migration 56
4.4.17 Defragmenting the hard disk 56
4.4.19 Updating custom setup files 58
4.4.21 Checking the server status 59
-5-
4.4.22 Synchronizing the server databases 59
4.4.23 Enabling file replication 59
4.4.24 Enabling file backup (flbkup.def) 60
4.4.25 Adding servers to a system 60
4.4.26 Enable EMDB replication 61
4.5 Migrating eServer 62

4.5.2 Migrating an Experion HS eServer 62

4.6 Post migration tasks 70

4.6.1 Converting non-redundant server to redundant server 70
4.6.2 Changing the ServerA to primary 71
4.6.3 Installing the Domain Controller package 72
4.6.4 Upgrading a Windows domain controller 72
4.6.5 Adding a node to a Windows domain 72
4.6.6 Re-establishing Engineering user groups 73
4.6.7 Importing the EDS files 73
4.6.8 Configuring ML Server Configurator Tool 73
4.6.9 Configuring MasterLogic Server (non-redundant server Configuration 73
4.6.10 Configuring MasterLogic Server (redundant server Configuration 74
4.6.11 Configuring Experion Client for ML Server 75
4.7 Troubleshooting Migration 75

4.7.1 Restarting the migration application 76
4.7.2 Correcting the computer name displayed in Configuration 76
-6-
CHAPTER
1 ABOUT THIS GUIDE
The Experion HS R511 migration guide assists you in understanding, planning, and migrating
your current Experion HS system. Specifically, this guide provides information and guidance for
migrating systems to Experion HS R511.
1.1 Special Terms

The following are the terms defined in the document, which are unique to the subject presented
in this guide.
Term Description
Base The release version of Experion that is currently in use before the
release migration.
Experion A location used to store the data (databases, system configuration,

Migration operating system preferences, and so on) when migrating an
Storage Experion platform. For setting up an EMSN, a node in the same
Node network, other than the one which is being migrated, is used.
(EMSN)
Installation A software application that installs the Experion system software

application with minimal user interaction.
Migration A software wizard application which migrates Experion system

Application components to latest release system software.
Supervisory SCADA is an Experion application for process control. It is designed

Control and to interface with serial devices (RS232 and RS485) such as PLCs.
Data
Acquisition
(SCADA)
ServerA and The standardized names of the redundant servers. ServerA

ServerB functions as the primary server and ServerB functions as the
backup server.
System The migration of Experion control system from one release to a

migration latest release.
Migration A tool that is used for saving the server data before migration.
Tool
-7-
Chapter 1 - ABOUT THIS GUIDE
1.2 Revision History
Version Date Description
A August 2019 Initial release of the document.
-8-
CHAPTER
2 BEFORE YOU BEGIN
2.1 Experion system migration

Experion system migration is defined as the upgrade of Experion system components, such as
server and client nodes, to the new release system software. Experion system migration involves
software migration for both servers and the clients. Server migration is the process of upgrading
Experion servers, client, and the software loaded in those systems. Migration can also include
upgrading the computer's operating system or hardware — such as adding more memory to a
server, or upgrading to a new computer (platform hardware).
2.1.1 About Experion HS

Experion HS R511 system software must be installed only on systems installed with Windows 10
Enterprise 2016 LTSB (x64) English version. Experion HS supports only off-process migration,
where the control will not be maintained during the migration process for both servers and
clients.
If you are on a release prior to R410, you must migrate your system to R410 and then to R511.
Ensure you contact TAC to perform migration from any release prior to Experion HS R410 to
Experion HS R511.
Experion HS R511 supports the following migration:
l Experion HS R410 to Experion HS R511
NOTE
OS reinstallation is mandatory when you migrate to R510 from R410 or R430 or R510.
2.2 Migration applications and tools

Various software applications and utilities are developed specifically to help streamline the system
migration process by:
l Detecting system conditions prior to a migration that may cause problems or faults once the
migration begins.
l Detecting inconsistencies in system databases and system components that may cause errors
during migration.
l Automating many of the tasks that are performed during a migration.
-9-
Chapter 2 - BEFORE YOU BEGIN
2.2.1 About Experion Migration Storage Node (EMSN)

The Experion Migration Storage Node (EMSN) is a shared folder which is used to store and
retrieve the database and configuration information, available on the Experion node that is
identified for migration. The EMSN must be set up and located on a node separate from the node
to be migrated, but must be within the same control network or Experion nodes.
The EMSN must have sufficient disk storage so that the information can be copied to the EMSN
from the server or client node to be migrated. You need to calculate and estimate the disk space
needed for the EMSN. Calculations must be based on the node type that is being migrated, the
current release operating on the node, and the database size. You can identify a node and allocate
space for the EMSN before you begin the migration. During migration, you need to create a
shared folder for the EMSN.
Special handling for EMSN hosted in a domain environment
In some migration scenarios, the EMSN is hosted on a computer that is in a domain and the
computer to be migrated is also a member of a domain. Resolution information will be lost for both
the Universal Naming Convention (UNC) path name to the EMSN connection and the security
(account/password) information when the following migrations are performed:
l All systems/releases that undergo a hardware platform upgrade during migration.
l All systems/releases that undergo an Operating System reinstall during migration.
There are several options that users can perform to manually work around this problem, with
option 3 being the preferred method:
1. If the machine is local to the system, (both computers operating within the same network).
a. Use normal UNC.
b. For security (account and password), create a local account (and password) on the
domain system that will match the account used to perform the migration on the node
being migrated.
l Add this account to the Share and File Permissions on the EMSN.
l The account entered should be the Account Name, and the associated password. Or,
you can specify an account on the EMSN by entering EMSNHostName\Account.
l Enter password normally.
2. If the machine is not local to the system, (computers must communicate across a router).
a. Define the server UNC path in the following format: \\ESMN Host IP Address\<<EMSN
ShareName>> For example: \\192.168.0.1\ESMN
b. For security (account and password), create a local account (and password) on the
domain system that matches the account used to perform the migration on the node
being migrated.
l Add this account to the Share and File Permissions on the EMSN.
l Enter the account name as <<EMSN Host IP Address>>\Account. For example:
192.168.0.1\MigAccount.
l Enter password normally.
3. All Cases:
A reconnection failure may occur during migration, (after the hardware platform upgrade
and/or Operating System install).
a. Cancel migration.
b. Enter the DNS, WINS, and other information into the IP Address configuration of each
network card. (TCP/IP properties.)
c. Add system back into the domain. (Reboot of system is required.)
- 10 -
d. Restart migration by starting Setup.exe on the installation media or clicking

Install/Migrate link on the Installer page.
2.2.2 Experion Software Installation Server (ESIS)

Starting in R400, you can use an Experion Software Installation Server (ESIS) to host the Experion
software. The ESIS is a file server/file share. Specifically, it is any accessible Windows networking-
based node or removable media capable of hosting a share with account security that has
available disk space to host the Experion installation media. The ESIS then can be accessed over
the control network for installation and migration of system software on multiple Experion system
nodes undergoing migration.
Using the ESIS, there is no need to insert and swap software media on Experion nodes to migrate
the system software. An ESIS repository consists of a copy of Experion installation media and
Experion HS R511 Experion User Assistance Media. You can create an ESIS repository on a local
hard disk that can be accessed using a network share, USB pen drive, or a removable hard drive. If
ESIS is hosted on a computer which is accessible on the network or a removable drive connected
to a computer which is accessible on the network, then multiple nodes can be installed in parallel,
at the same
TIP
The ESIS and the (EMSN) can be hosted on the same or separate physical nodes. When
combined on the same node, you must create separate shares to access the ESIS and the
EMSN.
2.2.3 Migration Application

The Migration Application is a software application that coordinates the migration of system
software to the latest release for servers and clients. The application is run on a server/client to be
migrated and safely handles system database and configuration information so that it can be
reloaded to the server after the new release system software is installed. It also allows for
hardware and Operating System upgrades during the migration process.
2.3 Migration planning

Preparation for system migration requires careful planning and should begin well in advance. A
successful migration requires coordination and cooperation among various departments and plant
personnel.
Develop a comprehensive migration plan that addresses the considerations described in the
following sections. The plan must also provide information on what to expect in the migration
process and must help the plant personnel to be alert.
This section provides information about preliminary planning, considerations, and tasks that are
essential for a successful system migration.
2.3.1 Choosing the migration method

Experion HS R511 supports the following two installation methods:
- 11 -
l Installation using Experion installation media

l Installation using Experion Software Installation Server (ESIS)
o Network share
o USB pen drive
o Removable hard drive
Following are the high-level tasks to be performed before using each of the options.
Installation method Steps to be performed
Using Experion Install Experion HS R511 using the installation

installation media: media.
Only one node

can be installed
at a time.
Using ESIS on a network 1. Set up the ESIS repository.

share 2. Establish network connection between ESIS and
the node to be migrated
3. From the node to be migrated, browse to the
Multiple nodes
network share that has ESIS repository
can be installed
in parallel using 4. Provide inputs when prompted till installation
ESIS on a starts after which no user intervention is
network share required.
Using ESIS on a USB pen 1. Set up the ESIS repository.

drive or a removable hard 2. On the node to be migrated, insert the
drive removable hard drive or USB pen drive and
browse to the ESIS repository.
3. Provide inputs when prompted till installation
Only one node
starts after which no user intervention is
can be installed
required.
at a time.
2.3.2 Develop a migration plan

It is essential that you develop a migration plan for your control system to minimize any problems
which may occur during a migration, and ensure that the migration is successful. While
developing a migration plan, you must consider the structure and the size of the control system,
and also the process which the Experion system controls.
A system may contain single Experion system, or in a larger system it may contain many Experion
systems. Large plants may contain a number of control systems that have many Experion systems
located throughout the plant.
- 12 -
2.3.3 Develop a migration timetable

Develop a timetable for conducting the migration. Consider the timing of the various tasks that
needs to be performed, and the order of the tasks. Estimate the time required for completing each
task.
Migration time estimates
Use the following information as a reference for estimating the time to perform migration. The
estimates are calculated based on a group of 5-10 stations and redundant servers. These times
can vary significantly based on user experience, database size, and the current condition of the
system.
Migration Task Estimated Time
Overall planning 1–2 days
Preparation and backups 8 hours
OS reinstallation 4 to 6 hours (each path)
ServerA and ServerB migration 3–4 hours each
Migrate each SCADA Client 1–2 hours each 1–2 hours each
2.3.4 Review hardware upgrades

Migrating an existing Experion system to new system software may require an upgrade to the
hardware platform (computer system) which supports software operation. Hardware platforms
may be configured as Experion servers, SCADA Clients or other client nodes. Hardware
components must be compatible with Experion hardware requirements. Typical upgrades include
adding memory cards, installing additional disk drives and upgrading to new network interface
cards.
Verify if the system hardware is supported on the latest release. If hardware upgrades are
necessary, identify which components need to be upgraded or replaced and install these new
hardware components before starting the node migration.
If you have redundant servers, the node hardware for both ServerA and ServerB must be
identical.
2.3.5 Review software requirements

Review and address the software requirements for the migration. Experion HS R511 system
software must be installed only on systems installed with For more information on computer
software specifications, refer to Software Installation User's Guide.
2.3.6 EMSN space requirements

You can use the following information as a guidance to calculate the EMSN space requirements.
- 13 -
l To determine Total space (T), right-click Drive C: and click Properties. The used space is
displayed in the dialog box that appears.
l The Base size in is the estimate for the Experion software installed in the server/client node,
minus Experion data and database files stored on the node.
l Options (O) include third-party applications, although the applications are not saved or
migrated forward during migration.
If you plan to use the same EMSN as storage for other node migrations, you must consider the
additional disk space needed. Identify a system (computer name) in the EMSN file structure that
has completed migration and delete all folders and data located under the system name to free up
space on the EMSN for future migrations.
Estimated
EMSN
Space
Node Type Total space (T) Base size (B) Options (O) needed
T - (B +O)
= EMSN
Server 8 GB + Options 9
SCADA Client 8 GB + Options 9
Formula: Total Space - (Base size + Options) = Estimated EMSN space

Options include third-party software and applications installed on the
node, so on.
2.3.7 Considerations for Local Windows groups and local user

accounts
CAUTION
If a new Operating System is installed or hardware platform is changed, all the custom local
user groups, custom local user accounts, and user-defined security policies (such as access
control lists on files and directories) are not saved during the migration.
Custom local user groups and custom local user accounts must be saved or documented in order
to restore them after the migration, if needed. You must capture the specific configurations and
settings for these groups and accounts, so that they can be restored. Any user specific files/folders
and their associated Access Control Lists (ACLs) settings and any user-defined security policies
that are not created during the Experion installation must be saved, so that they can be loaded to
the migrated system.
Note that Experion standard local groups, user accounts and policies are saved and restored to the
system by Experion Migration.
The Experion standard local account includes the following:
l LocalComServer
l mngr
- 14 -
Both the Experion standard local accounts are used only by services/servers. They are not
allowed to be used interactively.
2.3.8 Migrating other Honeywell products and applications

The following Honeywell applications could be installed on nodes within an Experion system and
are not migrated as part of Experion migration. Specific considerations for some of these
applications when migrating Experion software are described below. During migration, you may
get a message screen that informs you about the software applications (both Honeywell and third-
party applications) that will not be migrated forward. Appropriate actions should be taken to
preserve these applications and user settings so that they can be restored after migration.
l Customized system components and display files must be manually saved since they are not
migrated and restored in the new release. For example:
o Point detail displays
o Customized Faceplates and Customized displays o Custom Station menu
configurations (*.stb files) o *.css files
l Digital Video Manager (DVM) — Compatibility with Experion — DVM. See the Digital Video
Manager User Guide for details to migrate DVM client and host components.
l Process History Database (PHD)
l Safety Manager - If you have Experion systems with Safety Manager, consider the following
before migration:
o Check if the new Windows platform used on a migrated Safety Station (the station
running Safety Builder — Safety Manager's Safety Station software) is supported by
the release of Safety Builder you have installed. For more information refer to the
Safety Manager Software Reference or the Release Notes of Safety Manager installed
in the system.
Safety Builder is not recommended on Experion server/station nodes.
o Check the time synchronization topology used for Safety Manager.

o Before migrating the Experion system, you must backup the Safety Manager
applications loaded on the station you are about to migrate to a new release, and you
must uninstall the Safety Builder software from that station.
o During the migration of Experion servers or stations, Safety Manager and/or Channel
link status might report communication failures.
o After migrating your station to the new release, you must reinstall Safety Builder on
your station and restore the Safety Manager application(s).
o If Safety Manager continues to report communication failures after completing the
migration, download the diagnostics on the Safety Station and reset the Safety
Manager.
o For details about taking back up and restoring Safety Manager applications, as well as
removing and installing instructions for Safety Builder, see the Safety Manager
Software Reference.
- 15 -
2.3.9 Migrating non-Experion third-party applications

Most non-Experion applications are not migrated as part of Experion migration. If your control
system includes non-Experion (third party) applications, consider a strategy for saving the data
and configuration files for the application so that the data and user settings can be restored with
the application after Experion migration is completed. Take appropriate steps to save these files
and applications. During server migration you may get a message screen that informs you about
the software applications that will not be migrated and that will be deleted from the node.
Additional considerations should be made such as:
l Are the third-party applications currently operating with the Experion system compatible with
the new release Operating System requirements?
l Are third-party applications interoperable with the new Experion platform software release?
l Are there upgrades available for the third-party software?
l Should compatibility testing be performed offline to ensure that the applications will operate
properly?
The following are some examples of third-party software applications:

l Antivirus applications are not migrated as part of Experion migration.
l Oil/Movement/Blending, Business applications.
- 16 -
CHAPTER
3 GETTING STARTED WITH MIGRATION
This section describes the tasks that you need to perform to start the migration process. Before
you begin the migration, ensure that:
l You have read the Experion HS R511 SCN which contain the last-minute information that was
not included in the standard documents. You must read this document to find out any
migration related information that is applicable to the system you are migrating.
l You have read the migration planning information for information related to your system and
the planned migration.
3.1 Migration considerations

The following sections contain important information that you should consider before you begin a
migration. The information is arranged by system function or feature and describes conditions
where data may be lost through the migration process, if precautions are not taken or procedures
are not followed. Where possible, workarounds are provided to help safeguard and restore data.
Therefore, if your Experion system contains certain configurations of system components or uses
these features, you must read the related topics of interest to determine if the information is
relevant to your system or situation. If so, take precautions to backup your data files and follow
any required workarounds.
3.2 Getting the latest software and documentation updates

Before installing Experion HS, check the Honeywell Process Solutions website for software and
documentation updates.
3.2.1 To download the latest software and documentation updates

1. In your Web browser application, type http://hpsweb.honeywell.com/Cultures/en-
US/Products/fieldsolutionssalesnet/default.htm.
2. Click Login to My Account.
If you are a new user, you must register for access to the web site.
3. Click Modular Control Solutions link on the left side.
4. Click Experion HS to access the links that contain the latest notifications, software and
documentation updates.
5. Click Technical Information link.
The latest software and documentation updates are available in the links under respective
releases.
6. Download the required software updates, if any.
- 17 -
Chapter 3 - GETTING STARTED WITH MIGRATION
3.3 Time synchronization during migration
3.3.1 Planning time topology during migration

Maintaining the correct time synchronization throughout migration is critical. If you have a time
topology for your system, you must verify whether the current time topology is comprehensive
enough to distribute time to all the system nodes during a migration. Otherwise, you should
establish a time topology that provides reliable time distribution to all the system nodes.
The system time source should derive its time from a reliable external time source.
3.3.2 Time check on system before you start migration

Server time and time zone settings must remain consistent during migration. Before starting
migration on a redundant server pair, ensure that the time and time zone settings are the same
on both ServerA and ServerB, and the client nodes. Change the time settings, if necessary. After
migration, check the time zone settings on the server and client nodes to ensure that they are the
same.
Do not change time zone settings during a migration.
Additionally, check the time zone setting on other servers in the system, and make the changes so
that all the nodes are set to the same time. .
Experion software includes support for the latest Daylight Savings Time fixes. However, due to
recent global time zone adjustments, it may be necessary to reset the time zone settings during
some migration scenarios. You need to verify the time zone and set the time (if necessary) after
the software upgrade, but before re-establishing server redundancy, and all other nodes.
3.4 HMIWeb Display Builder and HMIWeb custom displays
Systems that use customized (user-defined) displays created in Display Builder (.dsp files)
and/or HMIWeb Display Builder (.htm files) should follow these important considerations.
Not following these recommendations may result in the loss of customized display files.
You must back up any file that contains user-defined information, (such as customized displays)
before starting the migration. These files may not be migrated as part of the migration process and
need to be reinstalled after migration.
Any custom display files may be stored in a user-defined location and may not be migrated
forward. Hence you must manually save these files before migration and then restore it after
migration. For example, you must back up and save the following files before starting migration.
l Point detail displays
l Faceplates
l *.css files
l *.htm files
- 18 -
Chapter 3 - GETTING STARTED WITH MIGRATION
3.4.1 Migrating Display Builder displays

Custom Displays built using Display Builder (.dsp files) can be made available on an upgraded
Experion Station provided that:
l The displays are custom displays
l The references to server data in the custom displays are limited to point parameters and data
in user tables.
In Display Builder when you save a display (.dsp file), you can specify the display release for the file.
This allows you to save the display in an old format which would allow you to use the display file
with an older release of Station. Once a display file has been updated or saved for a newer release,
it cannot be displayed on a Station operating on an older release.
3.4.2 Migrating HMIWeb custom displays

You must use either HMIWeb Display Builder or the Bulk Display Migration tool to migrate all
custom HMIWeb displays (.htm files) to the new Experion release. After you migrate a node to the
new release, you must use either HMIWeb Display Builder or the Bulk Display Migration tool to
migrate the display files before you can display the custom or user-defined HMIWeb displays (.htm
files) in Station. For example, when a display file (created in an older release) is opened using a
new release of HMIWeb Display Builder, the file is automatically converted to the new display
format by saving the file in the new format. If you want to update the HMIWeb displays in bulk, you
can use the Bulk Display Migration tool (bulkdisplaymigrator.exe).
3.5 Restoring Excel data exchange

Microsoft Excel (if installed) and Excel data exchange can be restored to an Experion node either
during or after migration of the node.
Restoring it during migration requires that you install Excel and set up data exchange on the node
after the installation or re-installation of the Operating System and before the upgrade/installation
of the new release of Experion is started.
Excel can be installed after migration of the Experion node, but you may encounter error dialogs
during the migration; (click OK to continue and complete the migration). For information on
restoring Excel data exchange on an Experion node, refer to the section “Setting up Microsoft
Excel data exchange” in the Supplementary Installation Tasks Guide.
3.6 Considerations for canceling the migration

There are no critical points for canceling server/client migration as the control system is not
operating. If necessary, restore all the migrated nodes to the base release. If you need to restore
any server or client node to the base release, you can use a disk image (saved prior to migration) to
restore the node to the base release. First you must cancel or abort any applications that are
running; then load the disk image to the node.
- 19 -
CHAPTER
4 PERFORMING THE MIGRATION
l When migrating redundant server systems, you must migrate ServerB first. After completing
ServerB migration, verify if the migration is successful and then proceed with the migration of
rest of the nodes.
l Ensure you have created a disk image of ServerB before you stop it. If you want to rollback the
migration, a disk image can make the process easier. If you restore ServerB from a disk image
and ServerB is part of a domain, you need to remove the computer from the Windows domain
and then add again and reestablish the trust relationship.
l All the nodes (servers and stations) must be migrated to the target release before the system
is restarted and nodes start communicating again.
l When migrating non-redundant server systems, perform all the migration tasks on the non-
redundant server.
Node Type Refer to
ServerB or non-redundant Migrating ServerB or non-redundant server.htm

server
SCADA Clients Migrating SCADA Clients.htm
ServerA Migrating ServerA.htm
eServer Migrating eServer.htm
4.1 Complete the pre-migration tasks

This section describes the tasks that you need to perform in preparing the system for migration.
Ensure that you perform these tasks in the order in which they are described.
4.1.1 Creating a disk image of the hard drive

Create a disk image (ghost) of the hard drive for the node that is to be migrated. This image can be
used if you need to restore the node to its original condition. For more information on creating
backup, refer to the Backup and Restore Guide in the Experion User Assistance Media
4.1.2 Performing system backup
The system backups must be up-to-date. Before starting the migration, ensure that the
system files are backed up.
- 20 -
Chapter 4 - PERFORMING THE MIGRATION
1. On the server, browse to.

l c:\Programdata\honeywell\Experion PKS\server\data\flbkup.def.
2. Save a copy of the flbkup.def file to a remote location, such as another system, removable
media or a file server.
4.1.3 Verifying the Windows manger account passwords

Although Windows security prevents you from discovering the password for the Windows mngr
account, you can check whether a password is correct by attempting to log on as mngr using that
password. The Windows mngr account is used by most Experion services and applications to
communicate with each other. For example, if the password is changed on the server, applications
on client computers can no longer connect to the server because they continue to use the old
password. This means that the password must be the same:
l On all Experion computers
l For all services that run under the mngr account
Considerations
l Passwords must be 8 to 14 characters in length and must contain at least one number and at
least one alpha character.
If you are unable to verify the passwords, you must change the password on each node. Use the
Password utility to change Experion Windows account passwords across the Experion system.
To change the Experion Windows account passwords
1. Log on as a user with Administrator privileges.

2. Browse to C:\Program Files x 86\Honeywell\Experion PKS\Utilities\pwdutil and double-click
PWDUtil.exe.
3. Click Allow.
4. Select mngr.
5. Type the new password in the Password and Confirm Password dialog boxes and then click
OK.
6. Click Go back and change password.
7. Click Done.
8. Click OK.
If the Password utility warns you that an existing Windows account is no longer
required, you must delete these Windows accounts, unless another application,
other than Experion, uses these Windows accounts.
9. Restart the computer.
4.1.4 Verifying the latest Experion software updates

Ensure that the software updates downloaded from the Honeywell Process Solutions website are
of the latest version. You must enable or reinstall the Experion software updates after migrating to
the new release.
- 21 -
4.1.5 Performing MasterLogic Backup

This section provides the pre-migration steps for MasterLogic backup.
Pre-migration steps
1. Disable all the MasterLogic Channels.

2. Manually note down the PLC configuration details such as configured IP address, Parent
Asset and PLC Configuration from the ML Server Configurator Tool. In dual-server setup, the
details must be noted from the Primary Server.
3. Initiate the migration.
4.1.6 Verifying the communication network

You must ensure that all the communications networks are intact. Verify that there are no
reported errors or active alarms on devices, in the I/O network (not applicable for eServer), or in
the supervisory communication networks. If there are any active errors or alarms, you must
resolve the faults/errors before starting the migration.
4.1.7 Running the Checkdisk utility

To run the Checkdisk utility on a local drive
1. In Windows Explorer, right-click the local hard disk drive and click Properties.
If you have multiple hard disks, you have to follow the procedure separately for each hard disk.
The local hard disk Properties dialog box appears.
2. Click the Tools tab.
3. Click Check Now under Error-checking. The Check Disk dialog box appears.
4. Click Automatically fix file system errors.
Unless a previous check for file system errors has detected bad sectors, do not select Scan for
and attempt recovery of bad sectors.
5. Click Start.
As the file system locks the hard disk, the computer cannot scan for file system errors until the
computer is restarted.
6. Click Schedule disk check to schedule the operation to occur the next time the computer is
started.
7. Click OK and restart the system.
The computer checks for file system errors during startup.
8. Log on to the computer using a Windows account with Administrative privileges.
9. Review the disk report in the Event Viewer. To display the Event Viewer:
a. Right-click the Computer icon on the desktop.
b. Click Manage.
The Computer Management dialog box appears.
c. Expand the Event Viewer under System Tools.
d. Click the Application.
If the disk report contains bad sector error, you must restart this task, and select Scan for and
attempt recovery of bad sectors option. If a hard disk continuously reports bad sectors, it
should be replaced as it usually indicates that the hard disk is experiencing hardware
malfunctions.
- 22 -
4.1.8 Calculating the disk space

You must calculate the disk space required to support the migration of the node. Experion
Migration Storage Node (EMSN) must be setup according to the calculated space requirement.
Setup the EMSN before starting the migration. For more information on setting up EMSN, refer to
Creating a shared folder on the EMSN.
To calculate the disk space
1. Using Windows Explorer, navigate to the history archive directory C:\Program

Data\Honeywell\Experion PKS\Server\Data\Archive
2. Right-click the directory and click Properties .
3. Estimate the free disk space required to save the server data, by adding 400MB to the size of
the history archives.
4. If the estimated size is greater than the free disk space on the server (or the destination
computer), then copy the history archive files to a removable media and delete these files from
the server before proceeding further.
4.1.9 Recording Windows network configuration settings

Experion migration does not save and then migrate all Windows network configuration settings for
the node. You must record the Windows network configuration settings for each node in the
system. For Experion nodes on a single or dual Ethernet network, the Interface Metric, DNS, link
speed, and other settings are not saved during migration and must be restored manually after
migration.
To record the Windows network configuration settings
1. Open Command Prompt.

2. Type ipconfig/all and press ENTER.
The network configuration settings are displayed.
3. Print the contents of the Command Prompt window or record these settings.
4. In addition, record your mapped network drives, so that they can be restored after the
migration.
4.1.10 Acknowledging all process and system alarms

You must perform this task only on Server B.
If there are persistent or recurring errors or alarms in the system, they must be addressed and if
possible corrected prior to beginning the migration. This helps to minimize errors and the elapsed
time for completing migration.
Acknowledge all process and system alarms. Resolve any alarms that are critical to your process.
After migrating to the latest release, the system recovers all alarms automatically. However,
information messages, alarm acknowledgement, shelving, and suppression states are not
retained.
To view the system alarms
- 23 -
1. Open the Station.

2. Choose View > Alarms.
The Alarm Summary is displayed.
3. Verify that there are no critical alarms or failures. If there are any critical alarms of failures,
resolve the issue and proceed with the migration.
4.1.11 Disabling file replication before migration

You must disable file replication on the node to be migrated.
To disable file replication
1. In Station, click Configure > File Replication.

2. Change to the mngr security level.
3. On the file replication page, clear all the Send check boxes.
While reinstalling the OS, review each custom file replication configuration on the
computer which uses custom file replication to send files, and note the following:
l The share name and path used for each custom file replication on each
Experion server involved in the migration.
l The computer name, share name, and path on every computer listed as a
specific computer (PC) within those custom file replications, if they are different
from the server's share name and path for the same replication.
This information is required to recreate the Windows network shares on each

computer required for file replication before re-enabling the custom file replications
after the migration.
4. Close Station.
4.1.12 Creating a shared folder on the EMSN

You must create a shared folder on the Experion Migration Storage Node (EMSN) to store the
database and configuration information that can be retrieved during the migration. The EMSN
should be created on another system separate from the node to be migrated but within the same
network.
To connect to this shared folder from another computer, you can use one of the following options:
l Connect as the Administrator of the node designated as the EMSN.
OR
l Create a local account on the Windows domain, and assign full control permissions to the
shared folder for this user.
To create a shared folder on the EMSN
1. Create a folder named Backup, on the node designated as the EMSN.

2. Right-click the folder and click Sharing and Security.
3. Click Share this folder.
4. In the Share name box, type the name of the share as Backup.
- 24 -
5. If you have created a local account on the Windows domain to access this shared folder, do
the following:
a. Click Permissions.
b. Click Add to locate the local account created on the Windows domain, and then click OK.
c. In the Group or user names list, select the account name that you have added.
d. In the Permissions list, click Full Control.
e. Click OK.
6. Click Apply and then OK.
4.1.13 Checking the synchronization status

Ensure that you check the synchronization status before starting the migration.
To check the synchronization status
1. Log on to Station running on ServerA.

3. Click View > System Status > Server Redundancy to open the Server Redundancy Status
display.
4. Check that the backup server (ServerB) is running and that the servers are synchronized.
5. If ServerB is not running, start ServerB to system running status.
6. If ServerB is running, however the servers are not synchronized, click Synchronize.
4.1.14 Disabling antivirus software

You must disable any virus protection software and stop all virus protection related services on the
system you are migrating.
To disable antivirus software
1. Launch McAfee > VirusScan Console.

The User Account Control dialog box appears.
2. Click Continue.
3. In the VirusScan Console window, click Task > Properties. The Access Protection Properties
dialog box appears.
4. Clear Prevent McAfee services from being stopped check box.
5. Click Apply and then click OK.
6. Close the VirusScan Console window.
7. Right-click on Start, and then select Run.
8. Type services.msc and then click OK.
9. Click Continue.
The Services window appears.
10. To disable the antivirus software, perform the following steps:
a. Right-click McAfee Framework Service and then click Properties. The Properties dialog
box appears.
b. On the General tab, click Stop.
c. From the Startup type box, select Disabled.
- 25 -
d. Click Apply, and then click OK.

Repeat the steps 9a through 9d for McAfee McShield and McAfee Task Manager
Services.
4.1.15 Setting up an ESIS repository

ESIS repository consists of a copy of the Experion installation media , required for installation. You
can create an ESIS repository on a local hard disk that can be accessed using a network share.
This section is applicable only if you want to install Experion from ESIS repository.
Prerequisites
l Create a folder that functions as the ESIS repository, in the required location. The destination
folder can be created only on local system drives.
l Ensure that minimum space of is available on the ESIS server for setting up the ESIS
repository.
l Ensure you have .Net 2.0 (minimum) installed on your system.
l Disable On-Access Scan for your antivirus program prior to starting the ESIS setup. Ensure
that you enable On-Access Scan for your antivirus program after you have completed the ESIS
setup.
To set up the ESIS
1. Insert the Experion installation media then click Run Experion HS Media Browser in the
AutoPlay dialog box.
The Honeywell — Experion Installer – R511 page appears.
2. Click Setup an Experion Software Installation Server.
If the ESIS tool fails to start and an error message .Net2.0 or higher needs to be installed.
appears, click OK to exit. Go to <Install
Media>\Packages\Microsoft\DotNet3.5\dotnetfx35SP1.exe and install .Net framework 4.5.
3. If a dialog box with file security appears, click Yes.
l Create a new ESIS Repository
l Upgrade existing ESIS Repository
l Resume a failed ESIS Repository creation
l Remove existing ESIS Repository
When the ESIS Preparation Utility is started on the computer for the first time, only
the option Create a New ESIS Repository is enabled by default; all the other options
are disabled.
4. Click Create a New ESIS Repository, if not already selected and click Next.
5. On the Select a path screen, click Browse to select the destination folder for the ESIS
repository.
6. Click Next.
If you select local system drive, a message prompting to share the destination location
appears.
- 26 -
7. Click OK.
The Folder Properties dialog box appears.
Consider the following before setting up permissions for the shared folder:
l Provide only Read permissions to the share.
l Provide share access permissions only to a single user account.
l Do not provide share access permissions Everyone or groups.
8. To set the folder permissions, perform the following steps.

a. In the Folder Properties dialog box, click the Sharing tab and then click Advanced
Sharing.
b. In the Advanced Sharing dialog box, select Share this folder check box.
c. Under Settings, type the Share name and click Permissions to assign permissions (Read
permission or Read and Write permission) to this share.
d. Click OK to close the Permissions dialog box.
e. Click Apply and then OK to close the Advanced Sharing dialog box.
f. Close the Folder Properties dialog box.
9. In the Select media page, select the check boxes against the names of the media to select the
media for ESIS repository creation and click Start.
A message to close all the Explorer windows appears.
10. Close all the windows and click OK to proceed. The Status Display screen appears.
If My Documents folder appears, close it.
11. After the media is copied, the Description is updated to ESIS Repository [<Name>] created
successfully at <Destination Location>.
12. Click Finish.
4.2 Migrating ServerB or non-redundant server

This chapter describes the tasks that you need to perform to complete the migration of
ServerB/non-redundant server. Complete the pre-migration tasks to ensure that the Experion
system is ready for migration.
4.2.1 Close Windows applications

You must close all Windows applications before starting migration.
4.2.2 Migrating an Experion server

This section describes the procedure to migrate an Experion system to Experion HS R511.
- 27 -
Prerequisites
l Ensure you have the following installation media:

o Microsoft Windows 10 Enterprise 2016 LTSB (x64)
o Experion HS R511 installation media
l When prompted, ensure you enter the same mngr password that was used at the beginning of
the migration.
l If you are using the Experion Software Installation Server (ESIS) to perform migration, make
sure that you have properly created the ESIS share.
l If you have installed MasterLogic Server, ensure that you have disabled the MasterLogic
channel.
Performing the migration
1. If a software protection key (dongle) is specified on the license certificate, insert this key on the
computers USB port.
The Found New Hardware dialog box appears.
2. Wait for the Operating System to complete the USB driver installation. Ignore any warning
dialog box that appears and proceed with the installation.
3. Perform one of the following:
Option Steps to be performed
If you are using ESIS to perform If installing from a network share:

the migration.
a. To connect to the ESIS repository, right-click Start >
Run and type \\<ESISServer IP>\<ShareName>.
Press ENTER.
b. If prompted for Windows credentials.
l Type the <Domain Name>\Username and
Password if you belong to a domain and if you
have share permissions.
l Type the<ESISServer IP>\Username and
Password if you belong to a workgroup and if
you have share permissions.
l Clear the Remember Password check box.
c. Double-click the setup.exe at the root of the

\<ShareName>.
d. If prompted for UAC, click Allow. If you are prompted
for the Windows credentials.
l Type the <ESISServer IP>\Username and
have share permissions
l Clear the Remember Password check box. The
Welcome To ESIS Tool page appears.
e. Type the Information for connecting to ESIS Share.

f. Click Next.
The Welcome to the Honeywell Experion HS
- 28 -
R511 Migration Setup Wizard page appears.
If you are migrating from ESIS

network, you must add the EMSN path
to the IE trusted site.
If you are using Experion a. Insert the Experion installation media in the DVD
installation media drive. The AutoPlay dialog box appears.
b. Under Install or run program, click Run Experion
Media Browser. The Honeywell — Experion HS
Installer — R511 page appears.
4. In the Welcome to the Honeywell Experion HS R511 Migration Setup Wizard page, click Next.
The License Agreement page appears.
5. Click I accept the terms in the license agreement and then click Next. The Setup type of Node
to migrate page appears. By default, the setup detects and lists the node that is being
migrated.
6. Click Next.The User and License Information page appears.
7. (This step is not applicable for Migrating SCADA Clients. For SCADA Clients, click Next on the
User and License Information page.) Browse the license file and click Next.The Existing
Packages Details page appears.
8. When migrating Experion HS R410 or R430 or R510 to R511 the Experion Migration Storage
Node and Advanced Migration Options page appears, with an option to re-install the operating
system. Perform one of the following options ONLY If you select the option Operating System
Re- installation.
l l If you select Local EMSN option, then EMSN folder is stored in the software path.
If local EMSN is not required to be stored after migration, then you can select Select this
to delete EMSN once Migration Complete (this helps to manage the disk space) check box.
l l If you select Remote/Network EMSN option, then perform the following:
a. Verify the Select Drive to connect Network Folder list.
b. In the Network Folder text box, click Browse and locate the EMSN node and the shared
folder (for example, \\<IP address>\EMSN>) or type the full path to the EMSN shared
folder, in the format as per the following options.
o For Workgroup: \\<IP_address_of_EMSN_node>\<EMSN_shared_folder>
o For Domain: \\< Domain Name >\<EMSN_shared_folder>
If you want to select EMSN folder from USB drive, click Browse and locate the EMSN
folder. The User Name and Password options are disabled, if you select EMSN folder
from USB drive.
c. Type the User Name and Password to connect to the shared folder.
If you have created a user account on the Windows domain for this purpose, type this
user account and password. Otherwise, type the user name and password of an account
with administrative privileges on the EMSN node.
- 29 -
9. Whenmigrating Experion HS R410/R430/R500/R510 to R511, the Experion Migration Storage

Node and Advanced Migration Options page appears.
a. From the Select Drive to connect Network Folder list, select the drive letter that is
assigned to the mapped EMSN shared folder.
b. In the Network Folder box, type the full path to the EMSN shared folder, in the following
format:
For Workgroup: \ \<Computer_name_of_EMSN_node>\<\EMSN_shared_folder> and
For Domain: \ \< Domain Name >\<EMSN_shared_folder> Or
Click Browse and locate the EMSN node and the shared folder. For example,
\\192.168.0.1\EMSN
You must add the EMSN path to the IE trusted site if you are migrating using ESIS
network.
You must add the EMSN path to the IE trusted site if you are migrating using
ESIS network.
10. Review the package details and then click Next. The Installation Path(s) Selection page
appears.
11. Click Next, if you are using the default installation path. Or
Perform the following to specify a new installation path.
a. Click Change and then click the Browse button corresponding to the path you want to
change.
b. Specify a new installation path.
c. Click Next.
The Feature and Options Selection page appears.
Under Experion HS Install Option the Typical option is selected by default.
12. Click Next, if you do not want any Add-on Features to be installed. Or
Perform the following to install Add-on Features:
a. Click Custom and then select the check box corresponding to the feature you want to
install.
b. Click Next.
The Experion Migration Storage Node and Advanced Migration Options page appears.
13. Click Next.
The Experion Accounts Passwords Entry page appears.
14. Type the password(s) for the Windows MNGR, Expengr, Expoper, (Experion SQL Agent Account
is not applicable for SCADA Clients), and Experion SQL Agent Account and then click Next.
15. (This step is not applicable for Migrating SCADA Clients.) Type the password for the Experion
SQL Account and click Next.
The Summary page appears.
16. Click Install.
The installation begins and few Experion components are installed with no user interaction.
The setup continues until the end of Phase-I migration. “A message appears that Phase 1 of
migration is complete. Reinstall the Operating System."
- 30 -
17. Install Microsoft Windows 10 Enterprise 2016 LTSB (x64) Operating System. The system
restarts after the Operating System installation.
l Ensure that the computer name has not changed after reinstalling the OS.
If you have changed the computer name, correct the computer name following
the steps in the section .
l The following sections explains the tasks that you must perform in order to
customize the OS.
4.2.3 Guidelines for naming Experion HS servers
CAUTION
You cannot change the computer name of the Experion HS servers after the installation.
However, if you want to change the computer name, you must reinstall the servers
software.
All Experion HS Servers/client computers must have a unique fixed name and IP address. The
following are the basic restrictions when naming the servers/client computers.
l The computer name must be 14 characters, or less, in length.
l The computer name must begin with an alphabetic character. For example a to z, or A to Z.
l The computer name cannot contain spaces or other non-standard characters.
l For non-redundant servers nodes, the computer name MUST NOT end with A or B.
l For redundant servers nodes, the computer name MUST end with A or B.
l The computer name must not end with "0" or "1". (Ending a name with 0 or 1 may result in
communication failure if you have redundant networks, because 0 and 1 suffixes are
appended to the computer names in host files to identify redundant links.)
4.2.4 Installation considerations

Ensure that the following tasks are performed before you begin installation.
l You must use a user account with administrative privileges to install Experion. Do not use the
default Windows administrator account.
l For redundant systems, the node hardware for ServerB and ServerA must be identical.
l If User Account Control dialog box appears, click Continue or Allow as applicable to proceed with
the task.
l Verify the operating system installed on your system by performing the following:
1. On the Start menu, right-click Computer and then click Properties.
2. Verify the system information in the System Properties window.
All procedures in this section are applicable for all the nodes, irrespective of entry level or high
capacity system. The steps to be performed may vary only based on the operating system.
- 31 -
4.2.5 Turning off the Windows automatic updates option

It is strongly recommended not to install any updates that are not qualified by Honeywell.
Honeywell qualifies Microsoft security updates/patches to ensure that the update or patch works
in conjunction with the Experion software. After qualifying any Microsoft patches/updates, the
customers are notified and the updates are made available through the Honeywell Process
Solutions website.
To turn off Window automatic updates option
1. Perform the following steps for Windows 10.

a. Navigate to Control Panel > Administrative Tools > Services.
b. Select and right-click Windows Update process.
c. Click Properties and select Disabled.
2. Under Recommended updates, clear the check box.
3. Click OK and close the Windows Update dialog box.
4.2.6 Setting the display resolution

To adjust the display resolution
1. Perform the following for Windows 10:

a. In the Windows Control Panel large or small icon view, click Display.
2. In the left pane, click Adjust resolution.
3. In the Resolution list, select the display resolution to a supported Experion resolution (for
example 1600 x 1200 and 1280 x 1024), and click OK.
4. In the Display Settings dialog box, click Keep changes.
The Display Settings dialog box appears only if you are adjusting the display setting
for the first time.
5. Close the Display window.
4.2.7 Configuring visual effects for increased performance

To customize the performance settings

a. In the Windows Control Panel large or small icon view, click System.
2. In the left pane, click Advanced System Settings.
The System Properties dialog box appears.
3. On the Advanced tab, click Settings under Performance.
The Performance Options dialog box appears.
4. On the Visual Effects tab, click Adjust for best performance.
6. Click OK to close the System Properties dialog box, and then close the System window.
- 32 -
4.2.8 Customizing the power options

To customize the power options

a. In the Windows Control Panel large or small icon view, click Power Options.
b. Under Preferred plans, click Balanced (recommended) and then click Change plan
settings.
2. In the Turn off the display list, click Never.
If Put the computer to sleep option appears, click Never.
3. Click Save Changes.
4. Close the Power Options window.
4.2.9 Disabling automatic disk defragmentation

To disable automatic disk defragmentation
1. Click Start > Windows system > This PC.

The This PC window appears.
2. Right-click Local Disc (C:) and click Properties.
The Local Disc (C:) Properties window appears.
4. Under Defragmentation, click Defragment Now.
The Disc Defragmenter dialog box appears.
5. Perform the following steps for Windows 10:
a. Click Configure schedule.
The Disc Defragmenter: Modify Schedule dialog box appears.
b. Click Select disks.
The Disc Defragmenter: Select Disks For Schedule dialog box appears.
c. Clear the Automatically defragment new disks checkbox and click OK.
d. Clear the Run on a Schedule (recommended) checkbox and click OK.
6. Click Close to close Disc Defragmenter window.
7. Click OK to close Local Disc (C:) Properties window.
8. Close the Computer window.
4.2.10 Turning off Windows Defender

If you have Windows Defender enabled in your system, perform the following steps to disable
Windows Defender for improved performance. Note that this procedure is applicable only for
Microsoft Windows 10 Enterprise 2016 LTSB (x64) nodes.
To turn off Windows Defender
1. Click Start > Windows system > Control Panel.

2. In the search box, type Windows Defender. Then, click Windows Defender.
The Windows Defender dialog box appears.
3. Click Tools, and then click Options.
- 33 -
4. Click Administrator, clear the Use this program check box, and then click Save. If you're
prompted for an administrator password or confirmation, type the password or provide
confirmation.
4.2.11 Disabling the fast user switching option

You must disable fast user switching in order to prevent multiple users from logging on to the
system simultaneously.
To disable the fast user switching option
1. Right-click Start > Run and type gpedit.msc.

The Local Group Policy Editor dialog box appears.
2. In the left side of the window, under Local Computer Policy expand Computer Configuration >
Administrative Templates > System and click Logon.
3. Double-click Hide entry points for Fast User Switching.
The Hide entry points for Fast User Switching dialog box appears.
4. Click Enabled, and then click OK.
5. Close the Local Group Policy Editor dialog box.
4.2.12 Disabling the antivirus services and applications

To ensure proper installation of the software, before you begin with Experion installation, disable
the antivirus services, if antivirus is already installed on the system.
To disable the antivirus services and applications
1. Right-click Start > Run and type msconfig.

2. In the Services tab, turn off all antivirus services and applications.
3. Enable and restart these services and applications after the installation is complete.
4.2.13 Completing the Experion node migration

Prerequisites
l After completing the OS installation, perform the following steps to continue Experion
migration.
l Ensure the virus protection software is disabled until Experion software installation is
completed.
l When prompted, be sure to enter the same mngr password that was used at the beginning of
the migration checklist.
- 34 -
To complete the Experion installation
1. To resume the migration, perform one of the following:
Option Description
If you are using an ESIS Select the mapped drive for the ESIS, or run
to perform migration the setup.exe .
If you are using the Insert the Experion installation media again in
installation media to the DVD drive and double-click the setup.exe.
perform the migration
2. In the Welcome to the Honeywell Experion HS R511 Installation Setup page, click Next.
The Migration/Clean Install Selection page appears.
3. Click Continue Migration and then click Next.
The Experion Migration Storage Node page appears.
4. In the Select Drive to connect Network Folder list, select the drive letter that is assigned to the
mapped EMSN shared folder.
5. In the Network Folder box, type the full path to the EMSN shared folder, in the format as per
the following options:
For Workgroup: \ \<Computer_name_of_EMSN_node>\<\EMSN_shared_folder>
and
For Domain: \ \< Domain Name >\<EMSN_shared_folder>
OR
\\192.168.0.1\EMSN.
6. Type the User Name and Password to connect to the shared folder.
If you have created a user account on the Windows domain for this purpose, type this user
account and password. Otherwise, type the user name and password of an account with
administrator privileges on the EMSN node.
network.
7. Click OK.
The wizard continues the migration and the Experion HS - Status Display page displays the
progress of migration.
Ignore the small user interface window that appears during server patch
installation. Ensure you do not click anywhere during this step.
8. Restart the system and log on as a user with Administrator privileges.
4.2.14 Re-enabling the antivirus software

After the migration, you need to re-enable and configure the antivirus software. Install the
antivirus software updates that you have downloaded and saved to a removable media, if any.
- 35 -
4.2.15 Defragmenting the hard disk

You can defragment the hard disk to improve the system performance.
Prerequisites
l Your computer must be “off control” before defragmenting the hard disk because the
performance of the computer is severely degraded during the defragmentation process.
l Check that no other applications (Experion Server, SQL Server, and so on.) are running
because the procedure involves restarting the computer.
l It is recommended that you add this task to your system's maintenance schedule, so that it is
performed during control shutdowns.
l You can upgrade the default fragmentation utility included with Windows to the full version.
Executive Software's Diskeeper includes a scheduler, and can defragment folders and page
files when a computer restarts. Defragmentation tasks affect the control system if they are set
to run automatically with the scheduler. Care must be taken when scheduling defragmentation
tasks. For more details, choose Start > Windows Administrative Tools > Defragment and
Optimize Drives, to refer to the Windows Help for Disk Defragmenter using the path.
To defragment the hard disk
1. Close all the running applications on the Windows desktop.

2. Launch the Experion PKS Server.
The Experion PKS Server dialog box is displayed.
3. To stop the services of the Experion server, in Full mode of the Start-Stop Experion PKS
Server window, select Database Unloaded.
4. Close all windows.
5. To stop MSSQLServer service, right-click Start> Run and type services.msc.
6. Click Continue.
7. Right-click SQL Server (MSSQLServer) and click Stop.
8. In the Stop Other Services dialog box, click Yes.
This stops the MSSQLServer services.
9. Close the Services window.
10. Launch This PC.
11. Right-click the hard disk drive to defragment and click Properties.
13. Click Defragment now.
14. Click Continue.
The Disk Defragmenter dialog box appears.
16. Click the volume name to defragment, which is usually C:, and then click OK.
Depending on the level of fragmentation and usage, the task may take some time to complete.
17. When the defragmentation is complete, click File > Exit to close the Disk Defragmenter
- 36 -
application.
18. Click OK to close the Properties dialog box.
19. Restart the computer and then log on to the system using an account with administrator
privileges.
4.2.16 Setting up time synchronization
Ensure that time zones in all the machines are same.
After completing the migration, you must synchronize the time between the node and the time
server.
You must log on to the migrated node with Windows System Administrator permission.
To run the NTPConfig utility
1. In Windows Explorer, navigate to C:\Program Files (x86)\Honeywell\Experion

PKS\Utilities\NTPSetup.
For custom installation path, navigate to <User selected path>\Honeywell\Experion
2. Right-click NTPConfg.exe and select Run as administrator.
The NTP Configuration dialog box is displayed.
For more information about setting up time synchronization, see the Experion PKS
Supplementary Installation Tasks Guide and Experion Server and Client Planning Guide.
3. To restore previous NTP configuration settings, click Yes.
The previous NTP configuration settings are restored.
4. If NTP configuration settings is not restored due to a file mismatch, then the "Couldnt restore
NTPConfig as system doesnt match to it" message is displayed.
5. Click OK.
If the NTP configuration settings are not restored, refer to the Supplementary Installation
Tasks Guide and Server and Client Planning Guide to reconfigure the NTP settings.
4.2.17 Updating custom setup files

If the system uses custom setup files (*.stn) in Station and you migrate the system to a new
release, you must update the path to these custom setup files so that they can be accessed when
the Station is launched.
To update the custom setup files
1. Open Station.
2. Click Station > Connection Properties.
3. Click the Toolbars tab.
4. Edit reference in Menu, toolbar and keyboard shortcuts: to display proper reference for
currently installed Experion release.
5. Click the Displays tab.
6. Edit search reference for the current release.
7. Click Save to save the changes and close the dialog box.
- 37 -
4.2.18 Updating display files

You must run the HMIWeb Bulk Display Migrator tool to the abstract folder or any folder containing
custom displays to migrate the displays after migrating the server and client nodes.
This section describes the use of the Bulk Display Migration tool to update/migrate custom display
(.htm) and shape (.sha) files to a new version. Once migrated, these files can be opened and
displayed accurately in station.
Prerequisites
The Autosave option must be disabled in HMIWeb Display Builder before you update your display
files.
To disable the Autosave option
1. Launch HMIWeb Display builder.

2. Click Tools > Options.
3. On the General tab, clear the Save AutoRecover info every minute check box.
4. Click OK.
5. Close HMIWeb Display Builder.
To update the display files
1. On the client node, back up all directories that contain the display files.
2. On the server, go to .
3. Right-click BulkDisplayMigrator.exe and click Run As Administrator.
4. Browse to the abstract folder that contains any custom display (.htm) files.
5. Click Go to run the bulk Display Migration tool on these folders to update the display files.
Be sure to enable the autosave option (if desired) after the display files have been
updated.
4.2.19 Restoring Windows network configuration settings

The Windows network configuration settings for the system may have not been saved or restored
during migration; you need to manually restore them after performing the migration process.
To restore the Windows network configuration settings
1. Obtain the printout or log of the configuration settings recorded before migration of the
server. For more information see the section, Recording Windows network configuration
settings.
2. Enter the configuration values in the appropriate Windows dialog boxes.
3. Re-map the paths to network drives previously configured on the system.
4.2.20 Updating the Quick Builder database

You must open Quick Builder and/or the Quick Builder project to update the database file.
- 38 -
l When you open Configuration Studio for the first time after migration,
o the Quick Builder migration wizard is launched to migrate the database
file.Do not click cancel during this migration process and allow the wizard
to complete its task.
l Ignore the message and click Convert.
See the Quick Builder Guide in https://www.honeywellprocess.com, for more information.
4.3 Migrating SCADA Clients

This chapter describes the tasks that you need to perform to complete the migration of SCADA
Clients.

4.3.2 Migrating an Experion HS SCADA Client

This section describes the procedure to migrate the current Experion HS system to Experion HS
R511.
Prerequisites

the migration.
If you are using ESIS to If installing from a network share:

perform the migration.
a. To connect to the ESIS repository, right-click Start > Run
and type \\<ESISServer IP>\<ShareName>. Press ENTER.
a. Type the <Domain Name>\Username and Password
if you belong to a domain and if you have share
permissions.
b. Type the <ESISServer IP>\Username and Password
if you belong to a workgroup and if you have share
permissions.
- 39 -

c. Clear the Remember Password check box.

\<ShareName>.
d. If prompted for UAC, click Allow. If you are prompted for the
Windows credentials.
a. Type the <Domain Name>\Username and
Password if you belong to a domain and if
b. Type the <ESISServer IP>\Username and Password
if you belong to a domain and if you have share
permissions l
c. Clear the Remember Password check box.
The Welcome To ESIS Tool page appears.

f. Click Next. The Welcome to the Honeywell Experion HS

If you are using Experion a. Insert the Experion installation media in the DVD drive.
installation media
The AutoPlay dialog box appears.
b. Under Install or run program, click Run Experion Media
Browser.
The Honeywell — Experion HS Installer — R511
page appears.
3. Click I accept the terms in the license agreement and then click Next.
The Setup type of Node to migrate page appears.
By default, the setup detects and lists the node that is being migrated.
4. Click Next.
The User and License Information page appears.
User and License Information page.) Browse the license file and click Next.
The Existing Packages Details page appears.
6. When migrating Experion HS R410 or HS R430 or HS R510 to HS R511, the Experion
Migration Storage Node and Advanced Migration Options page appears, with an option to re-
install the operating system. Perform one of the following options ONLY If you select the
option Operating System Re-installation.
- 40 -
l If you select Local EMSN option, then EMSN folder is stored in the software path.If local
EMSN is not required to be stored after migration, then you can select Select this to delete
EMSN once Migration Complete (this helps to manage the disk space) check box.
l If you select Remote/Network EMSN option, then perform the following:
from USB drive.
7. When migrating Experion HS R410/R430/R500/R510 to R511, the Experion Migration Storage

format:
and
Or
\\192.168.0.1\EMSN
network.
ESIS network.
8. Review the package details and then click Next.

The Installation Path(s) Selection page appears.
9. Click Next, if you are using the default installation path.
Or
change.
c. Click Next.
- 41 -
Under Experion PKS Install Option the Typical option is selected by default.
10. Click Next, if you do not want any Add-on Features to be installed.
Or
install.
b. Click Next.
11. Click Next.
12. Type the password(s) for the Windows MNGR, Expengr, Expoper, (Experion SQL Agent Account
is not applicable for SCADA Clients), and Experion SQL Agent Account and then click Next.
14. Click Install.
15. Install Microsoft Windows 10 Enterprise 2016 LTSB (x64) Operating System.
The system restarts after the Operating System installation.
customize the OS.
4.3.3 Guidelines for naming SCADA Client
CAUTION
You cannot change the computer name of the SCADA Client after the installation. However,
if you want to change the computer name, you must reinstall the client software.
All Experion client computers must have a unique fixed name and IP address. The following are
the basic restrictions when naming the client computers.
communication failure if you have redundant networks, because 0 and 1 suffixes are appended
to the computer names in host files to identify redundant links.)

- 42 -
l All procedures in this section are applicable for all the nodes, irrespective of entry level or high

Solutions website.



for the first time.
- 43 -




settings.


- 44 -



confirmation.




- 45 -

Option Description
network.
6. Click .

- 46 -
server.

5. Click OK.

settings.
4.3.17 Considerations after migrating a SCADA Client

l Ensure you have completed the following tasks after migrating from Experion HS
R400/R410/R430/R500/R510 to Experion HS R511.
l Recreated the custom local user security groups, local user accounts or local security policies, if
any.
l Required modifications are made to the custom displays that are migrated.
l Reapplied any customizations to the standard system displays.
- 47 -
l Reapplied any configurations that needs to be applied to the Operator accounts that were
linked to Windows user accounts.
l Reapplied any customizations to the standard station menus, if any.
l Reapplied any changes to the station configuration file (..\Windows\station.ini), if any.
l Reapplied the configuration settings of station setup file.
4.4 Migrating ServerA

Migrate ServerA only when you are satisfied with the operation of the migrated ServerB and
clients. Once ServerA is migrated, the two servers (ServerB and ServerA) are synchronized and
operate as redundant servers running on the new release software. The following sections
describes the tasks that you need to perform, and the order in which these tasks must be
performed.
4.4.1 Migrating remaining SCADA Clients

Migrate the remaining Stations before migrating ServerA.

4.4.3 Migrating an Experion server

This section describes the procedure to migrate an Experion system to Experion HS R511.
Prerequisites

the migration.
l If you have installed MasterLogic Server, ensure that you have disabled the MasterLogic
channel.
1. If a software protection key (dongle) is specified on the license certificate, insert this key on the
computers USB port.
The Found New Hardware dialog box appears.
2. Wait for the Operating System to complete the USB driver installation. Ignore any warning
dialog box that appears and proceed with the installation.

the migration.
- 48 -

Press ENTER.

\<ShareName>.

f. Click Next.


migrated.
- 49 -
Re- installation.
from USB drive.
9. Whenmigrating Experion HS R410/R430/R500/R510 to R511, the Experion Migration Storage

format:
\\192.168.0.1\EMSN
network.
ESIS network.
appears.
- 50 -
change.
c. Click Next.
Under Experion HS Install Option the Typical option is selected by default.
install.
b. Click Next.
13. Click Next.
14. Type the password(s) for the Windows MNGR, Expengr, Expoper, (Experion SQL Agent
Account is not applicable for SCADA Clients), and Experion SQL Agent Account and then click
Next.
16. Click Install.
customize the OS.
CAUTION
software.
- 51 -


the task.

Solutions website.

- 52 -


for the first time.




settings.
- 53 -





confirmation.


- 54 -




Prerequisites
l After completing the OS installation, perform the following steps to continue Experion
migration.
l Ensure the virus protection software is disabled until Experion software installation is
completed.
l When prompted, be sure to enter the same mngr password that was used at the beginning of
the migration checklist.
Option Description
5. In the Network Folder box, type the full path to the EMSN shared folder, in the format as per
the following options:
and
- 55 -
OR
\\192.168.0.1\EMSN.
network.
7. Click OK.
4.4.15 Proceeding with migration

In the procedures that follow, you need to install Honeywell software updates. Before you proceed
with these procedures, ensure that the installation of all software on ServerA is completed
successfully.
Do not proceed further with the migration if the installation of any software on ServerA
cannot be completed successfully.

4.4.17 Defragmenting the hard disk

You can defragment the hard disk to improve the system performance.
Prerequisites
l Your computer must be “off control” before defragmenting the hard disk because the
performance of the computer is severely degraded during the defragmentation process.
l Check that no other applications (Experion Server, SQL Server, and so on.) are running
because the procedure involves restarting the computer.
- 56 -
l It is recommended that you add this task to your system's maintenance schedule, so that it is
performed during control shutdowns.
l You can upgrade the default fragmentation utility included with Windows to the full version.
Executive Software's Diskeeper includes a scheduler, and can defragment folders and page
files when a computer restarts. Defragmentation tasks affect the control system if they are set
to run automatically with the scheduler. Care must be taken when scheduling defragmentation
tasks. For more details, choose Start > Windows Administrative Tools > Defragment and
Optimize Drives, to refer to the Windows Help for Disk Defragmenter using the path.
To defragment the hard disk
1. Close all the running applications on the Windows desktop.

2. Launch the Experion PKS Server.
The Experion PKS Server dialog box is displayed.
3. To stop the services of the Experion server, in Full mode of the Start-Stop Experion PKS
Server window, select Database Unloaded.
4. Close all windows.
5. To stop MSSQLServer service, right-click Start> Run and type services.msc.
6. Click Continue.
7. Right-click SQL Server (MSSQLServer) and click Stop.
8. In the Stop Other Services dialog box, click Yes.
This stops the MSSQLServer services.
9. Close the Services window.
10. Launch This PC.
11. Right-click the hard disk drive to defragment and click Properties.
14. Click Continue.
The Disk Defragmenter dialog box appears.
16. Click the volume name to defragment, which is usually C:, and then click OK.
Depending on the level of fragmentation and usage, the task may take some time to complete.
17. When the defragmentation is complete, click File > Exit to close the Disk Defragmenter
application.
18. Click OK to close the Properties dialog box.
19. Restart the computer and then log on to the system using an account with administrator
privileges.
- 57 -
server.

5. Click OK.
4.4.19 Updating custom setup files

If the system uses custom setup files (*.stn) in Station and you migrate the system to a new
release, you must update the path to these custom setup files so that they can be accessed when
the Station is launched.
To update the custom setup files
1. Open Station.
2. Click Station > Connection Properties.
3. Click the Toolbars tab.
4. Edit reference in Menu, toolbar and keyboard shortcuts: to display proper reference for
currently installed Experion release.
5. Click the Displays tab.
6. Edit search reference for the current release.
7. Click Save to save the changes and close the dialog box.

- 58 -
settings.
4.4.21 Checking the server status

On ServerA, ensure that you change the Experion server status to system running. It should now
show as backup.
4.4.22 Synchronizing the server databases

Synchronization is the process of copying the Experion server database from the primary server to
the backup server. When the server database on the backup server is identical to the database on
the primary server, the servers are said to be synchronized.
To synchronize the server databases
1. Launch Experion on the primary server and connect a Station to it.

3. Click View > System Status > Server Redundancy.
The Server Redundancy Status display opens.
4. Ensure that backup server is started.
5. On the Server Redundancy Status display on the primary server, the LEDs in the Link Status
group should change from red to green and indicate the following:
l Running
l Link n (LINK0n)
6. Click Synchronize to synchronize the servers.

The Experion database on the primary server is automatically copied to the backup server. The
time taken to synchronize depends on the size of your system. Synchronization in large
systems takes considerable time to complete, while the synchronization in small systems takes
only up to 10 minutes. The synchronization indicator (the first LED in the Backup Server
group) should change from red to green, and the text should change from Not synchronized
to Synchronized.
4.4.23 Enabling file replication

This section describes how to enable file replication for the migrated servers/clients. After
migration, you must restore the file replication settings so that file replication is enabled on the
nodes.
Prerequisites
You must manually and locally create the appropriate Windows network shares on each source
and destination computer before configuring custom replications on the Experion server, as
intended for use in each custom replication. For more information about configuring these
Windows network shares, see the ‘Configuring File Replication’ section in the Server and Client
Configuration Guide in .
- 59 -
To enable file replication
1. In Station, click Configure.

2. Select all Send check boxes on the file replication page.
3. Close Station.
4.4.24 Enabling file backup (flbkup.def)

This procedure describes how to enable file backups on the server by editing the file flbkup.def.
After migration you must enable any file backups in the flbkup.def file for the server.
To enable file backups after migration
1. On the server, open in a text editor such as Notepad.

2. Review the file and re-apply any backup requests disabled previously by placing an S at the
start of the line.
Refer to the flbkup.def file saved to the remote location before migration and add any
userdefined file backups from this file to the new filbkup.def file.
3. Save the file.
4. Close the text editor.
4.4.25 Adding servers to a system

Prerequisites
l At least one user has been defined on the server.

l You have a security level of ENGR or higher.
TIP
When adding a server, you can choose to import any areas, assets, and alarm groups
defined on that server into the Enterprise Model Database. Messages will prompt you on
your choices.
To add system servers to the Enterprise Model
1. In the Configuration Explorer in Configuration Studio, select the highest-level system node or
the Servers node.
2. Under Server Tasks, click the Add a server to this system task.
The SERVER Block Parameters dialog box appears.
3. In the Alias box, type a new unique tag name.
4. In the Description box, type a description of the server.
5. In the Abbreviation box, type an abbreviated name for the server.
6. If the server is a non-publishing server, select the Non-Publishing Server check box.
An example of a non-publishing server is eServer.
7. In the Node Name box, type the name of the server node. It can be the same as the server tag
name.
8. In the Network Type list, select the server network connection type (DUAL).
9. If the server is part of a redundant pair, select the Redundant? check box.
- 60 -
10. Click the Identification tab.

In the Block Comment boxes, type additional information about the server.
11. Click OK.
A message box appears prompting you to perform a load of the system configuration to
distribute the change to all of the servers.
12. Click Yes to continue loading system model into server’s database.
If you click No, the server is be added in the local server only and system model will not be
loaded into the server database. You can download the system model at a later time by clicking
Load server configuration on the DSA tool main page.
13. Repeat steps 1 to 12 for each server to be defined in the system model.
14. Type a valid user name and password. In the domain list, select <None>, and then click OK.
A migration of Asset Model/Alarm Groups dialog appears, prompting you to choose whether to
import the existing asset model/alarm groups on the newly created server into the Enterprise
Model Database.
Select the Overwrite if duplicate entity found in database check box to overwrite any existing
assets or alarm groups that are duplicates. Clear this check box if you want to be prompted
when a duplicate is found.
CAUTION
If you click Skip, any existing asset and alarm groups on the server will be
overwritten when a model is loaded to that server.
15. If you click Continue, the asset model and alarm groups from the server will be imported into
the EMDB.
Once completed, the newly added server now displays in the System Model tree in
Configuration Explorer.
If migration of an asset model or alarm groups fails, the server is not added to the system.
16. Repeat steps 1 to 15 for each server to be defined in the system model.
Results
After a server is added to the system, an icon representing the server displays in the Configuration
Explorer tree view. You are now able to configure settings on the server by clicking on a relevant
icon under the Server and completing the tasks displayed on the right of the window.
4.4.26 Enable EMDB replication

This section describes how to enable the Enterprise Model DataBase (EMDB) replication. Complete
these steps on Server B only.
To enable Experion EMDB replication
1. Launch Configuration Studio. The connect dialog appears.

2. Select a listed system and click Connect.
3. Log on to the primary server with engineer (Engr) security permissions.
4. To enable Experion EMDB replication:
a. From the Configuration Explorer tab, click the top level system name in the tree view.
b. From the System Level Tasks grouping, click Administer the system database.
5. Expand the DbAdmin item.
- 61 -
6. Log on with a user having manager access level.

7. Click Yes to continue.
8. Click OK to acknowledge the successful completion message dialog box.
9. Click Enable Replication.
10. Click Yes to continue.
11. Click OK to acknowledge the successful completion message dialog box.
12. Close the DB Admin application.
4.5 Migrating eServer

This chapter describes the tasks that you need to perform to complete the migration of eServers.
Only the migration from Experion HS R430 to R511 supports eServer

4.5.2 Migrating an Experion HS eServer

This section describes the procedure to migrate the current Experion HS system to Experion HS
R511.
Prerequisites

the migration.
- 62 -

the migration.
Press ENTER.

\<ShareName>.

f. Click Next.


2. In the Welcome to the Honeywell Experion HS R511.x Migration Setup Wizard page, click Next.
- 63 -
migrated.
Re- installation.
from USB drive.
7. When migrating Experion HS R410/R430/R500/R510 to R511, the Experion Migration Storage

format:
\\192.168.0.1\EMSN
network.
ESIS network.
appears.
- 64 -

change.
c. Click Next.
Under Experion PKS Install Option the Typical option is selected by default.
install.
b. Click Next.
11. Click Next.
12. Type the password(s) for the Windows MNGR, Expengr, Expoper, (Experion SQL Agent
Account is not applicable for SCADA Clients), and Experion SQL Agent Account and then click
Next.
14. Click Install.
customize the OS.
CAUTION
software.
- 65 -


the task.

Solutions website.

- 66 -


for the first time.




settings.
- 67 -







- 68 -

Option Description
network.
6. Click .

- 69 -
server.

5. Click OK.

settings.
4.6 Post migration tasks

Perform the following tasks to complete the migration of the nodes.
4.6.1 Converting non-redundant server to redundant server

If you want to convert a non-redundant to redundant server, refer to the section Support for
nonredundant to redundant server conversion, in the HS R511 Software Change Notice
document.
- 70 -
4.6.2 Changing the ServerA to primary

Ensure that you check the server states after completing migration.
To check the server states
1. Log on to Station running on ServerA.

3. Click View > System Status > Server Redundancy to open the Server Redundancy Status
display.
Option Description
If Server A is running as Ensure that the servers are synchronized.

primary and Server B as
backup
Server B is running as a. Ensure that the servers are

primary and Server A as synchronized.
backup b. In Station, click View > System Status
> Server Redundancy to open the
Server Redundancy Status display on
the primary Experion server. In the
Link Status group, the LEDs must
change from red to green and
indicate the following:
a. Backup server is green.
b. Link On (LINKOn) is OK.
c. Click Synchronize to synchronize the

servers.
d. Click Manual failover.
e. In the message zone, click Yes.
f. Ensure that ServerA is running as
primary and ServerB as backup.
g. After a few minutes, click
Synchronize, and then Yes to
resynchronize the databases. (If you
start synchronization immediately
after the failover, an error might
occur.)
- 71 -
4.6.3 Installing the Domain Controller package

To install the domain controller package
1. Insert the Experion installation media in the disk drive of the domain controller node.
2. Using Windows Explorer, browse to \Packages\dcsecurity folder and double-click .
3. Follow the instructions on-screen to proceed with the installation.
The InstallShield Wizard Completed dialog box appears.
4. Click Finish.
Perform steps 5 through 9 in the Experion nodes that are added to the domain.
5. Click Start > Windows System > Command Prompt, right-click Run as Administrator and click
Yes.
6. In the Command Prompt, type the following and press Enter.
The Command prompt displays the following path:
7. To link the domain groups, type LinkDomainGroups.vbs and press Enter.
8. Click OK in the confirmation dialog box and follow the instructions on-screen to complete the
configuration.
To remove the domain controller package
1. Right-click Control Panel on the domain controller node.

The Control Panel window appears.
2. Click Programs and Features.
3. Select Experion Security Policy in the list of installed programs and click Uninstall.
Honeywell-provided Group Policy Objects (GPOs) are over-written when the new
domain controller security package is installed. Therefore, any customizations
made to the GPOs must be recreated once the new domain security package is
installed. Users should create their own GPOs for settings they want to customize,
rather than modifying the Honeywell-provided GPOs.
4.6.4 Upgrading a Windows domain controller

If your Experion system is part of a Windows domain, and that Windows domain is running an
unsupported version of Windows operating system, you must upgrade the Windows operating
system on that domain controller.
For more information about the recommended operating system upgrade procedures, see
http://support.microsoft.com/default.aspx?scid=kb;en-us;325379.
4.6.5 Adding a node to a Windows domain

l The procedure to add a node to a Windows domain is applicable only if you want your computer
to be assigned to a Windows domain.
l Refer to the Experion Software Installation User's guide for more information on adding a node
to a Windows domain.
- 72 -
4.6.6 Re-establishing Engineering user groups

If the system has custom local user groups, custom local user accounts, and user-defined security
policies, ensure that local Windows groups and local user accounts are re-established on the
migrated Experion nodes. For more information, refer to the section Considerations for Local
Windows groups and local user accounts .
4.6.7 Importing the EDS files

You must import the EDS files, in case
l you have performed an Operating System change (install, reinstall, or product hardware
change) during migration
l you have RSLinx installed on your system.
For more information, visit http://www.software.rockwell.com.
4.6.8 Configuring ML Server Configurator Tool

For migration from Experion HS R430, you must reconfigure the IP address for PLC in the ML
Server Configurator Tool. In redundant-server scenario, this needs to be done on the Primary
Server.
4.6.9 Configuring MasterLogic Server (non-redundant server

Configuration
This section provides post-migration steps for configuring MasterLogic Server in non-redundant
server scenario. The steps are applicable when you migrate from Experion HS R400 and R410.
Perform the following steps on on the primary (non-redundant) server
1. Stop the File Replication. To do this refer to section Disabling file replication before migration
2. Disable all the MasterLogic channels from Experion station.
3. Stop MLGuardLauncher service (Perform this step as administrator user. Type services.msc
from Run menu to perform this step).
4. Now ensure that MLGuard.exe is removed from TaskManager.
5. Delete the XML and XSD files deployed by MasterLogic from the path
ProgramData\Honeywell\Experion PKS\Client\Abstract of Experion Server and Client
machines.
l MLAppSettings.xml
l MLAppSettings.xsd
l MLConfig.xml
l MLConfig.xsd
l MLGuard.xml
l MLMonitor.xml
l MLMonitor.xsd
l MLSOEConfig.xml
l MLSOEConfig.xsd
- 73 -
6. Copy the files from media path Packages\ServerClient\MLServer\Configuration Files and

paste to the folder path ProgramData\Honeywell\Experion PKS\Client\Abstract of Experion
Server and Client machines (MLGuard.xml is generated dynamically and hence it is excluded
from copy operation.).
7. Perform Step 5 and Step 6 on HS client machines.
8. Enable File Replication on the Primary server.
9. Start MLGuardLauncher service on the Primary server.
10. Configure the ML PLC configuration details such as Configure the IP address and Parent
Asset and PLC Configuration Details from ML Server Configurator Tool.
11. Save ML Configuration, and ensure there are no errors while saving.
12. Open the existing ML Quick Builder (qdb) file.
13. If the Quick Builder file migration dialog box appears, click Next to perform the migration.
14. Open Quick Builder and then select the ML channel.
15. In the ML Server Configurator Tool, select appropriate ML channel ID for each channel from
the drop-down list.
16. Click to download channel configuration to the server.
17. Open the Experion Station.
18. Choose View > System Status > Channels. The Channel Summary page appears.
19. Select the check box corresponding to the ML channel to enable it.
4.6.10 Configuring MasterLogic Server (redundant server

Configuration
This section provides post-migration steps for configuring MasterLogic Server in redundant server
scenario. The steps are applicable when you migrate from Experion HS R400 and R410.
Prerequisites
Server A and Server B are synchronized, with Server A machine kept as primary.
Perform the following steps on Server A
1. Stop the File Replication. To do this refer to section Disabling file replication before migration
2. Disable all the MasterLogic channels from Experion station.
3. Stop MLGuardLauncher service (Perform this step as administrator user. Type services.msc
from Run menu to perform this step).
4. Now ensure that MLGuard.exe is removed from TaskManager.
5. Delete the XML and XSD files deployed by MasterLogic from the path
ProgramData\Honeywell\Experion PKS\Client\Abstract of Experion Server and Client
machines.
l MLAppSettings.xml
l MLAppSettings.xsd
l MLConfig.xml
l MLConfig.xsd
l MLGuard.xml
- 74 -
l MLMonitor.xml
l MLMonitor.xsd
l MLSOEConfig.xml
l MLSOEConfig.xsd
6. Copy the files from media path Packages\ServerClient\MLServer\Configuration Files and

paste to the folder path ProgramData\Honeywell\Experion PKS\Client\Abstract of Experion
Server and Client machines (MLGuard.xml is generated dynamically and hence it is excluded
from copy operation.).
7. Perform Step 3 to Step 6 on the backup server as well.
8. Perform Step 5 and Step 6 on HS client machines.
9. Enable File Replication on the Primary server.
10. Start MLGuardLauncher service on the Primary server.
11. Configure the ML PLC configuration details such as Configure the IP address and Parent
Asset and PLC Configuration Details from ML Server Configurator Tool.
12. Save ML Configuration, and ensure there are no errors while saving.
13. Open the existing ML Quick Builder (qdb) file.
14. If the Quick Builder file migration dialog box appears, click Next to perform the migration.
15. Open Quick Builder and then select the ML channel.
16. In the ML Server Configurator Tool, select appropriate ML channel ID for each channel from
the drop-down list.
17. Click to download channel configuration to the server.
18. Open the Experion Station.
19. Choose View > System Status > Channels. The Channel Summary page appears.
20. Select the check box corresponding to the ML channel to enable it.
Perform the following steps on Server B
1. Start MLGuardLauncher service.

2. Perform Server switch over. The existing Backup will become Primary server.
3. Perform server synchronization between redundant servers.
4. Run the ML Server Configurator Tool from the new Primary server.
5. Save the ML configuration ensuring that the save happens without any errors.
4.6.11 Configuring Experion Client for ML Server

Incase of Experion HS clients, if the changes are not reflected, perform manual copy of below files
from Primary Server to client machine.
Copy the files MLAppSettings.xml, MLAppSettings.xsd, MLConfig.xml, MLConfig.xsd,
MLMonitor.xml, MLMonitor.xsd, MLSOEConfig.xml, and MLSOEConfig.xsd from the Primary
server to the Experion HS Client.
The destination path for the files is ProgramData\Honeywell\Experion PKS\Client\Abstract on
both the server and the client.
4.7 Troubleshooting Migration

Restarting the migration application Correcting the computer name displayed in Configuration
Studio
- 75 -
4.7.1 Restarting the migration application

If you find that migration application must be stopped to correct an error, the migration application
can be restarted and resumed from the last operation. In most cases, nothing is lost and migration
resumes from the point where it stopped. To restart the migration application, eject the installation
media from the disk drive and then re-insert it. The migration application should launch and
resume from the last operation completed.
If you encounter errors while using the migration tool, acknowledge the errors. After you
acknowledge the error, the system restarts. You need to restart the migration tool to
continue with the migration.
4.7.2 Correcting the computer name displayed in Configuration

When performing a migration with Operating System reinstallation, ensure that the computer
name is not changed after reinstalling the Operating System. If you have changed the computer
name, perform the following steps to correct the computer name displayed in Configuration
Studio.
To correct the computer name
1. Launch Diagnostic Tools and then click Command Prompt.

2. Change the directory to .
3. Type the following command at the Experion Command Prompt:
EMBCKBUILDER c:\Out.xml –SYSTEM
Wait for the command to complete.
4. In Notepad, open the file, C:\Out.xml.
5. Search and replace the old computer name with the new computer name to update the
following entries:
<BlockName> ComputerName </BlockName><EntityName> ComputerName
</EntityName><ParamName> NODENAME </ParamName><ParamValue> “ComputerName”
</ParamValue>
Note: If this node is a part of the redundant pair, then the new computer name is its
base name without the suffix A or B.
6. Check the server redundancy setting:

<ParamName> REDUNDANT </ParamName><ParamValue> OFF </ParamValue>
This setting must be OFF for a non-redundant server and ON for a redundant server.
7. Save the file and close Notepad.
8. Type the following command in the Experion Command Prompt:
EMBUILDER C:\Out.xml –FORCE
Wait for the command to complete.
- 76 -
Notices
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of
Honeywell International, Inc.
ControlEdge™ is a trademark of Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.
Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is
a business unit of Honeywell International, Inc.
Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit of
Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation
in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark owner,
with no intention of trademark infringement.
Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The
third party materials may be subject to licenses, notices, restrictions and obligations imposed by
the licensor. The licenses, notices, restrictions and obligations, if any, may be found in the
materials accompanying the product, in the documents or files accompanying such third party
materials, in a file named third_party_licenses on the media containing the product, or at
http://www.honeywell.com/ps/thirdpartylicenses.
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website
at: http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
hpsdocs@honeywell.com
Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact your local Honeywell
Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance Center
(TAC).
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness
that can be exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and
services.
To report a potential security vulnerability against any Honeywell product, please follow the
instructions at:
https://www.honeywell.com/product-security
Support
- 77 -
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To
find your local CCC visit the website, https://www.honeywellprocess.com/en-US/contact-
us/customer-support-contacts/Pages/default.aspx.
Training classes
Honeywell holds technical training classes that are taught by process control systems experts. For
more information about these classes, contact your Honeywell representative, or see
http://www.automationcollege.com.
- 78 -

Migration Users Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Migration Users Guide

Uploaded by

Copyright:

Available Formats

EXPERION HS

Migration User's Guide

2.2 Migration applications and tools 9

2.3 Migration planning 11

Chapter 3 - GETTING STARTED WITH MIGRATION 17

3.3 Time synchronization during migration 18

3.4 HMIWeb Display Builder and HMIWeb custom displays 18

3.5 Restoring Excel data exchange 19

4.1.15 Setting up an ESIS repository 26

4.2 Migrating ServerB or non-redundant server 27

4.3 Migrating SCADA Clients 39

4.3.16 Restoring Windows network configuration settings 47

4.4 Migrating ServerA 48

4.5 Migrating eServer 62

4.5.9 Disabling automatic disk defragmentation 68

4.6 Post migration tasks 70

4.7 Troubleshooting Migration 75

1 ABOUT THIS GUIDE

1.1 Special Terms

Experion A location used to store the data (databases, system configuration,

Installation A software application that installs the Experion system software

Migration A software wizard application which migrates Experion system

Supervisory SCADA is an Experion application for process control. It is designed

ServerA and The standardized names of the redundant servers. ServerA

System The migration of Experion control system from one release to a

1.2 Revision History

Version Date Description

A August 2019 Initial release of the document.

2 BEFORE YOU BEGIN

2.1 Experion system migration

2.1.1 About Experion HS

2.2 Migration applications and tools

2.2.1 About Experion Migration Storage Node (EMSN)

Special handling for EMSN hosted in a domain environment

d. Restart migration by starting Setup.exe on the installation media or clicking

2.2.2 Experion Software Installation Server (ESIS)

2.2.3 Migration Application

2.3 Migration planning

2.3.1 Choosing the migration method

l Installation using Experion installation media

Installation method Steps to be performed

Using Experion Install Experion HS R511 using the installation

Only one node

Using ESIS on a network 1. Set up the ESIS repository.

Using ESIS on a USB pen 1. Set up the ESIS repository.

2.3.2 Develop a migration plan

2.3.3 Develop a migration timetable

Migration time estimates

Migration Task Estimated Time

Overall planning 1–2 days

Preparation and backups 8 hours

OS reinstallation 4 to 6 hours (each path)

ServerA and ServerB migration 3–4 hours each

2.3.4 Review hardware upgrades

2.3.5 Review software requirements

2.3.6 EMSN space requirements

SCADA Client 8 GB + Options 9

Formula: Total Space - (Base size + Options) = Estimated EMSN space

2.3.7 Considerations for Local Windows groups and local user

2.3.8 Migrating other Honeywell products and applications

Safety Builder is not recommended on Experion server/station nodes.

o Check the time synchronization topology used for Safety Manager.

2.3.9 Migrating non-Experion third-party applications

The following are some examples of third-party software applications: