Windows 2003 bridge head servers

[Charlie]

I know this is a windows 2000 forum but I didnt see one
for windows 2003. I need confirmation on bridgehead
servers in windows 2003. In windows 2000 the bridgehead
server if manully defined had to be from the same domain
since only DC's from the same domain replicate the domain
partition. If you have multiple domains in windows 2003
has this changed. I know windows 2003 GC have changed
some but they are still only read only copies so I would
think the bridgehead server for a site would still need to
be from the same domain.

 

[Herb Martin]

I know this is a windows 2000 forum but I didnt see one
for windows 2003.

They are call microsoft.public.windows.server (.etc)

Yes, it's confusing. I really wish that the Microsoft newsgroups
would just have a Server.CurrentVersion (.etc) but they don't.

Don't worry about it too much -- you might get better help in
correct forum but generally if you specify your OS someone will
help you or direct you there.

I need confirmation on bridgehead
servers in windows 2003. In windows 2000 the bridgehead
server if manully defined had to be from the same domain
since only DC's from the same domain replicate the domain
partition.

Well, yes, but if multiple domains are involved you need to
make sure that BOTH have bridgehead servers available at
each (relevant) site.

Also note that GCs need to be among the bridgehead servers.

GCs set up a parallel replication topology for the FOREST.

If you have multiple domains in windows 2003
has this changed. I know windows 2003 GC have changed
some but they are still only read only copies so I would
think the bridgehead server for a site would still need to
be from the same domain.

Or all domains need one (or more.)

My only REAL criteria for picking bridgehead servers manually
is to allow them to be TIGHTLY FILTERED over firewalls.

Since each "pair of potential" bridgehead servers need two (or
more) sets of filters, the number of filters grows exponentially
as the number of potential bridgehead servers.
[/QUOTE]

 

[charlie]

Thanks for the reply. I was pretty sure this had not
changed. Although the parrallel replication for GC might
have according to windows 2003 resources documentation.
Still good ideal to have GC as bridgheads but according to
the site listed below windows 2003 in full 2003 functional
mode might have improved parrallel replication for GC. Id
be interested in seeing what you got out of it if you have
time.

http://www.microsoft.com/resources/documentation/WindowsSer
v/2003/all/techref/en-us/Default.asp?
url=/resources/documentation/windowsServ/2003/all/techref/e
n-us/w2k3tr_repup_tools.asp

-----Original Message-----


They are call microsoft.public.windows.server (.etc)

Yes, it's confusing. I really wish that the Microsoft newsgroups
would just have a Server.CurrentVersion (.etc) but they don't.

Don't worry about it too much -- you might get better help in
correct forum but generally if you specify your OS someone will
help you or direct you there.


Well, yes, but if multiple domains are involved you need to
make sure that BOTH have bridgehead servers available at
each (relevant) site.

Also note that GCs need to be among the bridgehead servers.

GCs set up a parallel replication topology for the FOREST.


Or all domains need one (or more.)

My only REAL criteria for picking bridgehead servers manually
is to allow them to be TIGHTLY FILTERED over firewalls.

Since each "pair of potential" bridgehead servers need two (or
more) sets of filters, the number of filters grows exponentially
as the number of potential bridgehead servers.

.
[/QUOTE]

 

[Herb Martin]

Thanks for the reply. I was pretty sure this had not
changed. Although the parrallel replication for GC might
have according to windows 2003 resources documentation.
Still good ideal to have GC as bridgheads but according to
the site listed below windows 2003 in full 2003 functional
mode might have improved parrallel replication for GC. Id
be interested in seeing what you got out of it if you have
time.

http://www.microsoft.com/resources/...2003/all/techref/en-us/w2k3tr_repup_tools.asp

Maybe that link is general rather than specific as I didn't
initially find much relevant to our discussion.

Could you give me some relavent, clear text for which to search,
then I can find it even if it's on another page.

--
Herb Martin

.

[/QUOTE]

 

[Cary Shultz [A.D. MVP]]

Charlie,

I am going to jump in for a second and restrict my comments to three points:
the partitions in AD replication, AD replication and Bridgehead servers ( in
WIN2000 ).

The Partitions - there are three partitions, or Naming Contexts, in Active
Directory replication: the Schema Partition, the Configuration Partition and
the Domain Partition. Both the Schema and Configuration Partitions are
replicated to all Domain Controllers in the entire AD Forest. However, only
the Domain Controllers in the same domain receive the Domain Partition. So,
if you had three domains only the DCs in domain1 would receive the Domain
Partition for that particular domain while only the DCs in domain2 would
receive the Domain Partition for that particular domain as would only the
DCs in domain3 receive the Domain Partition for that particular domain.

I am sure that this is all very clear to you but just to be on the safe
side.


AD replication - there are two types: Intrasite and Intersite. Since we are
talking about BHS we will concentrate on Intersite replication. As I am
sure that you know, when you have a domain that spans several Sites ( as
created in Active Directory Sites and Services ) within each Site you have
your normal Intrasite AD replication. This is all clear. But, in order for
the DCs in each Site to be able to replicate with the DCs in the other Sites
we have Intersite replication. As I am sure that you are aware, a DC in
each Site is ( typically ) designated as a BHS. It is actually the BHSs
that do the Intersite replication. So, the BHS in Site1 is the replication
partner for the BHS in Site2. There may well be several DCs for each Domain
in each Site. However, it is only the BHS from each Domain that will be the
replication partner for the BHS in the other Site(s). And, just to refresh,
all replication is based on incoming connection objects.


Bridgehead Servers ( BHS ) - are typically the designated domain controller
( via the KCC ) from each site that will be responsible for Intersite
replication. However, you may decide that it better suits your needs to
manually select the DC(s) from each domain in the Site to play the role of
preferred BHS. Typically you need to be careful when doing this. Please
take a look at the following MSKB Articles:

http://support.microsoft.com/?id=271997

HTH,

Cary