The replication may seem like it is serialized when there are slow connections in a DFS Replication configuration in Windows Server 2003 R2

Consider the following scenario.

• In an organization, there is a central office and several branch offices.
• One or more of the connections from the branch offices to the central office is slow, or the bandwidth for the branch office is throttled to a low value.
• All branch offices replicate files to a server at the central office by using the DFS Replication service in Windows Server 2003 R2.
• Files are being replicated from some branch offices to the server at the same time.

In this scenario, replication may seem like it is serialized. The DFS Replication service downloads files from only one branch office whose connection is slow. Other branch offices must wait for this branch office to finish replication. This causes the replication performance to be very poor.

This problem occurs because the DFS Replication service does not efficiently manage resource allocation in this scenario. During the resource allocation process, the DFS Replication service allocates all resources to the slow connection. During this period, the other fast connections have to wait until the resources that are allocated to the slow connection are released.

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 the problem described in this article. 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 be running Windows Server 2003 R2 or Windows Server 2003 R2 Service Pack 2 on the computer. Additionally, the computers must have the DFS Replication component installed.

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

Windows Server 2003 R2, x64-based versions

Windows Server 2003 R2 with Service Pack 2, x86-based versions

Windows Server 2003 R2 with Service Pack 2, x64-based versions

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

This hotfix enables the DFS Replication service to better allocate resources so that the replication on fast connections is not affected by the replication on slow connections.

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