The DFS Replication role is also installed when you add the DFS Namespaces role on a Windows Server 2008 R2-based computer


You install the Distributed File System (DFS) Namespaces role on a computer that is running Windows Server 2008 R2. To do this, you use Server Manager, servermanagercmd, pkgmgr, ocsetup, or dism. Then, you find that the Distributed File System (DFS) Replication service is also installed and started. The DFS Namespaces and DFS Replication roles are separate and unrelated components. You expect that the installation of one component will not affect the other component.


The DFS Namespaces servicing manifest packages (MUM) incorrectly include the DFS Replication service role component. For example, see the entries in the following <component> sections:


        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-DFSR-ServerEdition-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="6.1.7600.16385" versionScope="nonSxS"/>

        <assemblyIdentity buildType="release" language="en-US" name="Microsoft-Windows-DFSR-ServerEdition-Deployment-LanguagePack" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="6.1.7600.16385" versionScope="nonSxS"/>

These entries indicate that, when you install DFS Namespaces, the DFS Replication binaries are also installed. However, because the administrator did not select the complete DFS Replication role for installation, the servicing management tools do not show that DFS Replication was installed.


To work around this issue, after you install the DFS Namespaces role, stop the DFS Replication service, and then set the service to disabled.

More Information

This behavior does not occur on versions of Windows Server 2008 that are not R2-based versionsOn the versions that are not R2-based, the servicing MUM files do not contain the entries that are described in the "Cause" section.

Microsoft Internal Support Information

Steps to reproduce.

1. Install a Windows Server 2008 R2 server.
2. Use server manager or servermanagercmd to install only the DFS Namespaces role. Do not select DFS Replication.
3. When the installation is complete, confirm by using servermanagercmd that DFS Replication is not installed:

servermanagercmd -query

[X] File Services  [File-Services]
    [X] File Server  [FS-FileServer]
    [X] Distributed File System  [FS-DFS]
        [X] DFS Namespaces  [FS-DFS-Namespace]
        [ ] DFS Replication  [FS-DFS-Replication]

4. Notice that the DFS Replication service is now installed and running. To verify the status of the DFS Replication service, open services.msc, or run the NET START command from a command prompt.

Note To stop this behavior, you must not edit the MUM file. If you edit the MUM file, this can cause issues later, and such editing is completely unsupported. For more information, visit the following website:

Product Bug Number: WIndows 8 bug 194590
Author ID (email alias): nedpyle
Writer ID(email alias): nedpyle
Tech Review ID (email alias):
Confirm Article has been Tech Reviewed: Yes/No
Confirm Article released for Publishing: Yes/No

Article ID: 2495051 - Last Review: Apr 20, 2011 - Revision: 1