Is there a way to reset Terminal Services to factory defaults?

[MichaelD]

Well, my curiousity has gotten the best of me again.

I mucked around w/the session and other settings..now I can't login remotely...I was able to BEFORE I messed w/it.

How do I reset it to "factory specs?"

Thank you.

 

[MichaelD]

Uppa.

 

[spyordie007]

It looks like the settings are stored here (for all versions):
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server

I would like to imagine that if you deleted that "Terminal Server" key and rebooted it would be reset to "default" (whatever that may be) however I dont know for sure.

If it were my desktop box (win xp pro) I would backup the registry and delete the key than find out if that did it. If not restore the registry key, reboot and look for a fix elsewhere.

Good Luck!

-Spy

 

[MichaelD]

Thanks, Spy. The registry is a scary place...especially in Server. :Q I'll give that a shot, though. I can always restore.

 

[lowtech1]

Go to your terminal server & open the TS Manager then right click the user that is hung & reset it.

Once the above is done open the AD Users and Computers and right click properties of the user session that has been played with and reset the session to below (default):

End a disconnected session: Never

Active session limit: Never

Idle limit: Never

When a session limit is reached or connection is broken:
* Disconnect from session

Allow reconnection:
* From any clients


It is critical that you read upon the above session management befor you play around with the defaul setting because it could kick a user out in a middle of an important transaction that could hung a database (if you are running a database).

However the "End a disconnected session" is the most common (and only) option that you might want to use in an office environment.

If you are running terminals for school labs or library then "Active session limit" & "Idle limit" in conjuntion with "End a disconnected session" can be use to control/limit the session

If the work is critical & you don't want the system to hung if the network break in the middle of your session then the defaul setting is use.

The user setting could also be override under TS Configuration as described in this post: Blocking sites for a certain user on Win2k Terminal Server

 

[MichaelD]

Originally posted by: lowtech
Go to your terminal server & open the TS Manager then right click the user that is hung & reset it.

Once the above is done open the AD Users and Computers and right click properties of the user session that has been played with and reset the session to below (default):

End a disconnected session: Never

Active session limit: Never

Idle limit: Never

When a session limit is reached or connection is broken:
* Disconnect from session

Allow reconnection:
* From any clients


It is critical that you read upon the above session management befor you play around with the defaul setting because it could kick a user out in a middle of an important transaction that could hung a database (if you are running a database).

However the "End a disconnected session" is the most common (and only) option that you might want to use in an office environment.

If you are running terminals for school labs or library then "Active session limit" & "Idle limit" in conjuntion with "End a disconnected session" can be use to control/limit the session

If the work is critical & you don't want the system to hung if the network break in the middle of your session then the defaul setting is use.

The user setting could also be override under TS Configuration as described in this post: Blocking sites for a certain user on Win2k Terminal Server

THANK YOU lowtech. I needed the step-by-step. (I guess it shows, huh? ) I like messing around w/the settings...that's how I learn. Thankfully, this is on my home server and nobody buy myself is inconvenienced.

Needless to say I don't mess around w/those same setting on the server at WORK>>>how to get fired in one easy step. :Q

Have a good weekend.

 

[lowtech1]

Originally posted by: MichaelD

Originally posted by: lowtech
Go to your terminal server & open the TS Manager then right click the user that is hung & reset it.

Once the above is done open the AD Users and Computers and right click properties of the user session that has been played with and reset the session to below (default):

End a disconnected session: Never

Active session limit: Never

Idle limit: Never

When a session limit is reached or connection is broken:
* Disconnect from session

Allow reconnection:
* From any clients


It is critical that you read upon the above session management befor you play around with the defaul setting because it could kick a user out in a middle of an important transaction that could hung a database (if you are running a database).

However the "End a disconnected session" is the most common (and only) option that you might want to use in an office environment.

If you are running terminals for school labs or library then "Active session limit" & "Idle limit" in conjuntion with "End a disconnected session" can be use to control/limit the session

If the work is critical & you don't want the system to hung if the network break in the middle of your session then the defaul setting is use.

The user setting could also be override under TS Configuration as described in this post: Blocking sites for a certain user on Win2k Terminal Server

THANK YOU lowtech. I needed the step-by-step. (I guess it shows, huh? ) I like messing around w/the settings...that's how I learn. Thankfully, this is on my home server and nobody buy myself is inconvenienced.

Needless to say I don't mess around w/those same setting on the server at WORK>>>how to get fired in one easy step. :Q

Have a good weekend.

Your welcome & I send you to the wrong link above. Here is the correct link --

terminal services -- how do I log onto the same session as is on the console?