Help me understanding what's happening with our licensing situatio

G

Guest

I started a new job last week at a small company and they have just one DC on
the AD and we need to promote a member server to a DC but there is a bizarre
licensing issue that needs to be addressed first.

The DC is a 2000 server that was initially configured for 20 'per seat'
licenses and was later upgraded to 40 'per seat' licenses which is plenty
enough for this tiny company. The problem is that for some reason there are
also 10 'per server purchased' listed in the license manager and when the
licensing service is started it quickly fills up and all server services stop!

I don't understand why the 'per server' should even matter if you have
configured the server on a 'per seat' basis. Is that normal?

Regardless I would love to hear any ideas on what's going on and how can I
remedy the situation. I would be happy to provide any more information
necessary.

Thanks in advance.
 
D

Danny Sanders

Stop and disable the license logging service and keep track of your licenses
manually as if in per seat mode.


hth
DDS W 2k MVP MCSE
 
G

Guest

That's what we have been doing. We want to turn it back on but when we do it
kills us although we have plenty of 'per seat purchases'. It's the 10 'per
server purchases' limitation that keeps getting used up thus killing the
services although it's supposed to be configured on a 'per seat purchase'
basis.
 
D

Danny Sanders

The License logging service does not work as expected. It is not needed or
necessary. If you insist on keeping it running it's going to cause the
problems you are seeing. There is/was a KB article that detailed how to
reset the license logging service and start all over. After resetting it,
the *same* thing would start all over again. The fix was to reset the
license logging service, which would act up again, which you fix by
resetting the license logging service. It caused a vicious circle until you
stop and disable the license logging service.


It's the 10 'per
server purchases' limitation that keeps getting used up thus killing the
services although it's supposed to be configured on a 'per seat purchase'


Sounds like another bug to add to the long list of License logging service
bugs.


DDS W 2k MVP MCSE
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top