AD replication

[Guest]

Hello all:

I understand the concept with AD replication but do not understand one
thing. Why would one want to replicate their changes across the AD network in
durations of one hour or even increments of 15 minutes? I understand for load
balancing, but if I add a user in AD I want that to replicate right away
within seconds. In other words, AD will not let the user sign on until it is
replicated amongst all servers, correct? Well, why would i wait say an hour
for it to replicate when I need the person to sign on the moment I create it?
My problem is is that I want to use AD sites and services but i cannot wait
for a default replciation time of 15 minutes on a site link. I want to add a
user and it replicates right away. I am not worried about traffic and dont
care about costs across our links. How can I make all my stuff replicate the
minute I create or delete something across 6 sites without using the
Replicate Now button.

Any help will work. Thanks.

Jimmy K

 

[Ryan Hanisco]

Some things do replicate immediately, but others are tied to the schedule.
You say that you don't care about the bandwidth and all that, but this is
rarely true. Though if that's the case, put everything in the same site and
it'll use RPC to replicate changes almost immediately.

Generally though, you need to mind replication traffic. In that case, if
you need something to take place immediately, do it on the DC closest to the
needed effect.

 

[Guest]

Some things do replicate immediately, but others are tied to the schedule.
You say that you don't care about the bandwidth and all that, but this is
rarely true. Though if that's the case, put everything in the same site and
it'll use RPC to replicate changes almost immediately.

Generally though, you need to mind replication traffic. In that case, if
you need something to take place immediately, do it on the DC closest to the
needed effect.

--
Ryan Hanisco
MCSE, MCDBA
FlagShip Integration Services
Chicago, IL