© 2004 Mustan Bharmal. All Rights Reserved.
•
The migration of directory service components of each in-scope legacy domaininfrastructure, and not the migration of other components listed below as out of scope.
•
The execution of inter-forest or intra-forest migration exercises to consolidate superfluousWindows Server 2003 domains / forests into one or a fewer number of Windows Server 2003 domains / trees / forests within the organisation where:
♦
The in-place upgrade of one or more legacy Windows NT 4.0 and / or Windows 2000domain infrastructures generated the superfluous Windows Server 2003 domains /trees / forests, or
♦
The execution of consolidation exercises legacy Windows NT 4.0 and / or Windows2000 domain infrastructures generated the superfluous Windows Server 2003 domains/ trees / forests.
1.2.2.Out-of-Scope Components
This design methodology does not provide support for any other components and aspectstypically associated with a migration from one or more legacy domain infrastructures to aWindows Server 2003 Active Directory infrastructure that do not comply with the above in-scope criteria. This hence includes, for example, the following components as been outside of the scope of this migration plan:
•
The migration of member servers and clients operating legacy Windows operating systems(Windows 2000 or earlier)
•
The migration of applications, services, resources on member servers and clients withineach in-scope legacy domain infrastructure
•
The migration of other directory service infrastructures within an organisation to the newproposed Windows Server 2003 Active Directory infrastructure, such as legacy MicrosoftExchange 5.5 infrastructures
•
The migration of infrastructure services (DNS, WINS, DHCP, and so on) operating withinthe legacy domain infrastructures (note that the design of a migration from a legacy /existing DNS infrastructure is supported by the Organisation-Wide Active Directory Planprocess “design of a DNS infrastructure”)
•
The execution of gap analysis for legacy domain controller server hardware (this issupported by the Domain Plan process “design for domain controllers”)
•
The requirements to migrate from the following third party network operating systeminfrastructures:
♦
Novell NetWare platforms
♦
Unix and Linux platforms
♦
Apple Macintosh platforms
♦
IBM OS/2 platform
•
The deployment of all “non-migration dependent” aspects and components of the newdesigned Windows Server 2003 Active Directory infrastructure
1.3.
Background Information
Presented within the following three sections are the background information considerationsfor this Migration Plan:1.Understanding the migration plan prerequisitesPage 3 of 446Last printed 27/7/2004 10:54 a7/p7
Leave a Comment