Microsoft Deployment FAQ

What is Microsoft Deployment?

Microsoft Deployment is the next version of Business Desktop Deployment (BDD) 2007. It unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. Microsoft Deployment adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Microsoft Deployment also supports Zero Touch Installation of desktop operating systems using Systems Management Server 2003 with the Operating System Deployment Feature Pack. For organizations without software distribution infrastructure, Microsoft Deployment provides a Lite Touch Installation option using the included Deployment Workbench and free tools for disk imaging and deployment.


Microsoft Deployment is available on the Microsoft Download Center and guidance can be read online in the Desktop Deployment and Server Deployment TechCenters on Microsoft TechNet. For more details and links to these destinations and other related content, visit

What applications and operating systems can I deploy using Microsoft Deployment?

Microsoft Deployment will deploy prerelease versions of Windows Server® 2008, Windows Server 2003, Windows® XP SP2, Windows Vista®, and the 2007 Microsoft® Office system using a variety of Microsoft tools and custom scripts. Ongoing updates to the toolset will support released versions of Windows Server 2008.


Can I use Microsoft Deployment to deploy prerelease versions of Windows Server 2008?

Yes. Microsoft Deployment and its Beta predecessor Windows Server Deployment have been part of the Windows Server 2008 Beta programs. Shortly after the official release of Windows Server 2008, an updated version of Microsoft Deployment will provide full support of Windows Server 2008.

Where do I find Microsoft Deployment?

Visit for all downloads and Microsoft TechNet online resources for Microsoft Deployment. The Microsoft Deployment Toolkit containing both the tools and guidance necessary for automating server and desktop deployment is currently available on the Microsoft Download Center at, keyword “Microsoft Deployment.”

What new features does Microsoft Deployment contain?

Microsoft System Center Configuration Manager 2007 support, with the following features:

  • Full support for Windows Vista, Windows XP, and Windows Server 2003 deployments with Microsoft Deployment and Configuration Manager 2007.

  • Complete integration into the Configuration Manager 2007 admin console and task sequencing capabilities.

    • Quick start Configuration Manager 2007 operating system deployments using one wizard to create needed task sequences and packages.

    • Extends the Configuration Manager 2007 task sequencing capabilities with new actions.

  • Feature parity with BDD 2007 and Systems Management Server 2003, including dynamic package installation, automatic determination of state store location, computer backup, and database settings.

  • Added support for online and offline language pack installation.

  • Added support for offline patching.

  • Added support for deployment to computers unknown to the System Center Configuration Manager 2007 database.

Lite Touch Installation support for Windows Server 2008:

  • Capability to deploy Windows Server 2008 Beta 3 and potentially RC1 (to be verified after RC1 release), including support for Server Core installation options. 

Lite Touch Installation enhancements:

  • Enhanced disk and network interface cards (NICs) configuration options, including support for static TCP/IP configuration.

  • Design changes to ease the migration from LTI to Configuration Manager 2007.

  • Support for multiple task sequence templates. New sample templates include:

    • Client template: Windows Vista, Windows XP SP2

    • Server template: Windows Server 2003, pre-release versions of Windows Server 2008

    • Replace scenario template

  • Ability to invoke Web service calls

    • Support for Web service calls from rules

    • Web services can be invoked as part of the rules processing performed by Deployment 4, using new rules that can be defined in CustomSettings.ini.

  • Support for side-by-side installation with Deployment 4 and BDD 2007 installed on the same machine.

  • Windows Update Integration

  • Enhanced User State Migration

Lite Touch Installation multicast support:

  • Deployment Workbench supports multicast transmission of operating system images when performing LTI deployments from Windows Server 2008 servers that are running Windows Deployment Services.

What is the difference between Microsoft Deployment Lite Touch Installation and Zero Touch Installation?

Microsoft Deployment has been updated from Business Desktop Deployment 2007. As with previous releases, Lite Touch Installation requires a minimum set of tools and assumes that the environment does not have systems management utilities, directory services, or deployment servers in place. The highly automated Zero Touch Installation requires Microsoft System Center Configuration Manager 2007 or Microsoft Systems Management Server 2003 and Microsoft Active Directory® environment for deployment. Microsoft Deployment’s Lite Touch Installation has been updated to share most of the configuration process with Zero Touch Installation. The unified architecture makes it easier to implement both Zero Touch Installation and Lite Touch Installation together if desired, depending on the breadth of tools available in the environment.

What does Microsoft Deployment include?

Microsoft Deployment provides the assets required to deliver Windows Vista and the 2007 Microsoft Office system to the corporate desktop.


  • Microsoft Deployment documentation explorer graphical user interface in the Deployment Workbench

  • Microsoft Deployment Getting Started pages in the Deployment Workbench

  • Component/tool download and installation status

Included Tools and Related Guidance

  • Deployment Workbench

  • Microsoft Application Compatibility Toolkit 5.0

  • Microsoft User State Migration Tool 3.0.1

  • Microsoft Windows Enterprise Learning Framework User Kit

  • Windows Automated Installation Kit (WAIK) User's Guide for Windows Vista

  • Microsoft Windows Preinstallation Environment 2.0

  • Stand-alone task sequencer derived from System Center Configuration Manager 2007

  • Lite Touch wizards

  • Zero Touch Configuration engine

Technical Solution Guidance

  • Getting Started Guide

  • Plan, Build, and Deploy Guide

  • Volume Activation Guides

  • Application Management Feature Team Guide

  • Infrastructure Remediation Feature Team Guide

  • Security Feature Team Guide

  • Migration Feature Team Guide

  • Imaging Engineering Feature Team Guide

  • Deployment Feature Team Guide

  • Preparing for Lite Touch Installation Guide

  • Preparing for Zero Touch Installation Guide

  • Preparing for System Center Configuration Manager 2007

  • Release Readiness Feature Team Guide

  • Operations Readiness Feature Team Guide

  • Plan, Build, and Deploy Guide for Office Upgrades

  • Office Deployment Guide

  • Enterprise Learning Framework User Guide

  • Test Feature Team Guide

Sample and Job Aid Documents

  • Sample Deployment Project Plan, featuring a fictitious company archetype named Woodgrove Engineering

  • Woodgrove Enterprise IT Archetype

  • Woodgrove Business Case Document

  • Woodgrove Business Case Presentation

  • Site Deployment Project Plan

  • Test Feature Team Guide

  • Functional Specification

  • Migration Plan

  • Pilot Plan

  • Risk Template Tool

  • Test Plan

  • Test Specification

  • Test Cases Workbook

  • Training Plan

  • Vision Scope

  • Client Build Requirements

  • Application Knowledge Sheet

  • Communications Plan

  • Network and Workstation Hardware Upgrades List

  • Inventory Template

  • Assessment Template

  • Current State Assessment Template

  • The 20 Commandments of Software Packaging

  • Macrovision Application Preparation Roadmap

  • MSI Repackaging and Customization Best Practices Guide

  • Macrovision Brochure

  • Office Assessment Template

  • Office Budget Plan

  • Office Communications Plan

  • Office Configuration Plan

  • Office Current State Assessment Template

  • Office Distribution Plan

  • Office File Migration Plan

  • Office Functional Specification

  • Office Hardware Upgrades List

  • Office Inventory Template

  • Office Management Plan

  • Office Pilot Plan

  • Office Project Plan

  • Office Risk Template Tool

  • Office Test Plan

  • Office Training Plan

  • Office Vision Scope Plan

Which organizations will benefit from Microsoft Deployment?

Microsoft Deployment offers a solution targeted to all corporate customers who have as few as 25 or more networked PCs using Microsoft desktops and/or servers who need a high level of operational excellence and scalability. Microsoft Deployment is especially useful for organizations with varied network and systems management infrastructure. Organizations with low bandwidth or disconnected branch offices or remote users can also benefit from new capabilities in Microsoft Deployment to create stand-alone media-initiated operating system deployments.

Which operating system migrations does Microsoft Deployment provide guidance for?

Microsoft Deployment can be used to manage desktop migrations of Windows 2000 and later operating systems to Windows Vista. Microsoft Deployment also provides functionality for migrating Windows 2000 to Windows XP with Service Pack 2.

Do I need Microsoft Deployment if my organization has System Center Configuration Manager 2007?

System Center Configuration Manager 2007 contains several deployment enhancements compared to Systems Management Server 2003. These enhancements include native support for operating system deployment, an integrated task sequencing engine and support for standalone media-initiated deployment. If your organization has System Center Configuration Manager 2007, Microsoft Deployment provides additional value by delivering deployment project management guidance, extensions to task sequencing capabilities, three additional task sequence templates and enhanced post operating system installation provisioning tasks—including automated role installation for Windows Server 2003 deployment.

How does the workflow process ensure smooth deployment?

The Microsoft Deployment process is based on Microsoft Solutions Framework (MSF). MSF delivers proven practices for planning, building, and deploying a variety of technology solutions. It combines aspects of software design and development plus infrastructure design and deployment into a single project life cycle. With MSF, organizations can achieve the right balance of flexibility while meeting their commitments, as well as achieve speed while minimizing their risks.

Does Microsoft Deployment make it easier for implementers to get to technical content?

Microsoft Deployment contains feature team guides in two sections: guidance for project management and guidance and technical guidance for implementers. The Deployment Workbench MMC application has document navigation features built into the tool.

How does Microsoft Deployment address the biggest obstacles in deployment?

Microsoft conducted extensive research to prioritize the top “deployment blockers” that prevent efficient migration and designed Microsoft Deployment to address these:

·         Application compatibility

·         Data migration

·         Deployment automation

·         Disk Imaging

·         Post installation configuration and provisioning

Which technologies are being applied in Microsoft Deployment?

Microsoft Deployment is based on deployment tools from Microsoft, as well as custom scripts.

·         Hardware and software Inventory—Application Compatibility Analyzer, Microsoft SQL Server™/Microsoft SQL Server™ 2000 Desktop Engine, Microsoft Office Access™

·         Application Compatibility Testing and Remediation—Application Compatibility Toolkit 5.0.2, Microsoft Virtual PC 2004

·         Core Application Packaging—Office Professional Edition 2007, the Microsoft Office Resource Kit

·         Imaging—ImageX, System Image Manager, Microsoft Windows Preinstallation Environment 2.0 (Windows PE 2.0), Sysprep, Deployment Workbench

·         Project Management—Microsoft Project 2003

·         Application Packaging—Customer choice

·         Volume Activation 2.0—New methods of activation

·         User Data and Settings—User State Migration Tool 3.0.1

·         Deployment Process—Windows PE 2.0, Sysprep, Windows Deployment Services, Microsoft Deployment Deployment Wizard

·         BitLocker™ drive encryption support for Lite Touch Install scenarios

Are there technology constraints to Microsoft Deployment?

By design, there are very few. With Microsoft Deployment, Microsoft does not assume that any network management system or specific deployment servers already exist within the organization.

Will desktop users lose all data and settings that they currently have on their computers?

No. Microsoft Deployment provides detailed, best-practice guidance about user state migration for desktops and employs the User State Migration Tool 3.0.1 to migrate the desired settings and attributes to the new desktop.

Does Microsoft Deployment support Windows XP Professional with Service Pack 2 and Windows Server 2003 installations?

Yes. Microsoft Deployment supports Windows XP SP2, Windows Vista, and Windows Server 2003 operating system installations.

How do I get Windows PE 2.0?

Windows PE 2.0 is available as part of the Windows Vista and Windows Server 2008 operating systems (boot.wim). It is also available separately in the Windows Automated Installation Kit (Windows AIK), which includes Windows PE for each platform (ia64, x64, x86) and tools to customize it using Windows System Image Manager and Windows Deployment Services. Microsoft Deployment downloads the Windows AIK from the Deployment Workbench.

What tools are used in the Microsoft Deployment accelerator for imaging?

Microsoft Deployment delivers a feature-rich MMC console, Deployment Workbench, which is built on Windows Vista and Windows Server deployment tools including: ImageX, Windows System Image Manager, Windows PE 2.0, and Windows Deployment Services. Microsoft Deployment also uses Configuration Manager 2007’s stand-alone media initiated operating system deployment feature as well as System Management Server 2003 OS Deployment Feature Pack OS Image package contents and image management.

Does Microsoft Deployment address security policies necessary for desktop and server hardware?

Microsoft Deployment helps companies understand how security policies affect the design of operating system images and also discuss strategies for hardening of desktops and servers. However, Microsoft Deployment is not intended to replace specific security solutions. In parallel with Microsoft Deployment, the Windows Vista Security Guide and Windows Server 2003 Security Guide is available on Microsoft TechNet and from the Microsoft Download Center. Future Deployment accelerator releases will integrate the 2007 Office Security Guide and the Windows Server 2008 Security Guide.

Can Microsoft Deployment be tailored to fit a company’s specific project-management methodology?

Yes. Microsoft Solutions Framework (MSF) is a life-cycle model that addresses a number of disciplines, including project management, so good project-management methodology can be used in conjunction with the solution. The solution can even be adapted to operate within a different life-cycle methodology. Although the phases, tasks, and milestones are specific to MSF, the process is generic. Any analyst with a basic knowledge of MSF and the target methodology should be able to adapt Microsoft Deployment to fit into any project-management methodology.

Who should use Microsoft Deployment and how much does it cost?

Microsoft Deployment is freely available to customers and partners to use in planning and testing their operating system migration and deployment projects for pre-release versions of Windows Server 2008, Windows Server 2003, Windows Vista, Windows XP SP2, and the 2007 Microsoft Office System. More information on Microsoft Deployment and links to downloads and related Microsoft TechNet content can be found at


Comments (2)
  1. Anonymous says:

    Thanks for your great work !!

    I have one big question in my mind,

    there should be a possibility to rollout W2k3 DC’s with WDT. You have implemented the ADDS Roles.

    But my Sys Engineers should be able to fill in Domain Name, ADRM Password,… in the Deployment Wizard.

    Do you have an idea ?



    ps.: we started production phase with WDT after 2 weeks testing and it works great 😉

Comments are closed.

Skip to main content