# 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 migrati
Trang 1Strategy
Trang 2Microsoft 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
Trang 3# 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."
Trang 4Explain 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
Trang 5# 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
Trang 7At 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 http://www.microsoft.com/msf
Trang 8management, 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
Trang 9Project 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
Trang 107# # 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
Trang 11# 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\# # 8#
,GHQWLI\LQJ#3HUVRQQHO#5HTXLUHPHQWV#DQG#0LJUDWLRQ#7HDPV#
Program Management
Program Management
Development
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
Trang 129# # 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
Trang 13Requirements 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 http://www.microsoft.com/msf
Trang 14Staffing Communications strategy
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
Trang 15# 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#
Trang 16$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
Trang 17# 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#
Trang 18deployment 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