{"id":29419,"date":"2023-04-14T10:49:19","date_gmt":"2023-04-14T10:49:19","guid":{"rendered":"https:\/\/kerisys.com\/?p=29419"},"modified":"2023-05-10T11:27:38","modified_gmt":"2023-05-10T11:27:38","slug":"doors-net-5-2-0-is-here","status":"publish","type":"post","link":"https:\/\/kerisys.com\/2023\/04\/14\/doors-net-5-2-0-is-here\/","title":{"rendered":"Doors.NET 5.2.0 Is Here!"},"content":{"rendered":"

Doors.NET v5.2.0 is here and packed with plenty of new features that enhance the installation speed and flexibility of the solutions you can offer, with a vast array of changes to extended product support, seamless installation, and increased functionality.<\/span>
\n<\/span><\/p>\n

The latest software versions are always recommended to our customers as soon as they become available, as they may include critical security patches and fixes for your access control solution, which serves as your first line of defense, as well as enhanced functionality.<\/span><\/p>\n

How has Doors.NET improved?<\/strong><\/p>\n

Prompt To Change Admin Password<\/strong> – 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). The 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.<\/span><\/p>\n

\"Doors.NET<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Hardware Setup Changes for Wireless Locks <\/b>– T<\/span>here is a slight change in setting up network hubs for certain wireless locks (for example, Simons Voss Gateways or Aperio AH-40 network hubs).\u00a0<\/span><\/p>\n

\"Doors.NET<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Setup Changes for Mercury Hardware <\/b>– <\/span>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).<\/span><\/p>\n

\"Doors.NET<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Setup Changes for NXT-MSC Controllers <\/b>– <\/span>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 a PIM or ENGAGE gateway.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Expanded Support for Allegion Locksets <\/b>– 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.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Expanded Support for SimonsVoss Locksets <\/b>– <\/span>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.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Expanded Support for the Aperio Lock sets and the AH40 hub <\/b>– <\/span>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.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Expanded Support for OSDP readers <\/b>– <\/span>Added expanded support for OSDP Exit readers when using Mercury’s EP or LP controller types.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Added Alternate Reader for Elevator Control <\/b>– <\/span>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.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Doors.NET has recently announced a number of improvements to the platform, making it easier and more reliable for users. One of the most significant changes optimizes the retrieval of card data for systems with exceptionally large cardholder databases (of more than 10,000 cardholders).<\/span><\/p>\n

We’ve also implemented a value check when enrolling an Entraguard user to ensure that both the Entraguard ID and Directory Code numbers are independently unique. This means that there should be no duplication or overlap between either of these numbers. This measure helps to ensure the accuracy of our records and simplifies user identification processes.<\/span><\/p>\n

Why update?<\/b><\/p>\n