Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The SYSVOL share migration from FRS to DFSR fails on Windows Server 2008 R2 Beta-based servers if a disjoint namespace is configured

The SYSVOL share migration from FRS to DFSR fails on Windows Server 2008 R2 Beta-based servers if a disjoint namespace is configured

View products that this article applies to.

Beta Information

This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.

↑ Back to the top

Symptoms

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 R2 Beta-based domain.
  • A disjoint namespace is configured in this domain.
In this scenario, the SYSVOL share migration process fails. Additionally, the following DFS Replication event log file is created after this problem occurs:

↑ Back to the top

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.

↑ Back to the top

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 this specific problem.


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, submit a request to 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.

Prerequisites

This hotfix can be applied on computers that are running Windows Server 2008 R2 Beta.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other 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.
For all supported x64-based versions of Windows Server 2008 R2 Beta
File nameFile versionFile sizeDateTimePlatform
Dfsrprovs.mofNot Applicable74,87619-Mar-200901:25Not Applicable
Dfsrress.dll6.1.7000.41332,04819-Mar-200907:07x64
Dfsrs.exe6.1.7000.41334,421,12019-Mar-200904:52x64

↑ Back to the top

Status

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

↑ Back to the top

More Information

A disjoint namespace means that the Domain Name Service (DNS) suffix of the discovered computer differs from the domain's DNS suffix.


For more information about the disjoint namespace, visit the following Microsoft Web site:
http://technet2.microsoft.com/windowsserver/en/library/fc16ca97-e86c-417b-a9ed-991e8860969a1033.mspx?mfr=true
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

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2 Beta
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.1.7000.4133_none_2eafe243de6fb8ec.manifestNot Applicable35,15319-Mar-200907:45Not Applicable
Package_for_kb968733_sc_0~31bf3856ad364e35~amd64~~6.1.1.0.mumNot Applicable1,67619-Mar-200916:51Not Applicable
Package_for_kb968733_sc~31bf3856ad364e35~amd64~~6.1.1.0.mumNot Applicable1,46419-Mar-200916:51Not Applicable
Package_for_kb968733_server_0~31bf3856ad364e35~amd64~~6.1.1.0.mumNot Applicable1,87819-Mar-200916:51Not Applicable
Package_for_kb968733_server~31bf3856ad364e35~amd64~~6.1.1.0.mumNot Applicable1,45519-Mar-200916:51Not Applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbexpertiseinter, kbfix, kbsurveynew, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 968733
Revision : 2
Created on : 6/12/2017
Published on : 6/12/2017
Exists online : False
Views : 268