Flushing policies' history client side - how to?

see:

jamf flushPolicyHistory command line binary

As part of imaging, we run a script that flushes the policy history at reboot (so you don't have to manually flush a computer when it's re-imaged). I imagine the same thing would work as a Self Service policy. You just call the jamf binary with:

jamf flushPolicyHistory

I haven't tried it with a Self Service policy, but that should do the trick.

Cheers,
Charlie

-------------------------------------
Charlie Smith
Desktop Engineer
Information Services Department (ISD)
MIT Lincoln Laboratory
244 Wood St. Lexington, MA 02420
Phone: 781.981.0854
E-mail: charlie.smith at ll.mit.edu
-------------------------------------

Many thanks to all.
I have not completed the workflow for imaging yet.
Very handy when a Mac it's re-imaged (even if it has to be done manually here…)
Cheers
Carlo

Da: "Smith, Charles - 1170 - MITLL" <charlie.smith at ll.mit.edu<mailto:charlie.smith at ll.mit.edu>>
Data: Mon, 9 May 2011 13:00:00 -0500
A: Carlo Anselmi <carlo.anselmi at interpublic.com<mailto:carlo.anselmi at interpublic.com>>, "Casper List (casper at list.jamfsoftware.com<mailto:casper at list.jamfsoftware.com>)" <casper at list.jamfsoftware.com<mailto:casper at list.jamfsoftware.com>>
Oggetto: Re: [Casper] Flushing policies' history client side - how to?

As part of imaging, we run a script that flushes the policy history at reboot (so you don't have to manually flush a computer when it's re-imaged). I imagine the same thing would work as a Self Service policy. You just call the jamf binary with:

jamf flushPolicyHistory

I haven't tried it with a Self Service policy, but that should do the trick.

Cheers,
Charlie

-------------------------------------
Charlie Smith
Desktop Engineer
Information Services Department (ISD)
MIT Lincoln Laboratory
244 Wood St. Lexington, MA 02420
Phone: 781.981.0854
E-mail: charlie.smith at ll.mit.edu<mailto:harlie.smith at ll.mit.edu>
-------------------------------------

It seems likely that that command will not completely flush the policy history when run via self service, as it submits its report after the command runs. The entry for the flush itself will remain in the log.

Not that it matters.