This KB is for reference purposes and informs the reader that the Simonsvoss CommNode Server Service is being monitored (Start/Stop) on the VM Server.
Article for IT Services Staff Only: mainly aimed at the Server Team, but for awareness across IT Services for Application Support, IT Service Desk.
IT SERVER TEAM ONLY:
Simonsvoss is a digital access locking software management system used across the University in managing access to the rooms that have been fitted with Simonsvoss locking technology.
The article is for IT Services Staff: mainly aimed at the Server Team, and awareness across IT Services for Application Support and IT Service Desk.
This article advises that the Simonsvoss CommNode Server Service is now being monitored to ensure that it is operational on the VM server: DSLOCKKEY1
From time to time, the Simonsvoss CommNode service stops working (Server DSLOCKKEY1) which then prevents the various Client Users, Faculty Building Managers and Estates E-Locking Team to program their networked remote door locks. There is an underlying bug and the root cause has never been fully identified, yet and sometimes false positives can occur. When the Simonsvoss CommNode service stops it needs to be restarted. This is 5 min fix as long as one understands the urgency of this software system and how its affects the Simonsvoss Users.
This does not effect any other functionality of Simonsvoss or the ability of any staff to use the fobs to enter/exit any door.
When the Simonsvoss CommNode service stops only the following Simonsvoss functions are effected and Building Managers are unable to:
A PowerShell script is now in place which:
Whenever an incident of this nature is logged with the IT Service Desk, the ticket is linked or references the KB article: KB0012841.
Service Name: SVCommNodeSvr
Display Name: Simonsvoss CommNode Server
Startup Type: Automatic