OS Update Policies

We mirrored our Intune rings in Jamf.

Preview = day 0
Pilot = day 7
Production = day 30.

All of these using blueprints to apply.

We’re pretty similar to what ​@Chubs posted. A little faster on the pilot (3 days) and Production (14 days) but our testing is pretty quick/routine. There’s not a lot of gotchas for us as we’re able to keep relatively well ahead on software roadmaps.

With that said, we’re still more likely to find a major issue reading various tech blogs or Jamf Nation!

For major updates (18 => 26) I usually wait for the x.1 release + 1 week.

For minor updates I usually wait for release + 1 week.

This has got us in trouble once but I don’t think it would have been much different even if we had waited 30 days as it was an issue with a specific type of app but wasn’t fixed until the next minor release.

I tried blueprints but had a lot of negative feedback especially for devices that were low on storage so I just push out over the weekend manually.

I sometimes adjust based on holidays or strategize around big projects.

For majors that’s what we do too.  We wait for the enterprise release (X.1) and then a 30 day window...then deploy.

Also Curious if people have multiple blueprints for different “waves”, we are using two, one for testing and one for production.

Can I ask what your validation processes look like?

Also Curious if people have multiple blueprints for different “waves”, we are using two, one for testing and one for production.

 

I’ve moved our mobile devices over to blueprints but haven’t done so with the Macs. My current setup looks something like yours but I have labs and kiosk devices broken into different blueprints. I envy the elegance of yours.