Re: Remote Connection
From: Frank McCallister SBS MVP (anonymous)
Date: 12/20/04
- Next message: Steve Hess: "Moving FSMO Roles from SBS Server"
- Previous message: Marty: "Re: Invalid Bookmarks"
- In reply to: cdhitman: "Remote Connection"
- Next in thread: cdhitman: "Re: Remote Connection"
- Reply: cdhitman: "Re: Remote Connection"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 19 Dec 2004 20:48:42 -0600
Hi Steve
What Axel says is correct. You should Logoff the WS instead of disconnect.
This will leave the WS at the Logon Screen for the Next user.
-- Frank McCallister SBS MVP COMPUMAC "cdhitman" <cdhitman@discussions.microsoft.com> wrote in message news:97A152C0-DC43-4A4C-B281-0EAD44521221@microsoft.com... > Hey everyone, > > Quick question: I've had sporattic instances of me connecting to the > server > remotely from home, and then further connecting to a desktop client at the > office through the server. Automatically, when this happens that specific > desktop becomes "locked". Essentially what should happen is that when I > disconnect from the server or terminate the connection to that remote > desktop, it should automatically "unlock" and all is well. Unfortunately, > sometimes this doesn't happen and I have been led to run down to the > office > to manually unlock that workstation so the office staff can use it. Is > this > issue common and are there workarounds around it? I have checked in > "terminal > services manager" when this occurs and indeed the connection remains > active. > I have leanred how to manually disconnect the session from TS manager. But > should I have to continually do this? Thanks. > > -Steve
- Next message: Steve Hess: "Moving FSMO Roles from SBS Server"
- Previous message: Marty: "Re: Invalid Bookmarks"
- In reply to: cdhitman: "Remote Connection"
- Next in thread: cdhitman: "Re: Remote Connection"
- Reply: cdhitman: "Re: Remote Connection"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|