The registrationlist is used to keep information about computers so it knows where to send UDP messages. This entry is from the BES Agent on the BES Server.
because when running the tool BESClientRefresher.exe ,it needs a computerid ,such as
“BESClientRefresher.exe -c 1183948667” ;
so i need to know when lots of computers report “Not reported”,and the refresh "UDP"cannot send to the clients,maybe i should use BESClientRefresher,but first i shoud know the computerid of such clients, but manually look for the computerid is a hard work when there are thousands of clients.
I am not sure why you are having so many computers… but if you need a quick way to get the computer ID, you can create a property “ComputerID” with the relevance
If I stop running the besclient from the services.msc ,then I log on the console and on the “computer” tab, I choose the computer mentioned above, right click ,“delete” from db and also use the “BESDeletedCompRemover” tool to remove the record of the db .
Then,I start the besclient from the services.msc, but the client shows everything “not reported” ,including the “computer ID” (I wrote a property already ) shows “not reported” . only “Last reported time” shows OK.
If there is a firewall between the client and server ,that is i cannot use right-click and refresh a “UDP” ping .
so the status will last for ever . I think I could use the BESClientRefresher tool.
If I knows the client’s IP address, i can look for the registrationlist.txt to find its computerid. so that is what i want to know, if the client’s IP address “not reported” on the console,how can i get its computerID
I highly recommend that you do NOT run the BESDeletedCompRemover.exe and all these issues will go away. There should be no good reason to run that tool unless you have more than 50,000 BES Agents with a very high turnover… and even then, I would only run it a couple times per year.
If you do not run the BESDeletedCompRemover.exe, the computer’s information will stay in the database and it will not need to be refreshed with the clientrefresher.
The only place to find the computerIDs are in the database or in the registrationlist.txt, but there is not really an easy way to do this.
You might make sure you are using the most recent version of the BESDeletedCompRemover.exe, there have been updates to help prevent the behavior (v. 2.2.8.23).
Be sure to use the -r switch when you run it, this will mark computers as needing a refresh at the time they are deleted and help prevent them from coming back with values.