Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / March 2005

Tip: Looking for answers? Try searching our database.

Terminal Server Licencing problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mac - 29 Mar 2005 20:57 GMT
Hi

I have a Windows 2000 server box which is a member of the domain controller
and I have a Windows 2003 server which is a domain controller. Our windows
2000 server is setup as a terminal server and it was working on our windows
nt 4.0 server (which was as a domain controler).  When we trying to connect
with the terminal server from our 98 and 2000 workstations its not allowing
me to connect. I checked the event ID it generate 29 (TermServLicencing can
not be found).
Can any one help me to configure licences on windows 2000 server, our
licences is valid till 09/2005.

Thanks in advance
Mac
Vera Noest [MVP] - 29 Mar 2005 22:38 GMT
A Windows 2000 TS Licensing Server must be running on a Domain
Controller. The only exception is when the W2K Licensing Server is
part of a workgroup or an NT 4.0 domain.
So that is why the Licensing Server did work in your old setup, but
has stopped functioning now.
If you check the EventLog, you will see:

Event ID 29
Terminal Services Licensing can only be run on Domain Controllers
or Server in a Workgroup.

Event ID 7024
The Terminal Services Licensing service terminated with service-
specific error 29.

The solution is to install the TS Licensing Service on your 2003
Domain Controller. A 2003 LS can handle both W2K and 2003 TS CALs.

--
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?TWFj?= <Mac@discussions.microsoft.com> wrote on 29 mar
2005 in microsoft.public.win2000.termserv.clients:

> Hi
>
[quoted text clipped - 12 lines]
> Thanks in advance
> Mac
Mac - 30 Mar 2005 20:13 GMT
Thanks Veera,
Can you please tell me how I am going to install TS Licensing Service on
your 2003
Domain Controller. Do I need to install  TS on W2K or not? and how I can
configure W2K to access the terminal server licencing from 203 server.
We want every one should connect with the W2K for accessing the data through
terminal server.

Thanks,
Mac

> A Windows 2000 TS Licensing Server must be running on a Domain
> Controller. The only exception is when the W2K Licensing Server is
[quoted text clipped - 39 lines]
> > Thanks in advance
> > Mac
Vera Noest [MVP] - 30 Mar 2005 20:29 GMT
On your 2003 Domain Controller, go to Start - Control Panel -
Add/Remove programs - Add/Remove Windows components - Terminal
Server Licensing.

You do not have to install anything on the W2K Terminal Server. It
will automatically detect the TS Licensing Server running on your
2003 DC.

You will need to install TS CALs on the 2003 TS Licensing Server
for the W98 clients (the W2K Pro and XP Pro clients will get a free
TS CAL from the pool of "Existing Windows 2000 Per Device TS CALs"
on the 2003 licensing server, when they connect to the W2K Terminal
Server).

--
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?TWFj?= <Mac@discussions.microsoft.com> wrote on 30 mar
2005 in microsoft.public.win2000.termserv.clients:

> Thanks Veera,
> Can you please tell me how I am going to install TS Licensing
[quoted text clipped - 52 lines]
>> > Thanks in advance
>> > Mac
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.