[Casper] Chaining updates

[Ryan Harter]

I haven't gotten into any updaters yet, but can't we just run composer  
and have it look for new and modified files, install all the updaters  
to MS Office, and then push the resulting package as a "slipstreamed"  
update.

I only ask because I was just about to do that for MS Office and  
though someone else might have done this before.

Ryan Harter
UW - Stevens Point
Workstation Developer
715.346.2716
Ryan.Harter at uwsp.edu

On Nov 4, 2008, at 9:55 AM, sean.hansell at jwt.com wrote:

>
> The way I've managed this is by chaining policies based on smart- 
> groups tagge to Application version.
>
> 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.
>
> 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.
>
> 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.
>
> <ATT00001.jpg>
> 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.
>
> <ATT00002.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20081104/9267c967/attachment.html