only search Wiseman.La

The World NEXT ends 


 
I've been at sooo many clients where when they try and connect to their windows servers via RDP, they get the "All active sessions are in use now, sorry, go fly a kite." message.

This is because (unless you're running terminal services) Windows servers have a limit of two active remote sessions.

And 99.99999% of the time, it's because some folks logged in remotely and forgot to logout - leaving the sessions live and useless.  There are two solutions.

+ Use ultraVNC. I'd vote for this option - includes file transfer, etc., OR

+ Set the remote sessions to timeout, using the following steps. You can use group policy as well (those steps are available from the links below)


Windows Server 2003

http://technet.microsoft.com/en-us/library/cc758177(WS.10).aspx

Using Terminal Services Configuration
1. Open Terminal Services Configuration.

2. In the console tree, click Connections.

3. In the details pane, right-click the connection for which you want to modify time-out settings, and then click Properties.

4. On the Sessions tab, above End a disconnected session, select the Override user settings check box. This allows you to configure time-out settings for the connection.

5. Configure the following time-out settings as appropriate:  

  • In End a disconnected session, select the maximum amount of time that a disconnected session remains on the server. When the time limit is reached, the disconnected session ends. When a session ends, it is permanently deleted from the server. SelectNever to allow disconnected sessions to remain on the server indefinitely.
  • In Active session limit, select the maximum amount of time that a user's session can remain active on the server. When the time limit is reached, either the user is disconnected from the session or the session ends. When a session ends, it is permanently deleted from the server. Select Never to allow the session to continue indefinitely.
  • In Idle session limit, select the maximum amount of time that an idle session (a session without client activity) remains on the server. When the time limit is reached, either the user is disconnected from the session or the session ends. When a session ends, it is permanently deleted from the server. Select Never to allow idle sessions to remain on the server indefinitely.
Notes
  • To open Terminal Services Configuration, click Start, click Control Panel, double-click Administrative Tools, and then double-click Terminal Services Configuration.
  • Group Policy overrides the configuration set with the Terminal Services Configuration tool.
  • These settings affect every client that uses the connection to connect to the terminal server. To define Session settings on a per-user basis, use the User Configuration Group Policies or the Terminal Services Extension to Local Users and Groups and Active Directory Users and Computers.
Windows Server 2008
http://technet.microsoft.com/en-us/library/cc754272.aspx
To specify timeout and reconnection settings for a remote session

1.        On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.
2.        Under Connections, right-click the name of the connection, and then click Properties.
3.        In the Properties dialog box for the connection, on the Sessions tab, select the following options as necessary:
  • Select the Override user settings check box, and then set timeout settings for End a disconnected session, Active session limit, and Idle session limit.
  • Select the Override user settings check box, and then select one of the following reconnection settings: Disconnect from session or End session.
4.        Click OK. Changes to timeout and reconnection settings are not applied to sessions that are connected when the change is made. The changes will take effect the next time the user establishes a new connection to the RD Session Host server.
You can also configure timeout and reconnection settings by applying the following Group Policy settings:
  • Set time limit for disconnected sessions
  • Set time limit for active but idle Remote Desktop Services sessions
  • Set time limit for active Remote Desktop Services sessions
  • Terminate session when time limits are reached

Comments (2)
Craig Wiseman March 3rd, 2010 09:57:35 AM

 Comments
1) Managing Remote Servers: Remote Desktop Session timeout
mark myers http://www.stickfight.co.uk 3/3/2010 11:33:23 AM

i always find that the "/admin" option is groovy as it uses the 3rd "REAL" session and just boots who ever is on it currently, off

2) Managing Remote Servers: Remote Desktop Session timeout
Craig Wiseman http://www.Wiseman.La/cpw 3/3/2010 12:39:42 PM

@1 - That's a good point, however, the /admin option does not always work. I've added this post to explain:

{ Link }


Discussion for this entry is now closed.