(imported topic written by bchae91)
We currently have a seat license for 10500. We have 10,000 clients checking in. The problem is that the BES Client Restricted by Seat Count fixlet is saying that we have 1700 clients that are not licensed. What could cause this and how could resolve this issue?
(imported comment written by BenKus)
Hi bchae,
Try adding the property “BES Client License State” from http://support.bigfix.com/bes/misc/retrievedproperties.html#Misc
See if you can find any patterns in the computers that are restricted that might shed some light on this issue… You also might want to contact support to look at this.
Ben
(imported comment written by rclarke)
Hi Ben,
We have exactly the same issue as bchae. Our BigFix server in AsiaPac is licensed for 1800 seats and we have 1703 assets actually registered and reporting. However, 867 BES Clients are restricted by seat count. The “seat of client license as string” relevance returns numbers well in excess of 1800, in actual fact the highest so far is 9866! Any ideas would be much appreciated.
Thanks,
Rod.
(imported comment written by BenKus)
Hey Rod,
It is possible that there might be one or more agent that are sucking up multiple licenses due to some sort of corruption on the agent end… If you looked at the agent log, you would probably see an agent registering over and over… On the BigFix server side, you can look at the registrationlist.txt (in the “ClientRegisterData” subfolder of the BES Server) and you should see roughly as many lines in this file as there are BigFix Agents that have ever been in your deployment (so if you see more than 2x-3x lines than agents, you probably have an issue). You can see if there is one IP address that is on many lines of this file and that might be the agent(s) who are causing the problem.
Ben
(imported comment written by rclarke)
Hi Ben,
A quick check of the “registrationlist.txt” reveals 37,438 rows :o with one IP listed 22,624 times and another listed 9,790 times. So the question now is how do I fix it 
Many thanks,
Rod.
(imported comment written by SystemAdmin)
Hey Rodney,
You’ll probably need to track down the BES Clients which are causing the registration entries, probably one or two clients are continuing to register over and over again, you can see them doing it in the log file if you can find the computers.
Try tracing the IP Addresses in the registration list. If the computer is a BES Relay, repeat the process of scanning the registration list and continue downstream.
Let us know what you find, sorry for the error.
Tyler
(imported comment written by BenKus)
After you find the agent, please run the BES Client Diagnostics and send us the results… This issue appears to be very rare, but we would like to examine it and see if we can fix it for the future.
After that, you can BES Remove and reinstall it… then check the agent logs to make sure it is fixed… Then you will probably want to clear your registrationlist.txt by doing the following:
After you do this, the server won’t know the IP addresses of the BigFix Agents to notify them of new actions until they register again (which occurs every 6 hours by default).
Ben
(imported comment written by rclarke)
Many thanks Ben and Tyler … our man in China (that is where we have traced the machines to) is hunting down the “rogue agents” as I type. We will keep you informed
Rod.
(imported comment written by Macideus91)
I have 1000 license and am getting same problem. Worked with Weylan yesterday but issue still not resolved. Any insight on this would be great. I should have 150-170 licenses free at this time. I am still new to this so go easy on me guys. Thanks
-Mike
PS not sure how you went about finding the one problem child’s IP…
(imported comment written by arpotu91)
All, I know this is an old thread, but I’m experiencing the same problem. I’ve started going through and mopping up, but do we yet know why this happens?
Arpotu.
(imported comment written by BenKus)
Hi arpotu,
It is something we had seen just a few times and it appeared to be related to very bizarre networking conditions, networking drivers, OR some sort of confused agent that fixed when we wiped the agent and re-installed.
It is something that is expected to be very rare.
What version of the agent are you running?
Ben
(imported comment written by SystemAdmin)
I think I am running into this issue. We have version 8.1 installed with 22000 licenses. Our licensing currently has about 1000 open seats but we have ~1000 machines that are Seat Count Grace Mode.
I took a look at that registrationlist.txt file from the server and it is 605968 rows. 352767 of those rows start with Relay:IP but they all appear to be different relays. From the looks of the remaining machines it looks like they could be machines that may have Deep Freeze installed but not configured properly. We currently address this issue but running the BESComputerRemover.exe but it appears this may be causing the licensing issue.
Is the resolution to this problem just stopping the BESRootServer service and then renaming/deleting this file from the Bes Server\ClientRegisterData folder and starting the BESRootServer again? I can try that after hours if that is all that is needed.
Ben Kus, Do you want any additional information to research this issue further?
(imported comment written by BenKus)
Hi tsikma,
That is a big registration list… Contact support and I think they have a tool that will safely clean up the file…
Ben