Off site DC needs to replicate over night only

[Guest]

We have 2 DC in our main site and one DC off site doe Disaster recovery
purposes. I only want users to authenticate to our 2 main DC's only and for
them to replicate at night only to this offsite DC, how can I do this?

 

[Tomasz Onyszko]

We have 2 DC in our main site and one DC off site doe Disaster recovery
purposes. I only want users to authenticate to our 2 main DC's only and for
them to replicate at night only to this offsite DC, how can I do this?

put this off-line DC in separate site - users, should authenticate first
against DC in it's own site. Modify default weight of this DC in SRV
records to make this DC "not attractive" for the users.

And for replication just create appropriate replication schedule.

 

[Guest]

I have created a new site and dragged the DC into it. But can't find the
schedule?

 

[PScyime via WinServerKB.com]

Hi

Replication schedule can be changed in AD Sites and
Services>sites>yoursite>yourserver>ntds>properties of connection > then
"change schedule"

You can pretty muc configure it exactly when you want it

HTH

S

I have created a new site and dragged the DC into it. But can't find the
schedule?

[quoted text clipped - 5 lines]

And for replication just create appropriate replication schedule.

 

[Jorge_de_Almeida_Pinto]

We have 2 DC in our main site and one DC off site doe Disaster
recovery
purposes. I only want users to authenticate to our 2 main
DC's only and for
them to replicate at night only to this offsite DC, how can I
do this?

you could also configure the DC not to register the domain-wide and
the site wide DNS service records and only register its name and IP
and the CNAME record for registration purposes. As Tomasz said, it
works best to put it into its own site. When doing that it is not
needed to put the DC in its own subnet.

* Create an additional site
* Create an additional site link and put the main site and the new
site in it and configure replication cost and schedules accordingly
* Create a 32bits subnet containing the IP address of the DC and a
subnet mask of 255.255.255.255
* Link the subnet to the new site
* move the DC to the new site
* Use a GPO on the new site so the DC does not register the records as
said earlier
* Cleanup DNS records of the DC in DNS in the old site (otherwise
clients might still authenticate to it)
* Do not assign WINS IP addresses to the DC in the new site otherwise
clients (legacy) might find the DC through WINS (1Ch record that
contains all DCs)