AD Replication: Wrong Bridgehead?? Help?

I started a large NT 4.0 to 2K3 AD migration last week. All went well
but I noticed something and it confuses me. After migrating my first
site to AD, the sites bridgehead isn't what I expected. Let me give
some environment details first.

Design is hub and spoke, single domain. The Hubs host datacenters in
Chicago and Nashville. Both hub sites have 2 WIN 2K3 AD DC's. We have
50 sites to migrate and plan to equally distribute site links between
each of the 50 and the 2 hub sites. Each remote site has 1 DC / file
server which will replcicate with the hub DC's. In migrating this
site, I created the site link with just the remote site (Indy) and
Chicago. Next will do the same and as we go, we again distribute the
site links so that each hub site has about 25 remote sites to replicate
with. After I created the site link with Chicago and Indy I noted that
the Indy DC is replicating with a DC in the Nashville hub site??? If I
go in Sites and Services for the Indy site and check the NTDS settings
and look where it says 'replicate from' - it lists a Nasville DC. This
Nashville DC is not even in the site link. I thought replication was
based on the info in my site links? So I am confused. The Nasville
site was the default first site. I know I can change it but
replication seems to be happy. Shoudl I? Is it because it's a single
domain? Like maybe the KDC just choose that Nasvhille server to be the
bridgehead??

Thanks for any info-

.

Relevant Pages

  • Re: How do I restrict NTDS Replication in Active Directory to specified Domain Controllers
    ... Verify that all site links are created correctly. ... For each branch you should have a separate site link containing only the hub and the branch sites. ... How do I keep the domain controllers at the individual branches from ... I want them all to replicate ...
    (microsoft.public.windows.server.networking)
  • Re: AD Replication - Question about auto-generated replication connections
    ... subnets and site links are correctly configured. ... that configuration should replicate to all DCs and the KCC on each DC for ... shouldn't they only replicate with each other? ... We've migrated about 10 and each remote site has 1 AD DC. ...
    (microsoft.public.windows.server.active_directory)
  • Re: KCC error 1311 - Windows 2003 network
    ... I un-checked the Bridge Site Links box, KCC would try to automatically create ... DCs that are GCs may need to replicate partitions for DCs within ... It will then replicate in a hub and spoke topology where A is your hub. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Please Clarify
    ... And I agree with you and Paul, that a star (hub and spoke) would work. ... Bridge all Site links is enabled. ... replication topology you have described manually configured by ... Second, knowing that the FSMO role is at site A, should I assume that ...
    (microsoft.public.windows.server.active_directory)
  • Re: Please Clarify
    ... And I agree with you and Paul, that a star (hub and spoke) would work. ... Bridge all Site links is enabled. ... replication topology you have described manually configured by ... Second, knowing that the FSMO role is at site A, should I assume ...
    (microsoft.public.windows.server.active_directory)
Loading