Release notes for version 6.1.3.16193 Release date: July 1th, 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 file. 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. For details on how to register this software, search on Registration in the on-line help afer installation. Ifthe 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.microsoft.com/kb/2032911 New features in this release (6.1.3) 1, Supported Windows Operating Systems: 1. Windows 7 (x86, x64) Windows Server 2008 (x86, x64) Windows Server 2008 R2 (x64) Windows 8 (86, x64) Windows Server 2012 (x86,x64) Windows 10 (86, x64) 2. Supported SQL Server Database Engines: 1, SQL Server 2005: Express, Standard, Enterprise (86, 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 SP1 Express edition (x86). The version that will be installed automatically will depend on the operating system of the computer where SQL Server will 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 systems. NOTE: the x86 version of SQL Server Express will install on both x86 and x64 versions of Windows. aAwaALL 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_ 4, Improved MultiPort service startup process. 5. Improved MultiPort service linking process. 6. Improved email dependency operation. 7 8 Resolved issue with Alarm Notes display. Resolved issue with creating custom capture types. 9. 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 e€MAX-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, Resolved issue with upgrading to 6.1.3.16146. 24, Added new command line database restore process and instructions to "Backups" folder on network installation path. 25, Miscellaneous bug fixes. 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 cither CRAM or eMAX area controllers either before, or during the upgrade process. If the RAMM area controllers are changed to MAX area controllers, then the BLPs must also be converted to MAX-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. Ifthe 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 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. 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, 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. 5. This version of the software 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. 6. This version of the software includes an updated firewall rules package for the eRAM and netEDGE area controllers, All RAM and netEDGE area controllers that will communicate with this software should be updated with the included firewall rules. 7. 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 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 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. 2. After upgrading the workstation that was previously the AXxess Server, custom files that have been added in the setver 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. 4, This version of the software is designed to use firmware version 07-2054 or later in the BarLock Panels when connected to RAM area controllers. See Known Issues when using older versions. 5. 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. 6. 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. 7. 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 resulls. 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. 2. 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. 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 install Computer Name: 4. 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. 5, Ifthe 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 concem, the shared folder may be set for read-only privileges or it may even be unshared after all the workstations have been 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. Please refer to the windows help, if necessat Network installation shared path: 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, 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10. ul 12. 13. 14, 15. 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. 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 RAM/netEDGE hardware, 2. eMAX arca controllers allow up to 8 holiday types/sp. 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 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. 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. al schedules. All 8 holiday types may be . 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. 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 each area controller. Causing many duplicate commands to be sent. . 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. 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. 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. 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 (ERAM-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 MAX or SVN hardware. 2, SVN hardware requires a "new key can be cancelled through blacklist” checkbox in the Badge e een, €MAX 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 MAX 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. 16, 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. 17. In template design, the badge type "CSN" is not fully implemented and should not be used at this time. 18. 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. 19, When using the Remote Point PDA with this version software, the "Remote_Point_6.1.2.1509: 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. 20, 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". 21. When enabling or disabling ease 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 unle: at least one RAM or netEDGE device is in the database. . When using Floor reporting with eMAX 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 eMAX 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 MAX 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. ‘irmware updates to serially connected EP area controllers will take longer to complete than network connected EP area controllers. 7. MAX-MR5le 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 the system is registered for netEDGE doors and