Vista

Another handy hotfix to keep around for your System Center Operations Manager 2007 install if you are running Server 2008 or Vista. If your Health Explorer is crashing, you will want to install this OS update here.

It looks as though it isn't an error in SCOM, but an error in ComCtl32.dll.

Go here for an update for Windows Vista SP1 and Windows 2008's RDP (Terminal Services) technology. It plugs a non-paged pool memory leak (my favorite to plug). On a good note, Vista and Server 2008 allocate non-paged pool dynamically instead of statically at boot time, so it will take a lot longer (typically) for this type of memory leak to take down your system.

In the past, before Vista, non-paged pool was a fixed amount, which can cause all sorts of problems if you have a leaky driver or application, like Symantec's Corporate Anti-Virus v10.

Only do this as a last resort for a problematic application because it opens up security restrictions in a bad way on a computer system.

To disable UAC remote restrictions, follow these steps:

1. Click Start, click Run, type regedit, and then press ENTER.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type LocalAccountTokenFilterPolicy, and then press ENTER.
4. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
5. In the Value data box, type 1, and then click OK.
6. Exit Registry Editor.

The LocalAccountTokenFilterPolicy registry entry in the registry can have a value of 0 or of 1. These values change the behavior of the registry entry to the behavior that is described in the following table.

Value
0 This value builds a filtered token. This is the default value. The administrator credentials are removed.
1 This value builds an elevated token.

You can read more about this in detail, here.

Go here to read about the issue and update your MDAC on XP SP2, XP SP3, Vista RTM, Vista SP1, and Server 2008 to this latest revision to prevent potential data loss in certain (rare) cases.

This is the bug that caused the delay with XP SP3 due to problems with CRM.

I was always curious what issue came up at the last minute that would cause the delay of XP SP3. I had wondered if they were pulling it due to aspects of the XP SP3 release still referring to itself as a beta in spots. I also had wondered if it was somehow related to the NTFS.sys/filter bug that affected Home Server and if it had become a blocking issue in the other operating systems.

Overall, it isn't a terribly interesting bug to me, but I don't deal with CRM a lot. I'm curious if it could affect other SQL/MDAC applications, but it sounds pretty isolated. If anyone bumps into a new issue, please leave a comment. If I am reading the article correctly, it looks like it might be isolated to the msadce.dll file shipped with XP SP3.

I am just happy overall that XP SP3 is finally out and I don't have to carry around a USB stick of hotfixes for people. I'm also curious to hear if you have any issues installing XP SP3 and I'll make sure your comments get to the Windows Client team in Redmond.