Re: Changing from App mode to Remote Admin mode via registry

Wouldn't "definitely" be a bit too definite?

There is a knowledge base article (KB #243215) that references the registry
entry for a Win2K terminal server. The article describes the values as one
of " a number of administrator-configurable values " that should be changed
"only to troubleshoot a problem or better define the user experience for the
sake of administration".

Changing the value from the GUI was supported for aWindows 2000 server; has
Microsoft decided that this was too risky for 2K3?

The value is present in a 2K3 terminal server, so it must serve some
purpose. I didn't add it, so that puts it in a different class than a value
that would not normally be present.

Can you point me to a KB article that discusses this for 2K3, or can you be
a bit more precise about the risks associated with changing this value?

And thank you...I appreciate you taking the time to respond. If we need to
open up a support incident I'm prepared to do that. It just seemed like a
minor question.

Steve

"Rob Leitman [MSFT]" <robleit@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:erQ6vk$iGHA.5036@xxxxxxxxxxxxxxxxxxxxxxx
That is definitely unsupported. Can't you just tell the users not to
install from a remote session?

Rob

--
This posting is provided "AS IS" with no warranties, and confers no
rights.
See the TS FAQ at

http://www.microsoft.com/windowsserver2003/community/centers/terminal/termin
al_faq.mspx

"Steve Sawkins" <ssawkins@xxxxxxxxx> wrote in message
news:%23qU6Ni1iGHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
We're considering advising users to change the TSAppCompat value and
reboot
to move from Application Mode to Remote Administration mode so that they
can
install our product. We can't install properly on a Win 2K3 server
running
TS in app. mode. if the user is logged in remotely.

Are we remiss in suggesting this? Will license servers or unused
licenses
be
affected?

Simple tests in our lab here bear out the fact that this does seem to
change
the mode completely after a reboot, but we have not tested exhaustively.

I've seen posts here on the TSAppCompat value that indicate that
changing
modes is not as simple as changing the value, but I'd like to have our
users
avoid uninstalling Terminal Services so they can install our app.

If we can't suggest that they do this, is there any other way to move
from
app. mode to remote admin. mode, install our application, and move back?

TIA,

Steve Sawkins
Apani Networks






.

Relevant Pages

  • Re: Terminal Server with SBS 2K3
    ... when a normal user logs on the terminal server ... have enough permission to install and uninstall printer drivers. ... If the printer driver for Windows 2003 server is not ...
    (microsoft.public.windows.server.sbs)
  • Re: Changing from App mode to Remote Admin mode via registry
    ... applications on the terminal server. ... Remote admin mode is simply activated by going ... Microsoft MVP - Terminal Server ... We'd like to do this because our application doesn't install right now in ...
    (microsoft.public.windows.terminal_services)
  • Re: Changing from App mode to Remote Admin mode via registry
    ... You can detect if your application is running in a remote ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Remote Administration mode for a Win2K3 terminal server without ... users not to install from a remote session? ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server with SBS 2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... |> Terminal server also, Please make sure that you have configured ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing SMS 2.0 on a 2003 Server
    ... Remote Administration Mode and this doesn't need to be changed. ... through Configure the Server and there is not any Terminal Server parts ... This is a fresh clean formatted server install so there should be ... >> that it has detected that Terminal Server is running and this needs to ...
    (microsoft.public.sms.setup)
Loading