WSUS recap

Main Entry:   blog
Part of Speech:   n
Definition:   an online diary; a personal chronological log of thoughts published on a Web page; also called Weblog, Web log
Example:   Typically updated daily, blogs often reflect the personality of the author.
Etymology:   shortened form of Weblog
Usage:   blog, blogged, blogging v, blogger n

So I’m out looking on the Technet blog site for WSUS news.  And of course kudos to the SBS team for having a blog post out there but there’s no post from the WSUS team.

Is it just me or have blogs lost a bit of the intended purpose?  Communication?  Oh don’t get me wrong, there’s information out there on this WSUS issue but forgive me if I think the fact that the only TechNet blog that is talking about it is a  SBS blog is a little bit suprising.  I can’t imagine us “riff raff” down here are the only ones running WSUS and noticed the problem today.  Combine that with the issue from a few weeks ago where WSUS deployed Desktop Search and still, in my opinion, has not properly communicated the recommended enterprise means to remove the patch.

A nice blog post about “we know this” “we’re investigating” might be nice. SBSers aren’t can’t be the only ones running WSUS out there.

WSUS sync snafu cripples enterprise update ability on eve of Patch Tuesday:

The Official SBS Blog : WSUS 2.0 and 3.0 Errors On Small Business Server:

Bobbie Harder in the WSUS newsgroups

Link to WSUS blog regarding this issue:
_______ none at this time ________
Response has been posted

2 Thoughts on “WSUS recap

  1. Jim Allen on November 13, 2007 at 8:45 am said:

    Did someone come in during the night and fix the problem? It seems to be gone this morning and I haven’t done anything. Or is it still just too early for me:)

  2. Any posting to the WSUS blog would be in a similar tone to the postings a couple of weeks ago re: Windows Desktop Search. They’d be in that same “we’re sorry, it’s fixed now, but it was really no big deal anyway” tone, and wouldn’t contain any useful information.

    This only confirms (*again*) my frustration with Microsoft’s lack of quality-control on updates. It’s as though they don’t actually use any of this software internally. Why aren’t they sync’ing internal WSUS servers to a Windows Update “lab” and verifying that there are no issues before they damage our production WSUS servers. Why aren’t they seeing Windows Desktop Search loading inappropriately on internal labs? Why are they seeing Spanish language versions of IE 7 updates being released with English metadata?

    How easy would it be for a disgruntled Microsoft employee (or a third-party attacker) to release an update that disabled tens of thousands of servers and hundreds of thousands of desktop computers?


    Of course they’re not going to say anything about it. We must ignore this elephant in the room.

Post Navigation