Archived from groups: microsoft.public.win2000.active_directory (
More info?)
There's a book that may come in handy -in fact, Herb may have been one of
the authors, it's called Managing Enterprise Active Directory
Services -Notes from the field (or something like that. It's a notes from
the field book written by MS Consulting). This goes into all this in quite
some depth, I believe.
Then again, you've been given a pretty good summary, and the only real way
from here on is to test and test again. There is however, a free tool
called the AD Sizer which may be able to help you. Search MS (using Google
;-) for that.
--
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
"TrutweinA" <TrutweinA@discussions.microsoft.com> wrote in message
news:766DDAB7-8DEA-4D1B-B96F-1535671DCC41@microsoft.com...
Cool thanks for that... yeah my teachers at school said that I was a bit
geographically challenged!!!
"Herb Martin" wrote:
> > implemented SMTP style replication before as we had a country in Bahrain
> > using a 64KB sat link... it works, but its a pain in the a55 to setup
> > and
> get
> > working correctly.
>
> Gosh I am glad you mentioned Bahrain and
> Kazakhstan -- Since you claimed a 100+
> pan-European deployment and there aren't
> that many countries IN EUROPE, I was
> beginning to suspect a bogus post <grin>
>
> > Point taken about transmission errors and other overheads. Is there any
> > point to which RPC errors will just fail and totally stop sending, if it
> > can't send the info in 1MB chunks? Or will it continually keep on
> > trying
> > until it does send the info or doesn't?
>
> There is no "technical limit" if the RPCs
> work and that HAS worked down to 9600
> bps on high quality, low latency (probably
> only dedicated/pinned) lines.
>
> At you your 64kbs (available?) you will get
> through most of the time (which is probably
> good enough) IF the lines are good enough
> but you still have to test.
>
> > Granted testing will need to be completed to find out the true nature of
> > link speeds, over heads and the testing of the AD replication.
> >
> > I would have thought Microsoft would have produced some documentation as
> to
> > what a minimum or recommended link speed would be to transfer AD
> replication
> > though? But I guess this does have quite a lot of dependencies
>
> They have; it's all over the web site and in
> several MS Press books -- however, I gave you
> a rough summary of that and a bit of experience
> but nothing like 100 countries across Eurasia
> including the Middle East.
>
>
>
> --
> Herb Martin
>
>
> "TrutweinA" <TrutweinA@discussions.microsoft.com> wrote in message
> news:AA65A09D-7106-4C7A-B388-DA0D6AF3D098@microsoft.com...
> > Thanks for your posts... I am currently working with the US on this and
> they
> > have final say so on the design and we have been told that there can be
> only
> > 1 domain for EMEA (the design is not just Europe now...!). I have
> > implemented SMTP style replication before as we had a country in Bahrain
> > using a 64KB sat link... it works, but its a pain in the a55 to setup
> > and
> get
> > working correctly.
> >
> > The types of links that i'm thinking is probably going to be 64KB links
> > or
> > worse to countries like Kazakhstan.
> >
> > Point taken about transmission errors and other overheads. Is there any
> > point to which RPC errors will just fail and totally stop sending, if it
> > can't send the info in 1MB chunks? Or will it continually keep on
> > trying
> > until it does send the info or doesn't?
> >
> > Granted testing will need to be completed to find out the true nature of
> > link speeds, over heads and the testing of the AD replication.
> >
> > I would have thought Microsoft would have produced some documentation as
> to
> > what a minimum or recommended link speed would be to transfer AD
> replication
> > though? But I guess this does have quite a lot of dependencies
> >
> > Thanks
> > Adam
> >
> > "Gary Simmons" wrote:
> >
> > > Hi..
> > >
> > > Yes fair comment on the GC over SMTP, however I'm yet to come across
> > > any environments that actually use SMTP for replication - so the point
> > > was easily missed..
> > >
> > > In order to authticate correctly a home DC is required - GC on its
> > > own is not enough.. GCs dont hold Domain Local Groups, so any AGLP
> > > nesting would not be fully satisified if only a GC from a foreign
> > > domain is used for authtication.. The GC requirement is there in
> > > order to resolve Universal Group memberships..
> > >
> > > Oh yes and I do mean Killer for RPC
> > >
> > > Cheerio
> > > Gary Simmons
> > >
> > > gsimmons.uk@gmail.com
> > >
> > > On Tue, 4 Jan 2005 22:04:47 -0600, "Herb Martin" <news@LearnQuick.com>
> > > wrote:
> > >
> > > >"Gary Simmons" <gsimmons.uk@gmail.com> wrote in message
> > > >news:g3rlt0p8050eeonedvope134iod4n2ladr@4ax.com...
> > > >> Latency is the filler for Domain NC replication..
> > > >
> > > >Is that killer? (I agree).
> > > >
> > > >Also noise/errors on the line. RPC don't recover
> > > >errors well.
> > > >
> > > >> If you use SMTP replication it will only replicate Schema and
> > > >> Config
> > > >> NC, so you are going to need to use multiple domains ie one for
> > > >> each
> > > >> site you create..
> > > >
> > > >As I mentioned, it will require a separate domain
> > > >across any link (to a location) which uses SMTP.
> > > >
> > > >GCs can however replicate across this:
> > > >
> > > >Google: [ gc "replication * smtp" | "smtp * replication" domain
> forest ]
> > > >
> > > >> However in doing so you will constrain users from logging into
> > > >> their
> > > >> own site only, as the potential WAN speeds between each site (as u
> > > >> indicate) will be low so cross iste authentication will be very
> > > >> slow.
> > > >
> > > >If you replicate the GC it should allow for the login.
> > > >
> > > >
> > > >> Even with one domain per site model you still will get RPC
> replication
> > > >> happening for GC replication between the domains, which could be
> large
> > > >> with many domains..
> > > >
> > > >See above...
> > > >
> > > >
> > > >> As indicated you need to test this out in order to understand where
> > > >> the balance in replication against availability is..
> > > >
> > > >Yes, testing is definitely in order -- very few people
> > > >have actually used SMTP replication in serious
> > > >production settings.
> > > >
> > >
> > >
>
>
>
Facebook
Twitter
Instagram