Vista

You might want to not install the 'Desktop Experience' feature on Longhorn terminal servers and/or disable Aero for clients, because each terminal services session spawns a new instance of DWM on the server.

The client does most of the heavy lifting drawing Aero, but I could forsee DWM becoming the ctfmon.exe of Windows Longhorn Server if you enable Aero for TS sessions.

Of course, with 64-bit terminal servers and gobs of ram, it isn't going to matter too much overall. I am thinking more along the lines of future SBS servers.

This tip originated from Eric Holk at MS on the LH TS newsgroups, btw, to give credit where credit is due.

Simply delete this key:
HKEY_CURRENT_USER\Software\Microsoft\MobilePC\TMM

More details here.

I am surprised that Adobe didn't create this themselves but they seem pretty anti-Microsoft lately anyway.
Check it out here.

It needs Adobe Reader 7.x or higher installed for the API calls, so that is noteworthy for FoxIt users.
It also needs .Net 2.0 Framework, but 99% of the users running Office 2007 and/or Vista will have that installed already.

You just need to use the driver mod here.

It will "add" support for the following Mobility chipsets:

FireGL:
T2/T2e
V3100/V3200/V5000/V5200

Radeon:
9500/9550/9600/9700/9800
X300/X600/X700/X800/X800 XT
X1300/X1400/X1450/X1600
X1700/X1800/X1800 XT
X2300/X2300 HD
XPRESS 200/XPRESS 200M

Are you getting the dreaded "A device attached to the system is not functioning" message from a shared network resource that is hosted on a NetApp appliance?

Request the fix here.

I haven't seen it firsthand, but I thought it was worth mentioning.

I always had a bad feeling about the whole concept of the Protected Mode Process in Vista. It is designed to help DRM authors but in the long run it might be used for 'bad things'. Thankfully, 64-bit is "locked down" better because it doesn't have the 'legacy crutch' to keep alive.

You can read about it here. Very smart guy. MS really should have him on their kernel team and not Apple.

A good KB article describing how to extract .MSU files, the files they contain, and how to use the contents with WUSA.EXE.

A quick rundown of the process:
When you use Wusa.exe to install an update package, Wusa.exe expands the contents of the .msu file to a temporary folder. Then, Wusa.exe performs the following steps:

1. Wusa.exe uses the Windows Update metadata in the .msu file to search for applicable updates.
2. Wusa.exe copies the contents of the applicable updates to the Windows Update sandbox. The Windows Update sandbox is a protected folder.
3. Wusa.exe calls the appropriate function in the Windows Update Agent API according to the mode in which you start Wusa.exe.
4. When the Windows Update wizard completes the installation, the Windows Update Agent API returns a status. Then, Wusa.exe works synchronously with Windows Update Agent API.

Read more about it here.