I have one specific Mac in our organisation that returns “Not running” when you run BESAgentControlPanel.sh -status
and if you try to running BESAgentControlPanel.sh -start if returns “BES Service Disabled”.
I have attempted to uninstall using BESAgentUninstaller.sh, rebooted then reinstalled, but still no change.
We are using a corporate installation package which does not cause the same issue on all of our other Macs,
any ideas what could be causing the BES Service to behave like this and how to fix it?
I’ve asked the user to confirm that /Library/LaunchDaemons/BESAgentDaemon.plist exists
if it does, run:
Sudo /bin/launchctl load /Library/LaunchDaemons/BESAgentDaemon.plist
It looks like someone has unloaded the launchdaemon with the -w switch which permanently disables it.
this setting can persist even when reinstalling the application. I’ve asked the user to run:
Sudo /bin/launchctl load -w /Library/LaunchDaemons/BESAgentDaemon.plist
which should re-enable the launchdaemon and get the bigfix client back up and running as it should.