On Feb 4, 2014, at 7:26 PM, Erik <
eriknico...@gmail.com> wrote:
> I was one of the people that replied over there. I still don't see the benefit of using this package for machines with erased volumes. AutoDMG is going to make an ASR dmg for you that will be much faster, deployment wise.
>
> Greg, am I wrong in my understanding?
>
You are not wrong in saying that restoring an image takes less time than running Apple's installer.
I've currently chosen to deploy using Apple's installer. There are several reasons:
1) I have to build an installer package for upgrades of existing machines via Munki; it makes some sense to not duplicate effort and to be able to use that exact same thing to do new installs as well.
2) I can have a deployable package within minutes using any available machine. This is very useful during the developer preview stage.
3) Most new machines here are not "imaged" at all, since the arrive with a perfectly good OS on them already. Instead, we just install a few packages and let Munki configure them.
4) InstaDMG has been a mess for a while and SIU was finicky. Both require building on the same major OS release as the image you want to build. Now that AutoDMG is available, it's possible I might revisit things, but not necessarily. Unlike an EDU organization, I don't have narrow windows in which I need to image or reimage a large number of machines. Instead, deployment and reimaging is continuous throughout the year, and never a huge number of machines at a time. If I had to quickly reimage hundreds of machines over summer or winter break, I would want the process to be as fast as possible, and would definitely use an imaging approach.
Know the tools and approaches that are available and make whatever choice is best for you and your environment.
-Greg