Doors control system
Plug in the fob reader BEFORE you launch Net2Access controls.
There is a Dell Optiplex 3020 on the desk in the Klee basement, running Windows 7 with the Net2 Access Control software. Users with access are Gene Martin, Kathy Barth, Darlene Gautreau, Lyle Nichols, and System Engineer.
Contact: Tom Milbert <tmilbert@monadnocksecurity.com> 603-878-0600
WHEN WE LOSE POWER and the UPS runs out, remember to turn this thing back on...
I requested a howto/manual, which he (Tom) sent it, and it's attached here. He did not know offhand whether the server can be virtualized, but he said he'd look into that. UPDATE June 2019 -- given that I now know Gene has to use a USB device to program fobs, I'm gonna go ahead and guess the answer is "no" to virtualization. :( Hope the backups work!
BACKUPS
Looks like it uses SQL Server. There's a scheduled task called "Net2 Maintenance" which executes some batchfile and writes results to a "backup" subdir at C:\Net2 Access Control\Backup. On June 13 I copied that whole folder to the fileserver so we have *something* offsite.
Oct 2017: I added a batch script called "makebackup.bat" under Gene Martin's local home dir on the CADOORS PC which runs this:
xcopy /s /y "c:\Net2 Access Control\Backup" "s:\doors-backup"
/s = subdirs
/y = accept prompts to overwrite
(I.e. his home dir on the fileserver.) Added a scheduled task ("remotebackup") to run that on Thursdays at 10am. Added his account to "logon as batch privilege" as per this: https://www.brooksnet.com/faq/granting-logon-as-batch-privilege
THIS WHOLE THING WAS AN EPIC FAIL. Here's the updated, working version as of June 2019:
1. C:\doors-backup.bat which contains
robocopy "c:\Net2 Access Control\Backup" "\\CA-2016-SRV\Faculty\gene.martin\doors-backup" /S /E /Z /ZB /R:5 /W:5 /TBD /NP /V /MT:16 /log+:backuplog.txt
2. Scheduled task "remotebackup" for Thursdays at 11:03am with the following parameters:
As per Brian Vandemark's post here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/d47d116e-10b9-44f0-9a30-7406c86c2fbe/scheduled-task-wont-run-bat-file?forum=winservermanager&prof=required Quoted here for posterity/preservation:
------
I wanted to summarize all of the steps I performed to solve my problem. I would guess that maybe some of these are not needed, but I'll list them all to hopefully help you get it working
1) Make sure that the task is set to "configure for Windows Vista or Windows 2008" on the first page of the task properties (under the "general" tab)
2) Make sure that the task is set to "start in" the folder that contains the batch file: open the task properties, click on the "actions" tab, click on the action and then the "edit" button at the bottom. In the "Edit Action" Window there is a field for "start in (optional)" that you set to the path to the batch file.
3) Make sure that the task is running as an account that has explicit "Full access" permissions to all these things: The .bat file itself, the folder containing the .bat file, and the target files/folders that are affected by the .bat script. Inherited permissions didn't seem to work for me.
4) Make sure that the account running the task is a member of the local "administrators" group for this machine
5) Make sure that the task is set to "run whether logged on or not"
6) The Task should run successfully with expected output when you right-click on the task and select "run" If it does that then it will run successfully when you are logged off.
Good Luck!
------
CLIENT SOFTWARE
After we got new faculty laptops in 2018, I set up Gene's and Lyle's laptops to connect to the doors PC at Klee via RDP. That's fine for adjusting things within the Net2Access software, but it turns out that Gene occasionally needs to connect a physical reader to a USB port to program a fob. THAT doesn't work over RDP since it requires a direct hardware connection. So, we installed a copy of Net2Access CLIENT on his laptop and pointed it to the server so that he can do direct USB stuff, no more RDP for him.
The installer backup for our old version of Net2Access (5.2.2525.4988) is in the technet share under Installers/Paxton. It offers a "client" option when you run the installer which is what I used for Gene's laptop because we're not making another server, duh.
It looks like our product key is KHH3-8C79-FC4F-HXF3-9935 but it didn't need that for the client install, presumably because it talks to the server and knows the server is already licensed.
