Thank for advance.
The reason you're not seeing anything when you when you disconnect is
because the session stops painting to the desktop device context when you're
not connected. Your application probably captures the desktop region
associated with its main window, which is why it fails.
One solution is to just keep your Remote Desktop Client active, you may need
to check that screen saver is disabled to keep it from failing while you're
not interacting with the session.
Another solution might be to set your server to have auto-logon for the
console & then use a remote execution utility that's session aware to start
your application, provided you can fully automate it. One major downside is
that your machine's console is then always active.
What is your intended application here? Perhaps there's another solution
better suited to your needs.
Drew
--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.asp
"Oleg" <ole...@hotmail.com> wrote in message
news:150d01c48c30$46ec0bd0$a301...@phx.gbl...