Getting Doordeck setup & installed on your STANLEY NT500 access control devices.
STANLEY NT500 4.6.333
Windows 2008 Server R2 SP1
Windows 2012 Server
Windows 2012 R2 Server
Windows 2016 Server
OEM interface licence
2GB free disk space
2566 GB SSD
Generate OEM key:
Login to the STANLEY NT500 interface.
Select Manage OEM interfaces.
Give the key a name.
Select Access and Read Write.
Specify a system location for the OEM key (eg Desktop).
Install Doordeck Fusion:
Download the Doordeck Fusion zip file from the Doordeck server.
Extract the zipped files from the folder.
From the certificate folder, double-click LoadCertificate.cmd.
Right-click LoadCertificate.cmd and select Run as Administrator. This will load the OEM certifications into the system keystore.
Select Doordeck Fusion Installer
The Doordeck Fusion SetUp Wizard will open. Select Next to continue.
Accept the terms of the license agreement and select Next.
Confirm the destination folder for Doordeck Fusion and select Next. The installation will begin.
You will be alerted when the installation is complete. Select Launch Doordeck Fusion and then select Finish.
The Doordeck Fusion login screen will open. Login using your Doordeck credentials.
The Doordeck Fusion configuration tool window will open. Select STANLEY NT500 from the select access control menu.
Specify the OEM key which was previously saved to your desktop.
Identify the relevant door from the list and select Enable Doordeck. Repeat this step as many times as required for the number of doors.
Doordeck Fusion is now ready to use. See the Administrator Guide for further instructions.
Extract the new version of the download from the Doordeck zip file.
Double-click the installer and the software will upload/update.
PLEASE NOTE: Doors will be offline during the upgrade process (usually around five minutes).
Verify that the certificate PAC OEM Interface is loaded in the Trusted Root Certification Authorities for the current user: Run > MMC > Add/Remove Snap-ins > Certificates > My user account.
Verify that the firewall or anti-virus software is not blocking communication.
Check logs in ApplicationInterfaceHost.exe.config.
Verify that the access control licenses are present and valid.
Service Manager will show Application Interface Manager.
If trying to access an org unit, verify that you’ve enabled access to that org unit in the access control application. Log into the access control app and switch org unit.
Never run the old OEM Interface server at the same time as Application Interface Manager because they can interfere with one another. By default, the OEM Interface service is disabled. Check Administrative Tools > Services.