Re: Setting the TS mode from DOS prompt??

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Here are the steps:

1. Open a command window (Start - Run - cmd)
2. Type "change logon /disable" (without the quotes) to disallow
new connections to the server
3. Use Terminal Services Manager to verify that there are no user
sessions; send a message to connected users, requesting them to
log off
4. Type "change user /install" (without the quotes) to put the
server into install mode
5. Install your application
6. When the installation is completely finished, type "change user
/execute" to put the server back into it's normal execute mode
7. Type "change logon /enable" to allow users to connect again

Before point 7., you should thoroughly test the newly installed
application, but that's a different thread ...

Description of what happens when the server is in install mode:

186498 - Terminal Server Application Integration Information
http://support.microsoft.com/?kbid=186498
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Joe Guerry" <Joseph.Guerry@xxxxxxxxxxxxxxx> wrote on 17 okt 2006
in microsoft.public.windows.terminal_services:

I'm hopeful this information (change user /install) may help me
with some software that only works properly for users if they
are in the admin group. I need to make sure I understand the
appropriate procedure. Am I supposed logon at the console, make
this change and then (re)install the software? Do I need to
perform these steps in the users remote session as well
(changing user to /install seems to require admin priveleges)?

Thx,

Joe Guerry



"J Porter" <porjoe@xxxxxxx> wrote in message
news:OnOLyYa8GHA.3740@xxxxxxxxxxxxxxxxxxxxxxx
Yes... Milo is correct and I like to go one step further
because a lot of times my installs are actually
updates/upgrades to existing software which may be in use. So,
I prevent users from logging into the system. In case you're
not up on this goodie, it's
change logon /enable
/disable
/query
This command prevents users from logging in. Use the TS Manager
to determine who is connected and maybe request they logoff via
a message.

"Milo Gancarz" <MiloGancarz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:0B712A12-09F4-4468-9EC3-3DC3875EACED@xxxxxxxxxxxxxxxx
You put the server in install mode to enable the application
to be used by
multiple terminal server users. It enables users to save
their own settings
separately, in a very rough approximation, instead of one
user's settings being saved over another's. The commands are
"change user /install" to move
into install mode and "change user /execute" to get out of it.
Doing this is
equivalent to running the install from Add/Remove Programs.
Also, some (most?) Windows Installer packaged applications
(the ones that use .msi files) automatically get into this
mode, but when in doubt you're better off
switching into install mode.

"Paul Fenton" wrote:

Someone told me that before installing new software on a
Windows Server 2003 computer running Terminal Services, TS
has to be put in the "install" mode. It was done from a DOS
prompt. The software is installed, and then TS is put back
into "execute" mode. (I think)

Can anyone explain this to me, the purpose, how it works, and
what the DOS commands are?


Paul Fenton
pfenton@xxxxxxxxxxxxxxxxxxxxxxxx
.



Relevant Pages

  • Re: Terminal Services In Application Server Mode
    ... The change user /install command is used to put your session into install mode, *not* to change the server from application server mode to remote admin mode. ...
    (microsoft.public.windows.terminal_services)
  • Re: Slow application start in Win2K3 terminal server
    ... CHANGE USER /INSTALL ... Then switch back to "Execute Mode"? ... terribly on the terminal server. ... There is a possibility that the case tracking program we use was installed by a user in the organization that is not an admin and did not use install mode. ...
    (microsoft.public.windows.terminal_services)
  • Re: Do I need my W2K3 Server to be a Domain Controller
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... That leaves you with no choice than to install Terminal ... Install mode is a special TS operational mode, ... When a user logs on to the Terminal Server with a Remote ...
    (microsoft.public.windows.terminal_services)
  • Re: Do I need my W2K3 Server to be a Domain Controller
    ... PC's to network with the Server which was running QB2005. ... That leaves you with no choice than to install Terminal Services on ... you must uninstall all user applications before you ... Install mode is a special TS operational mode, ...
    (microsoft.public.windows.terminal_services)
  • Re: Do I need my W2K3 Server to be a Domain Controller
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... That leaves you with no choice than to install Terminal ... Install mode is a special TS operational mode, ... When a user logs on to the Terminal Server with a Remote ...
    (microsoft.public.windows.terminal_services)