BF client service shuts down for no obvious reason

(imported topic written by DocFly91)

BigFix inexplicably shuts down every day on about 100 of our machines. We have several thousand machines in our environment so the problematic PC’s are just a small fraction of the total with BF installed. We are running version 7.2.5.22 on WinXP SP3. The service starts up manually with no problem and log entries from there look good. However within 24 hrs it will shut down again with the last BF log entry being “Client shutdown (Service manager stop request)" There is no indication in previous log entries or in event viewer as to who/what shut the BF service down. We have thoroughly removed and reinstalled the BF client to no avail. Please advise

Thanks

Eric Myers

(imported comment written by JackCoates91)

Service Manager Stop Request means just that… some one or something used ‘net stop besclient’ or services.msc to do it. Could there be a policy or scheduled task (maybe windows) in place to do this? Maybe a GPO intended to install the agent that’s gone awry?

To solve the problem without hunting that down, you might try BES Client Helper.

(imported comment written by DocFly91)

Thanks for your quick reply sir. Actually I have a correction. The event viewer logs do show that the BES service was sent a stop control user the end-user’s account. Anyway I understand your point. Was just hoping that you knew of a possible conflict with another app/service that could close the BF service. I guess I have to look into the fact that I have a few dozen end-users taking it upon themselves to stop the service probably due to perceived performance issues. Now it’s political and not a technical issue. Again Thanks for your help.

Eric