Scotty said:
If I understand correctly AD will update every 15 minutes.
That is not generally true.
Update what?
Same site or different site?
Are we talking about a WAN here?
Is there any way to change this refresh interval?
For Intersite replication, it is entirely controllable.
If you have a WAN you really should have a SITE
at each location.
InterSite replication is controlled by the admin:
frequency and time of day (also costs)
If you have never setup Sites, you need to do a few
things:
create the sites
create 'subnets' to represent each site and assign them
create at least one Site Link that includes each Site
and allows for 'full connectivity'
On each site link set:
a) cost
b) frequency (default 3 hours last I checked)
c) schedule (default 24 hours, 7 days per week)
move appropriate DCs into their respective sites
Also, when AD updates does it send a lot of
info that might bog down our network?
Usually not. It is very efficient, but it must send the
changes you have made to it since the last update.
A common misunderstanding, even by many near experts
is that delaying updates (less frequent) you cut down
on network usage.
Except for the issue of near empty updates where the
overhead of frequent updates predominates over the
actual (useful) data this isn't generally true.
Sending twice as much data, half as often is more
likely to cause a noticable delay on your network.
The advantage of delaying updates is in avoiding
unnecessary overhead just to say "Nothing much
new" OR in delaying it until a time when the net
is not really in use for other business (night, weekends,
lunchtime, other offpeak times.)
