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.
