Zero Touch Installation Deployment Feature Team Guide

Introduction

Published: August 27, 2005

This guide contains detailed information about how to deploy Microsoft Windows XP Professional, Windows XP Tablet PC Edition, and Office 2003 Editions using Solution Accelerator for BDD. The document shows how the automated deployment process should be run to successfully replace previous Windows operating systems with Windows XP.

This process takes advantage of and combines the results of the other processes in the Solution Accelerator for BDD to accomplish the following tasks:

Collect hardware and software inventory information by using SMS 2003 with Service Pack 1 (SP1).

Migrate existing user profile information by using USMT version 2.6.

Install a Windows XP Professional or Windows XP Tablet PC Edition operating system image on workstations automatically by using the SMS OSD Feature Pack, the ZTI scripts, and the AdminDB.

Monitor the deployment process by using Microsoft Operations Manager (MOM) 2005 and Solution Accelerator for BDD Management Pack.

Optionally, copy existing user data and preferences from the workstation to a network deployment server.

Optionally, create a backup image of the user workstation to a network deployment server.

Repartition and format the existing primary hard drive.

Install a Windows XP Professional or Windows XP Tablet PC Edition operating-system image that includes enterprise applications such as Office 2003 Editions.

Dynamically install applications that are specific to the workstation model, such as DVD software.

Automatically install previously packaged software specific to the user of the workstation.

Optionally, restore the user data and preferences that were previously stored on the network deployment server.

In addition, this process provides guidance on deciding where to place deployment servers and other planning information.

On This Page
BackgroundBackground
PrerequisitesPrerequisites
Determining When Lite Touch Deployment Is AppropriateDetermining When Lite Touch Deployment Is Appropriate

Background

The work described in this guide typically starts in the MSF Planning Phase after a commitment to plan the deployment has been established. The work will continue through the Deploying Phase, where the workstations are actually re-deployed using the new Windows images.

The MSF Release Management Role Cluster is the primary consumer of the work, because most of this document focuses on the actual deployment in the production environment. The Release Management feature team will need to work closely with all the other feature teams to ensure a timely and successful deployment.

Prerequisites

Installing, configuring, and using this process for deploying Windows XP operating systems require personnel who understand and meet certain prerequisites. Those who execute this deployment process should be familiar with the following concepts:

USMT 2.6

SMS 2003 with SP1

SMS OSD Feature Pack

MOM 2005

RIS

Windows PE supplied with the SMS OSD Feature Pack

Application Compatibility Toolkit (ACT)

CD image creation

Network infrastructure, including routers, switches, and firewalls

Networking services infrastructure, including Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), Windows Internet Naming Service (WINS), and remote access

Active Directory® directory service infrastructure, including logical and physical design of infrastructure

Server capacity planning

Workstation image creation

Automated application installation

The Release Management feature team will rely heavily on the development teams that created the workstation images, USMT process, application packages, network analysis, application remediation strategies, and hardware inventories to act as escalation contacts for troubleshooting and resolving problems that arise during the deployment.

Determining When Lite Touch Deployment Is Appropriate

The Solution Accelerator for BDD ZTI deployment process may be inappropriate for deploying certain desktops within your environment. For scenarios in which ZTI deployment is inappropriate, use the Lite Touch deployment process, instead. These scenarios include:

Workstations are not managed by SMS, or no SMS infrastructure exists.

Network capacity is nonexistent or insufficient for ZTI.

Security policies prohibit automatic software installation.

Clients are remote from image distribution point services.

Firewalls prohibit communication.

For more information about Lite Touch deployment, see the Lite Touch Deployment Feature Team Guide, Enterprise Edition in the Additional Resources section of this guide.


**
In This Article
**