Moving Doordeck Fusion To A New Server

This guide explains how to move Doordeck Fusion from one server to another, this guide assumes both the old and new server are fully operation and is not meant as a disaster recovery guide.

‍

Prepare the new server

Start by downloading a fresh copy of Doordeck Fusion, contact support@doordeck.com if you don't have a recent download link.

‍

Install as normal, but don't open the Doordeck Fusion tool at the end of the installation.

‍

Moving configuration from the old server

Ensure all of the Doordeck services in Windows Service manager (Start -> Run -> services.msc) have been stopped before starting the migration.

Each door has a dedicated configuration directory, these can be found in c:\Program Files (x86)\Doordeck Fusion\Service, the configuration directories are a bit cryptic sounding but all have a name along the lines of "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", where X is either a number of a letter, the screenshot below illustrates this better.

Here we have two doors setup with the names 5908ed20-cd38-11e8-a234-6986d3c6ca8eand ddb74c90-7c1e-11e7-9823-a9f736dac766. Copy all of the door configuration directories to the new server so the directory structure is the same.

Enabling doors on the new server

‍

Now you've moved the configuration across to the new server we need to enable them as Windows Services - each door is its own Windows Service to ensure a high level of resilience.

‍

Start by loading the command prompt, you can do this by clicking Start -> Run and typing 'cmd'.

‍

Change to the Doordeck Fusion service directory by typing the following command:

‍

cd "c:\Program Files (x86)\Doordeck Fusion\Service"

‍

Please note, the following steps do not apply for NT500, contact support@doordeck.com for details about how to migrate NT500 doors.

‍

For each door configuration you've moved across, run the following command:

‍

nssm install "Doordeck - XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

‍

Replacing XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX with the door identifier, this command should be exactly as above.

‍

This will cause the nssm service configuration to popup, we need to set the values as follows:

‍

Path: C:\Program Files (x86)\Doordeck Fusion\Service\skeleton.exe
Startup Directory: C:\Program Files (x86)\Doordeck Fusion\Service\XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Arguments: server etc/server.yml
Service Name: Doordeck - XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

‍

The service name should be pre-populated already, but you'll need to set the path, startup directory and arguments, once done, click Install Service. Repeat for all other door configurations.

Once all doors have been enabled, you should be able to start the services via Windows Service manager or the Doordeck Fusion tool - each door may take 30 seconds or so to startup, test each door to ensure proper operation and contact support@doordeck.com if you have any issues.