You enable the account management auditing feature in a Windows Server 2003 domain. When you add a user of a different domain to a universal group, an incorrect audit event is logged in the event log on the domain controller. In the audit event, the Member ID field is a combination of the security identifier (SID) of the domain in which the universal group is located and a -0 value. However, you expect the Member ID field in the audit event to use the Domain\User format.

Note The -0 value represents a NULL relative identifier (RID).

The following is an example of the incorrect audit event:

Event Type: Success Audit
Event Source: Security
Event Category: Account Management
Event ID: 660
User: S-1-5-21-2528721576-1674618835-3633233423-1286
Computer: MyComputer
Description:
Security Enabled Universal Group Member Added:
Member Name: CN=User1,CN=Users,DC=contoso,DC=com
Member ID: %{S-1-5-21-2528721576-1674618835-3633233423-0}
Target Account Name: MyGroup
Target Domain: MyDomain
Target Account ID: %{S-1-5-21-2528721576-1674618835-3633233423-13660}
Caller User Name: administrator
Caller Domain: CallerDomain
Caller Logon ID: (0x0,0x17CAD54A)
Privileges: -

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Apply this hotfix on domain controllers that are running Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 1, x64-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the auditing account management feature, visit the following Microsoft TechNet Web site: