Doors.NET v5.0.0 Release Notes

Doors.NET v5.0.0 Release Notes

Doors.NET v5.0.0 Release Notes

Doors.NET Release Notes - 01298-011 Rev. A

Doors.NET v5.0.0 Software - 02635-011

 

Operating System Compatibility

Doors.NET software IS COMPATIBLE with:

  • Windows 8.1
  • Windows 10 - all versions
  • Windows Server 2012 and 2012 R2
  • Windows Server 2016
  • Windows Server 2019

All other operating systems are NOT SUPPORTED.

 

Microsoft .NET Framework Notes

  • Beginning with v4.8.0, Doors.NET uses .NET Framework v4.8.
  • If your PC does not already have .NET Framework v4.8 installed, the Doors.NET installer will stop and prompt you to install it.
  • All supported operating systems are compatible with Microsoft.NET Framework v4.6.2 or greater.
  • PhotoID Badging requires .NET Framework v3.5. If you are running the Microsoft Server 2019 operating system, you must install .NET Framework v3.5 prior to installing Doors.NET software, or else the PhotoID installation will fail. This is done via Server Manager > Manage > Add Roles and Features > Install .NET Framework v3.5.

 

SQL Server Compatibility

If SQL is ALREADY INSTALLED on your computer:

  • The Doors.NET installer will poll the host computer and use the SQL version that is already installed.
  • This is true for both new Doors.NET installations and for Doors.NET upgrades.

If SQL is NOT INSTALLED on your computer:

 

64-bit computers using Windows 10, Windows Server 2016, or Windows Server 2019:

  • SQL Server 2019 Express will be installed if SQL server is not already present.

64-bit computers using Windows Server 2012 or 2012 R2:

  • You must manually install Microsoft SQL Server Express 2016 or 2017 if SQL server is not already present.

Link to Microsoft's SQL Server Express 2016 SP1 download page:

https://www.microsoft.com/en-us/download/confirmation.aspx?id=54276

 

Link to Microsoft's SQL Server Express 2017 download page:

https://www.microsoft.com/en-us/download/confirmation.aspx?id=55994

 

32-bit computers:

  • You must manually install the SQL revision appropriate for your operating system.
  • Keri recommends installing SQL Server 2014 (the last SQL Server supporting 32-bit computers).

Link to Microsoft's SQL Server Express 2014 download page:

https://www.microsoft.com/en-us/download/details.aspx?id=42299

 

Please Note

  • Doors.NET software installation will not begin if a Windows Update is in progress or a computer restart is pending due to a Windows Update. Make sure all Windows Updates have been completed prior to installing Doors.NET.

Support for PXL and Entraguard Modem Communication Has Ended

Doors.NET v4.8.0 was the last software revision that will support modem communication for PXL and Entraguard products.

Modem communication for PXL and Entraguard units IS NOT SUPPORTED beginning with Doors.NET v4.9.0.

Installers are notified of this change when selecting an Upgrade Installation in the Doors.NET installation program. Systems that have existing modem communication with controllers can continue to use modem communication using the existing configuration information. The Advanced View option will continue to display this information. Any new controllers added to an existing system must be added using either a serial connection or a LAN network connection. Should someone attempt to select modem communications a popup message box appears stating modem communication is no longer supported. Further, should someone change an existing communication path from modem to serial or network that change is made permanent and there is no reverting to modem communication.

 

This change was made due to the rapid conversion by telecommunication providers from POTS lines, which are completely modem compatible, to VOIP lines, which do not transfer data packets reliably and have differences that vary from vendor to vendor, making it impossible for us to ensure modem compatibility with all VOIP vendors and the VOIP hardware they use.

 

You can switch from modem communications to either of the following communication methods:

 

For Data Communication with Either PXL or Entraguard Units

  • Keri recommends replacing your modems with a LAN-520 Ethernet module.
  • Alternatively, if your computer has a serial communication port, you can use a direct-connection cable.

For Voice Communication with Entraguard Units

  • You will need a VOIP converter for voice calling between Entraguard units and tenants.
  • Keri recommends the Cisco SPA 112 VOIP Adapter, however your ISP likely has their preferred unit.

 

 

New Features

Video Plug-n-Play Replacing Reflections

Keri has ended support for its Reflections video program, replacing it with a new Video Plug-and-Play platform that provides integrated access to multiple video platforms. Keri’s optional video license is required to access this feature. Video licensing also requires a count of the number of cameras to be supported by the system.

The same feature set that was in Reflections is supported in the new Video Plug-and-Play platform. However, the camera options themselves will be managed by the video software itself.

The Reflections video program will be removed from the current Doors.NET installation should it be detected during a Doors.NET software upgrade process to ensure there is no video platform confusion for the end user.

 

Keri currently has video plugins for the following vendors:

  • Axis
  • Axxon
  • Digital Watchdog
  • Exacq
  • Hanwha
  • OpenEye
  • Milestone

 

Development is under way to add several other video software vendors.

 

Doors.NET Software Installation Improvements

  • Slow Installation Times - Improvements have been made to the Doors.NET software installation process to inform installers of possible slow installation times due to underspec PCs and mechanical hard disc drive (HDD) limitations. And to address potential installation issues caused by antivirus software already installed on the host PC. Keri has found that slow software installation times are typically due to the processing time required for installing the online help file set. Underspec PCs and HDDs take a long time to unarchive the online help file set and then copy the file set to the HDD, possibly adding an hour or more to the software installation time. The following changes have been made to inform the installer of the possible time issue and to allow for software installation without the online help file set.

    - The installation program will now check the PC’s hardware specifications and provide a “Low Performance PC” warning message should the host PC’s specifications imply a slow installation time is likely.

    - The installation program now provides the ability to skip the online help installation to save installation time.

    - The software installation AutoRun menu now has a stand alone, online help installation option.


  • Addressing Anti-Virus Software - Keri is continually working to be acknowledged as valid software with anti-virus software programs, but it can be difficult to keep up given the large number of anti-virus vendors and their continual security updates. To minimize installation issues, when the installation program is started a prompt appears asking the installer to disable the PC’s anti-virus software during Door.NET Installation. This prompt requires acknowledgment before continuing and it provides a link to supporting documentation on Keri’s knowledge base should the installer have questions on how to perform this task. In most cases, this step allows for a successful installation.

  • Updating Mercury Hardware from Series 2 (EP) to Series 3 (LP) - Doors.NET has added the ability to upgrade Mercury Series 2 EP hardware to Series 3 LP hardware using the same configuration parameters resulting in a seamless hardware upgrade without having to reconfigure any of the controllers or their peripherals, saving the installer time and minimizing the possibility of configuration errors. A warning message is displayed should the new LP controller type not match the previous EP controller type.

 

Doors.NET Improvements

  • Changed the Mercury MR62E reader default setting from a generic reader to an OSDP reader.
  • Added a cardholder search filter for cardholders without an Access Group assignment.

  • Added a check to prevent an operator from deleting the last System Administrator account. There must always be at least one System Administrator.

  • Restricted card plus PIN configuration options to lock sets on the same gateway.

  • Corrected a Hardware ribbon display issue for Auto Unlock Suspend and Restore.

  • Added REX property “Disable During This Schedule” to the standard Doors.NET hardware configuration grid. Previously this feature was only available to Doors.NET Pro installations.

  • Corrected an Elevator Control Floor Select alignment issue between inputs and outputs when using NXT-MSC 2-door controllers.

  • Edited the Elevator Control Floor Select Status and Override Schedule descriptions for live events to be more descriptive of event state.

  • Added OSDP reader descriptions to the reader configuration pull-down menu. These will only be displayed if the controller type supports OSDP readers.

  • Corrected an issue on NXT-MSC controllers with MR16IN boards. When using Elevator Control, if you changed an elevator reader from “Reader with Feedback” to “Reader without Feedback” you would be prevented from changing the reader function on any other NXT-MSC controller with MR16IN boards.

  • Corrected a bit mapping issue on credentials using the HID Corporate 48-bit and Corporate 35-Bit formats.

  • Expanded support for new Wiegand Control Flags per the current Mercury SDK specification.

  • Corrected a grid refresh issue when displaying SimonsVoss lock set Chip IDs on imported devices.

  • Changed cardholder download management when implementing the Download On First Use option to maintain existing cardholders in controller databases.

  • Restored the LED/Buzzer configuration settings for OSDP readers on NXT-MSC controllers. These configuration settings are shown under Advanced Properties.

  • Added a configuration check to disallow the addition of other peripherals to a controller bus with OSDP readers. Using an OSDP reader consumes all of the resources of that controller bus.

  • Added a digital signature to the EclipseServer.exe program to prevent it from being flagged by certain anti-virus software, allowing installation without installer intervention.

  • Corrected a timing issue when enrolling multiple controllers simultaneously to ensure proper enrollment of all controllers.

  • Corrected a licensing issue that prevented the System Calendar from being displayed.

  • Corrected a control point variable issue that prevented execution if no time value was set.

  • Updated a software installation warning window to be more descriptive of the reason for the warning.

  • Corrected a typographical error in the SimonsVoss, Smartingo Import Wizard window.

  • Corrected an issue that prevented the System Calendar feature from being displayed when using a distribution license. The System Calendar feature is a purchasable option and is displayed as part of the Advanced View menu options when enabled.

  • Corrected a grid display issue for LP1501 controllers when changing an Input to a Monitor Point that resulted in the display of the Circuit Type Line Supervision option. This option is not relevant to Monitor Point configuration.

  • Corrected a grid display issue with LP1501/1502/4502 controllers that prevented a Link Schedule from being assigned to onboard MR50s/52s.

  • Corrected a grid display issue with LP1501/1502/4502 controllers using MR16in boards for Elevator Control that prevented Elevator Feedback assignment from being changed.

  • Corrected inconsistencies with NXT reader LED and beeper responses when both an entrance and an exit reader are attached.

 

Improvements to Both Doors.NET and Visual Doors

  • Corrected an event reporting issue when manually adding a new PXL controller to an existing system. When a new controller came online an update network command began and an Update Network event was posted. When the update finished the "Update Complete" message appeared but the notice for "Update Network Required" was still active.

 

Visual Doors Improvements

  • Corrected a display issue that could cause the program to crash when loading the cardholder database.
  • Corrected a timing issue when enrolling multiple controllers simultaneously to ensure proper enrollment of all controllers.

  • Changed the message displayed when auto-detecting PXL secondary controllers to correctly identify the task.

  • Implemented a check when setting a credential expiration date to not allow an expiration date that is earlier than the activation date. In this case, the expiration date will be changed to match the activation date.

  • Corrected a grid refresh issue. When changing credential activation and expiration dates on the cardholder grid, these changes were not being updated on the general information grid.

  • Corrected a grid refresh issue when changing the configuration of multiple monitor points on 4x4s simultaneously. Not all changes were correctly reflected on the grid.

 

Mercury Firmware v1.294

  • Corrected a problem specific to NXT-MSC controllers when issuing pulse commands to MR16OUT and GIOX units. Changing the pulse command from the default of 5 seconds to any other value would cause the output to continuously stay active when pulsed.

 

Mercury LP Controller Firmware v1.30.0

  • I408 - Corrected an issue with LP1502 controllers that caused a slowly increasing delay between card presentation and strike relay energizing.

 

Current Firmware Revisions

For NXT Hardware:

  • NXT-MSC Controller - v1.294
  • Standard NXT Controller - 2.05.80
  • NXT Controller Bootloader - 2.00.01
  • NXT Reader - 4.00.03
  • Standard and WIPLUS Reader Interface Modules (RIMs) - 3.03.21
  • Wiegand-Only Reader Interface Modules (now obsolete - replaced by the WIPLUS)
    • 3.03.21 provides single-line LED support for Wiegand-Only RIMs
    • 3.03.10 provides dual-line LED support for Wiegand-Only RIMs
  • 4x4 I/O Module - 3.00.03
  • GIOX Motherboard - 1.00.21
  • GIOX Input Module - 1.00.10
  • GIOX Output Module - 1.00.10

 

For PXL:

  • Standard PXL Controller - 8.6.09
  • Legacy PXL Controller - 8.5.22 (requires a Legacy license for operation)

 

For Entraguard:

  • Standard Titanium and Silver - 7.8.02
  • Standard Platinum - 9.2.02
  • Legacy Titanium and Silver - 7.6.13 (requires a Legacy license for operation)
  • Legacy Platinum - 9.1.09 (requires a Legacy license for operation)

 

For Neutron:

  • Neutron Controller - 1.00.19
  • Neutron Bootloader - 1.00.08

 

For Mercury LP Hardware:

  • LP Controller - 1.296 (new revision - see information below)

 

For Mercury EP Hardware:

  • EP Controller - 1.291

 

Firmware Improvements

Mercury LP Controller Firmware v1.296

  • Corrected an issue with delayed relay reaction to card presentation on LP1502 controllers.

 

Mercury Firmware v1.294

  • Corrected a problem specific to NXT-MSC controllers when issuing pulse commands to MR16OUT and GIOX units

    • Related Articles

    • Doors.NET v4.9.0 Release Notes

      Doors.NET Release Notes - 01298-010 Rev. A Doors.NET v4.9.0 Software - 02635-010 Operating System Compatibility Doors.NET software IS COMPATIBLE with: Windows 8.1 Windows 10 - all versions Windows Server 2012 and 2012 R2 Windows Server 2016 Windows ...
    • Doors.NET v4.8.0 Release Notes

      Operating System Compatibility Doors.NET software IS COMPATIBLE with: (both 32-bit and 64-bit where applicable) Windows 8.1 Windows 10 - all versions Windows Server 2012 and 2012 R2 Windows Server 2016 Windows Server 2019 All other operating systems ...
    • Doors.NET v3.5.1.20 Release Notes

      Please read this document. It contains a summary of the latest information regarding this software release. Doors.NET v3.5.1.20 replaces previous release v3.5.1.19 SP1. NOTE: The Ingersoll/Rand reader line has been spun off into its own company. This ...
    • Doors.NET v3.5.1.22 SP1 Release Notes

      Operating System Compatibility Beginning with v3.5.1.22, Doors.NET software is NO LONGER COMPATIBLE with any version of Windows XP.   Doors.NET software IS NOT compatible with the Home/Basic version of Windows Vista and Windows 7. This is due to ...
    • Doors.NET Software Release Notes History

      Release dates for every revision of Doors.NET. Click on the specific revision to jump to the individual software release information page.   Revision Release Date 4.8.0 November 13th 2020 4.4.0 August 10th 2020 4.3.7 February 25th 2020 4.3.6 ...