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:
In addition, this process provides guidance on deciding where to place deployment servers and other planning information. On This Page
BackgroundThe 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. PrerequisitesInstalling, 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:
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 AppropriateThe 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:
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 |