<br><font size=2 face="sans-serif">The way I've managed this is by chaining
policies based on smart-groups tagge to Application version.</font>
<br>
<br><font size=2 face="sans-serif">In your case for instance, I have a
smart-group whose members consist of computers running 12.1.1, and 12.1.2
(Our Office 2008 package is 12.1.1). A policy is in place to deploy 12.1.3
to that members of that smart group (make sure to remember to add "Update
Inventory" to the advanced tab in the polciy.</font>
<br>
<br><font size=2 face="sans-serif">Then you can create a simliar smart
group of users that have 12.1.3, and create a policy to deploy 12.1.4 to
members of that second smart group.</font>
<br>
<br><font size=2 face="sans-serif">Users that have any version prior to
12.1.3 will not get 12.1.4 until they are updated to 12.1.3, as they move
from one smart group to the second; "Slipstreaming", as you say.
In practice the whole process happens relatively quickly and efficiently.</font>
<br>
<br><img src=cid:_2_0FFEA3540FFE792400577882852574F7><font size=2 face="sans-serif"><br>
</font>
<pre></PRE><p><span style="font-size:9.5pt;line-height:115%;font-family: Arial">This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender.</span></p>