Release notes for version 5.4.

0
WARNINGS
1. DO NOT CONTINUE if this version of software has not been legitimately purchased from the
factory. This installation must be registered with the factory to receive a valid license otherwise it
will expire in 20 days. To register the site, the factory must have a valid purchase order on file.
2. When upgrading from a previous version, be sure to read the Features removed from this release and
Upgrade Considerations below. This version may not be compatible with the existing system
configuration.
3. For details on how to register this software, search on Registration in the on-line help after
installation.
4. If multiple workstations will be required, refer to Network Installation before proceeding.

New features in this release

Note: With the addition of multiple badges per cardholder, all references to “cardholder” limits must be
understood to be a limit to the number of badges that the hardware or software will support.

1. Changed the sa account for new installations of SQL Server Express to use a strong password.
2. Added asset management functionality for eMAX hardware line.
3. Added Operator options.
a. Operator User names may be case sensitive.
b. Added Lockout option on settable number of invalid log in attempts.
c. Operator access may be scheduled.
d. Operator allowed to log into only one workstation at a time.
e. Added user selectable number of password retries.
4. Added optional security for credential printing.
5. Added optional fingerprint capture module. Only available on Windows Vista and Windows 7.
6. Added the ability to assign multiple badges/credentials to any cardholder. See Upgrade
Considerations below for required template and badge design changes.
7. Added enrollment reader functionality.
8. Added support for TWAIN capture devices. Only available on Windows Vista and Windows 7.
9. Added keypad duress mode for eMAX hardware line.
10. Added one-time-events schedule functionality to eMAX hardware line. Unit must be online for one-
time-events to be processed.
11. Increased personnel template tab count from 5 to 10 tabs.
12. Increased personnel screen size. Windows screen resolution should greater than 1024x768.
13. Added the ability to alter the color of text fields in template design. May be used to highlight
required fields.
14. Significantly faster loading of the Desktop Plans on systems with many icons.
15. Implemented MiFare card decoding in eRAM/netEDGE and eMAX hardware.
16. Added second capture option (Import) in Badge print screen to allow capturing a picture from a file.
17. Enhanced dependencies that will be downloaded to eMAX Area Controllers.
18. Added flexibility to configure custom eMAX dependencies through new Triggers and Procedures
configuration tabs.
19. Added capability of implementing a snow day (delayed unlock) feature using Triggers and
Procedures.
20. Added optional ability to configure Door Groups and Output Groups that span modules.
 21. Unprocessed updates to panels are deleted after 7 days by default. Added option to change the
expiration age for updates records.
22. Added option to add custom Allowed types for logging in Time & Attendance table.
23. Added the ability to connect to Milestone Enterprise, Professional and Corporate NVR’s using
Windows authentication.
24. Added optional re-verification of valid access events to ensure that invalidated badges have been
removed from the system hardware.
25. Improved operator activity logging.
26. eReports allows for multiple distinct reports from a single eReport integrator library.
27. SIA-DC07 integrator library now supports Ademco ContactId protocol.
28. Many enhancements have been made to Arabic language localization.
29. Added ability to switch Desktop language localization dynamically.
30. Added Hijri calendar support.
31. Capture function now supports multiple picture, signature and image fields for a cardholder. Only
available on Windows Vista and Windows 7.
32. The Cieffe ViewPoint integrator library has been replaced by the March ViewPoint integrator
library.

Back to top

Bugs fixed in this release

1. MultiPort would crash if eReports was used and the emailed report was larger than approximately
512KB.
2. Desktop allowed weak passwords to be entered when resetting expired passwords when strong
passwords are required.
3. The Save Picture function in Cardholder screen did not function for saving the picture file from the
database to other media.
4. The Desktop would only allow Doors and Outputs to be assigned to one door or output group.
5. MultiPort would have an increased frequency of "Communication Lost" and Communication Back"
messages from encrypted eMAX devices.
6. Miscellaneous bug fixes.

Back to top

Features removed from this release

1. Due to changes in the database, the Notifications integrator library has been removed until further
notice.
2. The IQinVision integrator library is not currently available.
3. Support for perpetual (“Every year”) holidays is no longer available. Holidays that fall on the same
date each year must be added individually.

Back to top
Upgrade considerations
Be sure to read the known issues with this release section below before upgrading to this version

1. Before upgrading see application note AN-107 for upgrade instructions.

The following information is provided to help prepare for the upgrade instructions, and should not be
used in place of AN-107.
2. Be sure that all applications and services have been stopped and closed before attempting the
upgrade.
3. Back up the database.
4. Back up any files in the Data Directory on the server that are unique and important to the site.
5. The database will need to be re-registered for the site after performing any upgrade.
6. After installation of the new version, any customized files such as templates or reports will need to
be transferred to the database before they will be available for use. The Resource Manager
application has been added to allow data files to be imported into the database. To use the Resource
Manager, in the Desktop go to Tools and Resource Manager. When the Resource manager opens,
click on Help for more information.
7. After all installation is complete and verified, the old Server is no longer required and may be
optionally uninstalled using the Windows' Add or Remove Programs application manager. The
obsolete files in the Data Directory are no longer required, and may also be deleted or archived as
desired.
8. CAUTION: When the upgraded system is started for the first time, the firmware in the eRAM and
netEDGE area controllers must be upgraded to the latest version included with this release BEFORE
making any configuration changes to the system. Failure to do this may cause the area controllers to
malfunction until updated.
9. This version of the software is designed to use firmware version 07-205A or later in the BarLock
panels when connected to eRAM area controllers. See Known Issues when using older versions.
10. In versions of the software prior to 5.2, an item not assigned to any partition was available to all
partitions. This is no longer true and an item must be assigned to the partition to be available to a
partitioned operator.
11. This version includes updated firmware for all EP controllers. Be sure to update all EP hardware in
the field using the MultiPort Manager command “Download EP firmware”.
12. The personnel templates file format has changed to support the Identity Management Module.
Because of this change, all existing custom templates being used on site will have to be converted to
the new format before they can be used. The Configuration/Templates/Template Design window has
a new “Convert” button that is used to convert any existing custom templates to the new file format.
13. The badge design file format has changed to support the Identity Management Module. Because of
this change, all existing custom badge designs being used on site will have to be converted to the
new format before they can be used. The Configuration/Templates/Badge Design window has a new
“Convert” button that is used to convert any existing custom badge designs to the new file format.
14. Enabling the ability to add multiple badges/credentials to a cardholder will require modification of
all existing custom personnel templates.
15. Archived Cardholder records cannot be imported back into the database completely. Because of the
new multiple badges/credentials per cardholder function, the badges will have to be manually added
back into the database. The badge data is included in the archived cardholder file.
16. Customer reports that include the Badge field will require modification before the Badge record will
show.
17. Any dependencies where the input and output are on the same eMAX area controller must be tickled
(edited without making any changes) then saved before they will properly download to the area
controller. During this process the dependencies will be removed and created as Triggers and
Procedures.
 18. This release of eFusion is not compatible with previous versions of the AXxess API. Contact the
factory for availability of an updated API before upgrading to this version.
19. The increased size of the Personnel screen requires a screen resolution greater than 1024x768.

Back to top

Network Installation
If multiple workstations will be installed, proceed as follows:

1. When installing the first workstation from the CD, usually on the SQL Server machine, ensure that
the Network Install box is checked. This will install the necessary files to allow additional
workstations to be installed over the network.
2. The network installation package will prompt for a folder location on the local workstation. When
upgrading on the existing Server from a previous version, the location will default to the original
Data Directory since this folder will already be shared on the Network.
3. After installation is complete, a password will be provided. This password will be unique to each
installation, and must be used when installing the additional workstations.
4. After installation is complete, the network file folder will need to be shared on the network if not
already shared.
5. If the network share will only be used when installing additional workstations, the share can be
created with read-only privileges. However, if this same folder will be used for saving files from
different workstations such as exports and archives, then the users on those workstations will need
both read and write privileges on the share folder. Normally read and write privileges would be
selected, however if there are concerns regarding network security, it is possible to share it with
read-only privileges, and even remove the share after all the workstations are installed.
6. To share the folder, right click on it in Windows Explorer and select Share... or Sharing and
Security.... The procedure will differ depending on the operating system so refer to the windows
help, if necessary.
7. To verify that the folder is shared, click on the Windows' Start button and select Run then type
\\WORKSTATION where WORKSTATION is the name of the workstation and click on OK. This
will display the list of shared folders.
8. Due to changes in the operating system and third party firewalls, it may be necessary to configure
the firewall to allow remote connections when running multiple workstations. See application note
AN-009 for information regarding the network ports used by applications and hardware.
9. If SQL Server 2005 EXPRESS has been installed, firewall exceptions must be added and it must be
opened to the network before it will be visible to other computers. See Microsoft knowledge base
article 914277 for more information. http://support.microsoft.com/kb/914277
10. To install the workstation software on another computer, at the computer click on the Windows'
Start button and select Run. Type \\WORKSTATION where WORKSTATION is the name of the
main workstation above and click on OK. Locate the shared folder and open it and double click on
Setup. Enter the network installation password, and then install the necessary components the same
as the main workstation.

Back to top
Known Issues in this release
1. When a panel is set for 1 door mode (slaved reader) and Show in Control List is checked for both
doors, the manual control screen will show entries for both doors. If the slaved door is selected and
unlocked, relay 2 on the panel will unlock not the door relay as expected.
2. If antipassback is being used and a full initialization is performed on an eRAM or netEDGE area
controller, all cards will be forgiven.
3. If using eRAM and BarLock firmware prior to 07-205A, failsafe operation may unlock the wrong
door and keypad operation may be erratic if both keypads are used at the same time.
4. Using eRAM and BarLock firmware prior to 07-205 is not recommended as there are a number of
unsupported functions. However, 07-025 is supported with RAMM Area Controllers.
5. Card access failsafe operation does not function correctly on badges that do not have a definable site
code such as MiFare.
6. Very large reports require a lot of memory and disk space and may cause a workstation to hang or
crash. If this occurs, limit the report size or increase the memory and drive space on the workstation.
7. The documentation for many of the Multiport libraries refers to configuration in the desktop.
Configuration is now done in MultiPort Manager.
8. When Inter-module encryption is first enabled, it may be required to restart MultiPort and re-link
MultiPort Manager for encryption to become fully enabled.
9. When the MultiPort service is started or has been reloaded, the status display in MultiPort Manager
may not display correctly. In these cases closing and reopening the MultiPort Manager or re-linking
to MultiPort will usually resolve the issue.
10. When adding eMAX panels, the maximum panel address allowed is one less than the Panel Count
value in the configuration of the area controller. For example, the default Panel Count for eMAX-
EP1502 and eMAX-EP2500 units is 20. The valid panel addresses when using the default are 0-19
for a total of 20 panels, however the Desktop will allow addresses 0-20 to be added to the area
controller.
11. When both readers of an eMAX-MR51e or eMAX-EP1501 are added to the system, the auxiliary
output on those units cannot be added to the system.
12. Cardholder names may not resolve correctly when using magnetic readers on RAMM elevators.
13. Some configuration changes to eMAX hardware may cause a momentary communication
interruption.
14. Picture display on badge activities is not supported on elevators with floor reporting enabled.
15. PIN entry on eMAX hardware will only resolve names for the primary site code. This is a limitation
of the eMAX hardware.
16. eMAX hardware is limited to 256 access levels and 256 elevator levels per area controller. The list
of access levels and elevator levels is unique for each area controller.
17. eMAX hardware is limited to 256 schedules. The list of schedules is global for all area controllers.
18. Global antipassback may get out of sync on eRAM and netEDGE devices when areas are used by
doors on more than one MultiPort.
19. MultiPort may report HSTMT errors when ambiguous badges exist in the database. Example:
Badge “12345” is entered for one cardholder and the site code for that badge is 50. Badge “90-
12345” is entered for another cardholder. When badge “90-12345” is read, MultiPort may report an
HSTMT error. To resolve, the ambiguous badge number (12345) must be altered to include the site
code in the badge field.
20. The System Status window will return to the top of the list in the right hand pane when it is
refreshed.
21. The Desktop will not allow selecting the maximum allowed panel address for local controller panels
on eRAM, RAMM, or eMAX area controllers. The maximum address may be manually typed in the
“Panel” field.
 22. When adding a new badge record to a cardholder, after accepting the badge record, the cardholder
record must be saved before the badge record may be edited.
23. Changes to the MultiPort links and database connection should not be performed while the Desktop
is in Plan design mode.
24. eMAX procedures cannot be added until one dependency has been added between an input and an
output on a single eMAX-EP.
25. The F1 keyboard shortcut may report “failed to launch help” on some screens. This is likely caused
by the screen losing focus.
26. Removing plan navigation icons from a plan will not update the Desktop plan window until the next
time the Desktop is started.
27. The Archive Manager included in this build is not compatible with Windows XP. Contact factory
for update availability.
28. Several new features for multiple badges and capturing are only available on Windows Vista or
later. Including, but not limited to, fingerprints and TWAIN.
29. Signature capture uses a single temporary capture file in the database for all workstations, and thus
should not be performed at multiple workstations at the same time.
30. eMAX hardware will report a “Door held open” message if the door sensor is open past the held
open timer on a “Door forced” event. When the door sensor is closed, a “Door closed (Forced)”
message is issued. If there is a dependency on the “Door closed (Held open)” message, it will
process even though the message was not recorded in the database. This is a limitation of the eMAX
hardware.
31. If an eMAX area controller is initialized, but the initialization does not complete correctly, the area
controller may report communication lost and communication back approximately every 60 seconds.
32. The included WebPoint package is not compatible with the new multiple badges per cardholder
feature. Contact factory for update availability.
33. The copy button on the personnel templates is not compatible with the new multiple badges per
cardholder feature. Contact factory for update availability.
34. Importing of cardholder records with badge numbers is not compatible with the new multiple
badges per cardholder feature. Contact factory for update availability.
35. The bulk add function in the batch printing screen is not compatible with the new multiple badges
per cardholder feature. Contact factory for update availability.

Back to top