Been a while since I used only wsus, but what does the reboot policy say? Computer Configuration/Policies/Administrative Templates/Windows Components/Windows Update "No auto-restart..."
> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Michael Leone > Sent: Friday, January 26, 2018 6:44 AM > To: [email protected] > Subject: [NTSysADM] Scheduling updates on a DC via GPO isn't working > > I can't tell what I am doing wrong (I'm practically certain it's my > fault, but I don't know where ... yet). I want to schedule automatic > updates using WSUS to my domain controllers. So I created new AD > groups (multiple groups, because I want to stagger the rebooting of > DCs - I have 6). And I made a series of new GPOs, and set them to > automatically download and schedule install, all at different hours > and different days. Filtered them to the new AD groups, linked them to > the "Domain Controllers" OU. > > So one was supposed to happen this morning at 5 AM. Nothing. No reboot. > > I check the host, and both "gpresult /r" and rsop.msc are telling me > the same thing - updates are scheduled to be installed Friday at 5 AM. > The specific GPO that this DC is supposed to use is actually being > applied, it says. > > And there are 5 important updates waiting, so I know that it checked > in with WSUS, and found what it should. So it should have done > *something*. > > But no installation today, no reboot. No interesting entries in event > log. Nothing interesting in windowsupdate log - it says it found 5 > updates, but nothing about installing the durn things ... > > This should work, right? No reason I can't create a GPO to > automatically install Windows Updates via WSUS, right? >
