jpierson_jerome
asked on
Windows 2003 Terminal Service sessions will not logoff
I manage a 2003 Terminal Server. Normally, we have 30 active sessions at a time. We run several apps including Office, Pervassive SQL client, Attachemante, and several other small apps.
Users access this server from XP and 2000 clients.
The server ran perfectly for many months. About 2 months ago we started having a problem. Users can not logoff the server. They can close the session by clicking on the 'X', but when they do a start > logoff, the server appears to hang forever.
I have setup group policy to force a disconnected session to logoff after 1 minute of inactivity. This works. Through Terminal Manager, I can force a logoff or disconnect.
For many reasons, closing a session by logging off is a much preferred method of exiting a session.
My thinking is that this problem was possibly caused by an update, but I can't confirm this.
Any thoughts on this?
Users access this server from XP and 2000 clients.
The server ran perfectly for many months. About 2 months ago we started having a problem. Users can not logoff the server. They can close the session by clicking on the 'X', but when they do a start > logoff, the server appears to hang forever.
I have setup group policy to force a disconnected session to logoff after 1 minute of inactivity. This works. Through Terminal Manager, I can force a logoff or disconnect.
For many reasons, closing a session by logging off is a much preferred method of exiting a session.
My thinking is that this problem was possibly caused by an update, but I can't confirm this.
Any thoughts on this?
I am running a couple of 2003 servers with the latest windows critical updates and haven't seen this issue. Just out of curiosity, how are the user profiles managed (i.e. roaming, local, etc...)?
ASKER
Local only.
It was an issue of timing and ruling out everything that I could think of that led me to consider that updates were the cause.
It was an issue of timing and ruling out everything that I could think of that led me to consider that updates were the cause.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oops... On 2003 the event IDs your looking for are 1517 and 1524 (1000 is the 2K error). Good luck.
ASKER
I downloaded the hive tool and that didn't seem to make any difference, but...
Ya got me to thinkin. At one point I suspected this was a profile issue and this problem also occured right after the SMS Remote Control / Mngt agent was installed.
I disabled the two services associated with SMS and another management tool.
I then tried to rename my old local profile and couldn't. Long after I had logged off that account, the C:\Documents and Settings\jpierson\Local Settings\Application Data\Microsoft\Windows\Usr
It is late and my head is foggy, but these profiles should not be 'locked' if there is no one logged on - correct?
So I figured, maybe the hive tool wouldn't work unless I rebooted - the service was running, but if the profiles were tied up then maybe the hive tool couldn't work. Apparently (I am guessing) that was the case. My profiles are now 'unlocked' and I can logoff properly. In fact, the logoff is quicker than ever.
I believe your suggestions was correct. BUT, I didn't have any of the associated events in my event logs.
FYI, I don't think SMS or the other management tool have anything to do with my problem, I added that just to try to make the documentation complete. I still have them disabled. Sometime this week, I will re-enable the services just to make sure they weren't part of the problem.
Thanks for the help.
Ya got me to thinkin. At one point I suspected this was a profile issue and this problem also occured right after the SMS Remote Control / Mngt agent was installed.
I disabled the two services associated with SMS and another management tool.
I then tried to rename my old local profile and couldn't. Long after I had logged off that account, the C:\Documents and Settings\jpierson\Local Settings\Application Data\Microsoft\Windows\Usr
It is late and my head is foggy, but these profiles should not be 'locked' if there is no one logged on - correct?
So I figured, maybe the hive tool wouldn't work unless I rebooted - the service was running, but if the profiles were tied up then maybe the hive tool couldn't work. Apparently (I am guessing) that was the case. My profiles are now 'unlocked' and I can logoff properly. In fact, the logoff is quicker than ever.
I believe your suggestions was correct. BUT, I didn't have any of the associated events in my event logs.
FYI, I don't think SMS or the other management tool have anything to do with my problem, I added that just to try to make the documentation complete. I still have them disabled. Sometime this week, I will re-enable the services just to make sure they weren't part of the problem.
Thanks for the help.