As with most day-to-day administrative tasks , avoiding network downtime is a priority when migrating to Windows Server 2003 and Active Directory. Avoiding end user disruption and network downtime can be accomplished by carefully planning, documenting, and testing the method in which a migration is performed as well as implementing an effective failover plan. To address network downtime, review the Windows Server 2003 Active Directory design and functionality available with Windows Server 2003. Avoiding Downtime Through Server RedundancyOne simple method you can use to leverage Windows Server 2003 functionality and redundancy is to implement redundant domain controllers and global catalog servers in a new active directory domain. You can rely on the secondary server to support the domain in the case of a domain controller failure. Installing an additional domain controller to support redundancy on the Active Directory domain during a migration, even if the domain controller is temporary, can be the difference between an immediate recovery and a complete domain restore. Domain Functional roles can be seized at any point of failure by the secondary domain controller to restore immediately domain functionality and user authentication. Configuring Redundant Global CatalogsBy installing an additional domain controller, you can also configure this system easily to provide additional redundancy by replicating the Active Directory Global Catalog. Configuring this option on a second domain controller will dynamically create a complete redundant copy of the domain's global catalog on the additional domain controller. To configure this option on an additional domain controller, perform the following steps:
For More Information This option can be created as a temporary solution or added into the Active Directory Design. For more information regarding design considerations, review Chapter 10. |