DC OS is Win 2012 R2. And yes, the option to reboot with logged in users is disabled. Not that I leave a DC with a logged in user overnight; I always log out when I am done, so there was no logged on user at the time the updates were supposed to install. Even if so, I should have seen a message to that effect in a log, shouldn't I?
On Fri, Jan 26, 2018 at 9:29 AM, Susan Bradley <[email protected]> wrote: > What OS? > > and did you set the setting to not reboot if a user is logged in? > > > On 1/26/2018 5:44 AM, Michael Leone wrote: >> >> 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 automaticWhat >> 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? >> >> >> > > >
