Doors.NET v5.1.0 Release

We would like to take this opportunity to announce the release of our Doors.NET software, which has received many improvements and new features. By continually updating our products, we enable our customers to benefit from the latest security features while also getting the most value.

New Features in Doors.NET v5.1.0

• Full compatibility with windows 11
• Cloud database backup/restore
• Otis destination dispatch
• Dormakaba lock integration
• Doors.NET improvements
• Improvements to both Doors.NET and visual doors
• Visual doors improvements
• Telepathy improvements

Full compatibility with windows 11

Windows 11 has been approved for new installations of Doors.NET software from v4.8.0 and newer.

Windows 11 has been approved for older installations of Doors.NET software under the following conditions:

• The installation is upgraded to Doors.NET v4.8.0 or newer
• The installation has the SQL Express software upgraded to SQL Express 2019
  

Cloud database backup/restore

Doors.NET Cloud Backup/Restore allows customers to create Amazon Web Services (AWS) backups of their Doors.NET SQL Server database and all Doors.NET configuration files.

The main purpose of Cloud Backup/Restore is for customers to quickly and easily restore or recover their Doors.NET system from a cloud-based backup. This is valuable in cases where the Doors.NET system hard disk needs to be replaced or reformatted due to data loss or disk damage or if a system needs to be migrated to a new workstation.

Otis destination dispatch

OTIS Destination Dispatch integration allows the Doors.NET software to integrate with an OTIS Destination Dispatch Elevator Control system via the use of Mercury LP4502 controllers, which in turn, communicate with the OTIS touchpad or touchscreen devices known as DECs. Destination Dispatch allows a facility to optimize elevator travel to reduce travel and wait times. Being able to group passengers according to their travel destination and point them towards the appropriate elevators.

The Destination Dispatch integration allows you to control up to 64 OTIS DECs with a single LP4502 controller.

dormakaba lock integration

From Doors.NET v5.1.0 you can integrate with the dormakaba Wi-Q wireless technology and BEST door hardware products (when using Mercury’s LP4502 controller). The integration provides seamless connectivity and management with the Wi-Q Gateway which, in turn, communicates with the WI-Q wireless access control hardware using Mercury’s Over-Watch service (embedded in the LP4502 controller).

• Each Wi-Q Gateway can control up to 64 WI-Q controllers.
• SSL encryption between the LP4502 and the Wi-Q Gateway.
• Easy to setup and configure.
• AES 128-bit secure encryption.
• Supports extended cardholder modes (Passage and Manager mode) – providing advanced reader mode control without requiring time-consuming programming. 
• Each Wi-Q Controller lock can store up to 14000 user credentials.
• Intelligence is stored at the controller/lock – providing full functionality even if the Wi-Q hardware is offline.
• ADA (Americans with Disabilities Act) compliant

Doors.NET improvements

• Corrected an admin user interface property grid refresh issue (related to changes made with Elevator Control setup). Improvements have been made to the setup logic to ensure multiple changes to facilities are correctly saved.
• Remote clients would intermittently not load all cardholders when using a remote client over a VLAN. For large systems, cardholders are now loading in incremental batches to ensure all records are displayed.
• Corrected an issue where the Generate PIN function was not triggering a save on the cardholder screen. Generating PIN now correctly triggers the save icons.
• Hardware ribbon group was displaying unsupported hardware types for NXT-MSC controllers. Corrected so that only Series 3 MR16 hardware now displays (and obsolete Series 2 MR16 modules are now hidden).
• The Doors.NET user interface was not limiting the number of Allegion readers to the maximum number supported per bus. This is corrected so that only 16 AD-400/WRI-400’s can be added per controller (including when multiple PIM400s are used on different buses).
• Provided an option to run a report that will limit the report to one record per cardholder for a single day – (regardless of the number of access events generated by the cardholder). This will display a quick summary of who has accessed a monitored area on a particular day.
• Standardized how cardholder deactivations are handled in the PXL gateway between the cardholder form and the Deactivate button on the cardholder ribbon.
• Simulate Credentials feature now hides any formats that have not been correctly defined in the Credential Types menu.
• The Credential Types menu now allows up to 16 active formats to be used on any MSC Gateway controller type. Previously the maximum number of active formats was limited to 8.
• Credential Types menu now includes import and export buttons – providing the ability to import and export active credential formats (or a full list of formats).
• Corrected an issue with Anti-passback where an anti-passback free-pass was not being sent with a new cardholder record if the record was using the ‘Unassigned’ cardholder template. An anti-passback free-pass is now sent with every card record (even if the cardholder has no access group assigned).
• Corrected an NXT-MSC controller status issue where a controller configured with TLS encryption was not correctly reporting the online status as encrypted until a status request was performed. An online controller will now always display ‘Online (Encrypted)’ when TLS is configured on the controller.
• Corrected an issue where the Simulate Credentials feature was not being restricted to MSC hardware only.

Improvements to both Doors.NET and visual doors

Corrected an event reporting issue when manually adding a new PXL controller to an existing system. When a new controller came online an update network command began and an Update Network event was posted. When the update finished the “Update Complete” message appeared but the notice for “Update Network Required” was still active.

Visual doors improvements

Corrected an error being generated for cardholders imported from a Doors32 database. The expiration date was incorrectly being displayed as the same date as the activation – even though ‘Never Expire’ was selected.

Telepathy improvements

Corrected an issue that was preventing new alerts from displaying at a remote workstation if those alerts occurred while the remote client was disconnected.

Why update?

• Full integration with dormakaba wireless lock sets.

• Full support with Otis destination dispatch.

• Documentation updates to the knowledge base and Doors.NET help file.

• Optimized processing and retrieval of alerts within the Telepathy client.