shoalcreek
MIS
We have some software which connects with our security system. It monitors who has entered each and every door with a key card. It also locks and unlocks our front door. The software runs on a Windows 2003 server and uses very little resources.
"Ruby" unlocks the door at 8am and locks it at 5pm. She's a major pain.
I've only been on this job for three months. During that time, I have observed many messes that were left by the previous network admin. I've been fixing them as I've found them.
After a while, Ruby began having problem with the security software. I later found that she was using remote desktop to access it, using an account called "door", and then running the software to unlock the doors. The problem was not the security software, but that remote desktop was locking up the whole machine. Rebooting is the only way to get the server working properly again.
I called up the software company. He wondered why we were doing that. I set it up so Ruby could access the security software directly without using Windows Remote Desktop.
Last Friday, I naturally hoped that the problem was solved.
But there is Ruby. Ruby called yesterday to say that she couldn't lock the doors at 5pm. I rebooted the server, and she ended up leaving about 15 minutes later than she wanted to leave.
This morning, I noticed that Ruby is again using Remote Desktop after I had specifically told her not to access the security software that way. In summary, I gave Ruby a way to access the software that does not lock up the server. She has decided to use a way that does lock up the server and then complains when the server locks up.