Client Runs

As of MunkiReport 5.0, by default a LaunchDaemon gets installed that checks for the existence of a file: /Users/Shared/.com.github.munkireport.run.

If this file exists, the LaunchDaemon will then run /usr/local/munkireport/munkireport-runner which is what the client uses to run the client scripts and send updated information to the server.

By default, this file is created by a Munki postflight script that is installed at /usr/local/munki/postflight to trigger the run. Munki runs happen at a random interval between one and two hours so that a server is not overloaded at any given time.

An admin who wishes more control over when the runner runs will need to either setup their own LaunchDaemon (or other recurring task) that will either touch /Users/Shared/.com.github.munkireport.run or setup a new LaunchDaemon to simply run the runner.

The article Using MunkiReport with Jamf gives an example of how to trigger the run with Jamf Pro. If you'd prefer to build your own LaunchDaemon, please see this GitHub repo.