The BES client service stops in the random systems in our network. We face this issue in approximately 30 to 40 systems in our network every month. Then we need to delete the revocations file & then start the BES cleint service as described in KB article- 476. But this would be laborious process as we need to identify those machines manually & delete revocations file then start the service. Also we have observed this happens sometimes when we push fixlets to systems.Would like to know the reason for instablity of the BES service & also the solution for resolving this issue permanently.
We have identified a rare bug in the Microsoft file system where we would write out a file using the Windows file APIs and they would return with “write succesful”, but the file would be corrupted. It only happens very rarely based on some timing events.
Microsoft provided to us some workaround code to avoid the filesystem issue and we also added some more protections into BigFix 7.1 (and more in BigFix 7.2) to address this issue.
Your best bet would be to update to BigFix 7.2. Alternately, you can try using the BigFix Client Helper service, but the 7.2 upgrade should eliminate the issue altogether.
We have upgraded to BF 7 and we are seeing similar issues with the BES client service stopping right after starting. We have uninstalled the clients deleted the BigFix Enterprise directory and even tried to install to a different directory but the service keeps restarting.
7.2 is the version we added extra workarounds for the Microsoft bug… I would try that… alternately you can contact support and see if they can look into your issue and make a specific recommendation…