28 Replies
· · ·
Serrano
OP
Feb 21, 2012 at 11:07 UTC
Atos N.A. is an IT service provider.
Is the remote or your Win 7 box set to "log off" after a timeout instead of "lock"?
0
· · ·
Serrano
OP
Feb 21, 2012 at 11:10 UTC
Open gpedit.msc
Browse to Computer Configuration --> Administrative Templates --> Windows Components --> Remote Desktop Services --> Remote Desktop Session Host --> Session Time Limits.
Enable the "Set time limit for disconnected sessions" and set it to Never
5
· · ·
Datil
OP
Feb 21, 2012 at 11:10 UTC
I know with remote desktop with terminal server there is a setting that will log off an inactive connection after a certain time. A group policy can control this any may be applying to the windows 7 boxes as well. Ours is set to keep the session alive for an indefinite amount of time.
Here's the policy and details:
//technet.microsoft.com/en-us/library/cc753112[v=ws.10].aspx
0
· · ·
Thai Pepper
OP
Feb 21, 2012 at 11:10 UTC
What is the operating system of the computer you are remoting into? I know Microsoft allows up 2 two users to be logged into the same box without have terminal server licensing.
0
· · ·
Chipotle
OP
Feb 21, 2012 at 11:20 UTC
It is a Windows 7 box that is being remoted into. From either a Windows 7 or XP machine. I have already tried setting up the session time limits but it hasn't been working.
0
· · ·
Serrano
OP
Feb 21, 2012 at 11:32 UTC
Check your active directory for user properties, under sessions make sure End a disconnected session, Active session limit, and Idle session limit are all set to never.
0
· · ·
Chipotle
OP
Feb 21, 2012 at 11:46 UTC
They already are. Just double checked.
0
· · ·
Serrano
OP
Feb 21, 2012 at 11:49 UTC
I found that if I change the Local Security Policy under Local Policies->Security Options-> Interactive logon: Do not require CTRL+ALT+Del" to Enabled, the problem dissapears.
0
· · ·
Chipotle
OP
Feb 21, 2012 at 12:02 UTC
We will give it a try.
0
· · ·
Chipotle
OP
Feb 21, 2012 at 12:50 UTC
That didn't work either.
0
· · ·
Ghost Chili
OP
Feb 21, 2012 at 12:55 UTC
curious.... are both users logging in to the same Win 7 box? are you just punting eachother "coincidentally"?
0
· · ·
Chipotle
OP
Feb 21, 2012 at 12:56 UTC
No these are different Win 7 boxes. These are our own desktops that we are remoting into.
0
· · ·
Serrano
OP
Feb 21, 2012 at 13:33 UTC
This keeps sounding like you have a rogue GPO in place somewhere. Have you done a gpresults and see what pops up on the remote PCs?
0
· · ·
Chipotle
OP
Feb 21, 2012 at 15:07 UTC
I am running it on both machines and nothing looks out of the ordinary.
0
· · ·
Serrano
OP
Feb 21, 2012 at 15:21 UTC
So the problem is only on a few of your Windows 7 boxes. Have you had one of the people this is happening to log into a different machine to see if the results are the same?
Are you using roaming profiles or redirected folders?
0
· · ·
Chipotle
OP
Feb 21, 2012 at 15:44 UTC
Yes I've tried that. I can remote into other machines no problem. It doesn't matter which machine I remote from when I am remoting into my problem child one it always does it.
No I'm not using roaming profiles or redirected folders.
0
· · ·
Serrano
OP
Feb 21, 2012 at 15:46 UTC
How many machines are affected, that you know of? Just one?
0
· · ·
Chipotle
OP
Feb 21, 2012 at 15:49 UTC
Two. Mine and one of the users. We are the only two it happens to.
0
· · ·
Datil
OP
Feb 21, 2012 at 15:55 UTC
This looks like an old issue. Here's a post I found:
//social.technet.microsoft.com/Forums/nb-NO/w7itprogeneral/thread/1d17617a-a222-4292-a6e5-1c522ed67f5f
0
· · ·
Chipotle
OP
Feb 21, 2012 at 16:07 UTC
I remember reading that article. It didn't work. Everything is already set to never.
0
· · ·
Serrano
OP
Feb 21, 2012 at 16:12 UTC
And if someone else other than you and the other person this affects logs into the afflicted machines? Does it exhibit the same behavior?
I'd create a user, log in with them and see if it happens the same way. At least then you'll know if it's a machine issues or a user issue.
0
· · ·
Pimiento
OP
Jan 28, 2013 at 00:44 UTC
1st Post
had the same problem. figured it out finally!
someone at work had set me up with my own OU so i could stay rdp'd longer than the default time permitted for users, well they also set it to 'terminate disconnected session' after 12 hours [unbeknownst to me]. so after looking at all the wrong OU's and wild goose chases for a while, i finally figured i would check my OU, but ADUC only showed that I had an OU not the settings, so i had to go into GPMC to see the actual settings for my OU and boom, there it was - TERMINATE DISCONNECTED SESSION = 12 HOURS... BOOO HISSS! changed to never, game over!
hope this helps, someone somehow...
0
· · ·
Pimiento
OP
Sep 19, 2013 at 05:17 UTC
1st Post
how do i check this?
0
· · ·
Pimiento
OP
Apr 10, 2014 at 18:24 UTC
1st Post
Perfect simple answer.
Thank You
0
- 1
- 2
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.