Last week,
On the Wednesday after Update Tuesday, I came in to find updates waiting to
be installed. Coffee didn't take effect quickly enough, and staffers were
staring to arrive before I realized it and could go ahead and reboot the
production server.
So I just brought up the Services MMC and turned off the Automatic Updates
service. That kept the server from automagically restarting like the
workstations do (I have not created AD containers for my servers so they can
have separate Group Policies, its on the to-do list).
Or so I thought. Well, the server did not restart at noon. But much later
Thursday morning, the logs show that the Automatic Updates service started at
one second after 1am.
WTF??? Is this action the result of defining and enabling the policy
"Reschedule Automatic Updates scheduled installations"? But how and why would
that perform as I saw when the service itself is not running?
Is there a watchdog service that kicks Automatic Updates back on? And if so,
which one is it?
tia,
-dq
--
Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better.
-Samuel Beckett, "Waiting for Godot"
|
Similar Threads
Linear Mode
