make sure your policies aren't scoped to once per machine...

Thanks, so what is the recommended frequency? How much of a server performance hit is "ongoing"? Or do we base the frequency on the type of policy based on how important it is to have something installed?

It all depends on how your policies are set up.

here's a good way to do it:

https://github.com/talkingmoose/Jamf-Management-Templates/wiki

Sounds like the it is set up machine based .. all you have do/remember when you wipe a machine you have to delete from the Jamf server...

you can automate that with scripts ...

https://www.jamf.com/blog/reinstall-a-clean-macos-with-one-button/

https://www.jamf.com/jamf-nation/discussions/14330/jss-api-delete-command

C

@mthoma How do you have your "Settings > Global Management > Re-enrollment" settings configured in Jamf Pro? Have you configured that section?

No, we have not yet configured the Re-enrollment settings. Do you have any guidance on what to set? Or is there a document we can follow that gives some more info.

Use the Jamf binary to jamf flushPolicyHistory somewhere early in your build.

That way it’s like a new machine and does not matter on policy frequency as it’s all flushed.

@mthoma At the very least I would check the "Clear policy logs on computers" and "Clear extension attribute values on computers and mobile devices".

However, I have them all checked and also have the bottom dropdown set to "Clear completed, failed, and pending commands".

As @ryan.ball stated, you need to adjust the settings in the Re-enrollment section in your JSS. I have them essentially set the same way as he stated, except for the Extension Attribute item.

This has seemed to work well for me.

Thanks everyone, I'll check off those settings and see how it goes. :)