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 (896722)
The information in this article applies to:
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
SYMPTOMSConsider 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. CAUSEThe 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. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required. Restart requirementYou must restart the computer after you apply this hotfix. Hotfix replacement informationThis 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 |
| Ntdsa.dll | 5.2.3790.439 | 1,427,968 | 07-Nov-2005 | 09:48 | x86 | None | RTMQFE | | Ntdsatq.dll | 5.2.3790.439 | 29,696 | 07-Nov-2005 | 09:48 | x86 | None | RTMQFE | | Ws03res.dll | 5.2.3790.439 | 65,536 | 05-Nov-2005 | 00:57 | x86 | None | RTMQFE | | Ntdsa.dll | 5.2.3790.2564 | 1,517,056 | 07-Nov-2005 | 09:57 | x86 | SP1 | SP1QFE |
Windows Server 2003, x64-based versions |
| Ntdsa.dll | 5.2.3790.2564 | 2,951,168 | 07-Nov-2005 | 10:15 | x64 | SP1 | SP1QFE | | Wntdsa.dll | 5.2.3790.2564 | 1,517,056 | 07-Nov-2005 | 10:15 | x86 | SP1 | WOW |
Windows Server 2003, Itanium-based versions |
| Ntdsa.dll | 5.2.3790.439 | 4,058,112 | 07-Nov-2005 | 10:15 | IA-64 | None | RTMQFE | | Ntdsatq.dll | 5.2.3790.439 | 82,432 | 07-Nov-2005 | 10:15 | IA-64 | None | RTMQFE | | Ws03res.dll | 5.2.3790.439 | 65,024 | 07-Nov-2005 | 10:15 | IA-64 | None | RTMQFE | | Wws03res.dll | 5.2.3790.439 | 65,536 | 07-Nov-2005 | 10:15 | x86 | None | WOW | | Ntdsa.dll | 5.2.3790.2564 | 4,242,944 | 07-Nov-2005 | 10:15 | IA-64 | SP1 | SP1QFE | | Wntdsa.dll | 5.2.3790.2564 | 1,517,056 | 07-Nov-2005 | 10:15 | x86 | SP1 | WOW |
WORKAROUNDTo 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.)STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 7/24/2006 |
|---|
| Keywords: | kbQFE kbHotfixServer kbBug kbfix kbpubtypekc KB896722 kbAudITPRO |
|---|
|