Domain controllers receive a security descriptor for an object that does not match the security descriptor from the Windows Server 2003-based domain controller where the object was created

Consider the following scenario:

• You create a new object in the Active Directory directory service.
• You create the object in one container on a Microsoft Windows Server 2003-based domain controller.
• This domain controller has additional writeable Active Directory domain controllers for the naming context in the same site.
• You move the object to a different container some seconds after you create the object.

In this scenario, some domain controllers eventually receive a security descriptor for the object that does not match the security descriptor from the domain controller where the object was created. The security descriptor does not reflect the inherited security from the new parent container.

The object is moved and replicated shortly after you create it. However, the security descriptor propagator (SDPROP) on the domain controller that replicates the changes may not run for this new object. Therefore, the security descriptor for the object is incorrect.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 this specific problem. 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

No prerequisites are required.

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 tool in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

To work around this issue, change the discretionary access control list (DACL) of a parent object so that SDPROP is invoked and re-applies inherited security. If you have examined the security descriptor and know the objects that do not have the correct security, you can also change the security descriptor for these objects. For example, you can toggle the Inherit from parent the permissions that apply flag. (This flag corresponds to the DSACLS /P option.)

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

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