firstcom Posted January 14, 2015 Report post Posted January 14, 2015 We have a schedule to sync updates from WSUS daily and deploy them every Thursday. However, we have a specific update that we do NOT want to deploy to any PCs. When I go to the specific update and choose to disable the deployment, it shifts back to "enabled" on the next synchronization. How do I permanently disable the update from deploying via SCCM? Quote Share this post Link to post Share on other sites More sharing options...
T1mnl Posted January 14, 2015 Report post Posted January 14, 2015 You could make a Dummy Update Group, Download and Deploy the update to that group and it shouldn't come back in the next synchronization. Quote Share this post Link to post Share on other sites More sharing options...
firstcom Posted January 14, 2015 Report post Posted January 14, 2015 So a software update needs at least one active and enabled deployment or it will re-visit all of them? You could make a Dummy Update Group, Download and Deploy the update to that group and it shouldn't come back in the next synchronization. Quote Share this post Link to post Share on other sites More sharing options...
surfincow Posted January 15, 2015 Report post Posted January 15, 2015 Hello, If you are using automatic deployment rules for this you can add "custom severity = none" in the criteria for your software updates. Then, on the individual update you do not want to distribute, set a "custom severity" to that update (anything other than "none"). Since your rule targets updates that do not have a custom severity set it should not download/deploy it. This assumes that you are using ADR's and not currently setting custom severity for updates. 2 Quote Share this post Link to post Share on other sites More sharing options...
firstcom Posted January 15, 2015 Report post Posted January 15, 2015 Good method. Thanks! Hello, If you are using automatic deployment rules for this you can add "custom severity = none" in the criteria for your software updates. Then, on the individual update you do not want to distribute, set a "custom severity" to that update (anything other than "none"). Since your rule targets updates that do not have a custom severity set it should not download/deploy it. This assumes that you are using ADR's and not currently setting custom severity for updates. Quote Share this post Link to post Share on other sites More sharing options...
Nunzi0 Posted January 15, 2015 Report post Posted January 15, 2015 Hello, If you are using automatic deployment rules for this you can add "custom severity = none" in the criteria for your software updates. Then, on the individual update you do not want to distribute, set a "custom severity" to that update (anything other than "none"). Since your rule targets updates that do not have a custom severity set it should not download/deploy it. This assumes that you are using ADR's and not currently setting custom severity for updates. Great method. I've been using the ADR's and excluding the title of the updates, but this is much easier to maintain in the long run. Quote Share this post Link to post Share on other sites More sharing options...
