Re: Remote desktop unlocking

On Apr 25, 2:54 pm, "Herb Martin" <n...@xxxxxxxxxxxxxx> wrote:
"Sarconastic" <w...@xxxxxxxxxx> wrote in message

news:1177528901.028259.157880@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

We recently installed a new 2003 server in both our locations, vpn'd
them together. Now we are really enjoying the remote desktop. We are
able to acces pc's at the other location and pull down information
someone here may need. The only real problem is when you log off RDC
it locks the pc with your logon, in this case admin.

NOT if you actually LOG OFF (as you say). When you merely
DISCONNECT it leaves your session running as it should.

We are using the LOG OFF, not the DISCONNECT. I understand that the
Disconnect leaves the programs running and preserves the desktop
enviroment. And logoff is supposed to take you clear out of the
session.

Which makes it so
the user can't log back in. Is there a way t o circumvent this
feature. I know it's doing what they want for people using it for
productiviy. But it bites for us.

Logoff when finished.

WHat is happening is while we are RDC'd into the pc. it has the "This
workstation has been locked" screen in place. After we LOG OFF the
session it goes back to the CTL+ALT+DEL Screen. When you go back in as
a user on the workstation and try to log in it pops up the "Your
interactive logon priveledge has been disabled" message and will not
allow logon.
So you have to logon on as admin first. Then everything returns to
normal.

ANy more help will be great.

Kevin w.


.

Relevant Pages

  • Re: Remote Desktop to XP Pro Problems
    ... I'm sorry to come back with so little, but from asking around, barring GP settings that would force logoff of disconnected sessions after sufficient idle time, you should not be losing sessions like this. ... You might want to check the Event Log and see what is happening in the period between disconnection and reconnection to see if the session is being logged off through some other mechanism. ... Disconnect is the correct option; logoff will definitely kill any running ... >>>> We are using Remote Desktop to access XP Pro desktops. ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Desktop to XP Pro Problems
    ... Being the "console" shouldn't matter much one way or another (Vista and Longhorn reserve the console session, session 0, for services; no one actually logs in to it). ... Disconnect is the correct option; logoff will definitely kill any running programs. ... >> We are using Remote Desktop to access XP Pro desktops. ...
    (microsoft.public.windows.terminal_services)
  • Re: Enforce session timeout on Remote Desktop
    ... There some Group Policies that you can configure to disconnect idle sessions. ... > We are using Remote Desktop for users to connect remotely back to our network ... > inactive for a long period of time, we would like to have the session ...
    (microsoft.public.windowsxp.work_remotely)
  • Remote Desktop - change in the way I am asked to logon - whats happened ?
    ... Hi - I use Remote Desktop to access a machine on the same LAN. ... the target machine is W2003. ... screen was an image of teh other machines logon screen (in other words ... for the 'remote desktop with logon handled through the RD session' as ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: RDP Session Closing Delay
    ... Thanks, Jeff, you and Vera both nailed it. ... Task Manager in a 2nd session: I opened a 2nd session to TS with no ... at logon that you are secure. ... I'm hoping there may be a disconnect parameter in the TS registry ...
    (microsoft.public.windows.terminal_services)
Loading