W2k TS in a Windows 2003 domain

Hi,

I am in the process of migrating our Windows NT 4.0 domain
to Windows 2003. In my NT 4.0 domain we have a Windows
2000 member server acting as a Terminal Server in
application mode containing also the licensing server
service. The server won't be upgraded to Windows 2003.

So my question is the following;

Will I encounter any problems with the terminal services
server while upgrading the domain to Windows 2003? Do I
need a Windows 2003 licensing server in a Windows 2003
domain?

Thank you

Yes. As soon as the W2K TS is made a member of the 2003 domain
(with AD), it will refuse to run the TS Licensing Server Service,
since that service only runs on domain controllers (exception:
when the W2K TS is a member of a workgroup or an NT 4.0 domain).

I would install a TS LS on a 2003 DC and install you licenses
there. 2003 LS can handle both 2003 and W2K TS CALs.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"Jacques" <anonymous@discussions.microsoft.com> wrote in
news:105c401c43f61$ee75c650$a101280a@phx.gbl:

> Hi,
>
> I am in the process of migrating our Windows NT 4.0 domain
> to Windows 2003. In my NT 4.0 domain we have a Windows
> 2000 member server acting as a Terminal Server in
> application mode containing also the licensing server
> service. The server won't be upgraded to Windows 2003.
>
> So my question is the following;
>
> Will I encounter any problems with the terminal services
> server while upgrading the domain to Windows 2003? Do I
> need a Windows 2003 licensing server in a Windows 2003
> domain?
>
> Thank you

Thank you for the answer. What about licensing? Do I have
to buy new TS licences?


>-----Original Message-----
>Yes. As soon as the W2K TS is made a member of the 2003
domain
>(with AD), it will refuse to run the TS Licensing Server
Service,
>since that service only runs on domain controllers
(exception:
>when the W2K TS is a member of a workgroup or an NT 4.0
domain).
>
>I would install a TS LS on a 2003 DC and install you
licenses
>there. 2003 LS can handle both 2003 and W2K TS CALs.
>
> --
>Vera Noest
>MCSE, CCEA, Microsoft MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
>"Jacques" <anonymous@discussions.microsoft.com> wrote in
>news:105c401c43f61$ee75c650$a101280a@phx.gbl:
>
>> Hi,
>>
>> I am in the process of migrating our Windows NT 4.0
domain
>> to Windows 2003. In my NT 4.0 domain we have a Windows
>> 2000 member server acting as a Terminal Server in
>> application mode containing also the licensing server
>> service. The server won't be upgraded to Windows 2003.
>>
>> So my question is the following;
>>
>> Will I encounter any problems with the terminal
services
>> server while upgrading the domain to Windows 2003? Do I
>> need a Windows 2003 licensing server in a Windows 2003
>> domain?
>>
>> Thank you
>.
>

No, as long as you don't upgrade the TS to 2003, you don't need
new TS CALs. You will have to call the Clearinghouse, though,
because you need their help in re-installing your existing W2K TS
CALs on your 2003 LS.

And you will of course need normal 2003 server CALs.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

<anonymous@discussions.microsoft.com> wrote in news:1062901c43f69
$fb2b2040$a101280a@phx.gbl:

> Thank you for the answer. What about licensing? Do I have
> to buy new TS licences?
>
>
>>-----Original Message-----
>>Yes. As soon as the W2K TS is made a member of the 2003
> domain
>>(with AD), it will refuse to run the TS Licensing Server
> Service,
>>since that service only runs on domain controllers
> (exception:
>>when the W2K TS is a member of a workgroup or an NT 4.0
> domain).
>>
>>I would install a TS LS on a 2003 DC and install you
> licenses
>>there. 2003 LS can handle both 2003 and W2K TS CALs.
>>
>> --
>>Vera Noest
>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>>"Jacques" <anonymous@discussions.microsoft.com> wrote in
>>news:105c401c43f61$ee75c650$a101280a@phx.gbl:
>>
>>> Hi,
>>>
>>> I am in the process of migrating our Windows NT 4.0
> domain
>>> to Windows 2003. In my NT 4.0 domain we have a Windows
>>> 2000 member server acting as a Terminal Server in
>>> application mode containing also the licensing server
>>> service. The server won't be upgraded to Windows 2003.
>>>
>>> So my question is the following;
>>>
>>> Will I encounter any problems with the terminal
> services
>>> server while upgrading the domain to Windows 2003? Do I
>>> need a Windows 2003 licensing server in a Windows 2003
>>> domain?
>>>
>>> Thank you

There are also two regedits that can be done to avoin installing a W2K3
license service. The regedits turn of the license service discovery process
and specify the default license server.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing
Modify the ImagePath value to "%SystemRoot%\System32\lserver.exe -nodc"
(without the quotation marks.

You will also need to add the following key to the Terminal Server (which is
the same box):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters

Add the following value:
"Name": "DefaultLicenseServer" (without the quotation marks)
"Data type": REG_SZ
"Data value": "ServerName" (without the quotation marks)
Substitute the NetBIOS name of the appropriate license server for
<ServerName>. If the license server is located on a remote subnet, make sure
the Terminal Services-based computer can resolve the NetBIOS name."

In this setup, the Terminal Server and the Terminal Services Licensing are
on the same W2K server.


Note: I have a 50% success with this. One forest, this works, the other
generates some errors on the TS server, but my users are not complaining so
I think the errors may be false.

adam

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns94F0E24BF9F4Fveranoesthemutforsse@207.46.248.16...
> No, as long as you don't upgrade the TS to 2003, you don't need
> new TS CALs. You will have to call the Clearinghouse, though,
> because you need their help in re-installing your existing W2K TS
> CALs on your 2003 LS.
>
> And you will of course need normal 2003 server CALs.
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> <anonymous@discussions.microsoft.com> wrote in news:1062901c43f69
> $fb2b2040$a101280a@phx.gbl:
>
> > Thank you for the answer. What about licensing? Do I have
> > to buy new TS licences?
> >
> >
> >>-----Original Message-----
> >>Yes. As soon as the W2K TS is made a member of the 2003
> > domain
> >>(with AD), it will refuse to run the TS Licensing Server
> > Service,
> >>since that service only runs on domain controllers
> > (exception:
> >>when the W2K TS is a member of a workgroup or an NT 4.0
> > domain).
> >>
> >>I would install a TS LS on a 2003 DC and install you
> > licenses
> >>there. 2003 LS can handle both 2003 and W2K TS CALs.
> >>
> >> --
> >>Vera Noest
> >>MCSE, CCEA, Microsoft MVP - Terminal Server
> >>http://hem.fyristorg.com/vera/IT
> >> --- please respond in newsgroup, NOT by private email ---
> >>
> >>"Jacques" <anonymous@discussions.microsoft.com> wrote in
> >>news:105c401c43f61$ee75c650$a101280a@phx.gbl:
> >>
> >>> Hi,
> >>>
> >>> I am in the process of migrating our Windows NT 4.0
> > domain
> >>> to Windows 2003. In my NT 4.0 domain we have a Windows
> >>> 2000 member server acting as a Terminal Server in
> >>> application mode containing also the licensing server
> >>> service. The server won't be upgraded to Windows 2003.
> >>>
> >>> So my question is the following;
> >>>
> >>> Will I encounter any problems with the terminal
> > services
> >>> server while upgrading the domain to Windows 2003? Do I
> >>> need a Windows 2003 licensing server in a Windows 2003
> >>> domain?
> >>>
> >>> Thank you

Since you don't quote the message you reply to, it's difficult to
know what you disagree with. Presumably it was my statement:

"Yes. As soon as the W2K TS is made a member of the 2003 domain
(with AD), it will refuse to run the TS Licensing Server Service,
since that service only runs on domain controllers (exception:
when the W2K TS is a member of a workgroup or an NT 4.0 domain)."

Since the whole previous content is about a W2K TS in a 2003 domain
(see the subject line), it doesn't apply to your situation, which is
the reverse.

--
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?RXVnZW5l?= <anonymous@discussions.microsoft.com> wrote
in news:47138BD1-3A33-4463-92E9-436D5D4633FC@microsoft.com:

> I disagree with that.
> We have W2000 domain and TS on W2003. I followeed the same paper
> and installed TS lisensing on 2000 domain and it worked for 120
> days (evaluation period). After call to PSS they told me to
> reinstall it on TS (WIN2003 Member in WIN2000 domain) and it
> works no problem. It is not nessesary to install TS Licensing
> Server on Domain Controller.