a server has been joined to the AD infrastructure and promoted to DC for the specific purpose of recovery of AD objects.
the intention is to configure the replication topology following what seems to be termed as "lazy replication partner" model. to this end the following tasks have been completed; it is connected to a subnet on which there are no other AD hosts a site / subnet has been defined site link linking it to a hub site defined netdiag confirms its site membership the server has been reconfigured with the following registry value - "DNSAvoidRegisterRecords" with the data of "DSACname" - this change is made with the intention of preventing it authenticating any logon requests - this would seem to be an additional step given that site membership should dictate no clients discover it once the server ids fully replicant, the site link has been configured with an extended value of the number of hours but yet the "slow" server is still replicating on the normal frequency it would seem that the "replication topology" has not learnt the configuration of the site link to the slow replication site/server. qu - is this by design and if so do we need to force a refresh of the replication topology - is this what repadmin /kcc does ? GT List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
