Microsoft KB Archive/896722

From BetaArchive Wiki

Article ID: 896722

Article Last Modified on 3/23/2007



APPLIES TO

  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition




SYMPTOMS

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.

CAUSE

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.

RESOLUTION

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:

889100 How to obtain the latest service pack for Windows Server 2003


Hotfix information

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
File name File version File size Date Time Platform SP requirement Service branch
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
File name File version File size Date Time Platform SP requirement Service branch
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
File name File version File size Date Time Platform SP requirement Service branch
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


WORKAROUND

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.)

STATUS

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.

MORE INFORMATION

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

824684 Description of the standard terminology that is used to describe Microsoft software updates



Additional query words: kbWinServ2003preSP2fix

Keywords: kbwinserv2003sp2fix kbqfe kbhotfixserver kbbug kbfix kbpubtypekc KB896722