Solved

Remote Desktop Console/Admin Session Times Out

Posted on 2010-09-08
13
4,049 Views
Last Modified: 2013-11-21
Hi,

We currently have a number of servers running Windows Server 2003 and Server 2008.  When I connect to the 2003 servers using the /console or /admin (depending on version of RD) switch using Remote Desktop, my idle sessions never expire.  I can leave the session up for days if I choose.  However, my sessions will expire when connecting to Server 2008 just as if I was connected to a regular session.  The error is: "Your Remote Desktop session ended because the remote computer didn't receive any input from you".  Anyone know why this might be happening?

We use Group Policy to control time-outs and disconnects of our sessions, but those only apply to non-console sessions, so they should have no effect.
0
Comment
Question by:mancalgroup
  • 7
  • 4
  • 2
13 Comments
 
LVL 17

Expert Comment

by:Chris Millard
ID: 33631441
This is by design. Console / Admin sessions do not timeout. Normal sessions can be configured through group policies to stay open, or to log out after how ever long you specify.
0
 
LVL 17

Expert Comment

by:Chris Millard
ID: 33631454
0
 
LVL 11

Expert Comment

by:mattibutt
ID: 33631483
after how long it happens like one minute?
0
VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

 

Author Comment

by:mancalgroup
ID: 33631660
roybrige:  Maybe I could have been a little more clear, but I realise that admin / console sessions are NOT supposed to time-out by design, but they are in fact connecting due to inactivity when I am connected to a Windows 2008 machine.  When I connect to a Windows 2003 machine, they do not time out when I am connected to the console.
Mattibutt: The connection times out after the normal amount of time which I believe is about 20-30 minutes of inactivity.
0
 
LVL 11

Expert Comment

by:mattibutt
ID: 33631675
i think thats fine its a good security measure in case if you go for smoke i do all the time but i lock my screen point of the matter is this kind of security is a good feature however you want to change that?
0
 
LVL 11

Expert Comment

by:mattibutt
ID: 33631680
windows 2003 remain active forever its true but do you want to setup like that?
0
 

Author Comment

by:mancalgroup
ID: 33631691
Sorry roybridge, I meant "they are in fact disconnecting due to inactivity when I am connected to a Windows 2008 machine"
0
 
LVL 11

Expert Comment

by:mattibutt
ID: 33631706
follow step here if you want to change the time
http://technet.microsoft.com/en-us/library/ee791886(WS.10).aspx
0
 

Author Comment

by:mancalgroup
ID: 33631723
OK, just so we are on the same page:  When a person connects using the /console or /admin switch, the session should never time out due to inactivity.   And yes, I want it to never disconnect when I use those switches, otherwise I would just connect using a regular RDP session without /console or /admin being used.  I will log out of the server when I am ready.
0
 

Author Comment

by:mancalgroup
ID: 33631744
If you read the explanation for each of the policies in the link you just sent Mattibutt, it says the following:

If you have a console session, disconnected session time limits do not apply.

If you have a console session, idle session time limits do not apply.

If you have a console session, active session time limits do not apply.

Please read my original post carefully as I have covered all of this already.
0
 

Author Comment

by:mancalgroup
ID: 33647728
Anyone?
0
 

Author Comment

by:mancalgroup
ID: 33648607
I guess I should mention that I am connecting from a Windows XP SP3 machine, and have tried both RDP 6 and RDP 7.
0
 

Accepted Solution

by:
mancalgroup earned 0 total points
ID: 33682661
Microsoft has decided the /Admin and/or /Console switches are no longer needed when connecting to Windows Server 2008.  Although the /Admin switch can be used, it will not actually do anything different than leaving it out, as a person is not permitted to connect to session 0 using RDP.  So it appears I will need to adjust my GPOs after all, but the GPOs will now affect all sessions including the console sessions to Server 2008.  

Details below...

http://support.microsoft.com/kb/947723

In Windows Server 2008 and Windows Server 2008 R2, the /console switch functionality is no longer needed for the following reasons:

Improved application compatibility guarantees that legacy applications that have to communicate with services in session 0 will be installed and run in sessions other than session 0. Additionally, if the service that is associated with an application tries to display UI elements in session 0, a built-in capability in Windows Server 2008, Windows Server 2008 R2 and in Windows Vista enables you to view and to interact with the session 0 UI from your session. Windows Server 2008/Windows Server 2008 R2 session 0 is a noninteractive session that is reserved for services. Therefore, there is no need for you to explicitly connect to this session.

Note For more information about session 0 isolation in Windows Vista, view the "Impact of Session 0 Isolation on Services and Drivers in Windows Vista" topic on the following Microsoft Web site:
      http://go.microsoft.com/fwlink/?LinkId=106201 (http://go.microsoft.com/fwlink/?LinkId=106201)
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

To effectively work with Diskpart on a Server Core, it is necessary to write some small batch script's, because you can't execute diskpart in a remote powershell session. To get startet, place the Diskpart batch script's into a share on your loca…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question