Sie sind auf Seite 1von 56
Experion Vista R301/HS R301 to HS R400 Migration User's Guide Release 400 January, 2011

Experion

Vista R301/HS R301 to HS R400 Migration User's Guide

Release 400

January, 2011

Document Release Issue Date   400 4.0 January, 2011 Disclaimer This document contains Honeywell

Document

Release

Issue

Date

 

400

4.0

January, 2011

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 2011 - Honeywell International Sárl.

Contents

About this guide

7

Before you begin

9

Experion system migration

10

Migration applications and tools

11

About Experion Migration Storage Node (EMSN)

11

Migration tool

13

Migration Application

13

Migration planning

14

Develop a migration plan

14

Develop a migration timetable

14

Review hardware upgrades

15

Review software requirements

15

EMSN space requirements

15

Considerations for Local Windows groups and local user accounts

16

Migrating other Honeywell products and applications

17

Migrating non-Experion third-party applications

18

Getting started with migration

19

Migration considerations

20

Considerations for migrating from Experion Vista R301/HS R301 to Experion HS R400 20

Getting the latest software and documentation updates

22

Time synchronization during migration

23

Planning time topology during migration

23

Time check on system before you start migration

23

HMIWeb Display Builder and HMIWeb custom displays

24

Migrating Display Builder displays

24

Migrating HMIWeb custom displays

24

Restoring Excel data exchange

26

Considerations for canceling the migration

27

Performing the migration

29

Complete the pre-migration tasks

30

Creating a disk image of the hard drive

30

Verifying the Windows mngr account passwords

30

Verifying the latest Experion software updates

31

30 Verifying the Windows mngr account passwords 30 Verifying the latest Experion software updates 31 3

3

CONTENTS

Verifying the communication network

31

Installing the migration tool on the server

31

Calculating the disk space

32

Recording Windows network configuration settings

33

Acknowledging all system alarms

33

Disabling file replication before migration

33

Creating a shared folder on the EMSN

34

Running the migration tool on the server

35

Checking the synchronization status

36

Disabling antivirus software

36

Migrating ServerB/non-redundant server

38

Close Windows applications

38

Migrating Experion Vista R301/HS R301 to Experion HS R400

38

Reinstalling antivirus software

38

Updating custom setup files

39

Updating display files

39

Restore Windows network configuration settings

40

Restoring and migrating the server database

40

Updating the Quick Builder database

42

Migrating Flex Stations

43

Close Windows applications

43

Migrating Experion Vista R301/HS R301 to Experion HS R400

43

Reinstalling antivirus software

43

Restore Windows network configuration settings

44

Considerations after migrating a Flex station

44

Migrating ServerA

45

Migrating remaining Flex Stations

45

Close Windows applications

45

Migrating Experion Vista R301/HS R301 to Experion HS R400

45

Proceeding with migration

46

Reinstalling antivirus software

46

Setting up time synchronization

46

Updating custom setup files

46

Restore Windows network configuration settings

47

Checking the server status

47

Synchronizing the server databases

47

Enabling file replication

48

Enabling file backup (flbkup.def)

48

Building the assets and alarm groups

49

Post migration tasks

50

Changing the ServerA to primary

50

Installing the Domain Controller package

51

CONTENTS

Upgrading a Windows domain controller

52

Adding a node to a Windows domain

52

Re-establishing Engineering user groups

52

Importing the EDS files

52

Configuring MLServer Configuration Tool

53

Troubleshooting Migration

54

Restarting the migration application

54

Correcting the computer name displayed in Configuration Studio

54

Restarting the migration application 54 Correcting the computer name displayed in Configuration Studio 54 5

5

CONTENTS

About this guide

The Experion HS R400 migration guide assists you in understanding, planning, and migrating your current Experion HS system. Specifically, this guide provides information and guidance for migrating Experion Vista R301 and Experion HS R301 to Experion HS R400.

Special terms

The following are the terms defined in the document, which are unique to the subject presented in this guide.

Term

Description

Base release

The release version of Experion that is currently in use before the migration.

Experion Migration Storage Node (EMSN)

A

location used to store the data (databases, system

configuration, operating system preferences, and so on) when migrating an Experion platform. For setting up an

 

EMSN, a node in the same network, other than the one which

is being migrated, is used.

Installation application

A software application that installs the Experion system

software with minimal user interaction.

Migration Application

A

software wizard application which migrates Experion

system components to latest release system software.

Supervisory Control and Data Acquisition (SCADA)

SCADA is an Experion application for process control. It is designed to interface with serial devices (RS232 and RS485) such as PLCs.

ServerA and ServerB

The standardized names of the redundant servers. ServerA functions as the primary server and ServerB functions as the backup server.

System migration

The migration of Experion control system from one release

to

a latest release.

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

7

ABOUT THIS GUIDE

Term

Description

Migration Tool

A tool that is used to save the server data before migration.

Before you begin

This section provides an introduction to the migration of Experion systems, the migration scenarios and migration plan.

Related topics

“Experion system migration” on page 10 “Migration applications and tools” on page 11 “Migration planning” on page 14

system migration” on page 10 “Migration applications and tools” on page 11 “Migration planning” on page

9

BEFORE YOU BEGIN

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

About Experion HS R400 migration

Experion HS R400 system software must be installed only on systems installed with Windows 7 Professional Edition (32-bit) 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.

Supported migration paths

Experion HS R400 supports the following migration:

• Experion Vista R301 to Experion HS R400

• Experion HS R301 to Experion HS R400

• Experion HS R310 to Experion HS R400

• Experion HS R311 to Experion HS R400

to Experion HS R400 • Experion HS R311 to Experion HS R400 Attention OS reinstallation is

Attention OS reinstallation is mandatory for all the above mentioned migration paths.

BEFORE YOU BEGIN

Migration applications and tools

Various software applications and utilities have been developed specifically to help streamline the system migration process by:

• Detecting system conditions prior to a migration that may cause problems or faults once the migration begins.

• Detecting inconsistencies in system databases and system components that may cause errors during migration.

• Automating many of the tasks that are performed during a migration.

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:

• All systems/releases that undergo a hardware platform upgrade during migration.

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

several options that users can perform to manually work around this problem, with option 3 being

11

BEFORE YOU BEGIN

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.

 

• Add this account to the Share and File Permissions on the EMSN.

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

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

 

• Add this account to the Share and File Permissions on the EMSN.

• Enter the account name as <<EMSN Host IP Address>>\Account. For example: 192.168.0.1\MigAccount

.

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

d. Restart migration by starting Setup.exe on the installation media or clicking Install/Migrate link on the Installer page.

Migration tool

BEFORE YOU BEGIN

Experion Vista R301 and HS R301 migration is performed using the migration tool. The migration tool saves the server data before migration. The server data includes the Quick Builder Project, custom displays, groups, trends, recipes, reports, history archives, and other configuration data. The tool is available at Server-Client \Server_Migration_Tool folder in the installation media.

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.

system software is installed. It also allows for hardware and Operating System upgrades during the migration

13

BEFORE YOU BEGIN

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. A plan will also provide information on what to expect in the migration process and will 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.

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.

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)

BEFORE YOU BEGIN

Migration Task

Estimated Time

ServerA and ServerB migration

3–4 hours each

Migrate each Flex Station

1–2 hours each

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, Flex Stations 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.

new hardware components before starting the node migration. Attention If you have redundant servers, the node

Attention If you have redundant servers, the node hardware for both ServerA and ServerB must be identical.

Review software requirements

Review and address the software requirements for the migration. Experion HS R400 system software must be installed only on systems installed with Windows 7 Professional Edition (32-bit) English version. For more information on computer software specifications, refer to Software Installation User's Guide.

EMSN space requirements

You can use the following information as a guidance to calculate the EMSN space requirements.

• To determine Total space (T), right-click Drive C: and click Properties. The used space is displayed in the dialog box that appears.

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

• 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. Space on the EMSN that was used for

for other node migrations, you must consider the additional disk space needed. Space on the EMSN

15

BEFORE YOU BEGIN

prior system migrations can be recovered. 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.

Table 1: EMSN estimated space

Node Type

Total space

Base size

Options (O)

Estimated EMSN

(T)

(B)

Space needed

T - (B +O) = EMSN

Server

 

8 GB

+ Options

8.7

Flex Station

 

9.6 GB

3 GB

12.6

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

 

Options include third-party software and applications installed on the node, so on.

Considerations for Local Windows groups and local user accounts

for Local Windows groups and local user accounts CAUTION If a new Operating System is installed

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 R400 Experion standard local groups include the following:

• Product Administrators (which replaces Honeywell Administrators from prior releases)

• Local Engineers

• Local Supervisors

• Local Operators

BEFORE YOU BEGIN

• Local Ack View Only Users

• Local View Only Users

• Local Servers (which in R400 limits the account for use by services/servers only)

The Experion standard local account includes the following:

• LocalComServer

• mngr

account includes the following: • LocalComServer • mngr Attention Both the Experion standard local accounts are

Attention Both the Experion standard local accounts are used only by services/servers. They are not allowed to be used interactively.

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.

• Customized system components and display files must be manually saved since they are not migrated and restored in the new release. For example:

– Point detail displays

– Customized Faceplates and Customized displays

– Custom Station menu configurations (*.stb files)

– *.css files

• Digital Video Manager (DVM) — Compatibility with Experion — DVM. See the Digital Video Manager User Guide for details to migrate DVM client and host components.

• Process History Database (PHD)

• Safety Manager - If you have Experion systems with Safety Manager, consider the following before migration:

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

refer to the Safety Manager Software Reference or the Release Notes of Safety Manager installed in

17

BEFORE YOU BEGIN

BEFORE YOU BEGIN Attention Safety Builder is not recommended on Experion server/station nodes. – Check the

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

– Check the time synchronization topology used for Safety Manager.

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

– During the migration of Experion servers or stations, Safety Manager and/or Channel link status might report communication failures.

– After migrating your station to the new release, you must reinstall Safety Builder on your station and restore the Safety Manager application(s).

– If Safety Manager continues to report communication failures after completing the migration, download the diagnostics on the Safety Station and reset the Safety Manager.

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

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:

• Are the third-party applications currently operating with the Experion system compatible with the new release Operating System requirements?

• Are third-party applications interoperable with the new Experion platform software release?

• Are there upgrades available for the third-party software?

• Should compatibility testing be performed offline to ensure that the applications will operate properly?

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

• Antivirus applications are not migrated as part of Experion migration.

• Oil/Movement/Blending, Business applications.

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:

• You have read the Experion HS Release Notes 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.

• You have read the migration planning information for information related to your system and the planned migration.

Related topics

“Migration considerations” on page 20 “Getting the latest software and documentation updates” on page 22 “Time synchronization during migration” on page 23 “HMIWeb Display Builder and HMIWeb custom displays” on page 24 “Restoring Excel data exchange” on page 26 “Considerations for canceling the migration” on page 27

on page 24 “Restoring Excel data exchange” on page 26 “Considerations for canceling the migration” on

19

GETTING STARTED WITH MIGRATION

Migration considerations

Attention The following sections contain important information that you should consider before you begin a migration. 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.

Considerations for migrating from Experion Vista R301/HS R301 to Experion HS

R400

Attention The following are some considerations when you are migrating from Experion Vista/ HS R301 to The following are some considerations when you are migrating from Experion Vista/ HS R301 to Experion HS R400.

Item

Description

Microsoft Office

The Microsoft Office applications might require upgrade during the migration. Refer to the Experion HS R400 SIUG for details of the supported versions of Microsoft Office.

Faceplate displays

Experion Vista R301 and Experion HS R301 included special faceplates that are used to hide the unused parameters on the point detail displays. To use these special faceplates, the Quick Builder point configuration includes a special entry in the Point Detail Display field that is “sysdtlana_pv”. If these definitions are used, they must be changed to new R400 Simplified SCADA display filenames after the migration.

MasterLogic

The MasterLogic interface is now included as standard interface in the Experion HS R400 installation.

controller interface

Enterprise Model

Experion HS R400 has a simplified version of the Enterprise Model; the Asset configuration is preserved during the migration.

Windows user

Any custom local user security groups, local user accounts or local security policies must be recreated after migration.

security

configuration

 

GETTING STARTED WITH MIGRATION

Item

Description

Event history

The recent online events are retained during the migration, but the SQL event history are lost. If you want to generate the Alarm and Event reports, save this information prior to the migration.

Custom displays

The custom displays are migrated, but modifications might be required after the migration due to functional changes.

System displays

If you have customized the standard system displays, the changes must be reapplied after the migration.

Operator security

If the Operator accounts are linked to Windows user accounts, these accounts will not exist after the migration and hence the configuration must be reapplied after the migration.

Station menus

If you have customized the standard station menus, these changes must be reapplied after the migration.

Station

If you have changed the station.ini file, the changes must be reapplied after the migration.

configuration file

\Windows

 

\station.ini

Station setup file \Station\Default.stn

The new default Station setup file is configured as “static Station 1”. The Station 1 configuration settings must be reapplied after the migration.

System acronyms

If you have customized the standard system acronyms, these customizations must be reapplied after the migration.

Scan periods

If special scan periods are used, it must be reapplied after the migration.

Allen Bradley

If RSLinx OEM is used, the RSLinx activation code must be moved to removable media before starting the migration and reinstalled after the migration.

RSLinx

Quick Builder

When opening an old project file with the new version of Quick Builder, you will be prompted to migrate the project file to the new format.

projects

Localization

If the Experion HS displays have been localized, the localization settings must be reapplied after the migration.

If the Experion HS displays have been localized, the localization settings must be reapplied after the

21

GETTING STARTED WITH MIGRATION

Getting the latest software and documentation updates

Before installing Experion HS, check the Honeywell Field Solutions Sales & Distribution web site for software and documentation updates.

To download the latest software and documentation updates

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.

GETTING STARTED WITH MIGRATION

Time synchronization during migration

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.

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.

server and client nodes to ensure that they are the same. Attention Do not change time

Attention 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

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.

the time (if necessary) after the software upgrade, but before re- establishing server redundancy, and all

23

GETTING STARTED WITH MIGRATION

HMIWeb Display Builder and HMIWeb custom displays

MIGRATION HMIWeb Display Builder and HMIWeb custom displays Attention Systems that use customized (user-defined)

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

• Point detail displays

• Faceplates

• *.css files

• *.htm files

Migrating Display Builder displays

Custom Displays built using Display Builder (.dsp files) can be made available on an upgraded Experion Station provided that:

• The displays are custom displays

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

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

GETTING STARTED WITH MIGRATION

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

you want to update the HMIWeb displays in bulk, you can use the Bulk Display Migration

25

GETTING STARTED WITH MIGRATION

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.

GETTING STARTED WITH MIGRATION

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.

base release. First you must cancel or abort any applications that are running; then load the

27

GETTING STARTED WITH MIGRATION

Performing the migration

Performing the migration Attention • When migrating redundant server systems, you must migrate ServerB first. After

Attention

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

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

• All the nodes (servers and stations) must be migrated to the target release before the system is restarted and nodes start communicating again.

• When migrating non-redundant server systems, perform all the migration tasks on the non-redundant server.

Related topics

“Complete the pre-migration tasks” on page 30 “Migrating ServerB/non-redundant server” on page 38 “Migrating Flex Stations” on page 43 This chapter describes the tasks that you need to perform to complete the migration of Flex Stations.

“Migrating ServerA” on page 45 “Post migration tasks” on page 50 “Troubleshooting Migration” on page 54

“Migrating ServerA” on page 45 “Post migration tasks” on page 50 “Troubleshooting Migration” on page 54

29

PERFORMING THE MIGRATION

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.

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 PDF Collection.

Verifying the Windows mngr 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 will no longer be able to connect to the server because they continue to use the old password. This means that the password must be the same:

• On all Experion computers

• For all services that run under the mngr account

Considerations

• 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\Honeywell\Experion PKS\Utilities\pwdutil and double-click PWDUtil.exe. The User Account Control dialog box appears.

3 Click Allow.

4 Select mngr.

PERFORMING THE MIGRATION

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.

back and change password . 7 Click Done . 8 Click OK . Attention If the

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

Verifying the latest Experion software updates

Ensure that the software updates downloaded from the Honeywell Field Solutions Sales & Distribution web site are of the latest version. You must enable or reinstall the Experion software updates after migrating to the new release.

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.

Installing the migration tool on the server

This procedure uses the Experion migration tool to save the server data so that it can be restored during the system migration. The server data includes the Quick Builder Project, custom displays, groups, trends, recipes, reports, history archives and other configuration data.

Considerations

• This procedure must be performed on the existing Experion server.

• The server data must be saved in a computer on the same network as the server. If this is not possible, the data must be saved to the local hard disk before copying it to a removable media.

• This procedure must be performed using an account with administrator rights.

copying it to a removable media. • This procedure must be performed using an account with

31

PERFORMING THE MIGRATION

Prerequisites

• Experion HS R400 installation media

• Install DotNet 3.5 SP1 before proceeding with installation of the migration tool.

1. In the Experion Application Software DVD, navigate to \Packages \Microsoft\DotNet3.5 directory.

2. Double-click dotnetfx35SP1.exe.

3. Follow the instructions on-screen to complete the installation.

4. Restart the computer.

To install the migration tool

1 Using Windows Explorer navigate to the CD\DVD drive\ Server-Client

\Server_Migration_Tool directory.

2 Double-click the Server Migration Tool.msi file.

3 Follow the instructions on-screen to complete the installation.

4 Ensure you clear Launch the program check box before you click Finish.

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” on page 34.

To calculate the disk space

1 Using Windows Explorer, navigate to the history archive directory which is

normally C:\Program Files\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.

PERFORMING THE MIGRATION

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.

Acknowledging all system alarms

Prior to migration, acknowledge all the system alarms. Resolve any alarms that are critical to your system.

To view the system alarms

1 Open 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 migration.

Disabling file replication before migration

You must disable file replication on the node to be migrated.

To disable file replication

1 In Station, choose Configure > Configuration Tools.

2 On the display page, click File Replication.

3 Change to the mngr security level.

> Configuration Tools . 2 On the display page, click File Replication . 3 Change to

33

PERFORMING THE MIGRATION

4 On the file replication page, clear all the Send check boxes.

the file replication page, clear all the Send check boxes. Attention While reinstalling the OS, review

Attention 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:

• The share name and path used for each custom file replication on each Experion server involved in the migration.

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

5 Close Station.

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:

• Connect as the Administrator of the node designated as the EMSN.

OR

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

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.

PERFORMING THE MIGRATION

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.

Running the migration tool on the server

Perform the following procedure to copy the files to the Experion Migration Storage Node (EMSN).

Prerequisites

All the Honeywell applications must be closed before stopping the Experion server.

To run the migration tool

1 Open Windows Explorer and choose Tools > Disconnect Network Drive. If there is a network connection listed as drive Z: then select this drive and click OK to disconnect the network drive. This procedure maps the shared directory as drive Z: the backup process will fail if there is another directory already mapped as drive Z.

2 Choose Start > Programs > Accessories > Command Prompt.

3 Type hscserver /unload /y and press Enter.

4 Choose Start > Settings > Control Panel > Administrative Tools > Services to display the Services window.

5 In the list of services, right-click Experion PKS Browser Orchestration service.

6 Click Stop and then Yes to stop both the browser services.

7 Close the Services window.

8 Go to the desktop and double-click the Server Migration Tool icon.

9 Click Next in the Experion PKS Migration Tool dialog box. The dialog box displays the current sever release.

10 Click Next.

11 Enter the destination computer name in the EMSN Machine Name box and the shared directory name (Backup) in the EMSN Share box and click Next. The Migration Tool Phase 1 dialog box displays the size of the data to be backed up to the shared directory.

Next . The Migration Tool Phase 1 dialog box displays the size of the data to

35

PERFORMING THE MIGRATION

12 Compare this size with the disk space requirement determined previously and if there is sufficient disk space click Next.

13 On the Connect to EMSN login dialog box, enter the user name and password for an account that has administrator rights on the destination computer, and then click OK. The migration tool tests the connection to the shared directory and start the file copy operations.

to the shared directory and start the file copy operations. Attention There is no indication of

Attention There is no indication of the progress during the file copying. Wait for the final dialog box to be displayed and then click Exit. If this step fails, click Exit and check the permissions on the shared (Backup) directory. The permissions must be set to allow Everybody Full Control. Repeat this procedure from Step 8.

14 Using Windows Explorer navigate to C:\Program Files\Honeywell\Experion PKS\Migrate\Plug-in\HSCServer directory.

15 Double-click the servermigrationtool_log.txt log file.

If the log file contains error or failure messages, repeat this procedure from Step

8.

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.

2 Change to the mngr security level.

3 Choose 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.

Disabling antivirus software

You must disable any virus protection software and stop all virus protection related services on the system you are migrating.

PERFORMING THE MIGRATION

To disable antivirus software

1 Choose Start > Programs > McAfee > VirusScan Console. The User Account Control dialog box appears.

2 Click Continue.

3 In the VirusScan Console window, choose 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 Choose Start > Run.

8 Type services.msc and click OK. The User Account Control dialog box appears.

9 Click Continue. The Services window appears.

10 To disable the antivirus software, perform the following steps:

a Right-click McAfee Framework Service and click Properties. The Properties dialog box appears.

b In the General tab, click Stop.

c In the Startup type box, select Disabled.

d Click Apply, and then click OK. Repeat the steps 9a through 9d for McAfee McShield and McAfee Task Manager Services.

Apply , and then click OK . Repeat the steps 9a through 9d for McAfee McShield

37

PERFORMING THE MIGRATION

Migrating ServerB/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.

Close Windows applications

You must close all Windows applications before starting migration.

Migrating Experion Vista R301/HS R301 to Experion HS R400

To migrate a node operating with Experion Vista R301/HS R301 to Experion HS R400 you must:

1. Install Windows 7 Professional Edition (32-bit) English version using the appropriate OS media.

Refer to the OEM documentation for more information on installing the OS.

2. Configure the Operating System. Refer to the section Preparing for installation

in the Experion HS R400 Software Installation User's Guide.

3. Clean install Experion HS R400 using Experion Application Software DVD. For installing Experion Experion HS R400, refer to the section Installing Experion HS Server/Installing Experion HS client software in the Experion HS R400

Software Installation User's Guide.

Experion HS R400 Software Installation User's Guide . Attention After completing Experion HS R400 installation,

Attention After completing Experion HS R400 installation, return to this section to proceed with the migration.

Reinstalling antivirus software

After the migration, you need to reinstall, and configure the antivirus software. Install the antivirus software updates that you have downloaded and saved to a removable media, if any.

Updating custom setup files

PERFORMING THE MIGRATION

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

Updating display files

Migrate the custom display htm 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 On the node, choose Start > All Programs > Honeywell Experion PKS > Server > HMIWeb Display builder .

2 Choose Tools > Options.

3 On the General tab, clear the Save AutoRecover info every minute check box.

4 Click OK.

5 Close HMIWeb Display Builder.

General tab, clear the Save AutoRecover info every minute check box. 4 Click OK . 5

39

PERFORMING THE MIGRATION

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 C:\Program Files\Honeywell\Experion PKS\Client \HMIWeb Display Builder.

3 Right—click BulkDisplayMigrator.exe and click Run As Administrator.

4 Browse to the abstract folder(C:\ProgramData\Honeywell\Experion PKS

\Client\Abstract) 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.

Migration tool on these folders to update the display files. Attention Be sure to enable the

Attention Be sure to enable the autosave option (if desired) after the display files have been updated.

Restore 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. Refer to the section, “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.

Restoring and migrating the server database

This procedure restores the server data that was saved to the Experion Migration Storage Node (EMSN). The server data includes the custom displays, groups, trends, recipes, reports, history archives and other configuration data.

Prerequisites

• This procedure must be performed after installing the Experion HS R400 server software.

PERFORMING THE MIGRATION

PERFORMING THE MIGRATION Attention Considerations • If the new system has redundant servers, perform this procedure

Attention

Considerations

• If the new system has redundant servers, perform this procedure on the primary server.

• This procedure must be performed using an account with administrator rights.

Moving the files from the EMSN to the new server

• Copy the shared folder (Backup) in the EMSN to the C:\ drive on the new server.

Restore and migrate the server database

1 Using Windows Explorer navigate to the C:\Backup\ServerData folder.

2 Choose Start > All Programs > Honeywell Experion PKS > Server > Diagnostic Tools > Experion Command Prompt > .

3 Type the hscserver /load /y at the command prompt and press Enter.

4 Type the following command at the command prompt using the full path name from Step 1 and the \data enclosed in quotes. For example: “C:\Backup\Honeywell Experion PKS\Migrate\ServerName \HSCServer\ServerData\data” sysbld -restore “path\data” -y

5 Review the output in the command window for errors. If a file open error is displayed, the restore failed as the data file was not found at the specified path. For example, file DATA open error 0209 at Backup open error 0209 path DATA EVFARC initialize error 0209 The file or directory was not found.

Copying the restored files to the new directories

1 Using Windows Explorer copy the files from

C:\Backup\

\HSCServer

\CustomDisplays1 to C:\ProgramData\Honeywell\Experion PKS\Client \Abstract.

Do not copy the MasterLogic controller displays (prefixed ML). These displays are included in the MLDP interface installation.

2 Using Windows Explorer copy the files from C:\Backup\

\HSCServer

\Archive0 to C:\ProgramData\Honeywell\Experion PKS\Server\Data.

3 Using Windows Explorer copy the files from C:\Backup\

\HSCServer

\Report to C:\ProgramData\Honeywell\Experion PKS\Server\Data\Report.

Select Skip for files and directories that already exist.

4 Using Windows Explorer copy the .TSV files from C:\Backup\

\HSCServer

\ServerData\OPCIntegrator to C:\ProgramData\Honeywell\Experion PKS \Server\Data\OPCIntegrator.

C S e r v e r \ServerData\OPCIntegrator to C:\ProgramData\Honeywell\Experion PKS \Server\Data\OPCIntegrator . 41

41

PERFORMING THE MIGRATION

5 Using Windows Explorer copy the files from C:\Backup\

\HSCServer

\ServerData\qdb to C:\ProgramData\Honeywell\Experion PKS\Server\Data \qdb.

6 Using Windows Explorer copy the files from C:\Backup\

\HSCServer

\ServerData\scripts to C:\ProgramData\Honeywell\Experion PKS\Server \Data\scripts.

7 Create ExceptionHistory folder in the C:\ProgramData\Honeywell\Experion PKS \Server\data directory.

Updating the Quick Builder database

You must open Quick Builder and/or the Quick Builder project to update the database file.

the Quick Builder project to update the database file. Attention • When you open Configuration Studio

Attention

• When you open Configuration Studio for the first time after migration,

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

See the Quick Builder Guide in Knowledge Builder for more information.

PERFORMING THE MIGRATION

Migrating Flex Stations

This chapter describes the tasks that you need to perform to complete the migration of Flex Stations.

Close Windows applications

You must close all Windows applications before starting migration.

Migrating Experion Vista R301/HS R301 to Experion HS R400

To migrate a node operating with Experion Vista R301/HS R301 to Experion HS R400 you must:

1. Install Windows 7 Professional Edition (32-bit) English version using the appropriate OS media.

Refer to the OEM documentation for more information on installing the OS.

2. Configure the Operating System. Refer to the section Preparing for installation

in the Experion HS R400 Software Installation User's Guide.

3. Clean install Experion HS R400 using Experion Application Software DVD. For installing Experion Experion HS R400, refer to the section Installing Experion HS Server/Installing Experion HS client software in the Experion HS R400

Software Installation User's Guide.

Experion HS R400 Software Installation User's Guide . Attention After completing Experion HS R400 installation,

Attention After completing Experion HS R400 installation, return to this section to proceed with the migration.

Reinstalling antivirus software

After the migration, you need to reinstall, and configure the antivirus software. Install the antivirus software updates that you have downloaded and saved to a removable media, if any.

software. Install the antivirus software updates that you have downloaded and saved to a removable media,

43

PERFORMING THE MIGRATION

Restore 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. Refer to the section, “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.

Considerations after migrating a Flex station

If the migrate Flex Station task cannot be completed successfully, do not proceed further with the migration. Ensure you have completed the following tasks after migrating from Experion Vista R301/HS R301 to Experion HS R400.

• Recreated the custom local user security groups, local user accounts or local security policies, if any.

• Required modifications are made to the custom displays that are migrated.

• Reapplied any customizations to the standard system displays.

• Reapplied any configurations that needs to be applied to the Operator accounts that were linked to Windows user accounts.

• Reapplied any customizations to the standard station menus, if any.

• Reapplied any changes to the station configuration file ( \Windows\station.ini), if any.

• Reapplied the configuration settings of station setup file.

PERFORMING THE MIGRATION

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.

Migrating remaining Flex Stations

Migrate the remaining Flex Stations before migrating ServerA. While migrating the remaining Flex Stations, ensure that you have moved all the points, including all SCADA points, to ServerB.

Close Windows applications

You must close all Windows applications before starting migration.

Migrating Experion Vista R301/HS R301 to Experion HS R400

To migrate a node operating with Experion Vista R301/HS R301 to Experion HS R400 you must:

1. Install Windows 7 Professional Edition (32-bit) English version using the appropriate OS media.

Refer to the OEM documentation for more information on installing the OS.

2. Configure the Operating System. Refer to the section Preparing for installation

in the Experion HS R400 Software Installation User's Guide.

3. Clean install Experion HS R400 using Experion Application Software DVD. For installing Experion Experion HS R400, refer to the section Installing Experion HS Server/Installing Experion HS client software in the Experion HS R400

Software Installation User's Guide.

Experion HS R400 Software Installation User's Guide . Attention After completing Experion HS R400 installation,

Attention After completing Experion HS R400 installation, return to this section to proceed with the migration.

. Attention After completing Experion HS R400 installation, return to this section to proceed with the

45

PERFORMING THE MIGRATION

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.

of all software on ServerA is completed successfully. Attention Do not proceed further with the migration

Attention Do not proceed further with the migration if the installation of any software on ServerA cannot be completed successfully.

Reinstalling antivirus software

After the migration, you need to reinstall, and configure the antivirus software. Install the antivirus software updates that you have downloaded and saved to a removable media, if any.

Setting up time synchronization

After completing the migration, you need to synchronize the time between the node and the time server. For more information on setting up time synchronization, see the Software Installation User's Guide.

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

PERFORMING THE MIGRATION

Restore 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. Refer to the section, “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.

Checking the server status

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

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 Start Experion on the primary server and connect a Station to it.

2 Change to the mngr security level.

3 Choose 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:

Running

Link n (LINK0n)

6 Click Synchronize to synchronize the servers.

green and indicate the following: • Running • Link n (LINK0n) 6 Click Synchronize to synchronize

47

PERFORMING THE MIGRATION

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.

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 Knowledge Builder.

To enable file replication

1 In Station, choose Configure > Configuration Tools.

2 On the display page, under the General heading, click File Replication.

3 Select all Send check boxes on the file replication page.

Select all Send check boxes on the file replication page. Tip Receive is no longer available

Tip Receive is no longer available at this point.

4 Close Station.

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 C:\ProgramData\Honeywell\Experion PKS\server\Data

\flbkup.def in a text editor such as Notepad.

PERFORMING THE MIGRATION

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 user-defined file backups from this file to the new filbkup.def file.

3 Save the file.

4 Close the text editor.

Building the assets and alarm groups

Experion HS has a simplified version of the Enterprise Model; the Asset configuration is preserved during the migration. This topic describes how to load the assets and alarm group models located in the Enterprise Model to servers. Note that performing this procedure loads the entire system enterprise model, (system model, asset model, and alarm groups) to servers.

To build the assets and alarm groups

1 Open Configuration Studio.

2 In the Configuration Explorer tab of Configuration Studio, click Enterprise Model.

3 In the tasks window, click Build Assets or Build Alarm Groups. The Assets Builder/Alarm Group Builder dialog box appears.

4 In the asset model tree, right-click on the parent for the new asset and click Add Asset. or

In the alarm group model tree, right-click on the parent for the new alarm group and click Add Alarm Group.

The Enterprise Assets or Alarm Groups dialog box appears.

5 Type the name of the asset or alarm group and click OK. The new asset/alarm group appears as a child of the parent asset/alarm group.

6 Configure the properties of the asset/alarm group.

group appears as a child of the parent asset/alarm group. 6 Configure the properties of the

49

PERFORMING THE MIGRATION

Post migration tasks

Perform the following tasks to complete the migration of the nodes.

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.

2 Change to the mngr security level.

3 Choose View > System Status > Server Redundancy to open the Server Redundancy Status display.

Option

Description

If ServerA is running as primary and ServerB as backup

Ensure that the servers are synchronized.

If ServerB is running as primary and ServerA as backup

1. Ensure that the servers are synchronized.

2. From Station, choose 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:

• Backup server is green.

• Link On (LINKOn) is OK.

3. Click Synchronize to synchronize the servers.

4. Click Manual failover.

5. In the message zone, click Yes.

6. Ensure that ServerA is running as primary and ServerB as backup.

Option

PERFORMING THE MIGRATION

Description

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

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 Honeywell security model – domain controller.msi.

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 Choose Start > All Programs > Accessories and right-click Command Prompt and click Run as an Administrator.

6 In the UAC, click Continue.

7 In the Command Prompt, type the following and press Enter.

cd C:\Program Files\Honeywell\WkStaSecurity

The Command prompt displays the following path:

C:\Program Files\Honeywell\WkStaSecurity

8 To link the domain groups, type LinkDomainGroups.vbs and press Enter.

9 Click OK in the confirmation dialog box and follow the instructions on-screen to complete the configuration.

To remove the domain controller package

1 Choose Start > Control Panel on the domain controller node. The Control Panel appears.

2 Click Programs and Features.

3 Select Experion Security Policy in the list of installed programs and click Uninstall.

Programs and Features . 3 Select Experion Security Policy in the list of installed programs and

51

PERFORMING THE MIGRATION

PERFORMING THE MIGRATION Attention Honeywell-provided Group Policy Objects (GPOs) are over-written when the new domain

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

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, seehttp://support.microsoft.com/default.aspx?scid=kb;en-us;325379.

Adding a node to a Windows domain

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

• Refer to the Experion Software Installation User's guide for more information on adding a node to a Windows domain.

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” on page 16 .

Importing the EDS files

You must import the EDS files, in case

• you have performed an Operating System change (install, reinstall, or product hardware change) during migration

• you have RSLinx installed on your system.

For more information, visit “http://www.software.rockwell.com”.

Configuring MLServer Configuration Tool

PERFORMING THE MIGRATION

If you are using MasterLogic channel, you must reconfigure the IP address for MLPLC in the MLServer Configuration Tool. This facilitates communication between MLPLC and the Experion server. The IP address must be configured on the primary server.

communication between MLPLC and the Experion server. The IP address must be configured on the primary

53

PERFORMING THE MIGRATION

Troubleshooting Migration

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.

should launch and resume from the last operation completed. Attention If you encounter errors while using

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

Correcting the computer name displayed in Configuration Studio

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 Choose Start > All Programs > Honeywell Experion PKS > Server > Diagnostic Tools > Experion Command Prompt.

2 Change the directory to C:\Program Files\Honeywell\Experion PKS\Server \Run.

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>

PERFORMING THE MIGRATION

PERFORMING THE MIGRATION Attention Note: If this node is a part of the redundant pair, then

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

the following command in the Experion Command Prompt : EMBUILDER C:\Out.xml –FORCE Wait for the command

55

PERFORMING THE MIGRATION