Licence logging problem

[T0GGLe]

Hi,

my company has multiple win2k servers, many of which (over70%) are on
remote sites connected by leased lines.
We have purchased the correct number of licences for these servers and
they have ALL been installed as "per seat".
We are running in mixed mode as a few of our old NT servers have
proved troublesome to upgrade due to the applications they hold/run
and we run active directory.

The problem we are having is multiple entries on the win2k servers in
the event logs attaining to servers having problems contacting licence
logging servers.
Here is a dump:-
***********
vEvent Type: Warning
Event Source: LicenseService
Event Category: None
Event ID: 213
Date: 18/02/2004
Time: 12:37:23
User: N/A
Computer: X
Description:
Replication of license information failed because the License Logging
Service on server XXX could not be contacted.
Data:
0000: 1b 00 02 c0 ...À
***********
Now the server that could not be contacted varies on each server that
has this error so my questions are thus:-

Should the licence logging service only be running on only one
DC/server in the enterprise?
(it is started by default when you upgrade or install win2k from fresh
therefore all our servers have it started)
Where do we you input licence information on win2k/active directory?
Do you need to?

Thanks folks.

 

[Lanwench [MVP - Exchange]]

Stop and disable the license logging service & keep track of your licenses
manually. The service is buggy and isn't mandatory - and apps such as
Outlook have a nasty habit of not releasing licenses.

 

[T0GGLe]

Stop and disable the license logging service & keep track of your licenses
manually. The service is buggy and isn't mandatory - and apps such as
Outlook have a nasty habit of not releasing licenses.

Yep thanks very much you are right - for everyone out there i found an
official document from MS which states almost exactly that.

Here is the link:-

http://support.microsoft.com/default.aspx?scid=kb;en-us;824196

Ho hum 100+ servers to disable the service on....dammit don't they
know their own product when they release it?!?!?!?