Technology Burner Technology Burner

I’ve had this happen to me a few times now. Fresh Windows Server 2008 install wants you to go online and get updates. Yet I am faced with this error:

The “dreaded” Code 80244022. OK, I dunno how dreaded that is, but I hate long numeric code errors. They usually correlate to a high p.i.t.a. factor.

This doesn’t happen very often so when it does I like to help spread the word. Microsoft released a “critical” update today impacting all supported OS’s from Windows 2000 through the Windows 7 pre-beta.

If you’re a Windows user or manage Windows machines, it seems like you should plan on getting this one and rebooting some rigs. I know I’ll be rebooting a bunch of servers later tonight.

This is noteworthy as the update was pushed today instead of waiting for next month’s “Patch Tuesday.” Therefore, clearly the folks at Microsoft are nervous.

With my new CentOS (Linux) servers, I wanted to be sure that I didn’t fall in to the trap of having them do any sort of automatic updates. I don’t do that with Windows servers and I sure don’t intend to start with Linux servers either! That way lies madness, right?