Re: add a new 2003 server to domain as DC

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

just follow "Q216498:How to remove data in Active Directory after an
unsuccessful domain controller demotion", checked all mentioned entries
with "metadata cleanup" and adsiedit again, but cannot find any
suspicious entries except references to these two actual servers? but
tried a thothrough diagnosing with dcdiag.exe, the situation looks
better, some warning/failures no more there but point to replication
and dns name problem(?):

failures reported on current PDC:
-- frsevent SYSVOL replication failure
-- VerifyReferences and VerifyEnterpriseReferenc missing expected
value failure(frsComputerReferenceBL,serverReferenceBL)

failures reported on new joined DC:
-- NetLogons not shared (as noticed, after added DC Role with dcpromo,
NTDS, SYSVOL folders are created but cannot get synchronized with PDC,
also not get shared automatically)
-- Advertising DsGetDcName error (?? have configured both server also
as DNS server and use own server but with replication)
-- VerifyEnterpriseReferenc failure similiar to PDC

all other tests have get through.

have checked Q312862 but havent really get a idea how to fix these
"Missing Expected Value" problem....can someone give me a clue, what
should I edit to fix these several value problems with adsiedit? could
this maybe the first key start to solve my problem?

will try dcpromo /forceremoval once to surely remove new DC from domain
and clean up with metadata and adsiedit tool, diagnose current PDC,
also be sure that current PDC running without any problem before add
another server as DC?

any help would be very appreciate,

Paulo

.

Quantcast