Re: Site links In a meshed network

If you delete your manually created site links the KCC will regenerate the
best routes for you.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
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.

"Spiff_21" <Spiff21@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D63D48A-E566-43E3-ACAA-CC8FBDB5D74E@xxxxxxxxxxxxxxxx
Thanks. At the moment, the connections under NTDS is a mix of autocreated
connected and manual created connections. In case that that our one
sitelink
is correct, should we do anything about these connections.

"Paul Bergson" wrote:

Geographically your site design makes perfect sense.

I wouldn't create any manual connections, but instead let the KCC
generate
all the connections. If there are connectivity AD is smart enough to
rebuild the connections. This takes time but it is self healing.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
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.

"Spiff_21" <Spiff21@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A858D5EF-705D-495C-A9EF-CF6620BF32A0@xxxxxxxxxxxxxxxx
Geographically does what ??

Could you be a little more specific, about what you would do. I am not
sure
i undestand how you would have the setup. Please have in mind we
already
have
and are using the 4 sites

"Paul Bergson" wrote:

Geographically it does. I would let the KCC do the work for you
though.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
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.

"Spiff_21" <Spiff21@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:63B5BE81-8730-434D-97F6-CB3FD537E02A@xxxxxxxxxxxxxxxx
The all 4 sites are created and are working at the moment. Thrugh
one
sitelink, but Replication to the us site are taking 3 times as long
than
EU
sites. This is Properbly due to slower Connection

The US1 and EU3 are small sites with 20 peeple, and only have one
Doman
controler, EU1 and EU2 are larger with 200 peeple with 2 domain
controlers.
All sites are located in different cityes so i think it makes sence
to
keep
the structure of the sites as they are, we only need to change the
sitelinks.

"Paul Bergson" wrote:

If you want to keep it simple, let the KCC handle everything.
Define
a
US
site and leave the EU site, there is no need to start assigning
costs
since
(From your description) the connectivity is all the same. If a
connection
goes down the KCC will re-assign a new route. I'm not sure how
many
dc's
you have but I would make sure that the US site has two dc's if
there
are
many users. I wouldn't want my fall back going to the EU on a US
dc
failure. You could define multiple static routes between the US
and
EU
but
like the old DNS days you then have to maintain it and your
environment
just
doesn't seem to need any human interaction.

You mention you have 10 meg between EU sites, but that is a
misleading
number. How much traffic is actively occuring has a big impact on
this.
There could be so much traffic that the 1.5 meg connection could
have
a
higher throughput the the 10 meg connections and then you would
want
to
define individual sites for each. As it is now, your US users
could
be
authenticating to any of the EU dc's since you haven't defined your
sites
yet.

This is my opinion and I'm sure others will jump in, but the less
hands
on
you do the easier your maintenance is going to be.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
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.

"Spiff_21" <Spiff21@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C3318B42-DA38-45FA-B6FC-0D455E827FB3@xxxxxxxxxxxxxxxx
I have a network spanning 4 sites, 3 EU and 1 US. All 4 sites are
interconnected by VPN tunnels in a mesh topology. All 3 EU Sites
are
connected to each other by 10 Mbit, and the us site are connected
to
all
sites by 1,5 Mbit. There is no main site, but to of the EU sites
are
larger,
and have secondary domain controlers.

As it is now all sites are connected by a single Sitelink. This
is
wrong
as
the US site don't have the same bandwith

_________EU1 EU1 = 10 MBit
| / | EU2 = 10 MBit
US1 --- EU3 | Eu3 = 10 MBit
| \ | US1 = 1,5 MBit
|_________EU2



As i see it we can do three things. But we need to have in mind
that
is
a
sites fails the replication should still work. so how should i
setup
our
sitelinks ?

also we may need to connect 2 new small US sites

In this case we create a sitelink for each connection. This
results
in
a
many sitelinks, and if we connect 2 extra sites the number of
sitelinks
will
increase rapetly
EU1-EU2 Cost 100
EU1-EU3 Cost 100
EU1-US1 Cost 650
EU2-EU3 Cost 100
EU2-US1 Cost 650
EU3-US1 Cost 650


In this case we have a central EU Site, and create sitelinks from
each
site
in EU to each smaller us site. This results in only 3 sitelinks
pr
site.
EU1-EU2-EU2 Cost 100
EU1-US1 cost 650
EU2-US1 Cost 650
EU3-US1 Cost 650

In this case we have a central EU Site, Then we pick a main site
properbly
the site that have the PDC and the create sitelinks from this
sites.

EU1-EU2-EU2 Cost 100
EU2-US1 cost 650













.

Relevant Pages

  • Re: Site links In a meshed network
    ... US1 site is also a different domain, does this change anuthing in how KCC ... generate the connections if you run the repadmin tool. ... sitelinks. ... EU1-EU2 Cost 100 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Site links In a meshed network
    ... If we only have one sitelink how will KCC know that US1 site is slower? ... generate the connections if you run the repadmin tool. ... sitelinks. ... EU1-EU2 Cost 100 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Site links In a meshed network
    ... the connections under NTDS is a mix of autocreated ... sitelinks. ... EU1-EU2 Cost 100 ... EU2-US1 Cost 650 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Site links In a meshed network
    ... I wouldn't create any manual connections, but instead let the KCC generate ... sitelinks. ... EU1-EU2 Cost 100 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Site links In a meshed network
    ... This is Properbly due to slower Connection ... sitelinks. ... EU1-EU2 Cost 100 ... EU2-US1 Cost 650 ...
    (microsoft.public.windows.server.active_directory)