Enterprise Buildings Integrator
Installation Guide
Notice
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 2010 – Honeywell International Sàrl Honeywell trademarks
Honeywell Enterprise Buildings Integrator™ is a trademark of Honeywell International Inc, and SafeBrowse® is a U.S. registered trademark 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.
Support and other contacts
For technical assistance, call your nearest Honeywell office. Training classes
Honeywell holds technical training classes on Enterprise Buildings Integrator. These classes are taught by experts in the field of building control systems. For more information about these classes, contact your Honeywell representative.
Related documentation
For a complete list of publications and documents for Enterprise Buildings Integrator, see the Enterprise Buildings Integrator Overview.
Contents
1 Starting a successful EBI installation
13
Using the checklists. . . 14
System Design form . . . 15
Filling in the System Design form . . . 19
Description of Windows Server properties . . . 20
Description of TCP/IP properties . . . 21
Description of EBI Server properties . . . 24
Description of Modem connection properties . . . 25
About computer names . . . 26
About Windows accounts, operator IDs and EBI security levels . . . 27
About User Account Control. . . 29
Recommendations for Cardholder Management and Global Schedules in a DSA system. 30 Related EBI installation documents . . . 31
2 New installation checklists
33
Installation checklist: Non-redundant EBI server . . . 34Installation checklist: Redundant EBI servers. . . 36
Installation checklist: Station on a client computer. . . 40
Installation checklist: Client applications (other than Station) on a client computer . . . 42
Installation checklist: Remote point server . . . 44
Installation checklist: Networked XLNET node . . . 45
Installation checklist: Mobile Station server . . . 46
3 Upgrade checklists
49
Upgrade checklist: From EBI R400 SP1 on existing non-redundant server. . . 51Upgrade checklist: From EBI R400 SP1 on existing redundant servers. . . 55
Upgrade checklist: From EBI R400 SP1 on new non-redundant server and/or operating system . 61 Upgrade checklist: From EBI R400 SP1 on new redundant servers. . . 66
Upgrade checklist: From EBI R400 SP1 on an existing DSA system . . . 73
Upgrade checklist: From EBI R310 SP3 or later on existing non-redundant server . . . 75
Upgrade checklist: From EBI R310 SP3 or later on existing redundant servers . . . 80
Upgrade checklist: From EBI R310 SP3 or later on new non-redundant server . . . 87
Upgrade checklist: From EBI R310 SP3 or later on existing non-redundant server with new operating system . . . 93
Upgrade checklist: From EBI R310 SP3 or later on existing redundant servers with new operating
system . . . 107
Upgrade checklist: From EBI R310 SP3 or later on an existing DSA system . . . .115
Upgrade checklist: Station and displays . . . .117
Upgrade checklist: EBI client applications other than Station . . . .119
Upgrade checklist: Remote point server on existing computer. . . 121
Upgrade checklist: Remote point server on new computer and/or operating system . . . 123
4 Preparing the server
125
Defining the basic server properties . . . 126Defining the basic server properties in Windows Server 2008 . . . 127
Defining the basic server properties in Windows 7. . . 129
Defining the basic server properties in Windows Server 2003 . . . 131
Defining the basic server properties in Windows XP Professional. . . 134
Starting the Licensing Service. . . 136
Configuring the display (monitor). . . 137
Updating the server’s hosts file . . . 139
Installing Microsoft Excel. . . 142
Installing Microsoft Excel . . . 143
Installing the Microsoft Office Service Pack . . . 144
Configuring Microsoft Excel. . . 145
Protecting your EBI system against viruses . . . 146
Configuring the Windows Firewall . . . 147
5 Installing specialized hardware on the server
149
Installing a Network Interface card . . . 150Changing the Network Adapter settings . . . 150
Installing the Microsoft Loopback adapter . . . 151
Installing a serial adapter. . . 153
Installing a Stallion EasyConnection. . . 154
Installing a Digiboard . . . 156
Installing a LonWorks Network Interface . . . 157
6 Installing EBI on the server
159
Installing the EBI components on the server . . . 160Recommended disk partitioning . . . 160
Typical installation of the EBI components on the server. . . 161
Custom installation of the EBI components on the server . . . 163
Registering EBI servers. . . 166
Registering a non-redundant EBI server . . . 167
Registering redundant EBI servers . . . 169
Re-registering EBI server software . . . 171
CONTENTS
Configuring RSLinx drivers for an Ethernet network. . . 174
7 Installing and setting up associated applications
175
Setting up Microsoft Excel reports . . . 176Setting up Microsoft Excel Data Exchange. . . 177
Installing the EBI ODBC client. . . 178
Configuring a printer . . . 180
Creating an account for third-party OPC clients . . . 181
Configuring DCOM security. . . 182
Setting up a file server. . . 184
Setting up a shared folder . . . 185
Assigning a drive letter on a client computer to a shared folder . . . 186
8 Connecting printers and modems to the server
187
Installing a printer . . . 188Installing a printer driver . . . 189
Installing a printer driver for a local printer . . . 189
Installing a printer driver for a local shared printer. . . 190
Installing a printer driver for a shared network printer (with a suitable share name) . . 190
Installing a printer driver for a shared network printer (whose existing share name is unsuitable) . . . 192
Setting up the Print Job Spool folder. . . 194
Creating a Guest account. . . 195
Installing a modem . . . 196
Setting up the modem . . . 198
Modem connection . . . 198
Setting up the modem connection . . . 199
Configuring RAS . . . 200
Adding a Remote User on Windows Server 2008. . . 202
Adding a Remote User on Windows 7 . . . 202
Adding a Remote User on Windows Server 2003. . . 203
Adding a Remote User on Windows XP . . . 203
9 Supplementary tasks
205
Starting and stopping the EBI server. . . 206Stopping EBI services . . . 208
Displaying the Computer Management Services Console . . . 209
Stopping RSLinx . . . 210
Making changes after installation . . . 211
Changing the EBI license . . . 212
Changing the default History Archive folders. . . 213
Adding new or reinstalling EBI components . . . 214
Configuring the database setup . . . 215
Adjusting history retention . . . 216
Determining how many points you can configure . . . 219
Synchronizing the date and time . . . 220
Moving the RSLinx activation file . . . 222
10 Preparing a client computer
225
Updating the computer’s hosts file . . . 22611 Installing applications on a client computer
229
Installing EBI client applications . . . 230Typical installation of the EBI client applications . . . 230
Custom installation of the EBI client applications . . . 232
Adding Windows accounts to the Honeywell Station Users group. . . 234
Configuring a Station for server redundancy . . . 235
Setting up a multi-monitor Station . . . 237
Setting up Display Builder for multiple monitors . . . 238
Installing Networked XLNET Node software. . . 239
Setting up a third-party OPC client or server . . . 241
Creating a Windows mngr account for a third-party OPC client . . . 242
Controlling Read/Write access . . . 243
Creating a Windows mngr account for a third-party OPC server . . . 244
Specifying the server name in Data Access applications . . . 246
12 Setting up Integrated PhotoID hardware
247
Setting up a FlashPoint card . . . 248Installing the FlashPoint card . . . 249
Installing the FlashPoint MCI driver. . . 250
Configuring station.ini. . . 252
Configuring Integrated PhotoID to use the card . . . 254
Setting up a TWAIN image capture device . . . 255
Setting up signature capture pads . . . 256
13 Installing point server components on a remote server
257
14 Installing Mobile Station Server
259
Installing Terminal Services . . . 260Activating Terminal Services Licensing server. . . 262
Installing the Client Access Licenses . . . 265
Configuring Mobile Station server to access an existing Terminal Services Licensing server. 267 Limiting the number of connections to the Mobile Station server . . . 268
Creating Windows accounts for Mobile Station server users . . . 269
Configuring Mobile Access for Station users . . . 270
15 Installing a terminal server
271
Configuring an EasyServer II . . . 272CONTENTS
Connecting the configuration computer to EasyServer II . . . 275
Specifying the IP address of the EasyServer II . . . 276
Setting up a Telnet session to configure EasyServer II . . . 278
Specifying a router/gateway address (EasyServer II) . . . 280
Configuring the Ethernet interface (EasyServer II). . . 281
Configuring TCP port numbers (EasyServer II) . . . 282
Specifying the EasyServer II’s inactivity timeout . . . 283
Configuring the EasyServer II’s TCP keepalive timer . . . 284
Configuring a serial port (EasyServer II) . . . 285
EasyServer II port parameters . . . 285
Adding the EasyServer II IP address to the server’s hosts file . . . 288
Connecting controllers to an EasyServer II. . . 289
Changing the EasyServer II’s TCP/IP address . . . 291
Configuring a Lantronix . . . 292
Resetting the Lantronix . . . 293
Specifying the Lantronix’s IP address. . . 294
Setting up a Telnet session to configure a Lantronix . . . 296
Specifying a gateway address (Lantronix) . . . 297
Configuring TCP port numbers (Lantronix) . . . 298
Setting the Lantronix’s inactivity timeout . . . 299
Setting the Lantronix’s TCP keepalive timer . . . 300
Configuring a serial port (Lantronix) . . . 301
Adding the Lantronix IP address to the server’s hosts file . . . 303
Connecting controllers to a Lantronix. . . 304
Changing the Lantronix’s TCP/IP address . . . 306
Configuring a Cisco 2610 Router . . . 307
Preliminary Cisco 2610 Router setup . . . 308
Configuring the Cisco 2610 router’s Ethernet properties . . . 309
Specifying the Cisco 2610 router’s gateway address . . . 311
Specifying the Cisco 2610 router’s IP address . . . 312
Setting the Cisco 2610 router’s TCP keepalive timer . . . 313
Configuring serial ports (Cisco 2610 router). . . 314
Setting up a serial port (Cisco 2610 router). . . 315
Setting a serial port’s TCP keepalive timer (Cisco 2610 router). . . 316
Configuring the communications characteristics (Cisco 2610 router) . . . 317
Setting a serial port’s inactivity timer (Cisco 2610 router) . . . 319
Setup example for typical controller’s serial port 3 (Cisco 2610 router) . . . 320
Adding the Cisco 2610 router IP address to the server’s hosts file. . . 321
Connecting controllers to a Cisco 2610 router . . . 322
Advanced Cisco 2610 router commands. . . 324
Configuring a Systech . . . 325
Specifying the Systech’s IP address . . . 327
Logging into the Systech terminal server using Internet Explorer . . . 328
Changing the Systech’s TCP/IP address . . . 329
Configuring the router/gateway address (Systech) . . . 330
Configuring serial ports (Systech). . . 332
Adding the Systech’s IP address to the server’s hosts file . . . 333
Upgrading the Systech terminal server to current release. . . 334
Configuring the Systech terminal server for use with fast failover. . . 335
Connecting controllers to a Systech . . . 336
16 Installing controllers
339
17 Planning for an upgrade
341
Planning for an upgrade to EBI on an existing server. . . 342Planning for an upgrade to EBI on a new server. . . 347
Planning for an upgrade to EBI on a DSA system . . . 352
Planning for an upgrade to components installed from the auxiliary DVD . . . 359
Uninstalling and reinstalling Honeywell DVM components . . . 360
18 Upgrade tasks
361
Upgrading EBI on an existing server . . . 362Typical upgrade of the EBI components on an existing server. . . 362
Custom upgrade of the EBI components on an existing server . . . 364
Upgrading EBI on a new server . . . 367
Typical upgrade of the EBI components on a new server . . . 367
Custom upgrade of the EBI components on a new server . . . 369
Upgrading remote point servers on a new computer. . . 373
Upgrading remote point servers on an existing computer. . . 375
Upgrading EBI components on a client computer . . . 377
Typical upgrade of the EBI components on a client computer . . . 377
Custom upgrade of the EBI components on a client computer. . . 378
Setting the EBI services to manual startup . . . 380
PreUpgrade.vbs . . . 381
Setting the EBI services to automatic startup . . . 382
Copying the existing EBI databases to the new computer . . . 383
Disabling SQL Server replication . . . 385
Migrating HMIWeb displays and shapes . . . 386
Migrating Station-level scripts . . . 387
Attaching scripts to the new Station . . . 387
Migrating Quick Builder projects . . . 388
Migrating from an area-based system to a location-based system . . . 389
Renaming areas . . . 389
Uploading locations after the upgrade. . . 390
Renaming points with illegal names (point IDs). . . 391
fixpointname.exe . . . 394
About downloading fire points . . . 395
CONTENTS
Checking the visibility of user fields on CMS displays . . . 398
Creating card layouts to replace DSP card layouts . . . 399
Migrating HTM card layouts. . . 400
Upgrade tasks for a LonWorks Point Server . . . 401
Checking the name of the LNS database. . . 402
Backing up the LonWorks point server data on the existing point server computer. . . 403
Restoring LonWorks point server data . . . 404
Reapplying customizations to the XML templates . . . 406
Upgrade tasks for EXCEL 5000 Direct. . . 407
Backing up EXCEL 5000 Direct data before upgrading. . . 408
Restoring EXCEL 5000 Direct data . . . 409
About Global Schedules migration . . . 410
Migrating Global Schedules . . . 412
Updating the server alias . . . 414
19 Removing EBI
415
Uninstalling EBI . . . 416Removing the EBI server components . . . 417
Removing Microsoft SQL Server . . . 418
Removing EBI client applications. . . 419
20 Troubleshooting
421
EBI server installation problems . . . 422EBI server startup problems . . . 423
Windows-related problems . . . 424
DNS performance in a redundant server system . . . 425
Network interface cards (network adapters) . . . 426
Modems . . . 427
Terminal server problems . . . 428
21 Tuning server performance
431
Introduction . . . 432Tuning the Windows Kernel . . . 433
Disk management . . . 434
Fixing File System errors . . . 435
Defragmenting the file system. . . 437
Memory and swapfile/pagefile . . . 439
Adjusting swapfile/pagefile size . . . 441
Networking . . . 442
Network optimization . . . 443
Management of traffic . . . 444
Adjusting bindings and disabling protocols on standard networks . . . 445
Benefits from other Network Services . . . 447
Other settings. . . 449
Video settings . . . 449
System usage . . . 449
Topology-related settings . . . 450
Monitoring the system and assessing the need for hardware upgrades. . . 451
Configuring the Performance Monitor . . . 452
1
Starting a successful EBI
installation
This guide describes how to install a new EBI system or upgrade your existing EBI system.
Preliminary tasks
Complete the tasks in the following order. Caution
This guide uses checklists and a System Design Form to guide you through installation/ upgrade tasks. You must use them to avoid installation problems.
Task Go to: Done?
Learn how to use the checklists. page 14 Fill in the System Design form. page 15 Read the Known Issues Bulletin and Software Release
Bulletin for any last-minute instructions.
EBI DVD If you are:
• Installing a new EBI system, select the top-level checklists that meet your installation requirements.
page 33
• Upgrading an existing EBI system, select the top-level checklists that meet your upgrade requirements.
Using the checklists
This guide makes extensive use of checklists to guide you through installation/ upgrade tasks. You must use the checklists (and the System Design form) to avoid installation problems.
Tips
• Make a photocopy of each checklist that is applicable to your system. • Check that you have satisfied the Prerequisites before you start the first task. • Complete the tasks in order shown, unless specified otherwise.
• When you complete each task, return to the checklist and mark the task as complete in the Done column. It is also a good idea to include the name of the person who completed the task and the date and time the task was completed to assist in diagnosing any problems that may occur.
Related topics
SYSTEM DESIGN FORM
System Design form
You use this form to record details that will be needed many times during installation/upgrade tasks. You must therefore fill in this form before starting the first task.
For instructions on how to fill in this form, see “Filling in the System Design form” on page 19.
Attention Make a photocopy of this form for each server (or redundant server pair). Windows Server properties
For a description of each property, see “Description of Windows Server properties” on page 20.
TCP/IP properties
For a description of each property, see “Description of TCP/IP properties” on page 21. (If you have a redundant system, you must also fill in the next section for the backup server.)
Primary Server Backup Server (if applicable) Computer Name
Administrator Password Number of Concurrent Connections
(Only applicable to Windows Server 2008 and Windows Server 2003.) Value General Tab IP Address Subnet Mask Default Gateway Preferred DNS Server Alternate DNS Server IP Settings Tab Interface Metric
DNS Tab
DNS server addresses, in order of use
Append primary and connection specific DNS suffixes
Append parent suffixes of the primary DNS suffix Append these DNS suffixes (in order)
DNS suffix for this connection
Register this connection’s addresses in DNS Use this connection’s DNS suffix in DNS registration WINS Tab
Defaults. If not specify:
Options Tab
Defaults. If not specify:
Domain/Workgroup Domain. Specify Administrator password:
Workgroup. Specify name:
Network Adapter Settings Address: Value
SYSTEM DESIGN FORM
TCP/IP properties for Backup server
Only applicable if you have redundant servers. For a description of each property, see “Description of TCP/IP properties” on page 21.
Value General Tab IP Address Subnet Mask Default Gateway Preferred DNS Server Alternate DNS Server IP Settings Tab Interface Metric DNS Tab DNS server addresses, in order of use
Append primary and connection specific DNS suffixes
Append parent suffixes of the primary DNS suffix Append these DNS suffixes (in order) DNS suffix for this connection
Register this connection’s addresses in DNS Use this connection’s DNS suffix in DNS registration WINS Tab
Defaults. If not specify:
Options Tab
EBI server properties
For a description of each property, see “Description of EBI Server properties” on page 24.
Modem connection properties
Only applicable if one or more client computers are connected to the server via a modem. For a description of each property, see “Description of Modem
connection properties” on page 25.
Domain/Workgroup Domain. Specify Administrator password:
Workgroup. Specify name:
Network Adapter Settings Address: Value Value Windows Account Passwords Mngr: Engr:
(Note that this account is not longer installed but may exist from an upgraded R310 server).
Oper:
(Note that this account is no longer installed but may exist from an upgraded R310 server).
OPC Account Username:
Password:
Fast History collection interval
Username Password
FILLING IN THE SYSTEM DESIGN FORM
Filling in the System Design form
This section describes the purpose of every property in the System Design form. If you have a DSA system, you must fill in a separate form for each non-redundant server or non-redundant server pair.
If you have Cardholder Management, Global Schedules and a DSA system, consider the networking issues. See “Recommendations for Cardholder Management in a DSA system”.
The System Design form will be required if you ever upgrade or reconfigure your system, so remember to keep it (and the EBI license) in a safe place for future reference.
Related topics
“System Design form” on page 15
“Recommendations for Cardholder Management and Global Schedules in a DSA system” on page 30
“Description of Windows Server properties” on page 20 “Description of TCP/IP properties” on page 21
“Description of EBI Server properties” on page 24 “Description of Modem connection properties” on page 25
Description of Windows Server properties
Property Description
Computer Name The name of the server computer (the computer name). For more information about computer names, see “About computer names” on page 26.
Administrator password The password for the Windows Administrator account. Note: This password is case-sensitive.
You need this password whenever you perform
administrative tasks on the server. If you have a DSA system, we recommend that the password for the Administrator account is the same on all EBI servers.
For an explanation of Windows accounts, see “About Windows accounts, operator IDs and EBI security levels” on page 27.
Number of
Concurrent Connections
Only applicable to Windows Server 2008 and Windows Server 2003.
The number of Windows client access licenses (CALs) required. You need to enter the correct number of CALs for your system configuration.
Note: If you require more than five CALs, you need to
purchase and maintain the required number of additional CALs.
For non-redundant systems:
Number of Stations Number of CALs required
5 5
6 to 10 10
11 to 15 15
16 to 20 20
For redundant systems:
Number of Stations Number of CALs required
8 5
9 to 13 10
14 to 18 15
FILLING IN THE SYSTEM DESIGN FORM
Description of TCP/IP properties
The tabs and properties in the following table correspond with the Microsoft TCP/IP Properties dialog box.
Tab Property Description
General IP Address If you have an existing network, this will be provided by your network administrator. Otherwise, specify something like 192.186.0.x, where x is a unique number for each network adapter (and usually each host) on the network. This number can be between 1 and 254.
Subnet Mask If you have an existing network, this will be provided by your network administrator. Otherwise, specify 255.255.255.0.
Default Gateway If you have an existing network, this will be provided by your network administrator. If the computer is connected to a stand-alone network, leave this blank.
Preferred DNS server
Ask your network administrator for the IP address of the preferred Domain Name Server (DNS). Your company may have one or more DNS. The preferred DNS is the first DNS that your computer
communicates with to resolve names to IP addresses. If the preferred DNS server is not available, your computer communicates with the alternate DNS, if one is supplied.
If you are configuring a stand-alone network this parameter can be omitted.
Alternate DNS
server Ask your network administrator for the IP address of the alternate DNS. If you are configuring a stand-alone network this parameter can be omitted.
IP Settings Interface metric Ask your network administrator for this information. If your network administrator does not supply an interface metric, accept the default value during installation.
If you are configuring a stand-alone network this parameter can be omitted.
DNS DNS server addresses, in order of use
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
Append primary and connection specific DNS suffixes
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
Append parent suffixes of the primary DNS suffix
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
Append these DNS suffixes (in order)
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
DNS suffix for this connection
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
Register this connection’s addresses in DNS
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
Use this
connection’s DNS suffix in DNS registration
Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
WINS Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
Options Ask your network administrator for this information. If you are configuring a stand-alone network this parameter can be omitted.
FILLING IN THE SYSTEM DESIGN FORM
Property Description
Domain/Workgroup If you are connecting to an existing network, ask your network administrator to specify the workgroup or domain. If it is a domain, you will need to find out the password from your network administrator.
If you have a stand-alone network, specify a workgroup with a name such as EBI_NW. The name must be the same for all computers on the network. If you have Cardholder
Management on a DSA system, all cardholder servers should be on a common domain. See “Recommendations for Cardholder Management and Global Schedules in a DSA system” on page 30.
Description of EBI Server properties
Property Description
Windows Account Passwords
The passwords for the Windows accounts that are created by the EBI installation wizard.
The passwords are case sensitive, must consist of at least six characters, and include at least one non-alphabetic character.
Note: If you have more than one EBI server (either redundant
servers or a DSA system), the passwords for the mngr
account must be the same on all servers.
For more information about Windows accounts, see “About Windows accounts, operator IDs and EBI security levels” on page 27.
OPC Account Only applicable if you have an OPC server option. This account is used by OPC clients to connect to the OPC server.
Fast History collection interval
The interval at which the server collects fast history snapshots for point parameters for which fast history collection is enabled. The interval can be between 1 and 30 seconds (the default is 5 seconds).
Note: If you make extensive use of fast history, an
excessively short interval may place a heavy load on the server.
FILLING IN THE SYSTEM DESIGN FORM
Description of Modem connection properties
Property Description
Username Password
The remote access user account and password. Only applicable if one or more client computers are connected to the server via a modem.
About computer names
All EBI server and client computers must have a unique name and IP address. The following restrictions apply when naming server and client computers: • The name must be 14 characters, or less, in length.
• The name can contain a combination of standard characters, that is, upper and lower case A to Z, digits 0 to 9, and hyphens.
• The name cannot contain spaces, or any of the following characters: < > ; : " * + = \ | ? , ~ ! @ # $ % ^ & ( )` _
• If you have a non-redundant server, avoid names (server and client) that end with “A” or “B”. Although this is not mandatory, it makes it easier if you later want to upgrade to redundant servers.
• If you have redundant servers, the names of the server computers have a common base name, plus a single-letter suffix. In the case of the primary server, the suffix is “A”, and in the case of the backup server, the suffix is “B”. For example, if the base name is HSSERV:
- The primary server name would be HSSERVA. - The backup server name would be HSSERVB.
FILLING IN THE SYSTEM DESIGN FORM
About Windows accounts, operator IDs and EBI security levels
The EBI installation wizard creates some Windows accounts and an operator ID (which is used to log on to Station).
Windows Accounts
The EBI installation wizard creates one Windows accounts and three Honeywell groups. The following table shows the account details after you install EBI.
Operator IDs
The EBI installation wizard creates the following operator ID. (Operator IDs are used to log on to Station.)
Note
With the installation of EBI R410, the Windows account EBIAdmin will be removed. Oper and Engr accounts which were available in previous versions will still work with sites that use them but are no longer set up when installing EBI.
Caution
Some Windows accounts, operator IDs and EBI security levels have the same names. Consequently, it is important that you do not confuse them.
This topic provides a summary of the accounts, operator IDs and security levels.
Windows group Windows account
mngri
i EBI services and some other EBI processes run under the mngr account.
Administratorii
ii This is the default Windows account.
Honeywell Administrators y y
Honeywell Usersiii
iii Use this group when creating your own user accounts
y y
Honeywell Station Usersiv
iv Use this group when creating user accounts for Station, HMIWeb Display Builder, and Quick Builder users
y Administratorsv
v These are default Windows groups.
y Usersv
EBI security levels
EBI provides the following security levels that apply when you use Station. If you use:
• Station-based security, you can “jump” to a particular security level by typing the password for that level on that Station
• Operator-based security, each person is given a unique operator ID and assigned a specific security level
Operator ID Description
mngr This is the default operator ID for Station, for which the:
• Security level is MNGR (see “EBI security levels” on page 28)
• Default password is mngr1 (note the use of lower case
because passwords are case-sensitive.)
If you intend to use operator-based security, you use this operator ID to log on to Station, so that you can then add other operator IDs to your system.
If you intend to use Station-based security, you do not need to use this operator ID, or create any other operator IDs.
Security level Description
LVL1 Only allows viewing. This level is only available with
operator-based security.
LVL2 Allows viewing and alarm acknowledgement. This level
is only available with operator-based security.
OPER The standard operator level that allows alarm
acknowledgement and routine control.
SUPV Provides access supervisor-level functions.
ENGR Provides access to engineer-level functions. MNGR Provides unrestricted access to all functions.
FILLING IN THE SYSTEM DESIGN FORM
About User Account Control
The Windows Server 2008 and Windows 7 operating systems have a new security feature called User Account Control (UAC) and secure desktop.
This topic summarizes some of the key points related to the new security feature. For more information about UAC, see the Microsoft Web site.
On these new operating systems, by default every application or process is launched with standard user privileges even if the current user is logged on with administrative privileges. (The exception to this is if the application has been specifically marked to launch with higher privileges.) This encourages the use of standard accounts for users of the computer rather than an administrator account. Another security feature on the new operating system is the use of elevation prompts. Elevation prompts are presented to all types of users if the action they are trying to perform requires administrator privileges. This can prevent such things as the silent installation of malware. A standard user must enter the name and password of the appropriate administration account to continue. An
administrative user must give consent to continue.
When the elevation prompts appear, the user’s desktop is replaced with the secure desktop. The user cannot continue normal operation until they cancel the action or give the appropriate consent. Using the secure desktop may cause issues by causing a loss of view of your EBI system. The secure desktop can be disabled. If the Station computer is connected to a network that is adequately secured, Honeywell recommends that the secure desktop be disabled so that there is no loss of view should any elevation prompt appear. Honeywell recommends that you assess the risk of disabling secure desktop.
During installation a new Windows group is created, called Honeywell Station Users. This group has the required privileges that EBI users require to use Station, HMIWeb Display Builder and Quick Builder. During the installation process, the user account used for the installation is automatically added to the Honeywell Station Users group. User accounts for all other users need to be added to this group. Note that this does not prevent the elevation prompts. The new security features can be disabled, however you should only do so in consultation with the site’s IT personnel.
Recommendations for Cardholder Management and Global Schedules in
a DSA system
In a DSA system, Cardholder Management and Global Schedules use Microsoft SQL Server Replication technology to synchronize the contents of the cardholder database on each server.
We recommend that all cardholder servers be on a common domain, logging on to a common domain server. This not only makes the DSA network more secure, it also simplifies account configuration and troubleshooting. If the servers log on to different domains, trust relationships must be set up between all domains the servers log on to.
If the servers do not log on to a domain, they must operate on a common Windows workgroup.
For more information about DSA in relation to Cardholder Management, see “Configuring Distributed System Architecture” in the Configuration and Administration Guide.
RELATED EBI INSTALLATION DOCUMENTS
Related EBI installation documents
The following EBI documents include information that may affect installation/ upgrade tasks. Please read these documents before starting the first task.
Document Description
Known Issues Bulletin and Software Release Bulletin
Includes last-minute information that was not able to be included in the standard documents. You must read them to find out whether they contains any changes to installation/upgrade tasks.
They are on the EBI DVD.
Overview Provides a comprehensive overview of EBI.
Interface and Controller References
There is a separate reference for each type of interface and controller supported by EBI. Each reference includes configuration information specific to a particular interface or controller.
Configuration and Administration
Guide Your main reference after installation, it describes how to configure EBI.
Backup and Restore Guide This guide describes how to backup and restore your EBI servers, clients and data.
2
New installation checklists
This section includes the top-level checklists for installing a new EBI system. Note that you only need to use the checklists appropriate to your installation scenario. For example, if you are installing a small system, you may only need the “Non-redundant EBI server” and “Station” checklists.
Caution
You must use these checklists to avoid installation problems. To learn how to use them, see “Using the checklists” on page 14.
Installation scenario Go to:
Installation of the EBI server
Non-redundant EBI server page 34 Redundant EBI server page 36
Installation of EBI client applications or third-party applications (not on the EBI server)
Station page 40
EBI client applications other than Station, or third-party applications such OPC servers/clients
page 42
Installation of remote point servers and specialized applications
Remote point server page 44 Networked XLNET node page 45 Mobile Station Server page 46
Installation checklist: Non-redundant EBI server
This is the top-level checklist for installing EBI on a non-redundant server. Note that controllers can be installed independently of EBI.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• You have filled in the System Design form.
• The server meets the hardware and software requirements. • The EBI DVD
• The EBI license
• You must log on with Windows administrator privileges.
• You cannot install EBI on a computer that is configured as a Windows domain controller.
• Disable any anti-virus programs on the server while installing EBI.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Tasks
Complete the tasks in the following order.
Task Go to: Done?
Prepare the server
Check the EBI compatibility matrix and verify the server complies with hardware and software requirements
Define the basic server properties. page 126 Configure the display (monitor). page 137 If required, install Microsoft Excel. page 142 Protect against viruses. page 146
Install specialized hardware on the server
If required, install a network interface card (network adapter).
INSTALLATION CHECKLIST: NON-REDUNDANT EBI SERVER
If required, install a LonTalk adapter. page 157 If you have the PhotoID option and this computer is to be
used to capture portraits/signatures, install the relevant hardware and software.
Note: Unless this is a very small system, we recommend
that you install PhotoID hardware on a client computer.
page 247
If required, install terminal server(s). page 271
Install EBI on the server
Install EBI components on the server. page 160 Register the EBI server. page 166 If you have controllers that communicate with the EBI
server via RSLinx, install RSLinx.
page 173
Install and set up associated applications
If required, set up Microsoft Excel data reports. page 176 If you have any third-party OPC clients, create an account
for them. page 181
If required, set up the EBI server as a file server. page 184
Additional tasks
If required, install the localization toolkit.
Configure any peripherals, such as modems and printers, that are connected to the server.
page 187 If your site implements Windows security policies, install
your local policies in the normal manner.
Configure custom firewall settings, if appropriate. page 147 Tune the performance of the server. page 431
Task Go to: Done?
Stop
Installation checklist: Redundant EBI servers
This is the top-level checklist for installing EBI on a redundant servers. Controllers can be installed independently of EBI.
Note that the primary server is called “server A” and the backup server is called “server B”.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• You have filled in the System Design form (page 19). • The servers meet the hardware and software requirements. • The EBI DVD.
• The EBI license.
• You must log on with Windows administrator privileges.
• Disable any anti-virus programs on the servers while installing EBI.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Tasks
The tasks are split up into three stages. Complete the tasks in the following order.
Server A tasks
Complete the tasks in the following order on server A.
Task Go to: Done?
Prepare and install EBI on server A. page 36 Prepare and install EBI on server B. page 38 Perform tasks on both server A and server B. page 39
Task Go to: Done?
Prepare the server
INSTALLATION CHECKLIST: REDUNDANT EBI SERVERS
Define the basic server properties. page 126 Configure the display. page 137 Update the server’s hosts file. page 139
If required, install Microsoft Excel. page 142 Protect against viruses. page 146
Install specialized hardware on the server
If required, install a network interface card (network adapter).
page 150 If required, install serial adapters. page 153 If required, install a LonTalk adapter. page 157 If you have the PhotoID option and this computer is to be
used to capture portraits/signatures, install the relevant hardware and software.
Note: Unless this is a very small system, we recommend
that you install PhotoID hardware on a client computer.
page 247
If required, install terminal server(s). page 271
Install EBI on the server
Install EBI. page 160
Register the EBI server. page 166 If you have controllers that communicate with the EBI
server via RSLinx, install RSLinx.
page 173
Install and set up associated applications
If required, set up Microsoft Excel data reports. page 176 If you have any third-party OPC clients, create an account
for them.
page 181 If required, set up the EBI server as a file server. page 184
Additional tasks
If required, install the localization toolkit.
Configure any peripherals, such as modems and printers, that are connected to the server.
page 187 If your site implements Windows security policies, install
your local policies in the normal manner.
Configure custom firewall settings, if appropriate. page 147 Tune the performance of the server. page 431
Server B tasks
Complete the tasks in the following order on server B.
Task Go to: Done?
Prepare the server
Check the EBI compatibility matrix and verify the server complies with hardware and software requirements
Define the basic server properties. page 126 Configure the display. page 137 Update the server’s hosts file. page 139
If required, install Microsoft Excel. page 142 Protect against viruses. page 146
Install specialized hardware on the server
If required, install a network interface card (network adapter).
page 150 If required, install serial adapters. page 153 If required, install a LonTalk adapter. page 157 If you have the PhotoID option and this computer is to be
used to capture portraits/signatures, install the relevant hardware and software.
Note: Unless this is a very small system, we recommend
that you install PhotoID hardware on a client computer.
page 247
If required, install terminal server(s). page 271
Install EBI on the server
Install EBI in the same location it was installed on server A.
page 160 Register the EBI server. page 166 If you have controllers that communicate with the EBI
server via RSLinx, install RSLinx.
page 173
Install and set up associated applications
If required, set up Microsoft Excel data reports. page 176 If you have any third-party OPC clients, create an account
for them.
page 181 If required, set up the EBI server as a file server. page 184
Additional tasks
If required, install the localization toolkit.
INSTALLATION CHECKLIST: REDUNDANT EBI SERVERS
Server A and Server B tasks
Complete the tasks on both server A and server B.
If your site implements Windows security policies, install your local policies in the normal manner.
Configure custom firewall settings, if appropriate. page 147 Tune the performance of the server. page 431
Task Go to: Done?
Task Go to: Done?
Configure EBI server redundancy. Run setupredun.vbs (located in the \Program Files\Honeywell\ server\run folder) to set up the server for redundancy.
For details, see “Configuring and monitoring a redundant server system” in the Configuration and Administration
Guide.
Stop
Installation checklist: Station on a client computer
This is the top-level checklist for installing Station on a client computer. (The checklist also allows you to install other EBI client applications, such as HMIWeb Display Builder and Quick Builder.)EBI supports two display storage techniques: centralized (displays and shapes are only stored on the server) and distributed (each Station has its own copies of the displays and shapes). For more information about the storage techniques, see “Display storage techniques” in the HMIWeb Display Building Guide.
A Typical client installation type will only install Station and HMIWeb Display Builder. If you want to use distributed storage, select the Custom client
installation type from the EBI installation wizard and select the required display options. For more information about installing Custom client options, see “Custom installation of the EBI client applications” on page 232.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• The System Design form (page 19).
• The computer meets the hardware and software requirements. • The EBI DVD.
• You must log on with Windows administrator privileges.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Tasks
Complete the tasks in the following order.
Task Go to: Done?
Prepare the Station computer
Check the EBI compatibility matrix and verify the computer complies with hardware and software requirements.
Configure the display. page 137 Update the client computer’s hosts file. page 226
INSTALLATION CHECKLIST: STATION ON A CLIENT COMPUTER
If you have licensed the PhotoID option and you want to use this computer to capture portraits/signatures, install the relevant hardware and software.
page 247
Install and set up Station
Install Station and, if required, other EBI client applications.
page 230 If Station and other EBI client applications are installed
on the Windows Vista, Windows Server 2008, or Windows 7 operating system, add the required user accounts to the Honeywell Station Users group.
page 234
If you have a redundant server, configure Station’s setup (stn) files for redundancy.
page 235 If required, set up Station to use multiple monitors. page 237 If required, set up Microsoft Excel Reports. page 176 If required, install the localization toolkit.
Configure the Station as appropriate. For details, see “Configuring Station connection properties” in the
Configuration and Administration Guide.
Task Go to: Done?
Stop
Installation checklist: Client applications (other than
Station) on a client computer
This is the top-level checklist for installing EBI client applications (other than Station), and third-party applications such as OPC servers/clients, on a client computer.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• You have filled in the System Design form (page 19). • The computer meets the hardware and software requirements. • The EBI DVD.
• You must log on with Windows administrator privileges.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Tasks
Complete the tasks in the following order.
Task Go to: Done?
Prepare the client computer
Check the EBI compatibility matrix and verify the computer complies with hardware and software requirements
Configure the display. page 137 Update the client computer’s hosts file. page 226
If required, install Microsoft Excel. page 142
Install applications as required
If required, install EBI client applications. page 230 If required, install Networked XLNET Node page 239 If required, install a third-party OPC client or server. page 241 If required, set up Microsoft Excel Reports. page 176
INSTALLATION CHECKLIST: CLIENT APPLICATIONS (OTHER THAN STATION) ON A CLIENT COMPUTER
Stop
Installation checklist: Remote point server
This is the top-level checklist for installing a point server on a remote computer, that is, a computer other than the EBI server computer.
Note that if you are using both the LonWorks and EIRIS point servers, they must be on separate computers (and therefore require separate adapters).
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• If you are installing a LonWorks point server, a qualified adapter. See the LonWorks Interface Reference.
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• You have filled in the System Design form (page 19). • The computer meets the hardware and software requirements. • The EBI license.
• The EBI DVD. Tasks
Complete the tasks in the following order.
Task Go to: Done?
Check the EBI compatibility matrix and verify the computer complies with hardware and software requirements
Update the computer’s hosts file. page 226
If you are setting up a LonWorks point server, install the
adapter. page 157
Install the point server components on the remote computer.
page 257
Stop
INSTALLATION CHECKLIST: NETWORKED XLNET NODE
Installation checklist: Networked XLNET node
This is the top-level checklist for installing a networked XLNET node.Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• You have filled in the System Design form (page 19). • The computer meets the hardware and software requirements. • The EBI license.
• The EBI DVD. Tasks
Complete the tasks in the following order.
Task Go to: Done?
Check the EBI compatibility matrix and verify the computer complies with hardware and software requirements
Install the Networked XLNET Node software. page 239 Configure the C-Bus.
For details, see “Configuring C-Busses” in the Honeywell
EXCEL 5000 Interface Reference.
Stop
Installation checklist: Mobile Station server
This is the top-level checklist for installing a Mobile Station server.
If Mobile Station Server is to be used in conjunction with Honeywell Digital Video Manager (Honeywell DVM), contact your local Honeywell representative.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• You have filled in the System Design form (page 19).
• The computer meets the hardware and software requirements. (Note that Mobile Station Server requires Windows Server 2008 or Windows Server 2003.)
• The EBI DVD. • The EBI license.
• Windows Server 2008 DVD or Windows Server 2003 CDs.
• You have the required Client Access Licenses (CALs) for Terminal Services, which is an authorization key. (You receive this authorization key when you purchase CALs from Honeywell, or another vendor.)
If your organization already has a Microsoft Terminal Services Licensing Server, you can use this server to assign CALs to handheld devices. In this case, do not install the Terminal Services Licensing option.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Tasks
Complete the tasks in the following order.
Task Go to: Done?
Prepare the Mobile Station Server computer
Check the EBI compatibility matrix and verify the computer complies with hardware and software requirements
Set up the basic server details. page 126 Configure the display. page 137
INSTALLATION CHECKLIST: MOBILE STATION SERVER
Update the server’s hosts file. page 139
Protect against viruses. page 146
Install specialized hardware on the Mobile Station Server
If required, install a network interface card (network adapter).
page 150
Install EBI client software on the Mobile Station Server
Install Station. (You can also install other EBI client
software if required.) page 230 If required, install the localization toolkit.
Install and configure Terminal Services on the Mobile Station Server
Install Terminal Services. page 260 If you installed the Terminal Services Licensing Server,
activate it.
page 262 Install the Client Access Licenses (CALs). page 265 If you are using an existing Terminal Services Licensing
Server, configure Mobile Station Server to access it.
page 267 Limit the number of connections to the Mobile Station
Server.
page 268
Create and configure Mobile Station Server users
Create the Mobile Station Server users. page 269 If providing Mobile Access for Station, configure the
Mobile Access for Station users. page 270
Task Go to: Done?
Stop
3
Upgrade checklists
This section includes the top-level checklists for upgrading EBI. Note that you only need to use the checklists appropriate to your upgrade scenario.
If you are upgrading from EBI R300 or earlier, you must first upgrade to EBI R310, and then upgrade to EBI R410.
Caution
You must use these checklists to avoid upgrade problems. To learn how to use them, see “Using the checklists” on page 14.
Upgrade scenario Go to:
Upgrades to the EBI server
Non-redundant upgrade from EBI R400 on existing server page 51 Redundant upgrade from EBI R400 on existing servers page 55 Non-redundant upgrade from EBI R400 on new server and/or Windows
operating system
page 61 Redundant upgrade from EBI R400 on new servers and/or Windows
operating system
page 66 DSA system upgrade from EBI R400 on existing servers page 73 Non-redundant upgrade from EBI R310 on existing server page 75 Redundant upgrade from EBI R310 on existing servers page 80 Non-redundant upgrade from EBI R310 on new server page 87 Non-redundant upgrade from EBI R310 on existing server with new
Windows operating system
page 93 Redundant upgrade from EBI R310 on new servers page 99 Redundant upgrade from EBI R310 on existing servers with new
Windows operating system
page 107 DSA system upgrade from EBI R310 on existing servers page 115
Upgrades to EBI client applications
Station and displays page 117 EBI client applications other than Station page 119
Upgrades to remote point servers
Remote point server on an existing computer page 121 Remote point server and moving to a new computer and/or Windows
operating system
page 123
UPGRADE CHECKLIST: FROM EBI R400 SP1 ON EXISTING NON-REDUNDANT SERVER
Upgrade checklist: From EBI R400 SP1 on existing
non-redundant server
This is the top-level checklist for upgrading from EBI R400 SP1 on an existing non-redundant server.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• The EBI R410 DVD. • The EBI R410 license.
• Relevant upgrades/service packs (if not on the EBI R410 DVD). • The server meets the hardware and software requirements. • Disable any anti-virus programs while upgrading EBI.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Upgrade Tasks
Complete the tasks in the following order.
Task Go to: Done?
Preliminary tasks
Create a plan for the upgrade. Use the Upgrading Best Practices product bulletin (available from the HBS Product Technical Support Global Website) and the planning information in this guide to create a plan. If you are also upgrading components from the auxiliary DVD, for example, BNPS, FPS, IPPS, you should read the SRB to understand when you need to incorporate upgrade tasks into this checklist.
page 341
Check the EBI compatibility matrix and verify the server complies with hardware and software requirements. Take the access control controllers out of service. This ensures that events are buffered until the upgrade is complete.
If you have any LonWorks point servers, check that the names of the LNS databases comply with the new rules.
page 402 Generate an event archive of all current events.
For details, see the “Archiving Events” section in the
Operators Guide.
If you use the Cardholder Management option and the server is part of a DSA system, disable SQL Server replication.
page 385
Freeze all changes on the server. Back up the server.
For details, see the “Backing up EBI servers” section in the Backup and Restore Guide.
Terminate any Station connections to the EBI server. • Stop any point servers.
• Close any EBI-related applications, such as the EBI Control Panel and Quick Builder.
Unload the EBI database and then close the Start-Stop
EBI Server application. page 206 If RSLinx is installed, uninstall it.
Upgrade the server hardware
Upgrade the hardware as specified when planning for the upgrade.
Upgrade the server software
(Only required if, during planning, you identified the need to upgrade third party software components on the server, for example, Internet Explorer.)
Set the EBI services to manual startup. page 380 Upgrade any other applications as appropriate.
Checkpoint
Before you proceed, ensure the operating system and any software and hardware has been installed correctly. You must fix any errors before proceeding.
Upgrade EBI
Upgrade EBI components on the server. page 362 Register the EBI server. page 166 If you have controllers that communicate with the EBI
server via RSLinx, install RSLinx.
page 173
UPGRADE CHECKLIST: FROM EBI R400 SP1 ON EXISTING NON-REDUNDANT SERVER
Checkpoint
Before you proceed, ensure that the EBI software has been installed correctly and there are no errors. You must fix any errors before proceeding.
Additional tasks
If required, install the localization toolkit.
Complete the upgrade
If you have fire points configured, download the points
from Quick Builder to the server. page 395 Reapply any changes to the system acronym set.
For details, see the “About acronyms” section in the
HMIWeb Display Building Guide.
Reapply any specialized scan periods.
For details, see the “Scanning and standard points” section in the Configuration and Administration Guide. Configure event archiving.
For details, see the “Configuring Event Archiving” section in the Configuration and Administration Guide. Return the access control controllers to in-service and check that they communicate without error.
Tip: You should enable one controller at a time because
they will send buffered events to the server.
When the access control controller are returned to in-service, a download modified action occurs
automatically. You can cancel the download modified action and perform a download all action when all access control controllers are back in service. It is recommended that you perform the download all action during off-peak times as the procedure may take some time and so that cardholders are not unnecessarily denied access. Check that all printers and OPC connections are working. If OPC connections are not working, see “Creating an account for third-party OPC clients” on page 181. Reapply any customizations to system displays. For details, see the “Configuring Stations and printers” section in the Configuration and Administration Guide. Reapply any customizations to the menus.
For details, see the “Customizing toolbars, menus and keyboard shortcuts” section in the Configuration and
Administration Guide
Reapply any customizations to Station’s toolbars For details, see the “Customizing toolbars, menus and keyboard shortcuts” section in the Configuration and
Administration Guide.
Reapply any customizations to Station’s configuration file, station.ini.
For details, see the “Station.ini” section in the
Configuration and Administration Guide.
Reapply any customizations to Station’s setup file,
default.stn.
For details, see the “Station setup files” section in the
Configuration and Administration Guide.
Reset any watchdog timers.
For details, see the “Monitoring the activity of a task” section in the Application Development Guide.
Migrate Station-level scripts. page 387 If you have any LonWorks points servers and have
customized the XML templates, reapply the customizations.
page 406
Task Go to: Done?
Stop
UPGRADE CHECKLIST: FROM EBI R400 SP1 ON EXISTING REDUNDANT SERVERS
Upgrade checklist: From EBI R400 SP1 on existing
redundant servers
This is the top-level checklist for upgrading from EBI R400 SP1 on existing redundant servers.
Attention Make a photocopy of this checklist so that it is easier to keep track of where you are in the installation process.
Prerequisites
• You have read the Known Issues Bulletin and Software Release Bulletin, located on the EBI DVD.
• The EBI R410 DVD. • The EBI R410 license.
• The server meets the hardware and software requirements. • Disable any anti-virus programs while upgrading EBI. • You have a local administrator account.
• If required, you have the Localization toolkit for your language. Localization toolkits are available from your Honeywell Technical Assistance Center. Preliminary Tasks
Complete the tasks in the following order.
Attention The primary server is called “server A” and the backup server is called “server B”.
Task Go to: Done?
Create a plan for the upgrade. Use the Upgrading Best Practices product bulletin (available from the HBS Product Technical Support Global Website) and the planning information in this guide to create a plan. If you are also upgrading components from the auxiliary DVD, for example, BNPS, FPS, IPPS, you should read the SRB to understand when you need to incorporate upgrade tasks into this checklist.