Among the most confusing stories that we have asked .NET Framework customers to understand has been .NET Framework 1.1 support on Windows Server 2003 and 64-bit versions of Windows. I've blogged about this before. Today I get to tell you that we've done right by putting .NET Framework 1.1 servicing releases on Windows Update for 64-bit platforms.

Updates for the the .NET Framework 1.1 come in two flavors: One set of packages for 32-bit x86 versions of Windows Server 2003 and a different package for everything else. Similarly, updates for the .NET Framework 1.0 come in two flavors as well: One set of packages for Tablet PC and Media Center editions of Windows XP, and a different set of packages for everything else. Confused? You're not alone. I'll try to help.

In the bad old days, before specialized update deployment program management, it was the responsibility of the update release manager to deploy their own updates. And in a sense, things haven't really changed so much from the bad old days, except that they have. Let me explain.

I have a vision statement up on my wall. It says this: "Deliver the right updates to the right customers at the right time."

I stated in an earlier post that "I am the person in charge of getting product updates (service packs and hotfixes) for Visual Studio and the .NET Framework into distribution channels like Windows Update, Microsoft Update, and the Microsoft Download Center." It occured to me that some of you might care which updates go where. If you do, read on!