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.
Consider the following scenario:
A DFSR replication group is created in a Windows Server 2008 R2 domain.
This domain has two or more domain controllers.
You add a member from another domain to the DFS replication group.
In this scenario, the operation fails and generates the following error message:
The DFS Replication subscriber object cannot be created in Active Directory Domain Services. The parameter is incorrect.
When a cross-domain member is added to a DFSR replication group, the DFS Management MMC snap-in must create Active Directory objects in both domains. In the first step of this process, an Active Directory object is created in the domain that contains the replication group. In the second step, an Active Directory object is created in the domain that contains the added replication member. This second Active Directory object must reference the Active Directory object that was created in the first step.
However, the DFS Management snap-in does not correctly cache domain controller information for the domain that contains the replication group. Therefore, the first Active Directory object is created on one domain controller, and another domain controller is used to query the Active Directory object during the second step. Because the first Active Directory object has not been replicated to the other domain controller, the operation fails.
To fix this problem, apply the following hotfix on Windows Server 2008 R2-based computers that have the DFS Management snap-in installed.
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:
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.
There are no prerequisites for installing this hotfix.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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 R2 file information notes
The MANIFEST (.manifest) files and the MUM (.mum) files that are installed for each environment are listed separately. The 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, whose attributes are not listed, are signed by using a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2