Sorry for the length but I wanted to include details. You can skip to the last paragraph for the short version.
We have the following computer groups:
1st weekend, 2nd weekend, 3rd weekend, 4th weekend, and last weekend. Each week, we select the updates for the month and approve/deploy them to the appropriate upcoming weekend. I discovered something strange that happened this past month that is no good...
This past weekend would have been 4th weekend which means only select machines (members of this computer group in WSUS) should have received updates and thus install them and reboot. However, machines from all different weekends also grabbed updates that they were missing and installed them and rebooted.
In particular, I have searched the logs on our WSUS server and saw where on 3/10 I deployed update KB2916036 to 3rd weekend. This included 6 different versions of the same KB: server 2012, server 2008 x64, server 2008 R2 x64, server 2008, server 2003, server 2003 x64. When looking at Server-A (member of 3rd weekend) I can see that it picked up and installed several updates like it should have on 3/15 but it did not install KB2916036 until this past weekend (3/22).
I verified that KB2916036 (Server 2008 R2 x64) was deployed on 3/10 but the server did not pick it up until 3/22, despite having picked up several other updates and installing them on 3/15. Please note, this is just a particular example of an update and a server - there are several different servers having the same issue with other updates. This means, I have several servers rebooting on weekends that they should not be! Why would a machine check into WSUS and successfully grab and install several updates but miss a couple?
