Link?
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, March 25, 2016 1:32 PM To: [email protected] Subject: [mssms] RE: Excluding single software update Vote, vote, vote! From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Friday, March 25, 2016 3:05 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Excluding single software update Thanks guys for your feedback. I do hope something like an exclusion is added one of these versions. Cory Becht Global IT Systems - SCCM CH2M <http://www.ch2m.com/> www.ch2m.com | <https://www.linkedin.com/company/ch2m> LinkedIn | <https://twitter.com/ch2m> Twitter | <http://www.facebook.com/ch2mhill> Facebook From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Friday, March 25, 2016 12:53 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Excluding single software update That would be a cool feature! From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, March 25, 2016 11:36 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Excluding single software update There’s really no choice but to create a new update group and even collections. In addition to the uservoice item, I have given this feedback directly to the product group and during the MVP summit last fall, they actually did start working on a feature to allow specific updates to be excluded from specific systems. Not sure if it’ll ever make it into product, I certainly hope so. Voting for the uservoice item is a great way to tell them that you think it should make it also. J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Friday, March 25, 2016 10:17 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Excluding single software update We use a separate update group and collection, excluding the systems that have issues. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Friday, March 25, 2016 7:35 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] Excluding single software update Hi Everyone, What’s everyone doing if you have to exclude a single update to certain systems for SCCM 2012 or Current Branch? Are you creating separate update groups, one with the patch and another without the patch and creating multiple collections? Every so often it comes up that a particular patch causes conflict on a small number of systems which then has to be prevented from installing. To keep it simple we usually have a monthly software update group that has several deployments with different options for servers and workstations. Those deployments go to the same collections each month, one for servers, one for workstations. So if a new software update group is created then the systems that can’t have the patch would have to be excluded from the existing collection so they don’t receive the patch, which will start to get messy down the road. Just trying to get an idea what everyone else is doing in this scenario. BTW there is feedback to add the ability to exclude a patch from going to systems which would simplify things: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8436163-exclude-updates Thanks, Cory Becht Global IT Systems - SCCM CH2M <http://www.ch2m.com/> www.ch2m.com | <https://www.linkedin.com/company/ch2m> LinkedIn | <https://twitter.com/ch2m> Twitter | <http://www.facebook.com/ch2mhill> Facebook
smime.p7s
Description: S/MIME cryptographic signature
