Re: License Server only
From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 11/03/04
- Next message: Vera Noest [MVP]: "Re: Windows 2003 terminal service licensing question"
- Previous message: SC: "Re: License Server only"
- In reply to: SC: "Re: License Server only"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 03 Nov 2004 15:10:24 -0800
I have no real answer, can only tell you that this particular
error message has been reported here a couple of times during the
last week or so.
Always in a setup with an NT4 and a 2003 domain, full trust in
both directions, and often (always?) after applying the October
security fixes on the 2003 servers.
I suspect that there is some sort of security incompatibility
going on, like some of those described here (but I've not been
able to find an exact match of the problem):
Client, service, and program incompatibilities that may occur when
you modify security settings and user rights assignments
http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
Personally, I haven't encountered this particular problem,
although I also have trusted NT4 and 2003 domains. I have been
forced to modify the "Network access: Allow anonymous SID/Name
translation" setting in the 2003 domain (as in point 7 in the KB).
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"=?Utf-8?B?U0M=?=" <SC@discussions.microsoft.com> wrote on 03 nov
2004 in microsoft.public.windows.terminal_services:
> yep, I got the LS installed and activated and I made the correct
> registry changes to the TSs in the NT 4.0 domain but they still
> were unable to connect. In addition when I attempted to add the
> NT 4.0 TSs into the Terminal Server local group on the LS I was
> receiving "Information returned from the object picker for
> object "machine name" was incomplete. The object will not be
> processed"
>
> As a work around I went ahead and created an TSLS inside the NT
> 4.0 domain and now I am able to function but I'd still be
> interested in knowing what might be causing the is error and why
> I'm having the xdomain issue. The both domains should be
> trusted.
>
> Thanks
>
> "Vera Noest [MVP]" wrote:
>
>> So you have managed to activate your Licensing server? Good!
>>
>> Have you made the registry changes on the Terminal Servers in
>> the NT 4.0 domain, as described in the KB article?
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "=?Utf-8?B?U0M=?=" <SC@discussions.microsoft.com> wrote on 02
>> nov 2004 in microsoft.public.windows.terminal_services:
>>
>> > Hi Vera, thanks for the reply. So I've got my License Server
>> > all setup on a 2k3 server inside of a 2k3 AD domain but I am
>> > not able to add machine accounts into the Terminal Servers
>> > Computer list, I keep getting "Information returned from the
>> > object picker for object "machine name" was incomplete. The
>> > object will not be processed"
>> >
>> > I am able to add machines from the AD domain and manually
>> > point them to the licensing server but so far the machines in
>> > the NT 4.0 domain are not able to connect.
>> >
>> > Any ideas? Thanks
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> No, Terminal Services is not required to install and
>> >> activate the TS Licensing Service.
>> >> Could you post the error message that you get when you try
>> >> to activate it and the Events from the EventLog on the
>> >> Server?
>> >>
>> >> Yes, you can point the TS in the NT4 domain to use your
>> >> Licensing Server in the 2003 domain:
>> >>
>> >> 279561 - How to Override the License Server Discovery
>> >> Process in Windows Server 2003 Terminal Services
>> >> http://support.microsoft.com/?kbid=279561
>> >>
>> >> --
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> http://hem.fyristorg.com/vera/IT
>> >> --- please respond in newsgroup, NOT by private email ---
>> >>
>> >> "=?Utf-8?B?U0M=?=" <SC@discussions.microsoft.com> wrote on
>> >> 02 nov 2004 in microsoft.public.windows.terminal_services:
>> >>
>> >> > Scenario
>> >> >
>> >> > Two trusted/trusting domains, Primary domain is 2k3 AD,
>> >> > Secondary domain is NT 4.0. I want to install a license
>> >> > server on a 2k3 server without TS installed in the 2k3
>> >> > domain and physically point my 2k3 TS servers in the NT
>> >> > 4.0 domain to it for licensing.
>> >> >
>> >> > Problem:
>> >> > The license server in the 2k3 domain will not allow me to
>> >> > activate it? Is TS required in order to install/setup TS
>> >> > license server?
>> >> >
>> >> > Question:
>> >> > My 2k3 TS servers in the secondary domain can be manually
>> >> > pointed to the 2k3 license server in the 2k3 domain
>> >> > successfully correct, this should work?
>> >> >
>> >> > Any other issues to be aware of using MSDN subscription to
>> >> > setup License server.
>> >> >
>> >> > Thanks
- Next message: Vera Noest [MVP]: "Re: Windows 2003 terminal service licensing question"
- Previous message: SC: "Re: License Server only"
- In reply to: SC: "Re: License Server only"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
