I would set the packages to ascending priorities, then trigger them all with the same policy.<div><br></div><div>Another way would be to create a smart group with the criteria of having a receipt for the first update. Scope a policy for the second update to this smart group, repeat as necessary until all updates in the chain have been covered.</div>
<div><br></div><div>Before doing any of this, I would verify that update X+1 requires update X, and does not include update X.</div><div><br><br><div class="gmail_quote">2008/11/4 Nichols, Jared <span dir="ltr"><<a href="mailto:jared.nichols@ll.mit.edu">jared.nichols@ll.mit.edu</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Is there any way to chain updates together? For instance, the Office 12.1.4 update just came out which requires the 12.1.3 update. 12.1.4 was released because 12.1.3 was broken. What's the best way to get people up to 12.1.4 while making sure they're not stuck on 12.1.3? Is there a way to slipstream it?<br>
<br>
j<br>
-- <br>
Jared Nichols<br>
ISD Infrastructure and Operations – Desktop Engineering<br>
MIT Lincoln Laboratory<br>
244 Wood St.<br>
Lexington, MA 02420-9108<br>
(781) 981-5500<br>
</span></font>
</div>
<br>_______________________________________________<br>
Casper mailing list<br>
<a href="mailto:Casper@list.jamfsoftware.com">Casper@list.jamfsoftware.com</a><br>
<a href="http://list.jamfsoftware.com/mailman/listinfo/casper" target="_blank">http://list.jamfsoftware.com/mailman/listinfo/casper</a><br>
<br></blockquote></div><br></div>