Link to home
Start Free TrialLog in
Avatar of SSAFECS
SSAFECS

asked on

Vista remote desktop session logging off my desktop that I remote into

I just upgraded from XP pro to Vista at work. I used to lock my XP machine, then remote in from home and see all of the windows that I had open when I was local to the machine. At the end of the night I would disconnect the remote desktop session and come in the following day and have a locked desktop with all of my windows still open. Now when I remote into my desktop from home, and come into the office the following day, my desktop is logged off and I have to create a new session and try and remember what I was working on.

From the security logs, it appears that my local session is logged off after about 5 minutes after I disconnect the remote session. The entry is an event id of 4647. This change is very very frustrating and I'd really like to find a solution to this, no matter what it takes. I'm a c# novice and would be open to help writing code that blocked log offs if that is my only solution.

Avatar of joinaunion
joinaunion
Flag of Canada image

What type of server?This appears to be the issue.
Avatar of SSAFECS
SSAFECS

ASKER

It's from a vista enterprise laptop (remote) to a vista enterprise desktop (local)

It has to be a configuration issue, as XP did not do this?
Is the local machine behind server?
Avatar of SSAFECS

ASKER

I'm not 100% sure what you mean, it's inside of a network, behind a firewall, a DNS machine etc.

As an update, I remotely RTPed into an XP machine and then RTP from the XP machine into the vista machine and I was able to log into the same Vista session this morning.

Somehow Vista RTP is taking control of a local session or something.
What I mean is at your work do they use a server,because the remote timeout sesion would
have to be adjusted on the server.
Avatar of SSAFECS

ASKER

I'm remoting into another workstation. Do you know where the timeout setting is, I didn't see anything in group policy.

This worked last night, I'll continue to test it throughout the week. I wrapped it in a c# application that blocks logging off without verification first. The same can be done for XP, but the first command is a bit different, it is " tscon 0 /dest:console " instead.

I through the wait commands in, because a few times that I was testing it would release the session before the lock command could run and then it would not lock the machine, so an unlocked desktop was left sitting at the office, not something I wanted to happen. Thanks for the help and encouragement Pete.

tscon.exe RDP-Tcp#0 /dest:console

wait 1

rundll32.exe user32.dll, LockWorkStation

wait 1

exit 

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of joinaunion
joinaunion
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial