penfold Posted February 2, 2021 Posted February 2, 2021 Can someone please check my train of thought. We want to move to a approve updates once per month, but stagger the install by setting group policy to install on different time. If a patch is released globally and we see a problem, can we then decline that update and it will not be installed on later systems? From what I can see when you decline an update it can remove it, but if it hasn't installed yet, what is the process? Will the client detect that this update is no longer needed and not install even though it is downloaded locally? I've just checked this https://social.technet.microsoft.com/Forums/ie/en-US/17bdb06e-1cc5-4e61-b39f-d3d5957f99a6/declining-an-update-thats-been-downloaded-but-not-installed?forum=winserverwsus I've also seen that once you have declined the update you can select approved for removal. Which if I understand will remove it where it is installed. But what happens for those systems that are yet to install it...does this mean it will be installed and then removed?
ajs Posted February 18, 2021 Posted February 18, 2021 My understanding is that it will remove it when a machine has it installed but won't offer it as an update for those that don't.
penfold Posted February 19, 2021 Author Posted February 19, 2021 This is what I was thinking. But I am not sure if the client has already downloaded the update, will it detect that it is no longer needed?
ajs Posted February 20, 2021 Posted February 20, 2021 The few times I've had to use the option, the update disappears from the client's list of available updates. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now