We have a mix of everything here, so hopefully I can simplify it for you. I have ADRs set up just for download/distribution and then are "deployed" to a blank group (that has the All collection excluded. Never can be too safe). That gets updates out to all of our distro points without us having to deal with that part of it when we do our deployments and packaging (we push out to our DEV environment on patch Tuesday). We have an arcane way of pushing our updates out to groups, but I am looking at replacing that with maintenance windows. But that's not germane to this. As for packages, I have them split by year for Product. Windows Server has a year (2014, 2015, 2016, etc). Desktop a year. Office a year, etc. For SUGs, we do a monthly group that includes all updates for a month in one SUG (one for servers, one for desktop because of different teams). As for ongoing maintenance, we have baselines for all explicit product groups... Windows 7, WIndows 2008 R2, Windows 2012, etc. Those baselines are always deployed to everything, no enforced reboots accept to a few special collections. Cleanup/maintenance happens after our patching cycle is complete (and some during the cycle). At that point we move everything from the monthly SUG to the baselines. Some of these steps are a bit cumbersome, but it is quite refined from where it was when I took over. Adding in maintenance windows will likely be the last piece that makes this process run much better.
We patch 2,000+ servers and 12,000+ workstations this way every month and generally hit 99% compliance on servers and 95% compliance on workstations. (Our workstation environment has some caveats.) If you want to know anything in more detail (this is all pretty high level overview) feel free to let me know. -Erik On Tue, Oct 18, 2016 at 5:03 PM, Jason Sandys <[email protected]> wrote: > For update group yes, not for update package though – they are two > different things and using them synonymously is not correct. You can’t > interchange them with ADR either. There is no limit with update packages > although it’s best to keep them smaller instead of using one giant one. > > > > J > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Adam Juelich > *Sent:* Tuesday, October 18, 2016 3:17 PM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM SUP updates groups > > > > Good point, Brian. > > > > Depends on the number of updates, those that are superseded, and the > severity/classes one chooses. I believe that 1000 limit per SUG is still > in effect. > > > > David, remember that Office 2007 goes out of support in October 2017. > > > > On Tue, Oct 18, 2016 at 2:58 PM, Brian Illner <[email protected]> > wrote: > > Don’t forget about the 1000 item limit on the distribution packages. If > you lump all Office into a single ADR/SUG/Package you may hit that limit > before too long. > > > > (unless that limitation has gone away with Current Branch??) > > > > *BRIAN* *ILLNER |* Canal Insurance Company > 864.250.9227 > 864.679.2537 Fax > > > > > Visit canalinsurance.com for news and information. > > > <https://www.linkedin.com/company/canal-insurance-company> > > *WARNING*: *As the information in this transmittal (including > attachments, if any) may contain confidential, proprietary, or business > trade secret information, it should only be reviewed by those who are the > intended recipients. Unless you are an intended recipient, any review, > use, disclosure, distribution or copying of this transmittal (or any > attachments) is strictly prohibited. If you have received this > transmittal in error, please notify me immediately by reply email and > destroy all copies of the transmittal. While Canal believes this > transmittal to be free of virus or other defect, it is the responsibility > of the recipient to ensure that it is virus free and no responsibility is > accepted by Canal (or its subsidiaries and affiliates) for any loss or > damage arising therefrom.* > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Adam Juelich > *Sent:* Tuesday, October 18, 2016 3:42 PM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM SUP updates groups > > > > Are you going to utilize ADR's? If so, it is up to you to design. You > can combine all clients with all versions of Office, for example, into a > single collection and ensure your updates for those products targeted > appropriately. Otherwise, you can do a collection for each product and > target that way. I'm sure others may have better reasons and > best-practices......... > > > > That being said, 4 versions of Office? Are you cray-cray? > > > > On Tue, Oct 18, 2016 at 1:58 PM, Fast, David D. < > [email protected]> wrote: > > Okay, I’m trying to get serious about implementing SUP in SCCM. In our > environment, we have W7x86, W7x64, W8.1x64, W10x64 (RTM, 1511 and 1607). > We also have Office 2007 (x86), Office 2010 (x86), Office 2013 (x86 and > x64) and Office 2016 (x86). > > Does each product/architecture combination get its own baseline SUG and > monthly update SUG? Seems like all of the guides for setting up SUP assume > the environment is standardized on single platform/product configurations. > Can someone point me to a guide that addresses multiple platform/product > environments with initial setup + ongoing month-to-month configuration? > > > > Thanks, > > > > David > > > > > ------------------------------ > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. > > > > > > > > > > > > > >
