What @AgentGuy is saying is that deleting the results file is the same as telling the client to send a full report, so the file isn’t the cause, it is a mismatch between what the client believes it has reported and what the server has. While there may be some unique cases, I would expect most (if not all) of these cases could be resolved using a SendRefresh or (if UDP is not reaching the endpoint) a
notify client forcerefresh action.
There was an issue with the BESComputerRemover that could cause this to occur where fully deleted endpoints were not being marked properly for refresh if they came back online. If you haven’t updated your BESComputerRemover in several months, you might check for our latest version to address this.
My question about the need for automation was really directed at the OP who had an identified cause that was no longer occurring. For other intermittent occurrences, the BESComputerRemover should provide sufficient automation, as it is capable of removing “Not Reported” computers and marking them for full refresh on the next registration.