I have been seeing this more offend and the fix is time consuming. I see a device that wont take any action it just sits there. I then look into it’s actionsite folder and see that the actions are way out of sync like several months. I then check out it’s relay that it reports too and same thing way out of sync with Top or main BES server. I need to understand why this is happening since I only know about it after troubleshooting a failed device that response to ping and refresh but won’t accept and action. The fix so far as been to remove BES client, remove Relay then hack registry key to make it think it’s a new install. I then use deployment tool to push agent to device. I wait for all fixlets and relay to reload then check to see it the actionsite is now sync with parent which it is.
I am not sure the details and if there is a known way to avoid/fix it in all cases, but I think they will be able to diagnose and manually repair… but I will ask them to add the KB article if they have useful info to offer…