?I concur with breaking the package down -- one giant monolithic package is asking for trouble. How you do it is almost always arbitrary though and depends upon your infrastructure. For those with a complicated topology and many remote DPs and/or secondary sites, then smaller packages make a lot of sense. For those not wanting to change the package referenced in their ADRs very often and who don't have a complicated topology, the somewhat bigger packages are fine. I think the key ultimately for everyone to remember is that as long as the updates is at least one available and accessible package, then you're fine. The exact package break-down is typically arbitrary and has no technical implications as long as you are breaking them down to "managable" levels with managable define by your environment.
J ________________________________ From: [email protected] <[email protected]> on behalf of s kissel <[email protected]> Sent: Wednesday, February 26, 2014 7:29 AM To: [email protected] Subject: RE: [mssms] SW Updates in SCCM 2012 I would actually highly recommend NOT going with a yearly package. You can end up with 5-10 gigs worth of patches passed around an environment, and when you have something like 80 secondaries and another 100 distribution points, pushing that size package around every month will deplete your sending resources for other packages very quickly. While it's a bit more management to have a monthly, or even quarterly package, it scales a lot better in terms of your WAN and far off resources being able to handle it better. Furthermore, if some of the content is missing (either a language didn't get downloaded or your clients in a distant region are complaining that the updates are stuck in a downloading state) it is a lot easier to find the problematic update, fix it, and then redistribute a small say 100-200 MB software update package than a couple gig one. -S ________________________________ From: [email protected] To: [email protected] Subject: RE: [mssms] SW Updates in SCCM 2012 Date: Wed, 26 Feb 2014 09:02:31 +0000 Better to go with yearly package. Whenever monthly patches are relased by MS those can be downloaded and kept into that package. Doing this method all your clients including new builds will be benefited to have minimum one year patches from MS and that would cover up most of the vulnerabilities. Thank You. From: [email protected] [mailto:[email protected]] On Behalf Of JRIT Sent: Wednesday, February 26, 2014 2:09 PM To: [email protected] Subject: [mssms] SW Updates in SCCM 2012 Folks, Is there a best (or common) practice to create packages for SW Updates? I mean, how many packages is common to have, one per month , or one for each semester, per year? Any tips around this? Thank you, _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
