Is the server running W2K or 2003?
If it runs 2003, you could configure the server for autologon and
start the application on the console, through a shortcut in the
Autostart folder.
And then you could connect to it from your workstation with the
mstsc /console command.
_________________________________________________________
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
"John Leenders" <(E-Mail Removed)> wrote on 01 jul 2005:
> Perhaps I should explain a little bit more...
>
> The server is at a remote location, so management is done via
> Terminal server in admin mode. The server needs to be running
> some GUI program which doesn;t have a service option ie it must
> run in a user session. Especially because it provides
> information which needs to be evaluated (so running something
> like svrany/firedaemon etc is out, they provided only local
> (console) access to the GUI). I don't want to install VNC
> because this is less secure. Currently when the machine reboots,
> i open a terminal session and start the application. However
> when the reboot is unexpected (ie a power outage) I' m not
> always aware of this fact, and the system (the GUI) stays
> down....
>
> So after reboot the server should open a terminal session to
> itself, in which the program would be started. And then the
> server would disconnect the session, leaving it running to be
> accessed from some where else.
>
> if you have any other ideas they are very welcome...!
>
> Doesn't the autologon of the server open the possibility of a
> 'deadlock' ie the server keeps opening sessions?
>
> thanks in advance
>
> John