Skip to content

Preventing a specific update from deploying

Featured Replies

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?

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.

  • Author

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.

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.

  • Author

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.

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.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.