Posted on 09-28-2011 09:19 AM
I was wondering what's the best method to run software update on firstboot after imaging a machine. I don't always get around to updating an image in a timely manner and there will be some software updates that come out during that time. Instead of relying on my techs to actually run softwareupdate (they never do) I want to make sure the systems are up-to-date. I thought about adding /usr/sbin/softwareupdate –ia to my firstboot script, but I was wondering if there is a better approach.
Thanks
Allen
Posted on 09-28-2011 09:39 AM
That's pretty much what I've done for a few years!
(actually have a firstboot policy with' set update server' & 'install all updates' ticked).
Regards,
Ben.
Posted on 09-28-2011 09:48 AM
How is that policy getting applied? By a custom trigger?
Posted on 09-28-2011 10:57 AM
Yep, custom trigger.
I have a base configuration, with smart configurations for each department or location (or both)...
Each of these run a custom trigger, this policy contains NTP settings, custom AD bindings, login window text, wireless ssid's etc... & sus installing updates.
Some of these triggers will be the same across configurations, others unique.. All my scripts have variables within them... So it's easy for me to update.
Regards,
Ben.