A SYSVOL share migration from FRS to the DFSR service fails on a computer that is running Windows Server 2008 if a disjoint namespace is configured in the domain

Article translations Article translations
Article ID: 969688 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You use the DFS Replication service migration tool (Dfsrmig.exe) to migrate the Domain System Volume (SYSVOL share) on a computer that is running Windows Server 2008.
  • You try to migrate the SYSVOL share from the File Replication Service (FRS) to the Distributed File System Replication (DFSR) service.
  • A disjoint namespace is configured in the domain.
In this scenario, the SYSVOL share migration process fails. Additionally, the following DFS Replication error is logged in the DFSR event log:

Log Name: DFS Replication
Source: DFSR
Event ID: 8028
Task Category: None
Level: Error
Keywords: Classic
Description:
DFSR Migration was unable to transition to the 'PREPARED' state for Domain Controller <domain controller name>. DFSR will retry the next time it polls the Active Directory. To force an immediate retry, execute the command 'dfsrdiag /pollad'.

CAUSE

This problem occurs because the SYSVOL migration process from FRS to DFSR incorrectly uses the domain controller DNS name to build an NTFRS SYSVOL junction point name. However, the junction point name does not work in the disjoint namespace.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released 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. The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Dfsrprovs.mofNot Applicable66,51104-May-200907:46Not ApplicableSP1
Dfsrress.dll6.0.6001.224252,04804-May-200910:00x86SP1
Dfsrs.exe6.0.6001.224252,242,56004-May-200910:01x86SP1
For all supported x86-based versions of Windows Server 2008 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Dfsrprovs.mofNot Applicable66,51104-May-200907:45Not ApplicableSP2
Dfsrress.dll6.0.6002.221282,04804-May-200909:49x86SP2
Dfsrs.exe6.0.6002.221282,244,09604-May-200909:50x86SP2
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Dfsrprovs.mofNot Applicable66,51104-May-200907:45Not ApplicableSP1
Dfsrress.dll6.0.6001.224252,04804-May-200910:16x64SP1
Dfsrs.exe6.0.6001.224253,672,57604-May-200910:18x64SP1
For all supported x64-based versions of Windows Server 2008 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Dfsrprovs.mofNot Applicable66,51104-May-200907:45Not ApplicableSP2
Dfsrress.dll6.0.6002.221282,04804-May-200909:56x64SP2
Dfsrs.exe6.0.6002.221283,673,60004-May-200909:58x64SP2

STATUS

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

MORE INFORMATION

A namespace is disjoint when the DNS suffix of the discovered computer differs from the DNS suffix for the domain.
For more information about the disjoint namespace, visit the following Microsoft Web sites:
http://technet2.microsoft.com/windowsserver/en/library/fc16ca97-e86c-417b-a9ed-991e8860969a1033.mspx?mfr=true
http://blogs.technet.com/filecab/archive/2008/02/08/sysvol-migration-series-part-1-introduction-to-the-sysvol-migration-process.aspx
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968733 The SYSVOL share migration from FRS to DFSR fails on Windows Server 2008 R2 Beta-based servers if a disjoint namespace is configured
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 file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_for_kb969688_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,63606-May-200907:28Not Applicable
Package_for_kb969688_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,52606-May-200907:28Not Applicable
Package_for_kb969688_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,70106-May-200907:28Not Applicable
Package_for_kb969688_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,84006-May-200907:28Not Applicable
Package_for_kb969688_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,53006-May-200907:28Not Applicable
Package_for_kb969688_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71206-May-200907:28Not Applicable
X86_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.0.6001.22425_none_9e04b50dc0f09c49.manifestNot Applicable42,65104-May-200914:04Not Applicable
X86_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.0.6002.22128_none_9fee27d3be143d72.manifestNot Applicable42,65104-May-200914:06Not Applicable

Additional files for all supported x64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.0.6001.22425_none_fa235091794e0d7f.manifestNot Applicable42,69104-May-200914:23Not Applicable
Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.0.6002.22128_none_fc0cc3577671aea8.manifestNot Applicable42,69104-May-200913:39Not Applicable
Package_for_kb969688_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,64606-May-200907:28Not Applicable
Package_for_kb969688_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,53606-May-200907:28Not Applicable
Package_for_kb969688_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,71106-May-200907:28Not Applicable
Package_for_kb969688_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,85206-May-200907:28Not Applicable
Package_for_kb969688_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,54006-May-200907:28Not Applicable
Package_for_kb969688_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72206-May-200907:28Not Applicable

Properties

Article ID: 969688 - Last Review: October 7, 2011 - Revision: 3.0
APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard
  • Windows Server 2008 Standard without Hyper-V
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB969688

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com