Tài liệu Module 8: Planning to Deploy a Migration Strategy doc

#




&RQWHQWV##
#
2YHUYLHZ#4
#
&UHDWLQJ#D#0LJUDWLRQ#3URMHFW#3ODQ#5
#
&UHDWLQJ#3URMHFW#3ODQQLQJ#'RFXPHQWV#;
#
&KRRVLQJ#DQ#,QVWDOODWLRQ#6WUDWHJ\#43
#
7HVWLQJ#WKH#0LJUDWLRQ#3ODQ#45
#
3LORWLQJ#WKH#0LJUDWLRQ#3ODQ#47
#
3ODQQLQJ#IRU#D#6PRRWK#7UDQVLWLRQ##
WR#:LQGRZV#5333# 4:
#
%HVW#3UDFWLFHV#4;
#
/DE#$=#'HYHORSLQJ#D#'RPDLQ#8SJUDGH##
7HVW#3ODQ#4<
#
/DE#%=#'HYHORSLQJ#D#'RPDLQ#5HVWUXFWXUH##
7HVW#3ODQ#57
#
5HYLHZ#5<

#
#
#
Module 8: Planning to
Deploy a Migration
Strategy

#

Information in this document is subject to change without notice. The names of companies,
products, people, characters, and/or data mentioned herein are fictitious and are in no way intended
to represent any real individual, company, product, or event, unless otherwise noted. Complying
with all applicable copyright laws is the responsibility of the user. No part of this document may
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of Microsoft Corporation. If, however, your only
means of access is electronic, permission to print one copy is hereby granted.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.


2000 Microsoft Corporation. All rights reserved.

Microsoft, MS, Windows, Windows NT, Active Directory, and Windows 2000 are either
registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.

The names of companies, products, people, characters, and/or data mentioned herein are fictitious
and are in no way intended to represent any real individual, company, product, or event, unless

otherwise noted.

Other product and company names mentioned herein may be the trademarks of their respective
owners.

Project Lead/Instructional Designer:
Sangeeta Garg (NIIT (USA) Inc.)
Lead Program Manager:
Angie Fultz
Instructional Designer:
Robert Deupree (S&T OnSite)
Subject Matter Expert
: Brian Komar (3947018 Manitoba Inc)
Technical Contributors:
John Pritchard, Greg Parsons, David Cross, Rodney Fournier, Tony de
Freitas, Christoph Felix, Shaun Hayes, Megan Camp, Richard Maring, Glenn Pittaway, Anne
Hopkins, Bob Heath, Jeff Newfeld, Jim Glynn, Paul Thompson (Mission Critical Software, Inc.),
David Stern, Lyle Curry, Steve Tate, Bill Wade (Wadeware LLC).
Testing Leads:

Sid Benavente, Keith Cotton
Testing Developer:
Greg Stemp (S&T Onsite)
Testers:
Testing Testing 123
Instructional Design Consultants:
Susan Greenberg, Paul Howard
Instructional Design Contributor:
Kathleen Norton

Graphic Artist:
Kirsten Larson (S&T OnSite)
Editing Manager:
Lynette Skinner
Editors:
Marilyn McCune (Sole Proprietor), Wendy Cleary (S&T OnSite), Jane Ellen Combelic
(S&T OnSite)
Copy Editor:
Shawn Jackson

(
S&T Consulting)

Online Program Manager:
Debbi Conger
Online Publications Manager:
Arlo Emerson (Aditi)
Online Support:
Eric Brandt (S&T Onsite)
Multimedia Development:
Kelly Renner (Entex)
Testing Leads:
Sid Benavente, Keith Cotton

Testing Developer:
Greg Stemp (S&T OnSite)

Courseware Testing:
Data Dimensions, Inc.
Production Support:

Lori Walker (S&T Consulting)
Manufacturing Manager:
Rick Terek (S&T Onsite)
Manufacturing Support:
Laura King (S&T Onsite)
Lead Product Manager, Development Services:
Bo Galford
Lead Product Managers:
Dean Murray, Ken Rosen
Group Product Manager:
Robert Stewart



# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##LLL#


,QVWUXFWRU#1RWHV#
This module provides students with the knowledge and ability to create a
project plan for deploying a migration strategy, create planning documents, and
plan for testing and piloting the migration strategy.
At the end of this module, students will be able to:
„# Plan the deployment of their migration strategy.
„# Identify the planning documents to create.
„# Choose a method for deploying Microsoft
®
Windows
®
2000.
„# Create the test and pilot plans for their migration strategy.

„# Define the steps to ensure a smooth transition from pilot to production.

0DWHULDOV#DQG#3UHSDUDWLRQ#
This section provides you with the required materials and preparation tasks that
are needed to teach this module.
5HTXLUHG#0DWHULDOV#
To teach this module, you need the following materials:
„# Microsoft PowerPoint
®
file 2010A_08.ppt
„# Module 8, “Planning to Deploy a Migration Strategy”

3UHSDUDWLRQ#7DVNV#
To prepare for this module, you should:
„# Read all of the materials for this module.
„# Complete the labs.
„# Read all of the delivery tips.
„# Read the technical white paper, “Automating the Windows 2000 Upgrade,”
on the Student Materials compact disc.
„# Read the following chapters from the Windows 2000 Server Deployment
Planning Guide on the Student Materials compact disc:
•
Chapter 4, Building a Windows 2000 Test Lab
•
Chapter 5, Conducting Your Windows 2000 Pilot
•
Chapter 13, Automating Server Upgrade and Installation
•
Chapter 14, Using Systems Management Server to Deploy Windows
2000

•
Chapter 21, Testing Applications for Compatibility with Windows 2000
„# Microsoft Official Curriculum (MOC) course 1517, Principles of
Infrastructure Deployment, is a good source of information for general
deployment guidelines and Microsoft Solutions Framework processes
discussed specifically in this module and used throughout this course.
„# Read the Appendix, "Mitigating and Managing Risk During Migration."

3UHVHQWDWLRQ=#
48#0LQXWHV#
#
/DEV=#
63#0LQXWHV#
LY##0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


0RGXOH#6WUDWHJ\#
This module shifts away from the technical details of migration to the soft skills
components of project planning and management. Because many of the
students we expect to see in planning courses are support professionals who
may lack project-planning skills, this module is important in bridging the skills
gap. This module provides a very brief look at a few key deployment project
components.
Explain to students why this information is important and engage the more
experienced consultants in discussion of their planning methods so that the less
experienced students can learn from them. If your class is filled with
experienced consultants who prefer to follow their own planning or project
framework, you might want to skim certain sections and spend more time on
the technical components, such as choosing an installation strategy.
Use the following strategy to present this module:

„# Creating a Migration Project Plan
Explain the steps for creating a project plan. Define vision and scope, and
speak about how these concepts help in guiding the planning process.
Explain the various roles that make up a successful project team. Describe
the components of a functional specification document.
„# Creating Project Planning Documents
Discuss the administrative and deployment planning documents to be
created. Emphasize that administrative documents help you identify goals
and define objectives.
„# Choosing an Installation Strategy
Discuss the different methods of running an automated installation of
Windows 2000 and when to use each one.
„# Testing the Migration Plan
Emphasize that testing is a way to reduce migration risk. Emphasize how
the test environment differs for different migration paths.
„# Piloting the Migration Plan
Explain that a pilot needs to be performed before beginning the actual
migration. Explain that the objective of the pilot is to provide a structured
environment for planning, designing, and deploying Windows 2000
technologies. Describe the pre-pilot tasks to be performed. Discuss the pilot
project phases.
„# Planning for a Smooth Transition to Windows 2000
Describe the steps that ensure a successful transition to Windows 2000.
Emphasize that students should not perform migration operations that affect
users in the middle of an important business project or critical time of year,
such as tax season.
„# Best Practices
Describe the best practices for deploying the chosen migration strategy.

# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##Y#

In the labs for this module, students make design decisions regarding the
development of a test plan for an early phase of migration. In Lab A, students
address design decisions for an upgrade test plan, whereas in Lab B, they
address the design decisions for a domain restructure test plan. The design
decisions addressed in the two different labs mirror one another. The main
difference between the labs is the test cases–the issues that need to be validated
in this phase of testing for a particular migration path. Students are not expected
to complete both labs.
Work with the students to determine which lab is of greater interest to students
based on the migration that they will perform in their organization. If you have
customized this course, the lab delivered for this module should reflect the
migration path content of the custom course materials.
If time permits and students are new to planning deployments, consider
presenting the Appendix, "Mitigating and Managing Risk During Migration."
This appendix can be placed either before or after Module 8. The lab for the
appendix is particularly useful for students new to the architect role because it
walks students through each step in developing a risk plan, a deployment
document that is key to migration success.



# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##4#


2YHUYLHZ#
„
&UHDWLQJ#D#0LJUDWLRQ#3URMHFW#3ODQ
„

&UHDWLQJ#3URMHFW#3ODQQLQJ#'RFXPHQWV
„
&KRRVLQJ#DQ#,QVWDOODWLRQ#6WUDWHJ\
„
7HVWLQJ#WKH#0LJUDWLRQ#3ODQ
„
3LORWLQJ#WKH#0LJUDWLRQ#3ODQ
„
3ODQQLQJ#IRU#D#6PRRWK#7UDQVLWLRQ#WR#:LQGRZV#5333
„
%HVW#3UDFWLFHV


Designing a Microsoft
®
Windows
®
2000 migration strategy involves selecting a
migration path to Windows 2000, developing an upgrade or restructuring
strategy, and ensuring continued productivity during a domain upgrade or
restructure by managing and mitigating risks of a production environment.
Before implementing your migration strategy, you need to develop a plan to
deploy it.
At the end of this module, you will be able to:
„# Plan the deployment of your migration strategy.
„# Identify the planning documents to create.
„# Choose a method for deploying Windows 2000.
„# Create the test and pilot plans for your migration strategy.
„# Define the steps to ensure a smooth transition from pilot to production.

For more information on deployment project planning and the Microsoft
Solutions Framework (MSF) approach to project management, see Microsoft
Official Curriculum (MOC) course 1517, Principles of Infrastructure
Deployment, and

6OLGH#2EMHFWLYH#
7R#SURYLGH#DQ#RYHUYLHZ#RI#
WKH#PRGXOH#WRSLFV#DQG#
REMHFWLYHV1#
/HDG0LQ#
,Q#WKLV#PRGXOH/#\RX#ZLOO#OHDUQ#
DERXW#WKH#VWHSV#WR#FRQVLGHU#
ZKHQ#FUHDWLQJ#D#SURMHFW#SODQ#
IRU#GHSOR\LQJ#\RXU#PLJUDWLRQ#
VWUDWHJ\/#ZKLFK#SODQQLQJ#
GRFXPHQWV#WR#FUHDWH/#WKH#
GLIIHUHQW#LQVWDOODWLRQ#
VWUDWHJLHV/#KRZ#WR#SODQ#IRU#
WHVWLQJ#DQG#SLORWLQJ#WKH#
PLJUDWLRQ#VWUDWHJ\/#DQG/#
ILQDOO\/#KRZ#WR#SODQ#IRU#D#
VPRRWK#WUDQVLWLRQ#WR#
:LQGRZV#53331#
([SODLQ#WR#VWXGHQWV#WKDW#WKLV#
PRGXOH#IRFXVHV#SULPDULO\#RQ#
WKH#VRIW#VNLOOV#DVSHFWV#RI#
GHSOR\LQJ#D#PLJUDWLRQ#SODQ1#
#
7KLV#PRGXOH#ZLOO#H[SRVH#

VWXGHQWV#WR#D#IHZ#RI#WKH#NH\#
HOHPHQWV#RI#GHSOR\PHQW#
SURMHFW#SODQQLQJ1#
1RWH#
5# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


‹‹
#&UHDWLQJ#D#0LJUDWLRQ#3URMHFW#3ODQ#
„
'HILQLQJ#0LJUDWLRQ#9LVLRQ#DQG#6FRSH
„
,GHQWLI\LQJ#3HUVRQQHO#5HTXLUHPHQWV#DQG#0LJUDWLRQ#
7HDPV
„
&UHDWLQJ#D#)XQFWLRQDO#6SHFLILFDWLRQ


To migrate to Windows 2000 successfully, you need to plan to deploy your
migration strategy carefully. Without a thoroughly-planned migration strategy
and a project plan, migration seems overwhelmingly large and complex, the
project would most likely fail to deliver its key business value, goals and vision
would conflict between Information Technology (IT) and executive
management, and the project lacks a certain integrity.
Your overall project plan includes various aspects of both your business and
your technical network infrastructure. When creating a project plan, you must:
„# Define your migration vision and scope.
„# Identify personnel requirements and organize your migration teams.
„# Create a functional specification.

6OLGH#2EMHFWLYH#
7R#LQWURGXFH#WKH#VWHSV#IRU#
FUHDWLQJ#D#SURMHFW#SODQ1#
/HDG0LQ#
<RXU#SURMHFW#SODQ#LQFOXGHV#
YDULRXV#DVSHFWV#RI#ERWK#\RXU#
EXVLQHVV#DQG#\RXU#WHFKQLFDO#
QHWZRUN#LQIUDVWUXFWXUH1#
.H\#3RLQWV#
$#GHSOR\PHQW#SODQ#EUHDNV#
GRZQ#D#PLJUDWLRQ#SURMHFW#
LQWR#VPDOOHU/#PRUH#
PDQDJHDEOH#SLHFHV1#
#
$#PLJUDWLRQ#SODQ#ZLOO#OLNHO\#
IDLO#ZLWKRXW#D#FOHDU#SODQ#WR#
HQVXUH#LW#LV#GHSOR\HG#
VPRRWKO\#DQG#LQ#D#ZD\#WKDW#
PHHWV#EXVLQHVV#QHHGV1#
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##6#


'HILQLQJ#0LJUDWLRQ#9LVLRQ#DQG#6FRSH#
„
9LVLRQ
z
,V#DQ#XQERXQGHG#YLHZ#
RI#WKH#IXWXUH#QHWZRUN
z
(VWDEOLVKHV#ERWK#ORQJ0

WHUP#DQG#VKRUW0WHUP#
JRDOV
„
6FRSH
z
3URYLGHV#WKH#ERXQGV#IRU#
WKH#PLJUDWLRQ#SURMHFW
z
'LIIHUHQWLDWHV#EHWZHHQ#
ZKDW#WKH#PLJUDWLRQ#PXVW#
DFFRPSOLVK#DQG#ZKDW#LV#
QRQ0HVVHQWLDO#
Executive Summary
Position
Problem Statement
Vision
Project Scope
Project Assumptions
Project Requirements
Project Success Factors
Project Team Structure
Roles and Responsibilities
Project Schedule
Project Risk Assessment
Document Sign off
Vision/Scope Document


9LVLRQ#6WDWHPHQW#
The migration vision is an unbounded view of the future network. It establishes

both long-term and short-term goals. You can use it to inspire the team for the
long-term success of the migration. It also helps establish shorter-range
objectives. Both in turn lead to high-quality action. A vision statement might
read like the following:
The vision of this project is to deploy a cost-effective, high-value architecture
that improves reliability, reduces the total cost of ownership, and provides for
end-to-end management of all systems in the enterprise.
Each organization has its own business vision. By collecting information on the
vision or goals of the organization and keeping these goals in mind while
creating the migration vision, you help ensure that the migration project aligns
with the long-term vision of the organization.
6FRSH#6WDWHPHQW#
Migration scope provides the bounds for the migration project. It may prioritize
the Windows 2000 components that must be in place first to meet the most
pressing business needs. It differentiates between what the migration must
accomplish and what is non-essential. A scope statement might read like the
following:
The scope of this pilot is to investigate and test the features and functionality of
Windows 2000. All departments will gain experience and interest so that they
are prepared for the future network.
6OLGH#2EMHFWLYH#
7R#GHILQH#PLJUDWLRQ#YLVLRQ#
DQG#VFRSH1#
/HDG0LQ#
$#PLJUDWLRQ#YLVLRQ#VWDWHPHQW#
VKRXOG#DUWLFXODWH#WKH#NH\#
EXVLQHVV#MXVWLILFDWLRQ#IRU#WKH#
PLJUDWLRQ#WR#:LQGRZV#5333#
$FWLYH#'LUHFWRU\1#7KH#
PLJUDWLRQ#VFRSH#HVWDEOLVKHV#

WKH#ERXQGDULHV#IRU#WKH#
PLJUDWLRQ#E\#GHILQLQJ#ZKDW#
WKH#SURMHFW#VHHNV#WR#
DFFRPSOLVK1#
8VH#WKH#VOLGH#WR#GHILQH#
PLJUDWLRQ#YLVLRQ#DQG#VFRSH1#
#
.H\#3RLQWV#
9LVLRQ#LV#WKH#LGHDOL]HG#YLHZ#
RI#WKH#IXWXUH#QHWZRUN1#
#
7KH#VFRSH#SURYLGHV#UHDOLVP#
WR#WKH#YLVLRQ1#,W#GHILQHV#ZKDW#
WKH#PLJUDWLRQ#SURMHFW#LV#QRW#
H[SHFWHG#WR#DFFRPSOLVK1#
7# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


9LVLRQ26FRSH#'RFXPHQW#
During the migration, the vision/scope document provides the data necessary to
make trade-off decisions about what features can be sacrificed if the schedule
becomes impossibly tight or if resources become scarce. It may also define:
„# The tasks that have been excluded from the migration project but are related
to the project implementation.
„# The time frame when certain functionality is required.
„# Any assumptions associated with the project.
„# Any business constraints that may affect the project.
„# The level of effort required for completing the planning phase.

# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##8#

,GHQWLI\LQJ#3HUVRQQHO#5HTXLUHPHQWV#DQG#0LJUDWLRQ#7HDPV#
Program
Management
Program
Management
Development
Development
Testing
Testing
Logistics
Management
Logistics
Management
User
Education
User
Education
Product
Management
Product
Management
Communication


The next step in deployment planning is to organize your migration team and
assign specific roles to team members. Depending on the size of your
organization and the complexity of your migration, you may want to create sub-
teams.

Identify tasks and determine resource requirements for each task. After you
have identified the tasks and determined what resources are required to
accomplish these tasks, you can determine which groups within the
organization need to be involved and whether you need additional resources
outside the organization.
Finally, plan your teams to reflect your internal structure, your business needs,
the Windows 2000 features and services that you want to deploy, and the way
that you want to deploy them.
7HDP#5ROHV#
There are six general roles on a complete planning team. All team members
participate in deployment planning and migration strategy design. These roles
include:
„# Product management. This person in this role is responsible for driving the
project vision and maintaining the scope of the deployment. The product
manager manages customer or executive expectations and develops,
maintains, and executes the business case.
„# Program management. This people in this role are responsible for
facilitating team communication and negotiation. This team typically
allocates resources, schedules projects, and creates status reports Team
members in this role approve changes to the functional specification, such
as eliminating functionality to keep the project on schedule.
6OLGH#2EMHFWLYH#
7R#LGHQWLI\#WKH#PLJUDWLRQ#
WHDPV#DQG#WHDP#UROHV1#
/HDG0LQ#
3ODQ#\RXU#WHDPV#WR#UHIOHFW#
\RXU#LQWHUQDO#VWUXFWXUH/#
EXVLQHVV#QHHGV/#WKH#
:LQGRZV#5333#IHDWXUHV#DQG#
VHUYLFHV#WKDW#\RX#ZDQW#WR#

GHSOR\/#DQG#WKH#ZD\#WKDW#
\RX#ZDQW#WR#GHSOR\#WKHP1#
([SODLQ#WKH#YDULRXV#UROHV#
WKDW#PDNH#XS#D#VXFFHVVIXO#
SODQQLQJ#WHDP1#
#
.H\#3RLQWV#
$VVHPEOH#D#GHSOR\PHQW#
WHDP#WKDW#UHIOHFWV#WKH#
VWUXFWXUH#RI#WKH#EXVLQHVV1#
#
$VVLJQ#UROHV#DQG#
UHVSRQVLELOLWLHV#WR#WHDP#
PHPEHUV1#
9# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


„# Development. The development manager is typically an experienced
implementation architect, able to understand the key issues in all technical
areas of the project. Team members in the role of development play a key
part in migration design and selection of the features to deploy. The people
in this role contribute to setting the deployment schedule by estimating the
time and resources required to implement a feature. Team members in this
role also configure or customize features and provide scripts to facilitate
deployment.Testing. The mission of testing is to ensure that all issues are
known before the release of the design. Testing prepares the test plan, test
specifications, and test cases, and conducts tests to ensure a successful
migration.Logistics management. The mission of logistics is to ensure that
the new environment is manageable, supportable and deployable. These
team members ensure that operational needs are served by the migration and

that the migration can be successful given the physical environment.
Logistics Management works with Development to ensure that the
necessary data is packaged to facilitate installation and administration.
„# User education. The mission of user education is to ensure that end user
needs are protected throughout the migration. This people in this role are
responsible for designing user and team training systems. Their second
mission is to reduce support costs by making the product easier to
understand and use.

# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##:#


&UHDWLQJ#D#)XQFWLRQDO#6SHFLILFDWLRQ#
„
(VWDEOLVKHV#$JUHHPHQW#
DQG#'HOLYHUDEOHV
„
3URYLGHV#%OXHSULQW#IRU#
7HDP#0HPEHUV
„
0XVW#%H#6XIILFLHQ WO\#
&RPSOHWH#%HIRUH#
'HYHORSPHQW#%HJLQV
„
,V#D#)OXLG#'RFXPHQW#
7KDW#8QGHUJRHV#
5HYLVLRQV#%HIRUH#)LQDO#
9HUVLRQ
Functional Specification
Executive Summary

Position
Problem Statement
Vision Statement
Project Scope
Scope
Audience
Contacts
Business Representatives
Overview
Requirements
Assumptions
Risks
Design
Tools
Product


A functional specification document establishes an agreement between the
migration team and key project stakeholders within the organization. The
functional specification document clearly states expectations and deliverables,
and documents these items for future reference.
Begin by creating a draft-functional specification that provides a definition of
migration. The team should describe all functionality at a high level as it works
out details during design of the migration strategy. The completed specification
acts as the blueprint for development, testing, user education, and logistics
management to begin laying out project plans for the deployment of the
migration strategy.
The functional specification is not a complete description of the design, but
must be complete enough to be tested against and to secure agreement among
stakeholders on the desired functionality. Additionally, the functional

specification is a fluid document that is revisited regularly during deployment
and updated to reflect changes in goals, risk, direction, or design.

For more information about creating a functional specification, refer to
course 1515, Principles of Enterprise Architecture, or course 1517, Principles
of Infrastructure Deployment. Or visit

6OLGH#2EMHFWLYH#
7R#H[SODLQ#WKH#FRPSRQHQWV#
RI#D#IXQFWLRQDO#VSHFLILFDWLRQ#
GRFXPHQW1#
/HDG0LQ#
7KH#IXQFWLRQDO#VSHFLILFDWLRQ#
GRFXPHQW#VWDWHV#
H[SHFWDWLRQV#DQG#
GHOLYHUDEOHV/#DQG#
GRFXPHQWV#WKHVH#LWHPV#IRU#
IXWXUH#UHIHUHQFH1#
8VH#WKH#VOLGH#WR#GHVFULEH#WKH#
FRPSRQHQWV#RI#D#IXQFWLRQDO#
VSHFLILFDWLRQ#GRFXPHQW1#
1RWH#
;# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


&UHDWLQJ#3URMHFW#3ODQQLQJ#'RFXPHQWV#
Administrative documents
Administrative documents
Administrative documents
Scope and vision

Scope and vision
Phases and milestones
Phases and milestones
Budget
Budget
Staffing
Staffing
Communications strategy
Communications strategy
Deplo
y
ment documents
Deplo
y
ment documents
Deplo
y
ment documents
Summary of the current networking
environment
Summary of the current networking
environment
Migration strategy
Migration strategy
Gap analysis
Gap analysis
Capacity plan
Capacity plan
Risk plan
Risk plan

Problem escalation plan
Problem escalation plan
Testing and deployment strategies
Testing and deployment strategies
Pilot plan
Pilot plan


Throughout your deployment project, you need to create a variety of documents
that define your vision, encourage support, and guide and summarize the
deployment process.
$GPLQLVWUDWLYH#'RFXPHQWV#
The administrative documents help you identify your goals and define your
objectives. Include the following information in your administrative documents:
„# Scope and vision. Make sure that your plan clearly states the project
objectives, defines the scope, and provides methods that measure progress
and success. This document defines the business problem or opportunity
that led to the decision to migrate, defines the solution, and defines the
audience for the solution.

You can use the scope and vision document at various milestones to
measure migration results and success.

„# Phases and milestones. Break down the deployment into manageable phases
to give your staff time to get oriented and to help you verify the assumptions
that you made in the planning stage. Establish and monitor milestones to
keep the project on schedule.
„# Budget. Identify and track the expected costs and cost constraints for the
project, including development, hardware, facilities, training, personnel,
testing, and deployment. Identify backup sources of funding to cover

unexpected expenses.
„# Staffing. Plan how you will staff your Windows 2000 sites post migration. A
document that outlines the reporting structure, responsibilities, frequency of
meetings, communication strategies, and owners of the overall task and
feature is useful. To avoid management gaps as the migration progresses,
this document should also define the roles and responsibilities during the
migration as you roll out new administrative features.
6OLGH#2EMHFWLYH#
7R#LGHQWLI\#WKH#SODQQLQJ#
GRFXPHQWV#WR#FUHDWH1#
/HDG0LQ#
<RX#QHHG#WR#FUHDWH#D#
QXPEHU#RI#DGPLQLVWUDWLYH#
DQG#GHSOR\PHQW#GRFXPHQWV#
ZKHQ#SODQQLQJ#WKH#
GHSOR\PHQW#RI#\RXU#
PLJUDWLRQ#VWUDWHJ\1#
8VH#WKH#VOLGH#WR#GHVFULEH#
HDFK#DGPLQLVWUDWLYH#DQG#
GHSOR\PHQW#GRFXPHQW#WKDW#
PXVW#EH#FUHDWHG#IRU#
GHSOR\PHQW#SURMHFWV1#
#
7HOO#VWXGHQWV#WKDW#02&#
FRXUVH#484:/#3ULQFLSOHV#RI#
,QIUDVWUXFWXUH#'HSOR\PHQW#
SURYLGHV#D#FRPSOHWH#
H[SODQDWLRQ#RI#HDFK#RI#WKHVH#
GRFXPHQWV/#WKH#WHDP#UROH#
UHVSRQVLEOH#IRU#PDQDJLQJ#

WKHP#DQG#KRZ#WKH\#DUH#XVHG#
WKURXJKRXW#WKH#GHSOR\PHQW#
SURFHVV1#
1RWH#
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\##<#


„# Communications strategy. Raise management and user awareness of the
deployment project by communicating your plans to your organization. This
reduces the resistance to change that a migration introduces and increases
acceptance among the user community.

'HSOR\PHQW#'RFXPHQWV#
You can create the following recommended deployment documents as a part of
your project plan:
„# Summary of the current networking environment. Include a high-level
description of the current networking environment, including the physical
and logical network infrastructure, the hardware, the policies, the number
and types of users, and the geographic locations.
„# Migration strategy. Detail how the transition to Windows 2000 will occur,
including the migration plan for your domains and domain controllers;
where, when, and how the migration will take place; and who will be
involved.
„# Gap analysis. Address the differences between the existing environment and
the desired environment. Then summarize the steps that are required to
arrive at the desired environment. This document provides the bridge
between the summary of the current networking environment and the
migration strategy.
„# Capacity plan. Identify the expectations, potential risks, and contingencies
that you will use to ensure that there is sufficient hardware and network

capacity for the Windows 2000 features that you deploy. For example,
identify the possible effects of the additional the replication traffic created
by the Active Directory
™
directory service or a remote operating system
installation.
„# Risk plan. Identify the risks in your plan and develop contingency plans for
dealing with those risks. Reevaluate your deployment plan continually and
make a formal evaluation after you complete each phase of the project.

For more information about what risks are and risk management,
refer to the Appendix, Mitigating and Managing Risk During a Migration,
on the Student Materials compact disc.

„# Problem escalation plan. Specify an escalation path that people in your
organization can use to resolve and escalate issues as needed. Match the
types of problems or situations to the people who can best address them.
„# Testing and deployment strategies. Plan how you will test and deploy
Windows 2000.
„# Pilot plan. Identify the roles and objectives for the servers that will
participate in the first rollout, decide which features you will deploy and
when, and which security principal groups will take part in each pilot phase.

1RWH#
43# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


&KRRVLQJ#DQ#,QVWDOODWLRQ#6WUDWHJ\#
„
$XWRPDWLQJ#1HZ#,QVWDOODWLRQV#RI#:LQGRZV#5333#6HUYHU

z
8QDWWHQGHG
z
6\VSDUW
z
6\VSUHS
z
%RRWDEOH#&'
„
$XWRPDWLQJ#8SJUDGHV#WR#:LQGRZV#5333#6HUYHU
z
6\VWHPV#0DQDJHPHQW#6HUYHU


During a migration, you may determine that additional domain controllers are
required to support the new Active Directory forest. The installation method
that you choose will vary depending on local IT policies and supporting
infrastructure.
$XWRPDWLQJ#1HZ#,QVWDOODWLRQV#RI#:LQGRZV#5333#6HUYHU#
Automated installation of Windows 2000 Server involves running Setup with
an answer file. Setup can take place in unattended fashion. An unattended setup
includes the following steps:
„# Creating an answer file
„# Determining and implementing a process to configure computer-specific
information
„# Determining and implementing a process to automate the selected
distribution method, such as by using a network distribution point or hard
disk duplication

6OLGH#2EMHFWLYH#

7R#H[SODLQ#WKH#PHWKRGV#IRU#
LQVWDOOLQJ#:LQGRZV#53331#
/HDG0LQ#
7KH#LQVWDOODWLRQ#VWUDWHJ\#WKDW#
\RX#FKRRVH#ZLOO#YDU\#
GHSHQGLQJ#RQ#ORFDO#,7#
SROLFLHV#DQG#VXSSRUWLQJ#
LQIUDVWUXFWXUH1#
'LVFXVV#WKH#PHWKRGV#RI#
SHUIRUPLQJ#DQ#DXWRPDWHG#
LQVWDOODWLRQ#RI#:LQGRZV#
53331#
#
0DQ\#VWXGHQWV#PD\#EH#
XQIDPLOLDU#ZLWK#WKHVH#
DXWRPDWLRQ#WHFKQLTXHV1#
3URYLGH#EDFNJURXQG#
LQIRUPDWLRQ#ZKHUH#
DSSURSULDWH#RU#UHIHU#VWXGHQWV#
WR#WKH#GRFXPHQWV#PHQWLRQHG#
LQ#WKH#QRWHV1#
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\# # 44#


You can use the following methods to automate the installation of
Windows 2000.
Method Use

Unattended You use the Setup Manager wizard to create answer files, which
Setup can use to perform unattended installations or upgrades of

Windows 2000.
Syspart You use Syspart for clean installations on computers that have
dissimilar hardware. Use Syspart to create a master set of files with
the necessary configuration information and driver support that can be
imaged.
Sysprep You use Sysprep for clean installations on computers that have
identical hardware, which includes the Hardware Abstraction Layer
(HAL) and mass storage device controllers. Sysprep prepares the hard
disk on the master computer so that the disk imaging utility can
transfer an image of the hard disk to other computers.
Bootable CD You use the bootable CD method to install Windows 2000 Server on a
computer whose basic input/output system (BIOS) allows it to start
from a CD. This method is useful for computers at remote sites with
slow links and no local IT department.

$XWRPDWLQJ#8SJUDGHV#WR#:LQGRZV#5333#6HUYHU#
You can use Microsoft Systems Management Server to perform managed
upgrades of Windows 2000 Server to multiple systems, especially those that are
geographically dispersed. You can perform upgrades in a centralized fashion
with Microsoft Systems Management Server, controlling when upgrades take
place and which computers are upgraded
Use Systems Management Server to upgrade the server operating system to
Windows 2000. You can then use scripting to automate domain controller
promotion, providing a hands-off way to create domain controllers for the new
Windows 2000 network.

For additional information on automating installations, see the white
paper, Automating the Windows 2000 Upgrade, as well as Chapter 13,
“Automating Server Upgrade and Installation,” and Chapter 14, “Using
Systems Management Server to Deploy Windows 2000” from the Windows

2000 Server Deployment Planning Guide. These documents are on the Student
Materials compact disc.

1RWH#
45# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


7HVWLQJ#WKH#0LJUDWLRQ#3ODQ#
„
'HILQLQJ#D#7HVW#(QYLURQPHQW
z
0XVW#EH#SK\VLFDOO\#LVRODWHG#IURP#SURGXFWLRQ
z
0D\#LQYROYH#GXSOLFDWLQJ#H[LVWLQJ#GRPDLQ#PRGHO#RU#
GHSOR\LQJ#D#SDUWLDO#IRUHVW
„
'HILQLQJ#7HVW#&DVHV
z
'HWHUPLQH#LQWHURSHUDELOLW\/#FRPSDWLELOLW\/#SURYLGH#
EDVHOLQHV#IRU#FDSDFLW\#RU#SHUIRUPDQFH1
z
*RDO#LV#WR#SURDFWLYHO\#H[SRVH#DQG#UHVROYH#SUREOHPV
z
.HHS#QXPEHU#DQG#QDWXUH#RI#WHVW#FDVHV#PDQDJHDEOH


Testing is a risk management technique used to proactively identify and resolve
any technical, political, or administrative issues that might hamper the
deployment project. The primary consideration during the course of all testing
is to eliminate the possibility of a negative impact on production systems and

services. Prior to beginning the pilot, you should create a test plan that
describes your scope, objectives, and test methodologies.
'HILQLQJ#D#7HVW#(QYLURQPHQW#
If you are planning a domain upgrade, the test environment must duplicate the
existing physical and logical production environment as closely as possible.
This requires recreating the current Windows NT
®
version 4.0 domain model.
You should configure and implement the hardware, software, network services,
and devices currently used in production in the same fashion in the test
environment.
If you are planning a domain restructure, the test environment may ultimately
become the production environment. In this situation, the hardware used in the
test environment should reflect the specifications required for the future
production network. The test environment for this migration scenario should
reflect at least a subset of the Active Directory design, which defines the
domain hierarchy, sites, services, and Windows 2000 features that must be
available in the future network. Although it is not necessary to deploy all
domain controllers or domains, you need adequate forest components to
perform restructure test cases and pilots.
6OLGH#2EMHFWLYH#
7R#SODQ#IRU#WHVWLQJ#WKH#
PLJUDWLRQ#VWUDWHJ\1#
/HDG0LQ#
<RX#QHHG#WR#WHVW#\RXU#
:LQGRZV#5333#PLJUDWLRQ#
VWUDWHJ\#LQ#D#ODE#EHIRUH#WKH#
PLJUDWLRQ#
(PSKDVL]H#KRZ#WKH#WHVW#
HQYLURQPHQW#GLIIHUV#IRU#

GLIIHUHQW#PLJUDWLRQ#SDWKV1#
#
.H\#3RLQWV
#
<RX#VKRXOG#DOZD\V#LVRODWH#
WKH#WHVW#HQYLURQPHQW#IURP#
WKH#SURGXFWLRQ#HQYLURQPHQW1#
#
$#JRRG#WHVW#ODE#KHOSV#
SURDFWLYHO\#UHVROYH#LVVXHV#
WKDW#PLJKW#RFFXU#GXULQJ#
PLJUDWLRQ1#
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\# # 46#


Regardless of the type of migration your organization chooses, you must create
the test environment on a dedicated subnet, isolated from production servers
and users, to prevent unnecessary network traffic and protect the existing
network from problems, such as naming conflicts. The test environment should
also use an isolated dynamic DNS and WINS infrastructure.

For more information on setting up the test lab or environment, see
Chapter 4 of the Windows 2000 Server Deployment Planning Guide, “Building
a Windows 2000 Test Lab”, on the Student Materials compact disc.

'HILQLQJ#7HVW#&DVHV#
A test case is a detailed procedure that fully tests a feature or an aspect of a
feature and specifies how a particular test is performed. You can use test cases
to determine interoperability, determine compatibility, or provide baselines for
capacity or performance.

When writing test cases, include the goal of the test, the hardware and software
requirements, the configuration requirements, the steps for performing the test,
and the expected results or success criteria for the test.
Members of the testing team develop test cases that describe the scenarios and
issues that you need to address during the pilot, for example installing servers
and promoting domain controllers or controlling inter-site replication traffic.
The primary purpose of the test cases is to expose specific issues and risks that
you need to resolve prior to full-scale migration.
It is not feasible to test everything. Instead of trying to test every possible
permutation, focus on limits. For example, test the slowest client computer, the
busiest server, or the least reliable network link. In addition, focus on areas
having the greatest risk or the greatest probability of occurring. It is important
to keep your suite of test cases manageable.

Consider automating each test case to save time and overhead. Scripts can
perform test cases and report results as well as remove any sign of testing to
ensure a clean environment for subsequent tests.

7LS#
7LS#
47# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


‹‹
#3LORWLQJ#WKH#0LJUDWLRQ#3ODQ#
„
3XUSRVH#RI#D#3LORW#3URMHFW
z
'HPRQVWUDWH#WKDW#WKH#GHVLJQ#ZRUNV#DQG#PHHWV#QHHGV
z

3UDFWLFH#DQG#UHILQH#GHSOR\PHQW#SURFHVV
„
&RPSRQHQWV#RI#D#3 LORW#3URMHFW#3ODQ
z
2EMHFWLYHV#DQG#UHTXLUHPHQWV
z
'HVFULSWLRQ#RI#ZRUN#DQG#FULWHULD#
z
'RFXPHQWDWLRQ


A pilot is a trial run of the migration processes that have been tested in the lab
environment. The pilot provides an opportunity for users to give you feedback
about how features work. This feedback should be used to resolve problems and
help determine the level of support that will be required after full deployment.
Ultimately, the pilot leads to a decision to proceed with a full deployment or to
slow down so you can resolve problems that could jeopardize your deployment.
3XUSRVH#RI#D#3LORW#3URMHFW#
The primary purpose of a pilot is to demonstrate that the migration strategy
works as expected and meets your organization’s business requirements. A
secondary purpose is to give the migration team a chance to practice and refine
the deployment process. If they discover issues during the pilot, you can refine
the migration strategy and other deployment documents to ensure a smooth full-
scale deployment.
&RPSRQHQWV#RI#D#3LORW#3URMHFW#3ODQ#
You should conduct the pilot as a series of small, manageable project phases.
Each phase should have clearly defined objectives a description of work, a list
of requirements, a list of the criteria define what you must successfully test
before moving to the next phase, and a series of deliverables. You must clearly
document the outcome of each phase of testing and track these outcomes over

time. You can use paper or electronic forms to ensure that people thoroughly
document test results.

For more information on planning and conducting a pilot, see Chapter 5,
of the Windows 2000 Server Deployment Planning Guide, “Conducting Your
Windows 2000 Pilot” on the Student Materials compact disc.

6OLGH#2EMHFWLYH#
7R#H[SODLQ#WKH#SXUSRVH#DQG#
FRPSRQHQWV#RI#D#SLORW#
SURMHFW1#
/HDG0LQ#
3LORWLQJ#WKH#PLJUDWLRQ#SODQ#
SURYLGHV#DQ#RSSRUWXQLW\#WR#
UHILQH#WKH#PLJUDWLRQ#SODQ#
EHIRUH#IXOO0VFDOH#
GHSOR\PHQW1#
8VH#WKH#VOLGH#WR#GLVFXVV#WKH#
SXUSRVH#RI#D#SLORW#DQG#WKH#
FRPSRQHQWV#RI#D#SLORW#
SURMHFW#SODQ1#
1RWH#
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\# # 48#


6DPSOH#3LORW#3ODQ#IRU#D#'RPDLQ#5HVWUXFWXUH#
„
,VRODWHG#/DE#7HVWLQJ
z
'HYHORS#DQG#GRFXPHQW#D#:LQGRZV #5333#VHUYHU#FRQILJXUDWLRQ

„
/LPLWHG#,QWHJUDWLRQ#7HVWLQJ
z
0RYH#VHUYHUV#WR#SURGXFWLRQ#VHJPHQW#WR#LGHQWLI\#FR0H[LVWHQFH#LVVXHV
„
([WHQGHG#,QWHJUDWLRQ#7HVWLQJ
z
)LQDOL]H#QDPHVSDFH#LQWHJUDWLRQ#DQG#FR0H[LVWHQFH#WHVWL QJ
„
/LPLWHG#3LORW#7HVWLQJ
z
,QVWDOO#VHUYHUV#LQ#DOO#ORFDWL RQV#DQG#PLJUDWH#VPDOO#SLORW#JURXS#RI#XVHUV
„
([WHQGHG#3LORW#7HVWLQJ
z
0LJU DWH#ODUJHU#XVHU#SRSXODWLRQ#DQG#LGHQWLI\#SURFHGXU HV#WR#PRYH#
H[LVWLQJ#VHUYHUV


The following is an example of a pilot plan for a restructure scenario.
Depending on the migration path and the complexity of your migration project,
your pilot plan may include more or fewer testing steps.
,VRODWHG#/DE#7HVWLQJ#
The objective of the isolated lab-testing phase is to develop and test a Windows
2000 Server configuration that can be connected to the production network
during later testing phases. Therefore, you must thoroughly test this
configuration to ensure that it creates no adverse impact on the production
network. The deliverable for this phase is a complete documentation of server
installation and configurations appropriate for the desired Active Directory
design.

During this phase, you install Windows 2000-basedservers and create domains
on an isolated lab network that simulates the production local area network
(LAN) and wide area network (WAN).
/LPLWHG#,QWHJUDWLRQ#7HVWLQJ#
The objective of the limited integration testing phase is to move the servers
testing Windows 2000 used in the previous phase from an isolated lab to a
single segment of the production LAN. Server, service domain, and domain
controller configurations will be performed according to recommendations
made during isolated testing. The purpose of this phase is to rule out any co-
existence problems with Windows 2000 and existing production systems while
both systems are operating on the same network segment. The main deliverable
for this phase is a revised version of the server installation and configuration
documentation.

You should not introduce any new features during this phase, or make
configuration changes unless they are required to remediate a co-existence
issue.

6OLGH#2EMHFWLYH#
7R#SUHVHQW#DQ#H[DPSOH#RI#D#
SLORW#SODQ1#
/HDG0LQ#
+HUH#LV#DQ#H[DPSOH#RI#D#SLORW#
SODQ#IRU#D#GRPDLQ#
UHVWUXFWXUH#VFHQDULR#WKDW#LV#
EURNHQ#GRZQ#LQWR#VHYHUDO#
PRUH#PDQDJHDEOH#SKDVHV1#
,Q#WKH#H[DPSOH#SLORW/#SRLQW#
RXW#KRZ#HDFK#SKDVH#
LQYROYHV#DQ#LQFUHDVLQJ#

DPRXQW#RI#QHWZRUN#
FRQQHFWLYLW\#DQG#LQWHJUDWLRQ#
ZLWK#WKH#SURGXFWLRQ#QHWZRUN1#
.H\#3RLQW#
7KLV#PHWKRG#SURYLGHV#WLPH#
WR#HYDOXDWH#WKH#LPSDFW#RI#
:LQGRZV#5333#RQ#WKH#
SURGXFWLRQ#HQYLURQPHQW#
EHIRUH#ILQDOO\#FRQYHUWLQJ#WKH#
WHVW#HQYLURQPHQW#WR#IXOO#
SURGXFWLRQ1#
1RWH#
49# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


([WHQGHG#,QWHJUDWLRQ#7HVWLQJ#
During extended integration testing, the focus shifts from a single network
location to multiple locations situated across the WAN, if one exists. The
objectives of the extended integration testing are to finalize integration of the
Active Directory namespace with the existing Domain Name System (DNS)
namespace so that DNS queries for Windows 2000 services are referred to the
Windows 2000 DNS servers; to install Active Directory in a few remote
locations to analyze replication traffic; to test client authentication and resource
access in the new environment; and to continue to perform interoperability
testing.
The deliverables for this phase include documentation of DNS configuration,
completion of the server installation and configuration documents, and client
configuration documentation.
/LPLWHG#3LORW#7HVWLQJ#
The objectives of this phase are to extend the deployment of the Windows 2000

pilot to additional locations and to migrate a limited population of users to the
new environment. To achieve these objectives, you must install additional
servers and domain controllers throughout the organization to provide global
catalog and logon services; create trust relationships between the production
and test environment to allow for resource access; and test the applications that
are required by the pilot users to complete their daily responsibilities. You may
also test and deploy remote access services to pilot users.
The deliverables for this phase include documentation of application
compatibility testing, a user migration checklist, documentation of the trusts
created during this phase, and identification of the requirements for the next
phase of testing.
([WHQGHG#3LORW#7HVWLQJ#
The purpose of the extended pilot testing phase is to expand the pilot to a larger
population of users, identify procedures for migrating existing servers to the
new environment, and finalize the comprehensive migration project plan. This
phase involves solving application compatibility issues identified in earlier
phases, deploying additional servers, migrating additional users, completing
application and compatibility testing, and defining processes for completing the
migration to Windows 2000.
The deliverables for this phase include documentation detailing the results of
application testing and the processes used to complete the migration of users
and servers, and a final and fully-tested migration project plan.
The documentation created throughout pilot testing provides the information
necessary to develop a plan that transitions the pilot environment to production.
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\# # 4:#


3ODQQLQJ#IRU#D#6PRRWK#7UDQVLWLRQ#WR#:LQGRZV#5333#
Phase your migration efforts
Phase your migration efforts

Create a backup or recovery plan
Create a backup or recovery plan
Provide appropriate training
Provide appropriate training
Keep teams informed
Keep teams informed
1
1
1
2
2
2
3
3
3
4
4
4
Schedule major migration activities around business
operations
Schedule major migration activities around business
operations
5
5
5


A goal of deployment planning is smooth conversion from pilot to production
with minimal interruption to users, the network, and the core business functions
of the organization.

Some recommended steps to ensure a successful transition include:
„# Phasing your migration efforts. Incremental migration breaks the project
down into smaller, more manageable pieces and allows you to test smaller
segments of the migration.
„# Creating a backup or recovery plan. A reliable and tested backup plan
enables you to recover quickly and easily if you encounter any problems
during the migration. Because a computer or site disaster can overcome
even the best data protection strategies, you need to have a tested system
disaster recovery plan.
„# Providing appropriate training. Make sure that your support and
administrative teams are fully trained and prepared for the migration. Ensure
that end users are informed of the migration and receive appropriate user
training before new technology is deployed.
„# Keeping teams informed. Make sure that the teams are aware of migration
plans as a whole, the scope of team responsibility and involvement, and any
changes to the plan or schedule.
„# Scheduling major migration activities around business operations. You can
minimize the impact on your users and network with thoughtful scheduling
of major Windows 2000 activities. For example, wait to deploy
Windows 2000 to a specific group until after that group has completed a
deadline or other major project, or perform domain controller upgrades
during off-peak hours when the fewest number of users require network
access.
6OLGH#2EMHFWLYH#
7R#H[SODLQ#WKH#VWHSV#WR#
HQVXUH#VPRRWK#WUDQVLWLRQ#
IURP#SLORW#WR#SURGXFWLRQ1#
/HDG0LQ#
7KHUH#DUH#VHYHUDO#VWHSV#WKDW#
\RX#FDQ#WDNH#WR#HQVXUH#D#

VPRRWK#WUDQVLWLRQ#WR#
:LQGRZV#53331#
'HOLYHU\#7LS#
'HVFULEH#WKH#VWHSV#
QHFHVVDU\#WR#HQVXUH#
VXFFHVVIXO#WUDQVLWLRQ#WR#
:LQGRZV#53331#
4;# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#


%HVW#3UDFWLFHV#
(VWDEOLVK#0LOHVWRQH#&KHFNSRLQWV
(VWDEOLVK#0LOHVWRQH#&KHFNSRLQWV
7HVW#$OO#'RPDLQ#0LJUDWLRQ#3URFHVVHV#DQG#6HUYLFHV
7HVW#$OO#'RPDLQ#0LJUDWLRQ#3URFHVVHV#DQG#6HUYLFHV
'HYHORS#D#3ODQ#WR#0LWLJDWH#0LJUDWLRQ#5LVNV
'HYHORS#D#3ODQ#WR#0LWLJDWH#0LJUDWLRQ#5LVNV
,QFOXGH#0DMRU#3UH00LJUDWLRQ05HODWHG#7DVNV#LQ#WKH#3URMHFW#6FKHGXOH#
,QFOXGH#0DMRU#3UH00LJUDWLRQ05HODWHG#7DVNV#LQ#WKH#3URMHFW#6FKHGXOH#


Consider the following best practices for deploying your migration strategy:
„# Establish milestone checkpoints as a way to monitor migration progress.
„# Thoroughly test all domain migration processes and services to minimize
the possibility of interruption to the network and business environment.
„# Develop a plan to mitigate migration risks, and review the plan regularly.
„# Include major pre-migration-related tasks in the project schedule, such as
hardware installation, WAN upgrades, disaster recovery testing, or
application upgrades.

6OLGH#2EMHFWLYH#
7R#SURYLGH#EHVW#SUDFWLFHV#IRU#
GHSOR\LQJ#D#PLJUDWLRQ#
VWUDWHJ\1#
/HDG0LQ#
+HUH#DUH#VRPH#EHVW#
SUDFWLFHV#IRU#GHSOR\LQJ#\RXU#
PLJUDWLRQ#VWUDWHJ\1#
8VH#WKH#VOLGH#WR#GHVFULEH#WKH#
EHVW#SUDFWLFHV#IRU#GHSOR\LQJ#
WKH#PLJUDWLRQ#VWUDWHJ\1#
# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\# # 4<#


/DE#$=#'HYHORSLQJ#D#'RPDLQ#8SJUDGH#7HVW#3ODQ#


2EMHFWLYHV#
After completing this lab, you will be able to create a domain upgrade test plan.
3UHUHTXLVLWHV#
Before working on this lab, you must have:
„# Knowledge of planning and performing a domain upgrade.
„# Knowledge of migration project planning documents.
„# Knowledge of migration project team roles.
„# Knowledge of testing migration plans.

(VWLPDWHG#WLPH#WR#FRPSOHWH#WKLV#ODE=#48#PLQXWHV#
6OLGH#2EMHFWLYH#
7R#LQWURGXFH#WKH#ODE1#
/HDG0LQ#

,Q#WKLV#ODE/#\RX#ZLOO#FUHDWH#D#
GRPDLQ#XSJUDGH#WHVW#SODQ1#
([SODLQ#WKH#ODE#REMHFWLYHV1#