Windows 2000 Licensing

[Guest Microsoft Newbie]

Hi Guys

 

In the Purchase History tab on my Domain Controller I noticed the following.

 

Product Quantity

MS Exchange 2003 30

 

Yet when I navigate to the Product View Tab I notice the following, with a

warning icon next to each product

 

Product Per Seat Purchased

Per Seat Allocated Per Server Reached

MS Exchange 2003 30

31 -65

MS Windows 2000 Server 0

57 -30

 

How do I rectify these warning issues and allocate the correct numbers for

each product.

 

Also note that the Application log is logging the following error:

 

Event Id: 202

Source: License Server

The product Windows Server is out of licenses. Use Licese Manager from the

Administrative Tools folder for more information on which users are out of

compliance and how many licenses should be purchased.

 

Thanks

[Guest Ryan Hanisco]

RE: Windows 2000 Licensing

 

Hey,

 

In Server 2000, the licensing service is usually more trouble than its

worth. Usually, people will disable the service, but this only works if you

are not running Terminal Services in application mode.

 

You have to have valid licenses and documentation of them all, but running

the service is not a requirement.

--

Ryan Hanisco

MCSE, MCTS: SQL 2005, Project+

http://www.techsterity.com

Chicago, IL

 

Remember: Marking helpful answers helps everyone find the info they need

quickly.

 

 

"Microsoft Newbie" wrote:

> Hi Guys

>

> In the Purchase History tab on my Domain Controller I noticed the following.

>

> Product Quantity

> MS Exchange 2003 30

>

> Yet when I navigate to the Product View Tab I notice the following, with a

> warning icon next to each product

>

> Product Per Seat Purchased

> Per Seat Allocated Per Server Reached

> MS Exchange 2003 30

> 31 -65

> MS Windows 2000 Server 0

> 57 -30

>

> How do I rectify these warning issues and allocate the correct numbers for

> each product.

>

> Also note that the Application log is logging the following error:

>

> Event Id: 202

> Source: License Server

> The product Windows Server is out of licenses. Use Licese Manager from the

> Administrative Tools folder for more information on which users are out of

> compliance and how many licenses should be purchased.

>

> Thanks

>

>

>

[Guest Hank Arnold (MVP)]

Re: Windows 2000 Licensing

 

Ryan Hanisco wrote:

> Hey,

>

> In Server 2000, the licensing service is usually more trouble than its

> worth. Usually, people will disable the service, but this only works if you

> are not running Terminal Services in application mode.

>

> You have to have valid licenses and documentation of them all, but running

> the service is not a requirement.

 

I think you are mixing apples and oranges. On the Windows 2000 server

(TS or not), everyone disables the licensing service. This is *supposed*

to control the licenses to access to the server (non-TS). It doesn't work.

 

With Terminal Services, you need a Terminal Services License Server.

This manages the TSCAL licenses. These are dirreferent that tne CALs

needed to run Server 2000. It is *MANDATORY* if you are running a server

in TS Application Mode.

 

--

 

Regards,

Hank Arnold

Microsoft MVP

Windows Server - Directory Services

[Guest Ryan Hanisco]

Re: Windows 2000 Licensing

 

Hi Hank,

 

You are right that Licensing and TS licensing are not the same thing. I

remember being in a situation where I was getting errors from the TS

Licensing service that were not resolved until it could locate the windows

licensing service on the bax. Maybe this is a red herring, but that made me

think that there might be a dependency there.

 

I will admit that it is possible that this a coincidence as there were a lot

of other things in the mix there too. ADMT consolidation, Citrix, and a DC

replacement.

 

Cheers,

--

Ryan Hanisco

MCSE, MCTS: SQL 2005, Project+

http://www.techsterity.com

Chicago, IL

 

Remember: Marking helpful answers helps everyone find the info they need

quickly.

 

 

"Hank Arnold (MVP)" wrote:

> Ryan Hanisco wrote:

> > Hey,

> >

> > In Server 2000, the licensing service is usually more trouble than its

> > worth. Usually, people will disable the service, but this only works if you

> > are not running Terminal Services in application mode.

> >

> > You have to have valid licenses and documentation of them all, but running

> > the service is not a requirement.

>

> I think you are mixing apples and oranges. On the Windows 2000 server

> (TS or not), everyone disables the licensing service. This is *supposed*

> to control the licenses to access to the server (non-TS). It doesn't work.

>

> With Terminal Services, you need a Terminal Services License Server.

> This manages the TSCAL licenses. These are dirreferent that tne CALs

> needed to run Server 2000. It is *MANDATORY* if you are running a server

> in TS Application Mode.

>

> --

>

> Regards,

> Hank Arnold

> Microsoft MVP

> Windows Server - Directory Services

>

[Guest Ryan Hanisco]

Re: Windows 2000 Licensing

 

As a follow up.... since I couldn't find these earlier. So looks like no

dependency is really there, though it does explain why I was seeing messages

in the log. Thanks! I love learning.

 

From the services guide:

 

License Logging Service - tracks Client Access License usage for server

products, such as IIS, Terminal Services, and File and Print services, as

well as other products such as SQL Server and Microsoft Exchange Server. If

disabled, licensing for these programs will work properly, but usage will no

longer be tracked.

 

Terminal Services Licensing - installs a license server and provides

registered client licenses when connecting to a Terminal Server. The Terminal

Services License Service is a low-impact service that stores the client

licenses that have been issued for a Terminal server and tracks the licenses

that have been issued to client computers or terminals. If this service is

turned off, the server will be unavailable to issue Terminal Server licenses

to clients when they are requested. If another License Server is discoverable

on a DC in the forest, the requesting Terminal Server will attempt to use it.

See also Terminal Services.

--

Ryan Hanisco

MCSE, MCTS: SQL 2005, Project+

http://www.techsterity.com

Chicago, IL

 

Remember: Marking helpful answers helps everyone find the info they need

quickly.

 

 

"Hank Arnold (MVP)" wrote:

> Ryan Hanisco wrote:

> > Hey,

> >

> > In Server 2000, the licensing service is usually more trouble than its

> > worth. Usually, people will disable the service, but this only works if you

> > are not running Terminal Services in application mode.

> >

> > You have to have valid licenses and documentation of them all, but running

> > the service is not a requirement.

>

> I think you are mixing apples and oranges. On the Windows 2000 server

> (TS or not), everyone disables the licensing service. This is *supposed*

> to control the licenses to access to the server (non-TS). It doesn't work.

>

> With Terminal Services, you need a Terminal Services License Server.

> This manages the TSCAL licenses. These are dirreferent that tne CALs

> needed to run Server 2000. It is *MANDATORY* if you are running a server

> in TS Application Mode.

>

> --

>

> Regards,

> Hank Arnold

> Microsoft MVP

> Windows Server - Directory Services

>