How are you macOS managing updates?

Best thing to do if you really want to control what updates go out and also have branches for updates (i.e. group A gets high sierra update, group B does not) is to use reposado. There's lots of guides out there, but this is probably one of the better ones even if it's a few years old: https://clburlison.com/reposado-guide/ Here's the github: https://github.com/wdas/reposado

If you'd like to stick with Apple only, the best you can do now is have a config profile that delays updates for up to 90 days. That gives you a little bit of time to test updates.

I would recommend looking at Reposado as well. I kind of went through what you're looking at now a few months back and decided to spin up Reposado on all our old Mac servers that had been running OS X Server. It takes a little work to get it all set up and humming, but once you do, it works well.

Any issues with older hardware running Reposado? It'd be great to not spend $15k to spin up a RHEL VM and storage. I've got my current ASUS running through an old Mac mini with a 1tb SSD.

Mine are mostly running on 2010 Mac Pros. But I don't see a reason you can't use it on a Mac mini like the one you have. it should run fine on that.

I am on the fence as well, but due to wanting to completely control updates and also keep traffic out to the internet to a minimum, I'm thinking reposado + margarita is my best bet.

My only issue is that we're a multi-site organization, and I'm not sure how to best handle managing updates for each site without having updates pull from across the WAN (network team might kill me).

Anyone who has set up reposado in a multi-site organization have any ideas?

We are a multi-site organisation and use NetSUS in each office. This was a must as originally the Macs in the office this were overloading the network with apple updates especially in offices with little bandwidth. Having it in each office is not ideal as when I need to make available certain updates this has to be changed per NetSUS server however seems to work well. At least when Apple make available new updates this allows us time to test it out before disaster happens :).

Just started running the JAMF/NetSUS and so far it seems to work well.

I have been using a NetSUS appliance on RedHat as well as on ubantu box and it is working like a charm, give a flexibility to chose what to install and what not to.
It also gives you an option whether Mac should download the update from NetSUS or directly from Apple SWU.

Just looking into everyone's suggestions (THANKS ALL!) and something jumped out at me. From the JAMF NetSUS getting_started doc it says

The Software Update Server uses Reposado to sync content from Apple

So is there an advantage to using NetSUS over Reposado that I'm not seeing if all I need is SUS? I wouldn't need a GUI, but I don't think either have one anyway. We don't use Netboot and don't need it as an LDAP proxy.

And I just realized...

How are you macOS managing updates?

I guess that degree from The Derek Zoolander School For Kids That Can't Read Good And Want To Do Other Things Good Too...

@easyedc got to love someone that can laugh at themselves, we knew what you meant. @mm2270 take a look at repotoddy to automate your software roll outs. Did you ever get that error 1100 fixed?

Update - I got Reposado working in test and so far so good. I do have one concern that is coming out of all this SUS Testing. Reposado leverages the catalogs that Apple currently publishes, but there's a functional SUS feature available in the server.app still today. Is there honest expectation that Apple's not going to yank out and Reposado breaks under macOS Mojave future OS's?