This happens when computer property data is removed from the database and is now missing for computers which are still active in the deployment. This property data might have been removed during a cleanup operation (such as running the Computer Remover tool too aggressively on computers which may have only been recently expired). Having a deployment where client endpoints only report in once every few months can contribute to this problem. Another scenario might be if the database is rolled back to a point in time where property data for certain endpoints did not exist.

To resolve this problem follow these instructions:

1. If you are running the Computer Remover tool on a frequent basis, check to see if you are consistently running it with options that are too aggressive for your deployment. For instance, if you are using the -t option (default 30 days) but a good number of computers in your deployment would not be considered expired unless the don't register/report for at least 90 days, then update the -t option value to be 90 instead of 30. Check the other options you are using and decide if they might be considered too aggressive for your deployment as well.

2. Login to the console as master console operator

3. Select the problematic computers (the one's missing all properties) and right click and delete them.

4. Immediately after deleting them, run the BESClient Refresher tool on the server using the -M option.

5. Repeat steps 1-3 once a day until no more computers are appearing in the console with "not reported" for all their properties.

Doing this flags all the recently deleted computers as needing to be refreshed. The next time the client endpoints register with the deployment, they will be instructed to send up a full report of all of their property data.

Note: Here is a related article for general troubleshooting for computers with properties that are displaying as not reported http://www-01.ibm.com/support/docview.wss?uid=swg21505948