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

What exactly is it that you want to achieve?
If you want to enforce that your application is installed from the
physical console, you can check that in your installation
procedure:

From http://ts.veranoest.net/ts_faq.htm

Q. How can my script / application detect if it is running in a
Terminal Services client session?

A. You can detect if your application is running in a remote
session by calling GetSystemMetrics().
The following function returns TRUE if the application is running
in a remote session and FALSE if the application is running on the
console.

BOOL IsRemoteSession(void)
{
return GetSystemMetrics( SM_REMOTESESSION );
}


_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"Steve Sawkins" <ssawkins@xxxxxxxxx> wrote on 14 jun 2006:

So does Microsoft offer a way to change from Application mode to
Remote Administration mode for a Win2K3 terminal server without
uninstalling terminal server?

Again, a Windows 2000 TS could legitimately do this(it was in
the GUI), and the knowledge base article indicated that the
value was modifiable. The only "not configurable" value in the
KB article was the ProductVersion.

Would you recommend some of the WMI provider stuff for Terminal
Services? I notice that there's a Win32_TerminalServiceSetting
class with a ChangeMode method that lets the caller set the mode
to one of three values:

Value Meaning
0 Remote Desktop for Administration or Personal Terminal
Server. 2 Per Device. Valid for application servers.
4 Per Session. Valid for application servers.


I haven't had much success with these, but I can't find any
other sanctioned way of doing this.

Steve

"Rob Leitman [MSFT]" <robleit@xxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23LyMk%23vjGHA.4508@xxxxxxxxxxxxxxxxxxxxxxx
This registry value is a side effect of changing the TS mode,
not what causes the change.

There are many registry values, but most aren't meant to be
modified directly. Think of it as internal data.

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/term
inal/terminal_faq.mspx

"Steve Sawkins" <ssawkins@xxxxxxxxxxxxx> wrote in message
news:6krig.11274$921.5051@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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/term
inal/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: Installing SMS 2.0 on a 2003 Server
    ... I am unsure about what you are talking about when you say "Remote ... Terminal Services (Heck if we insist that is it installed, ... "Roger Crawford" wrote in message ... Then it gives me the error> that it has detected that Terminal Server is running and this needs to be in> intsall mode. ...
    (microsoft.public.sms.setup)
  • 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: Problems after SP2
    ... Can you connect to RWW and then remote to a client PC, or is this effecting clients and server? ... > install last time we tried it I think I'll just skip it and forge ahead ...
    (microsoft.public.windows.server.sbs)
  • RE: Re: Remote connections
    ... the TSWeb client is a simple and ActiveX based terminal server ... management remote control programs ...
    (Focus-Microsoft)