Enterprise Buildings Integrator (EBI) R610.

1
Command and Control Suite (CCS) R310.1
Software Release Bulletin
Issue 1, August 19, 2021

This document provides important information about release contents and installation procedures. It assumes you are familiar with
previous releases of Honeywell EBI/CCS.

This article discusses: Related releases:

• New or changed functionality EBI R430.1 CU2
• Localization EBI R500.1 CU5
• Installation EBI R600.1 CU3
• List of deliverables DVM R700.1 SP1
• Resolved Issues DVM R710.1

Related documents: Support:

• Thin Client Web Server (TCWS) R300 Software Release For information about updates to this
Bulletin bulletin, contact your nearest Honeywell
office or Technical Assistance Center
• PB-746: EBI Cloud Connector registration process
(TAC).
• EBI R610.1 Known Issues Bulletin
• EBI R610.1 Compatibility Matrix
• EBI R610.1 Installation Guide

Copyright 2021 Honeywell International Sàrl

HONEYWELL DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND MAKES NO EXPRESS WARRANTIES EXCEPT AS MAY BE
EXPRESSLY STATED IN ITS WRITTEN AGREEMENT WITH AND FOR ITS CUSTOMERS.
In no event will Honeywell be liable to anyone for any direct, indirect, special, or consequential damages. The information and
specification in this document are subject to change without notice.

1 www.honeywell.com
Revision status

Version Date Description

1 August 19, 2021 Initial version

Revision description
The following sections were added to (A), modified (M), or deleted (D) from version 1.

Section Change Description

2
Contents

Release contents 4
R610.1 new or enhanced functionality 4
Platform support permanently removed in EBI R610.1 5
Technologies and features permanently removed in EBI R610.1 5
Deprecated interfaces and controllers 5
Supported upgrade paths 5

Installing the software 6

About installation 6
Prerequisites for new installations and upgrades 7
Prerequisites for upgrades 8
Installing EBI R610.1 on computers that are part of a domain controller 8
Checking the size of database files before upgrading to EBI R610.1 9
Additional steps for upgrades with Global Schedules 10
Additional steps for upgrades with LonWorks 10
Additional steps for Temaline 11
Additional steps for integrating with Honeywell DVM 11
Installing and configuring Cyber Security Monitoring Services 11
Additional steps for migrating Station client connection shortcuts 12
Localization 12

Troubleshooting 13

Performing post-installation tasks 14

System registration 14
Registering EBI Cloud Connector 14
Configuring DCOM permissions and Group Policy 14
Configuring EBI client Internet options 15
Configuring orchestration 16

List of deliverables 22
Product deliverables 22
Third-party product deliverables 23
Related Product deliverables 23

Resolved issues 25
Issues resolved in EBI R610.1 25
EBI 25
Enterprise Web Services 27
IdentIPoint 28
IPPS-G 28
Quick Builder 28
Station 28
XLS80E 29

Appendix: Installation planning Frequently Asked Questions (FAQ) 30

3
Release contents
This Software Release Bulletin should be used for new installations of EBI, as well as upgrades to EBI R610.1.

R610.1 new or enhanced functionality

This section lists improvements included in EBI R610.1.

IT standard compliance
• Support for Microsoft Windows Server 2019
• Support for Microsoft SQL Server 2019
• Support for Microsoft .NET Framework 4.8
• Removed dependency on port 80
• Removed dependency on Internet Explorer 11
• Support for non-MNGR local or domain service account

Building standards compliance

• BACnet B-AWS v1.15 certification
• AMEV BACnet 2017
• KBOB BACnet 2017

OPC UA enhancements
EBI OPC UA Server interface available to enable OPC UA Clients to access and control EBI point value and history
data:
• OPC UA Server - Data
• OPC UA Server - History

EBI Analytics
EBI R610.1 includes a new core component, EBI Analytics, which supports Healthy Buildings (HB) dashboards that
provide AI-derived insights about EBI events and alarms. EBI Analytics runs as a daemon. The first version of EBI
Analytics counts HB and access events.

CCS scalability improvements

• Support for 20 concurrent CCS client connections
• Support for 20,000 Smart Objects

Support for Forge Connect

New APIs have been added (and existing APIs updated) to enable Forge Connect to retrieve data/history from EBI
and update data in EBI. These new APIs make it easier to migrate to Forge Connect, which serves as the gateway to
integrate EBI and Forge.
• Support for Healthy Buildings dashboards
• EBI History Configuration API for Forge Connect in EWS

4
• Events filter API for Forge Connect in EWS

Capacity changes
• Increased the maximum number of licensable access point readers to 4,000 and non-access point readers to
8,000
• Increased the maximum number of controllers from 512 to 999 if scan task access controllers are not licensed

Platform support permanently removed in EBI R610.1

The Windows Server 2016 operating system is no longer supported in EBI R610.1.
Refer to the EBI R610.1 Compatibility Matrix for a complete list of supported operating systems and Internet Explorer
versions.

Technologies and features permanently removed in EBI R610.1

The following technologies and features have been permanently removed in EBI R610.1.
Note: You should review this list carefully when planning to upgrade a system that may be using any of these features. Contact
your regional EBI product manager for more information about replacement and migration strategies.

• Microsoft Silverlight support

In previous releases, Microsoft Silverlight was used for card printing. Microsoft Silverlight has been replaced by
ASP.NET.

Deprecated interfaces and controllers

EBI R610.1 is the final release to support BNPS for integration of Excel Plus R7044, Excel Classic, Excel IRC, and
EMC controllers, and the DeltaNet-L2 interface. These controller families have been obsoleted and replaced by new
controller types.
All EBI R610.1 new or upgrade orders that include one of these interfaces (either for new EBI systems or for existing
systems that are upgrading to R610.1) will require approval from the regional product manager (RPM).

Supported upgrade paths

Upgrades to EBI R610.1 are supported from the following releases:
• EBI R600.1 CU3
• EBI R500.1 CU5
• EBI R430.1 CU2
Upgrades from the following Temaline releases are supported:
• EBI R600.1 CU3
• EBI R500.1 CU5 (R500_1_Tema_5_7_Update_5 and R500_1_Tema_5_7_Update_5_19)
• EBI R430.1 CU2 (R430_Tema_5_5_Update_3 and R430_Tema_5_5_Update_3_2)
Refer to the EBI Temaline 6.1 Software Release Bulletin for more information.

5
Installing the software
If you are: Follow the instructions in:
Checking whether your system is ready to “Prerequisites for new installations and upgrades” on page 7.
install EBI
Checking whether your system is ready to “Prerequisites for new installations and upgrades” on page 7.
upgrade to EBI R610.1 “Prerequisites for upgrades” on page 8.
“Checking the size of database files before upgrading to EBI
R610.1” on page 9.
Installing EBI R610.1 on a new system EBI Installation Guide
On average, a new installation of EBI takes approximately
two hours, based on hardware specifications listed in the EBI
R610.1 Compatibility Matrix.
Upgrading to EBI R610.1 from an earlier EBI Installation Guide
version of EBI
Upgrading from a previous release of EBI and “Additional steps for upgrades with Global Schedules” on
you use Global Schedules page 10.
Upgrading from a previous release of EBI and “Additional steps for upgrades with LonWorks” on page 10.
you have LonWorks Network Server installed
Upgrading from a previous release of EBI and PB-746: EBI Cloud Connector registration process.
are connected to the Cloud using EBI Cloud
Connector
Integrating EBI with Honeywell Digital Video Honeywell DVM Installation and Upgrade Guide in the
Manager (DVM) 700.1 SP1 or R710.1 relevant Honeywell DVM Documentation Set and “Additional
steps for integrating with Honeywell DVM ” on page 11.
Installing or upgrading a point server from the Before installing components from the Auxiliary DVD, install
Auxiliary DVD the point server components from the EBI main DVD as
described in the EBI Installation Guide.
Then refer to the SRB for the relevant point server to
complete the installation or upgrade.
Installing the Thin Client Web Server (optional) Thin Client Web Server Software Release Bulletin. For the
latest version of the Thin Client Web Server (TCWS), contact
your local Honeywell Technical Assistance Centre (TAC).
Finished with your install or upgrade “System registration” on page 14.

About installation
The EBI Installation Guide in the EBI R610.1 Documentation Set contains detailed installation and upgrade
procedures. To ensure the system is deployed correctly, you must follow each step in the relevant installation or
upgrade checklist. These checklists include steps for preparing, installing, upgrading, and configuring your system.
The additional points described below are also relevant.
For information on troubleshooting the EBI installation, see the section “Troubleshooting” on page 13.

6
Windows updates
You must install all valid Windows updates before installing EBI on each computer. Ensure that EBI computers do not
have any “Not Supported” Microsoft hot fixes installed. Refer to the latest Microsoft Security Hotfix Bulletin available
as a download from https://honeywellprod.sharepoint.com/teams/hbs-EBIHome/Pages/default.aspx

Upgrading an EBI Building Manager-only system

If you are upgrading an EBI Building Manager-only system to EBI R610.1, when the installation finishes the system
may display a message stating that it could not find the CMS database backup and therefore initialized a new CMS
database. This message is displayed because the upgrade process could not find a CMS database backup to
upgrade; you can ignore this message.

Prerequisites for new installations and upgrades

Before installation:
• You have read the EBI R610 Known Issues Bulletin.
• All Microsoft Windows updates have been installed on the target machines.
• Microsoft .NET Framework 3.5 must be installed for EBI R610.1. You may have to deploy this prerequisite
manually:
o If the EBI Server is being installed on Windows Server 2019, Microsoft .NET Framework 3.5 will be
installed automatically, regardless of whether the system is connected to the Internet or not.
o If EBI clients and remote point servers are being installed on a Windows Server 2019 or Windows 10
computer which is connected to the Internet, Microsoft .NET Framework 3.5 will be downloaded and
installed automatically.
o If EBI clients and remote point servers are being installed on a Windows Server 2019 or Windows 10
computer which is not connected to the Internet, you must manually download and install Microsoft .NET
Framework 3.5 before beginning the installation.
For more information, refer to the following link:
https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10
• If you are installing EBI using a domain Administrator account, the account must be added to the local
Administrators Windows Group.
• If your system uses a WSUS server other than Microsoft for Windows updates, you must temporarily disable your
local WSUS server during EBI R610.1 server and client installations and then re-enable it afterwards using the
following procedures:
To disable your local WSUS server
1. Type regedit into the Windows Search box and press ENTER.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
(or equivalent in internationalized systems).
3. Change the DWORD UseWUServer registry key value data to 0.
4. Restart the Windows Update service.
To re-enable your local WSUS server
1. Type regedit into the Windows Search box and press ENTER.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
or equivalent in internationalized systems.
3. Change the DWORD UseWUServer registry key value data to 1.

7
 4. Restart the Windows Update service.
• If you are using LonWorks Point Server or Excel 5000 via LON, you need an Activation Key for the Echelon IzoT
Network Server (LNS) software for each computer that will connect to a LonWorks Network. For more information
about purchasing activation keys, see the section “Additional steps for upgrades with LonWorks” on page 10.
Note: Because it can take a while to issue Activation Keys, you should purchase keys well in advance of installing EBI.

• If you are using BACnet, an active network connection is required during installation. It has been reported that
the BACstac install may fail if there is no active network connection.
• Ensure the server has enough disk space available.
The recommended minimum available disk space required for an upgrade is the greater of 50GB or (40GB + 4
times the size of the backup database obtained by running preparedataforupgrade.bat).
If your system uses CCS maps, you must add an additional 2.5GB per map to the disk space requirement.
Note: If the EBI software will be installed on a different partition, the same amount of disk space is required on the operating
system partition.

Prerequisites for upgrades

Note: If you want to restore events from a previous release of EBI, consider the following points and see the topic “Configuring
Event Archiving” in the EBI Configuration and Administration Guide.
• You cannot restore a pre-EBI R400 archive on an EBI R610.1 server.
• You can have archives from multiple releases restored at the same time.
Before installation:
• IMPORTANT: As a precaution, you should always back up your system before upgrading. It is recommended
you use a program such as Acronis or VEEAM (for ESX environments) to create an image of the hard drive
partition where Windows is installed and where EBI is installed (which may be the same partition). Alternatively,
or in conjunction with drive images, the upgrade may be performed on a new set of hard drives, retaining the
original disk set for backup/fallback purposes.
• If you are upgrading EBI and personal data has been secured as per PB-728: How to enable secure
management of personal data in EBI, complete the following steps. For more information, see the topic “Enabling
encryption" in the EBI Configuration and Administration Guide.
1 Open the EBI Configuration Panel.
2 Go to Enhanced Security Settings.
3 Disable all options.
4 Select OK.

Encryption and decryption of CMS data files and images may take a long time depending on the total size,
and it is recommended to plan for this before starting the upgrade process.
• The data prepared for upgrade may contain personally identifiable information (PII), including cardholder
information and images. Due diligence must be done to protect PII before, during, and after performing an
upgrade. It is highly recommended to dispose of old data once upgrade is complete and the new system is
running with no issues.
For more information on securing the management of personal data on the upgraded system, see PB-728: How to
enable secure management of personal data in EBI.

Installing EBI R610.1 on computers that are part of a domain controller

Domain policies vary from site to site. Depending upon policy, the user account used to install EBI might be
prevented from performing required actions, even if that user is a member of the local Administrators group. To avoid

8
group policy-related installation issues, it is recommended that you temporarily remove the machine from the domain
during the EBI installation/upgrade and checkout process. The machine can be rejoined to the domain when the EBI
installation is completed and system functionality has been verified.
Where site IT policies prohibit removing EBI system computers from the domain:
1 Create a domain user and add that user to the local Administrators group. Make sure there are no local users
with the same name as the domain user.
2 On the local computer, launch the Local Security Policy editor from Windows Administrative Tools > Local Security
Policy. Expand Local Policies and select User Rights Assignment. Add the domain user to the following policies:
• Backup files and directories
• Manage auditing and security logs
• Debug Programs
3 Log on as the domain user and install EBI.
Note: Even after following the previous steps, installation may not be trouble-free since it strongly depends on the complexity of
the domain policies applied on that site. In these cases, consult your local Honeywell TAC for assistance.

Checking the size of database files before upgrading to EBI R610.1

Depending on the size of the SQL database files in your existing EBI system, you may need to perform additional
tasks before upgrading to EBI R610.1. Databases larger than 2 GB can significantly increase installation time, and in
some cases, can cause the installation to fail.

To check the SQL database file size

1 On the server computer, in Windows Explorer, navigate to ProgramData\Honeywell\EBI\Server\data
and sort the files by size so that the largest files appear at the top of the list.
2 Check to see if any files exceed 2 GB.
In particular, check to see if the emsevents.mdf and cms.mdf files are larger than 2 GB. If they are, follow the
advice in the relevant section below. If other files are greater than 2 GB, contact your local Honeywell TAC to
discuss whether the file size will impact the installation.

Reducing the size of the events database

If the emsevents.mdf database is larger than 2 GB it could be because event archives have been restored. We
recommend you remove any restored archives before starting the upgrade. You should plan to remove the restored
archives 24 hours before the start of the installation. This 24-hour period provides time to:
• Remove the archive. Depending on the size of the archive, it can take 45 minutes to remove an archive.
Note that the upgrade process removes any restored archives. Manually removing restored archives can
help reduce the amount of time required to upgrade.
• Run the EMS maintenance task. (On a nightly schedule, the EMS maintenance task moves events that are
older than the “Keep events online for” time period from the online events database. If there is an overlap
between the restored archive and online events, this can increase the size of the online events database.)
If you cannot remove archives 24 hours before installation, contact your local Honeywell TAC to discuss further
steps.
If you do not have restored archive events but your emsevents.mdf database is larger than 2 GB, you should
contact your local Honeywell TAC to discuss how to reduce the size of the database.

9
Reducing the size of the CMS database
If the cms.mdf database is larger than 2 GB and you are using Temaline technology, it could be because transit
events are not being managed. We recommend that you configure a schedule to move and delete transit archives
before attempting installation. For information about scheduling, moving, and deleting transit archives, see the
“Moving data automatically” topic in the “Temaline Interface Configuration Displays Reference” section in the
Temaline Access Control Configuration Guide. When you configure the schedule, set the parameters according to
your site data retention policy.
After the schedule has run, check the size of the cms.mdf database. If the database has not reduced in size, you
should contact your local Honeywell TAC to discuss how to reduce the size of the database.

Additional steps for upgrades with Global Schedules

• We recommend that all schedules are downloaded again after upgrading to EBI R610.1. This will help identify
possible issues early while engineers are still onsite. You should try to complete the download before the
automatic daily download, which occurs at 01:00 AM every day. Before starting a download, make sure the
controllers are online and operating without any errors. Consider performing downloads to controllers at a time
that will be minimally disruptive to the operation of the building, such as outside of business hours.
• Migration of custom displays with the Global Schedules Resource Status Control needs to be done manually
after the upgrade. Using a Command Prompt window on the EBI server, navigate to <install
folder>\Honeywell\Server\ and run the following command by passing in the location of custom displays
as a parameter:
UpdateResourceStatusControlDisplays.vbs <custom displays location>
• For displays with the Resource Status Control located in a custom location (other than the <install
folder>\Honeywell\Client\Abstract folder on the EBI server), you must copy the folder
GSResourceStatusControlImages from <install folder>\Honeywell\Client\Abstract on the EBI
server to the custom location.

Additional steps for upgrades with LonWorks

The Echelon IzoT Net Server has replaced the former Echelon LNS and is used for interfacing with LonWorks
networks starting from EBI R500. EBI R610.1 will automatically install the IzoT Net Server to support the EBI
LonWorks Point Server.
An IzoT Net Server activation key is required to monitor or control LonWorks devices. This key is associated with one
or more Echelon product licenses installed using the Echelon License Wizard. Each license may be used by only one
computer at a time. If your computer cannot communicate to the Echelon license server, you must manually activate
these licenses.
• If IzoT has not previously been used (for example, new installations or upgrades from EBI R430 or
earlier)
You must purchase an OPENLNS SERVER STAND ED KEY (part number 38200-400). Activation Keys can
be purchased through Digi-Key Electronics at the following link:
https://www.digikey.com/en/products/detail/echelon-corporation/38200-400/4754834
Activation Keys may also be purchased directly from Dialog Semiconductor. Dialog Semiconductor acquired
Adesto/Echelon in 2020. For information, see Industrial Edge Computing at https://www.dialog-
semiconductor.com
• If IzoT has previously been used (for example, upgrades from EBI R500 or R600)
If you are upgrading from a previous release that already uses IzoT Net Server, you must use the Echelon
License Wizard to move your license activations from your existing installation to the new computer. Use the
license wizard to “Return” the license on the old computer and then “Activate” it on the new computer.

10
Note: If you want to use the IzoT Commissioning Tool to design/draw your LonWorks system (rather than CARE), the Activation
Key must include the Commissioning Tool product license.

Caution! If you try to use a license on more than one computer (or virtual machine), the license on the old
computer is automatically deactivated.

The Echelon Licensing Wizard requires client-side TLS 1.0 to work in online mode. By default, TLS 1.0 is disabled in
EBI R610.1 on Windows Server 2019. You must modify the registry SCHANNEL values to manually enable TLS 1.0
to complete the automated registration process, and then re-disable TLS 1.0 after the license is successfully
activated.

To enable/disable TLS 1.0

1 Type regedit into the Windows Search box and press ENTER.
2 Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Prot
ocols\TLS 1.0\Client.
3 To enable TLS 1.0:
a Set DisabledbyDefault DWORD to 0
b Set Enabled DWORD to 1
4 To disable TLS 1.0:
a Set DisabledbyDefault DWORD to 1
b Set Enabled DWORD to 0

Additional steps for Temaline

Temaline can be customized via registry entries to enable specific features or behavior. These registry settings are
not migrated, and the upgraded system will have the default behavior. Any customization of Temaline using registry
entries should be noted before performing the upgrade, and then re-applied after the upgrade is complete.

Additional steps for integrating with Honeywell DVM

Integration with Honeywell DVM requires the installation of Honeywell DVM Integration Components on your EBI
server(s). If you are upgrading from an earlier release of EBI that is integrated with Honeywell DVM, you should:
• Check that your Honeywell DVM system will remain compatible with your EBI system after upgrading to EBI
R610.1. Software compatibility is documented in the EBI R610.1 Compatibility Matrix and in the Honeywell DVM
Compatibility Matrix for the relevant Honeywell DVM release.
• Uninstall the Honeywell DVM Integration Components from your EBI server(s) before upgrading to EBI R610.1.
To install the Honeywell DVM Integration Components, follow the instructions in the Honeywell DVM Installation
Guide in the Honeywell DVM Documentation Set for your Honeywell DVM release.

Installing and configuring Cyber Security Monitoring Services

Honeywell provides a suite of Cyber Security Monitoring Services, which can be installed by using the Cyber
Products Installer Tool (CPIT). You can obtain the latest version by navigating to the following link and searching for
CPIT:
https://honeywellprod.sharepoint.com/teams/HBS-ICT-COE

11
Additional steps for migrating Station client connection shortcuts
After migrating your Station client, you must use the Command Client Configuration tool to configure the client
according to your operational requirements.

Localization
This EBI release contains files that require localization. Internationalized sites should apply the EBI R610.1
localization kit to ensure that all language strings are translated in the system.

12
Troubleshooting
This section provides troubleshooting information.

Creating the data encryption file while backing up the database for migration
If, while running the preparedataforupgrade.bat file, the system displays the prompt “Supply values for
the following parameters:” backupFilePath, you must type the full path to the data folder using the exact
filename of dbenc.out to create the data encryption file. For example:
C:\programdata\honeywell\server\data\dbenc.out
The dbenc.out file will then be created, which is the database encryption password.

Installing the Honeywell DVM Integration Components

When you install the Honeywell DVM Integration Components, Microsoft Reporting Services may be slow to restart,
resulting in the following error message:
Setup is unable to register the DVM report “Honeywell DVM Comprehensive Audit”. You
can choose to continue with the installation if you’re not using the DVM reporting
feature.
If this error occurs, clear the Abort Setup check box, and continue with the installation. When the installation is
complete, open a Command Prompt window using the Run as administrator option, and then run the command
ssrsconfig /d when the server is primary to deploy the Honeywell DVM reports.
Note: ssrsconfig commands do not run on the backup server.

Correcting the status of Automation Rules after completing the migration

After upgrading an EBI R600.1 CU3 system to EBI R610.1, some Automation Rules may show a status of Disabled
(Needs Review). To fix this issue, do the following:
1. Open a Command Prompt window using the Run as administrator option.
2. Navigate to <install folder>\Server\ApplicationServices\Services\, where <install
folder> is the folder where EBI is installed.
3. Run the following command:

ApplicationServicesConfig.exe /o:Migrate /mt:R863ToR864

4. On Station, display the Automation Rules summary, select all the Automation Rules that have the status Disabled
(Needs Review), and then click Enable.

13
Performing post-installation tasks
This section describes the tasks you need to perform after you have completed the installation.

System registration
If you are changing to new server hardware, you must re-register the EBI server. For more information, refer to the
“Registering EBI Servers” section in the EBI Installation Guide.
Note: The registration email address has changed since EBI R500. Please ensure you use the email address provided in the EBI
R610.1 Installation Guide.

Registering EBI Cloud Connector

Refer to PB-746: EBI Cloud Connector registration process for details on how to register EBI Cloud Connector by
using the link on the EBI server Windows desktop.

Configuring DCOM permissions and Group Policy

Permissions for launching and accessing EBI DCOM components are required by the EBI service account in most
cases, and the Local Operators group in some. Where possible, these permissions are configured by the EBI
installer.
In Windows Group Policy, the “DCOM: Machine Access Restrictions in Security Descriptor Definition
Language (SDDL) syntax” and “DCOM: Machine Launch Restrictions in Security Descriptor Definition
Language (SDDL) syntax” policies lock down DCOM permissions on the computers beyond what EBI can auto-
configure. These policies are not enabled by default in current operating systems.
• If you enable one or both of the above DCOM group policies on your EBI server computers, you must add the
EBI service account (./mngr by default) and every EBI operator account in the Local Operators group to the
Distributed COM Users group on the EBI server computers.
• If you enable one or both of the above DCOM group policies on your Point Server computers, you must add the
EBI service account (.\mngr by default) to the Distributed COM Users group on Point Server computers.
• If you enable one or both of the above DCOM group policies on your Station client computers, you must add
every EBI operator account in the Local Operators group to the Distributed COM Users group on the Station
client computers.
Failure to add these accounts to the Distributed COM Users group when these group policies are enabled can result
in (for example):
• Failure to communicate with Point Servers.
• Failure to log on to Honeywell DVM through Station.
• Failure to log on to orchestrate using Command Console.
Windows groups can be accessed from “Local Users and Groups” in the Windows Computer Management app.

14
Note: Other Group Policies not discussed here may have similar negative impacts on EBI systems. You should have a procedure
in place for validating your system functionality when changing Group Policy on EBI servers and clients.

Configuring EBI client Internet options

To ensure that an EBI client can communicate correctly with the server (and to optimize performance), you must
configure the Internet options on each EBI client computer. This procedure must be performed for each operator who
logs on.

To configure Internet options

1 Ask the operator to log on to the computer by typing their username and password.
2 Open Windows Control Panel > Network & Internet, and then click Internet Options to open the Internet Properties
dialog box.
Tip: If you cannot open Internet Options, open the Registry Editor and check whether the following entry is
included:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet
Settings\Security_HKLM_only
If the entry is present, set the value to 0.
3 In the Internet Properties dialog box, click the Security tab, and then click the Trusted Sites icon.
4 Click the Sites button.
5 In the Add this Website to the zone box, add the following entry and then click Add.
https://EBIServerName, where EBIServerName is the host name of the of the EBI server.
6 If you have Honeywell DVM as part of your system, add the following:
https://DVMServer, where DVMServer is the host name of the Honeywell DVM Database Server.
7 Click Close to close the Trusted sites dialog box.
8 With Trusted sites still selected, select the Enable Protected Mode check box.
9 If Honeywell DVM is integrated with the EBI system, do the following:
a Click the Custom Level button.
b Navigate to Miscellaneous settings; under Access data sources across domains, click the Enable option.
c Navigate to the User Authentication settings and under Logon, click the Automatic logon with current username and
password option.
d Click OK to close the Trusted Sites Zone Security Settings dialog box.
10 Click the Connections tab, and then click LAN settings.
11 Under Automatic Configuration, clear the Automatically detect settings check box.
12 Under Proxy server, clear the Use a proxy server for your LAN check box.
13 Click OK to close Local Area Network Settings.

15
14 Click the General tab.
15 Click the Delete button in the Browsing history area.
16 Select only the Temporary Internet files and website files check box
17 Click the Delete button to clear the browser cache.
18 Click OK to close Internet Options.
19 Repeat steps 1−18 for each operator.

Configuring orchestration
Orchestration supports user interactions between EBI clients, as well as interactions with Honeywell DVM Console
clients. For more information about orchestration, refer to the topic "Understanding orchestration" in the EBI
Configuration and Administration Guide.
Orchestration uses standard Windows messaging capabilities via an On-Premise Service Bus (known as Service Bus
for Windows Server 1.1), which is automatically installed on every EBI server.
Manual steps are required to configure the Service Bus, and to enable clients to use it.

Task: Follow these instructions:

Check the prerequisites “Prerequisites” on page 16
Configure the Service Bus “Double-click the certificate you want to check.
1 In the Certificate window, on the General tab, look for the
Issued to element to verify that the certificate is FQDN.
2 Click OK.
Configur” on page 17
Set up the Honeywell DVM Console clients “Setting up Honeywell DVM Console clients” on page 19
Register a Honeywell DVM Console “Registering a Honeywell DVM Console subscription” on
subscription page 20
Launch a Honeywell DVM Console client “Launching a Honeywell DVM Console client with an
assigned Console ID” on page 21

Prerequisites
• Your Honeywell DVM system is licensed for orchestration.
• All clients and Service Bus computers must have their time and time zones synchronized otherwise subscriptions
will fail. If subscriptions fail, you will receive the following message:
The remote server returned an error: (401) Unauthorized.
• You know if you have a Fully Qualified Domain Name (FQDN) certificate.

To check whether you have an FQDN certificate

1 On the primary EBI server, open a Command Prompt window using the Run as administrator option.
2 Run the command mmc.
3 In the mmc console, click File > Add or Remove Snap-ins.
4 Under Available snap-ins, click Certificates, and then click Add.
The Certificate snap-in dialog box appears.

16
5 Click Computer Account, and then click Next.
6 Click Local computer, and then click Finish.
7 On the Add or Remove Snap-ins, click OK.
8 On the main mmc console, click Console Root > Certificates (Local Computer) > Personal > Certificates.
9 Double-click the certificate you want to check.
10 In the Certificate window, on the General tab, look for the Issued to element to verify that the certificate is FQDN.
11 Click OK.

Configuring the Service Bus

Note: If domain policies require a password change, the Service Bus will need to be updated or it will stop functioning. For more
information, see “Changing the Service Bus password” on page 19. Also, if it meets your requirements, consider setting the
user account password to never expire.

Creating a Service Bus farm and topics

This task needs to be completed on the EBI server.

Prerequisites
• You have a name and password for an account which will be used to configure Service Bus. The account must
be a direct member of Administrators and Product Administrators Group on the EBI server.
• If the account used to configure Service Bus is a domain account, you are logged in as the same domain account
user on the server.

To create a Service Bus farm and topics

1. Open Windows PowerShell using the Run as administrator option and run the command Import-Module
ServiceFabric.
2. If prompted, choose the Always run option by typing A and press Enter; otherwise, go to the next step.
3. Open the Local Group Policy Editor, and navigate to Administrative templates > Windows Components > Windows
PowerShell -> Turn on Script Execution, and then enable it for all scripts.
4. In the right pane, click Turn on Script Execution.
5. Click Enabled, and then click Apply.
6. Open a Command Prompt window using the Run as administrator option.
7. Navigate to %honeywelldir%Server\ServiceBus\ServiceBusConfiguration.
8. Run the following command:
ServiceBus.Configuration.exe /o:OrchestrationConfigurator /Account=<name>
/Password=<password> /ConsoleIds=<ConsoleId1>,<ConsoleId2>
Where:
o name is the name of the account that you configured to run the Service Bus.
o password is the password for the above account.
o ConsoleIds is a comma-separated list of the Console IDs in use. These are the IDs for Command
Wall, Command Console, Command Station, and Station with maps clients. This ID is defined in the
Client Configuration Tool on the client computers.
For example, if the account name was Smith, the password was abc123, and if there were three Consoles in
use with the ID numbers 1, 5 and 12, the command would be:

17
 ServiceBus.Configuration.exe /o:OrchestrationConfigurator /Account=Smith
/Password=abc123 /ConsoleIds=1,5,12
Note: The above command will also create a Service Bus farm with a default Service Bus auto-generated certificate.
9. If you see errors when running the command, clear the Service Bus farm by following the procedure below, and
then try the configuration again.

To clear the Service Bus farm:

1. From the Windows menu, click Service Bus 1.1 > Service Bus Configuration.
The Service Bus Configuration Wizard is displayed.
2. Click Leave Farm and follow the prompts.
3. Open SQL Server Management Studio (SSMS) and delete the following three databases that were created
during Service Bus farm creation:
o SbGatewayDatabase
o SbManagementDB
o SBMessageContainer
Note: Before deleting the databases, it is recommended that you select the Close existing connections check box.

Reuse the EBI server FQDN certificate

Complete this procedure if you want to replace the auto-generated certificate with an FQDN certificate.
This task must be completed on the EBI server.

Prerequisites
• You have an FQDN certificate on the EBI server.

To use an FQDN certificate that was already present on the server

1 Obtain the thumbprint value of the certificate.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-retrieve-the-thumbprint-of-a-
certificate
2 Use the Set-SBCertificate Powershell cmdlet to use the custom certificate with Service Bus.
https://docs.microsoft.com/en-us/previous-versions/azure/jj614319(v=azure.10)

Exporting the certificate and connection string from the EBI server for Honeywell DVM Console orchestration
This task needs to be completed on the EBI server and is only required if EBI and Honeywell DVM need to be
orchestrated. To set up Honeywell DVM Console orchestration you need the:
• Service Bus trust certificate, if your system does not use a custom FQDN certificate.
• Service Bus connection string.

To get the certificate and connection string:

1 On the EBI server, create a folder on C drive named OrchestrationFilesForDVMConsole.
2 Navigate to %honeywelldir%Server\ServiceBus\ServiceBusConfiguration\Cert
3 Copy the auto-generated certificate file (HoneywellServiceBusCA.cer) to
C:\OrchestrationFilesForDVMConsole

18
4 Open Service Bus Powershell as Administrator.
5 Run the command Get-SBClientConfiguration >
"c:\OrchestrationFilesForDVMConsole\ConnectionString.txt"

Configuring map orchestration

Ensure that all the Geo JSON files in %HONEYWELLDATADIR%\Glass\Store are valid and being used in the
Navigation Model.

Changing the Service Bus password

This task needs to be completed on the EBI server.

To change the Service Bus password:

1. Open a Command Prompt window using the Run as administrator option.
2. Navigate to %honeywelldir%Server\ServiceBus\ServiceBusConfiguration.
3. Run the following command:
ServiceBus.Configuration.exe /o:UpdateAccountPassword /Account=<name>
/Password=<password>
Where:
o name is the name of the existing account that you have configured to run the Service Bus.
o password is the new password for the above account.

Setting up Honeywell DVM Console clients for orchestration

This section is applicable to domains and workgroups.

Establishing a trust relationship with Honeywell DVM

To connect from another computer to the Service Bus, you must establish a trust relationship between that computer
and the Service Bus. This must be done for all Honeywell DVM Console clients using orchestration, as well as for
any computer running applications that publish messages to the Service Bus.
http://msdn.microsoft.com/en-us/library/windowsazure/jj192993.aspx

To establish a trust relationship using your custom FQDN certificate:

1 On the server, open a Command Prompt window using the Run as administrator option.
2 Run the command mmc.
3 In the mmc console, click File > Add or Remove Snap-ins.
4 Under Available snap-ins, click Certificates then click Add.
The Certificate snap-in dialog appears.
5 Click Computer Account, and then click Next.
6 Click Local computer, and then click Finish.
7 On the Add or Remove Snap-ins, click OK.
8 On the main mmc console, click Console Root > Certificates (Local Computer) > Personal > Certificates.
You should now be able to see the certificate chosen previously as the FQDN certificate.
9 Right-click the corresponding certificate, click All Tasks, and then click Export.

19
10 Click Next until a file name is requested. Enter a file name and save the file to a location where it can be copied to
Honeywell DVM console computers later.
11 Copy the exported certificate to the Honeywell DVM Console computer.
12 On the Honeywell DVM Console computer, open a Command Prompt window using the Run as administrator
option.
13 Navigate to the location of your copied FQDN certificate file.
14 Type the following command:
certutil -addstore -f root <FQDNCertificateName.cer>
Where <FQDNCertificateName.cer> is the name of the FQDN certificate exported in step 9.
15 Repeat steps 11−14 on every Honeywell DVM Console computer.

To establish a trust relationship using the auto generated EBI certificate:

On Honeywell DVM Console client computers, the certificate should be installed in the Local Computer “Trusted Root
Certification Authority” certificate store by doing the following:
1 Copy the certificate from C:\OrchestrationFilesForDVMConsole to your Honeywell DVM Console client.
2 Open a Command Prompt window using the Run as administrator option.
3 Navigate to the location of your copied certificate file (HoneywellServiceBusCA.cer or otherwise).
4 Type the following command:
certutil -addstore -f root <CertificateName.cer>
Where <CertificateName.cer> is the name of the certificate file copied from EBI server.

Registering a Honeywell DVM Console subscription

The Console ID for each Honeywell DVM Console client needs to be registered to subscribe to messages. The
following procedure will create that ID for each Honeywell DVM Console client.

Prerequisites
• You have the file you saved the Service Bus connection string to.

On each Honeywell DVM Console client:

1 Open a Command Prompt window using the Run as administrator option.
2 Navigate to your Honeywell DVM Console application directory (by default, C:\Honeywell\DVM Console).
3 Run the CmdLineServiceApi.exe with the following parameter and arguments:
/SetupOrchestration connectionString1 connectionString2
Where the /SetupOrchestration command line parameter takes the following arguments:
connectionString1 - connection string from Service Bus 1 (EBI/CCS Server A).
connectionString2 - connection string from Service Bus 2 (EBI/CCS Server B)

For example:
CmdLineServiceApi.exe /SetupOrchestration “Endpoint=sb://<machinename>/
ServiceBusDefaultNamespace;StsEndpoint=<machinename>:9355/
ServiceBusDefaultNamespace;RuntimePort=9354;ManagementPort=9355”

20
 This will create a Honeywell DVM Console shortcut on the desktop with the correct ID passed into the application
when run.

Launching a Honeywell DVM Console client with an assigned Console ID

Each Honeywell DVM Console that you interact with via Service Bus messages needs to be launched using its
unique Console identifier at runtime. To do this, launch the Honeywell DVM Console using the following command
line parameter:
-id n
Where n is the Honeywell DVM Console ID assigned to identify that Honeywell DVM Console client.
For example:
DVMConsole.exe –id 1
If more than one Honeywell DVM Console client is launched with the same Console ID, only one of those clients will
process the message—it is non-deterministic which client this will be. Therefore, the Console ID must be unique per
client.
Note: If the Honeywell DVM Console is on an EBI client, run the Command Client Configuration tool. In the DVM Console Target ID
box, type a value that matches the value you configured in the topic “Creating a Service Bus farm and topics” on page 17.

21
List of deliverables

Product deliverables
The following product deliverables are included in EBI R610.1.

Installation DVD Item Build/Issue

EBI R610.1 21-2.1
Activator 2.43.0.0
Analytics 1.34.0.0
ApplicationServices.Geo 1.32.0.0
ApplicationServices.Product 1.32.1.2
BrowserControl 1.7.0.0
Cloud Connector 3.2.1.64
Content Management Tool 1.1.1.
EasyMobile 5.3.3.0
Enterprise Web Services 1.8.335.0
Glass IIS services 1.3.417.0
HMIWeb Station and Display Builder 7.4.92.0
Honeywell CCS Components 1.4.285.0
Honeywell Domain Entity Server Templates 1.4.344.0
Honeywell Domain Entity Templates for Apex Client 1.4.344.0
Honeywell ThinkGeo Licensing Tool 1.27.0.0
IdentIPoint Firmware 5.0.149.0
Maps 1.27.0.0
MEDE 2.1.241.0
OPC Server 2.1.241.0
Orchestration 200.26.0.0
Point Data Live 1.9.0.0
Quick Builder 3.9.161
RDFStore 1.27.0.0
Realtime Data Services 1.1.88.1
Salto 2.1.241.0
SQL Server 2019 15.0.2000.5
SQL Server 2019 Express 15.0.2000.5
SQL Server Management Studio 15.0.18369.0

22
 Installation DVD Item Build/Issue
Temaline 6.1.0.7
Window Manager 1.8.233.0

Third-party product deliverables

The following third-party product deliverables are included on the EBI R610.1 Installation DVD.

Installation DVD Item Build/Issue

BACstac R7.0j
IzoT 4.40
NetMonI 6.10
PCMon R6.10
Remote Sync Server R2.08.21
SQLXML R4.0 SP1

Related Product deliverables

The following related product deliverables and third-party products are included on the EBI R610.1 Auxiliary DVD.

Auxiliary DVD Item Build/Issue

BNA3 1.0.6.L
BNA-I 5.0.1.B
BNA-II 5.0.1.B
BNPS R6.10
Cache Generator 1.27.0.0
CBNA-1 4.0.2
CBNA3 1.0.3
CBNA-II 3.0.1
DomainEntityBuilder 864.1.921.0
DomainEntityCustomizer 864.0.3612.90
DotNetFramework .NET 4.8
FNA3 1.0.4.U
FNA-I 5.0.0.A
FNA-II 5.0.0.C
FPS R6.10
Honeywell Automation Rules - Instant Alert Plus 1.3.221.0
Honeywell OPC UA Server Connect R610.1

23
Auxiliary DVD Item Build/Issue
IPPS-Galaxy R6.10
IPPS-Vista R6.10
Mercury Interface R190
ServerBackupAndRestore 1.3.0.0
XLS80ePS R6.10

24
Resolved issues

Issues resolved in EBI R610.1

EBI

Access Downloader
• ISR 222935 On a multi-credential system, non-IdentIPoint cards sometimes may be flagged as requiring
download to an IdentIPoint reader.

• ISR 222957 An arithmetic overflow error occurs when more than 32767 access groups are required for
IdentIPoint.

• ISR 223112 On systems with many readers and access groups, downloading IdentIPoint cards is slow.

• ISR 223549 Cards may not be downloaded and may be denied as "certificate too old" if an IdentIPoint card
renewal download times out.

• ISR 228070 Under certain circumstances, IdentIPoint downloads may fail due to incomplete time period
assignments.

Alarm Pager
• ISR 223134 The Alarm Pager has minor issues with the GSM modem "Preferred Message Store" command.

Automation Rules
• ISR 223089 If the points and parameters are not in capital letters in the "Control Points by location" action, the
system cannot validate the rule.

• ISR 223886 On a system with many automation rules, the validation of all rules at startup takes too long.

• ISR 225021 The automation rules engine may become locked if a rule is re-saved at the same time it is
activated.

• ISR 225155 DVM alarm monitor actions may fail if executed concurrently.

• ISR 228145 Camera views sent to Alarm Monitor via Automation Rules do not show the cause of the alarm in
the caption for access events.

• ISR 228274 The system cannot validate many (over 550) automation rules and execute rules at the same
time.

Cardholder Management
• ISR 222951 IdentIPoint card read errors flood the SQL log with hsc_sp_GetLegacyHolderInfoFromCard errors
that are expected and should be suppressed.

25
Cardholder Presentation - Card Printing
• ISR 223569 Encode and Print is not sent to the printer if only one card layout is assigned.

Displays - General
• ISR 223159 Changes to some options on the Server Wide Settings display are not evented.

• ISR 223336 When an operator changes an access level, the operator name is not shown with the "last
change" details.

• ISR 223344 A deleted operator profile is still shown as available on the Operator Assignment details display.

Incident Workflow
• ISR 220724 Subreports are not produced when an Incident Detail report is run with the destination set to a
PDF file.

Installation
• ISR 223417 Changing the server name by using "hscconfig /servername" does not update the connection
string for OPC Data Transfer.

• ISR 226384 On the Start menu, the Enterprise Buildings Integrator -> BACstac Configuration Tool command
does not work.

LONWorks Point Server

• ISR 225065 If the XML template for a point references a non-existent enum, point values are displayed in
inverse video.

MicroLPM
• ISR 226316 When a site has a negative time offset, PCSC-FT controllers do not report alarms correctly.

OPC Data Client (Scan Task)

• ISR 223530 OPC scan task points using data format 13 (REAL) do not convert int4 data types in the same
way as previous product releases and no other available data format works.

OPC UA Server
• ISR 223637 The OPC UA Server process continuously logs that it is unable to validate the application on a
server that does not have a license for it.

Realtime Data Services

• ISR 220628 When redundancy failover happens, some parameters are sometimes set to BAD and do not
report normal until a COV is received.

26
• ISR 225015 If the RealtimeDataServer runs for more than 24.8 days, several point server functions become
unresponsive.

• ISR 228030 When Three Stage alarm management is enabled, each alarm from a Real Time Data Services
point server has to be responded to twice: once for the original alarm, and once for the alarm
acknowledgement.

Redundancy - Server
• ISR 223413 Redundancy synchronization fails if Winhttp calls fail on the backup server due to the proxy server
not forwarding local packets directly.

Redundancy - SQL
• ISR 223036 Redundant replication locks the CMS database, which can prevent CMS working while servers
are synchronizing.

Reports
• ISR 223120 Print Preview on the event and alarm summary display refers to the A Server when B is the
Primary server.

• ISR 227915 Selecting a door in the Door Access report might be difficult because the ordering of the door list
is inconsistent and may change during selection.

Salto E-lock
• ISR 223320 Salto Elock low battery alarms return to normal in a few seconds even though the alarm is still
active in the Salto controller.

Scanning Subsystem
• ISR 223502 Systems that are not licensed for scan task access controllers should be able to extend the
number of controllers beyond the current system limit of 512.

Utilities (non engineering)

• ISR 223836 Changing the server name by using "hscconfig /servername" fails to update server name
references that are used in automation rules

XLS
• ISR 223142 XLS firmware and database values cannot be reset from Station after the field hardware/firmware
is changed.

Enterprise Web Services

27
Server Interop
• ISR 226327 Enterprise Web Services (EWS) does not support raising events with custom categories.

IdentIPoint

Access Firmware
• ISR 217394 A buffer overrun in the mifare card library code causes the card reading thread to terminate and
leads to a deadlock that results in comms loss.

• ISR 220031 Buffer overrun in low level mifare code is not handled correctly by the 5.0.148.0 firmware

EBI Server
• ISR 220514 Input Close Circuit event entries are not being cleared from the irdb->alarm table.

IPPS-G

Core
• ISR 212128 Sometimes EBI graphics that display values for the IPPS alarm point (alarm state, physical state,
and so on) show these values as blacked out.

• ISR 223514 Values in Point Detail displays take up to 30 seconds to populate if the point parameters are not
currently in subscription.

Quick Builder

Selector
• ISR 137186 When adding a new BACnet controller, the Controller column shows the BACnet instance number
instead of the controller name.

Station

Content Window
• ISR 226577 On a multi-window setup, Station windows lose their pinned status after they are recycled.

28
Window Manager
• ISR 223477 Window Manager fails to refresh the map window if Internet Explorer terminates.

XLS80E

Reports
• ISR 222154 The XLS80e sensor status report shows discrepancies for the device Status, Pre-alarm and Short
circuit properties.

29
Appendix: Installation planning Frequently Asked Questions
(FAQ)
What format does the package come in?
DVD and electronic download from SoftCo.

Where do I find information on prerequisites for hardware\software?

See the EBI R610.1 Compatibility Matrix.

Do I need to upgrade the operating system?

Yes, see the EBI R610.1 Compatibility Matrix for more information.

How do I upgrade my operating system on my existing EBI servers?

Upgrading Windows on an existing EBI server computer is not supported.
You need to install a new clean operating system before installing/upgrading EBI.
Please refer to the corresponding checklist in the “Upgrade checklists” sections of the EBI Installation Guide.

How long does a new install of EBI take?

Approximately 1.5 to 2 hours.

How long does an upgrade of EBI take?

2 to 2.5 hours

Do I need to install the latest Cumulative Update (CU) to my system before I upgrade?
Yes. Upgrades are only supported from the latest CU versions.

How can I make the upgrade faster? How do I ensure there are no events lost during the upgrade?
See the section “Checking the size of database files before upgrading to EBI R610.1” in this document before
installing.
Notes:
• Reducing the size of the EMSEvents database reduces the system upgrade time as there are fewer events to
migrate.
• Failure to reduce the size of the EMSEvents database could result in a loss of events.
• To reduce the possibility of losing events, you must minimize the time between archiving events and stopping the
server.

Will EBI run on my current hardware?

EBI R610 should run well on any server computer that is approximately 1−2 years old.
We have summarized the performance specification requirements, and you must ensure that your server meet these
minimum requirements.
Remember you must install Windows Server 2019 on the server hardware; see the EBI R610.1 Compatibly Matrix.

30
Which versions of Honeywell DVM are supported?
DVM R700.1 SP1 and R710.1.

Do I need to restart the EBI server after completing the installation?

Yes.

Can my system continue to operate during the upgrade?

No, the EBI server upgrade is an offline process that requires a new operating system to be installed. However, if
new hardware or a new virtual server machine is used, the original system can remain online until the cutover time.

Can my old EBI Station client connect to the new system?

No. See the next question for more information.

How do I upgrade a system that has many Stations?

Most systems will need to upgrade the operating system and the Station version for each client.
As far as is possible, all Station clients must be upgraded at the same time as the EBI server is upgraded, as there is
no interoperability supported between R610.1 and R500.1 CU5 or R600.1 CU3 Station/server combinations.
One recommendation is to upgrade one or more Stations to R610.1 before you upgrade the EBI server so that you
can always maintain visibility of critical operations during the upgrade.
Another recommendation is to install a temporary computer (for example, a laptop) pre-installed with the Station
upgrade version.

I have an EXCEL 5000 point server/LonWorks point server. Are there any specific tasks I need to do to upgrade?
Please see the relevant section in the “Upgrade Tasks” section in the EBI Installation Guide.

Can I view events from the previous EBI release?

Yes, events are migrated, both in the flat file and in the EWS SQL database. Event archives can also be restored
from older releases into the new system; testing has proved that event archives from as far back as EBI R430 can be
successfully restored.

Do I need to upgrade the firmware in the controllers?

See the EBI R610.1 Compatibility Matrix - Interfaces & Options tab for more information.

Is there an installation order when upgrading?

See the section in the “Installing the software” section in this document that is relevant to your system architecture.

Which interfaces are no longer supported in this release?

Refer to the EBI R610 Advanced Training slides available from the following link:
https://honeywellprod.sharepoint.com/teams/hbs-EBIHome/techresources/Pages/TechnicalTraining.aspx

What benefit does support for Chromium in Station provide to my customer?

Chromium support enables modern web pages to be displayed inside EBI Station. This enables customers who need
content from an external website to display it in Station.

31
Does support for Chromium in Station eliminate the dependency on IE11?
No. IE11 is no longer required to be installed.

When I build a custom display using HMIWeb Display Builder, will the display use Chromium?
No. EBI custom displays that are created by using HMIWeb Display Builder will continue to use the traditional IE
browser component.

Do any new system displays use the Chromium browser?

No.

In a redundant EBI system, should I install EBI R610.1 on the A server first, or on the B server?
EBI R610.1 can be installed first on either server. For more information, refer to the section “Installation checklist:
Redundant EBI servers” in the EBI Installation Guide.

Will my integration to Honeywell DVM be affected?

Yes. The Station configuration (.stn) file must be updated after completing the installation. See the “Prerequisites for
new installations and upgrades” and “Performing post-installation tasks” sections in this document.

Do I need to update any components on Honeywell DVM?

If you are integrating with Honeywell DVM R700.1 SP1 or Honeywell DVM R710.1, you must install the
corresponding Honeywell DVM Integration Components. See the section “Additional steps for integrating with
Honeywell DVM” in this document.

Will my point DSA to earlier versions of EBI be affected?

No. But refer to the EBI R610.1 Compatibility Matrix - DSA interoperability tab to be sure.

I applied a Rolling Update to fix a software defect in my earlier version of EBI/CCS. Will the fix also be included in EBI
R610.1?
If you have an ISR number associated with the software defect, you can check the “Resolved issues” section and the
Known Issues Bulletin to confirm whether your fix is included in EBI R610.1. If you still have concerns, contact your
local regional TAC.

What should I do if I see any error messages during installation?

Take a screen snapshot (ALT + Print Screen) and paste the image into Microsoft Paint. Save the image as a *.jpg file
and send it to your Honeywell TAC with a Diagnostic Framework package. Remember to include as much
information about the situation as possible.

What devices will need to be re-commissioned after the upgrade?

You should not need to re-commission any devices if the configuration remained the same. As part of the site’s post-
upgrade tests, you may want to test some devices to confirm everything works as before.

Do I have to change the DVD during the installation or attend to it in any way?
No. After you have selected the initial settings, and after it has started installing Microsoft SQL Server, the installation
can be left unattended to complete its tasks. There are no more Next buttons to click.
Some point servers are installed from the AUX DVD after completing the main EBI install procedure.

32
Do I need to run any software before starting an upgrade?
When preparing for an upgrade, the most important software is the Acronis software to back up your computers. For
a checklist of the upgrade tasks you will need to perform, see the relevant checklist in the “Upgrade checklists”
section of the EBI Installation Guide.

Can I keep the same directory structure in EBI R610.1 that I had in my existing EBI server?
You can, but the recommended setup is to use the new default directory for EBI R610.1, which is the
\ProgramData\Honeywell directory. Be careful if displays contain hard-coded drive path references.

I have both Honeywell DVM and Temaline connected to my original EBI system. I am upgrading using the same
hardware. What will happen to the Honeywell DVM integration after I upgrade to R610.1?
You will install a new operating system. When the EBI R610.1 installation has completed successfully, you can install
the Honeywell DVM components. Temaline is upgraded by the R610.1 installation.
For more information, see the section “Interactions between Temaline Interface and DVM (Digital Video Manager)” in
the Temaline Access Control Configuration Guide.

I have an existing EBI system with Temaline, I am upgrading to R610.1. Do I need to install the Temaline point server
again?
No. The EBI R610.1 upgrade process migrates the Temaline database and point server.

Do I need to do a backup before I upgrade?

Yes. Follow the recommendations in the Backup and Restore Guide.

On what drives and partitions do you recommend I install EBI R610.1?

For information, see the “Recommended disk configuration” section of the EBI Installation Guide. Also refer to the
EBI R610.1 Compatibility Matrix - Server Hardware tab for hard disk recommendations based on system size.

How do I upgrade an EBI that has Honeywell DVM integrated? What do I need to do with Honeywell DVM?
For the EBI servers:
• You will install a new operating system. When the EBI R610.1 installation has completed successfully, you can
install the Honeywell DVM components.
For the EBI Stations:
• Uninstall the Honeywell DVM client components
• Upgrade the EBI Station software
• Install the Honeywell DVM client components

My current system is not supported for direct upgrade to R610.1. Do I need to run the system on an R610.1 supported
pre-R610 upgrade version before upgrading to R610.1?
It is good practice to run any upgraded version for a few days to validate the system before upgrading to R610.1.
Remember that you should include test time as part of any upgrade planning process.

33
Where can I find information about the new features of EBI R610.1?
There are many good resources, for example:
• Slides and podcasts from the Technical How-to Sessions are in the Technical Resources section on the HBS
Product Technical Support Global Website at:
https://extranet.honeywell.com/HBS/EBI/EBIHOME/Pages/default.aspx
• EBI R610 Advanced Training slides can be found at:
https://honeywellprod.sharepoint.com/teams/hbs-EBIHome/techresources/Pages/TechnicalTraining.aspx
• Slides and marketing collateral associated with the release are available from HBS Systems and Products team
room at:
https://honeywellprod.sharepoint.com/teams/HBSSystemsandProducts/SitePages/Integrated%20Operations.
aspx

Do known issues related to EBI 610.1 have workarounds?

See the Known Issues Bulletin for details of known software issues and corresponding workarounds. The Known
Issues Bulletin is posted on the HBS Product Technical Support Global Website at:
https://extranet.honeywell.com/HBS/EBI/EBIHOME/Pages/default.aspx

What if I have a question about my installation or upgrade that is not answered here or in the EBI Installation Guide?
For any additional questions, please contact your local TAC before you attempt an installation or upgrade.

34