Release notes for version 5.4.2 (5.4.1 security patch) This is a manditory update for any site running versions 5.1, 5.2, or 5.4, WARNINGS 1, DO NOT CONTINUE ifthis 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 fil 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 muttiple workstations will be required, refer to Network Installation before proceeding, 5. eMAX EP area controllers must be upgraded to version 01-118 using the MuliPort Manager command "Download firmware (EP)". Failure to do so will result in seemingly random communication lost and communication back messages for the area controler. 6. As of version 5.4.1.11297, the default password for the "MaxxessUser" SQL Server Express login has ‘been changed to comply with strong password requirements. The new default password is "Letmein4” This change will only affect new SQL Server 2005 Express installations, software upgrades will not alter the password for the existing "MaxxessUser" login 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. Added Salto Sallis finctionality as a standard product. Improved MultiPort Manager status tree window. Added support for badge numbers greater than "4294967294" for eMAX hardware. Access Levels may now begin with a number, but cannot be completely numeric Repe Back to top Bugs fixed in this release 1. Fixed issue where an operator could be granted administrator access using a weak password, 2. Fixed issue where a large number of communication modules in a partitioned system could cause errors when trying to link to some (but not all) of the communication modules, 3. Fixed issue with manually changing a cardholder's area in the antipassback, manual control tab. This issueTAA only impacts RAMM, eRAM, and netEDGE hardware. Fixed a number of issue revolving around the reporting of denied access for PIN entry attempts. Fixed issue where "fault" messages for supervised sensors will be disabled by a disarmed Alarm Zone. Fixed issue where MAX area controller address zero could not be used with encryption enabled. Fixed issue with copy fimetion in Access Levels. Copy button now correctly copies the schedules assigned to the source access level Back to top Features removed from this release Due to changes in the database, the Notifications integrator library has been removed until futher notice. The IQinVision integrator library is not currently available. Support for perpetual (“Every year”) holidays is no longer available. Holidays that fall on the same date each year must be added individually. WebPoint has been removed from the installation CD. The Identity Management Module (IMM) has been created to provide an enhanced web based user interface for cardholder management. Back to top Upgrade considerations Be sure to read the known issues with this release 1 paen 9. section below before upgrading to this version 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. Be sure that all applications and services have been stopped and closed before attempting the upgrade. Back up the database. The database will need to be re-registered for the site after performing any upgrade. fier upgrading from versions prior to version 5.0, any customized files such as templates or reports wil 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. Afier 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. CAUTION: When the upgraded system is started for the first time, the firmware in the €RAM 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 malfimction until updated. This version of the software is designed to use firmware version 07-205 or later in the BarLock panels when connected to RAM area controllers. See Known Issues when using older versions. In versions of the software prior to 5.2, an item not assigned to any partition was available to all partitions.10. 13. 14, 15 16, 17. 18, This is no longer true and an item must be assigned to the partition to be available to a partitioned operator. This version inchides updated firmware for all EP controllers. Be sure to update all EP hardware in the field using the MultiPort Manager command “Download EP firmware”. . When upgrading ftom a version prior to version 5.4, the custom personnel templates being used on site must be converted to the new file format, 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. . When upgrading fiom a version prior to version 5.4, the custom badge designs being used on site must be converted to the new file format. 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. ‘When upgrading ftom a version prior to version 5.4, enabling the ability to add muiple badges/credentials to a cardholder will require modification of all existing custom personnel templates. Archived Cardholder records cannot be imported back into the database completely, Because of the new muutiple badges/credentials per cardhokler function, the badges will have to be manually added back into the database. The badge data is inchuded in the archived cardholder file. ‘When upgrading ftom a version prior to version 5.4, custom reports that include the Badge field will require modification before the Badge record will show correctly. 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. This release of eFusion is not compatible with previous versions of the AXxess API. Contact the fictory for availabilty of an updated API before upgrading to this version. . The increased size of the Personnel screen requires a screen resolution greater than 1024x768. Back to top Ne twork 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 ‘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 akeady be shared on the Network. fier 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. fier installation is complete, the network file folder will need to be shared on the network ifnot already shared. Ifthe 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10. there are concerns regarding network security, itis possible to share it with read-only privileges, and even remove the share afte all the workstations are installed. 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, ifnecessary. To verify that the folder is shared, click on the Windows’ Start button and select Run then type \WWORKSTATION where WORKSTATION is the name of the workstation and click on OK. This will display the list of shared folders Due to changes in the operating system and third party firewalls, it may be necessary to configure the firewall to allow remote comnections when running mutiple workstations. See application note AN-009 for information regarding the network ports used by applications and hardware. IfSQL 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.microsoff.com/kb/9 14277, 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 6. . Ifusing MAX area controllers with dependencies to perform momentary, energize, or deenergize fimtions to Door Group(s) or Output Group(s), other dependencies may be overwritten by the Group dependency during initialization. This is only a problem if the Group has one or more doors/outputs that are on the same panel as the Input point. In these cases, these doors/outputs should be removed from the Group and separate dependencies should be created for the doors/outputs. Any doors/outputs that are not on the same area controller may remain in the Group, and the dependency will perform correctly for those points. ‘The Batch Print function in Personnel does not work. Operators must log into the Desktop before opening the Personnel window. Failure to do so will result in no Personnel templates being displayed. Custom messages added to an eMAX door, sensor, or output with the same address point as another MAX door, sensor, or output will delete any custom messages for the existing eMAX door, sensor, or output when saved. ‘When a panel is set for 1 door mode (saved 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 lock not the door relay as expected, Ifantipassback is being used and a full initialization is performed on an eRAM or netEDGE area controller, all cards will be forgiven. Ifusing RAM and BarLock firmware prior to 07-205, failsafe operation may unlock the wrong door and keypad operation may be erratic ifboth keypads are used at the same time. Using eRAM and BarLock firmware prior to 07-205 is not recommended as there are a number of unsupported fimetions. However, 07-025 is supported with RAMM Area Controllers. Card access failsafe operation does not fiction correctly on badges that do not have a definable site10. ll. 12. 14, 15 16, 17. 18 19, 20, 21. 22, 23. 24, 25. 26, 27, 28. 29, code such as MiFare. Very large reports require a lot of memory and disk space and may cause a workstation to hang or crash Ifthis occurs, limit the report siz or increase the memory and drive space on the workstation The documentation for many of the Multiport libraries refers to configuration in the desktop. Configuration is now done in MutiPort Manager. When Inter-module eneryption is first enabled, it may be required to restart MultPort and re-link MuttiPort Manager for encryption to become filly enabled. .. 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 MufiPort Manager or re-linking to MutiPort will usually resolve the issue When adding eMAX panels, the maxinum 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. When both readers ofan eMAX-MRSte or eMAX-EPISO1 are added to the system, the auxiliary output on those units cannot be added to the system. Cardholder names may not resolve correctly when using magnetic readers on RAMM clvators. ‘Some configuration changes to eMAX hardware may cause a momentary communication interruption. Picture display on badge activites is not supported on elevators with floor reporting enabled. PIN entry on MAX hardware will only resolve names for the primary site code. This is a limitation of the eMAX hardware, eMAX hardware is limited to 256 access levels and 256 elevator levels per area controller. The lst of access levels and elevator levels is unique for each area controller. eMAX hardware is limited to 256 schedules. The list of schedules is global for all area controllers. Global antipassback may get out of syne on eRAM and netEDGE devices when areas are used by doors on more than one MuliPort 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, MuliPort may report an HSTMT error. To resolve, the ambiguous badge number (12345) must be altered to include the site code in the badge field. ‘The System Status window will return to the top of the list in the right hand pane when itis refreshed, 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. ‘When adding a new badge record to a cardholder, afier accepting the badge record, the cardholder record must be saved before the badge record may be edited. Changes to the MultiPort links and database connection should not be performed while the Desktop is in Plan design mode. MAX procedures camot be added until one dependency has been added between an input and an output ona single eMAX-EP. Hotkeys such as FI for help may not work as intended ifthe primary Desktop window loses keyboard fucus. This is default Windows behavior, To resolve, click the mouse on the Desktop title bar and reenter the hotkey. Removing plan navigation icons from a plan will not update the Desktop plan window until the next timethe Desktop is started. 31. Several new features for multiple badges and capturing are only available on Windows Vista or later, including, but not limited to, fingerprints and TWAIN. 32. Signature capture uses a single temporary capture file in the database for all workstations, and thus should not be performed at mutiple workstations at the same time, . Due to fimetion differences, eMAX hardware will always report a “Door held open” message ifthe 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. Ifthere is a dependency on the “Door closed (Held open)” message, it will process even though the message was not recorded in the database. ‘This isa limitation of the eMAX hardware. 34. Ifan eMAX area controller is initialized, but the intiazation does not complete correctly, the area controller may report communication lost and communication back approximately every 60 seconds. 35. The copy button on the personnel templates is not compatible with the new mutiple badges per cardholder feature. Contact factory for update availabilty. 36. Using the Desktop Import routines to import cardholder records with badge numbers is not compatible with the new multiple badges per cardholder feature. When importing cardholder records with badge numbers is required, the Import/Export MultiPort library should be used. 37. The bulk add function in the batch printing screen is not compatible with the new multiple badges per cardholder feature. Contact factory for update availabilty. Back to top