You have a domain that uses Distributed File System (DFS) replication to replicate the Domain System Volume (SYSVOL share).
You prompt a member server that is running Windows Server 2008 R2 to a read-only domain controller (RODC) in the domain.
You run the Dcdiag.exe utility on the RODC.
In this scenario, the VerifyReferences test fails. Additionally, the following message is logged:
Starting test: VerifyReferences Some objects relating to the DC <DC name> have problems:  Problem: Missing Expected Value Base Object: CN=<DC name>,OU=Domain Controllers,DC=<domain name> Base Object Description: "DC Account Object" Value Object Attribute Name: frsComputerReferenceBL Value Object Description: "SYSVOL FRS Member Object" Recommended Action: See Knowledge Base Article: Q312862 ......................... 28-1205B710A failed test VerifyReferences
DFS replication creates the DFSR-LocalSettings object for the new RODC during the first restart after the promotion. Because the new RODC cannot create the object locally, the RODC targets any writable domain controllers to create the object and to set the msDFSR-Flags property. If the DFS replication service creates the object on a domain controller and then tries to set property of the object on another domain controller, the object is not replicated to this domain controller. Therefore, the setting operation fails, and this issue occurs.
To resolve this issue, install the hotfix on all Windows Server 20008 R2-based domain controllers in the affected domain.
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 website:
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.
To apply this hotfix, you must be running Windows Server 2008 R2.
To use the hotfix, you do not have to change the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-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.
For more information about the Dcdiag.exe command-line tool, visit the following Microsoft website: