Carl,
Thanks. We had noticed what you describe, though it is not clear to me why
Microsoft would do that.
In any case, we will follow your suggestion to do autologon whenever
possible. Of course, this also means, we have to configure a very short
duration of lockout for security reasons. Correct?
Jay
----- Original Message -----
From: "Carl Houseman" <[EMAIL PROTECTED]>
To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com>
Sent: Tuesday, June 24, 2008 6:39 PM
Subject: RE: RDP in console mode -- often it is not so
If the console session was first logged on at the PHYSICAL console before
you connected to it with RDP, then the environment will reflect:
SESSIONNAME=Console
If the console session was logged out and you connect to it with RDP, then
you get this or similar:
SESSIONNAME=RDP-Tcp#5
The remedy? Establish autologon so the console is logged on as soon as
the
system boots, and be careful never to logout from the console session -
only
disconnect. This presumes the same username can be used and password
known
to anyone who would take remote control of the console.
Carl
-----Original Message-----
From: Ajay Kulsh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2008 9:17 PM
To: NT System Admin Issues
Subject: RDP in console mode -- often it is not so
When using Microft Remote Desktops MMC, you can check a box to have RDP
session via console. You can also use mstsc.exe with "/console" switch to
use console mode.
However, once I connect using these options and run Set command on the
connected server, often it shows that the session is NOT in console mode;
rather it is in a terminal session mode.
Does anyone know what causes this inconsistent behavior and how to remedy
it? Thanks.
- Jay Kulsh
So. Pasadena, CA
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
