<html>
<head>
<style type="text/css">
<!--
body { font-variant: normal; line-height: normal; margin-top: 4px; margin-right: 4px; margin-bottom: 1px; margin-left: 4px }
p { margin-top: 0; margin-bottom: 0 }
-->
</style>
</head>
<body>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Lucida Grande">Yes our SUS is an Xserve that is dedicated to SUS and file sharing, and I want it to download and cache out all approved updates to distribution points, since our distribution points run off of RAIDs on building level Xserves. That way they could sync the updates over night, and during operating hours machines would not go over the WAN for updates, they could pull them off the casper distribution point.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Lucida Grande">Does that make sense?</font><br><br>>>> "Miles Leacy" <miles.leacy@themacadmin.com> 12/11/08 1:29 PM >>><br>Are the distribution points on OS X Servers?  If so, the easiest solution is to create multiple instances of SUS on different network segments. </p>
<div content="text/html; charset=UTF-8" http-equiv="Content-Type">
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
I was thinking through an automated way to move packages from an SUS to a Casper distribution point, and it's relatively easy to get the packages there.  The hurdle is making them useful to Software Update, or even to Casper. </p>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
I suppose you could forego the SUS and add Apple update pkgs to your JSS and deploy them that way.  This would bring on additional work as you'd need to determine the dependencies and compatibility of each update manually and scope their installation appropriately.  If you use an SUS and Software Update, Apple does that work for you. </p>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
----------<br>Miles A. Leacy IV<br><br> Certified System Administrator 10.4<br> Certified Technical Coordinator 10.5<br> Certified Trainer<br>Certified Casper Administrator<br>----------<br>voice: 1-347-277-7321<br><a href="mailto:miles.leacy@themacadmin.com">miles.leacy@themacadmin.com</a><br><a href="http://www.themacadmin.com">www.themacadmin.com</a><br><br><br><br><br> </p>
<div class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
On Thu, Dec 11, 2008 at 1:40 PM, Thomas Larkin </p>
<div dir="ltr">
<p style="margin-top: 0; margin-bottom: 0">
<<a href="mailto:TLARKI@kckps.org">TLARKI@kckps.org</a>> </p>
</div>
<p style="margin-top: 0; margin-bottom: 0">
wrote:<br> </p>
<blockquote style="margin-top: 0; padding-left: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; border-left: 1px #ccc solid" class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
I have a self service policy that runs all approved updates off of our<br>sus. I also download the pkg for quick critical updates and push them<br>out via a policy.<br><br>I only have one sus and it would be awesome if I could cache those<br>updates to the casper distribution points. Then I wouldn't have 6000<br>clients pulling updates off one server.  Then just use that one server<br>to control it while the casper share points distribute it to their set<br>vlans.<br> </p>
<div>
<div>
<br>
</div>
<div class="wj3c7c">
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
-----Original Message-----<br>From: "Miles Leacy" <<a href="mailto:miles.leacy@themacadmin.com">miles.leacy@themacadmin.com</a>><br>Cc: List, Casper <<a href="mailto:casper@list.jamfsoftware.com">casper@list.jamfsoftware.com</a>><br>To: Nichols, Jared <<a href="mailto:jared.nichols@ll.mit.edu">jared.nichols@ll.mit.edu</a>><br><br>Sent: 12/11/2008 11:29:28 AM<br>Subject: Re: [Casper] Updates<br><br>Do your users run it via self-service?<br>I have an "updates available" smart group that consists of all machines<br>with<br>>0 updates available.  A self-service policy scoped to this smart group<br>allows non-admins to run Apple updates.  As silly as it may seem, this<br>option can inflate the egos of many users.  You might be surprised how<br>far<br>the illusion of control gets you with people.<br><br>Of course, I have a second policy scoped to the same group that runs<br>over<br>the weekend for anyone who didn't avail themselves of self-service.<br><br>----------<br>Miles A. Leacy IV<br><br> Certified System Administrator 10.4<br> Certified Technical Coordinator 10.5<br> Certified Trainer<br>Certified Casper Administrator<br>----------<br>voice: 1-347-277-7321<br><a href="mailto:miles.leacy@themacadmin.com">miles.leacy@themacadmin.com</a><br><a href="http://www.themacadmin.com" target="_blank">www.themacadmin.com</a><br><br><br><br><br> </p>
</div>
</div>
<div class="ih2e3d">
<p style="margin-top: 0; margin-bottom: 0">
2008/12/11 Nichols, Jared <<a href="mailto:jared.nichols@ll.mit.edu">jared.nichols@ll.mit.edu</a>><br><br>>  I run our own Software Update Server so I can vette any packages<br>first.<br>>  If it's ok, I release it in SUS and let the software update mechanism<br>> handle it.  I do force a once monthly mandatory update.  Users can run<br>it<br>> optionally on their own or it'll pop up automatically weekly.<br>><br>> j<br>><br>><br>><br> </p>
</div>
<div class="ih2e3d">
<p style="margin-top: 0; margin-bottom: 0">
> On 12/11/08 12:12 , "Jeff Strauss" <<a href="mailto:jstrauss@loyolahs.edu">jstrauss@loyolahs.edu</a>> wrote:<br>><br>> Hey all,<br>><br>> Do you guys have any procedures for deploying updates to machines? If<br>so,<br>> can you shed some light on how you handle updating clients?<br>><br>> Thank you much!<br>><br>> *Jeffrey A. Strauss<br>> *Department of Educational Technology<br>> *Systems Administrator<br>> *Loyola High School of Los Angeles<br>> 1901 Venice Blvd.<br>> Los Angeles, Ca 90006<br>> (213) 381-5121 x265<br>><br>> Please consider the environment before printing this e-mail.<br>><br>><br>><br> </p>
</div>
<p style="margin-top: 0; margin-bottom: 0">
> --<br> </p>
<div>
<div>
<br>
</div>
<div class="wj3c7c">
<p style="margin-top: 0; margin-bottom: 0">
> 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>><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>><br><br> </p>
</div>
</div>
</blockquote>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
</div>
</body>
</html>