What are the Steps For Upgrading a Doors32 System to Doors.NET?

What are the Steps For Upgrading a Doors32 System to Doors.NET?

Introduction

This document provides the requred steps for converting a Doors32 (PXL-500) system into a Doors.NET system.

Notes: 
  1. PXL-250 controllers are not supported with Doors.NET
  2. The minimum firmware version for PXLs when using Doors.NET is v8.4.49 - any controllers with firmware lower than this will require a firmware upgrade.
  3. There is a charge to use older revision controllers (these are known as legacy controllers) and are PXL controllers manufactured before 2012).

Run the PXL Upgrade Advisor on the Doors32 System

It is highly recommended that you run the Upgrade Advisor program before you start your conversion process and then send the results from the Advisor to Keri Systems via email at the following address: techsupport@kerisys.com.

The Upgrade Advisor analyzes your database to ensure that all hardware installed on your Doors32 network is compatible with Doors.NET. The PXL upgrade advisor will analyse your Doors32 system database and will send you an e-mail about which controller types were detected and if all these controllers can be used in Doors.NET.

Prior to running the PXL upgrade utility, if you are currently logged into the Doors32 software you should click Operate >> Net Disconnect (or you can close the Doors32 software).
  1. Download the PXL Upgrade Advisor here:
  2. Download the zip file to the Download directory of the host PC.
  3. Navigate to the downloaded file and unzip the file.
  4. From the list of extracted files, click on the 'Doors32UpgradeUtilityNET' executable file.
  5. The upgrade advisor window will open.
  6. If you are using a Serial connection or a USB-Serial adapter to the PXL network, you should select the relevant COM port.
  7. If you are using a LAN-520 for connecting to the PXL network you will need to know the IP address for the LAN-520.

    Note: You can view the network connection settings in Doors32 by going to Setup >> System >> Network Config.



  8. Return to the upgrade utility.
  9. Enter the PXL primary modem phone number (if connecting via modem).
  10. Select the appropriate modem initialization string from the drop-down list (if connecting via modem).
  11. Typically the PXL primary Site ID will usually be 0. To check this in Doors32... (if you have multiple sites look for the SELECT SITE button). If there is no SELECT SITE button visible then you are not using multiple sites.
  12. The PXL Primary Site PIN will also usually be 0.
  13. Click the CONNECT button.
  14. Enter your Email address (e-mail address is required) and optionally you can enter a customer contact telephone number.
  15. Click the OK button.
  16. In the Status Messages pane you should see a 'SUCCESSFULLY CONNECTED' message.
  17. Once successfully connected, click the 'GENERATE LEGACY LICENSE REPORT' button.
  18. In the Status Messages pane you will see the message: 'PLEASE WAIT - AUTO-CONFIG IN PROGRESS'.
  19. Once Auto-config is complete you will see a message notifying you to copy the report into an e-mail and send it to: 'keripxlupgrade@kerisys.com'.



  20. Click OK to confirm this message and to generate an review the report.

  21. After generating the report it can then be reviewed. It will detail the total number of PXL controllers that have been detected on the site. It will provide a count of the number of fully supported controllers, a count of legacy controllers (there is a charge to add legacy controllers to Doors.NET) and there will be a count of how many unsupported controllers (such as the older PXL-250 controller type) - the PXL-250 controllers are NOT supported in Doors.NET - these controllers would need to be replaced for PXL-500s.



  22. As mentioned, in the message above, this report can then be sent in the body of an e-mail message to Keri Systems so that you can be provided with a quote to upgrade your Doors32 system.

Detecting and Converting Legacy Controllers

Doors.NET software notes the firmware revision of each Entraguard and/or PXL unit during Auto Configuration and determines if the unit is "Standard" or "Legacy." Standard units are accepted by Doors.NET software with no additional fee. Legacy units require a per-unit conversion fee. Contact your Keri Systems Inside Sales Rep for pricing. Details for identifying Legacy controllers is provided below. 

Standard Versus Legacy PXL Controllers The following PCB part numbers are non Legacy PCBs.

The following PCB part numbers are non Legacy PCBs.

Controller Type
PCB Part Numbers
PXL-500P-X
05496-001
PXL-500P-X NE
05496-002
PXL-500W-X
 05497-001
PXL-500W-X NE
05497-002
TDK-500-X
05668-001

All earlier PCB part numbers designate Legacy PCBs.

Standard Versus Legacy Entraguard Controllers

The easiest method for identifying Standard versus Legacy Entraguard controllers is through the firmware revision of the individual controllers. These firmware revisions are recognized as Standard by Doors.NET:

• Platinum v9.2.02 or greater
• Titanium/Silver v7.8.02 or greater


These are the firmware revisions recognized as Legacy by Doors.NET:

• Titanium/Silver - v7.6.09 and v7.6.13
• Platinum - v9.1.09


These Legacy firmware revisions have improvements in how Smart and Full Updates are performed that are required for operation in Doors.NET.

Doors32 Database Submission

This is a two step process:
  1. Prepare the Doors32 installation for backup.
  2. Submit the Doors32 backup folder and host PC datafile.


Prepare for Backup

  1. Ensure the software revision of the existing Doors32 installation is at v5.20 or higher. If you are not at the minimum revision or greater, you must update your Doors32 installation to the current revision.
  2. Ensure your controllers meet minimum firmware requirements:

    - Keri strongly recommends the firmware on your PXL-500 controllers be at revision v8.4.49 or greater. This is the minimum firmware revision that supports the current Daylight Savings Time dates as set by the U.S. government. It is also the minimum firmware revision that has complete support for anti-passback (note that anti-passback is not yet supported by Doors.NET software). Keri suggests you upgrade to the most recent firmware revision available (currently v8.6.09) for best operation.

    - Entraguard Platinum units must be at v9.1.09 or greater. This firmware revision implements changes that increase the stability of Smart and Total Updates.

    - Entraguard Titanium and Silver must be at v7.6.09 or greater. This firmware revision implements changes that increase the stability of Smart and Total Updates.

  3. Perform a full-update to ensure the information within all controllers is completely up to date, is synchronized with the Doors32 database, and all events are cleared from the PXL controller buffers.

Submit the Doors32 Subfolder

  1. Copy and submit the entire “C:\Kerisys\Doors32_vN.NN” sub-folder set. The specific database “Db/Files” and “Db/Badge” folders are not sufficient to ensure a proper database conversion. Keri needs the entire folder tree from C:\Kerisys\Doors32_vN.NN on down. Submit this folder set using the “Upload File” link provided on the Keri Systems’ website: - http://www.kerisys.com/pages/tech/
  2. You must provide the exact version number of Doors.NET that you will be installing and licensing (typically the current release version). This is critical since Keri is continually making improvements to both Doors.NET and to the database conversion programs. To ensure compatibility between the converted Doors.NET SQL Server database files and your actual, installed Doors.NET system, Keri needs to know the exact version of Doors.NET you will be installing and licensing. Typically, you can include a text file with your Doors32 database submittal including this information.
  3.  As much as possible, ensure no changes are made on the existing Doors32 database during the conversion time period. If you change anything in your Doors32 system after submitting your database for conversion, you will have to manually recreate all of those changes in your converted Doors.NET system.

Install the Doors.NET Software

When installing the Doors.NET software you must be logged into the Host PC as an Administrator, or have your user permissions elevated to Administrator. 
  1. Installation via DVD is the quickest and easiest way to perform an installation. Insert the DVD and the Auto-Run program begins.
  2. Click “Install Software” to begin the installation.
  3. Once started, the installer performs a quick file verification and configures the file set for the installation.
  4. The welcome window then appears displaying the software title, version, and the detected Windows operating system. If your PC does not have an accepted operating system the installer displays a disqualification window and exits the program.
  5. Next is the license agreement. Keri recommends you read through the agreement in its entirety, then enter a tick in the confirmation box to accept the terms. Click the Next button.
  6. Enter the user registration information and organization information.
  7. The hardware selection page is next. Select “Keri PXL and/or Entraguard Controllers.”
  8. Then comes the Installation Type selection page. - Default option will install the Application Server, the PXL Gateway, and an Administrative client. - Second option is a Basic Install and will only install the client. - Third option will install the client with the PXL Gateway. - Fourth option, Custom Install, will allow custom installation where you select exactly what components you wish to include. Choose the “Custom Install” and click Next.
  9. The minimum selections you will need to make for the custom installation are: the Administrative Client plus the Application Server, Gateway PXL Series, and the Archive Services. If you will be adding IP cameras for recorded video then also select “Video Client” and “Gateway Video.” Click Next when you have made your selections.
  10. The review page is next. Review this list carefully as it explicitly states what will and will not be included in the installation. The items to be installed will be listed on the left in green, the items that will NOT be installed will be listed on the right in red. If the information shown is not correct, click Back and review the installation selections.
  11. If all is correct check the confirmation box and click Next.
  12. Now the Destination Folder page is displayed. This is the default folder into which the Doors.NET software and other supporting files will be installed. Most systems will use this default directory: C\Keri\DoorsNET. Keri recommends using this default folder for your installation. This page will also display the required Hard Disk space and the disk space available.
  13. Now comes the Shortcuts page. Select the types of program shortcuts to be installed on the host PC.
  14. The final installation screen will list an SQL Server if it is detected on the PC. You will be presented with three options: - Install the database in this computer – this is the default option. - Scan the Network for an existing SQL Server – this option requires the network folder always be available for the PC/Doors.NET program. - Install the Application Server only – this will require a manual installation of the database using the InstallDHSDB program which is also installed into the C:\Keri\DoorsNET on a default installation.
  15.  Click Next once more when you are ready to proceed with the installation.
  16. A progress bar keeps you informed of the status of the installation. There are several steps involved where there may be a delay of several minutes. Please be patient during the installation.
  17. Once the installation process has been completed you are prompted to run the License Manager.

Activating Your Doors.NET License

  1. With a check mark placed against “Run License Manager now,” click on the Finish button. The installation window closes and the License Manager window opens. The Doors.NET License Manager can also be opened by clicking Start > All Programs > Doors .NET > License Manager.
  2. There is a Doors.NET software license key on the DVD case. You may also retrieve a license key either via e-mail or over the phone.
  3. Type your license key into the license key fields.
  4. Click the “Activate” button. If the PC has unrestricted access to the Internet then you will see a notification window appear stating “Thank You For Registering.” Click Okay to continue. If the License Manager cannot connect to Keri's Licensing Server, then you will either need to: overcome the Internet connection issue or perform activation via e-mail.
  5. Once activation is successful, restart the Application Server.
  6. With the Application Server highlighted on the left hand side of the License Manager, click on the License tab. Under “Capacities,” verify the “PXL controllers (Legacy)” count is set to the number of legacy PXL or Entraguard controllers used in your Doors32 system.
  7. Scroll down until you can see the “Supported Hardware” section. - For PXL controllers, verify “Keri Systems - PXL 500” is set to True. - For Entraguard controllers, verify “Keri Systems - EntraGuard” is set to True. 
  8. Close the License Manager. You are now prompted to run the Gateway Wizard. Ignore this step at this time as much of the information needed by the Gateway Wizard will be included in the converted database.

Installing the Converted Doors.NET Database

In order to install the converted Doors32 to Doors.NET database you must detach the existing, default database and attach the newly converted database.

Retrieve the Converted Database Files

Retrieve the converted database files using the DropSend file link provided via email by Keri Tech Support. If your Doors32 system has badging, there will be a Photos folder included with the converted database with all converted badging photos.

Remove the Default Doors.NET Database

Use Microsoft SQL Server Management Studio Express to detach the database that is created during the installation. If you are running this program for the first time you will also see a message stating it is configuring the environment for first time use.
  1. Stop all Doors.NET related Windows services. Open the Services window by clicking on Start > Administrative Tools > Services. Scroll down the list of service names. Right-click on any service name beginning with Doors .NET and select Stop.
  2. Open the SQL Server Management Studio program. Perform one of the following depending upon Operating System and SQL version installed:

    - Go to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express
    - Go to Start > All Programs > Microsoft SQL Server 2008 > SQL Server Management Studio Express
    - Go to Start > All Programs > Microsoft SQL Server 2012 > SQL Server Management Studio Express

  3. Logon using Windows Authentication then click on Connect.
  4. Expand “Databases” in the left hand pane, right click on “DHS_MAIN,” then select “Delete” from the menu. The “Delete Object” dialog pops up.
  5. In the “Delete Object” dialog, click OK. After the database files are deleted, the “Delete Object” dialog automatically closes. The files named DHS_MAIN_Data and DHS_MAIN_Log should have been deleted from the following directory (depending upon operating system type): C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (32-bit OS) or C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data (64-bit OS).
  6. Start all Doors.NET related Windows services. Open the Services window by clicking on Start > Administrative Tools > Services. Scroll down the list of service names. Right-click on any service name beginning with Doors .NET and select Start.

Attached the Converted Doors.NET Database

The converted database is made up of replacement DHS_MAIN_Data and DHS_MAIN_Log files.
These new files will overwrite the existing, detached database files.
  1. Copy the new DHS_MAIN_Data and DHS_MAIN_Log files to the appropriate directory (overwriting the existing files): C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (32-bit OS) or C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data (64-bit OS)
  2. From Studio Express right-click on Databases and select “Attach” from the menu. 
  3. Click on the Add button and double-click on the DHS_MAIN.mdf file.
  4. Click “Ok” on the “Attach Database” window and allow it to run.
  5. On the lower-left of the “Attach Database” window a green progress wheel indicates the progress of the procedure.
  6. When the procedure is completed, the DHS_MAIN database will now be present under “Databases.”


Transfer the Badging Photos

If your Doors32 system had badging you will need to transfer the badging photos to the new photo directory. The converted database download includes a Photos folder with all converted badging photos.
  1. Copy all files within the retrieved Photos folder to the C:\Keri\DoorsNET\Photos folder.

Run the Gateway Wizard

Now run the Gateway Wizard to associate the PXL Gateway with the system's Application Server. 
  1. From the Start menu click >> All Programs > Doors .NET > Gateway Wizard.
  2. From the logon window select the Keri - PXL Series gateway from the Gateway Selection dropdown list.
  3. The server IP address and TCP Port value are automatically entered. This assumes the access control hardware and the host computer on which the software is installed are on the same network.
  4. Enter the default username and password (admin/admin).
  5. Click the “Connect” button to select the PXL gateway.
  6. The PXL Gateway now appears in the “Existing Gateways” list on the left. Highlight this gateway and click on the “Next” button.
  7. On the final screen of the Gateway Wizard check that the Gateway Type is correct then click the “Finish” button.
  8. You will then be prompted to restart the PXL Gateway service. Select “Yes.” Shortly a confirmation message stating the service has been started appears.

Verify the PXL/Entraguard Controllers are Online

  1. Login to the Doors.NET software via the Administration Client icon. You should see the icon on the desktop; it is named “Keri Systems Client.”
  2. Enter the default username and password (admin/admin).
  3. Click Connect and the Doors.NET program opens.
  4. From the Setup tab click on the Hardware Setup icon and then go to the All tab. This takes you to the hardware tree where your PXL gateway will appear, along with a “Communications Channels” node, and then your master PXL beneath that.
  5. Highlight the master controller and verify in its properties that it is showing as online.
  6. Open the Live Events grid and you should see online messages for all the PXL and/or EntraGuard controllers on the network. If the PXL network fails to come online refer to the troubleshooting section at the end of this document.

Auto-Configuration and Initial Update Now you need to auto-configure and update the network

  1. With the master PXL/Entraguard highlighted and showing as online, click the Auto-Config button.
  2. Monitor the messages that appear in the Status Messages grid of the Auto-Config page. You should see “PXL Master is searching for slave controllers.”
  3. After 2 or 3 minutes all the detected slave controllers will appear in the Available Controllers list. Review the detected controller information then click the Apply button to complete the AutoConfiguration.
  4. Close down the Auto-Configuration page and return to the Hardware Setup page.
  5. Double-click the master controller and a list of all controllers on the network appears. To the right of each controller will be an “Update Network” indicator. A full update network is required on each PXL/Entraguard controller to synchronize the hardware configuration with the Doors.NET software.
  6. Highlight the master PXL controller then click the Update Network icon on the ribbon bar near the top of the screen. In Live Events you will see a message appear stating: “Update Network Started.”
  7. Wait for the Update Network Completed message to appear a few minutes later and then the system will be fully up and running and converted over to Doors.NET.

Troubleshooting

Simple Steps:
  1. If the master controller does not come online then you may need to restart the PXL Gateway windows service. This can be done by selecting the Kiwi bird icon in the bottom right in the Windows Toolbar Tray and clicking the Restart All button.
  2. Doors.NET will not operate correctly if Doors32 is actively trying to communicate with the controllers. If the primary controller does not come online and the Doors32 software is still open. Click on Operate > Net Disconnect within the Doors32 program. 



Detailed Routine: 

  1. Stop all Doors.NET Services.
  2. Run Doors32 > Setup System > SET TIME button to test the connection to the primary controller. If the system connects, then the connection wiring is OK, the primary controller is OK, and PC data communications are OK.
  3. Disconnect from the primary controller and close Doors32.
  4. Stop the PXL Gateway Service.
  5. In the Doors.NET Client GUI, select the primary controller. 
  6. Change “Connection Control” to “Manual” and SAVE the change.
  7. Wait at least 60 seconds for the primary controller  to prepare for a new, incoming connection request.
  8. Start the PXL Gateway Service. 9. In the Doors.NET Client GUI, select PXL/Entraguard Master, right-click, and select “Connect.”
  9. Watch the “Live Events” to see if the PXL/Entraguard primary comes online.
  10. If not, in Doors.NET Client GUI, select the primary controller, right-click, and select “Disconnect.”
  11. Stop the PXL Gateway Service.
  12. RAM reset the master controller. This forces the primary controller to prepare for a new, incoming connection request.
  13. Start the PXL Gateway Service.
  14. In the Doors.NET Client GUI, select the primary controller, right-click, and select “Connect.”
  15. Call Keri Tech Support if it still will not connect.


    • Related Articles

    • Upgrading to Windows 10

      1.0 Introduction Doors.NET is fully compatible with Windows 10 operating system beginning with Doors.NET v3.5.1.20. No additional steps are required to enable the program following an operating system upgrade from Windows 7 or 8.1 to Windows 10.   As ...
    • Doors.NET - Migrating a System

      1.0 Introduction There are several steps that need to be taken to successfully transfer a Doors.NET installation onto a different host PC. It is important that these steps are performed in the exact order that they are listed: Note: The version of ...
    • Doors.NET - Full Installation

      1.0 Introduction The Doors.NET software can be downloaded from the www.kerisys.com software downloads section. You can download just the installation file or you can download the entire installation file set (which will allow you to perform the ...
    • Doors.NET - PXL Upgrade

      An overview of some of the main features and benefits available to you when upgrading your Doors32/PXL-500 system to Doors.NET.
    • Doors.NET - Software Installation Guide

      1.0 Introduction The Doors.NET software can be downloaded from the www.kerisys.com software downloads section. You can download just the installation file or you can download the entire installation file set (which will allow you to perform the ...