Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / October 2005

Tip: Looking for answers? Try searching our database.

Running spacific program on connection - hangs on exit

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
A. de Verteuil - 28 Oct 2005 15:11 GMT
Hi,
I have a number of sessions which run an RDP connection with 'start a
specific program' set up both on the users properties in local users and
computers and on the client RDP connector.
Most of them work fine however I have just created another one and when I
exit the application the program quits but the session sits with a blue
screen (nothing in it) and does not quit the RDP session. I have made the use
an admin and no different - I have seen other people on the net with the same
issue but no fixes - can anyone help?

Thanks
Vera Noest [MVP] - 28 Oct 2005 21:18 GMT
From the FAQ on http://ts.veranoest.net :

Q. My session doesn't logoff when I quit my starting application

A. If you define a Starting application, either in Terminal
Services Configuration, a GPO or in your RDP client, your session
should be automatically logged off when you quit the application.
Sometimes, this doesn't happen and you are left with a session
which only shows the desktop background, without the possibility to
log off the session manually. The cause for this problem is a
process which is still running in your session, preventing it from
closing and logging off.

To solve the problem, open a second connection to the Terminal
Server and check in Task manager which process is keeping the
session from closing. Some anti-virus applications are known to
cause this behaviour.
If you can't avoid running the process, you can use a work-around
to log off your session.

Create a batch file, containing something like this:
cd <path_to_the_folder_containing_your_application>
start /wait <your_applications_executable>
logoff

Now define this batch file as the starting application.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?QS4gZGUgVmVydGV1aWw=?="
<AdeVerteuil@discussions.microsoft.com> wrote on 28 okt 2005 in
microsoft.public.win2000.termserv.clients:

> Hi,
> I have a number of sessions which run an RDP connection with
[quoted text clipped - 8 lines]
>
> Thanks
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.