Windows NT Windows Server 2008 Terminal Services in W2K AD Domain?

  • Thread starter Thread starter LVAdmin
  • Start date Start date
L

LVAdmin

Greetings,
I have a Win2K SMall Business Server-based domain, and have recently added a
2008 member server that is intended to be a Terminal Server. I have
purchased 5 User Cals to start, and managed to install and activate them, but
I seem to have a problem with getting them issued to incoming users.

When I go into TS Licensing Manager, and choose Review Configuration, I see
a yellow exclamation point indicating the following:

"This license server is not a member of the Terminal Server License Servers
group in Active Directory Domain Services. This license server will not be
able to issue TS Per User CALSs to users int eh domain, and you will not be
able to track or report the usage of TS Per User CALs on this license server."

There is an "Add to group" button, but when I click that, I get:

"The computer account for license server <servername> cannot be added to the
Terminal Server License Servers group in the Active Directory DOmain Services
(AD DS) because the license server is unable to contact AD DS."

I click close, then OK, and I get:

The following error occured on the license server: 0x534, No mapping between
account names and security IDs was done."

I have looked to see, but there is no "Terminal Server License Servers"
group anywhere in my AD. I tried creating it (and manually adding the
license server as a member), but that didn't seem to help (I didn't really
expect it to).

I have a sneaking suspicion that this is a problem with my DC being
W2K-based, but I haven't seen anything specifically stating that 2008
Terminal Services required >W2K AD. I have seen documents explaining how to
get it working with W2K3 AD, but nothing about W2K. Am I missing something
here?

I have a feeling I know the answer, that W2K AD is not supported for W2K8
Terminal Services to be able to track User CALs. I am not adverse to
upgrading the whole domain to 2008, but I was waiting for the new release of
Small Business Server to do it, so we can get Exchange 2007 in the process.
As I understand it, that is still a few months out, at least, and I need a
solution. Any suggestions?

I only need it for a few users right now, so one solution I had considered
was purchasing a few Device CALs. If I understand the problem correctly,
Device CALs would work with my W2K domain, right? I hate to waste the money,
as User CALs are more suited to my application, but this would buy me the
time I need until SBS is released, right? Anyone got a solution that DOESN'T
require laying out wasted money?
 
have you thought about downgrading to Win2k3 until you can upgrade
completely to Win2k8?

Jeff Pitsch
Microsoft MVP - Terminal Services

"LVAdmin" <LVAdmin@discussions.microsoft.com> wrote in message
news:B194098E-8F00-4F6E-B16F-395823968648@microsoft.com...
> Greetings,
> I have a Win2K SMall Business Server-based domain, and have recently added
> a
> 2008 member server that is intended to be a Terminal Server. I have
> purchased 5 User Cals to start, and managed to install and activate them,
> but
> I seem to have a problem with getting them issued to incoming users.
>
> When I go into TS Licensing Manager, and choose Review Configuration, I
> see
> a yellow exclamation point indicating the following:
>
> "This license server is not a member of the Terminal Server License
> Servers
> group in Active Directory Domain Services. This license server will not
> be
> able to issue TS Per User CALSs to users int eh domain, and you will not
> be
> able to track or report the usage of TS Per User CALs on this license
> server."
>
> There is an "Add to group" button, but when I click that, I get:
>
> "The computer account for license server <servername> cannot be added to
> the
> Terminal Server License Servers group in the Active Directory DOmain
> Services
> (AD DS) because the license server is unable to contact AD DS."
>
> I click close, then OK, and I get:
>
> The following error occured on the license server: 0x534, No mapping
> between
> account names and security IDs was done."
>
> I have looked to see, but there is no "Terminal Server License Servers"
> group anywhere in my AD. I tried creating it (and manually adding the
> license server as a member), but that didn't seem to help (I didn't really
> expect it to).
>
> I have a sneaking suspicion that this is a problem with my DC being
> W2K-based, but I haven't seen anything specifically stating that 2008
> Terminal Services required >W2K AD. I have seen documents explaining how
> to
> get it working with W2K3 AD, but nothing about W2K. Am I missing
> something
> here?
>
> I have a feeling I know the answer, that W2K AD is not supported for W2K8
> Terminal Services to be able to track User CALs. I am not adverse to
> upgrading the whole domain to 2008, but I was waiting for the new release
> of
> Small Business Server to do it, so we can get Exchange 2007 in the
> process.
> As I understand it, that is still a few months out, at least, and I need a
> solution. Any suggestions?
>
> I only need it for a few users right now, so one solution I had considered
> was purchasing a few Device CALs. If I understand the problem correctly,
> Device CALs would work with my W2K domain, right? I hate to waste the
> money,
> as User CALs are more suited to my application, but this would buy me the
> time I need until SBS is released, right? Anyone got a solution that
> DOESN'T
> require laying out wasted money?
>
>
 
AFAIK, Per User licenses are not enforced in 2008 TS. So you can
just keep track of the number of connecting users by hand, until
you have upgraded your domain.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote on 14 jul 2008
in microsoft.public.windows.terminal_services:

> have you thought about downgrading to Win2k3 until you can
> upgrade completely to Win2k8?
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "LVAdmin" <LVAdmin@discussions.microsoft.com> wrote in message
> news:B194098E-8F00-4F6E-B16F-395823968648@microsoft.com...
>> Greetings,
>> I have a Win2K SMall Business Server-based domain, and have
>> recently added a
>> 2008 member server that is intended to be a Terminal Server. I
>> have purchased 5 User Cals to start, and managed to install and
>> activate them, but
>> I seem to have a problem with getting them issued to incoming
>> users.
>>
>> When I go into TS Licensing Manager, and choose Review
>> Configuration, I see
>> a yellow exclamation point indicating the following:
>>
>> "This license server is not a member of the Terminal Server
>> License Servers
>> group in Active Directory Domain Services. This license server
>> will not be
>> able to issue TS Per User CALSs to users int eh domain, and you
>> will not be
>> able to track or report the usage of TS Per User CALs on this
>> license server."
>>
>> There is an "Add to group" button, but when I click that, I
>> get:
>>
>> "The computer account for license server <servername> cannot be
>> added to the
>> Terminal Server License Servers group in the Active Directory
>> DOmain Services
>> (AD DS) because the license server is unable to contact AD DS."
>>
>> I click close, then OK, and I get:
>>
>> The following error occured on the license server: 0x534, No
>> mapping between
>> account names and security IDs was done."
>>
>> I have looked to see, but there is no "Terminal Server License
>> Servers" group anywhere in my AD. I tried creating it (and
>> manually adding the license server as a member), but that
>> didn't seem to help (I didn't really expect it to).
>>
>> I have a sneaking suspicion that this is a problem with my DC
>> being W2K-based, but I haven't seen anything specifically
>> stating that 2008 Terminal Services required >W2K AD. I have
>> seen documents explaining how to
>> get it working with W2K3 AD, but nothing about W2K. Am I
>> missing something
>> here?
>>
>> I have a feeling I know the answer, that W2K AD is not
>> supported for W2K8 Terminal Services to be able to track User
>> CALs. I am not adverse to upgrading the whole domain to 2008,
>> but I was waiting for the new release of
>> Small Business Server to do it, so we can get Exchange 2007 in
>> the process.
>> As I understand it, that is still a few months out, at least,
>> and I need a solution. Any suggestions?
>>
>> I only need it for a few users right now, so one solution I had
>> considered was purchasing a few Device CALs. If I understand
>> the problem correctly, Device CALs would work with my W2K
>> domain, right? I hate to waste the money,
>> as User CALs are more suited to my application, but this would
>> buy me the time I need until SBS is released, right? Anyone
>> got a solution that DOESN'T
>> require laying out wasted money?
 
You can upgrade the AD Schema on Win2k DC box to Win2K3 Schema.

Please check the following link for doing so,
http://technet2.microsoft.com/windo...a8d7-4761-b38a-e207baa734191033.mspx?mfr=true

Ratnesh


"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9ADBD611BAECBveranoesthemutforsse@207.46.248.16...
> AFAIK, Per User licenses are not enforced in 2008 TS. So you can
> just keep track of the number of connecting users by hand, until
> you have upgraded your domain.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote on 14 jul 2008
> in microsoft.public.windows.terminal_services:
>
>> have you thought about downgrading to Win2k3 until you can
>> upgrade completely to Win2k8?
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>> "LVAdmin" <LVAdmin@discussions.microsoft.com> wrote in message
>> news:B194098E-8F00-4F6E-B16F-395823968648@microsoft.com...
>>> Greetings,
>>> I have a Win2K SMall Business Server-based domain, and have
>>> recently added a
>>> 2008 member server that is intended to be a Terminal Server. I
>>> have purchased 5 User Cals to start, and managed to install and
>>> activate them, but
>>> I seem to have a problem with getting them issued to incoming
>>> users.
>>>
>>> When I go into TS Licensing Manager, and choose Review
>>> Configuration, I see
>>> a yellow exclamation point indicating the following:
>>>
>>> "This license server is not a member of the Terminal Server
>>> License Servers
>>> group in Active Directory Domain Services. This license server
>>> will not be
>>> able to issue TS Per User CALSs to users int eh domain, and you
>>> will not be
>>> able to track or report the usage of TS Per User CALs on this
>>> license server."
>>>
>>> There is an "Add to group" button, but when I click that, I
>>> get:
>>>
>>> "The computer account for license server <servername> cannot be
>>> added to the
>>> Terminal Server License Servers group in the Active Directory
>>> DOmain Services
>>> (AD DS) because the license server is unable to contact AD DS."
>>>
>>> I click close, then OK, and I get:
>>>
>>> The following error occured on the license server: 0x534, No
>>> mapping between
>>> account names and security IDs was done."
>>>
>>> I have looked to see, but there is no "Terminal Server License
>>> Servers" group anywhere in my AD. I tried creating it (and
>>> manually adding the license server as a member), but that
>>> didn't seem to help (I didn't really expect it to).
>>>
>>> I have a sneaking suspicion that this is a problem with my DC
>>> being W2K-based, but I haven't seen anything specifically
>>> stating that 2008 Terminal Services required >W2K AD. I have
>>> seen documents explaining how to
>>> get it working with W2K3 AD, but nothing about W2K. Am I
>>> missing something
>>> here?
>>>
>>> I have a feeling I know the answer, that W2K AD is not
>>> supported for W2K8 Terminal Services to be able to track User
>>> CALs. I am not adverse to upgrading the whole domain to 2008,
>>> but I was waiting for the new release of
>>> Small Business Server to do it, so we can get Exchange 2007 in
>>> the process.
>>> As I understand it, that is still a few months out, at least,
>>> and I need a solution. Any suggestions?
>>>
>>> I only need it for a few users right now, so one solution I had
>>> considered was purchasing a few Device CALs. If I understand
>>> the problem correctly, Device CALs would work with my W2K
>>> domain, right? I hate to waste the money,
>>> as User CALs are more suited to my application, but this would
>>> buy me the time I need until SBS is released, right? Anyone
>>> got a solution that DOESN'T
>>> require laying out wasted money?
 
"Ratnesh Yadav[MSFT]" wrote:

> You can upgrade the AD Schema on Win2k DC box to Win2K3 Schema.

I haven't been able to test it, but I believe this is going to be the
answer. It led me to the thought that when I go to introduce the new SBS
2008 box to the domain, I will need to do adprep first (for 2000 -> 2008).
After doing some digging, it looks like there is a proper path for that, so
that is the direction I will try. I'll post back here after, to indicate if
it resolved the issue. It will be a few days, as I am remote right now, and
don't dare to make such a change to the customer network unless I can race
over there if it goes south.

And thanks for the fast answers everyone. Glad to see Usenet hasn't become
completely useless just yet. :)
 
Jeff,

No, I am using the Terminal Server for publishing an application via
RemoteApp, so going back to 2003 is not desirable. I suppose if all else
failed, it would at least be an option though.

"Jeff Pitsch" wrote:

> have you thought about downgrading to Win2k3 until you can upgrade
> completely to Win2k8?
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
 
Back
Top