I am not planning on using RODCs, and so I did not do the adprep switch for RODC prep (I figure the less you mess with the schema, the better). However, after bringing my first win2008 DC up, I noticed that DCDIAG would fail the NCSecDesc part of the win2008 dcdiag. Interestingly, this test passed when running the win2003 dcdiag. The 2008 dcdiag.exe would fail this test whether I pointed it at the new win2008 dc or my old win2003 dc. The 2003 dcdiag.exe would pass this test regardless of which server it pointed to. Odd!
Googling wasn't any help because every single post regarding the NCSecDesc error has to do with people installing exchange 2003 in a domain/forest with win2000 DCs. No help!
Finally I dug deep into technet and found the following:
If you have not run adprep /rodcprep, Dcdiag.exe returns an error when it runs the NCSecDesc test. This test checks that the security descriptors on the naming context heads have appropriate permissions for replication. The error indicates that the Enterprise Domain Controllers group does not have Replicating Directory Changes In Filtered Set access rights for the DNS application directory partitions. If you do not plan to add an RODC to the forest, you can disregard this error. If you plan to add an RODC to the forest, you must run adprep /rodcprep.
Wes, I would strongly consider running the update. If done properly, schema updates are a breeze. Also, I suspect that AD-aware apps -- like DCDIAG -- are going to assume that you're RODC-aware.