Zero Touch Installation Deployment Feature Team Guide

ZTI Deployment Process Overview

Published: August 27, 2005

Before you begin your deployment process, you need to identify the high-level steps in the Solution Accelerator for BDD ZTI deployment process. Figure 1 illustrates the Solution Accelerator for BDD ZTI deployment process.

Figure 1. The Solution Accelerator for BDD ZTI deployment process

Figure 1. The Solution Accelerator for BDD ZTI deployment process
See full-sized image

The steps within the Solution Accelerator for BDD ZTI deployment process are grouped by the corresponding MSF phases in your project. Based on your MSF role, you may need to read only portions of this documentation. However, in most instances, you should read all the sections in this guide.

Identifying the Project Milestones

As a part of the Solution Accelerator for BDD ZTI deployment process, you need to identify the project milestones that must be completed for a successful deployment. Table 3 lists the high-level project milestones included in a Solution Accelerator for BDD ZTI deployment by MSF phase and a description of each milestone. Each high-level project milestone is covered in a section later in this guide and has subordinate milestones that are discussed in the corresponding section.

Table 3. High-Level Project Milestones and Their Descriptions

High-Level MilestoneDescription

Planning

 

Appropriate deployment scenario selected

The appropriate combination of scenarios (new computer installation, computer refresh, or computer replacement) is identified.

Required infrastructure exists

Prerequisite technologies and infrastructure to support the deployment exist.

Monitoring plan completed

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

Operations and Deployment feature teams trained

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

Consensus for deployment plan obtained

All stakeholders in the Solution Accelerator for BDD project provide consensus for acting on the deployment plan and future project milestones.

Developing

 

Solution Accelerator for BDD installed

Solution Accelerator for BDD is installed on the appropriate servers.

Appropriate resource access assigned

Shared resources (such as shared folders for user migration data) are configured to allow access to the appropriate service accounts.

SMS OSD Feature Pack packages and programs configured

Each phase of the SMS 2003 OSD Feature Pack deployment (Validation, State Capture, Preinstall, Postinstall, State Restore) is configured to used the ZTI script.

ZTI processing rules configured

Rules for processing the ZTI installation are configured and stored in the appropriate location for deployment.

Reference Computer Images created

Images that the SMS 2003 OSD Feature Pack uses for deploying the operating system are created (also known as golden images or master images).

Windows PE CDs prepared

CD images used to create boot CDs or that are applied to RIS servers are created.

Stabilizing

 

Lab tests and pilot deployments completed

The deployment process is validated in test labs. Further validation occurs during one or more pilot deployments. Any modifications to the deployment process are incorporated prior to production deployment.

Deployment teams prepared

Deployment teams are debriefed on the outcome of the lab tests and pilot deployments. Any common deployment issues, troubleshooting tools, and remedies are communicated to the team.

Deploying

 

SMS 2003 OSD Feature Pack Deployment Wizard run

Deployment of images to workstations is initiated.

Transitioning to Operations

 

Transition preparations completed

Notification of the transition date is established, and users are notified of the change in support (Deployment feature team to Operations feature team).

Current status of deployment communicated

The current list of migrated workstations, workstations that were unable to migrate, and current processes for resolving deployment issues is communicated from the Deployment feature team to the Operations feature team.


**
In This Article
**