Microsoft KB Archive/937855

From BetaArchive Wiki

Article ID: 937855

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems



SYMPTOMS

You delete many Active Directory objects on a Microsoft Windows Server 2003-based domain controller. Then, you perform an authoritative restoration to restore the deleted objects. However, after you perform the authoritative restoration, the linked attributes of some objects are not replicated to the other domain controllers in a linked-value replication (LVR). Instead, these linked attributes remain only on the domain controller on which you performed the authoritative restoration.

For example, when you perform an authoritative restoration to restore deleted group objects, the member attributes of the groups are not replicated to the other domain controllers.

This problem also occurs on global catalog servers. This problem does not occur if the replication model is not the LVR model.

CAUSE

This problem occurs because the linked attributes of an object may be replicated to another domain controller before the object itself is replicated. In this situation, the destination domain controller drops the linked attributes. However, because the update sequence number (USN) vector is updated, the linked attributes will not be replicated again.

RESOLUTION

To resolve this problem, apply the following hotfix to the domain controllers that are changed during the authoritative restoration.

Usually, you cannot determine which domain controllers are changed. Therefore, we recommend that you apply this hotfix to all the domain controllers on which you did not perform the authoritative restoration.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. 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


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 2, x86-based versions
File name File version File size Date Time Platform SP requirement
Ntdsa.dll 5.2.3790.4120 1,525,248 20-Jul-2007 09:02 x86 SP2
W03a2409.dll 5.2.3790.4106 453,632 28-Jun-2007 07:20 x86 SP2
Windows Server 2003 with Service Pack 2, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Ntdsa.dll 5.2.3790.4120 2,969,600 19-Jul-2007 18:35 x64 SP2 Not applicable
W03a2409.dll 5.2.3790.4082 454,144 19-Jul-2007 18:35 x64 SP2 Not applicable
Wntdsa.dll 5.2.3790.4120 1,525,248 19-Jul-2007 18:35 x86 SP2 WOW
Ww03a2409.dll 5.2.3790.4106 453,632 19-Jul-2007 18:35 x86 SP2 WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Ntdsa.dll 5.2.3790.4120 4,259,328 19-Jul-2007 18:32 IA-64 SP2 Not applicable
W03a2409.dll 5.2.3790.4082 452,608 19-Jul-2007 18:32 IA-64 SP2 Not applicable
Wntdsa.dll 5.2.3790.4120 1,525,248 19-Jul-2007 18:32 x86 SP2 WOW
Ww03a2409.dll 5.2.3790.4106 453,632 19-Jul-2007 18:32 x86 SP2 WOW
Windows Server 2003 with Service Pack 1, x86-based versions
File name File version File size Date Time Platform SP requirement
Ntdsa.dll 5.2.3790.2978 1,524,224 20-Jul-2007 08:42 x86 SP1
W03a2409.dll 5.2.3790.2957 28,672 19-Jun-2007 07:30 x86 SP1
Windows Server 2003, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Ntdsa.dll 5.2.3790.2978 2,968,064 19-Jul-2007 18:23 x64 SP1 Not applicable
W03a2409.dll 5.2.3790.2957 29,184 19-Jul-2007 18:23 x64 SP1 Not applicable
Wntdsa.dll 5.2.3790.2978 1,524,224 19-Jul-2007 18:23 x86 SP1 WOW
Ww03a2409.dll 5.2.3790.2957 28,672 19-Jul-2007 18:23 x86 SP1 WOW
Windows Server 2003 with Service Pack 1, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Ntdsa.dll 5.2.3790.2978 4,257,280 19-Jul-2007 18:23 IA-64 SP1 Not applicable
W03a2409.dll 5.2.3790.2957 27,648 19-Jul-2007 18:23 IA-64 SP1 Not applicable
Wntdsa.dll 5.2.3790.2978 1,524,224 19-Jul-2007 18:23 x86 SP1 WOW
Ww03a2409.dll 5.2.3790.2957 28,672 19-Jul-2007 18:23 x86 SP1 WOW


WORKAROUND

To work around this problem, manually export the linked attributes from the domain controller on which you performed the authoritative restoration. Then, import the linked attributes to all the other domain controllers. To perform these operations, you can use the Ldifde.exe tool. For more information about how to use the Ldifde.exe tool, visit the following Microsoft TechNet Web site:

STATUS

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

MORE INFORMATION

Windows Server 2003 introduced a new LVR replication model for linked multivalued attributes. LVR replicates each group member in a separate replication operation instead of replicating the whole group in a single operation. LVR becomes available after the forest functional level is raised to one of the following functional levels:

  • Windows Server 2003 interim
  • Windows Server 2003

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

322692 How to raise domain and forest functional levels in Windows Server 2003


For more information about how to restore deleted user accounts and their group memberships, click the following article number to view the article in the Microsoft Knowledge Base:

840001 How to restore deleted user accounts and their group memberships in Active Directory


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

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



Additional query words: auth-restore linked attribute

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB937855