Newsletter Archives
-
WSUS on Windows Server 2012 R2 appears to be badly broken
Left hand, meet right hand.
Thanks to Cliff Hogan, who’s awake while we all sleep.
InfoWorld Woody on Windows
UPDATE: Following on a tip from Rod Trent, over at WindowsITPro, Microsoft has reported on the issue and marked it closed:
[Resolved] Service Restored(Started on 5/3/2016 8:53:00 PM UTC)5/4/2016 8:19:08 AM (UTC)Final Status: Engineers identified that the Intune service was unable to synchronize with recently deployed Microsoft updates. Engineers deployed a fix to the affected updates, which resolved the issue. User Impact: There was no end-user impact; impact was limited to administrators only. Affected administrators may have been not receiving recently published updates through Microsoft Update or Windows Update. Scope of Impact: Many customers appeared to be impacted by this event. For those customers affected, this issue potentially affected any administrator attempting to access or use the affected feature. No customer reports of the issue were identified during this event. Incident Start Time: Tuesday, May 3, 2016, at 9:53 PM UTC Incident End Time: Wednesday, May 4, 2016, at 7:45 AM UTC Preliminary Root Cause: An issue has occurred that prevented update synchronization. Please consider this service notification the final update on the event.I count that as a 10-hour WSUS disruption.It’d be interesting to know if the source of the problem was ESD encryption. -
Botched WSUS patch KB 3148812 still throws errors 80244019, 80244008, 8024401f
And Microsoft just pulled the only documentation they had.
InfoWorld Woody on Windows
-
Microsoft provides workaround for issues with KB3148812 WSUS update
If you’re a WSUS admin, this may come as a relief. Or not.
From Richard Hay at WindowsITPro
-
Windows Update Agent and WSUS oddity
I’m no expert on WSUS, so I pass this on for general consumption. From IT:
I’m a System Admin, running SBS2011 with WSUS. In the SBS Console I have updates for Client AND Server computers set to none… On the Client Workstations that use WSUS (Not WU) I have them set to update automatically… My thinking is The clients will update automatically only after I manually OK the updates, yet this morning everything has been updated Windows updates, Office updates… Is Microsoft pulling a fast one or am I missing something?
Also please see screenshot of Windows Update Agent 7.6.7600.256 being installed as well as updates that aren’t security related (I have several of them on other screenshots) despite having security only which has since been changed to NONE, Windows update seems to only be honoring our request unless MS really wants it installed and this is using WSUS… Do a search for the windows update agent in “Installed Updates” and it won’t show up, but from my screenshot you can clearly see it was successful…
-
How Windows 10 will be updated
I think.
The story’s not as bad as I thought – although I’m certain many of you will disagree. Have at it in the InfoWorld comments. Some of the powers that be at Microsoft will be watching.
InfoWorld Tech Watch
-
Microsoft fixes Windows 8.1 Update for corporate WSUS servers
… and extends the corporate (corporate only!) Windows 8.1 Update cutoff to August.
InfoWorld Tech Watch
-
Tech behind Flame attack could compromise Windows Update
Flame itself is a yawner. But the technology that’s been used – which researchers are only starting to dig into – is breathtaking.
And scary.
InfoWorld Tech Watch.