WSUS screwed up?

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Has anyone ever done a force update in WSUS? I did one like a month and a half ago and according to our field techs since that time some of the patches that I approve in the normal fashion act like they've been forced. Normally it isn't an issue, but today it is acting like the .net 3.5 hot fix that came out on Tuesday is being forced and the problem with that is it is forcing a reboot. At the moment plenty of people are slightly perturbed.

Thanks

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

What do the reports on the individual machines in WSUS state have they updated and when?

 

yeah they're updating and rebooting, it is the rebooting part that is the problem because it is forcing them to do so. the box for postpone is grayed out and so is the "X" to close the dialog box.

 

Not sure about your specific GPO settings you have in place, but check the following out:

No Auto-restart for Scheduled Automatic Update Installation Options
This policy specifies that to complete a scheduled installation, Automatic Updates will wait for the computer to be restarted by any user who is logged on, instead of causing the computer to restart automatically.

If the status is set to Enabled, Automatic Updates will not restart a computer automatically during a scheduled installation if a user is logged on to the computer. Instead, Automatic Updates will notify the user to restart the computer in order to complete the installation.

Be aware that Automatic Updates will not be able to detect future updates until the restart occurs.

If the status is set to Disabled or Not Configured, Automatic Updates will notify the user that the computer will automatically restart in 5 minutes to complete the installation.

This policy applies only when Automatic Updates is configured to perform scheduled installations of updates. If the Configure Automatic Updates policy is disabled, this policy has no effect.

To inhibit auto-restart for scheduled Automatic Update installation options
In Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then click Windows Update.

In the details pane, click No auto-restart for scheduled Automatic Update installation options, and set the option.

Click OK.

Taken from technet

 

the gpo has it set to not reboot if a user is logged in and the delay is the default 5 minutes. all the typical items are right it really just seems like a glitch in wsus to where it makes some updates have the deadline forced. man is it frustrating me.

 

By your comments, I'm assuming that you did'nt force the updates to have a deadline.

Is there any common occourences, e.g. workstations in the same OU, same update etc?

 

no, i only force updates when they're major security related such as the conficker patch. it is doing it in all of our domains (50+) so it has me puzzled at the moment. i did some googleing and only found people commenting on how to force, which really wasn't what i was looking for, but i do appreciate the dialog to help trouble shoot.

thanks

 

Not sure mate, I would proceed down the lines of trying to replicate the issue and trying to determine if one patch is causing this.

Let us know what you find out.

 

yeah, yesterday i only pushed the one .net 3.5 hotfix and it is sucking wind for me today with all these issues. we'll figure it out... maybe