Note: If your license requires multiple gateways, multiple hardware types, multiple clients or additional features, such as: Global Linkage or Situation Manager, you will need to contact Keri Systems inside sales to obtain a new license key.
If you have one of these installation types you MUST call Inside Sales for a license:
• You are using legacy PXL/EG controllers (described below).
• You are using multiple hardware gateways.
• You are installing optional, licensed features.
- Go to the License Key page on the Kerisys website (http://license.kerisys.com/)
- Read through the License Provision Terms and Conditions.
- Tick the confirmation/agreement box, then click Continue.
- Enter the required information in both the Installer and End-User sections. Fields denoted with an asterisk (*) are required.
- In the System Information section, select the hardware type that will be in use. An image of the selected controller type will appear as soon as you make your selection.
- Enter the CAPTCHA validation code then click Continue.
- A new license key will be created and it will appear on the screen.
- Click the Finish button and a copy of the license will also be e-mailed to the installer e-mail address.
3.0 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, Entraguard, or Mercury Powered NXT controllers.
4.0 PXL Legacy Versus Standard Controllers
If you have PXL Legacy controllers you are required to call Keri Inside Sales for a PXL Legacy license key. You will need to provide the number of Legacy PXL controllers you want to license.
4.1 Identifying Legacy versus Standard 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.
4.2 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 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.
5.0 Entraguard Legacy Versus Standard Controllers
If you have Entraguard Legacy controllers you are required to call Keri Inside Sales for an Entraguard Legacy license key. You will need to provide the number of Legacy PXL controllers you want to license.
5.1 Identifying Legacy versus Standard Entraguard Controllers
Entraguard units with this level of firmware or greater are Standard Entraguard units and are not subject to licensing fees:
• Titanium and Silver - v7.8.01
• Platinum - v9.2.01
Entraguard units with these firmware revisions require Legacy licensing:
• Titanium and Silver - v7.6.09 (minimum revision allowed), v7.6.13
• Platinum - v9.1.09 (minimum revision allowed)
5.2 Legacy Entraguard Controllers
Legacy controllers require an Entraguard 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 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.
6.0 Run the License Manager
Following installation of the software the system will need to be activated. Activation is performed using the License Manager Utility and is most easily done using an active, unrestricted Internet connection. The License Manager registers and activates your software and validates any applicable features or controller values, allowing system use. Please have your license key ready before beginning this section.
- Once the software has successfully installed you will be prompted to run the License Manager.
- The License Manager can also be opened by clicking Start > All Programs > Doors.NET > License Manager.
- Or it can be run from the C:\Keri\DoorsNET directory.
- If it is the first time you have run the License Manager you will see the following welcome screen.
- The next screen you see is where you enter your license key.
- Enter your key then click Next.
Note: Once you have your license key you can then copy and paste the key into the fields shown below. Put the cursor into the first text field, then paste.
- Next is the registration page. Enter information about the site and installer contact details.
- You will then see a summary page. Click next to complete the task.
- Within a few seconds you should see a registration successful notification. Click OK to this.
- The next notification is to restart/start the Application Server Windows Service. Click Yes to this.
- Once the Application Service service has restarted you will be prompted to install the hardware communication gateway services plus any other Doors.NET feature that requires a Windows service. Click the Yes button to install the services.
- When the Doors.NET Windows services have successfully been installed the License Manager will automatically open.
- The software is now fully activated and ready for Gateway Configuration.
7.0 Configure the Gateway
The gateway driver is the component that communicates with the controllers (so for example; there is a NXT Gateway for communicating to the standard NXT 2D and 4D controllers. As per the previous section, the relevant gateway service is installed during license activation. You can then use the license manager to create the new gateway.
- In the license manager, look to the list of installed components.
- You will see that the gateway is marked as needing configuration.
- Select the gateway.
- Click the SETTINGS button.
- The Add Gateway window will appear - prompting you to enter a name for the new gateway.
- Enter the gateway name then click OK.
- The new gateway will be added to the system.
- You will see another message informing you that the gateway service has started.
- The gateway service will then be displayed in the license manager as both licensed and configured.
- You can now close down the license manager. Doors.NET is now ready for controller setup.