Licensing

[Guest]

We have a problem with our domain in that we have 2 servers and are running in per seat client mode, but licensing reports that we are out of license. As I understand it we need a windows server license for each server then share out enough back office licenses for each machine so users can access network resources. However it reports that we are -238 for windows servers and in the server browser tab it lists all the machines in the domain (all xp) with the role "workstation or server"- Is this normal or have the client machines been misconfigured somehow

Thank

Graeme Davison

 

[Danny Sanders]

You should stop and disable the License logging service. It does not work as
expected. Keep track of your licenses manually as if in per seat mode.


hth
DDS W 2k MVP MCSE

We have a problem with our domain in that we have 2 servers and are

running in per seat client mode, but licensing reports that we are out of
license. As I understand it we need a windows server license for each server
then share out enough back office licenses for each machine so users can
access network resources. However it reports that we are -238 for windows
servers and in the server browser tab it lists all the machines in the
domain (all xp) with the role "workstation or server"- Is this normal or
have the client machines been misconfigured somehow.

 

[Guest]

On the server or workstations - what implications will this have I don't want to stop any important services

 

[Danny Sanders]

The license logging service is running on your servers.
The only implications will be stopping the errors from showing up in the
event viewer. If you are audited and the license logging service is turned
off, you are assumed to be in per seat mode.

The license logging service is not required for anything except logging
connections and tracking licenses. It is a convince for the Admin, but it
doesn't work as expected.

That is one of the first services I disable when setting up servers.

hth
DDS W 2k MVP MCSE

On the server or workstations - what implications will this have I don't

want to stop any important services

 

[Guest]

So basically the service is there to scan your network and report back how many servers you have so you can keep up to date with licenses and having the correct number. But in our case it is misreporting the number because it is including the XP machines as servers as wel

Graeme Davison

 

[Danny Sanders]

It is not scanning servers. You enter your amount of CALs you've bought and
the license logging service tries to keep track of client connections. It
does not count the connections correctly so you get errors.

I don't think it has anything to do with XP being on the domain. The license
logging service had the same flaws in Windows NT 4.0 servers and NT 4.0
clients. It happens on a pure Win 2k domain.

The license logging service just plain and simply does not work. It's not
just in your case. Most people fall into the category of "I can delete and
revoke user's licenses but they continue to reappear months later". The
other category of complaints are "The License logging service is counting my
licenses wrong". I have NEVER seen a fix for either, besides stopping and
disabling the service and manually keeping track of the licenses. There may
be a small percent of people that use the license logging service with no
problems. But I'm not aware of any setup where it works.

hth
DDS W 2k MVP MCSE

So basically the service is there to scan your network and report back how

many servers you have so you can keep up to date with licenses and having
the correct number. But in our case it is misreporting the number because it
is including the XP machines as servers as well