Log in

No account? Create an account
Sep. 18th, 2006 @ 12:53 pm (no subject)
How NOT to architect Active Directory...


Case studies underscoring the importance of good AD design.

From the article:

But rather than using solid, time-tested design principles, Acme came up with the most bizarre solution imaginable. It involved an incredibly obscure tiebreaker rule described on page 166 of the Distributed Systems Guide of the Windows 2000 Resource Kit, that says if the Knowledge Consistency Checker (KCC) has two site links to choose from and both are equal cost, it will break the tie by building a connection to the site with the most domain controllers in it. If both sites have the same number of domain controllers, it selects the site based on alphabetical order. <-- that is NOT good AD design....
About this Entry
new logo
[User Picture Icon]
Date:September 18th, 2006 06:59 pm (UTC)
(Permanent Link)
Fourteen hundred child domains? Shudder...
[User Picture Icon]
Date:September 18th, 2006 07:14 pm (UTC)
(Permanent Link)

I have to wonder whether the consultant was being evil ($$$$) or was just a dumbass.
[User Picture Icon]
Date:September 18th, 2006 07:15 pm (UTC)
(Permanent Link)
Never attribute to malice (or greed) what can be accounted for by stupidity.