Re: RDP Sessions not "disconnecting"
- From: "Frank McCallister SBS MVP" <anonymous>
- Date: Fri, 8 Jun 2007 00:16:46 -0500
Yes simply disconnecting does not free up the session unless you go into TS Manager and reset the session. Th user must logout to free up the session.
To use the /console switch enter RDP from a command prompt or Run command with mstsc /v:address /console. Only one user may login to console at a time so if you logon to console remotely this will blank the Server console screen.
--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"Blake" <Blake@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:5C80A54D-376A-46E5-B35F-EA3F8852BBDD@xxxxxxxxxxxxxxxx
Thanks Frank..
And this hits my original question - when Owner disconnects, he's off the
machine, but the Terminal Services Manager still shows his session, albeit
"Disconnected" - That in turn is locking out the 2nd connection. It isn't
until I re-connect/log-on and reset the session- for which it then
disappears. Admin2 can now log on. Is this right? I would think that
disconnecting would free up the RDP without having to go in and reset/refresh
things.
Secondly, is this proof that Owner ISN'T fully logging off? But, simply
disconnecting? I think he's merely shutting down RDP window. He's not the
most patient guy, and not computer savy, but hard headed as can be!
This may be elementry, but what is the /console switch? In where? That
sounds like a viable option right now if it will keep Admin logged on but
free up an RDP connection.
Thanks again,
Blake
"Frank McCallister SBS MVP" wrote:
Hi Blake
Two Choices here. You can logon to the Console as Admin and Disconnect
instead of logging off and this will leave Admin logged on to Synch Act and
will leave 2 more Remote slots open. To logon to Console use the /console
switch. The other choice is to disconnect from a normal session as Admin
instead of Logging off and when you connect again you will resume your
session. The second choice may anger the owner as if Admin and Admin2 are
logged on he won't be able to unless he is knowledgeable enough to know
about the /console switch
--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"Blake" <Blake@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:94E19ED1-6618-437E-B60B-40EB49DAAC47@xxxxxxxxxxxxxxxx
> Haha, i knew someone would ask, and was initially inclined to put that
> very
> explanation in my original post.
>
> To cut to the chase, 2 of us admin the machine - we each have our own
> login.
> The 3rd, however, only logs in occassionally - I do the regular IT > stuff,
> she manages some of the server based apps like ACT for Workgroups, and
> QuickBooks, etc. etc. She's not using it as a WS - but to manage the
> server based apps - she also hits it from remote. But the 3rd (the one
> I'm
> skeptical about logging off versus disconnecting) is the Company Owner.
> He's
> as hard-headed as a brick, and insists remotely loggin on to server > verses
> his Desktop to hit these 3rd party apps (ACT, Quickbooks, etc.) when > he's
> on
> the road. If he needs email and such, he RWW's to his desktop - but > won't
> got RWW/DP then back to the server based ACT and QB. I've tried to
> explain
> to him numeruous times to no avail. Note that he's my client (not > boss,
> but
> client)
>
> So, it's when he occassionally logs on and then fails to fully > disconnect,
> it prevents Admin2 from getting in to do her thing with QB and ACT and
> such.
>
> Which leads me to my next question/point... Can I, as Admin, close out > my
> RDP connection WITHOUT logging off. We have to keep Admin logged on > for
> ACT
> Workgroups to run properly (the remote synching) so I end up keeping > my
> session there, or at least "disconnected" which i'm thinking uses up > one
> of
> the 2 slots. If I fully log off, then it logs admin off and ACT remote
> synchronizing stops.
>
> Thanks, blake
>
> "Henry Craven {SBS-MVP}" wrote:
>
>> Ok ...feel I need to ask...
>>
>> WHY are three of you tripping over each other logging onto the server >> ?
>> ...need we again point out that the Server is -not- a Workstation and
>> shouldn't be used as one ?
>> The TS Sessions on the server are for Administration Only, not running
>> applications.
>>
>> -- >> Henry Craven {SBS-MVP}
>>
>>
>> "Blake" <Blake@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:EE9CE9A0-A8DD-45DA-8482-7E9803AD0FCD@xxxxxxxxxxxxxxxx
>> > There are a total of 3 of us that remotely access our SBS2003 server
>> > from
>> > outside the network (and sometimes from inside) I'm getting >> > instances
>> > where
>> > if 2 of us are logged on, but one logs off, his session is remaining >> > in
>> > the
>> > Terminal Services window, and preventing the 3rd person from loggin >> > in.
>> > I
>> > always have to go to Terminal Services, and "Reset" the session and >> > it
>> > disappears. The 3rd user is then able to login.
>> >
>> > I was thinking that he is simply "disconnecting" his session, rather
>> > than
>> > "Logging Off" the server, but he insists that he's logging off.
>> > (Though
>> > i'm
>> > still skeptical) Is there any reason why the session would remain >> > in
>> > the
>> > list, and if so, how can i ensure it's cleared out when someone >> > get's
>> > off?
>> >
>> > Thanks,
>> > Blake
>>
- References:
- Re: RDP Sessions not "disconnecting"
- From: Henry Craven {SBS-MVP}
- Re: RDP Sessions not "disconnecting"
- From: Blake
- Re: RDP Sessions not "disconnecting"
- From: Frank McCallister SBS MVP
- Re: RDP Sessions not "disconnecting"
- From: Blake
- Re: RDP Sessions not "disconnecting"
- Prev by Date: Re: RWW or VPN issues with remote access
- Next by Date: RE: Connection Manager connects but network not visible
- Previous by thread: Re: RDP Sessions not "disconnecting"
- Next by thread: Problem Companyweb
- Index(es):
Relevant Pages
|
