I was under the impression that if I put a pkg installer in a config
that it would run at reboot but apparently I'm wrong about that. Does
anyone know of a way to do this. I know I can create a custom trigger
and a policy that will do the install, but that just seams messy. I
would like to just have someone check the installer in Imaging and
have in install at reboot.
The reason I want to do this is because many pkg installers have pre
and postflight scripts that do various things and are based off of the
booted volume. For instance, with ADmit Mac you can create a custom
installation that will join the domain automatically, but this can't
be done unless you are booted into the target disk. Their postflight
script also does a bunch of other things and since their deployment
tool packages this all up as a pkg I would like to keep it that way
since it's cleaner and easier.
Any ideas?
Ryan Harter
UW - Stevens Point
Workstation Developer
715.346.2716
Ryan.Harter at uwsp.edu
