sorry, you are wright.
Tried to start mstsc.exe /console and it looks like the normal client. So i didn't connect....
but after connecting it works as jeremy mentioned - sorry, my fault.
thanks, thats the solution i've looked for.
Roland
|
"Dirk Bulinckx" <[EMAIL PROTECTED]> Sent by:
12.02.2004 16:50
|
To: <[EMAIL PROTECTED]> cc: (bcc: Roland Schmid/BBL/MS/PHILIPS) Subject: RE: [SA-list] Problem with SA and W3K/Terminal Server Service Classification:
|
Not correct.
IF SA is running as service (system account with desktop interaction) then you will see the icon on the desktop of the system running SA. Then if that system is a Win2K3 system with Terminal services you can connect to the real desktop of that system using the /console parameter and will be able to see the icon and from the icon call the interface and configure like that. I just tried this and it works. (I did not try in on a Win2K3 datacenter but towards a Win2K3 Standard).
Dirk.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, February 12, 2004 4:42 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Problem with SA and W3K/Terminal Server Service
Hi,
mstsc.exe /console = terminal server console for Windows 2003, called remote desktop connection. Thats what i use.
I know, that, if logon locally to that Server, i have the Icon in the Taskbar and are able to configure whatever i want within SA.
Normally a monitoring tool should run and not stopped as a service, restartet from Menue, configured, closed, restartet as a Service.
And as Servers normally locatet in a Datacenter and a administrator does'nt have his desk in a Datacenter, it's a problem. I don't have the time and its boring me to go downstairs for every tasks to do.....
With Windows 2003 i stopped using pcAnywhere or things like that, cause normally the intergratet consolle is good enough for admin tasks.
But as it looks like, the only resolution is installing pcAnywhere or similar.......................
thanks,
Roland Schmid
