Re: Restricting Which Installed Applications Start For Terminal us

"Although I'm a bit puzzled as to why you'd want to run FTP
services on a TS box :-)"

Yea, me too. I don't know what the guy prior to me was thinking. Thanks for
the help!
"Lanwench [MVP - Exchange]" wrote:

Scrivnet78 <Scrivnet78@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Really. I thought you could define which users it installs for in
Add/Remove.

Nope.

In any case, there was no entries in the all users startup folder.
When I removed the check from the Startup entries in MSCONFIG the
applicatin stopped launching on user login, but that also stops the
admin account from automatically launching the program if the server
is rebooted.

Well, I imagine you don't have autologon enabled on a TS box, so this
shouldn't represent a problem if you use the startup folder...

Is the simplest solution to just place a shortcut in the admin startup
folder?

Yes, if you want this to start up when the admin logs in. Which it sounds
like you do. Although I'm a bit puzzled as to why you'd want to run FTP
services on a TS box :-)


"Jeff Pitsch" wrote:

Add/remove programs installs it for all users as well. Please answer
the initial question of how is it starting. the Startup group? the
Run reg key?

Jeff Pitsch
Microsoft MVP - Terminal Services

Scrivnet78 wrote:
The person who is installing these applications didn't do it through
Add/Remove Programs, they ran the EXE by itself. So they are
installed for all users. Do I have to reinstall the apps through
Add/Remove or can I manually stop those applications from loading
when someone logs in?

"Lanwench [MVP - Exchange]" wrote:

Scrivnet78 <Scrivnet78@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,

How can I stop an installed application for starting for every
user on the Terminal Server? For instance, we have a 3rd Party
FTP Server installed on the server and it starts up with every
concurrent user account. I only want this application to start
with the Admin login. This is on Server 2000, running in
Application Mode.
How is it set to autostart? You could put it in the
Administrator's start menu\programs\startup folder, if it's a
startup item.




.

Relevant Pages

  • Re: Restricting Which Installed Applications Start For Terminal us
    ... Scrivnet78 wrote: ... Get another server for that & stick ... When I removed the check from the Startup entries in MSCONFIG the ... Is the simplest solution to just place a shortcut in the admin ...
    (microsoft.public.windows.terminal_services)
  • Re: errors running scheduled tasks
    ... the run as user was a copy of the domain admin ... *** Yes generally exit code 0 means the job that was scheduled completed. ... Note that this is server side of the connection. ... Since you're tranfering via ftp the ftp site admin will need to grant you a ...
    (microsoft.public.windows.server.general)
  • Re: Eingehende Netzverbindung zu anderem Rechner tunneln
    ... Der Server soll mit einer Firewall "dicht gemacht werden". ... Zur Verwaltung sollte der Admin aber noch Zugriff via SSH, FTP und POP3 haben. ...
    (de.comp.os.unix.linux.misc)
  • Re: Restricting Which Installed Applications Start For Terminal us
    ... When I removed the check from the Startup entries in MSCONFIG the ... applicatin stopped launching on user login, ... Is the simplest solution to just place a shortcut in the admin startup ... user on the Terminal Server? ...
    (microsoft.public.windows.terminal_services)
  • Re: FTP fails to start
    ... I stopped the server .. ... $ TCPIP SHOW SERVICE FTP ... TCPIP$CONFIG has a startup and shutdown in it's menu. ...
    (comp.os.vms)
Loading