How NOT to Architect Active Directory
Working in customer support for HP Services, one of the world's biggest computer support companies, I've seen some pretty messed-up Active Directory (AD) designs in my time. In many cases, the design disaster was the work of the nefarious "consultant" who was conveniently unreachable once the network was broke. But even if the AD architect was available, a perception problem exists that can hamper efforts to repair the damage: Some believe that once the AD design is complete and implemented, it's set in stone. That's false: Although it can take significant time, effort and money, implementing a new design is usually possible and sometimes required, if the root cause of the problem is the design itself.(continue at source)








