I frequently log into my Home PC running Windows XP Pro SP3 from work. When I leave home, the session is locked.I recently found out that when I disconnect from a remote desktop session, the computer is left *unlocked* even if I disconnect from the session by locking the PC.I'm fairly certain this wasn't the way things behaved initially. Did this change with SP3?I presently connect from work with a Windows 7 Pro (64 bit) machine but this behavior occurred with my old laptop which ran XP Pro SP3.How do I get the console session to remain locked upon disconnect? LOGGING OFF IS NOT AN OPTION. I have user programs running in the session that need to remain running. I need the session to be running, but locked. 5 people got this answerI do too

Hello,In my case it was the Teamviewer full client that did the problem, especially a version prior to 5.1.9385, when i upgraded to this one the problem went away!Now there is another issue that should be checked, if you have Live Mesh Beta (which runs on windows XP and not the new one that is Vista/7 only) then there are chances that you have enabled the Remote Desktop Feature, you may find two devices under the "Display" node in the Device Manager named "Live Mesh Curtain Driver" and "Live Mesh Mirror Driver", you might want to disable them and restart and check if the problem persists.A final suggestion if the above failed to resolve the issue is to update the network card drivers of your machine.Hope this helps.George SimosMicrosoft MVP - System Center Configuration ManagerMCSE 2003, MCTS Virtualization, ConfigMgr

Hello George,Thanks for the support, i checked doing all the exercise you have suggested but it didn't work out for me.Can you please suggest some things else. Looking forward for your support.BRBye

Hi BR,What O/S are we talking about? Windows XP, Vista, 7 or Windows Server 2003, 2008, 2008 R2 ?George Simos Microsoft MVP - System Center Configuration Manager MCSE 2003, MCTS Virtualization, ConfigMgr

hey GSit is WIN XP SP3

Well then i can't find another reason.... just check that your network drivers are recent and check the driver's date.George Simos Microsoft MVP - System Center Configuration Manager MCSE 2003, MCTS Virtualization, ConfigMgr