AD Replication

[Gurvinder nijjar]

We have 1 windows 2000 AD domain. We have 3 sites and each site has its own
subnet. The KDC automatically creates the site links between the sites, so
every site has a replication partner with the other site.

We recently purchased another company and they have their own AD. But now
we want them to be added in our AD domain. as another site and subnet. This
company has hired an external consultant to do this. But what he has done
know is made things worsed. He has made this site a hub and all other sites
a spoke.

So not all sites have replication partners between them anymore everything
goes through this new site 4. The problem we have now is some sites are
replicating and some are not which is causing huge problems.

I want to know go back to the original setup whereby all sites have
replication partners between all other sites.
I dont want to manually add the site links I want them to be automatically
generated. How do I get the KDC to do this or how can i get the sites links
to be automatically generated.

Can anyone please help.

 

[Paul Bergson [MVP-DS]]

You are looking for a mesh topology, the KCC will not generate this for you.
It will determine the best replication topology and lay it out as such. You
can bridge sites though.

Do you have site links set up for all of your sites? It sounds like this
consultant setup site links that all connect back to this remote site. If
you go and recreate the site links to all come back to your site the KCC
should set it up to have your site as the hub.

If you want site A to be the Hub and if you have sites A - E then create
site links as follows.

Site A - Site B
Site A - Site C
Site A - Site D
Site A - Site E

http://support.microsoft.com/default.aspx/kb/199174
http://technet2.microsoft.com/Windo...d167-409b-a8c7-04364964e5e51033.mspx?mfr=true


Why do you say all sites aren't replicating? Have you got errors showing
this?

Run diagnostics against your Active Directory domain.

If you don't have the tools installed, install them from your server install
disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located in the download section on my website at
http://www.pbbergs.com

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.




--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Gurvinder nijjar]

Thanks for that.

What I really want is all sites to have links between each other like site A
connects to all sites and site B connects to all sites and so on.

We have one site link which has all sites as members.

I then go to each DC and under NTDS settings and click new active directory
connection and then type the name of the domain controller on the other
sites. This is the manual way. How can i get this to be setup
automatically generated.

I am worried a

 

[Jorge de Almeida Pinto [MVP - DS]]

We recently purchased another company and they have their own AD. But now

we want them to be added in our AD domain. as another site and subnet

you cannot cut and paste a domain from one forest into another forest. the
only option here is to migrate the stuff from one domain to another. I just
wanted to get that out of the way...

Lets say you have three sites within YOUR company:
LOCATION A with subnet X
LOCATION B with subnet Y
LOCATION C with subnet Z

The network looks like:

LOCATION B-------(WAN)--------LOCATION A-------(WAN)--------LOCATION C

WHAT I would do:
* Create an AD site for LOCATION A called SITE-A
* Create an AD site for LOCATION B called SITE-B
* Create an AD site for LOCATION C called SITE-C

Then I would:
* create a AD subnet called X and link it to SITE-A
* create a AD subnet called Y and link it to SITE-B
* create a AD subnet called Z and link it to SITE-C

Then I would:
* Create an AD site link called SITE-A--to--SITE-B and link SITE-A and
SITE-B to it
* Create an AD site link called SITE-A--to--SITE-C and link SITE-A and
SITE-C to it
* Kick all sites out of the DefaultFirstSiteLink OR if it exists rename it
to one of the site links above instead of creating a new one
* Configure all site links accordingly

Then I would:
* Put/Move the DCs in LOCATION A to SITE-A
* Put/Move the DCs in LOCATION B to SITE-B
* Put/Move the DCs in LOCATION C to SITE-C
* Allow replication to occur or forcing it manually

With this configuration the ISTG (sub-process of KCC) in each site will
create connection objects (COs) for a DC in the corresponding site with the
nearby site, etc, etc.

It has NO added value to create a full mesh replication topology here. An
example of this would be where you also would create a site link called
SITE-C--to--SITE-B and link SITE-C and SITE-B to it. Why is this NOT
logical? If noWAN link exists between location C and location B information
will still go through location A. You get the exact same result WITHOUT that
additional site link.

Now you guys bought some company that has one location. Lets call that
LOCATION D and a WAN link is established between LOCATION A and LOCATION D.

The network would now look:
LOCATION A with subnet X
LOCATION B with subnet Y
LOCATION C with subnet Z
LOCATION D with subnet #

The network looks like:

LOCATION B-------(WAN)--------LOCATION A-------(WAN)--------LOCATION C
|
|
|
(WAN)
|
|
|
LOCATION D

For the additional location I would:
* Create an AD site for LOCATION D called SITE-D
* create a AD subnet called # and link it to SITE-D
* Create an AD site link called SITE-A--to--SITE-D and link SITE-A and
SITE-D to it
* Put/Move the DCs in LOCATION D to SITE-D
* Allow replication to occur or forcing it manually

And THEN I would:
* Migrate all the stuff from the bought company into your company

This is just an example of what we are trying to explain to you....

SO:
* Look at how your network looks like and check if SITES, SUBNETS and SITE
LINKS ate defined correctly accordingly.

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx

 

[Herb Martin]

You are looking for a mesh topology, the KCC will not generate this for you.
It will determine the best replication topology and lay it out as such. You
can bridge sites though.

Paul, "sites" are not bridged, only "sites links" are bridged (grouped),
which
really just makes these links transitive (to the KCC).

Do you have site links set up for all of your sites? It sounds like this
consultant setup site links that all connect back to this remote site. If
you go and recreate the site links to all come back to your site the KCC
should set it up to have your site as the hub.

Good advice...