Hello,

Anybody out there who's an early adopter of .Net with more than 100 sites?

We've got more than 100 sites and are moving towards an AD migration next
year.  We've decided, at Microsoft's recommendation, to go straight to .Net
and it's version of AD.  I've read that the KCC can handle the number of
sites that we have with relative ease.  But I'm still concerned.

We have a hub-and-spoke WAN environment with a single hub and slightly more
than 100 field offices, each of which will be considered a site.  We'll
have four DC's in the hubsite.  We wish to not have to script the creation
of the connection objects and would rather have the KCC do this.  However,
I'm concerned about whether the KCC will make efficient use of the number
of DC's in the hubsite by making them all, or as many as it needs,
bridgehead servers automatically.

It would seem to me that this would work properly, based on Microsoft's
statement that they'll handle many more sites.  I've heard 2000 and 5000
sites stated at different times.  But how does it do this and will it do
what we need?


Any experiences out there yet?  Any thoughts?  The beta site just doesn't
have specific enough information on it yet.


Thanks,
Mike Baudino



******************* PLEASE NOTE *******************
This E-Mail/telefax message and any documents accompanying this
transmission may contain privileged and/or confidential information and is
intended solely for the addressee(s) named above.  If you are not the
intended addressee/recipient, you are hereby notified that any use of,
disclosure, copying, distribution, or reliance on the contents of this
E-Mail/telefax information is strictly prohibited and may result in legal
action against you. Please reply to the sender advising of the error in
transmission and immediately delete/destroy the message and any
accompanying documents.  Thank you.


List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to