What's New in Doors.NET v5.4.0

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

Doors.NET v5.4.0 Software - 02635-015

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.

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).

SQL Server Express Download Instructions

To download SQL Server Express, visit the official Microsoft website and search for either:
- 'SQL Server Express 2019 download'.
- 'SQL Server Express 2017 download'.
- 'SQL Server Express 2016 download'.
- or 'SQL Server Express 2014 download' (for a supported 32-bit operating system).

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 will be Ending Soon

Doors.NET support for the PXL and Entraguard controller types will be ending soon. 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

Mercury MP Controller Support

• Added support for Mercury's new MP range of controllers. The MP controllers, as you would expect from Mercury, feature unmatched cybersecurity features, including ARM TrustZone, secure boot CPU and latest crypto and robust and reliable components. They are fully backwards compatible with Mercury's EP and LP range of controllers.

Notes:
- Mercury EP controllers are now considered an 'obsolete' product but can still be used in Doors.NET.
- Mercury MP controllers are fully interchangeable and backwards compatible with LP and EP controllers.

Temporary Upgrade Settings

• Cardholder Temporary Upgrade Settings is now enabled. This feature allows you to temporarily change the assigned access rights of a cardholder. This feature is supported on NXT-MSC and Authentic Mercury controller types.

Doors.NET Improvements

• Corrected an issue with Photo ID when using a dynamic custom field - the field was not allowing conditional display text.
• Diagnostic logging has been increased in the PXL/Entraguard Gateway.
• Improved security posture for customers using AWS cloud backup option.
• Corrected a display issue in Local Linkage procedures when using AntiPassback Free Pass for a specific area. The selected area was not being retained after leaving the page.
• Corrected a minor typo on the PXL update required notification.
• Corrected an issue with MP controllers where the controller's IPV6 address would initially display on the Scan page if the controller had been down-powered for an extended period of time.
• Resolved an issue with the Professional Report Client that was generating an error for all cardholder type reports.
• Replaced the Teamviewer Quick Remote support utility with an alternative application, named ZOHO Assist.
• Updated the RS-485 port descriptions for MP controllers to match what is stated in the installation guides.
• Set the default reply time on the controller port to 90ms if an MP controller is added to the port.
• Resolved a communication issue with an MP2500 when using an address other than a default assigned address of 0.
• Corrected an issue when configuring Primary/Secondary reader linking on an MR52 or MR50 module. The secondary reader was not being automatically configured in the user interface as a Secondary reader.
• Corrected an issue with the LP4502 controller where it was not possible to add a dormakaba Wi-Q gateway.
• Prevented the Mutual TLS data security option on NXT-MSC and EP controllers as this setting is only supported on Mercury LP and MP controllers.
• Corrected an issue where performing an auto-config, using an Entraguard primary controller, would cause the LCD screen to continuously display an update in progress message. The workaround was to perform a full update on the Entraguard Primary.
• Corrected an issue with Transaction Reports where a specified date range was not saving correctly (such a saving a report for All Events during the past 3 days).
• Corrected an issue with the 'Work Hours' reports. It was not possible to save this type of Transaction Report.
• Resolved a display issue in Global Linkage setup where the linkage macro name was not always being saved correctly.
• Corrected an issue where controller settings could not be imported (applying a controller template), for certain controller types and hardware configurations.
• Corrected an access issue where a 'Never Expire' cardholder was getting: Access Denied - After Expiration Date if a controller was deleted and then re-added. The workaround was to download cardholders again.
• Corrected as issue where it was not possible to add an Allegion gateway if the RS-485 address was 254. This is now seen as a valid network address.
• Corrected an issue where the Doors.NET License Manager was not detecting SQL Server 2022 and Management Studio 22 as supported SQL components.

• Corrected an issue where some cardholders would be missing from Cardholders >> All Report (on very large databases).

• Corrected an issue where cardholders would get 'Access Denied - Expired' for a Doors32 conversion where the controller type was replaced with NXT-MSC controllers.

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.296
• 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.31.0 (new revision - see information below).

For Mercury EP Hardware:

• EP Controller - v1.291

Firmware Improvements

• None at this time.

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.
• MP1501 controller does not currently support downstream devices, such as the MR52 or MR16 modules.
• Allegion Schlage, such as the ENGAGE, PIM-400 or AD-300 devices do not stay online when connected to MP series controllers
• Constant online/offline events are generated when an Aperio AH40 is connected. This happens when TLS is enabled at the AH40 hub on MP controllers only.
• There is an issue when using Aperio Legacy AH30 on MP controllers where the legacy mode settings are not being correctly retrieved.
• There is an issue with MP controllers not loading peer certificates correctly.
• There is an issue with MP controllers not migrating peer certificates correctly.
• It is not currently possible to configure an MP4502 controller for Dormakaba or Destination Dispatch.

Click here for the software release history.