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

Doors.NET v5.2.0 Software - 02635-013

Operating System Compatibility

Doors.NET series 5 software IS COMPATIBLE with:

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

All other operating systems are NOT SUPPORTED.

Microsoft .NET Framework Notes

• Doors.NET v4.8.0 and higher 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 has Ended

Doors.NET v5.2.0 is the last software revision that supports the PXL and Entraguard controller types. Ongoing support and development for these products will be in Borealis.

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.

Note: Please keep in mind, if you are using modems for Entraguard and controller communication, Doors.NET v4.8.0 is the last version that fully supports modem communication.

New Features

Prompt to Change Admin Password

Prompt to change the default admin password (for a new system or when the password has not been changed for a specific number of days). Default duration is 90 days. You will be prompted when logging into a new system or when the specified number of days has passed since the last admin password change.

Hardware Setup Changes for Wireless Locks

There is a slight change in setting up network hubs for certain wireless locks (for example, Simons Voss Gateways or Aperio AH-40 network hubs). From v5.2.0 and onwards, the network hub/gateway node is added to the hardware tree as a Network Device. This change improves the setup workflow of wireless lock integration with NXT-MSC and Mercury controllers. Although a controller is still required for the integration, this change also allows for all of the controller buses to be used for general access control.

Setup Changes for Mercury Hardware

Downstream hardware is under each TB node instead of directly off the controller. This is now consistent with how the hardware is displayed for NXT and NXT-MSC in the previous Doors.NET version (v5.1). TB names change to reflect the actual name on the MSC controller. The baud rate setting for the downstream devices is also set at the TB/Bus port (instead of on the controller). Each TB port can have a different baud rate setting. The ribbon bar icons now display the icons relative to the protocol enabled on the bus.

Setup Changes for NXT-MSC Controllers

NXT-MSC controllers still support the same wireless locks as before but how the locks are supported has changed. In Doors.NET v5.1 only 1 PIM or ENGAGE gateway was allowed per bus. In v5.2 you can have multiple devices per bus up to a maximum of 8. AD-300 locks previously required a dedicated bus but now they can be on the same bus as as a PIM or ENGAGE gateway. In addition, previously the address of the device needed to match the bus that the device was connected to. Now the address of the device in the software now matches how the device is addressed in the field.

Expanded Support for Allegion Locksets

Doors.NET v5.2.0 has added wireless lock support to Mercury Security EP and LP. Doors.NET v5.1.0 only provided wireless lock integration when using the NXT-MSC controller type. Wireless support on the NXT-MSC controllers is also modified to increase

capacity and to be more consistent when adding wireless locks across NXT-MSC ,EP and LP controllers. Wireless locks that were previously only available on NXT-MSC are now available on MSC EP and LP hardware.

Expanded Support for Simons Voss Locksets

SimonsVoss locks are now supported with 'Real Mercury' hardware (EP and LP controller types) as well as the standard integration using NXT-MSC controllers.SimonsVoss controllers in 5.1 required removing all devices from a bus and adding the 1 SV gateway node. In 5.2, these are under the Network Devices node and therefore the devices/peripherals on the bus can remain - allowing the remaining buses to be optionally used for general access control.

Expanded Support for the Aperio Lock sets and the AH40 hub

Added support for AH30 hubs when using EP and LP controller types and support for the AH-40 hub when using Mercury's LP controller types

Expanded Support for OSDP readers

Added expanded support for OSDP Exit readers when using Mercury's EP or LP controller types.

Added Alternate Reader for Elevator Control

Added support for an NXT Exit reader when setting up and using Elevator Control with NXT-MSC controllers. Presenting a credential at either reader (original cab reader or the Exit reader) will be processed as if the card presentation was at the original cab reader. This will allow for a second reader to be installed and used on the opposite side of the cab, for added convenience.

Doors.NET Improvements

• Added a value check when enrolling an Entraguard user that ensures that the Entraguard ID and Directory Code numbers are independently unique. There should be no duplication of either of these numbers.

• Added the ability to generate a random Entraguard ID number when enrolling a new Entraguard user.

• Changed the default sort order in Destination Dispatch for the floor description list. Floors are now listed in ascending order from lowest floor to highest floor.

• Added a verification prompt when removing a DEC Collection from a Mercury controller configured for Destination Dispatch. This requires an operator to confirm the task to prevent the need for a restoration operation should the DEC Collection not have been deleted.

• Corrected the tabbing order when stepping through the creation of a new Wiegand credential type.

• Corrected an issue where the System Calendar was incorrectly applying Pulse Times to 4x4 I/O modules.

• Corrected the message displayed when an OSDP Reader Tamper event occurs.

• Corrected how the PXL Gateway handles errors that occur when power to the controller is restored following a power outage and when data comms are lost with the PXL primary controller.

• Corrected an LDAP cardholder data mapping error with activation date and access group not being set correctly.
• Increased the timeout setting when retrieving data with the LDAP Import/Sync service to optimize performance with large databases.

• Added checks to not allow Primary or Secondary OSDP Reader types to be changed from the OSDP reader configuration if the readers are paired.

• Added checks to ensure that each reader has a unique address if there are multiple OSDP readers on one port.

• Corrected a setting in the 56-bit MIFARE CSN format so that the suppress facility code option is now selected by default.
• Modified the properties of NDE and LE locks to prevent the manufacturer model from being changed.
• Corrected an internal configuration error with the Mercury LP4502. Under certain circumstances the NIC1 DNS IP address was displaying reversed.
• Corrected an issue with the NXT-MSC Internal Config settings where the APPLY & REBOOT wasn't displaying after changing web configuration, autosave or card database size settings.
• Corrected an issue where the door contact line supervision settings were not displaying for readers connected to Mercury EP or LP controllers.
• Added vendor information for various new OSDP manufacturer models.
• Corrected a display issue where a second NIC option was incorrectly being displayed for an EP1502 controller (which has only one NIC).
• Corrected a display issue with an LP1502 reader settings - where the default online mode was set to Card Or PIN instead of Lock.
• Added a notification of the increased security risk if a reader's default online mode is changed to Facility Code.
• Corrected an issue with an LP4502 where the default comm address value for the first device added to TB3 would be 0 instead of 1.
• Added an auto-unlock suspend notification to advise the user that the unlock schedule will remain inactive until manually restored and if using Standard NXT, if the door is auto-unlocked, the door will need to be manually locked following the AUL Suspend (it is a 2-step process).
• Correct a SimonsVoss Gateway communication issue. The MSC gateway no longer needs to be restarted if the Gateway's Wavenet address is changed.
• Resolved an issue where an incorrect hardware mapping notification would sometimes appear when enabling the door contact on an NXT-MSC controller.
• Corrected an issue where individual readers added to the Allegion Gateway were not automatically added to Total Access.
• Corrected a display issue where PXL and Entraguard inputs and output list where not displaying until the hardware tree was re-opened.
• Resolved a display issue where the onboard MR52 was not displaying for a newly added EP4502 until the hardware screen was re-opened.
• Improved the time it takes to load a very large cardholder database (300,000 or more cardholders).
• Corrected an issue where a database of more than 10,000 cardholders would not always return the full list of cardholders.
• Corrected an issue where when viewing Cardholders, a viewer could see the same cardholder record reported multiple times.
• Corrected an issue where Entraguard users without credentials were only being sent to Entraguard units during a Total Update. Entraguard users without credentials should also be sent to units during Smart Updates.
• A security risk prompt is now generated if the Default Online Reader Mode is set to Facility Code only (for readers that support this setting).
• Corrected an issue when remapping I/O between two buses where the remapped assignments were not always accepted.
• Keri M series reader individual manufacturer model names have been changed to drop the NXT reference.

Improvements to Both Doors.NET and Visual Doors

• None at this time.

Telepathy Improvements

• None at this time.

Visual Doors Improvements

• None at this time.

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 - v1.30.5 (new revision - see information below).

For Mercury EP Hardware:

• EP Controller - v1.291

Firmware Improvements

Mercury LP Controller Firmware v1.30.5

• Resolved an issue where web users were not being properly logged out

• Resolved an issue downloading the Syslog

• Resolved an issue where the GMT Offset was not being set appropriately

• Resolved an issue where a controller loses its GMT offset and operates with incorrect time after a firmware update

• Added support for new Wiznet PHY

• Resolved DHCP not sending out new DHCP Request/Discovery when link goes from down to up

• Removed weak DH 1024 key exchange algorithm

• Resolved a memory leak in controller when IP Client reconnecting over and over

• Resolved an issue with Web Config Timeout Redirect Page

• Resolved where a crash was causing a 500 Internal server error on webpages

• Resolved a level 3 web user permission issue

• Resolved an issue where Webpage common password popup was reporting incorrectly.

• Resolved a web user editing issue

• OSDP keys failing to delete on a bulk erase

• Host Grant Bypass: Inconsistent timeout behavior when host is not connected to controller

• Control Point not deactivating and contradicting the transaction report

• Control Point activity not generating transactions

• New crypto chip support

• Cross-Site Scripting vulnerability

• Inability to create web users

• Potential injection vulnerability

• Potential condition where web users can be deleted

• Applying network settings refreshes page and shows default settings

Known Issues

• AH40 Remains offline after completing a firmware upgrade to the controller and a controller reset is required to bring the AH40 back online. Applies to Mercury LP controller only.

Click here for the software release history.