Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2560
  • Last Modified:

Migrating from SBS 2008 to SBS 2011: DCDIAG Errors

Experts,

I am migrating from SBS 2008 to SBS 2011, following the instructions provided in Microsoft's document "Migrating to SBS 2011 Standard from SBS 2008".
On beforehand, I checked that there were no problems in the source server's event logs, and that the SBS 2008 Best Practice Analyzer reported no problems.
The new server is installed and joined to the domain, and I am about to start with the Exchange migration. At this point, the migration document recommends that I run DCDIAG and correct any problems there first.

DCDIAG then reported the following errors:

 Starting test: NCSecDesc
 Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set  access rights for the naming context:
DC=ForestDnsZones,DC=mydomain,DC=local
 Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access rights for the naming context:
 DC=DomainDnsZones,DC=mydomain,DC=local
 ......................... MYSERVER failed test NCSecDesc

...and also,

Starting test: FrsEvent
         There are warning or error events within the last 24 hours after the  SYSVOL has been shared.  Failing SYSVOL replication problems may cause  Group Policy problems.
         ......................... MYSERVER failed test FrsEvent

I read somewhere that the first error could be fixed by giving ENTERPRISE DOMAIN CONTROLLERS the appropriate rights in ADSI EDIT, which I did, but the errors still persists. Somewhere else I also read that the NCSecDesc error could be ignored unless I was planning to add a RODC.

Should I be concerned with these errors? Or will they disappear when the migration is complete and the source server is demoted and disconnected?
0
Dataing
Asked:
Dataing
  • 2
  • 2
1 Solution
 
Darius GhassemCommented:
Here is a link about the first error

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_3645-Dcdiag-fails-for-NCSecDesc-test-on-Windows-2008-Domain-Controllers.html

I would monitor the SYSVOL error but this could be an old error but everything is working fine.

Run repadmin /syncall
0
 
ronnypotCommented:
About the sysvol message take a look at the file replication event log.

I have put some common sysvol errors together in a blog post, maybe this will help you http://blog.ronnypot.nl/?p=738

Ronny
0
 
DataingAuthor Commented:
Thanks for your reply!
I ran the repadmin /syncall command, and here is the output:

C:\Windows\system32>repadmin /syncall
CALLBACK MESSAGE: The following replication is in progress:
    From: 924b96ac-b458-4be1-a62a-c0bf950ba2b3._msdcs.MyDomain.local
    To  : 53b1988b-1b0a-4694-a1e2-e012f8c40ed1._msdcs.MyDomain.local
CALLBACK MESSAGE: The following replication completed successfully:
    From: 924b96ac-b458-4be1-a62a-c0bf950ba2b3._msdcs.MyDomain.local
    To  : 53b1988b-1b0a-4694-a1e2-e012f8c40ed1._msdcs.MyDomain.local
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.

DCDIAG now only reports one error, the one about NCSecDesc.

So this is to say that I can ignore the NCSecDesc error and go on with the migration tasks?
0
 
Darius GhassemCommented:
You can ignore the error. Everything looks good
0
 
DataingAuthor Commented:
That's great, then I'll go on with the migration. Thanks!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now