WSUS Itanium Cranium 64-bit Drainium Insanium
Holy crap! This is getting tedious. I do not have any 64-bit or Itanium machines in my environment. If I did, it would signify one of two things: (A) I would have WAY too much time to play with computers and no life outside of that, or (B) my family packed up and left me alone in a prison on an island with nothing to do but work on 64-bit or Itanium computers.
WSUS 3.0 has indeed been a huge improvement over SUS 1.x and WUS 2.0, but there are still shortcomings you have to deal with. One of these is that it is incapable of excluding 64-bit and Itanium patches. I don't care what you do. You can select products and categories around those platforms all you want, they will still show up. It's sort of the Night of The Living Dead, part 20. Remember when SUS and WUS would choke on all the languages of .NET framework updates? You would be grinning away like you won the lottery whilst selecting only English in your options setup, only to drop your jaw on the floor in complete dismay over Korean, Croatian, Serbian and Japanese versions of the patch showing up everywhere. The fun of it all. Well, they didn't want you to feel left out in WSUS 3.0 so they've brought back ill-filtered updates for your enjoyment. Granted, it's not totally WSUS's fault. A lot of the blame rests on how the patches are built and cataloged. Many just do not publish their properties in a granular manner to allow for such filtering. That was the case with the .NET framework updates.
Here's the fun. If you're like me and don't manage any 64-bit or Itanium computers in your environment, you have to use the semi-functional "Search" feature and look for strings "x64", "64-bit" and "Itanium" and then select-all and right-click and choose Decline. I sure hope they do something to make it easier to avoid synchronizing 64-bit and Itanium updates upfront so I don't have to keep declining them all them time to keep my lists clean.