Previously under Windows XP Terminal Services supported one concurrent connection and if another user tried to login that user was forced to logoff. Under Windows 7 RC there is one concurrent connection however if another user attempts to login the previous user is not logged off. The connection is instead put into a disconnected state and all of the applications continue to run chewing up CPU/memory. Id like to limit the # of connections to 1 (disconnected or otherwise). I know Windows Server supports a reg key HKLM\System\CurrentControlSet\Control\Terminal Server =>MaxInstanceCount which you can set to 1 to accomplish this. However this setting does nothing under Windows 7. I also know I can bump down the idle time to a low amount but I really would rather not because the users could possibly lose their work on a regular basis (rather than when someone forcibly bumps them).Is there reg setting or otherwise to make it so sessions forced into a disconnected state (by another user logging in) get logged off instead?Thanks!

Are you using this machine in a production environment? This is a bad idea for Windows 7 as it is a release candidate, and the website advises to only use where it will not cost anyone production time.

I'm trying to get everything set for go live; automated build, application packaging and configuration. I'm on this last piece and would like to have this ironed out before we begin deployment.

Hello Terence,Do you have group policy set to Restrict terminal services to a single session?-Scott

Scott,Thanks for the reply. I tried:Computer Configuration/Administrative Templates/Windows Components/Terminal Services => Limit Number of Connections with a setting of 1.Thisreally doesn't solvethe problem. If a user is connect anyone trying to terminal serve to the machines gets a generic "The computer can't connect to the remote computer". This would be fine however it does nothing to prevent a user from disconnecting and the someone else connecting as another user. I did this several times and has processes running for 4 different disconnected accounts still on the machine.It does prevent another user from taking over a session but doesn't force a logout once a different user connects.Terence

Hi Terence, You should give a look to a 3rd-party tool called UserLock that allows simultaneous logon (same ID, same password) limitation or prohibition, per user or user group and per session type (workstation, terminal, interactive or VPN/RAS).. Best,Franois Amigorena President & CEO IS Decisions (Security Software) http://www.isdecisions.com