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.


From: [] On 
Behalf Of Adam Juelich
Sent: Tuesday, October 18, 2016 3:17 PM
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 

David, remember that Office 2007 goes out of support in October 2017.

On Tue, Oct 18, 2016 at 2:58 PM, Brian Illner 
<<>> 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 

(unless that limitation has gone away with Current Branch??)

BRIAN ILLNER | Canal Insurance Company
864.679.2537<tel:864.679.2537> Fax


Visit<> for news and information.

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.
On Behalf Of Adam Juelich
Sent: Tuesday, October 18, 2016 3:42 PM
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. 
<<>> 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?



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.

Reply via email to