And yes, as others have stated, don't go over 100 per SUG. I actually have
two 2016 SUGs, one is for overflow.   J


From: []
On Behalf Of Murray, Mike
Sent: Tuesday, October 18, 2016 1:14 PM
Subject: [mssms] RE: SCCM SUP updates groups


I'm sure you will get many different responses - there is no single way. We
went for simplicity. Everything goes into one SUG for the current month's
updates, then get moved to a 2016 - all SUG once the next month's updates
are released. Then we set our deployments to our desired tastes.




From: <>
[] On Behalf Of Fast, David D.
Sent: Tuesday, October 18, 2016 11:58 AM
To: <> 
Subject: [mssms] SCCM SUP updates groups


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



Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to