Export (0) Print
Expand All

Planning

Published: November 09, 2007

Figure 2 illustrates the primary activities that occur during the Planning Phase. While other teams are developing images, project plans, and so on, the Deployment feature team is focusing on the existing production environment to decide how to approach deployment. The team must look at all the locations and departments in which computers will be upgraded and decide in which order the upgrades will occur.

Figure 2. Activities during the Planning Phase

Figure 2. Activities during the Planning Phase
On This Page

Planning Checklist Planning Checklist
Roles and Responsibilities Roles and Responsibilities
Select Deployment Scenarios Select Deployment Scenarios
Select Deployment Methods Select Deployment Methods
Ensure That the Required Infrastructure Exists Ensure That the Required Infrastructure Exists
Determine the Appropriate Processing Rules Determine the Appropriate Processing Rules
Determine the Monitoring Plan Determine the Monitoring Plan
Train Team Members Train Team Members
Milestone: Deployment Plan Complete Milestone: Deployment Plan Complete

Planning Checklist

The primary focus in this phase is on selecting the appropriate deployment scenarios and methods, ensuring that the required infrastructure exists, determining the appropriate processing rules and the monitoring plan, and training team members. Table 2 shows the high-level steps in the Planning Phase.

Table 2. Planning Phase Checklist

High-level steps in the deployment Planning Phase

Select the appropriate deployment scenarios.

The environment typically requires more than one deployment scenario. The team must determine which combination of deployment scenarios the environment will use (including the New Computer, Upgrade Computer, Refresh Computer, and Replace Computer scenarios).

Select the deployment methods.

Determine which computers in the environment can be migrated to the new operating system using LTI or ZTI. The environment can use one or both of these methods.

Ensure that the required infrastructure exists.

Ensure that the appropriate infrastructure exists before beginning deployment. If the appropriate infrastructure does not exist, the team cannot use Microsoft Deployment to deploy the operating system.

Determine the appropriate processing rules.

Before using ZTI or LTI to deploy the operating system, configure the processing rules. The processing rules help determine which operating system images are deployed and their configuration settings.

Determine the monitoring plan.

As team members are deploying the operating system in the test and production environments, they should monitor the progress of the deployment. In addition to using either System Center Configuration Manager or Systems Management Server 2003 (in the case of ZTI), the team can use System Center Operations Manager and the Microsoft Deployment Management Pack for System Center Operations Manager.

Train the team members.

Before beginning deployment in the test and production environments, ensure that all team members are properly trained. This helps the team deploy, manage, operate, troubleshoot, and support target computers throughout the entire deployment process.

Roles and Responsibilities

All six role clusters from the MSF Team Model play a role in the Planning Phase. Table 3 lists those roles and defines the focus areas for each role cluster relative to the deployment process in the Planning Phase.

Note   For more information about MSF role clusters, see the white paper, “MSF Team Model,” which is available for download from Microsoft Solutions Framework at http://www.microsoft.com/technet/itsolutions/msf/default.mspx.

Table 3. Team Roles and Responsibilities in the Planning Phase

Role

Focus

Product Management

  • Business requirements analysis

  • Communications plan

Program Management

  • Budget

  • Master project plan and master project schedule

Development

  • Development plan and schedule

  • Establishing the lab

  • Logical and physical design

  • Technology evaluations

Test

  • Test plan and schedule

  • Testing requirements definition

User Experience

  • Localization/accessibility requirements

  • Schedules

  • Training plans

  • Use scenarios/use cases

  • User documentation

  • User requirements

Release Management

  • Application and hardware inventory

  • Interfacing with Information Technology (IT) Operations and the Security feature team

  • Network discovery

  • Operations requirements

  • Pilot and deployment plan/schedule

Select Deployment Scenarios

As the first step in the Planning Phase, select the deployment scenarios that are appropriate for the environment. Table 4 lists the deployment scenarios and provides a brief description of each.

Table 4. Deployment Scenarios and Descriptions

Scenario

Description

User State Migrated

Uses existing target computer

File system preserved

New Computer

A new installation of Windows is deployed to a new computer. This scenario assumes that there is no user data or profile to preserve.

No

No

No

Upgrade Computer

The current Windows operating system on the target computer is upgraded to the deployed operating system. The existing user state migration data, user profile, and applications are retained (as supported by the deployed operating system).

Yes

Yes

Yes

Refresh Computer

A computer currently running a supported Windows operating system is refreshed. This scenario includes computers that must be re-imaged for image standardization or to address a problem. This scenario assumes that the team is preserving the existing user state data on the computer.

Yes

Yes

No

Replace Computer

A computer currently running a supported Windows operating system is replaced with another computer. The existing user state migration data is saved from the original computer. Then, a new installation of Windows is deployed to a new computer. Finally, the user state data is restored to the new computer.

Yes

No

No

Based on the existing environment, the team can select any combination of these scenarios in the deployment. For example, if the organization is only upgrading existing computers, they might use only the Refresh Computer and Upgrade Computer scenarios. If the organization is deploying new computers for some users and upgrading the remaining computers, the team might use the Upgrade Computer, Replace Computer, and Refresh Computer scenarios.

For more information on the Windows Vista upgrade and migration paths, see the section, “Upgrade and Migration Paths,” in the Microsoft Deployment document, Getting Started Guide.

Select Deployment Methods

In most instances, the Deployment feature team will use a combination of LTI and ZTI to deploy operating systems to the target computers. In Microsoft Deployment, LTI and ZTI use the same common set of scripts and configuration files (such as CustomSettings.ini) for deploying the operating system. However, there are instances in which one method of deployment might be more advantageous.

For more information about:

  • ZTI deployment, see the Microsoft Deployment documents, Preparing for Microsoft Systems Management Server 2003 or Preparing for Microsoft System Center Configuration Manager 2007.

  • LTI deployment, see the Microsoft Document, Preparing for LTI Tools.

Deploy Operating Systems Using LTI

LTI requires minimal infrastructure to operate. The team can deploy operating systems over the network using a shared folder, or locally using removable storage (such as a CD, DVD, USB flash drive [UFD], or other device). Team members can initiate the deployment process automatically (using Windows Deployment Services) or manually. They initially configure LTI using Deployment Workbench, and then further customize CustomSettings.ini for the specific environment.

In LTI deployment, the team provides configuration settings for groups of computers. The configuration settings for each individual computer are usually provided manually during the deployment process. As a result, customizing LTI usually requires less effort than customizing ZTI.

Deploy Operating Systems Using ZTI

ZTI requires System Center Configuration Manager or Systems Management Server 2003 with SP2, and the SMS 2003 OSD Feature Pack. The team deploys operating systems from System Center Configuration Manager or Systems Management Server 2003 distribution points. The installation process can be initiated by System Center Configuration Manager, Systems Management Server 2003, or Windows Deployment Services. The ZTI deployment process is always initiated automatically. Like LTI, the team initially configures ZTI using Deployment Workbench, and then further customizes CustomSettings.ini for their environment.

In ZTI deployment, the team must provide all configuration settings for each target computer being migrated using ZTI. By definition, there is no manual configuration in ZTI. As a result, customizing ZTI usually requires more effort than customizing LTI.

Contrast LTI and ZTI

In Table 5 provides a contrasting view of the use of LTI and ZTI in the deployment.

Table 5. Contrast of LTI and ZTI Deployments

LTI deployment

ZTI deployment

Provides configuration settings that are common to a group of target computers.

Provides all necessary configuration settings for each target computer.

Requires less upfront configuration time.

Requires more upfront configuration time.

Can be used with slow-speed connections or in instances where no network connectivity exists.

Requires a high-speed, persistent connection.

Requires little or no infrastructure to support deployment.

Requires an infrastructure sufficient to deploy operating system images using either the SMS 2003 OSD Feature Pack or System Center Configuration Manager.

Supports deployment over the network or locally.

Supports only network deployments.

Target computers are not required to be managed using either System Center Configuration Manager or Systems Management Server 2003 (or other software-management tools).

Target computers must be managed using either System Center Configuration Manager or Systems Management Server 2003.

Supports security policies where automatic software installation is prohibited.

Supports only security where automatic software installation is allowed.

Supports deployment to target computers isolated by firewalls.

Requires Remote Procedure Call (RPC) communication with target computers (and so usually requires too many ports to be opened through firewalls).

Supports Upgrade Computer deployment scenarios.

Upgrade Computer scenarios are not supported.

Ensure That the Required Infrastructure Exists

Before using Microsoft Deployment to deploy Windows, ensure that the required infrastructure exists. For most production environments, the majority of services required for deployment already exists. However, the Deployment feature team must verify that all of the required components are in place before continuing the deployment process.

For a detailed listing of required infrastructure for:

  • Microsoft Deployment and LTI deployment, see the section, “System Requirements,” in Getting Started Guide.

  • ZTI, see the section, “Ensure that the Required Infrastructure Exists for ZTI , ” in Infrastructure Remediation Feature Team Guide.

Determine the Appropriate Processing Rules

The ZTI and LTI deployment processes use processing rules that determine the steps and configuration parameters during the process of deploying the images to target computers. These settings are stored and managed in CustomSettings.ini.

For more information about:

  • Determining the processing rules required for minimal functionality in LTI, see the section, “Configure the Appropriate Processing Rules,” in Preparing for LTI Tools.

  • Determining the processing rules required for minimal functionality in ZTI, see the section, “Configuring the Appropriate Processing Rules,” in Preparing for Microsoft Systems Management Server 2003 or Preparing for Microsoft Systems Center Configuration Manager 2007.

  • Extending functionality in LTI and ZTI, see Deployment Customization Guide.

  • Examples for configuring the processing rules in LTI and ZTI, see the Deployment Customization Desktop Samples Guide.

Determine the Monitoring Plan

The ZTI Management Pack for System Center Operations Manager monitors the deployment of operating system images to the target computers and collects data. Team members can also use it monitor the ZTI and LTI deployment processes. Using Microsoft System Center Operations Manager 2007 Reporting Services, team members can generate reports about the deployment process. For more information on the ZTI Management Pack, see the Microsoft Deployment document, Zero Touch Installation Management Pack.

Train Team Members

Before beginning deployment, ensure that all team members are properly trained to deploy, manage, operate, troubleshoot, and support the deployment process and the migrated computers. Customize the training for each team.

To train the team members:

  • Identify the training requirements for the organization. Each team has different training requirements. At a minimum, all team members must be able to describe the high-level steps in the deployment process. Other team members require detailed knowledge of the technologies and processes involved in the deployment process.

  • Determine budgeting requirements for training. Include training in the budgetary estimates. In addition to the cost of training, include any estimated travel expenses and human resource costs.

  • Include training in the project plan. Ensure resource allocation for training attendance in the project plan. While team members are attending training, they will not be available to contribute to or complete other tasks in the project.

  • Schedule team members’ training prior to their involvement in the project. The training should occur before team members participate in the project. Ensure that training is provided early enough in the process that team members have adequate time to become familiar with the technologies and processes.

Milestone: Deployment Plan Complete

Milestones are synchronization points for the overall deployment project. For more information, see the Microsoft Deployment document, Planning Guide.

At this milestone, shown in Table 6, the team has completed the required tasks, and the deployment plan is complete.

Table 6. Planning Phase Project Milestones and Deliverable Descriptions

Planning Phase milestone

Deliverable description

Owner

Appropriate deployment scenario selected

The appropriate combination of scenarios (New Computer, Upgrade Computer, Refresh Computer, and/or Replace Computer) is identified.

Development

Appropriate deployment method selected

The appropriate combination of deployment methods (LTI or ZTI) is selected.

Development

Required infrastructure exists

Prerequisite technologies and infrastructure exist for performing the deployment.

Development

Appropriate processing rules determined

The processing rules that ZTI and LTI use are configured.

Development

Monitoring plan complete

The list of servers, services, and system resources to be monitored is created. The frequency of monitoring is also decided.

Development

Teams trained

Any training that IT Operations and the Deployment feature team require occurs to ensure that both teams are ready by the time deployment occurs.

Program Management


Download

Get the Microsoft Deployment Solution Accelerator

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft