5 2008 R2 Domain Controllers across 4 sites
Functional Level 2008 R2
All Global Catalog Servers
I recently had one DC die and had to seize the FSMO roles on another DC then build a new DC to replace the failed one. The new DC has a new name and IP address assigned. Running dcdiag I can confirm that replication is working across all 5 DC's except for one error on the new DC
Starting test: VerifyReferences
Some objects relating to the DC DC3 have problems:
 Problem: Missing Expected Value
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
......................... DC3 failed test VerifyReferences
The article referenced does not apply as the domain was built at 2008 R2 level and DFRS has been in place as far as I know since the beginning (I started with the company after this was in place). No other DC's provide this error. I began digging deeper and upon checking the DFSR Migration state found that DC3 is not in sync. Here are the results from some dfsrmig commands
Current DFSR global state: 'Eliminated'
The following Domain Controllers are not in sync with Global state ('Eliminated'):
Domain Controller (Local Migration State) - DC Type
dc3 ('Start') - Writable DC
Migration has not yet reached a consistent state on all Domain Controllers.
State information might be stale due to AD latency.
Replication Summary Start Time: 2015-04-01 10:10:41
Beginning data collection for replication summary, this may take awhile:
Source DSA largest delta fails/total %% error
dcremoteofc2 06m:43s 0 / 5 0
dcremoteofc1 14m:30s 0 / 5 0
dc1 21m:43s 0 / 10 0
dc2 14m:30s 0 / 15 0
dc3 06m:41s 0 / 5 0
Destination DSA largest delta fails/total %% error
dcremoteofc1 13m:57s 0 / 5 0
dcremoteofc2 04m:25s 0 / 5 0
dc1 14m:31s 0 / 10 0
dc2 21m:45s 0 / 15 0
dc3 03m:38s 0 / 5 0
I found this excellent write up which describes how to migrate
but as I said earlier this is not a migration. DC3 was built to replace a failed dc. DC3 has been in place for about a month now. Has anyone seen this before? Would it be safe to modify the registry key of DC3 to which controls this to '3' which is "Eliminated" state? Should I start the migration process over from the FSMO role holder?
In addition I do not have a share of 'sysvol_DFRS' but only 'sysvol' exists.
I have also attempted to force this by issuing