The ntdsutil.exe utility in Windows Server 2003 writes out too many links to .ldf files during an authoritative restore process

Consider the following scenario. You use the ntdsutil.exe utility to recover objects or attributes in a Windows Server 2003-based Active Directory forest. When you restore the objects, the ntdsutil.exe utility creates .ldf files. These files are imported into the domains of the forest so that you can obtain all links to the restored objects.

However, when you inspect the .ldf files of the linked objects, you find that the number of links that are restored in an .ldf file exceeds the number of objects that exist in the backup for the corresponding domain. These .ldf files incorrectly include all links, such as the links that have been removed in the tombstone lifetime interval.

In this case, users remain in groups to which they should no longer belong. This may cause a security problem.

When the ntdsutil.exe utility creates the list of the links, the list incorrectly includes the links that have been removed in the tombstone lifetime interval. However, the list should only include the links that actually exist in the backup.

Hotfix information

If you have to run an authoritative restore in an emergency, install the hotfix in DS Restore mode after you restore the system state.

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

To install this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 SP1, x86-based versions

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003 with SP2, Itanium-based versions

Windows Server 2003 and Windows XP, x64-based versions

Windows Server 2003 with SP2 and Windows XP with SP2, x64-based versions

To work around this problem, manually remove the problematic links from the .ldf files.

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

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

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site:

Steps to reproduce the problem

1. Two Windows Server 2003-based domains (domain1 and domain2) exist in a forest. The forest functional level is configured as Windows Server 2003.
2. The user account user1 exists in domain1. The groups, group1 and group2, exist in domain2. The user account user1 is a member of both group1 and group2.
3. You remove the user account user1 from the group2 group.
4. You back up the system state on a domain controller in domain1.
5. You delete the user account user1.
6. You perform an authoritative restore to restore the user account user1 by using the ntdtutil.exe utility. An .ldf file is generated in this process. This file must be imported into domain2.

In the .ldf file, you find that the user account user1 has to be added into group2. This is not expected behavior because user account user1 is removed from the group2 group when you backed up the system state in step 4 on a domain controller in domain1.