MemberName attribute and Account Name field are not populated in a Windows Server 2008 R2-based domain

Applies to: Windows Server 2008 R2 DatacenterWindows Server 2008 R2 EnterpriseWindows Server 2008 R2 for Itanium-Based Systems More

Symptoms


When you remove a member of a Global or Universal security group on a Windows Server 2008 R2-based domain controller, the MemberName attribute and the Account Name field are not populated in the security audit events. This problem occurs when you take any of the following actions:
  • You remove the member by using the user's security identifier (SID).
  • You remove the member from a group by using the Active Directory Administrative Center.
  • You remove the member by using the Remove-AdPrincipalGroupMembership Windows PowerShell cmdlet.

For example, you start the Active Directory Module for Windows PowerShell. To remove the user account "Audit1" in the Group1 Global security group, you use one of the following commands together with either the user's SID or the user's name:

PowerShell command using the users SID

PowerShell command using the users name

In this scenario, when you use either command, the MemberName attribute is not populated and is instead displayed as a dash (-) on the Details tab of the Event 4729 log. Additionally, the Account Name field is not populated and is instead displayed as a dash (-) on the General tab. The results are shown in the following screen shots.

The MemberName attribute is not populated and is displayed as a dash (-).

The Account Name field is not populated and is displayed as a dash (-).

Notes
  • This problem does not occur with the Domain Local group. The event always shows the MemberName attribute as the distinguished name, even if the removal is performed by using the member SID.
  • This problem can also occur in the Event ID 4757 log for the Universal group.

Cause


This problem occurs because the Windows PowerShell command uses the user's SID when the request is sent by using the Lightweight Directory Access Protocol (LDAP) regardless of whether the identity is passed as a distinguished name.

Resolution


Hotfix information

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, go to the following Microsoft website: 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

To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1) .

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


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