• Embed Doc
  • Readcast
  • Collections
  • CommentGo Back
Download
 
 © 2004 Mustan Bharmal. All Rights Reserved.
Table of Contents
M
P
P
O
P
S
I
P
A
P
P
M
P
P
D
C
M
P
L
D
I
(
S
O
S
 
I
A
C
P
C
D
A
L
D
I
(
S
C
S
M
P
I
O
C
U
S
M
P
C
R
M
S
O
S
I
A
C
P
C
D
D
R
M
S
C
R
M
P
(
S
O
S
I
A
C
P
C
D
D
R
M
P
(
S
C
M
S
C
P
O
I
A
C
P
C
D
D
M
S
C
P
C
 
 © 2004 Mustan Bharmal. All Rights Reserved.
1.Introduction to the Migration Plan
Execute the processes within this Migration Plan only where it is possible to identifycompliance with the following basic criteria:
It is possible to identify the presence of one or more legacy Windows NT 4.0 or Windows2000 directory service infrastructures within the logical boundaries of this organisation, and
There is a requirement to design and execute the migration of one or more of these legacydomain infrastructures to the new Windows Server 2003 Active Directory infrastructure for the organisation.Where it is not possible to identify compliance with the above criteria, then there is norequirement to generate a Migration Plan.Where it is possible to identify the requirement to generate a Migration Plan, then note thatthis design methodology stipulates that a single “Migration Plan” will support the execution of all migration tasks. This will hence include all migration tasks to migrate from each existing in-scope legacy Windows NT 4.0 domain and Windows 2000 Active Directory infrastructure tothe new Windows Server 2003 infrastructure for this organisation.
1.1.
Migration Plan Objectives
The objectives of the “Migration Plan” are to assist an organisation in the generation of adesign for a plan that will support only those components of this project associated with themigration from one or more Windows domain infrastructures to a new Windows Server 2003Active Directory infrastructure.
1.2.
Migration Plan Scope
As only one migration plan is required for the entire project, the scope of this migration planincludes the following:
The migration requirements for all existing Windows-based domain infrastructures withinthe organisation that fall within the scope of this migration plan (the Migration Plan process“analysis of legacy domain infrastructures” will define the migration scope)
All Windows Server 2003 domains and forests within the Windows Server 2003 ActiveDirectory infrastructure for the organisation that have domain creation dependencies uponthe migration of the legacy domains and domain infrastructures.As there is a plethora of excellent information available on the migration to Windows Server 2003 Active Directory from legacy Windows domain infrastructures, this design methodologywill assist an organisation in the design of a migration plan with only a limited technicalperspective. The technical scope, as a strict reflection of the domain or directory serviceperspective, hence stipulates that the following aspects of a migration from one or morelegacy domain infrastructures be inside and outside of the scope of this migration plan:
1.2.1.In-Scope Components
Only the following components and aspects of a migration from one or more legacy domaininfrastructures are within the scope of the Migration Plan:
The design of a migration plan to migrate from the following legacy domain infrastructuresto the new Windows Server 2003 Active Directory infrastructure:
From Windows NT 4.0 domain infrastructures (single domains, single master domainmodels, multiple master domain models)
From Windows 2000 directory service infrastructures (single domains, multiple domaintrees, multiple forests)Page 2 of 446Last printed 27/7/2004 10:54 a7/p7
 
 © 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
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...