I'm setting up a Windows 7 "resource computer" that will have applications installed like Visio 2013 and others that are used by my employees but not needed enough to buy individual licenses for everyone.
I don't have a need for a full blown terminal server for this (even with the current drawbacks), and have set it up as a resource in Exchange for scheduling purposes.
I've done a few local policy edits to enforce disconnects of idle sessions, printer drivers, and bandwidth control.
My questions are:
- Is there a way to prevent a simple disconnect of a session (X/close) and require a logoff?
- Any method for controlling the actual resource and time allotments short of manual intervention? Meaning if a user books the resource in Exchange from 2pm-4pm right now there's nothing that forces them or at least prompts them that their session should be ending and they technically could keep using the shared computer past 4pm even if someone else is scheduled (thus requiring me to intervene like a parent). I keep hoping for something similar to scheduling a "webex" or similar, but so far no luck.
Trying to search online for some of these issues I haven't found a great method for preventing disconnects. Most involved programming or a script on the client side not the resource computer side. For the second question, I haven't found anything yet.