Release notes for version 6.0.2.14042 WAR! GS 1, DO NOT CONTINUE uniess this version of software has been legitimately purchased. 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 fom a previous version, be sure to read the Features removed from this release and Upgrade Considerations sections below. The existing system may be using hardware that may not be compatible with this version of software. 3. For details on how to register this software, search on Registration in the on-line help after installation. 4. Ifthe site will include muttiple workstations, refer to the Network Installation section, 5. SQL Server must not be installed on a domain controller. For details, see Microsoft knowledge base article: https://support.microsoft.comkb/2032911 New features in this release 1. Added compatibility with PCSC FTC/DDM/SDM, IQ, and SIM hardware lines. 2. Supported Windows Operating Systems: Windows 7 (986, x64) Windows Server 2008 (x86, x64) Windows Server 2008 R2 (364) Windows 8 (86, x64) Windows Server 2012 (x86, x64) 3. Supported SQL Server Database Engines: 1. SQL Server 2005: Express, Standard, Enterprise (986, x64) 2. SQL Server 2008: Express, Standard, Enterprise (286, x64) 3. SQL Server 2008 R2: Express, Standard, Enterprise (986, x64) 4, SQL Server 2012: Express, Standard, Enterprise (86, x64) 4. This installation media includes SQL Server 2008 R2 Express edition (86), and SQL Server 2012 SPI Express edition (6), The version that will be installed automatically will depend on the operating system of the computer where SQL Server wil be installed. 1. SQL Server 2008 R2 Express: will be the default database engine for Windows 7, Windows Server 2008, and Windows Server 2008 R2 operating systems 2. SQL Server 2012 SP1 Express: will be the default database engine for Windows 8 and Windows Server 2012 operating systems NOTE: the x86 version of SQL Server will install on both x86 and x64 versions of Windows. wrens NOTE: When installing SQL Server onto a 32 bit OS, it is important to ensure that the OS has been updated with the current Windows patches. Failure to do so may cause the SQL Server installation to fail.13 14, 15. 16, 17. 18, 19. 20. 21. 22. 23. 24, 25. 26, 27, 28. 29, 30, 31 32. 33. ESecnena NOTE: If one of the supported SQL Server versions is already installed, the supplied Express edition of SQL Server is not required. The connection information for the existing SQL Server instance will be required during the installation, NOTE: SQL Server must not be installed on a domain controller. For details, see Microsoft knowledge base article: https:/support.microsoft.com/kb/2032911_ Improved the SQL Server installation processes for the included editions to automate feature configurations that previously had to be performed manually before additional workstations would be able to connect to the SQL Server. Specifically applying SQL Server firewall rules, and allowing remote TCP/IP connections. Desktop system status reports may now be unique for each workstation. ‘Added support for Assa Abloy Aperio wireless door lock hardware for MAX area controllers. Added optional support for integrated enrollment with Bioserypt 4G biometric prox card readers. Added optional support for integrated enrollment with Face Key biometric readers. Added support for Salto Sallis wireless door lock hardware for MAX area controllers, Added support for Schlage AD series wired and wireless lock hardware for MAX EP2500 and PIM AD 400 with eMAX EP1501-AD area controllers, Added optional eTour module for managing real time guard tour operations. Added optional module for Kone elevator integration for "Destination Operating Pane!" and "Car Operating Pane!" elevator operation. Added Routing and Escalation options for alarm messages. Improved the dependency configuration in Desktop for ¢MAX area controllers. Improved cardholder template functionality in Desktop. ‘Added new cardholder template field to display badge design for cardholder on template. Improved hardware configuration experience in Desktop. Added ability to support kegacy Mercury SCP area controllers. Improved Schedule efficiency by implementing a unique list of schedules that are used on each Area Controller. Improved throughput on MultiPort. MultiPort Library configuration has been moved from the Desktop to MuliPort Manager. MultiPort Manager now has an improved editor for commands and scripts. Added the abilty to alter the logging of events on a per MultiPort / message basis to meet requirements regarding personal data collection and storage, ie. the Norwegian Regulatory requirements spelled out in Directive 95/46/EC. Added enhanced operator logging of cardholder changes. Reporter now handles database views as well as tables. This allows easier partitioning of reports. Enhanced operation of Resource Manager when used on systems with a large number of pictures. ViewPoint now supports named presets on some devices. ‘Updated ViewPoint user interface to implement new Microsoft ribbon interface Enhanced operator security with stong password requirement options. Added ability to assign activation and deactivation date and time for access levels when used with eMAX area controllers. Added escorting feature for eMAX and PCSC hardware lines, Enhanced holiday types in e MAX area controllers by adding 5 additional holiday types for use on eMAX area controllers only.34, 35. 36. 37. 38. 39, 40. 4 42. 4B 44, 45 46. 41. 48 49, 50, 51 52 33 34, 55. 56, 57. 58. 59. 60. 61. Enhanced eM AX area controllers to support one-time event schedules. Added new module to Desktop to allow easier editing of eMAX badge formats Added support for TWAIN capture device for documents & images. Enhanced asset administration to include options to capture pictures, print badges, and perform badge enrollment. Enhanced international character set support. Enhanced Milestone ViewPoint integrator to allow for live and recorded video to display on event dependencies. Added SmartVMS ViewPoint integrator. Added Video Insight ViewPoint integrator. Added Canon ViewPoint integrator. Added Archive-Baekup MultPort integrator. Added eMobile MultPort integrator. Updated DVTel ViewPoint integrator. Updated Peleo ViewPoint integrator. Updated Exaeq ViewPoint integrator. Updated Hikvision ViewPoint integrator. Updated Aver ViewPoint integrator. Updated Sony ViewPoint integrator. Updated Vion ViewPoint integrator. Updated Bosch ViewPoint integrator. Updated Geutebruck ViewPoint integrator. Updated Salient Systems ViewPoint integrator. Updated OpenEye ViewPoint integrator. Updated Axis ViewPoint integrator. Updated Toshiba ViewPoint integrator. Updated Generic Interface MuliPort integrator. Updated EventQuery MultiPort integrator. Updated Inovonies MuliPort integrator. Miscellaneous bug fixes k to top Features removed from this release 1 2. Removed support for Windows XP and Windows Server 2003 operating systems. RAMM area controllers are no longer supported by this version of software. All RAMM area controllers must be upgraded to either eRAM or eMAX area controllers either before, or during the upgrade proci The SMS Desktop will no longer update the [BadgeDate] and [BadgeCount] fields in the cardholder record. These fields have been replaced by the [LastPrintDate] and [PrintCount] fields for each badge a cardholder has assigned to them. The [BadgeDate] and [BadgeCount] fields on the cardholder record will be removed in a future version, Please ensure to consider this ifthese fields are being used to track the printing of badges.Back to top Upgrade considerations This version of software is designed to allow direct upgrades ffom version 4.4.1 or later. Ifthe curently installed version is prior to version 4.4.1, or the current system is using MultiDrop or MultiRAMM, please contact the factory before starting an upgrade on that system. General upgrade considerations. 1. Be sure to read and follow the upgrade instructions in application note AN-140 before and during the upgrade process. It is preferred that the upgrade be performed onto a new server rather than performing an upgrade on top of an existing server. However an upgrade on top of an existing server is a viable option when there are no other options, 2. Be sure that all programs (Desktops, Reporters, Communication Modules, ete.) on all workstations have been stopped and closed before attempting the upgrade. 3. Back up the database and store the backup in a safe location, 4, Afler the system has been upgraded, the site will need to be registered with the factory before any significant changes to the database may be made. 5. This version of the soffware inchides updated firmware packages for the eM.AX area controllers. All eMAX area controllers that will communicate with this software should be updated with the included firmware. Failure to do so may result in unanticipated results. 6. This version of the software inchides an updated firewall rules package for the €RAM and netEDGE area controllers, AlleRAM and netEDGE area controllers that will communicate with this software should be updated with the included firewall rules. 7. Afler the software upgrade is completed, the existing hardware will require an initialization. This step is required to ensure proper operation, and failure to initialize the hardware will likely result in undesired operations, 8. Due to customizable nature of the SQL Server database on site itis possible for the Database upgrade process to report errors. This does not normally happen, however should it occur during an upgrade, please contact Technical Support prior to continuing. Most offen these errors can be resolved quickly and casily, and usually do not prevent the upgrade from being completed successfully. 4.4.1 to version 6.0 upgrade considerations. 1. Back up any files in the Data Directory on the server that are unique to this site 2. Afler upgrading the workstation that was previously the AXxess Server, custom files that have been added in the server Data Directory will need to be imported into the database using the Resource Manager. This includes reports, templates, badge designs, cardholder pictures, etc. To use the Resource Manager, in the Desktop go to Tools and Resource Manager. When the Resource manager opens, click on Help. 3. CAUTION: When the upgraded system is started for the first time, any RAM and netEDGE area controllers that are not already upgraded to the latest firmware version will retum an alarm indicating that the firmware must be updated. The firmware must be upgraded BEFORE making any configuration changes to the system, Failure to do this may cause the area controllers to malfimetion. Use the Area Controller Configuration Utility to perform this upgrade.4. 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. In previous versions of the software, 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. In previous versions of the software, the [BadgeDate] and [BadgeCount] fields in the cardholder table were used to track printing of badges. Since the newer versions of software allow for multiple badges per cardholder, these fields have been moved to the [LastPrintDate] and [PrintCount] fields in the [Badges] table so that they more accurately track the printing of individual badges. Back to top Network Installation Ifthe system includes multiple workstations, proceed as follows: 1 When the first workstation is installed from the installation media, usually on the SQL Server machine, ensure that the Network Install box is checked. This will install the necessary files, and provide the required network installation password to allow additional workstations to be installed over the network without needing the installation media, Prior to the network files being installed, the system will prompt for the folder location where the network files should be installed on the local workstation. Ifthe system is being upgraded from a previous version and the server has not changed, the location will default to the original Data Directory. After installation is complete, the network install password will be presented along with the count of installed features. The password will be required when installing the additional workstations. Use the following space to log the password and computer name for the network installation server for the site. ‘Network install password: ‘Network installation computer name: fier installation is complete, the installation foWder must be shared on the network with permissions that will allow the additional workstations to connect and run the setup. Ifthe shared folder will only be used for the installation of additional workstations, then the permissions only need to allow read-only privileges. However, ifthe shared folder will also be used for saving files from different workstations such as exports and archives, then the permissions will need to allow both read and write privileges. Normally read and write privileges will be selected, however ifnetwork security is a higher concem, the shared folder may be set for read-only privileges or it may even be unshared after all the workstations have been 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, Please refer to the windows help, if necessary, 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. 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. Install the necessary components the same as the main workstation. Back to top Basic operation, things to know 1 ‘A few MuliPort and ViewPoint integrators, as well as a few Optional modules require NET framework version 2.0 or 3.5 to operate, Please ensure that the NET framework 3.5 feature (which includes NET 2.0) has been installed on the workstation before instaling optional components. The feature may be added through the Control Panel, Programs and features option on Windows 7 and Windows 8, or in the Server Manager on Windows Server 2008 and Windows Server 2012. ‘The PCSC FTC/DDM/SDM, IQ, and SIM hardware lines use an additional communication service. ‘The PanelProxy service must be running as well as the MultiPort service in order for the MultiPort to communicate with the PCSC hardware Stopping and starting the PanelProxy service will require a reload of the MultiPort service before commnication with the PCSC hardware will resume. Before PCSC hardware may be added to the system, the PCSC Interface optional module must be installed, and MultiPort must be restarted. Until this is completed, the hardware will not be visible in the Desktop for selection, Performing a hard reset of an IQ or SIM panel that has been connected to a MuliPort requires the following steps to ensure proper operation of the panel. 1. Use MultiPort Manager to reload the MultiPort that the panel connects through. 2. Stop the MultiPort and Panel Proxy services, then restart the MultiPort service. 3. Initialize the panel. Coniiguring a DDM, 1Q, or SIM input for supervision mode requires the following steps to activate the changes. 1. Configure the hardware to have the supervised resistors in place, and in the secure state, 2. Configure the sensor for supervised = Yes, and save the changes. 3. Wait for incremental door updates to be processed by MultiPort, and wait for the unit to come back online. 4. Configure the sensor for supervised calibrate = Yes, and save the changes Wait for the indicator LEDs on the DDM, IQ, or SIM to change. 6. Cycle the input point through the alarm and secure states, and verify the indicator LED changes. Note: The sequence of this process is a requirement of the hardware Changes to the Invert setting of an input sensor ona FTC/DDM/SDM , IQ, or SIM must be made with supervision mode disabled. Configuring a FTC/DDM/SDM , IQ, or SIM input for both invert state (secure open) and supervision mode requires the following steps to activate the changes 1. Configure the hardware to have the supervised resistors in place, and in the desired secure stat. 2. Configure the input sensor invert setting as desired. Send the Restart Area Controller command to the FTC, IQ, or SIM, and wait for the unit to come back online. 4, Verify that the input sensor is inverted as desired.© 10, i 12 13, 14. 15. 16. 17. 18. 19. 20, 21. 5. Configure the sensor for supervised = Yes, and save the changes. 6. Send the Restart Area Controller command to the FTC, IQ, or SIM, and wait for the unit to come back online. 7. Configure the sensor for supervised calibrate = Yes, and save the changes. 8. Wait for the indicator LEDs on the DDM/SDM, IQ, or SIM to change. 9. Cycle the input point through the alarm and secure states, and verify the indicator L Note: The sequence of this process is a requirement of the hardware FTC/DDM/SDM, IQ, and SIM doors on the same area controller within a single access level must all use the same schedule, Some hardware does allow different schedules per door within the same access level, because of this, the Desktop will not prevent a user from using different schedules within the same access level. Note: This requirement is a function of the hardware. When a door sensor or REX input is release ftom their normal duties for general purpose use, the sensors are automatically deleted fiom the database, This is done to avoid invalid messages from disconnected inputs. Ifthe input will actually be used, the sensor will need to be added back into the database before it will report. Only the primary FTC may be initialized. Attempts to initialize any FTC that is not the primary will be ignored, Each FTC group may have up to 120 units (FTC, DDM, SDM) in it, addressed 1-120. The address of each FTC on any one MuliPort must be unique, i.e. there cannot be two FTC groups on one MultiPort, each with address 1 for the primary, and 2 for the secondary FTC. The addresses for all DDM and SDM units within an FTC group must be unique, however the addresses do not have to remain unique across FTC groups. For example, each FTC group may have a unit with address 10, and that unit may be a DM in each FTC group. Changes to the Invert setting of the door sensor or REX inputs on a SDM do not take effect until the FIC is restarted. Changes to the Door REX logging, Door REX unlock, and Door REX unlock time settings ona SDM do not take effect until the FTC is restarted Changes to the Door Unlock time and Door Unlock time (Extended) on a SDM do not take effect until the FTC is restarted, Changes to the Card Data format setting on a DDM do not take effect until the FIC is restarted. Using the Assign exit reader setting ona DDM will cause the DDM to fil in such a manner that the on board Reset button must be pressed to clear the unit, Currently the Assign exit reader setting must not be used on DDMs. Invalid PIN messages from FTC/DDM/SDM, IQ, and SIM doors will only be seen following 4 consecutive invalid PIN attempts. Note: This is a function of the firmware in the FTC/DDM/SDM, IQ, and SIM hardware. Invalid site messages from FTC/DDM/SDM, IQ, and SIM doors will only be seen following 5 consecutive invalid site badge read attempts. Note: This is a function of the firmware in the FTC/DDM/SDM, IO, and SIM hardware. For FTC, IQ, and SIM units, the Status... commands in the MutliPort Manager will report the data fiom the previous Status request (either automatically or manually requested). Sending the command a second time ina short period of time will report the current information, Note: This is a function of the hardware interface. Use of the reset button on an IQ or SIM unit will restore normal operation to any doors that have been changes.placed in lockdown mode. Plan icons for the restored doors will still indicate that the door is locked down until they have been manually cleared from lock down mode. 22. Currently the maximum number of schedules allowed at any FTC, 1Q, or SIM unit is reduced by 1 fiom the published maximum for that unit, 23. When managing schedules, the Desktop will allow the user to create schedules with more time intervals than the FTC, 1Q, or SIM units can accomodate. This is by design, as schedules are not only used in the hardware. 24, Disabling DDM. or SDM panels does not prevent messages fiom being received in MultiPort, 25. Changes to the Badge count setting for FTC, 1Q, or SIM unit require a MultiPort reload followed by an initialization before the new setting will take effect. 26. The "Module" selection boxes that exist on many configuration screens will show all FTC units in a group. items in these configuration screens must be created on the primary FTC only. All other FTC units in the group will automatically be updated fiom the primary. 27. When auxuiliary outputs wil need to be momentarily unlocked manually, the Outputs/Energize scale factor: setting will need to be modified on each workstation from the default 3600 to 1. The default scale factor equals | hour, so the time setting in the manual control window will be multiplied by one hour. A scale factor of | equals one second, and a seake factor of 60 equals one minute, Currently the minumum allowed momentary unlock time is 7 seconds. 28, Schedules are limited to 7 intervals for IQ , and SIM units, FTC units are limited to 12 intervals. 29. Schedule special days have changed. Different hardware offers different operation of the holiday types/special schedules. The look of the Calendar and Schedules windows will change depending on the hardware that is configured in the database. Care must be taken when configuring schedules within a system with mixed hardware platforms, 1. eRAM/netEDGE area controllers allow 3 holiday types/special schedules. Only one holiday type is active on any given day on €RAM/netEDGE hardware. 2. eMAX area controllers allow up to 8 holiday types/special schedules. All 8 holiday types may be active on any given day on eMAX hardware, 3. PCSC FIC/DDM/SDM, IQ, and SIM hardware allow one holiday type per day. When configuring the schedules for PCSC hardware, special | is for Monday holidays. Special 2 is for Tuesday holidays, ete. 30. When adding an EP1501 the Add Points option will only add door | to the EP1501 internal panel. Ifthe internal panel will be used as an in-out reader, door 2 must be manually added to the system, and configured as the paired reader in door 1 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, the relay on the panel normal assigned to that door will unlock not the door relay as expected. To eliminate this issue, ensure that only the master door is configured with the Shoe in Control List option checked, Ifantipassback is being used and a fil initialization is performed on an eRAM or netEDGE area controller, all cards will be forgiven.10. i 12 13, 14. 15. 16. 17. 18. 19. 20, 21 22, 23. 24. Ifusing 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. Using RAM and BarLock firmware prior to 07-205 is not recommended as there are a number of unsupported functions. Card access failsafe operation does not fiction correctly on badges such as Mifare CSN that do not have a definable site code 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. ‘The documentation for many of the Multiport libraries refers to configuration in the desktop. Configuration is now done in MuiPort Manager. The elevator control functionality with PCSC IQ and SIM hardware is not currently supported. When initializing 1Q and SIM. area controllers, the MultiPort will show mutiple Communication Lost and Communication Back messages. This is expected behavior. ‘The command list in MutiPort Manager will be blank each time the MuliPort Manager window is opened from the Desktop tools menu, To get the list populated, minimize the MuliPort manager to the system tray, and reopen, After logging in, the command list will be populated. FTC/DDM/SDM, IQ, and SIM outputs must be defined in the system before the state of the outputs willbe tracked. When using occupancy counter on FTC/DDM/SDM, IQ, and SIM hardware, the act of reading the card will increment or decrement the occupancy counter, regardless of whether the door was physically ‘opened or not. Note: This is a function of the firmware in the IQ and SIM hardware. During an initialization of an FTC group, there is a short window (typically less than 10 seconds) where all. FTCs in the group will stop communicating with the DDM and SDM panels. During this time, card reads and REX events at the DDM and SDM panels will not produce an access event. The local alarm output on an DDM and SDM wil only operate in a local alarm shunt capacity. DDM and SDM panels do not report Escorted card access events, only Escort card access events are reported. The IQ and SIM panels report both Escorted and Escort card access events. Momentary energize commands to DDM outputs or output groups do not function. The Tamp, AC Fail, and Batt Fail inputs on the SDM teminal block are not operational. The on board tamper switch is fimetional. Note: This is a function of the firmware in the SDM hardware. The cabinet tamper switch on FTC enclosures is not fimetional at this time. The primary FTC in the enclosure will be the only unit that will report a tamper event. Note: This is a function of the FTC hardware, and how it is configured by the factory. Door lock outputs ona DDM cannot be reassigned to auxiliary outputs. The predefined door lock relay output is the only output allowed for door lock operation, Input point reassignment for REX sensors on DDM doors does not fimction. The predefined inputs for REX work as expected, however the auxiliary input points may not be used. In MultiPort Manager, the individual "Download..." commands should only be used when technical support directs their use, Unusual and undesired results may be seen if used in an incorrect sequence. Changes to a FTC/DDM/SDM, IQ, and SIM doors will resut in the counters in the FTC, 1Q, and SIM being reset to zero, If counters are being used for occupancy, care must be taken when modifying settings for doors, The Schedule Pinpad disable setting for doors is not fimetional,25. 26. 27. 28. 29, 30, 31 32. 33. 34, 35. 1Q and SIM door setting REX unlock time is not functional. FTC, IQ, and SIM units must be configured to communicate through a MultiPort in the same time zone as the unit When using IMM template fil names cannot contain spaces. Spaces in template fle names should be replaced with an underscore " " character. For example, change "Cardholder (Doctors)" to “ardhokder_(Doctors)", This will allow the template to correctly operate in IMM. When Initializing eRAM and netEDGE area controllers, the "Initialization sequence” events are no longer retumed to the MutiPort Manager window. This isa side effect of a new initialization process that will minimize the down time of the eRAM and netEDGE during the initialization. New systems will not allow the "Resource Manager", "MultiPort Manager’, or "Reporter" applications to open without a valid password. On a new installation, if passwords have not been. enabled, those applications cannot be opened. To allow these applications to open without passwords, the System Master password must be set, and then removed from the system. Communication back message will show in MultiPort Manager with a disabled priority. The message does get logged correctly in the database, In order for the new "Public DHCP" setting for eMAX-MRS1e hardware to work, the eMAX-EP that itis connecting through must ako be configured for DHCP. The Bulk Change utility may time out when there are a large number of cardholder records in the database, The "Add Points" check box on the Panels tab cannot automate the addition of Elevator configurations. Changes to CRAM elevator configuration (adding/editing'temoving floor outputs or elevator groups) are not incrementally updated to the RAM. ‘When using the "Bulk Change" application, with localization files for "Croatian, Dutch, Greek, Polish, Portuguese, and Turkish’ languages, the application will report "Cuifure is not supported." and display in English. Back to top