KB925902 forced reboots

we have a policy making updates manual so we can push them rather than
install them automatically. On April 3 and 4, we had a few reports that
people received a notification that their machine was shutting down and after
a minute, it rebooted. From the reports, it appears KB925902 was the
culprit. It affected a fairly small number of machines but it caused
problems for the affected users. How did the update force itself to install
and reboot without user interaction? Why were just some machines affected
that way? How can we ensure it doesn't happen again?

"janieray" wrote:

> we have a policy making updates manual so we can push them rather than
> install them automatically. On April 3 and 4, we had a few reports that
> people received a notification that their machine was shutting down and after
> a minute, it rebooted. From the reports, it appears KB925902 was the
> culprit. It affected a fairly small number of machines but it caused
> problems for the affected users. How did the update force itself to install
> and reboot without user interaction? Why were just some machines affected
> that way? How can we ensure it doesn't happen again?

Check to see if Auto updates has been tunred on with the affected machines.

Yes, Auto updates are turned on for all our 800+ machines. But I expected
the Default Domain Policy to override that. Default Domain Policy is set to
make updates manual.
But even with auto updates, we usually get the yellow icon in the
notification area and when the update is loaded, the machine asks to be
restarted. In these cases, it just said rebooting in "x" minutes, save your
work.

"Leo" wrote:

>
>
> "janieray" wrote:
>
> > we have a policy making updates manual so we can push them rather than
> > install them automatically. On April 3 and 4, we had a few reports that
> > people received a notification that their machine was shutting down and after
> > a minute, it rebooted. From the reports, it appears KB925902 was the
> > culprit. It affected a fairly small number of machines but it caused
> > problems for the affected users. How did the update force itself to install
> > and reboot without user interaction? Why were just some machines affected
> > that way? How can we ensure it doesn't happen again?
>
> Check to see if Auto updates has been tunred on with the affected machines.