Keri Systems Doors NET User Manual

Doors.NET Reference Manual

Welcome to Doors.NET

Welcome to Doors.NET- a comprehensive software suite that addresses access control,
intrusion monitoring, video integration, biometrics, and facility automation. Doors.NETis
the flagship product for Keri Systems, Inc. and is a result of an experienced development
and sales team, with feedback from focus groups, consultants, and end users. Door­s.NET software allows users to configure, control, and command NXT controllers, Mer­cury-Powered NXT controllers, Mercury Security controllers, PXL-500/-380/-160
controllers, ASSA IP series wireless and PoE locks, and IR/Schalge AD series wired
and wireless lock sets.

Getting Started with the Software

l What's New in this Release - a listing of new features, improvements, and cor-

rections

l Software Tour - become familiar with the software interface
l Software Installation - software installation, licensing, and gateway configuration
l Basic System Setup - basic hardware configuration

Changes are periodically made to this product and these changes will be incorporated
into new editions of this manual. Keri Systems, Inc. shall not be liable for errors con­tained herein or for any consequential damages connected with the use of this material.

Training and Technical Support

Online, in-house, and on-site training courses covering the installation and use of all
Keri Systems, Inc. products are available. Please contact your sales representative for
training options. It is strongly recommended that any persons installing or com­missioning Keri Systems, Inc. products attend a suitable training course beforehand.
This service is provided primarily for installing technicians. End users of Keri Systems,
Inc. products should first contact their installation or maintenance company before con­tacting Keri Systems, Inc.

Copyright and Protective Notices

1. The copyright of this document and the associated drawings are the property of
Keri Systems, Inc., and are issued on condition that it they not copied, reprinted or
reproduced, nor the contents disclosed, either wholly or in part, without the consent
in writing of, or in accordance with the conditions of a contract with Keri Systems,
Inc.

2. The publication of information in this document does not imply freedom from patent
or other protective rights of Keri Systems, Inc. or others.

- 1 -

Doors.NET Reference Manual

3. Performance figures and data quoted in this document are typical, and must be spe­cifically confirmed by Keri Systems, Inc. before they become applicable to any
tender, order, or contract.

Document p/n: 01249-001
Software version 3.5.1.19 - Rev A

Corporate Headquarters

Keri Systems, Inc.

2305 Bering Drive

San Jose, CA, USA 95131

Phone: [phone]

Toll Free: 800-260-5265

E-mail: [e-mail]

Web: www.kerisys.com

Keri Australia Pty. Ltd.

Unit 1, 5A Pioneer Avenue

Tuggerah NSW 2259

Australia

Phone: + 61-2-4353-0466

E-mail: [e-mail]

Europe, UK, Ireland

Keri Systems UK Limited

Unit 17

Park Farm Industrial Estate

Ermine Street

Buntingford

Herts SG9 9AZ UK

Phone: + 44 (0) 1763 273 243

E-mail: [e-mail]

Web: www.kerisystems.co.uk

Keri Systems U.A.E.

Phone [phone]

E-mail: [e-mail]

Keri Systems, Latin America

Phone: [phone]

E-mail: [e-mail]

- 2 -

Doors.NET Reference Manual

Software Overview

What is Doors.NET?

Doors.NET is Keri Systems' flagship software product. Designed to manage Keri Sys­tems hardware, including NXT, NXT Mercury-Powered, Mercury controllers, as well as
the PXL range of controllers. It is designed natively in Microsoft's .NET platform and util­izes an SQL database engine. With all instructions and communications with the data­base done through stored procedures, making response time lightning fast.

Doors.NET is extremely easy to learn and operate, yet powerful and scaleable enough
to meet the requirements of most applications.

In addition to sophisticated access control functionality, Doors.NET allows multiple oper­ators to manage and monitor an unlimited number of sites concurrently. As well as
providing Integrated video,
alarm reporting, SMS/E-mail notifications, live events and sophisticated Automation cap­abilities when using certain hardware types together with the Global or Local Linkage
licensed components.

The User Interface

- 3 -

Doors.NET Reference Manual

Doors.NET has a very intuitive interface, that will perhaps seem familiar if you have used
Keri's Doors32 software. It has a similar Doors32-like operation, but with enhanced fea­tures and an updated look and feel. The interface can be used 'out of the box with its
default layout settings, or it can be configured to individual preferences for daily use. The
GUI supports multiple monitors. All GUI screens, such as transaction information,
alarms, configuration data and reports, can be docked or placed wherever the operator
prefers to see the information presented.

Upgrading From Doors32

It is a very simple and straight-forward process for Keri Systems to upgrade an entire
Doors32 database into Doors.NET, providing all the existing controllers are of the PXL­500 variety. All the required information is copied across, including; Cardholder names
and cardnumbers, cardholder photographs, door names, controller names, timezones
(time schedules), access groups plusany other settings such as Dual Verification and
Automatic Unlock timezones. Contact Keri Systems inside sales for further information
about upgrading an existing Doors32 site.

Windows Compatibility

The software is compatible with most popular business-versions of Windows; Including
Windows 7 Professional and Ultimate, Vista Business and Ultimate, XP Pro x32, Win­dows Server 2003 and 2008 and the free version of SQL (Express) is automatically
installed along with the access control database when you perform a full install of the

- 4 -

Doors.NET Reference Manual

software. It can be configured to run on a single PC or multiple PCs across a network ­depending upon the desired characteristics of the system.

Software Installation

The software can be installed either via the webinstaller - the files can be downloaded
via the www.kerisys.com website, or it can be installed via the installation DVD - Which
you can obtain from Keri Systems, free of charge. The software is compatible with most
business versions of Windows and the standard version of the software is free of charge
and includes SQL Express (the free Microsoft SQL Server package).

License Activation

Doors.NET uses a license key, which is most easily activated over the Internet, following
installation of the software. You can however, run the software in demo mode for 30
days, in which case you will not need a license key (and an Internet connection is also
not required for demo mode). Or, you can send in the license key via e-mail and Keri Sys­tems will activate the license for you. Note: a standard Doors.NET license only includes
support for standard NXT controllers. When using PXL or NXT Mercury-Powered con­trollers you will need to contact inside sales to have these controller types enabled.
Ensure you have your license key at hand when you call.

Additional Features

- 5 -

Doors.NET Reference Manual

Custom Credential Formats, Area Control, Host Schedules, System Calendar, Rollcall
Client, and a Professional Report Client. The license key can be altered to allow for addi­tional client connections, additional gateways or for increasing the capacity for sup­ported cameras - Many of these additional features are covered in detail elsewhere
within the Online Help. Note: Not all hardware types supports all the available features,
please consult Keri Technical Documentation if you are unsure of compatibility.

Video Integration

The built in Reflections EVR client is an advanced video solution that provides you with
a number of advantages over traditional DVR/NVR video products
by enhancing the functionality of those systems. It is a separate video client that gathers
pre-defined events from a source (DVR, NVR or IP camera) and
associates them with their corresponding events within the Doors.NET access control
application for later recall. A key feature is how Doors.NET events
and recorded video clips are associated. For example, you can create video clips if a cer­tain door (or doors) are forced open, if readers or controllers go
offline, or if someone tries to gain access where they shouldn't.

Event Management

- 6 -

Doors.NET Reference Manual

Alerts can be easily setup in Doors.NET to automatically give an indication in the soft­ware when a certain event occurs. For example, if a panic button is pressed, if a secure
door is forced open, if an Anti-Passback violation occurs, if a reader or a controller goes
offline, if a tamper switch goes active, or if a motion detection sensor is activated.

An alert can be generated from virtually any hardware object defined in the system; (a
reader, controller, input (monitor point), output (control point) or NXT 4x4 module). A
sound alert can also be attributed to a wide variety of system events, so that a sound file
will automatically play when the event happens, and it can be set to repeat until the
event has been confirmed. This is ideal for a system that is not being continually mon­itored, (as there will not always be someone looking at the software screen). The sound
file can be any .WAV format file or you can use any of the sound files included in the soft­ware by default. In addition, if the system is not always monitored, it is easy to setup
event notification to occur via e-mail or SMS. A notification will appear in the recipient's
inbox or on their mobile phone when the event happens, along with additional inform­ation such as the event type, the door location and time/date stamp.

Users and User Restrictions

- 7 -

Doors.NET Reference Manual

Doors.Net supports an unlimited number of software users and user groups. User rights
can be configured with limitations or they can have the same user rights as a system
administrator. Anyone with administrator rights can add users, configure rights and
assign those rights to other users. User rights can be used to restrict which software per­missions and features are available, which cardholders and access rights can be seen
and edited and which transaction events will be seen from the system hardware.

Licensed Components/ Optional Modules

The Doors.NET license key controls which hardware can be used and which features
are available. There are many additional features and
components that can be enabled to enhance the functionality and performance of a Door­s.NET system.

Map Client and Map Editor - The Map interface provides a graphical representation of

the status of selected objects in the Doors.NET system.
In addition, it allows you to control those objects through context menus and custom tool­bars. The map diagram editor is a fully managed .NET
application that lets you create, edit and save diagram documents. The map client
allows you to link sensors, readers and outputs to the shapes
you have created with the editor.

Photo-ID client - Consists of a task-orientated user interface that has two main com-

ponents the template designer and the cardholder menu.
In the Doors.NET Photo ID client you have the ability to capture images, export images
and print badges. It is a professional-quality design
software that makes creating superb, full color photo badge templates quick and easy.

Rollcall Client - Combines area roll call, muster reporting and batch updates to card-

holder records. The main purpose of the feature is to
provide a list of all cardholders that are "in" a designated area.The list is dynamic and

- 8 -

Doors.NET Reference Manual

updates in real-time as the cardholders move throughout
the facility. An occupancy counter updates as cardholders enter or leave the area.

Elevator control - Allows for an extremely cost-effective means of controlling elevators for

various sized elevator applications (requires
the use of NXT Mercury-Powered controllers and NXT 4x4 or GIOX modules). When
using a 4x4 module on each controller bus up to 20
floors can be controlled per controller. A reader is situated within the elevator cab, which
is responsible for cardholder access requests to
the floors.

Global Linkage - Provides automation capability for actions that will occur when spe-

cified trigger conditions are met. It is supported
on all hardware types but is dependent on the controllers being online to the software.
Action examples that can be defined are; activating
or deactivating multiple outputs (control points), changing the reader modes of multiple
readers, masking/unmasking inputs or a combination
of multiple actions. A trigger condition is simply a transaction that meets a specified cri­teria; this could be a change of state of an input or
multiple inputs, an access event or a tamper input going active.

Local Linkage - Similar to Local Linkage but is only supported on Mercury and NXT-Mer-

cury-Powered controllers. Once defined the
actions are stored and processed at the controller - so there is no reliance on the con­trollers being 'online' to the software. Allows custom
IF/WHEN scenarios to be configured without a change in software. Local linkage trig­gers are defined to automatically action procedures
(which can be one, or a list of items and can vary from unlocking a door to a complicated
mantrap.

Time and Attendance Module - Windows background service that provides a generic

interface to export access granted messages
from designated readers directly to an SQL Server or Oracle database. As cardholders
are granted access at designated readers, the
transaction is initially logged in at the Doors.NET database along with an IN/OUT des­ignation. This allows a third-party Time and
Attendance software to use its own database for reports with any modification. Please
contact your Keri Systems representative for
additional information.

System Calendar - Has the familiar Microsoft Outlook style calendar control with added

appointment categories that execute system­wide functions. This menu is available only to System Administrators (and those

- 9 -

Doors.NET Reference Manual

customers that have this feature enabled on their
license). A number of new categories have been added to the traditional meeting, per­sonal reminders, etc, that include backup, global
linkage and direct hardware control. In addition, the Host Schedules use the Holidays
that are scheduled in this calendar. A recurrence
engine is also provided that allows you to configure recurring events with ease. This
allows you to configure the system to change its
operational behavior on an ad-hoc basis to account for both planned and unplanned
events.

- 10 -

Doors.NET Reference Manual

System Architecture Overview

The core software module is the Application Server. This component communicates with
the SQL database, client work stations, and software gateways that communicate with
the access control hardware. It is a TCP socket server that accepts connections from
both the gateways and clients, and provides a generic transport mechanism for any
.NET class object, collection of those objects, or file. It interrogates the transport objects
in real-time and determines which stored procedures are to be executed. It also controls
which clients have access to data and routes messages from the gateways to the correct
clients. All communication is handled asynchronously and has the following options on
encryption:

l No Encryption
l RC2
l DES
l TripleDES (128 or 192 bit keys)
l AES/Rijndael (128,192, or 256 bit keys)

Both clients and gateways can be configured for DHCP as the Application Server tracks
each incoming connection by its current IP Address. Since only .NET class objects are
transported over the network socket connection, there is no need for any database know­ledge at either the client or the gateway. This not only provides an increased level of
security to the database but also requires only a SQL client license for the Application
Server and not for each gateway/client connection. In addition, the optional encryption
on every network packet provides a secure Internet connection without the need for spe­cialized hardware or VPN client software.

A single Application Server can communicate with up to 32 hardware gateways (512
readers per gateway, standard gateway license). The base Application Server is con­figured to support 1 client work station, but can be expanded with additional client
licenses. A client license includes the standard Doors.Net GUI (Graphical User Inter­face). At least one Application Server is required for each system. The Application
Server includes SQL Express.

The second required component is the Gateway. The Gateway is the software service
component that communicates with the field hardware and the Application Server. It
receives .NET class objects for the hardware that it is responsible for servicing. All trans­actions generated by the hardware are formatted into a .NET class object for transport
back to the Application Server. The Gateway can reside on the same machine as the
Application Server, on another machine on the network, or across the Internet. The ser­vice supports static IP Addresses as well as the default of DHCP. There are different
types of Gateways, each supporting different types of hardware.

- 11 -

Doors.NET Reference Manual

The Doors.Net Gateway connects to up to 64 NXT controllers (256 reader capability,
standard license, using 4 readers per NXT-4D controller) and communicates with the
Application Server. Only 1 Gateway is allowed per computer.

Optional licensed applications include:

l Additional User Clients
l Photo ID/Badging
l Report Designer
l Managed Services
l Visitor Management
l IT Package including a Report Designer, Time and Attendance, and an LDAP ser-

vice

- 12 -

Doors.NET Reference Manual

What's New In This Release

Doors.NET Version 3.5.1.19

Operating System Compatibility

Operating System 32-Bit 64-Bit

Windows XP

Home NO NO

Business Yes Yes

Pro Yes Yes

Vista

Home Basic / Premium NO NO

Business Yes Yes

Enterprise Yes Yes

Ultimate Yes Yes

Windows 7

Home Premium NO NO

Professional Yes Yes

Ultimate Yes Yes

Windows 8

Windows Server

(1) The ASSA gateway for WiFi/POE products is not yet Windows 8 or Windows Server
2012 compatible. The software installer will not allow the ASSA gateway to be installed
if the operating system is either Windows 8 or Windows Server 2012.

(1)

Basic NO NO

Professional Yes Yes

Enterprise Yes Yes

2003 Yes Yes
2008 Yes Yes

2008 R2 Yes Yes

2012 N/A Yes

NOTE: Doors.Net software IS NOT compatible with any Home/Basic version of Win­dows XP, Windows Vista, Windows 7, or Windows 8.
This is due to networking restrictions built into the Home/Basic versions of Windows
operating systems.

- 13 -

Doors.NET Reference Manual

New Features

New Hardware Release:

l The GIOX (Greater I/O Board) has been released for use by NXT and Mercury

Powered NXT controllers. The GIOX unit is made up of a back plane and a com­bination of Input and/or Output plug-in modules. The back plane handles up to 8
plug-in modules in any combination of input module or output module. Input mod­ules have 8 inputs and Output modules have 8 outputs. This product can be used
for either Elevator Control or general I/O; the two uses cannot be mixed in one
GIOX unit. Elevator Control is currently only supported on Mercury Powered NXT
controllers.

For All Hardware Platforms:

l Doors.NET is now capable of running multiple concurrent hardware gateways. In a

multiple concurrent gateway system, the software limits itself to the lowest hard­ware common denominator for certain operating parameters. Also, certain features
may be displayed, but may only apply to one specific gateway, and not to any other
gateways. The factory default allows one gateway. There are additional charges
for each additional gateway and your license must be updated to enable each addi­tional gateway. This includes any combination of the following gateways:

l NXT
l Mercury Powered NXT
l PXL-500 Series
l Standard Mercury
l ASSA Aperio and WiFi/POE
l Ingersoll-Rand/Schlage

Unique to Keri NXT Controllers:

l None at this time.

Unique to Keri PXL Controllers:

l None at this time.

Unique to Keri NXT Mercury Powered Controllers and Mercury Hardware:

l None at this time.

Unique to ASSA Aperio Lock Hardware:

- 14 -

Doors.NET Reference Manual

l None at this time.

Unique to ASSA WiFi/POE Lock Hardware:

l None at this time.

Unique to IR/Schlage Lock Hardware:

l None at this time.

Program Improvements

For All Hardware Platforms:

l Corrected an issue that prevented the Auto Config window from closing if the

installer opted not to complete the Auto Config process.

l Added the ability to clear the Roll Call list at a specific time every day.
l Corrected an issue that would not allow a remote client delete a photo in a card-

holder record.

l Corrected an issue with activating Host Schedule triggers in global linkages and

when using the System Calendar.

l Changed manual entry of MACaddresses to no longer be case-sensitive.
l Changed the time stamp used for event reports from the server time stamp to the

controller time stamp. The controller time stamp reflects the time the event
occurred, and is typically the information that these types of reports are presenting.

l When setting the ADA/DDA option for a cardholder, enabling either the Extended

(ADA/DDA) value for the Cardholder Type or the Use ADA/DDA Timing check box
also enables the other setting. You can then disable one value or the other if
desired.

l When performing a client-only installation the software will now not automatically

run the license manager as this step is unnecessary.

Unique to NXT Controllers:

l Set a limit to the number of times the software reports a controller is offline. Pre-

viously the software would report "controller offline" every time an attempt was
made to reconnect. Now it will only report the offline condition the first time it
occurs. The report enables itself once the controller comes back online.

l Corrected a gateway issue with the holiday index running out of space causing

doors to not unlock on a holiday when Active on Holiday is set.

l Added checks to ensure Holiday schedules and associated limits are being

applied correctly.

- 15 -

Doors.NET Reference Manual

Unique to PXL Controllers:

l Made a number of gateway improvements to accommodate network timing con-

ditions in medium to large controller networks (typically 20 controllers or more).

l Corrected an issue with single-door applications using two readers. Operating

parameters assigned to the second reader are now properly applied to that reader.

l Implemented a check to prevent multiple back-to-back Update Network requests

from being executed.

l Corrected an issue where if a slave controller was reset and then comes back

online, the property grid was correctly updated, but the status grid was not until a
request status command is performed. The status grid now does a real-time update
to ensure displayed information is correct.

l Made a number of improvements to the reporting function options.
l Added checks to ensure Holiday schedules and associated limits are being

applied correctly.

Unique to Keri NXT Mercury Powered Controllers and Mercury Hardware:

l Added support for a double credential presentation feature allowing a double-

presentation of a credential be a local linkage trigger.

l Corrected an issue with temporary cards disabling themselves 1 minute late.
l Added credential Use Count to the credential template.
l Corrected the clock synchronization feature in the System Calendar. It was not

properly synchronizing the controllers with the host computer. Also added the abil­ity to synchronize all controller clocks at one time.

l Added a new Reader mode control "timed to action list" option to Local Linkages.

Allows a local linkage macro to set any Reader mode for a designated amount of
time.

l Added support for IPv6 addressing.

Unique to ASSA Aperio Hardware:

l Added support for new devices - Securitron R100, HES KS100, and AS100.
l Added a Scheduled Relock command.
l Added support for the Situation Manager feature.
l Corrected an issue with event display filtering.
l Added a Scheduled Relock command.

Unique to ASSA WiFi/POE Hardware:

l Added support for remote Unlock/Lock. These lock sets must have the Always Con-

nect option enabled.

l Added support for the Situation Manager feature.

- 16 -

Doors.NET Reference Manual

l Corrected an issue with event display filtering.
l Implemented new WiFi/POE drivers provided by ASSA. Driver version is now 4.4.

NOTE: If you are upgrading an existing ASSA WiFi/POE installation you must manually
remove the existing ASSA driver (version 1.2) before running the Doors.NET installer.

Unique to IR/Schlage Hardware:

l Corrected the display of the Interior Push Button indicator.
l Corrected temp LEDcommands.
l Corrected operation in Card OR PIN mode.
l Now actively requesting Wake-on-Radio status, improving notification of latch state

changes.

l Corrected a backwards compatibility issue for operation with older AD-series lock-

sets.

Known Issues

With NXT Controllers:

l If additional doors are added to an existing access group, causing a cardholder in

that access group to exceed eight access levels, then Update Network will not
work for that controller. To correct this condition the operator will have to review
access group/door assignments and determine which assignment exceeds the
limit. This will be corrected in the next software release.

With PXL Controllers:

l PXL controllers, by default, are configured for a standard credential file size.

Features such as Temp Cards, Anti Passback, Card + PIN, require a extended cre­dential file size. Under most situations, the PXL gateway automatically notifies con­trollers on the line that a switch to extended credential file size is required. This is
not being done correctly when Temp Cards is the feature being activated. The
workaround is to manually perform a full update to the controllers. This will be cor­rected in the next software release.

Firmware Requirements

For NXT controllers and peripherals:

l Standard NXT controllers require new firmware revision 2.05.40.
l NXT Readers require firmware revision 3.00.01 or greater.
l Reader Interface Modules (RIMs) require firmware revision 3.02.05 or greater.
l 4x4 I/O Modules require firmware revision 3.00.02.

For PXL:

- 17 -

Doors.NET Reference Manual

l PXL controllers require firmware revision 8.6.09.
l Legacy PXL controllers should be at firmware revision 8.4.49 or greater (this firm-

ware revision is programmed with the current U.S. Daylight Savings Time dates
and has the complete PXL implementation of Anti-Passback).

For Mercury Powered NXT controllers and Mercury Hardware:

l Mercury Powered NXT controllers require new firmware revision 1.185.

Firmware Upgrades

NXT Firmware v2.05.40

l Added support for updating NXTReader firmware.
l Implemented a number of Ethernet communication enhancements that help protect

the controller from data that does not apply to the controller, including bad data
packets and invalid connection attempts. These changes help to prevent the con­troller from being knocked offline.

l Added a health monitor to collect and save information on questionable Ethernet

events. This information can be used to assist in debugging Ethernet related
issues. This feature is selectively enabled, and should only be used if a controller
has repeated networking issues.

l Corrected an error in applying holiday dates to door unlock schedules.

Mercury Hardware Firmware v1.185

l The 4x4 status command now provides more status information.
l Corrected the red LED display pattern when in 2-wire LED control mode.
l Corrected a configuration issue with Schlage AD300 lock sets that could cause the

controller to reset.

l Now actively requests Schlage Wake-on-Radio status, improving the reporting of

latch state changes.

l Corrected Schlage lock set operation in Card OR PIN mode.
l Added extended lock set modes: Classroom, Office, Privacy, and Apart-

ment/Canadian-Law.

l Double card presentation is treated as a toggle state in extended lock set modes

Classroom and Office.

l Added support for OSDP biometric types.
l IPv6 web connections now use Zeroconf name, resolving browser incompatibilities

with IPv6 literal addresses.

l Made changes to how Scheduled Override for Aperio operates when invoked by a

linkage trigger to accommodate the triggering condition. This prevents conflicting
operations from occurring.

l Corrected a backwards compatibility issue with older Schlage AD-series locksets.

- 18 -

Doors.NET Reference Manual

Translations

Completed Translations:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)
l French (France)
l Polish
l Russian
l Slovenian
l Spanish (Castilian)
l Turkish

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l Italian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in US English.

Click Here to link to the revision history for previous

releases.

- 19 -

Doors.NET Reference Manual

Release History

Previous Releases:

l v3.5.1.18
l v3.5.1.17
l v3.5.1.16
l v3.5.1.15
l v3.5.1.14
l v3.5.1.12 - SP-2
l v3.5.1.11
l v3.5.1.10
l v3.5.1.9
l v3.5.1.8

Doors.NET Version 3.5.1.18

Operating System Compatibility

Operating System 32-Bit 64-Bit

Windows XP

Home NO NO

Business Yes Yes

Pro Yes Yes

Vista

Home Basic / Premium NO NO

Business Yes Yes

Enterprise Yes Yes

Ultimate Yes Yes

Windows 7

Home Premium NO NO

Professional Yes Yes

Ultimate Yes Yes

Windows 8

(1)

Basic NO NO

Professional Yes Yes

Enterprise Yes Yes

Windows Server

- 20 -

Doors.NET Reference Manual

Operating System 32-Bit 64-Bit

2003 Yes Yes
2008 Yes Yes

2008 R2 Yes Yes

2012 N/A Yes

(1) The ASSA gateway is not yet Windows 8 compatible for IPlocks (Wifi and POE). The
software installer will not allow the ASSA gateway to be installed if the operating system
is Windows 8.

NOTE: Doors.Net software IS NOT compatible with any Home/Basic version of Win­dows XP, Windows Vista, Windows 7, or Windows 8.
This is due to networking restrictions built into the Home/Basic versions of Windows
operating systems.

New Features

For All Hardware Platforms:

l Added a linkage Export/Import function that allows a programmed linkage to be

exported from one controller and then imported by another on the same system or
on a completely different system. This feature is available via local linkage.

l Added a Apply Template/Save Template for all controllers. This feature saves the

existing properties of a controller and its devices to a template file. That file can
then be applied to another controller of the same type. Available only in Design
mode.

Unique to Keri NXT Controllers:

l None at this time.

Unique to Keri PXL Controllers:

l Implemented the Global Unlock/Lock feature set in Doors.NET. When the cor-

responding input is activated, these features automatically either lock or unlock
ALL of the online and functioning doors in the PXL system; it does not allow selec­ted doors to be excluded from the lock or unlock command. Since these features
are hardware controlled they are not dependent upon the PC to be activated. If con­trollers are offline when a Unlock/Lock command is issued they will not respond to
the Unlock/Lock command until they come back online.

l The Global Unlock/Lock functionality of PXL hardware can be extended using the

Situation Manager within Doors.NET software. This provides you with greater con­trol and flexibility in how the Global Unlock/Lock features are implemented,

- 21 -

Doors.NET Reference Manual

including varying restriction levels of lock and unlock and the ability to assign/un­assign specific doors. The Situation Manager requires the master controller always
be online with the host PC.

Unique to Keri NXT Mercury Powered Controllers and Mercury Hardware:

l None at this time.

Unique to ASSA Lock Hardware:

l None at this time.

Program Improvements

For All Hardware Platforms:

l Corrected an issue where the Archive database could not connect when using Win-

dows 8. Windows 8 uses SQL Server 2012 which has a slightly different structure
for its connection information. The program now recognizes when SQL Server
2012 is active and adjusts its connection information accordingly.

l Corrected an issue where both a door strike and a door forced alarm could be

assigned to the same control point (when reassigning a door strike from its default
control point) resulting in unexpected operation. The program now prevents the
control point from being assigned to door forced if already assigned to door strike.

l Corrected an issue that, in certain applications, would not allow a temporary

unlock command to be overridden by a lock command.

l Restricted access to Design Mode to operators designated as System Admin-

istrators. You must also be in Advanced View to access Design Mode. Design
Mode allows an operator to change the appearance and layout of program
screens.

l If a gateway disconnects from the host PC, the status grid will set all controllers on

that gateway to offline status.

l Added a "Remove All" option to Local Linkage triggers and procedures. You must

be a System Administrator to perform a Remove All and you must remove triggers
before you remove procedures.

l If a reader is an exit reader or does not have Door Contact enabled the Door Status

grid would not display status in the Door Forced or Door Held fields.

l A "Client Only"installation was unnecessarily installing the Gateway Wizard. If no

gateway is being installed, the program now does not install the Gateway Wizard.

Unique to NXT Controllers:

l None at this time.

- 22 -

Doors.NET Reference Manual

Unique to PXL Controllers:

NOTE: For PXL installations, Keri strongly recommends upgrading to the 3.5.1.18
release to take advantage of the improvements made for data throughput and event col­lection, and for master/slave controller updating.

l Made multiple improvements in data handling and event collection in the gateway,

increasing data throughput when multiple master controllers are connected.

l The PXL controller firmware revision was not being displayed in the grid.
l Provided the ability to allow PXL masters to be placed in different world time

zones.

l Optimized timing parameters in the gateway to improve data throughput.
l Added a check on credential block enroll for quantity of more than 100 records and

automatic download is enabled on any PXL master. If those two conditions are
met, a message is displayed to the user with two options 1) either reduce the quant­ity or 2) set the PXL to manual update. This check is necessary due to the slow
data transfer rate from master to slave units.

l Changed the level of detail on certain Live Event messages to be less technical

and more user friendly.

l Ensured that if a Smart Update was initiated on a master controller, any slave con-

trollers also requiring an update were updated as well.

l Added the ability to select if an Update Network or Smart Update command

applies to the master only or to the master and slaves.

l Added a check to Holiday scheduling to ensure only a holiday type of 1, 2, or 3 is

selected. The PXL cannot support greater than 3 holiday types.

Unique to Keri NXT Mercury Powered Controllers and Mercury Hardware:

l When adding controllers manually, the program's user interface now waits until a

controller update is complete before allowing the next controller to be added.

l Added an automatic status update request following a firmware upgrade on RIMs

and 4x4s to collect the information needed to immediately update the unit's status
following the upgrade.

l When manually adding Mercury Hardware, the software automatically adds a net-

work communication channel to support the hardware, instead of requiring the com­munication channel to be added manually. Conversely, if you manually remove
hardware its communication channel is now automatically removed as well.

l If a controller's Daylight Savings Time rules are changed, the controller is now

tagged as needing to be reset so the new DST rules can be applied to the con­troller.

l Controllers would not enforce DST rules following a reset as the information was

cleared. Controllers now retain this information regardless of the reset function.

- 23 -

Doors.NET Reference Manual

l If you deleted an elevator controller from the hardware tree before deleting elevator

access groups, you could not remove the elevator access groups from the access
group list.

l A new communication channel for a controller is only created if a unique IP

address is provided and controller/channel is enabled.

ASSA Gateway:

l Corrected an issue when adding a new access group. The ASSA gateway

required a restart to accept the access group. A restart when adding an access
group is no longer needed.

l Added new message types to increase the reporting ability of ASSA hardware

events.

l Added a Lock/Unlock feature for ASSA IP locks. This feature is enabled only when

the lockset is set to Always Connect.

Archive Service

l Made the maximum database size variable based on the SQL revision: SQL 2008

R2 and higher allows a maximum database size of 10 GB, SQL 2008 and lower
allows a maximum database size of 4 GB.

l Changed the decision to archive to being based on either of two criteria: the data-

base size in MB or the maximum number of days to keep records in the message
table.

Time and Attendance

l Added new access granted event codes to accommodate ASSA and Ingersoll

Rand wireless and IP lock products.

Known Issues

l The recent Doors.NET v3.5.1.18 release includes a number of PXL gateway

changes that improve data throughput speed between master controller and host
computer. As a part of this release a body of network characterization work was per­formed and optimum values were determined for controller timeout and network
timeout. These new values are implemented as part of a new PXL installation.
However, they are not updated if a software upgrade is performed from Doors.NET
software revisions prior to v3.5.1.18. This results in increasing network com­munication degradation as the number of master controllers increases. To correct
this issue the Controller Timeout and Network Timeout values must be changed to
the optimum values. Refer to the Set PXL Network Timeout Settings section for
information on how to make these changes.

- 24 -

Doors.NET Reference Manual

Firmware Requirements

For NXT controllers and peripherals:

l Standard NXT controllers require new firmware revision 2.05.27.
l NXT Readers require firmware revision 3.00.01 or greater.
l Reader Interface Modules (RIMs) require firmware revision 3.02.05.
l 4x4 I/O Modules require firmware revision 3.00.02.

For PXL:

l PXL controllers require new firmware revision 8.6.09.
l Legacy PXL controllers should be at firmware revision 8.4.49 or greater (this min-

imum firmware revision is programmed with the current U.S. Daylight Savings
Time dates and has the complete PXL implementation of Anti-Passback).

For Mercury Powered NXT controllers and Mercury Hardware:

l Mercury Powered NXT controllers require new firmware revision 1.179.

Firmware Upgrades

NXT Firmware v2.05.27

l A number of communication improvements have been made with NXT readers to

ensure proper communication with older reader firmware revisions as well as cur­rent releases.

PXL Firmware v8.06.09

l Improves the functionality of the Global Unlock/Lock feature for PXL controllers.

Mercury Hardware Firmware v1.179

l Corrected an issue with properly restoring an NXT reader's LED state following a

power cycle.

l Added new message types to increase the reporting ability of certain hardware

events.

l Improved communication connectivity with 4x4 units to minimize unit dis-

connections.

l Updated the collection of data from the 4x4 status command to include more inform-

ation.

Translations

Completed Translations:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)

- 25 -

Doors.NET Reference Manual

l French (France)
l Polish
l Russian
l Slovenian
l Spanish (Castilian)
l Turkish

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l Italian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in US English.

Doors.NET Version 3.5.1.17

Operating System Compatibility

Operating System 32-Bit 64-Bit

Windows XP

Home NO NO

Business Yes Yes

Pro Yes Yes

Vista

Home Basic / Premium NO NO

Business Yes Yes

Enterprise Yes Yes

Ultimate Yes Yes

Windows 7

Home Premium NO NO

Professional Yes Yes

Ultimate Yes Yes

Windows 8

(1)

Basic NO NO

Professional Yes Yes

Enterprise Yes Yes

- 26 -

Doors.NET Reference Manual

Operating System 32-Bit 64-Bit

Windows Server

2003 Yes Yes
2008 Yes Yes

2008 R2 Yes Yes

2012 N/A Yes

(1) The ASSA gateway is not yet Windows 8 compatible for IPlocks (Wifi and POE). The
software installer will not allow the ASSA gateway to be installed if the operating system
is Windows 8.

NOTE: Doors.Net software IS NOT compatible with any Home/Basic version of Win­dows XP, Windows Vista, Windows 7, or Windows 8.
This is due to networking restrictions built into the Home/Basic versions of Windows
operating systems.

New Features

For All Hardware Platforms:

l Doors.NET is compatible with the Windows 8 operating system.

NOTE: Doors.Net software IS NOT compatible with the Basic version of Windows 8.
This is due to networking restrictions built into the Basic version of this operating system.

Unique to Keri NXT Controllers:

l A database conversion process is now available to transfer NetXtreme databases

into Doors.NET. Please contact your RSM or Keri Inside Sales person for data­base conversion information and pricing.

NOTES:

l The NetXtreme database conversion process does NOT convert NetXtreme cus-

tom input/output linkage programming.

l The NetXtreme to Doors.NET conversion process does NOT convert elevator con-

trol programming.

Unique to Keri PXL Controllers:

l None at this time

Unique to Keri NXT Mercury Powered Controllers:

- 27 -

Doors.NET Reference Manual

l An Elevator Override Schedule feature has been added allowing the enabling of

floor access via a schedule. This feature is accessible when the Advanced View is
enabled.

l An "Honor Day of the Week" option has been added to schedule intervals. This is

used if you need specific schedule intervals to be activated regardless of if the day
is a holiday (when all intervals would have been disabled).

l Added Door Forced and Door Held alarm options to the Door property grid.

Unique to Mercury Hardware:

l An Elevator Override Schedule feature has been added allowing the enabling of

floor access via a schedule. This feature is accessible when the Advanced View is
enabled.

l An "Honor Day of the Week" option has been added to schedule intervals. This is

used if you need specific schedule intervals to be activated regardless of if the day
is a holiday (when all intervals would have been disabled).

Program Improvements

For All Hardware Platforms:

l Corrected the ability to use hardware control to turn system calendar schedules or

global linkages on/off.

l PINExempt was not displayed as a selectable option for the distribution Door-

s.NET interface. It has been added to the pull-down menu.

l Corrected several grid update issues that required exiting, then re-entering a grid

to properly refresh grid values.

l Enabled the ability to save a new system layout without having to permanently set

the save new layout tick-box. This accommodates systems where an administrator
will set and save a new layout and then reboot the system for a standard user for
everyday use.

l Corrected a Holiday grid issue when setting an extended holiday date range. If you

used the click-and-drag method for setting the date range, it would be set correctly.
If you used the click-and-shift-click method, the program would not accept the end­ing date.

l Added a buffer codec option for video cameras allowing greater flexibility in cam-

era configuration for video clips and snapshots.

l Corrected a time value entry issue in certain fields. If the PC/system clock was set

for 24-hour display (versus 12-hour AM/PM) display, certain fields were only
accepting 12-hour AM/PM format entries.

l Added the ability to allow video recording per a schedule. With no schedule set,

the video camera operates all the time. If a video camera is assigned a schedule, it
will only record during the schedule time period.

- 28 -

Doors.NET Reference Manual

l Added the ability to set operator permissions for viewing the status menu. Pre-

viously, all operators could view the status menu; now permission can be either
granted or denied per operator.

l Corrected an issue that prevented Panel type hardware Reports from being gen-

erated.

Unique to NXT Controllers:

l Extended the maximum strike time. The program had been limiting the maximum

strike time to 255 seconds; this is much too short a time. It now allows a strike time
of up to 65535 seconds (1092 minutes or 18 hours).

l Corrected an issue where an incorrect door status was reported when doors were

in lockout mode. Enhanced to show effective Card Only or Card And PIN mode
based on both dual verification time schedule and requested dual verification
mode.

l Update Network corrected to send full configuration to controller. Was sending only

a partial configuration to controllers while only Auto Config would send a full con­figuration.

Unique to PXL Controllers:

l Corrected an issue if an alarm sound was programmed to play when a controller

offline event occurred, the alarm sound would not play.

l Corrected an issue with the PXL gateway. When it was manually stopped, events

occurring during the stoppage period were not being correctly retrieved from the
controller and passed up to the program.

l Corrected an issue with the PXL gateway. If you disable a controller and then re-

enable that controller, you had to restart the gateway to bring the controller back
online.

l Added support for Global Lock types Lock, Lockout, and Lockdown.

Unique to Keri NXT Mercury Powered Controllers:

l Now limits firmware upgrade revisions displayed to those by hardware type. Pre-

viously all available firmware upgrades, regardless of hardware type, were dis­played.

l Added NXT Exit Readers to the pull-down list of available NXT reader models.

Now when adding a paired set of entrance/exit readers the program automatically
sets the entrance reader to Master paired with the exit reader. If you remove the
exit reader, then it will set the reader status back to single, and not paired.

l Added several low-battery notification events for the ASSA Aperio product.
l Corrected an issue if a controller was set to have a unique Controller Holiday

schedule, that schedule would be overridden by an update to the Master Holiday
schedule.

- 29 -

Doors.NET Reference Manual

l Corrected an issue with the "Check With Host" feature. If a reader has this feature

enabled the controller will check with the host system to confirm access per­mission. If not enabled, the controller is free to use the permissions already pro­grammed in.

l Corrected an issue with Master Holidays. Once a Master Holiday schedule was

set, changes in Master Holiday schedules were not being automatically updated to
the controllers.

Unique to Mercury Hardware:

l Now limits firmware upgrade revisions displayed to those by hardware type. Pre-

viously all available firmware upgrades, regardless of hardware type, were dis­played.

l Corrected an issue if a controller was set to have a unique Controller Holiday

schedule, that schedule would be overridden by an update to the Master Holiday
schedule.

ASSA Gateway:

l Does not allow the ASSA gateway to be installed if the operating system is Win-

dows 8 as ASSA is not yet compatible with Windows 8.

l Corrected an issue if a controller was set to have a unique Controller Holiday

schedule, that schedule would be overridden by an update to the Master Holiday
schedule.

l Added a new set of ASSAspecific messages for reporting.

Archive Service

l Made the maximum database size variable based on the SQL revision: SQL 2008

R2 and higher allows a maximum database size of 10 GB, SQL 2008 and lower
allows a maximum database size of 4 GB.

l Changed the decision to archive to being based on either of two criteria: the data-

base size in MB or the maximum number of days to keep records in the message
table.

Time and Attendance

l Added new access granted event codes to accommodate ASSA and Ingersoll

Rand wireless and IP lock products.

Known Issues

l None at this time.

- 30 -

Doors.NET Reference Manual

Firmware Requirements

For NXT controllers and peripherals:

l Standard NXT controllers require new firmware revision 2.05.25.
l NXT Readers require current firmware revision 3.01.01.
l Reader Interface Modules (RIMs) require current firmware revision 3.02.05.
l 4x4 I/O Modules require current firmware revision 3.00.02.

For PXL:

l PXL controllers require current firmware revision 8.6.04
l Legacy PXL controllers should be at firmware revision 8.4.49 or greater

NOTE: Legacy PXL controllers require the PXL Gateway license to be used with Door­s.NET software.

For Mercury Powered NXT controllers:

l Mercury Powered NXT controllers require new firmware revision 1.175.

For Mercury Hardware controllers:

l Mercury Hardware controllers require new firmware revision 1.173.

Firmware Upgrades

NXT Firmware v2.05.25

l Addresses an issue where corrupted network data in flash is not recovered and the

NXT board is in a constant state of reset (the 485 LEDs flash in sync). This typ­ically happens when a controller reset command is interrupted during the reset pro­cess, corrupting the data in flash. To handle this possibility, a backup copy of the
controller's network data is now stored in a unique location. If the controller detects
a corrupted flash or has issues with the network data, it will retrieve the backup
data and restore the primary data after it verifies that the controller's MAC address
stored is a valid Keri MAC address. If the controller's MAC address is invalid it then
writes a default MAC address: 00-14-34-ff-ff-ff and sets the IP Address to

169.254.1.1 and Subnet Mask to 255.255.0.0 allowing the controller to be redis­covered and reconfigured via an Auto-Config.

Mercury Powered NXT Firmware v1.175

l Provides support for the new IPv6 standard.
l Improves the controller's network response when an Ethernet cable is unplugged.
l Improves the controller's ability to recover from large, rogue data packets.
l Corrects several ASSA and Ingersoll/Rand WiFi lock set issues.
l Adds SNMP capability.
l Corrects a Reader LED issue where the green LED state did not properly follow

the strike time.

- 31 -

Doors.NET Reference Manual

Mercury Hardware Firmware v1.173

l Provides support for the new IPv6 standard.
l Improves the controller's network response when an Ethernet cable is unplugged.
l Improves the controller's ability to recover from large, rogue data packets.
l Adds SNMP capability.

Translations

Completed Translations:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)
l French (France)
l Polish
l Russian
l Slovenian
l Spanish (Castilian)
l Turkish

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l Italian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in US English.

Doors.NET Version 3.5.1.16

Operating System Requirements

Doors.Net software IS NOT compatible with any Home version of Windows XP, Win­dows Vista, or Windows 7.

This is due to networking restrictions built into the Home versions of Windows operating
systems.

- 32 -

Doors.NET Reference Manual

Doors.NET IS compatible with the Business, Professional, Ultimate, and Enterprise ver­sions (both 32-bit and 64-bit) of Windows XP, Windows Vista, and Windows 7; as well
as Windows Server versions 2003 and 2008 (both 32-bit and 64-bit).

New Features

For All Hardware Platforms:

l An Onvif video plug-in is now available.

Unique to Keri PXL Controllers:

l A database conversion process is now available to transfer Doors32/PXL data-

bases into Doors.NET. Please contact your RSM or Keri Inside Sales person for
database conversion information and pricing.

NOTE: Doors32/PXL-based sites with the following types of controllers are not eligible
for conversion to Doors.NET at this time.

l Entraguard telephone entry controllers (including mixed PXL and Entraguard sites)
l PXL-510 controllers for alarm panel control
l LC-502/-508 controllers for elevator control
l Obsolete PXL-250 controllers

Unique to Keri NXT Mercury Powered Controllers (MSC):

l Added support for ASSA Aperio K100 Cabinet Locks.
l Provided support for Ingersoll Rand AD-300 Networked Locks.

Unique to Mercury Hardware:

l None at this time.

Program Improvements

For All Hardware Platforms:

l Simplified the menu options for setting Activation Date and Time, and for Deactiv-

ation Date and Time.

l Corrected a video grid refresh issue when working with video cameras that pre-

vented multiple selection/de-selection of cameras unless you exited and then re­entered the video grid.

l Set the software installation program to exit immediately if the PC operating system

cannot be identified.

- 33 -

Doors.NET Reference Manual

l Corrected a date-check issue with appointment schedules that would not allow an

appointment schedule to cross midnight.

l Added the ability to show/hide Alerts in the operator permissions grid.
l Modified the License Manager to allow Demo mode to activate regardless of the

availability of an Internet connection.

l Changed the Block Enrollment default for credential access from "Total Access" to

"Unassigned."

Unique to NXT Controllers:

l None at this time.

Unique to PXL Controllers:

l Corrected the message displayed if a PINis not entered when in dual verification

mode from "No Second Card" to "No PINEntered."

Unique to Keri NXT Mercury Powered Controllers (MSC):

l Added a pop-up window to confirm the configuration of Exit Readers.

Unique to Mercury Hardware:

l Corrected an issue where the Update Network icon was not made available to Mer-

cury hardware.

l Corrected a hardware configuration grid refresh issue where the grid would con-

tinue to show a Network Update was required following resetting an AP controller.

Known Issues

l None at this time.

Firmware Requirements

For NXT controllers and peripherals:

l Standard NXT controllers require current firmware revision 2.05.23.
l NXT controllers with Mercury Inside firmware require current revision 1.01.40.
l NXT Readers require current firmware revision 3.01.01.
l Reader Interface Modules (RIMs) require current firmware revision 3.02.05.
l 4x4 I/O Modules require current firmware revision 3.00.02.

For PXL:

l PXL controllers require current firmware revision 8.6.04

- 34 -

Doors.NET Reference Manual

l Legacy PXL controllers should be at firmware revision 8.4.49 or greater

(this minimum firmware revision is programmed with the current U.S. Daylight Sav­ings Time dates)

NOTE: Legacy PXL controllers require the PXL Gateway license to be used with Door­s.NET software.

For Mercury Inside (MSC) NXT controllers:

l MSC NXT controllers require current MSC firmware revision 1.01.40.

Firmware Upgrades

None at this time.

Translations

Completed Translations:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)
l French (France)
l Polish
l Russian
l Slovenian
l Spanish (Castilian)
l Turkish

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l Italian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in US English.

- 35 -

Doors.NET Reference Manual

Doors.NET Version 3.5.1.15

Operating System Requirements

Doors.Net software IS NOT compatible with any Home version of Windows XP, Win­dows Vista, and Windows 7.

This is due to networking restrictions built into the Home versions of Windows operating
systems.

Doors.NET IS compatible with the Business, Professional, Ultimate, and Enterprise ver­sions (both 32-bit and 64-bit) of Windows XP, Windows Vista, and Windows 7; as well
as Windows Server versions 2003 and 2008 (both 32-bit and 64-bit).

New Features

l Releases a PXL Gateway that supports PXL-500 controllers in the Doors.NET pro-

gram. This gateway provides free Doors.NET software support for new PXL-500
controller/site installations. Existing Doors32 sites with PXL-500 controllers (now
deemed Legacy PXL controllers) can be upgraded to Doors.NET software via a
purchased license upgrade. Please contact your RSM or Keri Inside Sales person
for upgrade information.

NOTE: Sites with the following types of controllers are not eligible for upgrading to Door­s.NET at this time.

l Entraguard telephone entry controllers (including mixed PXL and Entraguard sites)
l PXL-510 controllers for alarm panel control
l LC-502/-508 controllers for elevator control

Unique to Keri NXT Mercury Powered Controllers (MSC):

l Added support for the ASSA ABLOY Aperio hub wireless lock (1 port and 8 port).
l Added support for ASSA ABLOY Sargent Profile VS2 (Wifi) locks.
l Added support for the Ingersoll Rand AD-400 series wireless lock.

Program Improvements

For All Hardware Platforms:

l Updated the MadCap Help Viewer program to the current v6.1 release.
l Added a wide variety of AXIS video plug-ins.

- 36 -

Doors.NET Reference Manual

l Corrected an issue when reassigning a door strike from a controller to a 4x4 I/O

module. The reader assignment list was not being filled with all the available read­ers.

l Corrected an issue in actively updating Access Group information between clients

when multiple clients are open. The client saving an Access Group change would
correctly display the new Access Group name; remote clients would display "New
Group" until the remote clients were closed and then re-opened. Now all clients dis­play the new Access Group name whenever changes are saved, regardless of cli­ent.

l Improved Temporary Card date resolution by including hours, minutes, seconds to

the date selection. In certain applications, a Temporary Card set for one day
access would expire immediately after being issued. The full date/time stamp
ensures one day Temporary Cards operate correctly.

l Corrected an issue where the online help file would not open when an operator

pressed F1 in certain software installations. When certain options were selected,
the online help viewer program was not properly being registered during the install­ation process. The installer has been changed to ensure proper help viewer regis­tration regardless of software installation options.

l Added several new options to the default list of entries for the Emergency Contacts

screen.

l Corrected several refresh issues with data entries in the cardholder grid not being

displayed until the cardholder grid was closed and then re-opened.

l Added a check that will not allow an Access Group to be deleted if there are still

Readers assigned to that group. This allows an Operator an opportunity to ensure
that Access Group should be deleted and to reassign any Reader assignments
that still exist.

l Increased the number of events that are posted to Live Events to include cre-

dential/reader mode changes. This allows the system to maintain a more complete
history of credential and reader activity.

l More tightly enforce the rules for disabling overrides with credential mode changes

when in the global lock and global unlock state.

l Added value comparison between minimum and maximum Strike times. Pre-

viously the program allowed these values to be set independently, and did not
check to see if an illogical entry was made (i.e., setting a maximum Strike time to a
value less than the minimum Strike time). The program now automatically
increases the maximum time if the minimum time is set to a value greater than the
existing maximum time and decreases the minimum time if the maximum time is
set to a value less than the existing minimum time. In both cases, the maximum
and minimum times will be the same.

l Added a value check to entries to the cardholder grid. If an invalid data value was

entered into one of the cardholder grid fields the grid display could go blank. The
program now checks and rejects invalid data entries.

- 37 -

Doors.NET Reference Manual

l The program now requires that a new cardholder entry be saved before attaching a

photo to that cardholder. This ensures the new cardholder entry is created in the
database, providing the proper database location for the photo to be attached.

Unique to NXT Controllers:

l Corrected an issue when in Lock-down Mode. RTE requests were being per-

formed by the system when they should not be. When in Lock-down Mode, an RTE
request should generate an event, but not be performed. Lock-down Mode now
operates correctly.

l Corrected a status display issue with RIMs when performing a Firmware Update.

When an update network was completed, the timing for requesting updated status
was performed so quickly that some RIMs had not completely rebooted following
the firmware update. These RIMs would not display on the status screen though
they had been correctly updated and were actually operating. The system now has
a slight delay between completing the update and requesting status from the RIMs
to ensure the RIMs have enough time to reboot and come back on line. Opening
the firmware update screen for NXT controllers now requests status of the con­trollers so the screen is up to date with the modules that are online.

l Added the Smart Update feature for NXT controllers. When a smart update is per-

formed only newly entered changes are uploaded to the controllers.

l Improved the tracking of updates for controllers that are offline at the time an

update is performed. Controllers are marked in the user interface as needing spe­cific updates if they were offline when the update was performed. When these con­trollers come back online, these updates are automatically performed. Successful
updates will clear these update markers and failed updates will reset these mark­ers.

l Improved the reporting of controller firmware revisions in Live Events. If a controller

failed to report its firmware revision, Live Events now reports the command failed. If
a controller reports a revision that is out of date, Live Events shows both the current
and the expected revision numbers.

l Corrected an issue where a change to a door strike time was not received by the

controller unless the gateway was restarted.

l Changed the door contact default value to No Door Contact (which disables the

call outs for strike minimum time and strike mode). This accommodates the major­ity of our customers who do not use a door contact on their installations.

Unique to Keri NXT Mercury Powered Controllers (MSC):

l Added a Special Event option to the Holiday Schedule list. This allows a one-time

special event schedule to be defined that does not affect any other existing sched­ule.

l Added support for the Assa Aperio AH-30 hub supporting 8 wireless locks with a

50 foot range.

- 38 -

Doors.NET Reference Manual

l Added firmware upgrade status messages to provide active feedback during an

upgrade.

l Added options to the System Calendar allowing a Full Cardholder Download and

an Update Network to be scheduled operations.

l Corrected an issue with setting a vacation date. Vacation Settings are used to tem-

porarily disable a credential when a cardholder goes on vacation. The program ori­ginally assumed a vacation would start at some date in the future and run some
number of days. If an operator set a credential's vacation date to begin imme­diately, that start date would not be applied correctly. The program now accepts
immediate vacation start dates.

Known Issues

l None at this time.

Firmware Requirements

For NXT controllers and peripherals:

l Standard NXT controllers require new firmware revision 2.05.23.
l NXT controllers with Mercury Inside firmware require new revision 1.01.40.
l NXT Readers require current firmware revision 3.01.01.
l Reader Interface Modules (RIMs) require current firmware revision 3.02.05.
l 4x4 I/O Modules require current firmware revision 3.00.02.

For PXL:

l PXL controllers require current firmware revision 8.6.04
l Legacy PXL controllers should be at firmware revision 8.4.49 or greater

(this minimum firmware revision is programmed with the current U.S. Daylight Sav­ings Time dates)

NOTE: Legacy PXL controllers require an optional license to be used with Doors.NET
software.

For Mercury Inside (MSC) NXT controllers:

l MSC NXT controllers require new MSC firmware revision 1.01.40.

Firmware Upgrades

Standard NXT Firmware v2.05.23

l Turns off multicast support within the firmware as the Doors.NET software does not

communicate with the NXT controller via multicast. This allows the NXT controller
to ignore an entire class of Ethernet communication that does not apply to the con­troller.

- 39 -

Doors.NET Reference Manual

Mercury Powered NXT Firmware (MSC) v1.01.40

l Corrects an issue with Assa Aperio wireless lock hubs that could interrupt com-

munication.

l Provides a method for temporary access to the web user interface. When a new

web user is added the default admin account is disabled. Should you lose the web
user password you could be permanently locked out of the controller. Now you can
press the S1 switch twice to re-enable the default web user admin account for 5
minutes.

Translations

Completed Translations:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)
l French (France)
l Polish
l Russian
l Slovenian
l Spanish (Castilian)
l Turkish

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l Italian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in US English.

Doors.NET Version 3.5.1.14

Firmware Requirements

l The standard NXT controller requires new firmware revision 2.05.22.

- 40 -

Doors.NET Reference Manual

l The NXT Reader requires new firmware revision 3.01.01 specifically to enable the

In/Out reader function. If this feature is not being used then the previous version of
reader firmware (v3.00.01) continues to be fully functional.

l The Reader Interface Module (RIM) requires new firmware revision 3.02.05.
l The 4x4 I/O Module requires new firmware revision 3.00.02.
l The Mercury Inside gateway (MSC) requires that NXT controllers have new MSC

firmware revision 136.

NOTE: Due to networking restrictions built into the Home versions of Windows operating
systems, Doors.Net software is NOT compatible with any Home version of Windows
XP, Windows Vista, or Windows 7. Doors.NET IS compatible with the Business, Pro­fessional, and Ultimate versions (both 32-bit and 64-bit) of Windows XP, Windows Vista,
and Windows 7.

New Features

l Added the ability to display a photo associated with an event in the Live Events

window. When an applicable event occurs, if the cardholder screen is open a
double-click displays the cardholder record. If the cardholder screen is not open, a
tool tip with the cardholder photo, last name, first name, middle name is displayed.

l Added the Personal Identity Verification (PIV) 75-bit format to the Wiegand library

of standard card formats.

l Added a Block Delete cardholder feature. This is useful if a Block Enrollment is

done incorrectly and needs to be deleted and performed again, saving time in the
cardholder deletion process. Block Delete is limited to 50 credentials at a time.

l Added support for the NXT-6RK keypad reader.
l Added support for keypad commands when using a Wiegand keypad with NXT

controllers with Mercury Inside firmware.

l Added support for Elevator Control when using NXT controllers with Mercury

Insidefirmware.

l Added In/Out Reader support for NXT controllers with Mercury Inside firmware.
l Added support for ASSA Aperio wireless door locks when using NXT controllers

with Mercury Inside firmware.

l Added support for Axis M1054 and M1103 cameras.

Program Improvements

l Corrected an issue where the software installer unnecessarily installed the Door-

s.NET Services Tray Application on client-only installs. This application is only
needed on the host computer running the Application Server.

l Corrected an issue with license reactivation while Internet access was unavailable

(typically done when a user adds a new licensed feature). The License Manager
would lock the program, waiting for an activation response until Internet access
was restored. The system will now allow the program to operate without the new

- 41 -

Doors.NET Reference Manual

feature addition, requiring the user to repeat the activation process when Internet
access is finally restored.

l Added a notification for the user such that if a Gateway is offline when a Syn-

chronize Clocks command is performed a notification dialog appears to alert the
user that the Gateway could not be synchronized.

l Added an automatic Gateway assignment such that when a new Gateway is

added in the Gateway Wizard, that new Gateway is automatically selected before
continuing to the activation step. Previously you had to manually select the newly
created Gateway.

l Added cut-and-paste capability when entering a starting IP address during auto-

configuration. The address field will parse the data being entered and delete it out
if invalid characters are entered.

l Disabled the Apply button during an auto-configuration. The Apply button has no

purpose during the auto-configuration process, so it is now disabled (grayed out)
during auto-configuration to minimize confusion during the auto-configuration pro­cess.

l Corrected the status update process following an auto-configuration to only collect

status on the selected controllers. This speeds up the status collection time and
does not collect unneeded data.

l Corrected an auto-configuration issue with very old NXT firmware revisions

(2.03.12 or earlier) where the software is waiting for a specific response from the
firmware that early firmware revisions do not provide.

l Added a notification regarding the proper method to change a controller's IP

address. A user cannot change a controller's IPaddress from the Communication
Setting property, it must be changed during auto-configuration.

l Increased the time out values used for firmware updates to accommodate updating

via slow, wireless networks.

l Implements an Update Network Required notification to be displayed in multiple

places when applicable. Certain types of system changes are not automatically
updated on the network. These notifications alert the Operator to the need to per­form a manual update when ever necessary.

l Corrected a settings issue with keypad readers where if you changed to a non-

standard setting the keypad reader would work correctly, but if you made a sub­sequent change to any other reader value, the keypad reader would revert to
default settings.

l Corrected a display issue under Access Groups where Keypad readers were listed

by code number and not manufacturer model.

l Corrected an interface display issue where the correct state for disabled readers

was not displayed properly following an auto-configuration until the user client was
restarted.

l Corrected a Controller status issue that prevented the Reader status from being

properly displayed under certain conditions.

- 42 -

Doors.NET Reference Manual

l Corrected an issue with Access Groups that allowed multiple Reader assignments

in an Access Group for Readers on buses 2, 3, or 4.

l Added time duration information to the Lock Out Duration parameter for keypad

readers. The tool tip associated with this field now explicitly states the time out is in
minutes.

l Removed the facility code field from the Credentials window for NXT credentials.

NXT credentials do not use a facility code field.

l Added a Close button to the Block Enrollment window that is enabled once a block

enrollment command is performed. The Block Enrollment window has the oper­ating system default "X" box to close the window, but adding an explicit Close but­ton makes the process more obvious.

l Restored a missing card number field to cardholder reports. When running a report

on cardholders, if you selected the card number column to be included in the
report, the reported value came up blank. When selected, the report now shows the
card number for the cardholders.

l Suppressed a spurious "No Search Results Found" warning message that would

appear in brand new software installations where no cardholders have been
enrolled. This message is now suppressed if there are no cardholders in the data­base.

l Increased the number of characters allowed in the Contact and Company data

fields under cardholders from 50 to 256.

l Corrected a credential editing issue that prevented an operator from manually

adding a credential to a cardholder record immediately following a credential dele­tion operation. Previously the credential deletion locked the credential fields and
required the operator to exit then reenter the cardholder record. This is no longer
necessary.

l Increased the number of characters allowed for cardholder address entry from 50

to 256.

l Corrected an issue such that any change entered for cardholders prompts a data-

base save operation. This ensures that all changes have the opportunity to be
saved.

l Corrected an issue in changing the Expiration Date for credentials once an Expir-

ation Reason has been added; adding a reason prevented the date from being
changed.

l Added an auto-fill feature when presentation enrolling credentials. All information

gleaned from the presentation enrollment is now automatically inserted into the
appropriate credential fields in the database.

l Corrected data field display issues when using Presentation Enrollment. Depend-

ing upon enrollment type, certain field values would reset to default or null values
between steps in the operation.

l Corrected a display issue when enrolling MS credentials where the credential

imprint number was not being automatically entered in it's field on the GUI.

l Added the ability for the operator to edit the description of card formats.

- 43 -

Doors.NET Reference Manual

l Added more options to the context menus used when creating an email/SMS mes-

saging macro. This makes it easier to include a greater variety of information to
these types of messages.

l Corrected operator permissions when setting holidays or time schedules. An oper-

ator with view-only permission for these two fields was still able to add new hol­idays or time schedules.

l Removed the default password when confirming Intrusion device type Alerts. The

use of passwords for confirmation is optional.

l Corrected a display issue under Local Linkage triggers where readers were listed

by bus number and not by reader name.

l Corrected an issue where certain user interface screens would not update their

data in real-time. You had to close and then reopen the screen to get current inform­ation.

l Changed the Request to Exit default setting from Disabled to Momentary.
l Corrected several language translation text errors.
l Corrected an issue with the Hardware Browser where the Save All button did not

highlight when more than one hardware change was made.

l Corrected an issue where there were certain categories of events that would not

activate Alarm Sounds when sounds were assigned to these events.

l Moved all line supervision settings to the Advanced View feature set as line super-

vision is not a commonly used feature.

l Corrected an issue where certain 3-state and 4-state supervision events were not

being reported correctly.

l Changed the descriptions of certain local linkage actions to be more descriptive of

the action.

l Corrected an issue where changes to a link action pulse time were never recog-

nized; the pulse time never varied from the default value.

l Added an automatic Access Group assignment such that if an operator is allowed

to create a new Access Group, that operator will automatically be allowed to
assign that Access Group to other users.

l Corrected an issue in reporting the Credential Lock Out event in the Live Events

window. This event is generated when the maximum number of PINattempts are
made on a keypad reader.

l Corrected the timing on Door Held Open events. The Door Held Open timer had

been set to start when the door lock is energized. This resulted in the Door Held
Open time functionally being the same as the Door Strike Time. Timing has now
been changed such that the Door Held Open timer now starts when the Door
Contact shows the door has been physically opened.

l Removed the requirement to select a day-of-the-week when setting a Master

Schedule. This allows a schedule to be created based only on time interval and
holiday type.

l Corrected an issue where the Situation Manager did not properly handle a specific

security level switching option. The system would correctly switch from less secure

- 44 -

Doors.NET Reference Manual

Card-Only to more secure Two-Card required, but would not switch back to the
less secure option.

l Standardized the wording for all Situation Manager states and all related event

messages.

l Corrected an issue where setting Operator Permissions did not correctly handle

permissions for System Options.

l Provided a warning that when making changes to operator permissions, these

changes will not take effect until the client has logged out and logged back in.

l Corrected an Operator Permissions issue when working with credential Block

Enrollment. Block Enrolled credentials are assigned to No Access Group. An oper­ator who has been granted restricted permission to view Access Groups may not
be able to view credentials assigned to No Access Group. These operators are
now able to view this group of credentials only on the All Cardholders report or
when first entering the cardholder menu.

l Changed the way Operator Permissions can be set for System Administrator

accounts. It had been possible for an Operator to set Permissions for all Operators
in a manner that disallowed ALL Operators access to Operator Permissions. This
meant that no further Permission changes could be made for any Operator. Now
the software will allow Operator Permission changes to be made to all other Oper­ators, but not to the Operator making these changes. This ensures that at least one
Operator retains full Permission changing ability.

l Corrected an issue with Reports for all Readers. If a Reader was offline, it would

not be included in the report.

l Changed the text for NXT controller reader status from device online/offline to

reader online/offline. This improves report readability and is consistent with what is
reported for Mercury Inside controllers.

l Added flexibility to client reports by changing from fixed report date periods of 1 to

4 weeks to flexible date report periods of 1 to 30 days.

l Improved the method by which controller events can be searched when creating

reports. Events can now be searched by either server time stamp or controller time
stamp.

l Set default start and end dates in the Reports feature to display the current day.

This is a requested convenience when generating reports later in the year as it
saves the user from having to step through calendar settings that begin at the first
of the year.

l Corrected an issue when searching by User Groups. Searching does not work

when multiple user groups are assigned to cardholders.

l Set data filtering to default to filtering by controller. This can be changed to be spe-

cific to reader, input, output, etc.

l Corrected an issue with text searches in Property Filters. If you entered text into the

Property Filter search field that is not present in the Property, the Property window
stops responding. The Administrative client had to be restarted to restore func­tionality.

- 45 -

Doors.NET Reference Manual

l Corrected an issue when creating monitoring filters. Certain filter types would not

save properly, rendering those filters unavailable.

l Corrected an issue when applying either the Mask Forced or Mask Both filters. A

Reader Contact - Door Closed event message would display in Live Events, but its
corresponding Reader Contact - Door Opened event would not. Both events now
appear in Live Events in proper order.

l Corrected an SQL issue where database backups would only be successfully per-

formed if the default backup name was used.

l Corrected a database issue where the database was not updated in a timely man-

ner following a controller deletion, allowing stale information to be displayed in the
grid.

l Corrected default settings for the Vivotek video driver.
l Corrected a positioning issue with the Photo Recall feature where horizontal dock-

ing would come up initially in a vertical orientation. Horizontal docking now comes
up in the correct orientation all of the time.

l Corrected a template display difference between the program client and the Photo-

ID client that could make it difficult to properly edit the template.

l Removed the Factory Defaults option from the Mercury Inside controller options

pull-down list as it does not apply to this controller type.

l Corrected a Mercury Inside gateway issue that had the Gateway Wizard auto-

matically assigning a default Mercury controller type to the gateway, even if None
was selected.

l Corrected an issue when assigning an IPaddress to a controller with Mercury

Inside firmware. When configuring a panel and assigning an IPaddress, you must
save the IPaddress before performing other tasks. The warning message to alert
the user to this requirement was not appearing when needed, allowing a user to
make other changes that invalidate the IP address assignment.

l Corrected an issue with the Request Status command when using Mercury hard-

ware or NXT hardware with Mercury Firmware. Not all status fields would be
updated and the controller date stamp would not be updated.

l Corrected a parameter update issue with NXT controllers using Mercury Firmware.

Certain parameter changes require the controller board to be reset, and this wasn't
always being announced to the user. When necessary, the program now will auto­matically perform the reset as a part of the parameter save operation.

l Extended IP addressing support in the Gateway for Mercury products.
l Added Suspend/Restore functions for Door override functions on NXT controllers

with Mercury Firmware.

Known Issues

l Door strike outputs cannot be reassigned from a controller to a 4x4. This should be

allowed in the software, but when you assign a 4x4 output to be a "Strike," the cor­responding drop-down list is not displaying the Readers that can be reassigned to

- 46 -

that output. This only applies to new reassignments. If you upgrade the software
from a previous revision and have these types of reassignments applied, they cor­rectly remain active. You just cannot make new assignments.

Translations

Completed Translations:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)
l French (France)
l Polish
l Russian
l Slovenian
l Spanish (Castilian)
l Turkish

Doors.NET Reference Manual

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l Italian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in US English.

Required Firmware Upgrades

Standard NXT Firmware v2.05.22

l Corrects an issue where presenting the same credential to a Reader multiple times

would cause the Controller to process the same credential data multiple times,
delaying the controller from processing data from a new credential. This additional
processing time, in turn, would delay the unlocking of the door for the new cre­dential.

l Corrects an issue with incremental credential adds and deletes that prevented

some credentials from being granted access until a full card holder database
update was performed.

- 47 -

Doors.NET Reference Manual

l Adds the ability to change the Server ID, Controller ID, and Network Data using Tel-

net commands. This feature can be useful when configuring Controllers that are
spread out over a WAN.

NXT Reader Firmware v3.01.01

l Provides support for In-door/Out-door Readers (also known as Master/Slave Read-

ers). This feature allows two Readers to be managed from one bus on the Con­troller, with both readers controlling one door; one Reader for the In/Entry direction
and one Reader for the Out/Exit direction. A Reader with this firmware revision or
greater can be toggled between In-door and Out-door configurations. This is done
by presenting an NXT Address Change Control Card to the reader within the first
60 seconds of reader power up.

NOTE: Having two Readers of the same configuration on one bus (both In-door or both
Out-door) is an illegal configuration resulting in neither Reader being recognized or
acknowledged by the system.

RIM Firmware v3.02.05

l Provides support for the Keri NXT-6RK Proximity Reader and Keypad.
l Provides support for reading 75-bit Wiegand Credentials. In this application the

Expiration Date is stripped from the data bits and just the binary 48-bit credential
value is sent to the Controller.

l Changes the handling of the * and # keys on Wiegand key pads to support the use

of special commands on NXT controllers using Mercury Inside firmware.

4x4 Firmware v3.00.02

l Provides complete hardware information when a status command is performed.

Mercury Inside (MSC) Firmware v136

l Remembers the controller's assigned IP instead of resetting the IP to a default

value whenever the controller is reset.

l Provides support for In/Out NXT Readers.
l Provides support for Assa Aperio wireless locks.

Doors.NET Version 3.5.1.12 - SP-2

Doors.NET v3.5.1.12 requires an NXT controller firmware upgrade to v2.05.16.

- 48 -

Doors.NET Reference Manual

NOTE: Due to networking restrictions built into the Home versions of Windows operating
systems, Doors.Net software is NOT compatible with any Home version of Windows XP,
Windows Vista, or Windows 7. Doors.NET IS compatible with the Business, Pro­fessional, and Ultimate versions (both 32-bit and 64-bit) of Windows XP, Windows Vista,
and Windows 7.

New Features:

l Implements the Mercury Inside/NXT firmware feature set which enables a new set

of features for applications with more sophisticated and customized requirements.
This broadens the scope of NXT hardware capability such that it makes it a good
choice for high-end and Enterprise applications as well as mid-sized projects.

l Implements the Global Lock/Unlock feature which allows a defined input (either

hardware or as part of the user interface) to immediately lock or unlock selected
doors in the access control network regardless of any current lock or unlock status.

l Implements Block Enrollment which allows an Operator to create a generic set of

credentials (using consecutive credential numbers) that can be, in turn, issued on
an as-needed basis.

l Improves/Simplifies the Software Installer. This revision reduces the number of

installation options and adjusts the order of operation to simplify and streamline the
installation process. It checks the host computer to ensure the computer meets soft­ware operation guidelines and includes acknowledgement windows so the
installer can double-check the installation parameters before starting the install­ation. For upgrade installations it remembers previous installation settings and
applies these settings as the defaults for the upgrade. For software upgrades of
existing installations it checks the firmware version of installed hardware and noti­fies the installer if firmware upgrades are required.

l Implements NXT controller auto-configuration over a Wide Area Network (WAN)

without the need of additional gateways for each subnet. This allows NXT con­trollers in one installation to be located on different subnets, but to still be recog­nized and auto-configured by the Doors.NET program. Previously, one gateway
would be needed for each subnet to provide a communication path from the host
computer to the remotely located controllers. This feature requires that IP routing is
correctly configured between the subnets using their internal IP addresses.

l Adds support for the following features to Eclipse software and the Mercury hard-

ware/gateway:

l First Person In
l Auto Unlock Schedule
l Dual Verification
l Mask-During-Schedule
l Follow Schedule
l Set Holidays by Controller
l Link Actions on Monitor Point
l Various new scheduling options for Control Points and Monitor Points

- 49 -

Doors.NET Reference Manual

l Ingersoll-Rand / Schlage AD-Series wireless locks
l Support for reverse bit patterns for specific types of Magstripe and Wiegand

format readers

l Adds P-640 Wiegand keypad reader support.
l Adds more information when displaying Local Linkage states to better annunciate

current status.

l Adds the ability to drag-and-drop controllers in the Hardware Browser. This makes

it easy to move existing controllers to a new gateway during system expansion.

l Adds sort order options to user defined entries on the Hardware Browser. Provides

greater flexibility when sorting and searching in the Hardware Browser.

l Adds a Reset sub-menu for controllers on the Hardware Browser. This allows one

of three types of resets to be performed via the software: basic, memory, factory
reset. Warning dialogs are provided to ensure the operator does want to perform a
reset.

l Adds a number of reporting and diagnostic messages to the gateway.
l Adds a number of cardholder text selection fields to the Photo ID client.
l Adds an ONSSI video plug-in.
l Adds a Pelco video plug-in. This plug-in is only compatible with 32-bit operating

systems.

l Adds a Vivotek video plug-in.

Released Translations:

Full translations are provided for the following languages:

l Chinese (Simplified)
l Chinese (Traditional/Taiwan)
l English (UK)
l Polish
l Slovenian
l Spanish (Castilian)
l Turkish

- 50 -

Doors.NET Reference Manual

Program Improvements:

l Corrected typographical and display field errors in several program windows.
l Corrected information field sizing issues that appear when using non-English lan-

guages.

l Re-enabled sorting by Access Group for transaction reports. Please keep in mind

that cardholders who are assigned to multiple Access Groups may not sort as
expected.

l Added a gateway identifier to the Access Group assignment screen to eliminate

confusion on gateway assignments. If an operator had assigned identical names to
controllers on different gateways it could be difficult to assign the desired Access
Group to the correct controller/gateway combination. To correct this a gateway iden­tifier has been added to the controller information displayed on the Access Group
screen.

l Now automatically divides event history archives into manageable sized files.

Adds the ability to selectively search through and report onevent transactions by
archive. Reports are presented on a per archive basis and cannot span multiple
archives. These changes increase the speed of sorting and searching. All sorting
is now done on the event history grid.

l Corrected the reporting of RIM and 4x4 firmware revisions in the individual device

listings in the hardware tree following an Auto-Configuration. The firmware revision
for these devices would be listed in the controller tree, but no value would be
shown under the individual device trees.

l Improved the Temporary Cardholder time resolution to correctly handle short-term

credentials (i.e. the credential has a short activation period and it becomes active
in a short amount of time).

l Corrected a speed-of-processing issue when multiple, single-card presentation

enrollments are done back-to-back. Some cards may have been dropped from the
enrollment process.

l Corrected a speed-of-processing issue when multiplecontrollers are added manu-

ally. If the controller additions were made too quickly the hardware trees displaying
the individual controller peripherals (such as readers) would not be filled correctly.

l Corrected an issue with displaying reader names when using a 4x4 to handle door

strikes for a controller. A hard-to-interpret ID number was displayed rather than the
reader name assigned to the door strike.

l Corrected an issue when assigning door contacts on a 4x4 relay board. The

assignments on the 4x4 would not be completely implemented until the operator
also saved corresponding changes on the corresponding reader. The program
now prompts the operator to save all changes.

l Corrected an issue when an installer removes a 4x4 module from an installation;

the program would remove the 4x4 without checking if any programmed inputs
were assigned to that 4x4. The program now checks for 4x4 programming and

- 51 -

Doors.NET Reference Manual

prompts the user to redefine that programming prior to removing the 4x4 from the
system.

l Corrected an issue with Doors.Net/Eclipse installations when using the Windows 7

operating system. In certain systems the Doors.Net/Eclipse software could not
retrieve the name assigned to the computer.

l Corrected SMS settings for Cingular and US Cellular carriers.
l Corrected an issue with the Confirm Alert button state on the host software. The

Alert Confirm button on the host software now correctly annunciates if a remote cli­ent has performed the alert confirmation.

l Corrected an issue with the application of host schedules on holidays to ensure

that schedules that are marked as inactive on holidays are not performed.

l Corrected an issue when attempting to download multiple holiday types that forced

a user to download one holiday type at a time.

l Corrected an issue where if multiple holidays were activewith the same start date

and one of these holidays was disabled, all holidays on that date were disabled.

l Corrected an issue where attempting to open the same report window multiple

times consecutively would hang the report window.

l Corrected an error when creating cardholder history reports. If the report was for

only one cardholder, certain search parameters would not return any information.

l Corrected an inconsistency when reporting on access granted events. Time &

Attendance access granted events were not being highlighted in green on the Live
Events screen as other access granted events were. These events are now high­lighted in green to match all other access granted events.

l Now posts Network Update progress messages as a part of Live Events for better

tracking of update progress.

l Corrected the operation of the "airlock" (man-trap) feature used with Mercury hard-

ware.

l Corrected a program login condition where if the program was unable to open, the

login routine would continuously retry. The login routine now retries five times and
if the program login screen does not open an error message is displayed.

l Corrected message handling should the SQL server be offline. The program now

recognizes when the SQL server is offline, correctly handles messages during the
offline state, and posts a user-friendly message to alert the operator.

l Corrected a multiple client connection issue with the Application Server. Should

the Application Server need to be restarted while multiple remote clients are con­nected and an operator then closes and later reopens one of these remote clients,
that remote client would not reopen.

l Corrected an issue with Local Linkage where a link definition would display if an

output point relay was off, but not if the output point relay was on. Now the linkage
definition always displays the relay state.

l Corrected an issue with GlobalLinkage where certain configuration parameters for

a newly created linkage were not being saved correctly.

l Corrected an issue in Operator Permissions where the permissions window would

not allow any operator permission value to be changed from "Full Control."

- 52 -

Doors.NET Reference Manual

l Separated the operator permissions for viewing credential activation dates from

viewing credentials themselves, creating two separate operator permissions.

l Disabled the ability to select a time interval for First Person In when the First Per-

son In feature is not enabled.

l Standardized the Archive Service date/time value format. All archiving is now done

in ISO 8601 format, eliminating confusion when reviewing data stored by the
Archive Service.

l Corrected an issue with the gateway’s monitoring queue when a controller's IP

address has been changed. The monitoring queue would poll for both the old and
new IP addresses. The old IP address is now removed from the polling queue
speeding up queue polling time.

l Improved the usability and speed-of-operation of the Reflections video feature.
l Corrected issues with the Panasonic video plug-in, addressing a connection issue

and recognizing/restarting stalled video streams when all streams are routed to the
same PC.

l Corrected issues with PhotoID where operator permissions were not always prop-

erly applied; not allowing operators who were not also system administrators to per­form certain actions.

l Now allows MAC address entry using either colons or dashes to separate char-

acters and is case insensitive. Also does not allow entry of invalid IP address char­acters.

Translations Pending Updates *:

l Arabic (UAE)
l Dutch (Belgium)
l French (Belgium)
l French
l Italian
l Russian

* These translation file sets are not yet complete pending submissions from our trans­lators. If you use these translations you will find mislabeled and/or non-translated ribbon
and menu fields in some sections of the program. Non-translated fields will be displayed
in USEnglish.

Known Issues:

l There is a communication time out issue in that a communication attempt can

timeout before it is completed on a slow network such as a wireless network or
VPN, or if a very large number of credentials are sent to a controller.

- 53 -

Doors.NET Reference Manual

NXT Firmware Version 2.05.16

l Corrected a controller power-up issue that could energize a 4x4 relay during the

power up process.

Doors.NET release version 3.5.1.11

New Features:

l There are no new features included in this release.

Program Improvements:

l Corrected an issue with the Archive Service that caused the service to create an

excessive number of databases in support of the archiving process.

l Corrected a Global Linkage licensing issue that incorrectly applied optional global

linkage features.

l Corrected a reader configuration issue where if the only configuration change

being downloaded to a controller is for a reader's LED Mode, the change would not
be downloaded.

l Provided more space in certain drop-down menus to display more menu descrip-

tion information.

l Corrected a login issue where possible language translations without culture

descriptors will no longer be displayed. An example of this is a language call-out
that just says English; the translation option must specify between US English and
UK English to accommodate cultural differences in how information is displayed.

l Changed the ordering of tabs in Global Linkage to a more logical progression.
l Corrected an issue with the mapping of door contacts for NXT 2-door controllers.

Known Issues:

l There is a communication time out issue in that a communication attempt can

timeout before it is completed on a slow network such as a wireless network or
VPN, or if a very large number of credentials are sent to a controller.

Doors.NET Version 3.5.1.10

New Features:

l An SQL database backup feature has been implemented. A full SQLbackup can

be performed at any time, manually from the user interface by the System Admin­istrator (Tools > Utilities >Backup). Backups can be scheduled via the system cal­endar as well. On the system calendar, the backup options are full or incremental.

- 54 -

Doors.NET Reference Manual

The system calendar option is licensed separately but include more features than
just the backup option.

Program Improvements:

l If a user executed the same save command, multiple times, back-to-back, com-

mand communication would fail and report a timeout. Checks have been imple­mented to filter out multiple instances of the same command.

l The NXT Gateway failed with an exception if a RIMor a GIOX firmware upgrade

command was performed multiple times, back-to-back. Checks have been imple­mented to filter out multiple instances of the same command.

l Corrected an error when creating a Trigger in local linkage, if you select a variable

to be false and select save, the "false" value would not be saved.

l The Time Stamp when viewing controller status was not updating. The NXT Gate-

way has been updated to include sending the timestamp as part of the controller
status report.

l Improved NXT Gateway data throughput when handling large numbers of readers

and cardholders.

l Added checking to the System Update process to verify that if there has been no

changes to a database, there is no need to update that database.

l The software installer now checks for an open client before performing an install-

ation. If a client is open, the installer presents a dialog box requesting the client be
closed before the installation can continue.

l Improved the process by which the software installer removes a previous install-

ation prior to performing a new installation.

l Corrected the Gateway Wizard tab order to correctly follow the flow of operations.
l The software installer did not properly configure the UK English language set for

operators who selected UK English.

l Improved cardholder access rights configuration. Following a specific set of oper-

ations, cardholder access rights could be reset to default values.

l With the Time and Attendance option enabled, the Rollcall/Tracking feature did not

properly follow cardholder state through In/Out readers.

l When in monitor mode, the Gateway would continue to send events to the Applic-

ation Server when the Application Server was off line. The Gateway now recog­nizes if the Application Server is off line and halts monitoring mode.

l The Application Server time stamp showing in the Auto-config status message did

not match the computer's time. It was off by the difference between local time and
GMT. The Server time now correctly adjusts for the GMT difference.

l If you let the system auto generate PINs, you could not change from default value

of 6 digits. The program should now allow you to set the number of digits and then
auto generate PINs.

- 55 -

Doors.NET Reference Manual

Firmware Updates for Hardware Components:

RIM v03.01.11

l Under certain conditions, typically when “hot-swapping” readers or in unusually

EMI noisy environments, the RIM’s Data0 and Data1 lines could be pulled into a
both-lines-low state. This is illegal per the Wiegand specification, and because of
this it was not properly managed by the firmware. Changes were made in the firm­ware to recognize this state and prevent this condition from being processed.

Known Issues:

l There is a communication time out issue in that a communication attempt can

timeout before it is completed on a slow network such as a wireless network or
VPN, or if a very large number of credentials are sent to a controller.

Doors.NET Version 3.5.1.9

New Features / Improvements:

l The Admin Client now has a video camera configuration option.
l An Applet Tray feature has been added allowing for direct and easy management

of the Doors.NET services used by the program.

l A basic, context sensitive version of Online Help has been added.
l Revision-to-revision software upgrades are now fully handledby the installer.

Program Corrections:

l The Default Administrator could change its account type which meant the Default

Administrator could change its own permissions and no longer be able to control
other operator or application permissions. This is no longer allowed for the Default
Administrator.

l When updating controller status, the Gateway was not returning a time stamp for

the returned controller status.

l When a controller with peripheral hardware was removed from a system, the con-

troller was correctly removed from the database, but the inputs and outputs for the
controller's peripherals were still listed in the database. Peripheral hardware is
now correctly removed.

l When setting an alert to require a password on confirmation, the Confirm button

was not enabled after entering the password.

l The GIOX Firmware Upgrade revision list did not differentiate between GIOX firm-

ware and any other firmware revision. It now lists only GIOX firmware revisions.

l If an alert was marked as In Progress the next alert to follow would not give the

alert sound, but all subsequent alerts would.

- 56 -

Doors.NET Reference Manual

l When setting operator permissions to View Only, certain permissions were not cor-

rectly applied.

l The Search Cardholder by Card Number option was not performing search oper-

ations correctly.

l When enrolling cardholders, the Imprint field could get locked out preventing input

after selecting a credential from one cardholder and then selecting a different card­holder.

l The Local Linkages screen would not update properly following User Group name

changes.

l NXT Readers could be listed as RIMs on the Firmware Upgrade screen.
l In certain circumstances Wiegand presentation enrollment would enroll the imprint

number and not the internal credential number.

l A device selected for a Firmware Upgrade from the Hardware Setup > Panels or

All tab will now remain selected when the Firmware Upgrade tab opens.

Known Issues:

l There is a communication time out issue in that a communication attempt can

timeout before it is completed on a slow network such as a wireless network or
VPN, or if a very large number of credentials are sent to a controller.

Doors.NET Version 3.5.1.8

New Features / Improvements:

l The program can now display live video by device type without an alert (video

popup).

l Implemented basic and advanced program modes, hiding less often used tasks

from the user unless specifically enabled.

l Added basic local linkages.
l Added I/O board support.
l Added "Auto-USB" support, a new feature that simplifies the NXT controller IP con-

figuration task by providing a network package that makes the configuration task a
virtual plug-and-play application.

Program Corrections:

l Corrected data entry issues with the credential imprint number field.
l Corrected miscellaneous typographical errors.
l Implemented several usability improvements.
l Corrected docking issues with the Photo Recall feature.
l Corrected a memory leak caused if the gateway could not authenticate with the

server. This issue could cause the program to crash.

l Opened the Door Held Open value from a 255 second limit to 18h 12m 15s.

- 57 -

Doors.NET Reference Manual

l Changing filter settings required a unique password and not the standard system

administrator password. Now the system administrator password works for allow­ing these changes to be made.

l Corrected a screen refreshing issues that required a window close/open to see

newly entered values.

l Expanded certain field name sizes to accommodate long name strings.
l Corrected an issue where you could not remove/replace a photo from the Photo

Recall client.

l Corrected an issue where an update command would reset temp cards expiration

date.

l Implemented a character check to prevent the MAC address field from accepting

invalid characters (I versus 1 and O versus 0).

l Corrected an issue where incorrect PIN values were saved when chan-

ging/entering multiple PINs simultaneously.

Firmware Updates for Hardware Components:

RIM v03.01.10

l General improvements to timing and credential decoding algorithms.

Known Issues

l There is a communication time out issue in that a communication attempt can

timeout before it is completed on a slow network such as a wireless network or
VPN, or if a very large number of credentials are sent to a controller.

l The Report Client custom option will not install properly unless the Milestone cus-

tom option is also installed.

- 58 -

Doors.NET Reference Manual

Technical Support

Keri's highly experienced and knowledgeable staff provides technical support world­wide.

U.S. Support:

l Office hours: Monday through Friday (6:00 AM to 5:00 PM, Pacific Time)
l Phone: [phone] or 1-408-435-8400 - When the phone greeting begins,

press 2 to enter the Tech Support queue.

l [e-mail] - We will respond within two working days, excluding

Saturday and Sunday.

UK, Ireland, Europe Support:

l Office hours: Monday through Friday (8:30 to 17:00, UK Time)
l Phone: [phone] - Press 2 for Tech Support
l [e-mail]

Africa, Asia, and Middle East Support :

l Office hours: Sunday - Thursday (8:00 - 17:00, Beirut, Lebanon Time)
l [e-mail]

Training Videos

We have a corporate YouTube account that hosts a selection of useful Doors.NET
related videos:

l https://www.youtube.com/user/kerisystems

- 59 -

Doors.NET Reference Manual

Software Installation

Doors.NET installation and controller configuration is a three step process. Each of
these steps has its own section, with controller configuration broken into separate doc­uments per hardware type.

1. Install the software (see below), which will also automatically install Microsoft's
SQLServer Express ® (a free SQL server program) if the PC does not already
have SQL available.

2. Activate the License and register your software using the License Manager utility.

3. Configure the Gateway using the Gateway Wizard utility.

Installing the Software

Doors.NET software installation can be done either via DVD or online via the WebIn­staller.

Installation via DVD is the quickest way as all necessary installation files are on the
DVD.

Via WebInstaller

If you do not have a Doors.NET DVD the WebInstaller links directly to an online version
of the installation program. This is a slower process as files are downloaded from the
Keri web server on an as-needed basis. Contact your Inside Sales Representative to be
given access to the download link. Download and run the WebInstaller program to start
the Software Installation. Any supporting files required to complete the installation are
downloaded via the Internet from the Keri web site, hence, installation via WebInstaller is
a much more time consuming process than installation via DVD as this process is based
on your Internet connection speed and reliability. A high-speed Internet connection is
recommended when using the WebInstaller.

Via Doors.NET Installation DVD

1. Insert the Doors.NET Software Installation DVD and the AutoRun program begins.

- 60 -

Doors.NET Reference Manual

NOTE:Navigate to the DVD's root directory and run the autorun.exe program if this
menu does not appear.

l Click the Keri Logo to open your web browser and visit the kerisys.com web site.
l Click View Release Notes to view a Readme.txt file with information on this soft-

ware release.

l Click Install Software to install Doors.NET.
l Click Installation Document Set to open an Explorer window with a set of doc-

uments covering basic installation.

l Click Technical Documentation to open an Explorer window with technical doc-

umentation.

l Click Marketing Documentation to open an Explorer window with marketing doc-

umentation.

l Click View Training Video to open an Explorer window of Windows media video

files.

l Click Exit AutoRun to close the AutoRun window.

2. If you are upgrading an existing installation the installer program first reviews the
firmware revisions for the hardware in the program database and notifies you of
any required firmware updates. Click START to begin the software installation. A
new installation skips this step.

- 61 -

Doors.NET Reference Manual

3. Once started, the installer performs a quick installation file verification and pre­pares the file set for installation.

4. The Welcome Window appears when the installation is ready to begin.

- 62 -

Doors.NET Reference Manual

5. Review the version listing to confirm the revision of the software to be installed.

6. Click NEXT to continue to the License Agreement.

NOTE: You must accept the terms of the License Agreement to install this software. Keri
recommends reading through the License Agreement in its entirety before accepting the
terms.

- 63 -

Doors.NET Reference Manual

7. Click the check-box to accept the License Agreement.

8. Click NEXT to enter Customer Registration information.

- 64 -

Doors.NET Reference Manual

9. Enter your User Name and (optionally) an Organization Name.

10. Click NEXT for Hardware Selection.

- 65 -

Doors.NET Reference Manual

11. Click the radio button corresponding to the controller type being used in the sys­tem.

l Keri NXT for standard NXT controllers.
l Keri NXT (Mercury Powered) and MSC for either NXT controllers using Mercury

firmware or for Mercury hardware controllers.

l Keri PXL for PXL controllers.

12. Click NEXT to select your Type of Installation.

- 66 -

Doors.NET Reference Manual

13. Click the Radio Button corresponding to your Type of Installation.

l A Full Installation installs all software components for a standard installation onto

the PC.

l A Basic Installation installs only the user client onto the computer.
l A Basic Installation with Hardware Driver installs the user client and the relevant

hardware gateway onto the computer. Use this option if your user client is on a dif­ferent subnet than the PC with the full installation.

l A Custom Install allows you to select additional applications to be installed. This

can include optional licensed applications beyond those included in the standard
installation package.

14. Click NEXT to verify the installation parameters.

15. Review this list carefully as it explicitly states what will and will not be installed on
your PC.

l A list of items to be installed is displayed in GREEN.
l A list of items that will not be installed is displayed in RED.
l If this list is not correct, click BACK and review the Type of Installation options.

16. Click the checkbox to confirm the installation parameters are correct.

17. Click NEXT to select the Destination Folder. This is the folder into which the Door­s.NET software is installed.

- 67 -

Doors.NET Reference Manual

18. The default destination folder is listed in the destination folder field. Keri recom­mends using this folder for the software installation. If a different destination folder
is desired than the default, you may use the Explorer window to locate the desired
folder. Once located, double-click on the folder name to enter the folder name into
the destination field.

19. Click NEXT to select the types of program shortcuts to be installed on the com­puter.

- 68 -

Doors.NET Reference Manual

20. Use the radio buttons to select if software access is to be granted to:

l Current User Only (the user logged into the PC)
l All Users of the Computer (any user logged into the PC)

21. Use the checkboxes to select any combination of:

l Desktop icon
l Start Menu folder
l Quick Launch Toolbar

22. Click NEXT to install the Doors.NET database.

23. The installer lists if it detects an SQL Server is available on the host PC. There are
three options based on what the installer finds:

l Install the Database on this computer - this is the default option. If the Installer

detects an existing SQL application, its revision is listed. If there isn't an SQL
Server available on the PC, then Microsoft's SQLServer Express® (a free SQL

- 69 -

Doors.NET Reference Manual

server package) will be installed and then the database will be installed.

l Scan the Network for Existing SQL Servers - allows the installer to search all

accessible network folders for an SQL application and installs the database on that
network folder. Using this option requires that the network folder always be avail­able for the PC/Doors.NET program.

l Install the Application Server only - requires a Manual database installation. This

option is recommended only for installers who are very familiar with SQL.

NOTE: SQL management tools are automatically installed with Windows operating sys­tems prior to Windows 8.
With Windows 8 they must be installed separately. If you are installing on Windows 8 an
additional tick-box appears, “Install SQL Management Tools” (highlighted in red in the
above graphic - you will not see this tick-box in non Windows 8 operating systems). Keri
recommends checking this tick-box and installing the SQL Management Tools. This
allows you to detach, relocate, and attach Doors.NET databases.

24. Click NEXT to confirm you are ready to install the software.

25. A progress bar keeps you informed on the installation process. There are several
steps during the installation process where there may be a delay of several
minutes. Please be patient as the software installs.

26. If you are upgrading the software from a previous revision the existing system data­base may need to be upgraded as well. If so, the database upgrade program will
automatically run once software installation is complete. A new software install­ation will not perform this step.

- 70 -

Doors.NET Reference Manual

27. The installation process is complete once the software is installed, and a new data­base is created or an existing database is upgraded.

28. Click FINISH to close the Installation Window.

29. If you opted for a desktop icon, the shortcut icon is placed on your desktop.

- 71 -

Doors.NET Reference Manual

The software is now installed and ready for licensing and gateway configuration.

- 72 -

Doors.NET Reference Manual

License Manager

The License Manager activates your software allowing use.

Retrieve the License Key

A license key is provided with the software DVD case, but this key is only valid for new
NXT controller installations. For PXL and Mercury Powered NXT controller installations
you must get a license key from Keri Inside Sales. Further, there are extended, optional
features that may require a license key update. This applies to all controller types.

NXT License Key

The NXT license key is typically retrieved from the software DVD case.

PXL License Key

A PXL license key must be obtained from Keri Inside Sales. The PXL license key sup­ports two types of PXL controllers:

l Standard – supported immediately with no restriction on the number of controllers
l Legacy – limited to a licensed number of controllers

Before contacting Keri Inside Sales for a license key, you need to know the number of
Legacy PXL controllers you have.

Identifying Standard versus Legacy PXL Controllers

The PXL controller’s model number label identifies if the controller is Standard or
Legacy (refer to the figure below). Standard controllers work directly with Doors.NET
using a standard license. There is no controller limit when using Standard controllers.

Legacy PXL Controllers

Legacy controllers require a PXL Legacy Count to be set on the license key to enable
the controllers to work with Doors.NET. By default this value is set to zero. Typically

- 73 -

Doors.NET Reference Manual

Legacy controllers are carrying over from an existing Doors32 installation that is being
upgraded to Doors.NET. There is a per-controller fee for licensing Legacy controllers.

Legacy PXL controllers must be at firmware v8.4.49 or greater. This firmware revision is
the earliest to implement the current U.S. Daylight Standard Time dates and has the
PXL’s complete anti-passback implementation. A CU500 firmware upgrade is available
for all PXL controllers to bring them up to the current firmware revision.

Mercury Powered NXT License Key

A Mercury Powered NXT license key must be obtained from Keri Inside Sales. The Mer­cury Powered NXT license is limited to a licensed number of controllers. Before con­tacting Keri Inside Sales for a license key, you need to know the number of Mercury
Powered NXT controllers you are licensing.
In some cases an appropriately configured license key may be provided with the
invoicing paperwork in a shipment.

Demo Mode

Doors.NET has a demo mode feature that allows you 30 days of limited, basic operation.
This can give you an opportunity to try the software before obtaining a license. However,
demo mode only supports NXT controllers; it does not support PXL or Mercury Powered
NXT controllers.

Offline Registration

Offline Registration is used when you already have an existing licensed system but want
to add additional features or enhancements.
Place a checkmark in the selection box then e-mail the license file as detailed in the
'Activation Via Email' section below.

License Manager

The License Manager registers your Doors.NET software and activates any applicable
features or controller values, allowing system use. Please have your license key ready
before beginning this section.

Run the License Manager Program

1. In the Keri > DoorsNET folder, locate and run the LicenseManager.exe program.

2. The License Manager window appears.

- 74 -

Doors.NET Reference Manual

3. Under Installed Components, expand the Services list and click on the Application
Server call-out.

4. Under the Registration Tab, please enter your Registration Information.

5. In the License Key field, enter your License Key.

- 75 -

Doors.NET Reference Manual

6. Double-check your entry as an incorrect character will invalidate your software
installation.

7. Click ACTIVATE.

l If the License Manager CANNOT connect to Keri's license server an error mes-

sage appears. You have the option of either correcting the Internet connection
issue and retrying the activation or performing activation via E-mail. Refer to the

Activation via Email section for instructions.

- 76 -

Doors.NET Reference Manual

l If the License Manager CAN connect to Keri's license server (requires an Internet

connection with external access permission) the software license is activated and
a “Thank You for Registering” window appears. Click OKto continue.

8. Once activated, the Application Server Service needs to be restarted so it may
receive the activated license information.

9. Click YES to continue.

10. A confirmation window appears when the Application Server service has been
restarted.

11. Click OK to acknowledge the restart.

- 77 -

Doors.NET Reference Manual

Activation via Email

If the License Manager is unable to connect to the License Server it may be due to a fire­wall or security setting that does not allow access. You may try resolving this connection
issue or you can activate your software via e-mail. This is done by e-mailing the original
license file to Keri, receiving an updated file with a digital signature, and then overwriting
the original with the new. This process typically takes one business day to complete.

1. If the License Manager is unable to connect to the Internet the following window
appears.

2. Click OK. The Registration Error window appears with instructions on retrieving
and e-mailing the license file.

- 78 -

Doors.NET Reference Manual

3. Click the Offline Registration button and the ApplicationServerLicenseoffline.dlsc
file is created.

4. Locate the license file within the Keri folder – C:\Ker­i\DoorsNET\ApplicationServerLicenseoffline.dlsc.

5. E-mail this file to [e-mail].

6. Close the License Manager.

7. You should receive an updated license file within one business day.

- 79 -

Doors.NET Reference Manual

8. Copy the received ApplicationServerLicense.dlsc file into the C:\Keri\DoorsNET\
directory.

9. Reboot your PC to restart the Application Server.

10. Open the License Manager and activate the new license file.

Verify License Values

Click on the License Tab to view information on the features and capacities enabled on
your system. Information is given on the following categories:

l Branding - lists the program identity displayed to the user
l Capacities - lists basic program feature capacities and activated licensed capa-

cities

l Optional Services - lists licensed application status (as applicable)
l Options - lists enabled optional features
l Server - lists server activation status
l Supported Hardware - lists the hardware gateways supported by this installation
l User Interface - Used to control the display of the user interface
l Video Options - lists the enabled video feature set
l Visitor Management - lists optional visitor management status

If any value is incorrect you must contact Keri Systems’ Inside Sales department to have
your license updated.

Verify Supported Hardware

The Supported Hardware section lists the controllers/gateways supported by the activ­ated license. Verify your controller/gateway types are set to “True” per the hardware you
are installing.

- 80 -

Doors.NET Reference Manual

Verify LegacyPXL Controller Counts

The Capacities section lists the number of Legacy PXL controllers supported by your
license. This only applies to Legacy PXL controllers; standard PXL controllers are not
subject to per-controller licensing.

- 81 -

Doors.NET Reference Manual

Verify Optional Features

Also, you should verify that any optional licensed features are enabled.

- 82 -

Doors.NET Reference Manual

Exit the License Manager

Click Close to exit the License Manager. The next step is to configure the gateway using
the Gateway Wizard.

- 83 -

Doors.NET Reference Manual

Licensed Applications

Licensed Applications are stand alone programs or plug-ins that add features or extend
functionality of Doors.NET.

The following applications are available:

l Archive Service Client - a background task that routinely checks and moves older

transaction events from the main database to a separate archive database

l Enroll Client - a client that contains only the cardholder menu
l Global Linkage Client - provides a way to automate system functions and noti-

fications

l IT Package Client - bundles the LDAP, Report, and Time and Attendance clients
l Lightweight Directory Access Protocol (LDAP) Client - provides a link between

Doors.NET and an LDAP/Active Directory service

l Managed Services Client - allows for the transfer of day-to-day responsibilities

related to management and monitoring of customer’s systems to a Managed Ser­vices Provider (MSP)

l Multiple User Client - allows for the connection of multiple clients concurrently
l NuVision Interface Client - provides a cardholder database integration with NuVi-

sion's One Card system

l Network Video Recorder (NVR) Client - performs two tasks:

1. monitors the transactions generated by the field hardware and inserts linked
transactions into the alarm queue of the NVR

2. monitors the video analytic intelligence stream and sends certain event types
back to the system

l Photo ID/Badging Client - provides a badge template designer and the ability to

capture images, export images, and print badges

l Report Client - a report designer that allows you to create a new report from

scratch or to modify any of the default reports

l Roll Call Client - combines area roll call, muster reporting, and batch updates to

cardholder records

l Time and Attendance Client - provides a generic interface directly to a SQL or

Oracle time and attendance database

- 84 -

Doors.NET Reference Manual

Archive Service

The Archive Configuration Wizard is used to setup archiving of event information that is
generated by the Doors.NET system. By default, all the event information is put into data­base files that reside within the default DHS_MAIN database.

Doors.NET comes with Microsoft SQL Server Express, which is the free version of SQL
Server. To prevent the Doors.NET database from growing too large and to make it more
manageable, Keri provides the Archive Configuration Wizard to allow you to auto­matically setup when the event transactions will be transferred from the main database
to an Archive database.

Setup Archive Service

1. Enter that the Archive Service is selected during the Installation.

2. Open the Archive Wizard via Start >> All Programs >> Doors.NET >> Archive Con­figuration Wizard.

3. Login by entering the default username and password of admin/admin then click
connect.

- 85 -

Doors.NET Reference Manual

4. Select the Maximum amount of days to keep event information before archiving,
(Min - 120 days, Max - 365 days)

5. Select what percentage of the events should be archived

6. Set how often you wish the system to check if archiving is necessary

7. Decide when you want old events to be purged (default is 1 year, but can be set as
high as 7 years.

8. Click the Save Settings button, then click Next.

- 86 -

Doors.NET Reference Manual

9. The default SQL database Instance will be shown. Use the drop-down list to locate
the database Instance if it resides on another machine.

10. Log into the Instance using the SQL Administrator Username and Password. The

default username is dhsuser, the default password is eclip$e.

11. Click Connect and you should almost instantly see the following confirmation:

- 87 -

Doors.NET Reference Manual

12. Click on Save Archive Server Settings and you should then see:

13. Finally, close the configuration wizard and the setup will be complete.

- 88 -

Doors.NET Reference Manual

Enroll Client

Help content section under development.

- 89 -

Doors.NET Reference Manual

Global Linkage Service

Help Content Section Under Development

- 90 -

Doors.NET Reference Manual

IT Package Client

The IT Package Client includes the professional Report Client, the Time and Attendance
interface, and LDAP Client.

- 91 -

Doors.NET Reference Manual

LDAP Import for Active Directory

The LDAP Import feature has two parts: a stand-alone LDAP Import utility and an LDAP
Synchronization Task that runs continuously to keep the Doors.NET Cardholder data­base synchronized with the Active Directory Users database.

The LDAP Import Utility is used to import Active Directory Users into Doors.NET and to
configure settings used by the LDAP Synchronization Task.

LDAP Import Utility includes the following features, requirements, and restrictions:

LDAP Import Utility

l Selective AD User Import – selective import of AD Users based on membership in

AD Security Groups

l Mapped Access Rights Assignment – automatic assignment of Cardholder access

rights based on mappings of AD Security Groups to Doors.NET Access Groups

l Card Number + Facility Code Import – import card numbers + facility codes by

entering values in mapped fields of each AD User

l Disabled AD User Accounts – after disabling AD User Account, based on “Dis-

abled AD User” configuration setting, automatically disables or deletes all cards for
corresponding Doors.NET Cardholder

l Deleted AD User Accounts – after deleting AD User Account, based on “Deleted

AD User” configuration setting, automatically disables or deletes all cards for cor­responding Doors.NET Cardholder

l Photo Import – imports AD User photo from Microsoft Exchange if image is ref-

erenced by AD User field “thumbnailPhoto”

l Allows operator to map AD User attributes to Doors.NET Cardholder fields
l Saves field mappings for later use by LDAP Synchronization Task
l Runs on any Windows PC with .NET Framework v3.5, requires network con-

nectivity to Doors.NET Application Server and AD Domain Controller

l Operator must be System Administrator on both AD Domain Controller and Door-

s.NET Application Server or LDAP Import Utility will refuse to run

LDAP Synchronization Task for Active Directory

The LDAP Synchronization Task will detect and sync changes between Active Directory
Users and Doors.NET Cardholders. Only one direction of sync is supported: either from
Active Directory to Doors.NET or from Doors.NET to Active Directory. The system oper­ator chooses sync direction by running the LDAP Import Utility and specifying all LDAP
Import configuration settings.

- 92 -

Doors.NET Reference Manual

l Runs on any Windows PC with .NET 3.5
l Requires network connectivity to Doors.NET Application Server and AD Domain

Controller

l Requires LDAP configuration files created by LDAP Import Utility to correctly

import AD Users and card numbers, assign Doors.NET Cardholder access rights,
import values for mapped AD User fields, etc.

l Runs continuously as a Windows Service
l Configurable to synchronize changes from AD to Doors.NET or sync changes from

Doors.NET to AD

l Configurable synchronization time interval
l When synchronization time interval occurs (every N seconds), detects changes in

source repository and immediately replicates changes to destination repository.
For example, every 10 seconds, checks for all changes to AD Users including
newly added users, deleted users, and modifications to existing users. Replicates
all changes to Doors.NET Cardholders database. Adding a new AD User results in
a new Doors.NET Cardholder being created.

l Operator chooses action to take when deleting AD User accounts.
l Operator chooses action to take when disabling AD User accounts.
l Modifying a mapped field on an AD User results in that field value being modified

on the corresponding Doors.NET Cardholder.

l The Operator must choose the direction of sync: AD to Doors.NET or Doors.NET to

AD.

- 93 -

Doors.NET Reference Manual

Managed Services Client

The Managed Services client provides a means for remotely accessing, managing, and
operating a number of sites, one-at-a-time, in a secure manner.

- 94 -

Doors.NET Reference Manual

Map Client

Help content section under development.

- 95 -

Doors.NET Reference Manual

Multiple User Clients

Multiple user clients allows for multiple concurrent users to administer and monitor sites
within the Doors.Net software. One client connection is included
with the standard version of the software and additional client connections can be pur­chased from Keri Systems inside sales. Once additional clients have
been enabled on your license, you need to open the License Manager from the host PC
and click on Activate. The PC will connect to the Licensing Server
over the Internet and once re-activation is successful you will be prompted to restart the
Application Server Windows service.

The installation disk will allow you to install the standard client GUI on as many work­stations as you desire. When each client workstation connects to
the Application Server, they utilize one of the client connection which are enabled on the
license.

Note: If you are installing clients on other networked machines you MUST set the Applic­ation Server to a static IP address.

Client-Only PC System Requirements

l Microprocessor - Intel Pentium, Dual-Core, 2.4 GHz or greater, 2 MB cache or

greater

l Memory - 2 GB or greater
l Operating System Compatibility:

- Windows 7 Professional/Enterprise/Ultimate, x32/x64

- Vista Business/Enterprise/Ultimate - Service Pack 1, x32/x64

- XP Professional - Service Pack 3, x32/x64

- Windows Server 2003/2003 R2/2008/2008 R2

l Hard Drive - 160 GB or greater
l Video - either on-board or plug-in card that supports a minimum resolution of

1280x1024
or greater

- Video - either on-board or plug-in card that supports a minimum resolution of
1280x1024
or greater

Communication Ports

The first client connection uses communication port number 11000 to connect to the
Application Server, the second uses 11001

- 96 -

Doors.NET Reference Manual

and so on, these ports are automatically added to the Windows firewall during the install­ation process.

- 97 -

EVR Client

Doors.NET Reference Manual

The Reflections Event Video Recording Client provides revolutionary integration of
video to any Doors.NET access control system. It is an advanced video solution that
provides you with a number of advantages over traditional DVR/NVR video products by
enhancing the functionality of those systems.

It is a separate video client that gathers pre-defined video events from a source (DVR,
NVR or an IP camera) and associates them with their corresponding events within Door­s.NET. These video events are stored on the host PC for later retrieval. It can also
provide video command and control functions from within the Reflections client, such as
Pan, Tilt and Zoom.

- 98 -

Doors.NET Reference Manual

By using the Reflections client, customers are benefited by a common video user inter­face across multiple manufacturer platforms via a growing list of "plug-ins", and have
available some powerful operator initiated actions. A key reflections feature is asso­ciating video with the access events in Doors.NET. The video clip is created at the time
of the event via a unique identification key such that inaccurate time stamps caused by
clock drifts are not a factor for subsequent reviewing or presentation of evidence.

In the Doors.NET software you simple select an event, such as a door forced or access
denied (both generated by a reader) and set the reader's associated camera to record
when one of those events happens. Later on a report can be run on that reader, even
specifying just those particular events and the video clips will all be associated, elim­inating the need to have to scan through hours of video. Video can be set to record from
most events in the system, including inputs going active, readers or controllers going off­line, anti-passback violations or many other invalid access attempts.

- 99 -

Doors.NET Reference Manual

Key Features

l Record on Event - Define what is to be recorded and when & whether triggered

by access hardware or by camera inputs.

l Local Playback - Associated video clips can be played from access control event

history.

l Home DVR Familiarity - Pause, Fast Forward, and Rewind live video, just like

with your home DVR.

l E-mail/SMS Notification - Receive messages when pre-defined events are avail-

able for viewing.

l Overlays - Text information about the time/date, camera, device, event, and card-

holder photo can be superimposed on the screen.

l Video Composite - Up to a 5x5 composite can be used for viewing live video.
l Observation Video - Video operators can initiate a recording at any time if they

see something suspicious. They can also take Snapshot photos, Flag and Cat­egorize observation video for later query, and monitor cardholder photo pop-ups.

l Hardware Linkage - Drag and drop access control hardware objects onto the

Reflections Client for right-click manual operation from the video screens.

l Multiple Monitors - Spread live or recorded video over up to 4 monitors.
l Camera Command and Control -including PTZ control.

- 100 -