Re: Changing from App mode to Remote Admin mode via registry
- From: "Rob Leitman [MSFT]" <robleit@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 Jun 2006 16:22:37 -0700
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/terminal/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 torights.
install from a remote session?
Rob
--
This posting is provided "AS IS" with no warranties, and confers no
See the TS FAQ athttp://www.microsoft.com/windowsserver2003/community/centers/terminal/termin
al_faq.mspx
running
"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
licensesTS in app. mode. if the user is logged in remotely.
Are we remiss in suggesting this? Will license servers or unused
changingbe
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
frommodes 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
app. mode to remote admin. mode, install our application, and move
back?
TIA,
Steve Sawkins
Apani Networks
.
- Follow-Ups:
- Re: Changing from App mode to Remote Admin mode via registry
- From: Steve Sawkins
- Re: Changing from App mode to Remote Admin mode via registry
- References:
- Changing from App mode to Remote Admin mode via registry
- From: Steve Sawkins
- Re: Changing from App mode to Remote Admin mode via registry
- From: Rob Leitman [MSFT]
- Re: Changing from App mode to Remote Admin mode via registry
- From: Steve Sawkins
- Changing from App mode to Remote Admin mode via registry
- Prev by Date: RDP Printers not being deleted on server when Session is closed
- Next by Date: Re: another NLB solution
- Previous by thread: Re: Changing from App mode to Remote Admin mode via registry
- Next by thread: Re: Changing from App mode to Remote Admin mode via registry
- Index(es):
Relevant Pages
|