In 2012, I add a custom severity to any update I don't want deployed. Then all of my ADR's filter that out.
Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, November 15, 2013 2:18 PM To: '[email protected]' Subject: RE: [mssms] Blacklist or Ban certain windows updates through SCCM It won't break it per se but that also won't work. ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Stephen Owen Sent: Friday, November 15, 2013 1:14 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Blacklist or Ban certain windows updates through SCCM Thanks for the quick reply, that is a solid work around. I've heard that if you open the Update Services console and make any changes, you can pretty much break everything, at least in 2007. Is that correct? You'd think declining the update there woudl be a good way to resolve this situation. On Fri, Nov 15, 2013 at 2:01 PM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: Nope. This is a common ask and there's no real solution. I add them to an update group called DO NOT DEPLOY and deploy them to an empty collection. Then when I search for updates I filter out deployed updates in my search. ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Stephen Owen Sent: Friday, November 15, 2013 1:00 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Blacklist or Ban certain windows updates through SCCM Hi all, SCCM 2007 R3 SP2 env here, need to find a way to ban or black list certain updates to ensure that other admins don't add them to updates lists due to a conflict with a line-of-business app. I think my google-fu is failing me today, for I cannot figure out a good way to do this. Can I force expire or supercede a certain update, to prohibit others (and myself) from accidentally deploying it? If you know of a good way to accomplish this, please let me know. thanks, ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
<<inline: image001.jpg>>
