Single application exiting problem

  • Thread starter Thread starter Tony Cimello
  • Start date Start date
T

Tony Cimello

I am trying to perform the following tasks:

1. Have user click on an icon to start an application on
the terminal server. (Great Plains E-Enterprise)

2. Do NOT execute the normal user logon script.

3. Run the application above.

4. Upon closing the application end the entire session.

I've tried a batch file with an exit command in the
client side start app on connect, which started the app
correctly, but let the logon script still run and didn't
end the application on exit, just left a blank desktop.

I know you can end the session using ctrl+alt+end, but I
really don't want my users to have to think that hard.
I'd like this to appear as if they were running the app
on their own desks.
 
you need to use the environment tab to deply the single app and block the
script via GPO
 
Will using the environment tab allow for the session to
end upon exiting the application? When using the GPO -
is that the local group policy? This is a mixed domain
with the terminal services server running in non-AD mode.
 
Actually, now that I look at it, I don't see where using
the environment tab on the server is any different than
using the program tab on the client. I don't want ALL
logins to run only one program, I want to create two
connections on the desktop. One that runs only the
program and one that allows for normal terminal services
access.
 
You do realize that each program will launch a separate RDP Session, yes? If users need both to be able to launch individual apps, or the explorer shell then using the Remote Desktop Client options or a 3rd party application like Citrix MetaFrame or WTSPortal are your options

Terminal Services add-ons listed here

http://www.workthin.com/tsao.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.com
 
All I need to be able to do is:

1. Log onto the terminal server and not launch a logon
script when the run a program option is used. (preferred
but not necessary due to asynch logon script launching)

and

2. Exit the single app that I am running AND close the
session at the same time.

If there is an option to run a single application on
launch I would figure there would be a simple way to get
out of the session, sort of like using the exit command
in a batch file.
-----Original Message-----
You do realize that each program will launch a separate
Click to expand...
RDP Session, yes? If users need both to be able to
launch individual apps, or the explorer shell then using
the Remote Desktop Client options or a 3rd party
application like Citrix MetaFrame or WTSPortal are your
options.
 
anony,
First, don't launch the app from the client, do it from the server, the
key being, centralization. Second, if all you want to do is launch and app,
enter in the environment tab and when they close the app it will log them
off the session. You are making it harder than it is I think.

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com
 
If I put the app in the environment tab then they can
*only* launch that app right? I need both - be able to
run just the app as one mode, and the whole desktop as
another.

I found a program called AppliDis that seems to do what I
need, it's just a shame that the functionality in the
program doesn't come in Windows. Just like printing...

Having to use third party programs to achieve what should
be built in results is getting frustrating LOL!
 
Back
Top