<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Ack. I meant "internal" SUSes, not "internet".</div><div><br></div><div>Clinton</div><div><br></div><br><div><div>On 2-Apr-09, at 10:40 AM, Miles Leacy wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Thu, Apr 2, 2009 at 12:33 PM, Clinton Blackmore <span dir="ltr"><<a href="mailto:clinton.blackmore@westwind.ab.ca">clinton.blackmore@westwind.ab.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div style="word-wrap:break-word"><div>In that case, how do you throttle it on the server side? We are using internet SUSes (although we really want to get a cascading SUS setup, so we can set on one server which updates need to go out, and which ones should be avoided.)</div> </div></blockquote><div><br></div><div>By "internet SUSes" do you mean Apple's SUS(es)? How large and in how many disparate locations is your deployment? I ask, because a single SUS should suffice for most deployments up to a few hundred machines, provided you run your updates in off-hours and have a relatively fast network. Cascading SUSes are typically used when you have a large number of clients and/or have clients that are in multiple locations and you don't want your SUS traffic going over WAN links.</div> </div></blockquote></div><br>
</body></html>