RIDManager and MachineAccount Failures in DCDIAG

Tech-Archive recommends: Fix windows errors by optimizing your registry

Since Paul Williams suggested I post here about the RID and MachineAccount
failures, I thought I would do so.

I have since moved on with the migration, ignoring the errors raised, and
here is why:

The main thing was which DCDIAG I was using... The one for Windows 2000
showed both the RIDManager and MachineAccount tests failured for the old DC,
but if I ran DCDIAG for Windows 2003 on one of the new DC's, and specified
to run the tests against the old DC using the /S:OLDDC switch, it passed
both tests.

Since I had heard mention that DCDIAG has bugs, and since everything else
seemed to be working OK, I made the 2 new DC's into GC's, and moved the FSMO
roles to the new primary DC.

Once I had configured the various Time Server settings, and created the
LMHOST file on both new DC's so that they recognised the NT4 domain with
which the W2K3 domain has a 2-way trust relationship, I shutdown the old DC
and ran various authentication, resource availability, MSMQ, and other tests
to make sure there wasn't anything specifically using the old DC.

Those all succeeded, so all I have left to do now is complete the migration
of the other W2K servers in the domain, then I can raise the functional
level to native W2K3.

....Andrew


.