Remote Desktop for Admin Console video problem

[Guest]

Hope this is a good forum. Can't find anything for 2K3.

We are experiencing problems when users use RD4A to connect to a console on
a 2K3 server. Once this happens we lose local console video. Furthermore,
our remote access tool (Radmin) fails. The manufacturer Famatech claims it
is because there is no longer any video signal, which seems to be born out by
the black screen locally. The hardware is Dell. O/S is W2K3 no service
pack. I have correspondence that shows that similar problems occur on XP but
I only personally support servers.

Here is Famatech's explanation:

http://www.famatech.com/support/for...D=6196&MID=8348&phrase_id=1200407#message8348

So I have two questions:

1) Is it possible to allow users to connect via remote desktop but restrict
them from connecting to a console?

2) If the answer to #1 above is no, is it possible to recover from the no
console video problem once someone has logged in via RD4A without rebooting?

tia
gt

 

[Guest]

Only users with the Logon Locally Right can logon to the console. This right
is NOT required to logon to a standard RDP Session.

 

[Guest]

That sounds like a reasonable solution, except that these guys need the logon
right when they use Radmin. To make matters worse most of them are admins.
But its a great idea

 

[Vera Noest [MVP]]

There is one little "trick" that you could try:
when you are finished with your remote console session, you can
actually "push" session zero back to the real console. I do this
all the time with applications that can't run as a service and have
to run as an application on the desktop. Don't know if it works
with Radmin, though.

Put a command file on the desktop of your server with the following
content, and run this command file in stead of disconnecting:

tscon 0 /dest:console

--
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?Q2FudWNrIGdlb2Zm?=