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:
C:\Windows\servicing\Packages
Microsoft-Windows-DFSN-Server~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.mum
Microsoft-Windows-DFSN-Server~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
<component>
<assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-DFSR-ServerEdition-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="6.1.7600.16385" versionScope="nonSxS"/>
</component>
<component>
<assemblyIdentity buildType="release" language="en-US" name="Microsoft-Windows-DFSR-ServerEdition-Deployment-LanguagePack" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="6.1.7600.16385" versionScope="nonSxS"/>
</component>
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.