dfsr migration
If you only have 2008 DCs, and you are replicating SYSVOL with FRS. You could/would/should migrate to DFS replication.
Like with any major changes you do to your domain, you should run a dcdiag before you do anything.
I just saw a case where an old Reference was still alive and stalled the migration. The DC (SYSVOL member) was cleaned out long ago, but it looked like it failed removing all traces. The solution was to delete the reference manually with adsiedit.
dcdiag:
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=Win2008-DC01,OU=Domain Controllers,DC=spurs,DC=local 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=Win2000-DC1, OU=Domain Controllers,DC=spurs,DC=local Base Object Description: "DC Account Object" Value Object Attribute Name: serverReferenceBL Value Object Description: "Server Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs Account Object.
Beware that the “VerifyEnterpriseReferences” tested from a Win2008 DC will report back a “Missing Expected Value” for msDFSR-ComputerReferenceBL. This is expected since the 2008 version of dcdiag don’t know that SYSVOL is still replicated with FRS.
So, don’t touch DFSR references.
Migrating step-by-step: