19
2
We have a bunch of servers that our engineers remote desktop into, but each server has a two connection limit. We will often attempt to RDP into these boxes and we will see the "This machine has exceeded the maximum number of connections" message.
It's a big pain because we have sent out several email messages to these users, and they never get the point.
I know how to connect to the root console and boot people, but I'd prefer not to do that. I also know that there are ways of booting inactive sessions after a period of time, and I don't want to do that either.
I want to force users to learn that they need to log out. This doesn't happen if you log them out manually (plus logging them out manually is a pain). If you just log them out manually, these engineers won't think twice about staying connected in an RDP session because it is convenient for them.
I would prefer some notification system where the inconsiderate user is notified via email or NET SEND message that their account is being disconnected from machine. That way, they will realize that they are doing something wrong. Even better, if they are in violation several times, I would like their account to be locked until a system administrator unlocks it.
Is there a way to achieve the goal of having users log out manually? All suggestions are welcome.
The best practical way I can think of is what you are already doing. Mail them all but add 'user A and user B are actively working on this machine at this time. Can either of you two mail use when you have finished and logged out?'. Goal: Yes, you are waiting. These are the people who forgot to log out, go complain to them.
Also, if you regualy need more users then there is a solution: Terminal server. As far as I know that means paying for a license and changing one DLL. – Hennes – 2015-10-15T13:15:11.567