So we have the random client which seems to have sent an update report to the server but the server has not changed the status of the client. We don’t know where the problem lies - client, network, server - but what we do know is that the client did indeed take the action and the server is reporting otherwise. This happens at elast once every few actions across random clients.
WARNING - FEATURE REQUEST BELOW (Should I repost in the Feature Request Forum??):
What we need is a way to force a client to resend this information, which by default it will never do. Or we need the client to verify it’s report was recieved on the server and processed successfully. I believe the client does verify it was recieved but the server doesn’t notify the client if the report was not processed successfully. This skews all our data and reports.
Has anyone figured out a way to repost an action report? Or is there another method to “un-skew” the data?
Have you tried sending a “notify client ForceRefresh” action command to clients to see if they update their status? I’ve done this for some action scripts where I want to client to check in before going to the next step. It seems to be effective most of the time…
The agent and the server keeps sequence numbers for reports so that if the server misses a report, it knows how to ask the agent for the missing data (it will send the agent a UDP message to resend the missing info and it also marks the need for the update so that when the agent registers again, it will know to send the missing info). Also, the full-refresh will tell the agent to send up all its data (full-refresh does exactly what you are asking for, which is to force the agent to resend all its data).
I am not clear what is going wrong in your deployment or where the error is occurring, but you might start a support ticket to see if we can isolate the behavior. (You can also clear the console cache as a shot-in-the-dark.)
Ben, we will call support, but I can tell you that even after a full refresh, what the client is showing locally is different than what the server is showing.