The "Automatic disconnect" setting in a WDS multicast transmission does not work in Windows Server 2008 R2

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
  • You install the Windows Deployment Services role on a computer that is running Windows Server 2008 R2.
  • You enable the multicast deployment setting on the Windows Deployment Services server.
  • You enable the Automatic disconnect setting under the Transfer Settings option to disconnect a Windows Deployment Services client when the transfer speed is under a specific value.
In this scenario, some Windows Deployment Services clients are not disconnected when the transfer speeds of the Windows Deployment Services clients is less than the specified value. Additionally, other Windows Deployment Services clients that have a high transfer speed cannot be deployed in the time that is expected.
This issue occurs because Windows Deployment Services incorrectly resets a timer that is used for the Automatic disconnect setting. Therefore, some slow Windows Deployment Services clients are not disconnected. Additionally, this behavior slows down the multicast transmission because a multicast transmission runs as fast as the slowest client.

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


To apply this hotfix, you must be running Windows Server 2008 R2 on the computer. Additionally, the computer must have the Windows Deployment Services role installed.

Restart requirement

You may have to restart the computer after you apply this hotfix.If you stop Windows Deployment Services before you install the hotfix, you do not have to restart the computer.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wdsmcctr.hNot applicable1,14410-Jun-200921:06Not applicable
Wdsmcctr.iniNot applicable4,69810-Jun-200921:06Not applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, 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
For more information about multicast deployments and multicast transmissions, visit the following TechNet Web sites:

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_9f42dbb8adef10f484d8061d2ed396c7_31bf3856ad364e35_6.1.7600.20660_none_b1cde9dd6ff25a37.manifest
File versionNot applicable
File size721
Date (UTC)05-Mar-2010
Time (UTC)10:52
PlatformNot applicable
File nameAmd64_microsoft-windows-d..-services-multicast_31bf3856ad364e35_6.1.7600.20660_none_aa1c7c49f0ec08df.manifest
File versionNot applicable
File size27,178
Date (UTC)05-Mar-2010
Time (UTC)09:00
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,454
Date (UTC)05-Mar-2010
Time (UTC)10:52
PlatformNot applicable

Article ID: 981347 - Last Review: 12/12/2015 03:43:15 - Revision: 1.0

Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard, Windows HPC Server 2008 R2

  • kbnosurvey kbarchive kbfix kbautohotfix kbhotfixserver kbsurveynew kbqfe kbexpertiseadvanced KB981347