Doors.NET Release Notes - 01298-013 Rev. A
Doors.NET v5.2.0 Software - 02635-013
Doors.NET series 5 software IS COMPATIBLE with:
All other operating systems are NOT SUPPORTED.
If SQL is ALREADY INSTALLED on your computer:
If SQL is NOT INSTALLED on your computer:
64-bit computers using Windows 10, Windows Server 2016, or Windows Server 2019:
64-bit computers using Windows Server 2012 or 2012 R2:
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:
Link to Microsoft's SQL Server Express 2014 download page:
https://www.microsoft.com/en-us/download/details.aspx?id=42299
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.
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
For Voice Communication with Entraguard Units
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.
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.
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.
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.
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.
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.
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.
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
Added expanded support for OSDP Exit readers when using Mercury's EP or LP controller types.
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.
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 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.
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.
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
Click here for the software release history.