We used to use a Wiki page for sign in and out, so people could look at the page and see what machines were claimed and by whom. That way there was tracking and the page could be looked from anywhere in the company.
Nothing learns better than experience.
"So as I struggle with this issue I am confronted with the reality that noting is perfect."
Now we have 14 lab machines.
We have a wiki page and the engineers aren't good about updating it.
I can't blame them. It's a nuisance. It's a process that should only take literally a few seconds.
I'm looking at MS lync thinking it would be perfect if every machine could have it's own lync account. Lync knows when the machine is inactive so if a script is running I am hoping Lync could figure that out.
Problem is I'm sure my IT people will frown upon my request for 14 outlook accounts that will be tied to particular machines.
Here's the winning idea that I can't believe I didn't think of earlier. I'm writing a simple windows form app in VB that uses an xml file and parse the information either into a form (for update) or a datatable (for Display). I'll put that on the network and have a shortcut on all the machines. Done.