OS: Windows Server 2003

I have this problem whereby I am getting multiple iterations of the same user account logged into my server.

I believe this is happening because when different users are trying to connect (via RDP) to a running interation of a user account they are get blocked somehow, and are being unknowingly logged in a second time with that username.

This causes problems because I have certain programs that are to run on certain user accounts only, and if the accounts get doubled, so do the programs. This causes lots of crashes, and of course server performance takes a hit.

So does anyone know how to stop multiple iterations of user accounts from running?

I am not sure if I completely understand what is going on, however, I will make a stab.

Never "x" out of RDP, always logout. This will hold the user's session open. Technically, under Winders 2003 you can have only a console login, and two RDP sessions going on simultaneously, unless you have additional Terminal Services licenses.

You are thinking down the right path.

If I use the logoff frotn the start menu won't the user be logged out? That is always how it was has reacted before. I need the user's session to keep going.

I will give it a try nevertheless.

Ok, that is correct, I run some scripts that must be under an active session, then I just "x out of the session" and you can also rejoin that session if needed.

Just a side note, some php errors and things need to run under "console". To RDP with console access just place connect using 123.123.123.123 /console. That is technically the same as being behind the computer.

Okay I will keep just closing the RDP session.

I sometimes use console and it is very helpful to diagnose problems.

The question stills remains, how do I limit a user account to just one active session.

Sometimes I will login as Admin and find up to three active sessions of the other user account.

If you are comfortable with dealing with group policies on your server:

(from http://www.microsoft.com/technet/community...minal_faq.mspx)
Q. How can I limit Terminal Services so that a user can connect only one time?

A. ...For Windows Server 2003, set the Restrict each user to one session option to Yes in Terminal Services Configuration. Alternatively, set the Restrict Terminal Services users to a single remote session group policy to Enabled.



Basically:
-click start -> administative tools -> terminal services configuration
-click server settings
-edit the value of "restrict each user to one session" to enabled

Realize though, this will affect all users, not just certain ones. Once you have a session on the server you will be connected back to it if you disconnect. You won't be able to open up multiple logon sessions. This is a very handy feature.

Excatly what I want. Now I just need to try it.

Thanks!

You're welcome.

It works...woohoo!

Been looking for a fix to this for a long time that it is almost embarrasing.

Thanks