Tuesday, July 10, 2012 2:19 PM
Hi, we have WSUS configured via a GPO to install patches unsday at 6 am
we had an issue yesterday were a server that should have had its patches installed on sunday july 8 at 6 am, instead downlaoded and installed its patches Monday July 9 at 6:30 pm
This caused an issue as it was an important SQL server
Does anyone know what could have caused this as the other 150 servers scheduled for sunday worked fine. the patches were approved friday morning so there was plenty of time for the SQL Server to connect to WSUS and detect what patches it needed.
Also, is there a way to configure the GPO so that if the patches havent been installed by noon on sundays to not continue. we cannot have patches being installed the next day like we experienced yesterday.
Tuesday, July 10, 2012 8:53 PMModerator
downlaoded and installed its patches Monday July 9 at 6:30 pm
Does anyone know what could have caused this
There are two scenarios that could cause this behavior, and the WindowsUpdate.log entries for 6:30pm will tell us exactly what happened.
- The updates had a deadline configured on the approval and the deadline expired.
- The machine was powered off at 6:00pm on Sunday, and powered back on Monday evening, and the updates installed at power-on because that's the default behavior of the Windows Update Agent when a scheduled installation event is missed and there were updates to be installed at that event.
Also, is there a way to configure the GPO so that if the patches havent been installed by noon on sundays to not continue.That really depends on why the updates installed on Sunday evening in the first place -- but generally No.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Friday, July 20, 2012 8:03 AMModerator
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.
If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
TechNet Subscriber Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Tuesday, July 24, 2012 1:19 PM
I was on vacatiion last week and therefore unable to respond
the updates did not hvae a deadline associated witr it and the server was not powered off and back on
this same server did the exact thing this past week. even though it was not in the computer group being patshed, it decided to apply pathces to itself again
i have taken it completely out of WSUS for now and i will look into the windowsupdate log