EL-Capitan cached

So I've done this recently with Yosemite and it's the same with El Capitan. I have a script that cached the installer and then ran it during off hours (10pm). When it runs it, it really just installs the "OS X Install Data" folder on the root and then blesses it to reboot into it. I noticed that sometimes 90% of the machines just boot back into their normal OS. So make sure you add a restart option in the policy to restart to the "OS X Installer" partition. BUT, since your doing this off hours, have another policy looking for machines with that "OS X Install Data" that are still in your old OS (i.e machines that didn't reboot into installer partition) - and force them to reboot into OS X Installer partition. I find that most machines needed about 2-3 reboots to get into installer partition.

Good luck.

Unfortunately I can't do this off hours, Teachers take laptops home.

What kind of time period do you have to do this? Usually the installer takes about 20-30 minutes depeding on computer type.

Are you going to do it all at once, or stagger it?

Yeah you can make a policy that runs the cached installer at a different trigger event like login, network state change or checkin. Under action for the package, select install cached and make sure under restart options it "restart if a package or update requires it" is selected.

Although this will disrupt any work your faculty are doing and probably won't make them very happy, I've considered just doing the same with our faculty. They refuse to take action and update!

@roiegat

Any Chance you can post the script? Trying to do this myself and am running into issues.

Or if anyone else has a script that works.

Thanks
-W

Here's another method you can look at that may be of value to you:
https://derflounder.wordpress.com/2015/11/23/providing-os-x-upgrades-via-caspers-self-service/