What's New in Doors.NET v6.0.0

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

Doors.NET v6.0.0 Software - 02635-016

Operating System Compatibility

Doors.NET series 6 software IS COMPATIBLE with:

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

All other operating systems are NOT SUPPORTED.

Microsoft .NET Framework Notes

• Doors.NET v6.0.0 and higher uses .NET Framework v4.8.1
• Doors.NET v4.8.0 to v5.4.0 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.
• 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 has now Ended

The PXL and Entraguard controller types are not supported with this version of
Doors.NET (v6.0.0) and future versions. Ongoing support and development for
these products will be in Borealis. Doors.NET v5.4.0.8 was the last version of
Doors.NET that supported PXL and Entraguard controllers.

The Doors.NET v6.0.0 installer will check the database for a PXL gateway. If one exists
locally then the software installation will not proceed. If there is a PXL gateway installed
and running on a remote PC, the installer will prompt you to stop the gateway service
and the PXL gateway will be removed during the software installation/update.

New Features

Aperio Gen 5 AH30 Devices

• Added support Aperio Generation 5 AH30 communication hubs (Mercury MP
  controllers only).
  

Aperio DL100 Support Added for All Aperio Hubs

• Support has been added for the Aperio DL100 wireless deadlatch and card reader. This device is now supported on all Aperio hubs.

Doors.NET Improvements

• Corrected an issue where a reader could continue beeping if a door secured
  event occurred at exactly the same time as a door-held open event. This has
  been corrected by implementing a 1 second delay for the beeper following
  the door secure event.
• If using Mercury 'downstream devices' (MR52, MR16IN, MR16OUT, etc), with
  non-Keri OEM codes, the Doors.NET license needs to be modified to support
  'Non-Keri Mercury Security Hardware'. This license setting will also allow
  you to use EP, LP and MP-series SPM controllers which have non-Keri OEM codes. Please contact Keri Systems inside sales for updating your Doors.NET license.
• Added a notification that PXL controllers are no longer supported if an attempt is made to configure a PXL gateway via the License Manager.
• Added two additional Local Linkage triggers for strike activate and de-activate. These triggers require Filter Door Change of State to be off in the advanced reader settings.
• Added an additional Local Linkage event for Door Held-Open Pre-Alarm Cancel.
• Corrected a issue where certain Local Linkage trigger selections were not being retained when toggling between different Local Linkage triggers.
• Modified the Local Linkage Procedure setup form for Reader Temporary LED
  Control to state that the Repeat setting is exclusive to LED control.
• Removed the Serial communication method in the MP controller network device properties as this method is not supported on this controller type.
• Increased the count for the maximum number of locksets (16) that can be added to an Aperio AH30 Gen 5 communication hub.
• Corrected a typo for the Adams Right E-Force button when adding to an Aperio AH40.

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

For Neutron:

• Neutron Controller - 1.00.19
• Neutron Bootloader - 1.00.08

For Mercury MP Hardware:

• MP Controller - v2.50.

For Mercury LP Hardware:

• LP Controller - v1.31.0 (new revision - see information below).

For Mercury EP Hardware:

• EP Controller - v1.291 or v1.297 for EP4502.

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