# &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 http://www.microsoft.com/msf 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. [...]... 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... 1 Name a few deployment documents that you should create when planning the deployment of your migration strategy Some of the deployment documents that you should create include a summary of the current networking environment, a migration strategy, a risk plan, and a pilot plan 2 Why should you create a test plan? To expose specific issues and risks that you need to resolve prior to fullscale migration. .. 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... 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 1RWH# 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... 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... 2000 network 1RWH# 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 45# # 0RGXOH#;=#3ODQQLQJ#WR#'HSOR\#D#0LJUDWLRQ#6WUDWHJ\#... 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... 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... 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 . Migration strategy Migration strategy Gap analysis Gap analysis Capacity plan Capacity plan Risk plan Risk plan Problem escalation plan Problem escalation. For additional information on automating installations, see the white paper, Automating the Windows 2000 Upgrade, as well as Chapter 13, “Automating