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 www.ch2m.com<http://www.ch2m.com/> | LinkedIn<https://www.linkedin.com/company/ch2m> | Twitter<https://twitter.com/ch2m> | Facebook<http://www.facebook.com/ch2mhill>
