The "Dfsutil /import" command takes a long time to finish when you try to import DFS links to a stand-alone DFS root on a Windows Server 2003-based computer

Consider the following scenario:

• You are running the Distributed File System (DFS) service on a Microsoft Windows Server 2003-based computer.
• You run the Dfsutil /import command on this computer to import DFS links from a metadata file to a stand-alone DFS root (namespace).

In this scenario, the command takes a long time to finish. For example, this problem occurs when you run the following command to import DFS links:Notes

• In this command, dfsRootName represents an existing DFS root to which you want to import DFS links
• In this command, FileName represents the name of the metadata file.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this problem, apply the hotfix that is mentioned in this article, change the DfsSkipResync registry entry to a value of 1 (one), and then run the Dfsutil /root command. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then right-click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfs\Parameters
3. Point to New, and then click DWORD Value.
4. For the registry entry name, type DfsSkipResync. Then press ENTER.
5. Double-click the DfsSkipResync registry entry that you created in step 4.
6. Enter 1 in the Value Data box.
7. Click OK.

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

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer. For more information about how to obtain the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

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

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

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

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