ollybuba
asked on
FRS DomainControllerName: (null)
I ran dcdiag /c to check the health of my domain. Under VerifyEnterpriseReferences
Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object: CN=server1,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[2] Problem: Missing Expected Value
Base Object: CN=server2,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
LDAP Error 0x20 (32) - No Such Object.
......................... server1 failed test VerifyEnterpriseReferences
I then ran dfsrmig /getglobalstate and noticed that the FRS DomainControllerName was null.
DFSR migration has not yet initialized. To start migration please
set global state to desired value.
C:\Windows\system32>ntfrsu
NTFRS CONFIGURATION IN THE DS
SUBSTITUTE DCINFO FOR DC
FRS DomainControllerName: (null)
Computer Name : server1
Computer DNS Name : server1.domain.local
If anyone could help me with issue that would be great!
Thanks
Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object: CN=server1,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[2] Problem: Missing Expected Value
Base Object: CN=server2,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
LDAP Error 0x20 (32) - No Such Object.
......................... server1 failed test VerifyEnterpriseReferences
I then ran dfsrmig /getglobalstate and noticed that the FRS DomainControllerName was null.
DFSR migration has not yet initialized. To start migration please
set global state to desired value.
C:\Windows\system32>ntfrsu
NTFRS CONFIGURATION IN THE DS
SUBSTITUTE DCINFO FOR DC
FRS DomainControllerName: (null)
Computer Name : server1
Computer DNS Name : server1.domain.local
If anyone could help me with issue that would be great!
Thanks
ASKER
It asks for the DN path of the NTDS Settings object so that would be CN=NTDS-Site-Settings,CN=S
It should be
CN=NTDS Settings,CN=server name,CN=Servers,CN=Site name,CN=Sites,CN=Configura
You can get above DN \ path from AD sites and services\sites\sitename\se
CN=NTDS Settings,CN=server name,CN=Servers,CN=Site name,CN=Sites,CN=Configura
You can get above DN \ path from AD sites and services\sites\sitename\se
ASKER
Do you know where to find this? member object (nTFRSMember) that lacks the settings reference
underneath adsieidt.msc add domain directory partition
There you will find domain controller object underneath below path:
domain.com\system\file replication service\domain system volume
Go to DC object properties (nTFRSMember) and Check ServerReference and frscomputerreference as well
There you will find domain controller object underneath below path:
domain.com\system\file replication service\domain system volume
Go to DC object properties (nTFRSMember) and Check ServerReference and frscomputerreference as well
ASKER
ServerReference looks good but frsComputerReference points to CN=servername,OU=Domain Controllers,DC=domain,DC=l
yes, it is correct
ASKER
So what would be the next step? Poll Active Directory even though nothing changed?
Navigate to domain.com\domain controllers\DC name\NTFRS Subscriptions and go to properties of domain system volume and check frsMemberReference attribute
It should point to:
CN=DC Name,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domai
If above is also correct, what exactly issue you are facing
Are you trying to migrate FRS to DFSR sysvol and facing any issues?
It should point to:
CN=DC Name,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domai
If above is also correct, what exactly issue you are facing
Are you trying to migrate FRS to DFSR sysvol and facing any issues?
ASKER
Yes that was correct. Well previously I have raised the forest functional level from 2003 to 2008. I'm going to moving my AD roles to another server and it said to run dcdiag /c to make sure everything was functioning properly. One of the errors was:
Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object: CN=server1,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[2] Problem: Missing Expected Value
Base Object: CN=server2,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
LDAP Error 0x20 (32) - No Such Object.
......................... server1 failed test VerifyEnterpriseReferences
Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object: CN=server1,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[2] Problem: Missing Expected Value
Base Object: CN=server2,OU=Domain Controllers,DC=domain,DC=l
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
LDAP Error 0x20 (32) - No Such Object.
......................... server1 failed test VerifyEnterpriseReferences
Have you tried the steps in the following Microsoft article on how to recover missing FRS attributes..
http://support.microsoft.com/kb/312862/en-us
http://support.microsoft.com/kb/312862/en-us
Ok
Can you run dcdiag /v on domain controller and paste output here?
Check if AD replication is working fine across both DCs?
Also download Frsdiag utility from MS and check \ test if sysvol shares are working correctly on both DCs
http://www.microsoft.com/en-in/download/details.aspx?id=8613 - Download Link for Frsdiag
Follow below guide to test FRS Sysvol shares with Frsdiag and same guide will help you to migrate FRS sysvol to DFSR sysvol
http://blogs.technet.com/b/askds/archive/2008/05/22/verifying-file-replication-during-the-windows-server-2008-dfsr-sysvol-migration-down-and-dirty-style.aspx
If AD replication and sysvol replication is working correctly, you can straight way go ahead and migrate FRS Sysvol to DFSR Sysvol
Can you run dcdiag /v on domain controller and paste output here?
Check if AD replication is working fine across both DCs?
Also download Frsdiag utility from MS and check \ test if sysvol shares are working correctly on both DCs
http://www.microsoft.com/en-in/download/details.aspx?id=8613 - Download Link for Frsdiag
Follow below guide to test FRS Sysvol shares with Frsdiag and same guide will help you to migrate FRS sysvol to DFSR sysvol
http://blogs.technet.com/b/askds/archive/2008/05/22/verifying-file-replication-during-the-windows-server-2008-dfsr-sysvol-migration-down-and-dirty-style.aspx
If AD replication and sysvol replication is working correctly, you can straight way go ahead and migrate FRS Sysvol to DFSR Sysvol
ASKER
Do I have to migrate from an FRS to DFSR Sysvol to move a PDC?
ASKER
I also ran dcdiag /v /q /f:c:\logfile.txt and the only errors are about redirected printer drivers from the machine I'm RDPing from.
I'm also trying to install adreplstatus and I'm getting an error about Windows Installer:
"The system administrator has set policies to prevent this installation."
I also have no local software restriction policies.
I'm also trying to install adreplstatus and I'm getting an error about Windows Installer:
"The system administrator has set policies to prevent this installation."
I also have no local software restriction policies.
You could use the repadmin command to view AD replication..
http://technet.microsoft.com/en-us/library/cc770963.aspx
http://technet.microsoft.com/en-us/library/cc770963.aspx
ASKER
I ran repadmin /queue and it said that the queue contained 0 items. I also ran repadmin /showrepl and all the times it tried to contact my second dc came back successful.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Everything does replicate but I still receive the errors. I will disregard the errors.
The value for msDFSR-ComputerReferenceBL
Probably its missing, check from adsieidt.msc under domain controllers\domain system volume
You cannot edit this attribute as far as I know
The root cause of this is FRS DomainControllerName was null
In http://support.microsoft.com/kb/312862 article
Find below paragraphs:
Detecting null Server-Reference attributes
Then follow steps mentioned in Repairing the null Server-Reference attributes
Once you cure that again run dfsrmig /GetGlobalState
Probably you can follow then FRS to DFSR guide to migrate FRS to DFSR
Also check below article
http://technet.microsoft.com/en-us/library/dd639789(WS.10).aspx