Prev: SBS 2008 - views on virtualization
Next: IE on Server2003 hosed by hotfix
From: Milhouse Van Houten on 7 Jul 2010 17:31
Hi Merv,

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.server.sbs&tid=18bf4b8f-fcd1-4bc7-a079-26a7444938ae&cat=&lang=&cr=&sloc=&p=1

Do you remember that old thread? I have the same problem as SolveIT, and
like him, TSAppCompat is already at 0.

However, later on he revealed that TSEnabled=1 solved the problem for him,
to which you replied "Now if we can just figure out how TSENabled
got set to 0 in the first place."

Ours is 0 as well -- but isn't that the default? Can you check on your
SBS2003 system please? I'll change it to 1 if that's correct, but the best
I can find is that 0 is the default. Anything to solve this problem, though.

Thanks

From: Chris Puckett [MSFT] on 8 Jul 2010 11:09
TSEnabled will be set to 0 if Terminal Services has been disabled.

TSEnabled - Indicates whether Terminal Services is enabled or not.
Type: REG_DWORD
Data value: 0x1 Enabled
Data value: 0x0 Disabled

There are two ways I can think of to do this in the UI (looks like it may
require a reboot for the change in the registry to take place)

1. Start - Admin Tools - Terminal Services Configuration - Connections -
Right-click RDP-TCP and go to All Tasks- Disable.

2. Properties of My Computer - Remote tab - Uncheck 'enable remote
desktop...'

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"Milhouse Van Houten" <btvs(a)myrealbox.com> wrote in message
news:#3$BMvhHLHA.1016(a)TK2MSFTNGP06.phx.gbl...
> Hi Merv,
>
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.server.sbs&tid=18bf4b8f-fcd1-4bc7-a079-26a7444938ae&cat=&lang=&cr=&sloc=&p=1
>
> Do you remember that old thread? I have the same problem as SolveIT, and
> like him, TSAppCompat is already at 0.
>
> However, later on he revealed that TSEnabled=1 solved the problem for him,
> to which you replied "Now if we can just figure out how TSENabled
> got set to 0 in the first place."
>
> Ours is 0 as well -- but isn't that the default? Can you check on your
> SBS2003 system please? I'll change it to 1 if that's correct, but the
> best I can find is that 0 is the default. Anything to solve this problem,
> though.
>
> Thanks

From: Al Williams on 8 Jul 2010 11:11
On our SBS 2003 SP2 TSAppCompat=0 and TSEnabled=1 so I would change
TSEnabled to 1 and reboot.

--
Allan Williams




Milhouse Van Houten wrote:
> Hi Merv,
>
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.server.sbs&tid=18bf4b8f-fcd1-4bc7-a079-26a7444938ae&cat=&lang=&cr=&sloc=&p=1
>
> Do you remember that old thread? I have the same problem as SolveIT,
> and like him, TSAppCompat is already at 0.
>
> However, later on he revealed that TSEnabled=1 solved the problem for
> him, to which you replied "Now if we can just figure out how TSENabled
> got set to 0 in the first place."
>
> Ours is 0 as well -- but isn't that the default? Can you check on
> your SBS2003 system please? I'll change it to 1 if that's correct,
> but the best I can find is that 0 is the default. Anything to solve
> this problem, though.
> Thanks


From: Milhouse Van Houten on 10 Jul 2010 02:34
Yes, TSEnabled most definitely should be on 1, and it is the default, which
is not exactly the easiest thing to determine without asking. Wonky things
happen to the UI if either it or the other one is flipped. It's unfortunate
that we inadvertently did just that to one of them. Thanks.

"Al Williams" wrote in message
news:O6#FK$qHLHA.5892(a)TK2MSFTNGP02.phx.gbl...

On our SBS 2003 SP2 TSAppCompat=0 and TSEnabled=1 so I would change
TSEnabled to 1 and reboot.

--
Allan Williams




Milhouse Van Houten wrote:
> Hi Merv,
>
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.server.sbs&tid=18bf4b8f-fcd1-4bc7-a079-26a7444938ae&cat=&lang=&cr=&sloc=&p=1
>
> Do you remember that old thread? I have the same problem as SolveIT,
> and like him, TSAppCompat is already at 0.
>
> However, later on he revealed that TSEnabled=1 solved the problem for
> him, to which you replied "Now if we can just figure out how TSENabled
> got set to 0 in the first place."
>
> Ours is 0 as well -- but isn't that the default? Can you check on
> your SBS2003 system please? I'll change it to 1 if that's correct,
> but the best I can find is that 0 is the default. Anything to solve
> this problem, though.
> Thanks

 | 
Pages: 1
Prev: SBS 2008 - views on virtualization
Next: IE on Server2003 hosed by hotfix