Posted on 06-26-2012 12:06 PM
We want to deploy 3 big PKG installers that have to be run in order.
We have 1 policy set up to cache each of the 3 packages. The policy has the [x]Install Cached Packages checked. Does this mean the 3 packages will also run in order?
We originally set up 3 separate policies, to daisy chain them, but for logistical reasons we have to use 1 single policy.
So I wanted to confirm...is JSS intelligent enough to respect the priority set for each PKG when we choose to cache and then install cached PKGs?
Thanks, [color=red]<-- Sorry @meck :)[/color]
Don
Posted on 06-26-2012 12:15 PM
I thought it worked in Alpha-Numeric order.
Could be wrong though.
Posted on 06-26-2012 12:22 PM
@Don, that's a really good question. I'm curious of the answer to this as well. We don't often need to install several cached pkgs in any particular order, but if we ever do, I'd like to know how it handles that.
Posted on 06-26-2012 01:05 PM
Hmmm...has me thinking as well about how [x]Must be installed at boot time works, does it install by priority when cached for install on first reboot at imaging time?
I'll ping our JAMF buddy to see if he has the answer...
Don
Posted on 06-26-2012 03:37 PM
@Don: from what I've seen, checking install at boot time does respect the ordering of 1. priority and then 2. alphabetic
The tricky part, I find, is when you have multiple scripts set to run on reboot (or first, or even last) that must follow a particular order. To this end, I've started prefixing such scripts with 00, 01, 02, etc., to ensure they run in a particular order, since Casper also defaults to alphabetizing scripts with the same "priority."
Posted on 06-27-2012 06:42 AM
+1 to Andrew. Spot on.