outset VS erase-install

and Outset

That sounds good! Is this the project?

Some of my machines are shared (like a lab environment) and I use outset to run a script on every login that resets the dock to the expected state. There are conditionals in there that check to see if the app is installed before trying to place the icon on the dock, so you don't end up with the ? icon.

Another option is to have Dockmaster create a package instead of a profile and install it at each user's first login with Outset. This gives the user the flexibility to modify the dock.

If it's templates in a shared folder, just reinstall the whole thing nightly (or after each user) with MDM or use outset to reinstall it locally at login.

Anything that isn't able to be achieved via config profiles, will need to scripted (see Outset https://github.com/chilcote/outset which is super useful for this). Take a look at https://macadmins.software/tools/ 'MailToOutlook 2.0') for your default email item.

Possibly outset can be of service?

There is no equivalent on macos, but you could install your shared files somewhere like /opt/company/shared and use outset to copy them into each users home the next time they log in.

You can see the function being called here (lines 549-562):

- Using the MDM + Erase install (https://github.com/grahampugh/erase-install/), I'd send: curl -s https://raw.githubusercontent.com/grahampugh/erase-install/main/erase-install.sh | sudo bash /dev/stdin --erase -fs --check-power

Off the top of my head - if you are just wiping them you can use https://github.com/grahampugh/erase-install/wiki to do a full erase and re-install of macOS as part of a jamf policy. You could then add in a script as part of that policy that would contact the other system you want the outgoing webhook to point at.

Not with those arguments. You can read about it in their wiki https://github.com/grahampugh/erase-install/wiki

So, depending on the os version you can curl the script or better yet the pkg from this project and then execute the erase and add new container install. This will format the current container and install the os to a mew one and reboot as new. You should be able to suppress the dialogs and maybe even password prompts depending on the os version and model. If the machine is on pre MacOS11 you can use the legacy version.

I'm trying to test a few ways out. I tried eraseinstall (Erase-Install which I quite liked.

An option for automating updates is the erase-install tool and you don't have to erase you can just install.

Best way to jump straight to current would be allowing users to run erase-install (i,e. put it in Self Service if you have Jamf). It's a script on GitHub that has really streamlined the major update process. Just make sure you use the latest v27 (27.3 currently - https://github.com/grahampugh/erase-install/releases/tag/v27.3) as v28 and above don't work on Catalina or lower. It needs ~45GB of free space, so you're in for some real fun if you have a fleet of 128GB's you're trying to get updated. And I can't recall if v27 supports Mojave, may want to look through the documentation. All of your Mojave's and older will be Intel, which gives you more control over pushing updates (can do some command line stuff that doesn't work on M1).