Release notes for version 6.1.3.16146 [Release date: May 25th, 2016. WARNINGS 1, DO NOT CONTINUE unless 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 fi 2. When upgrading from 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. If the site will include multiple workstations, refer to the Network Installation section. . SQL Server must not be installed on a domain controller. For details, see Microsoft knowledge base article: https://support microsofi,com/kb/2032911 New features in this release 1. Supported Windows Operating Systems: 1, Windows 7 (x86, x64) 2. Windows Server 2008 (x86, x64) 3. Windows Server 2008 R2 (x64) 4, Windows 8 (x86, x64) 5. Windows Server 2012 (x86, x64) 6, Windows 10 (x86, x64) 2, Supported SQL Server Database Engines: 1, SQL Server 2005: Express, Standard, Enterprise (x86, x64) 2. SQL Server 2008: Express, Standard, Enterprise (x86, x64) 3. SQL Server 2008 R2: Express, Standard, Enterprise (x86, x64) 4, SQL Server 2012: Express, Standard, Enterprise (x86, x64) 5. SQL Server 2014: Express, Standard, Enterprise (x86, x64) 3. This installation media includes SQL Server 2008 R2 Express edition (x86), and SQL Server 2012 SPI Express edition (x86). 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, Windows 10, and Windows Server 2012 operating s O01 the x86 version of SQL Server Express will install on both x86 and x64 versions of Windows. NOTE: When installing SQL Server Express 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. 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 a sysadmin login on 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 MultiPort service startup process. Improved MultiPort service linking process. Improved email dependency operation. Resolved issue with Alarm Notes display. Resolved issue with creating custom capture types. Resolved issue with creating custom badge designs. 10, Resolved issue with System Master operator becoming disabled. 11, Added eMAX Intrusion Processing Support functionality. 12. Added eMAX-MRDT Intrusion Panel keypad support. 13. Added eMAX-4502 Area controller support 14, Added support for Honeywell Galaxy Dimension or Flex intrusion panels. 15. Added support for Bosch Automation Mode One aware intrusion panels. 16, Added support for Schindler PORT Technology Elevator destination dispatch control. 17. Added support for Maxxess AlarmKey event annunciator. 18, Added support for Evolis TWAIN signature tablet. 19. Added support for Mercury enabled Aperio 1-8 hub. 20. Added support for March ESM, RS SDK connections. 21. Resolved issue with SQL Server error when Door Groups. 22. Added support for auto populating the DoorData table when adding new Area Controllers, Panels, Doors, Sensors, and Outputs. 23. Miscellaneous bug fixes. 4. 5, 6. 1. 8, 9. Back to top Features removed from this release 1. RAMM area controllers are no longer supported by this version of software. All RAMM area controllers must be upgraded to either CRAM or eMAX area controllers either before, or during the upgrade process. If the RAMM area controllers are changed to eMAX area controllers, then the BLPs must also be converted to eMAX-MR200 panels. 2. 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 if these fields are being used to track the printing of badges. 3. IMM is currently not included in this release. Contact factory for availability. Back to top Upgrade considerations This version of software is designed to allow direct upgrades from version 4.4.1 or later. If the currently installed version is prior to version 4.4.1, or the current system is using MultiDrop, RAMM or MultiRAMM, please contact the factory before starting an upgradeReo on that system. When this version of software will be installed onto a system with versions prior to 5, be sure to uninstall the previous version completely before starting the installation process. When installing the Workstation for this version over an existing version 6.0.2 or earlier Workstation that also includes ViewPoint, be sure to manually uninstall ViewPoint before installing the new version. General upgrade considerations. 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. . Be sure that all programs (Desktops, Reporters, Communication Modules, ete.) on all workstations have been stopped and closed before attempting the upgrade, Back up the database and store the backup in a safe location After 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. This version of the sofiware includes updated firmware packages for the eMAX 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. This version of the software includes an updated firewall rules package for the RAM and netEDGE area controllers. All RAM and netEDGE area controllers that will communicate with this software should be updated with the included firewall rules. After 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. Due to customizable nature of the SQL Server database on site, it is 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 often these errors can be resolved quickly and easily, and usually do not prevent the upgrade from being completed successfully. 4.4.1 to version 6.x upgrade considerations. Back up any files in the Data Directory on the server that are unique to this site. . Afler upgrading the workstation that as 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. 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 return 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 malfunction. Use the Area Controller Configuration Utility to perform this upgrade. This version of the software is designed to use firmware version 07-205A or later in the BarLock Panels when connected to RAM 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. For Salto SVN support, this version of software requires Salto ProAccess Space version 2.0.8.4 or later. Using earlier versions of Salto ProAccess Space or Salto ProAccess RW will produce undesirable results, Back to top Network Installation If the 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. If the system is being upgraded from a previous version and the server has not changed, the location will default to the original Data Directory. . Aer 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 install Computer Name: After installation is complete, the installation folder must be shared on the network with permissions that will allow the additional workstations to connect and run the setup. If the shared folder will only be used for the installation of additional workstations, then the permissions only need to allow read-only privileges. However, if the 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 if network security is a higher concern, 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. Network installation shared path: 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. 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 MultiPort 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 installing 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. 2. When a door sensor or REX input is release from their normal duties for general purpose use, the sensors are automatically deleted from the database. This is done to avoid invalid messages from disconnected inputs. If the input will actually be used, the sensor will need to be added back into the database before it will report. 3. When auxiliary outputs will 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 1 hour, so the time setting in the manual control window will be multiplied by one hour. A scale factor of 1 equals one second, and a scale factor of 60 equals one minute, Currently the minimum allowed momentary unlock time is 7 seconds. NOTE: This feature is currently non-operational, see Known Issues in this release section for more information, 4, 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, €RAM/netEDGE area controllers allow 3 holiday types/special schedules. Only one holiday type is active on any given day on eRAM/netEDGE hardware. 2, MAX 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. Salto SVN hardware allows up to 3 holiday types/special schedules. All 3 holiday types may be active on any given day in the Salto SVN 5. When using Windows Authentication for SQL Server, the MultiPort service must be configured to login using a valid Windows account with access to the SQL Server. NOTE: this is not the default method used to authenticate when using the supplied SQL Server engine, 6. The title bar of the MultiPort Manager application has been changed to "SMS Service Manager", and will show in the Windows Task Manager as such. All other locations still reference MultiPort Manager. 7. When using Alarm Routing, alarm events may be seen at all workstations before the Alarm Routing Delay has passed if a non-routed alarm comes in during the delay period. 8, When using Door or Output groups that span modules, commands to unlock or lock the group from the Desktop Plan window will generate as many commands as there are area controllers for cach area controller, Causing many duplicate commands to be sent, 9, After the system has been registered for the first time, be sure to log out and log back in before adding hardware to the Plan window. 10. When adding panels to the system, the Add Points check box may be used to add basic access control points, it will not add points for an Elevator. Be sure to uncheck the box when adding a panel for Elevator control. 11. Adjusting the time zone or DST setting of the PC while the Desktop is open may cause a "This14, 15 16. 17. 18 19. 20, 21 registration is not valid for this site or the database has been restored or modified!" error message when the Desktop is closed. This is expected behavior, and will only be seen the first time the Desktop is closed following a time zone or DST change. . Area Controllers cannot be added to the system through the Plan Design window, but must be added through the "Configuration" window before panels may be added to the controller. When performing an upgrade on a system that is using badge designs that is a version 5 or earlier, in order to convert the existing badge designs to work with in this version, the selected badge design cannot be read only. Access Level names cannot begin with a 1-9 character, Zero is a valid first digit for the name of an access level. For example "12345 Access Level" is not valid, however "012345 Access Level" is a valid access level name, Systems with mixed hardware platforms (€RAM-BLP, eMAX, PCSC, and Salto SVN) will have items in Configuration screens that do not pertain to all hardware platforms. The following is a partial list. 1, PCSC hardware requires a "secondary expiration" field for badges that will show in the Badge edit screen. The field is not supported on eMAX or SVN hardware. 2, SVN hardware requires a "new key can be cancelled through blacklist" checkbox in the Badge edit screen, eMAX and SVN hardware do not support this function, 3. The Access Levels options for "Activate datetime", "Deactivate datetime", "Escort", and “Escort required" are only supported on eMAX hardware. PCSC and SVN hardware do not support these functions. 4, With SVN hardware, there will be 256 Calendars added to the system named "Calendar000" through "Calendar255". These calendars are only applicable to SVN hardware. 5, The Schedules configuration option for "One Time Events" is only applicable to eRAM- BLP/netEDGE and eMAX hardware. The function is not downloaded to eMAX hardware and requires MutliPort connectivity for schedule changes. 6. The Bulk Add function is not applicable for SVN hardware. When changing the antipassback mode of a system (i.e. none, soft, or hard), all existing cardholders must be forgiven through the "Manual Control" window to prevent antipassback violations. In template design, the badge type "CSN" is not fully implemented and should not be used at this, time. When using Morpho readers with this version of software, the "Morpho_Manager_6.1.2.15092.iso" must be used to install the Morpho Manager application, Other versions of Morpho Manager may not have been tested with this version software, and may cause undesirable results if used. The supported Morpho reader firmwares are included in the Morpho Bio Toolbox application on this ISO image. When using the Remote Point PDA with this version software, the “Remote_Point_6.1.2.15092.iso" must be used to install the Remote Point server software. Other versions of Remote Point may not have been tested with this version software, and may cause undesirable results if used. Dependencies that have an email action will require an email account to send through. The email account SMTP settings must be configured in the Desktop Settings for the system before emails will be sent, The SMTP Server, account name, account password, SMTP port number must all be known and entered in the correct "email" section for "_All Workstations" When enabling or disabling case sensitive user names in operator options, it is important to note that all operator records must be edited and their user names must be tickled so that the record can be saved with the new rules in place. This must be completed before logging out of the Desktop application. Failure to do so will result in failed login attempts and will require the operator to use the lost password procedure.22. The maximum allowed Expiration date for an Access Level is currently "2029-12-31 23:59:59" Any date/time greater than this value will result in cardholders not being granted access using those access levels. Back to top Basic operation, things to know when using eMAX and eRAM/netEDGE hardware 1. When adding an EP1501, the Add Points option will only add door 1 to the EP1501 internal panel. If the 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. 2. The netEDGE configuration tab will not be visible unless the system is registered for netEDGE doors and at least one RAM or netEDGE device is in the database. 3. When using Floor reporting with MAX elevators, accesses that occur while the "Offline" or "Override" schedules are active will be reported as accesses from the elevator reader only, and will not send the floor selected. 4. Before changing the Door Lock Output of an MAX door that is configured with an Alarm Shunt Output, be sure to disable the Alarm Shunt Output and save the door before setting the new door lock output. Then save the door record again before re-enabling the alarm shunt output. 5. If PIN will be used on one or more eMAX doors, and one or more cardholders will not need a PIN, "NONE" should be entered as the PIN for each cardholder which does not need a PIN. 6. Firmware updates to serially connected EP area controllers will take longer to complete than network connected EP area controllers. 7, ¢MAX-MRSle devices may be saved without an IP Address or MAC address. The units will not function until these settings are correctly entered. 8, Changes to the IP and MAC addresses of the eMAX-MRSle require a reset and initialize of the eMAX-EP area controller it is assigned to. 9. After the system has been registered for the first time, be sure to log out and log back in before adding hardware to the Plan window. 10. With Salto SVN doors, the "Audit on Keys" configuration setting is only valid for offline locks. While the setting exists for Control Units and Wireless locks, the feature does not apply to them. 11, When adding panels to the system, the Add Points check box may be used to add basic access control points, it will not add points for an Elevator. Be sure to uncheck the box when adding a panel for Elevator control. 12. Adjusting the time zone or DST setting of the PC while the Desktop is open may cause a "This registration is not valid for this site or the database has been restored or modified!" error message when the Desktop is closed. This is expected behavior, and will only be seen the first time the Desktop is closed following a time zone or DST change. 13. When using Panel Encryption for eMAX panels, the following list is the minimum firmware version required for the MR panels. Versions later than those listed below will support panel encryption. eMAX-MR30 - revision 1.40.3 eMAX-MR32 - revision 1.40.1 eMAX-MRSle - revision 1.2.6 eMAX-MRIGIN - revision 1.31.1 eMAX-MRI60UT - revision 1.31.1 eMAX-MR200 - eneryption not supported 14. When using the Aperio AH30 Mecury Hub 8, the Aperio locks and Aperio Hub 8 firmwares mustbe version 3.0 or greater for manual unlock/lock to function. Additionally the eMAX-EP firmware must be version 1.21.2 or later. Back to top Basic operation, things to know when using Salto SVN hardware 1. There must only be one Salto SVN area controller defined in the database. If multiple Salto SVN area controllers are defined in the database, some features will use the configured values for the first Salto SVN area controller added to the system. NOTE: Currently the system will not prevent the user from adding multiple Salto SVN area controllers to the system. 2. For Salto SVN support, this version of software requires Salto ProAccess Space version 2.0.8.4 or later. Using earlier versions of Salto ProAccess Space or Salto ProAccess RW will produce undesirable results. 3. The Salto SVN hardware line uses an additional communication service. The Salto RW service must be running as well as the MultiPort service in order for the MultiPort to communicate with the Salto SVN hardware. 4, Before Salto SVN hardware may be added to the system, the Salto SVN Interface optional module must be installed, and MultiPort must be restarted. Until this is complete, the hardware will not be visible in the Desktop for selection. 5, When a door sensor or REX input is release from their normal duties for general purpose use, the sensors are automatically deleted from the database. This is done to avoid invalid messages from disconnected inputs. If the input will actually be used, the sensor will need to be added back into the database before it will report. 6. Salto Sallis and Salto SVN GEO cylinder locks may only be paired with one Salto site code or database, Once a Salto GEO cylinder has been paired with a database using the Portable Programming Device, it cannot be moved to another Salto system with another site code. This functionality is by design and unique to the Salto GEO cylinder locks. 7. When a Salto SVN user is deleted, their key becomes blacklisted in the Salto hardware network. If the user reads their badge after they have been deleted, the Salto hardware will return a "Voided card" event with the raw key number for the details. This will only happen on the first read, any subsequent read attempts will return an empty details for the "Voided card" event. 8. The calendar for Salto SVN doors is not currently configurable. All doors will use "Calendar000" at this time. This is a limitation of the Salto SVN protocol. Cardholders may be configured to use any of the available 256 calendars. 9. The address for the Salto SVN interface must be between 1 and 999. Values outside that range will cause unexpected results. 10. With Salto SVN, the "Two-Person rule” open mode is not operational with SVN GEO locks. 11, Salto SVN locks do not support Scheduled Door Group unlock. Manual and Dependency Door Group unlocks are supported by Salto SVN online and wireless online locks. 12. Offline Salto SVN locks may only be unlocked using the PPD or by schedule. 13. Changes to the configuration of the Salto SVN integration will require a reload of the MultiPort service before the changes will take effect. 14, Currently the Salto SVN "Description" fields for "Access Levels", "Schedules", and "Calendars" do not exist. The description fields do exist for "Doors", "Door Groups", and "Automatic Changes". 15. When adding a new Door Group the "Description" field is not sent to the Salto SVN database. To send the description to the Salto SVN database after the record has been added, the description must be entered, and the list of door points must be altered. 16. With Salto SVN the total number of Doors, Door Groups/Zones, and Access Levels that can beassigned to each cardholder is 96. 17. Changes to the Cardholder Enable for a Salto SVN cardholder will require the key to be updated before the change will take effect. 18, With Salto SVN doors, the "Audit on Keys” configuration setting is only valid for offline locks. While the setting exists for Control Units and Wireless locks, the feature does not apply to them. 19. The Schedule day named "Special 3" is "Holiday 2" for Salto SVN hardware in a system with eMAX hardware. 20. Schedules on Salto SVN hardware only Start/End on the even 10 minute interval. I.e. schedules that are set to change state at 15 minutes after the hour will actually change state at 10 minutes afier the hour, and schedule that are set to change state at 45 minutes after the hour will actually change stat at 40 minutes after the hour. Back to top Basic operation, things to know when using PCSC hardware. 1. After adding an FTC, 1Q, or SIM area controller to the system, be sure to send an “Initialize Area Controller" command through the MultiPort Manager, and once the initialization has completed, send the "Reset Area Controller" command to pair the unit to the database 2. Performing a hard reset of an IQ or SIM panel that has been connected to a MultiPort 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. 3. Configuring a DDM, IQ, 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. 5. 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 4. Changes to the Invert setting of an input sensor on a FTC/DDM/SDM , IQ, or SIM must be made with supervision mode disabled. 5. 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 state. 2. Configure the input sensor invert setting as desired. 3. 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. 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. Wait for the indicator LEDs on the DDM/SDM, IQ, or SIM to change.