You are currently offline, waiting for your internet to reconnect

Data loss occurs after you use the Dfsrmig.exe tool to migrate the SYSVOL share from the FRS to the DFSR service in a Windows Server 2008-based domain

Consider the following scenario:
  • You use the DFS Replication service migration tool (Dfsrmig.exe) to migrate the SYSVOL share from the File Replication Service (FRS) to the Distributed File System Replication (DFSR) service in a Windows Server 2008-based domain.
  • Some read-only domain controllers (RODCs) exist in this domain.
In this scenario, the Windows NT File Replication Service (NTFRS) subscriptions containers are not deleted on domain controllers in this domain after the migration process. This issue may cause large data loss if all of the following conditions are true:
  • Active Directory is removed from one of the domain controllers in this domain.
  • Active Directory is installed on this same domain controller in another domain.
  • In the new domain, you use the Dfsrmig.exe tool to migrate the SYSVOL share from the FRS to the DFSR replication service. In this case, two junctions point to the same target (%SYSTEMROOT%\Sysvol_dfsr\domain) after the migration.
  • If an administrator finds the redundancy that is triggered by this scenario and deletes the additional junction, all Group Policy objects and scripts in the new domain are deleted on all domain controllers after Active Directory directory service replication.
This issue occurs because the DFS Replication service migration tool (Dfsrmig.exe) does not delete the invalid junction that points to the %SYSTEMROOT%\Sysvol_dfsr\domain folder during the migration process.
To resolve this issue, install hotfix 967326 before you perform a SYSVOL share migration from the FRS to the DFSR service.

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.


There are no prerequisites.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

Windows Server 2008, x86-based version
File nameFile versionFile sizeDateTimePlatform
Dfsrprovs.mofNot Applicable66,51112-Feb-200900:40Not Applicable
Windows Server 2008, x64-based version
File nameFile versionFile sizeDateTimePlatform
Dfsrprovs.mofNot Applicable66,51112-Feb-200900:44Not Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The %SYSTEMROOT%\SYSVOL folder is also re-created on RODCs by the NTFRS subscriptions after the primary domain controller emulator tries to delete the folder during the eliminated phase. This behavior means that two SYSVOL folders (the original SYSVOL folder and the Sysvol_dfsr folder) exist. This problem is also resolved by this hotfix.

Windows Server 2008 includes the Dfsrmig.exe tool. This tool helps administrators migrate the replication of the SYSVOL share from the FRS to the DFSR service. This tool is installed together with the DFSR service.

The Dfsrmig.exe tool is supported only on domain controllers that are running at the Windows Server 2008 domain functional level. This is because SYSVOL migration from the FRS to the DFSR service can be performed only on domain controllers that run on the Windows Server 2008 domain functional level.
For more information, 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
Additional files for all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Package_for_kb967326_sc_0~31bf3856ad364e35~x86~~ Applicable1,63612-Feb-200919:22Not Applicable
Package_for_kb967326_sc~31bf3856ad364e35~x86~~ Applicable1,42212-Feb-200919:22Not Applicable
Package_for_kb967326_server_0~31bf3856ad364e35~x86~~ Applicable1,84012-Feb-200919:22Not Applicable
Package_for_kb967326_server~31bf3856ad364e35~x86~~ Applicable1,43012-Feb-200919:22Not Applicable
X86_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.0.6001.22375_none_9dcea38bc1192ad7.manifestNot Applicable42,65112-Feb-200906:14Not Applicable
X86_microsoft-windows-dfsr-util_31bf3856ad364e35_6.0.6001.22375_none_1638074d8da42912.manifestNot Applicable8,98012-Feb-200906:09Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.0.6001.22375_none_f9ed3f0f79769c0d.manifestNot Applicable42,69112-Feb-200906:49Not Applicable
Amd64_microsoft-windows-dfsr-util_31bf3856ad364e35_6.0.6001.22375_none_7256a2d146019a48.manifestNot Applicable9,01612-Feb-200906:45Not Applicable
Package_for_kb967326_sc_0~31bf3856ad364e35~amd64~~ Applicable1,64612-Feb-200919:22Not Applicable
Package_for_kb967326_sc~31bf3856ad364e35~amd64~~ Applicable1,43012-Feb-200919:22Not Applicable
Package_for_kb967326_server_0~31bf3856ad364e35~amd64~~ Applicable1,85212-Feb-200919:22Not Applicable
Package_for_kb967326_server~31bf3856ad364e35~amd64~~ Applicable1,43812-Feb-200919:22Not Applicable

Article ID: 967326 - Last Review: 10/07/2011 23:07:00 - Revision: 2.0

Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard

  • kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB967326
var m=document.createElement('meta');'ms.dqp0';m.content='true';document.getElementsByTagName('head')[0].appendChild(m);" onload="var m=document.createElement('meta');'ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="">