Lost access to console when someone else connects with /console

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

snj2000 - 11 Jul 2005 19:50 GMT

Is there any way, from the real console, you can prevent loss of access to
the console when someone else logs into that server with /console?

The person logging in with /console gets no indication that I am at the
console loggged in, they are logging into the server using the same userid as
I used at the main console.

I get presented with the PRESS CTL/ALT/DEL prompt at the main console when
somone else remotes into the CONSOLE. If I log back in, they get forced off.

Reply to this Message

Vera Noest [MVP] - 12 Jul 2005 00:01 GMT

This is by design.
Don't use shared accounts, give every administrator his or her own
unique account with Administrator rights.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?c25qMjAwMA==?=" <snj2000@discussions.microsoft.com>
wrote on 11 jul 2005 in microsoft.public.win2000.termserv.clients:

> Is there any way, from the real console, you can prevent loss of
> access to the console when someone else logs into that server
[quoted text clipped - 7 lines]
> console when somone else remotes into the CONSOLE. If I log
> back in, they get forced off.

Reply to this Message

snj2000 - 27 Jul 2005 21:37 GMT

So, maybe we are using the wrong tool? I have a need to remotely see the
actual screen that is being displayed for the user who is logged into the
server. For example, to see an error message that is being displayed in a
window, or monitor progress of an application running. If I am not mistaken,
if I as an ADMINISTRATOR were to log into that server with MY account rather
than the account that was actually logged in AT the server, I would not "SEE"
the same desktop and windows as I would if I logged into the same account
that is logged in at the server.

So that is why I am remotely connecting using the account that is being used
at the server, but as I stated, that "steals" the console from then and they
have to CTL/ALT/DEL to log back in to get it back, which of course, forces me
out......

> This is by design.
> Don't use shared accounts, give every administrator his or her own
[quoted text clipped - 19 lines]
> > console when somone else remotes into the CONSOLE. If I log
> > back in, they get forced off.

Reply to this Message

Vera Noest [MVP] - 27 Jul 2005 22:29 GMT

You are not running an application on the console of the server,
which must run interactively all the time, are you?
If that's the case, then you have to use the same user account when
connecting directly to the console, as you describe.
But if that is the case, it's not the tool that's wrong, it's the
application :-) Have you tried running the application as a
service, with SrvAny from the Resource Kit?

If the above is not your setup, and you simply want to see if there
are any error messages on the console, or check a service which
only is accessible in the system tray on the console, then you can
use any account with administrative rights. Nobody needs to be
logged on at the physical console. You will then get a warning if
another admin is already logged on to session 0, and can choose if
you want to throw the other admin out or not.

For both scenarios above, it's still possible to achieve what you
want, with unique administrative accounts for every admin.
You can shadow the console from within a normal session to the
server. Documented here:

278845 - How to Connect to and Shadow the Console Session with
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=278845

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?c25qMjAwMA==?=" <snj2000@discussions.microsoft.com>
wrote on 27 jul 2005 in microsoft.public.win2000.termserv.clients:

> So, maybe we are using the wrong tool? I have a need to
> remotely see the actual screen that is being displayed for the
[quoted text clipped - 36 lines]
>> > console when somone else remotes into the CONSOLE. If I log
>> > back in, they get forced off.

Reply to this Message