Two DCs - Schema replication result with repadmin - Last Attempt @ (never) was successful



Hi. We currently have a single domain with one DC (Windows 200 Srv Std) and
are currently in the process of upgrading to 2003 R2 Ent. We have added a
second DC with 2003 R2 Ent and there have been no unexpected errors in the
Event Logs (just the expected replication notifications etc), no errors in
DCDiag and similarly no obvious errors in repadmin. On running "repadmin
/showrepl /all /verobose [DCName]" against the original 2000 DC all entries
for inbound and outbound neighbours have successful replication results and
valid times. But, on running the same command against the new 2003 DC all
inbound and neighbours have similar results apart from
"CN=Schema,CN=Configuration,DC=domain,DC=local" which has the result "Last
attempt @ (never) was successful".

I have searched online and found some documentation and postings with this
same entry but have not been able to determine whether this is an acceptable
result or whether this should have been replicated and therefore if we have
a problem to resolve before we continue. Just in case this has any
relevance the original 2000 DC with all successful results is currently
holding all 5 FSMO roles, both DCs are GC. We were planning on transferring
the FSMO roles to the new DC, demoting the 2000 DC to a member server and
replacing it with a new 2003 R2 Ent server with the same name, dcpromo that
to a DC with GC and eventually transfer the FSMO roles back.

Can anyone give me any advice regarding this repadmin entry and what if we
need to take any action ?

Thanks for any help,

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question