Windows NT RE: Default application not launching

  • Thread starter Thread starter Jaro
  • Start date Start date
J

Jaro

Hi Gonzo,
Please can you explain me exactly how I set this - starting the application
and when close user the application, also the session is closed.
Starting the application is for me easy, but how is possible the rest -
closing application and also the session ?

Many Thanks
Jerry

"Gonzo" wrote:

> Hello everyone,
>
> My customer has several hundreds clients, each of whom connects to one
> of five Win2K servers using remote desktop. All of the clients are
> configured so that when they connect to the server, instead of just
> ending up on the regular Windows screen (with the Start button at the
> bottom and the Desktop showing certain icons), they go right into the
> application they will use for the whole session when they close this
> application, the whole session closes. This seems to work 95% of the
> time, but some times some clients will connect to the server and this
> default application will not launch, with the result that they end up
> in the regular Windows desktop. The questions are:
>
> * What is the best way to configure the remote desktop client (or TS
> server) to launch a certain application instead of going into the
> regular Windows Desktop?
>
> * Anybody knows of any reason why some of the clients will not run the
> default application that has been configured for them, and instead end
> up in the regular Windows desktop on the server?
>
> Thanks for any information and best regards.
>
>
 
That's a built-in feature when you define a starting application,
either on the server in Terminal Services Configuration or in the
rdp client.

_________________________________________________________
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?SmFybw==?= <Jaro@discussions.microsoft.com> wrote on 11
jul 2007 in microsoft.public.windows.terminal_services:

> Hi Gonzo,
> Please can you explain me exactly how I set this - starting the
> application and when close user the application, also the
> session is closed. Starting the application is for me easy, but
> how is possible the rest - closing application and also the
> session ?
>
> Many Thanks
> Jerry
>
> "Gonzo" wrote:
>
>> Hello everyone,
>>
>> My customer has several hundreds clients, each of whom connects
>> to one of five Win2K servers using remote desktop. All of the
>> clients are configured so that when they connect to the server,
>> instead of just ending up on the regular Windows screen (with
>> the Start button at the bottom and the Desktop showing certain
>> icons), they go right into the application they will use for
>> the whole session when they close this application, the whole
>> session closes. This seems to work 95% of the time, but some
>> times some clients will connect to the server and this default
>> application will not launch, with the result that they end up
>> in the regular Windows desktop. The questions are:
>>
>> * What is the best way to configure the remote desktop client
>> (or TS server) to launch a certain application instead of going
>> into the regular Windows Desktop?
>>
>> * Anybody knows of any reason why some of the clients will not
>> run the default application that has been configured for them,
>> and instead end up in the regular Windows desktop on the
>> server?
>>
>> Thanks for any information and best regards.
 
Hello,
RDP client - this is clearly, but where I can configure this in Terminal
Services ? - I know start the application, but how is possible close the
session, when I close the application ?

Thanks Jerry

"Vera Noest [MVP]" wrote:

> That's a built-in feature when you define a starting application,
> either on the server in Terminal Services Configuration or in the
> rdp client.
>
> _________________________________________________________
> 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?SmFybw==?= <Jaro@discussions.microsoft.com> wrote on 11
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Hi Gonzo,
> > Please can you explain me exactly how I set this - starting the
> > application and when close user the application, also the
> > session is closed. Starting the application is for me easy, but
> > how is possible the rest - closing application and also the
> > session ?
> >
> > Many Thanks
> > Jerry
> >
> > "Gonzo" wrote:
> >
> >> Hello everyone,
> >>
> >> My customer has several hundreds clients, each of whom connects
> >> to one of five Win2K servers using remote desktop. All of the
> >> clients are configured so that when they connect to the server,
> >> instead of just ending up on the regular Windows screen (with
> >> the Start button at the bottom and the Desktop showing certain
> >> icons), they go right into the application they will use for
> >> the whole session when they close this application, the whole
> >> session closes. This seems to work 95% of the time, but some
> >> times some clients will connect to the server and this default
> >> application will not launch, with the result that they end up
> >> in the regular Windows desktop. The questions are:
> >>
> >> * What is the best way to configure the remote desktop client
> >> (or TS server) to launch a certain application instead of going
> >> into the regular Windows Desktop?
> >>
> >> * Anybody knows of any reason why some of the clients will not
> >> run the default application that has been configured for them,
> >> and instead end up in the regular Windows desktop on the
> >> server?
> >>
> >> Thanks for any information and best regards.
>
 
You define a starting application for all users on the TS in
Terminal Services Configuration - rdp-tcp connection - Environment
- Start the following program

As I wrote, the session should logoff automatically when a user
exits the starting application. If it doesn't, check this:

From
http://ts.veranoest.net/ts_faq_applications.htm#logoffsession

Q: User sessions don't logoff when users quit their starting or
published application

A: If you define a Starting application, either in Terminal
Services Configuration, a GPO or in the RDP client, the session
should be automatically logged off when users quit the application.
Sometimes, this doesn't happen and users 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 the session, preventing it from
closing and logging off. The same can happen after quitting a
Citrix published application.

To solve the problem, open a 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 user sessions.

Create a batch file, containing something like this:

cd
start /wait <application_executable>
logoff

Now define this batch file as the starting application.
Or use the following vb script (courtesy of Steven Bendis) to
launch your application, and define the vb script as the starting
application.

Dim objWshShell, objExec, strAppExe
strAppExe = "\<application_executable>"
Set objWshShell = CreateObject("WScript.Shell")
Set objExec = objWshShell.Exec(strAppExe)
Do While objExec.Status = 0
WScript.Sleep 500
Loop
Set objExec = objWshSHell.Exec("logoff")


For a different solution to the problem, and a list of known
processes which cause this behaviour, check:

CTX891671 - Graceful Logoff from a Published Application Keeps
Sessions in Active State
http://support.citrix.com/article/CTX891671
_________________________________________________________
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?SmFybw==?= <Jaro@discussions.microsoft.com> wrote on 12
jul 2007 in microsoft.public.windows.terminal_services:

> Hello,
> RDP client - this is clearly, but where I can configure this in
> Terminal Services ? - I know start the application, but how is
> possible close the session, when I close the application ?
>
> Thanks Jerry
>
> "Vera Noest [MVP]" wrote:
>
>> That's a built-in feature when you define a starting
>> application, either on the server in Terminal Services
>> Configuration or in the rdp client.
>>
>> _________________________________________________________
>> 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?SmFybw==?= <Jaro@discussions.microsoft.com> wrote on
>> 11 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Hi Gonzo,
>> > Please can you explain me exactly how I set this - starting
>> > the application and when close user the application, also the
>> > session is closed. Starting the application is for me easy,
>> > but how is possible the rest - closing application and also
>> > the session ?
>> >
>> > Many Thanks
>> > Jerry
>> >
>> > "Gonzo" wrote:
>> >
>> >> Hello everyone,
>> >>
>> >> My customer has several hundreds clients, each of whom
>> >> connects to one of five Win2K servers using remote desktop.
>> >> All of the clients are configured so that when they connect
>> >> to the server, instead of just ending up on the regular
>> >> Windows screen (with the Start button at the bottom and the
>> >> Desktop showing certain icons), they go right into the
>> >> application they will use for the whole session when they
>> >> close this application, the whole session closes. This seems
>> >> to work 95% of the time, but some times some clients will
>> >> connect to the server and this default application will not
>> >> launch, with the result that they end up in the regular
>> >> Windows desktop. The questions are:
>> >>
>> >> * What is the best way to configure the remote desktop
>> >> client (or TS server) to launch a certain application
>> >> instead of going into the regular Windows Desktop?
>> >>
>> >> * Anybody knows of any reason why some of the clients will
>> >> not run the default application that has been configured for
>> >> them, and instead end up in the regular Windows desktop on
>> >> the server?
>> >>
>> >> Thanks for any information and best regards.
 
Last edited by a moderator:
Back
Top