Operating System Compatibility
Doors.NET software IS COMPATIBLE with:
(both 32-bit and 64-bit where applicable)
- Windows 8.1
- Windows 10 - all versions
- Windows Server 2012 and 2012 R2
- Windows Server 2016
- Windows Server 2019
All other operating systems are NOT SUPPORTED.
- All supported operating systems are compatible with Microsoft.NET Framework v4.6.2 or greater.
- Doors.NET is currently using .NET Framework v4.8.
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:
- If SQL server is not present, then SQL Server 2019 Express will be installed.
- 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).
The following link will take you to Microsoft's SQL Server Express 2014 download page:
- 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.
End-of-Life for PXL and Entraguard Modem Communication
Keri has decided to delay removing support for modem communication for PXL and Entraguard units to the next software release.
Doors.NET v4.8.0 will be the last software revision that will support modem communication for PXL and Entraguard products.
Modem communication for PXL and Entraguard units will end beginning with Doors.NET v4.9.0.
This change will be made to accommodate 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.
Keri strongly recommends preparing for this change by the following 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 use a VOIP converter for voice calling between Entraguard units and tenants. This requires the use of a VOIP adapter.
- Keri recommends the Cisco SPA 112 VOIP Adapter, however your ISP likely has their preferred unit.
New Features in Doors.NET
- Updated the License Manager and Doors.NET software to detect and support existing SQL 2019 and SQL Studio 2019 installations.
- Added the ability to Doors.NET to install and support SQL Express 2019.
- Verified support for MS SQL Management Studio 2019.
- Implemented support for FIPS 140-2 data encryption.
- Implemented Microsoft .NET Framework v4.8 support.
- Added a Unique Cardholder selection feature to Cardholder Reports allowing a user to create a report listing if an individual cardholder has been inside a selected area on a specific day or date range. This can be used to provide contact tracing by area and individual.
Microsoft .NET Framework Notes
- 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.
- Keri has changed our controller networking terminology from Master/Slave to Primary/Secondary.
- Corrected a sporadic issue with high CPU usage with the Application Server at boot up associated with log in socket handling and the video gateway.
- Corrected an issue where a GIOX unit did not report connected modules until a status request was sent to the unit.
- Made improvements for software upgrades made to installations in a non default drive location. When performing an upgrade software installation, the Doors.NET installer now shows the installation directory when being installed on a system with Doors.NET already on it, and the installation is on a drive other than the default C: drive. When performing this kind of upgrade, the person installing the software needs to browse to the drive to which the installation should be performed.
- Improved the installation detection for PhotoID and Milestone DirectShow when upgrading Doors.NET software. On an upgrade, the installer will attempt to automatically install a new PhotoID/Milestone instance. If it cannot perform the installation it will prompt the installing tech to rerun the software installer and select the appropriate PhotoID/Milestone client installation option.
- Corrected a sporadic issue that could cause a global linkage function to stop operating.
- Added checks to ensure Admin Operators could not accidentally disable their own account and render the operators function inaccessible.
- Added dynamic Access Group array modification to accommodate Doors32 to Doors.NET database upgrades where the Doors32 database has greater than 255 access groups. While having that many Access Groups makes personnel management difficult, we are finding that many customers are doing this in Doors32, hence the need to accommodate that in Doors.NET.
- Corrected an issue that prevented the PXL gateway from following a Holiday Schedule if that schedule was enabled on the first day of the holiday schedule.
- Corrected an issue with the Doors.NET Tray App that affected the performance of the Restart All function resulting in certain services not being restarted.
- Implemented IP checking during AutoConfig to not allow two controllers to be assigned the same IP address during the IP assignment operation.
- Added XLS export to the drop-down menu in Global Linkage Macro for report exporting. You must have a designed report in the Report Client for this new option to appear in the report drop-down menu.
- Corrected a grid refresh issue that handles a custom field name header change without having to exit then reload that grid.
- Corrected a grid refresh issue when configuring the UI to use the Global Lock command without the corresponding Global Unlock command. You would have to restart the client for the correct icon to display.
- Corrected an issue when adding or updating custom field names for cardholder reports.
- Corrected a logic issue where adding an AD300 reader to any bus other than bus 1 would prevent bus 1 from working with any other reader type.
- Corrected an issue with I/O devices connected to MSC controllers regarding I/O device offline acknowledgment. If your I/O device is offline and you issue an unlock command to the device, you would have had to acknowledge a "Command cannot be sent" message for every individual output. This has been changed to only requiring one acknowledgment for the device itself.
- Corrected an issue that prevented Holiday Type 1 from being applied to MSC controllers.
- Corrected a licensing issue that could prevent an MR51e from being added to an LP1501.
- Corrected an issue that prevented a new Time Schedule/Access Group from allowing access until a Memory Reset is performed on the controller. This only affected the first new Time Schedule. Any other added schedules worked correctly.
For Visual Doors
- Keri has changed our controller networking terminology from Master/Slave to Primary/Secondary.
- Corrected a display issue when setting Access Groups for Cardholders using Allegion lock sets. The list of lock sets available was limited to the initial ten shown on the display screen.
- Corrected a grid refresh issue that prevented a user from making multiple configuration changes to a reader without exiting and reentering the grid between each change.
- Corrected a grid refresh issue for cardholders following a search operation that partially obscured the cardholder names.
- Corrected an issue where modifying a Report by deselecting a data column caused multiple columns to be deselected.
- Corrected a cardholder grid display issue that required an extra grid refresh step to properly display the cardholder list.
- Corrected an issue that prevented an operator from multiple edits to the descriptions of inputs and outputs on 4x4 units.
- Corrected an issue that prevented link assignments from being completed on 4x4 units.
- Corrected an Access Group assignment logic issue that could allow unwanted access to a cardholder depending upon when an Access Group was configured and assigned to the cardholder. Disabling then re-enabling the Access Group restored proper operation.
- Corrected a display issue with PXL controllers where SB-593 Satellite Board options are not disabled should a controller not have a satellite board attached.
- Made several typographical corrections.
Current Firmware Revisions
For NXT Controllers and Peripherals:
- 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
- Standard PXL Controller - 8.6.09
- Legacy PXL Controller - 8.5.22 (requires a Legacy license for operation)
- 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)
- Neutron Controller - 1.00.19
- Neutron Bootloader - 1.00.08 (new revision - see information below)
For Mercury Powered NXT (MSC) Controllers:
- MSC Controller - 1.293 (new revision - see information below)
Neutron Bootloader v1.00.08
- Corrected an intermittent firmware bootloader issue that could prevent a controller memory reset operation from completing correctly. This issue only happens when the reset switch is held longer than necessary for starting the reset operation.
MSC Controller Firmware v1.293
- Corrected an issue where the strike time for 4x4 and GIOX units under elevator control stayed active longer than the strike time set for the controller board.
- Corrected an issue where MSC controllers did not set the correct default gateway when set to DHCP mode.
- Corrected a 4x4/GIOX output timing issue that caused relay pulse operations to stick in the ON position requiring a manual OFF command.
Click here for the software release history.