This is going to be long since I want to include as much info as I can as to what is going on. Please bear with me.
I have one workstation (and of course it belongs to a very vocal, anti-SCCM person) that yesterday installed update KB2898869 a .Net 4.5.1 update, and rebooted outside the established maintenance window. I need to get to the root cause of why this happened and if possible fix this. Configuration: SCCM 2012 R2 CU2 - Single site, single site server. All roles on this server except for SUS and MP and DP. Workstation - Windows 7 SP1 Enterprise - Maintenance Windows are: Thursdays 12:05 AM duration 240 & Fridays 12:05 AM duration 240. (This is the only maintenance window defined in SCCM.) KB2898869 is a member of the Software Update Group dated 02-12-2014. (I create a new Software Update Group each month.) Software Update process: Each month I create a new Software Update Group with that month's updates. I then set the deployment up so that it can only be installed and rebooted during the maintenance window. [cid:image002.png@01CFDEDC.CE528680] Then I go back to the previous month and I check ONLY the 'Software updates installation' box. I also go back 2 months and check both boxes. That way the current month's updates can only be installed and rebooted during the maintenance window, the previous month updates can be installed at any time and only rebooted during the maintenance window, and then 2 months back the reboot can occur at any time. I figure if the updates aren't installed within two months they need to be installed and applied now. Based on the above setting the Software Update Group dated 02-12-2014 now has both of those boxes checked, thus allowing the KB2898869 upgrade to be installed and rebooted at any time. That is as I want it. Problem: There were 30 other updates in that Software Update Group. There were at least 11 updates from that update group that installed on this workstation either 02-13-14 or 02-21-14 (well within the month set aside to use the maintenance windows). The only update in that update group to install outside the maintenance window was the KB2898869 update. >From the looks of the logs and from a PowerShell query of the hotfix wmi >repository updates are applying as they should each month for this workstation. What can be causing this behavior for this client? Why is this workstation waiting 7 months to install this one update? There should have been plenty of time for this workstation to install the update and reboot in a maintenance window. This isn't the first time this user has complained about unscheduled reboots caused by SCCM. What log files besides WindowsUpdate.log can I look at to see why this is happening? I am going to completely remove the SCCM client, scrub the registry, delete the SMSCFG.ini file, and make sure all SCCM folders are deleted then reinstall the client. Any other actions you can think of that I should try? If this user wasn't so vocal and anti-SCCM I wouldn't be so concerned, but you know how this goes. This use thinks he should be able to maintain his own machine on his own schedule and doesn't see the need for SCCM. Since he is a fellow Systems Administrator he doesn't understand why he can't be SCCM free on his workstation. I am trying to do everything I can to keep SCCM on his machine. HELP! Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260 509.477.4227 [cid:image001.png@01CFDEDB.2B622490]
