Microsoft Deployment Toolkit Team BlogOfficial blog for MDT 2010
What is Deployment 4?
Deployment 4 combines the guidance and toolset from previous releases of Business Desktop Deployment and Beta releases of Windows Server Deployment. This release continues to support Zero Touch Installation of desktop operating systems using Systems Management Server 2003 with the Operating System Deployment Feature Pack and adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Deployment 4 also continues to provide Lite Touch Installation support without infrastructure requirements and adds capabilities for Windows Server 2003 and pre-release versions of Windows Server 2008.
Deployment 4 is available at the Microsoft Deployment Connection (http://connect.microsoft.com).
What applications and operating systems can I deploy using Deployment 4?
Deployment 4 will deploy pre-release 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.
Can I use Deployment 4 to deploy pre-release versions of Windows Server 2008?
Yes. Deployment 4 is part of the Windows Server 2008 Beta and TAP Programs. It is also available as an open beta download.
Where do I find Deployment 4?
Deployment 4 is currently an open program on Microsoft Connect. To join the Deployment 4 Beta 3 program, follow these steps:
If you have not previously registered with Microsoft Connect, you might be required to register before you continue with the invitation process.
If the link in step 1 does not work for you, copy the full link and paste it into the Web browser address bar.
What new features does Deployment 4 contain?
Microsoft System Center Configuration Manager 2007 support, with the following features:
Lite Touch Installation support for Windows Server 2008:
Lite Touch Installation enhancements:
Lite Touch Installation multicast support:
What is the difference between Deployment 4 Lite Touch Installation and Zero Touch Installation?
Deployment 4 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 System Management Server 2003 and Microsoft Active Directory® environment for deployment. Deployment 4’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 Deployment 4 include?
Deployment 4 provides the assets required to deliver Windows Vista and the 2007 Microsoft Office system to the corporate desktop.
Usability
Included Tools and Related Guidance
Technical Solution Guidance
Sample and Job Aid Documents
Which organizations will benefit from Deployment 4?
Deployment 4 offers a solution targeted to all corporate customers who have 25 or more networked PCs using Microsoft desktops and/or servers who need a high level of operational excellence and scalability. Deployment 4 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 Deployment 4 to create stand-alone media initiated operating system deployments.
Which operating system migrations does Deployment 4 provide guidance for?
Deployment 4 can be used to manage desktop migrations of Windows 2000 and later operating systems to Windows Vista. Deployment 4 also provides functionality for migrating Windows 2000 to Windows XP with Service Pack 2.
How does the workflow process ensure smooth deployment?
The Deployment 4 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 Deployment 4 make it easier for implementers to get to technical content?
Deployment 4 has contains feature team guides in two sections: guidance for project management and guidance for feature team technical implementers. The Deployment Workbench MMC application has document navigation features built into the tool.
How does Deployment 4 address the biggest obstacles in deployment?
Microsoft conducted extensive research to prioritize the top “deployment blockers” that prevent efficient migration and designed Deployment 4 to address these:
· Application compatibility
· Office documentation migration
· User state migration
· Automation of deployment
· Desktop Imaging
Which technologies are being applied in Deployment 4?
Deployment 4 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, 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
· Deployment Process—Windows PE 2.0, Sysprep, Windows Deployment Services, Deployment 4 Deployment Wizard
· BitLocker™ drive encryption support for Lite Touch Install scenarios
Are there technology constraints to Deployment 4?
By design, there are very few. With Deployment 4, 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. Deployment 4 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 Deployment 4 support Windows XP Professional with Service Pack 2 and Windows Server 2003 installations?
Yes. Deployment 4 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. Deployment 4 downloads the Windows AIK from the Deployment Workbench.
What tools are used in the Deployment 4 accelerator for imaging?
Deployment 4 delivers a feature-rich MMC console, Deployment Workbench, which is built on Windows Vista deployment tools including: ImageX, Windows System Image Manager, Windows PE 2.0, and Windows Deployment Services. Deployment 4 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 Deployment 4 address security policies necessary for desktop and server hardware?
Deployment 4 helps companies understand how security policies affect the design of operating system images and also discuss strategies for hardening of desktops and servers. However, Deployment 4 is not intended to replace specific security solutions. In parallel with Deployment 4, the Windows Vista Security Guide and Windows Server 2003 Security Guide is available on Microsoft TechNet and available from the Microsoft Download Center. Future Deployment accelerator releases will integrate the 2007 Office Security Guide and the Windows Server 2008 Security Guide.
Can Deployment 4 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 Deployment 4 to fit into any project-management methodology.
Who should use Deployment 4 and how much does it cost?
Deployment 4 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. Deployment 4 is available at the Microsoft Deployment Connection (http://connect.microsoft.com).
Deployment 4 is the code name for the next version of Business Desktop Deployment (BDD) 2007 and unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. For the thousands of IT professionals already trained on BDD 2007, Deployment 4 requires minimal extra training to perform large-scale Windows Server 2008 and Windows Server 2003 deployments, while offering a further enhanced desktop deployment experience. Deployment 4 adds integration with recently released Microsoft deployment technologies to create a single path for image creation and deployment, including:
System Center Configuration Manager 2007 Operating System Deployment Windows Automated Installation Kit Windows Deployment Services with new multicast technology Application Compatibility Toolkit 5.0 User State Migration Tool 3.0.1 Windows Server 2008 Server Manager for automated server role definition (coming soon) Enhanced Beta Program on Microsoft Connect
This Beta release also offers an enhanced Microsoft Connect portal including technical frequently asked questions, deployment tips and tricks, a recommended 10-step program for new users to quickly get acquainted with deployment accelerators, customer-ready Solution Accelerator informational materials, and deployment-related conference presentations.
Accelerator Description
Deployment 4 Beta 3 combines the guidance and toolset from previous releases of Business Desktop Deployment and Beta releases of Windows Server Deployment. This release continues to support Zero Touch Installation (ZTI) of desktop operating systems using Systems Management Server (SMS) 2003 with the Operating System Deployment Feature Pack and adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Deployment 4 also continues to provide Lite Touch Installation (LTI) support without infrastructure requirements and adds capabilities for Windows Server 2003 and pre-release versions of Windows Server 2008.
New features in Deployment 4 Beta 3
Full support for Windows Vista, Windows XP, and Windows Server 2003 deployments with Deployment 4 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 SMS 2003, including dynamic package installation, automatic determination of state store location, computer backup, database settings.
Lite Touch Installation (LTI) support for Windows Server 2008:
Support for deploying Windows Server 2008 Beta 3 and potentially RC0 (to be verified after RC0 release), including support for Server Core installation options. (Windows Server 2008 TAP customers only.) Lite Touch Installation (LTI) 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 Server template: Windows Server 2003, 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.
Lite Touch Installation (LTI) 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.
Where to Find Deployment 4 Beta 3
Deployment 4 Beta 3 is part of the Windows Server 2008 Beta and TAP Programs. It is also available as an open beta download.
To join Deployment 4 beta 3 program, follow these steps:
Visit the Microsoft Connect Web site (http://connect.microsoft.com).
Click Invitations on the Connect menu.
You will need to sign in using a valid Windows Live ID before you can continue to the Invitations page.
Enter your Invitation ID in the box. Your invitation ID is: BDDP-QMYH-VWTH Click Go.
To download Deployment 4, click Download Now.
(If this link does not work for you, copy the full link and paste it into the Web browser address bar.)
Thanks for your participation.
Deployment 4 Team
Microsoft
Q. What additional files are needed to deploy Windows XP SP2 with BDD 2007?
A. In addition to the Windows XP SP2 source files, sysprep.exe, setupcl.exe, and factory.exe from the deploy.cab file from the Windows XP SP2 Support Files located at the root of the Product media or downloaded from:
http://www.microsoft.com/downloads/details.aspx?familyid=3E90DC91-AC56-4665-949B-BEDA3080E0F6
Q. How does BDD 2007 utilize the tools from the deploy.cab file?
A. By copying the deploy.cab file into the Distribution\tools\x86 folder, BDD will locate and extract the necessary files as part of the Lite Touch process to properly sysprep the XP master image before capturing into a WIM file.
Q. What log files can be evaluated to troubleshoot deployment issues with Windows XP?
A. The primary log files for Windows XP SP2 are located in the %windir% folder and are named:
setuplog.txt - Contains information about setup actions during the installation.
setuperr.txt - Contains information about setup errors during the installation.
setupapi.log – Contains information about hardware detection during the installation.
Q. Are there BDD specific log files and where are they located?
A. BDD scripts automatically create log files. Each script creates a log file that matches the name of the script, for example ZTIGather.wsf creates a log file named ZTIGather.log. Each script also updates a common log file (BDD.log) that aggregates the contents of logs created by the BDD scripts. BDD logs are located in the C:\MININT\SMSOSD\OSDLOGS folder during the deployment process. They are then moved at the completion of a deployment, their destination is dependent on the deployment type:
Lite Touch - C:\WINDOWS\TEMP\BDDLogs unless the /debug:true option has been specified.
Zero Touch - C:\TEMP\SMSOSD or C:\SMSOSD unless the C:\MININT\Archive_OSD.SMS file is found.
Q. Can I use Windows System Image Manager to create a catalog file or edit Windows XP setup information files?
A. No, Windows SIM is only used to create and edit unattend.xml files for Windows Vista and Server 2008 deployments. Unattend.txt, and setup.inf files can be edited with a plain text editor such as Notepad.
Q. Can I create a single Windows XP SP2 image for deployment that can be installed to any hardware?
A. As long as the Hardware Abstraction Layer (HAL) of the reference computer matches the HAL of the destination computer, as detailed in the following knowledge base article:
http://support.microsoft.com/kb/309283/
Q. How do I add a storage driver to my already captured Windows XP WIM file for deployment?
A. Unlike Windows Vista, storage drivers must be present on the computer when “sysprep –reseal” is run.
Q. How do I add a storage driver to Windows XP image before syspreping so that it will be available in my image for deployment?
A. After acquiring the correct driver download package, first extract the INF file(s) included in the driver package so that you can determine the correct Plug and Play ID’s (PnP ID) that the driver package supports. Examine the files and locate the PnP ID’s in lines resembling something like the following in the txtsetup.oem file provided by the manufacturer
id = "PCI\VEN_8086&DEV_2922&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_282A&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2829&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"
You will need to copy the drivers & associated files into the distribution share so that they will be available to the setup and sysprep processes. One method is to use the $OEM$ folder structure to automate the necessary copying. A folder structure such as the following is one example:
.\Distribution\Control\<BUILDID>\$OEM$\$1\Drivers\DriverName
Once the driver is available from a known location such as the above, you need to edit the sysprep.inf file so that it includes information which references the PnP ID’s of the driver as illustrated below:
[Sysprep]
BuildMassStorageSection = YES
[SysprepMassStorage]
PCI\VEN_8086&DEV_2652&CC_0106="C:\DRIVERS\DriverName\driverfile.INF"
Each additional driver PnP ID must be added to the sysprep.inf file before running sysprep to integrate the storage driver into the syspreped image.
For a step by step example of integrating the Intel IASTOR driver into sysprep.inf, look a the article: BDD 2007 - Integrating Mass Storage Drivers into your XP image
Q. When I deploy Windows XP with Lite Touch, on some hardware, the machine halts with a Blue Screen (BSOD), or hangs loading mup.sys after the machine attempts to boot into mini-setup?
A. This problem occurs because Windows Vista and Windows PE 2.0 create disk partitions differently than Windows XP. This problem occurs only on computers that use certain BIOS firmware. Knowledge Base article describes the problem and a hotfix for Windows XP that can serve as a workaround for the issue: http://support.microsoft.com/kb/931760/en-us . This problem can also occur due to a HAL mismatch between the source computer and the destination computer or this could also be due to a missing mass storage driver.
Q. I have already created my master XP image and don’t want to rebuild, but am still getting the above problem on some hardware. Is there another workaround available for this issue?
A. One workaround is to add data & values to the registry of WinPE 2.0. These settings will change how WinPE partitions and formats the hard drive before the XP image is applied. The following settings need to be added to WinPE to workaround the issue:
[HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT]"LessThan4GB"=dword:00000000"Between4_8GB"=dword:00000000"Between8_32GB"=dword:00000000"GreaterThan32GB"=dword:00000000
Another workaround that does not require changing the registry in WinPE is a simple change to the Distribution\Scripts\ZTIDiskpart.txt file used by BDD. If you change the file as follows, WinPE will partition the drive in such a manner that there is no need for either of the above steps:
Original ZTIDiskpart.txt file:
select disk 0
clean
create partition primary
assign letter=c:
active
exit
Modified ZTIDiskpart.txt file:
create partition primary align=16065
The "align=16065" command solves the issue described in kb931760 since it would does not create the partition in the area that gets overridden by this bios bug of some systems, but will cause you to to lose approximately 2 MB disk space.
Q. How do I integrate all of the hotfixes for Windows XP as part of my deployment when I build my master image?
A. One suggested method is to use a batch file such as “RunUpdates.cmd” as mentioned in this early TechNet Magazine article:
http://www.microsoft.com/technet/technetmag/issues/2005/11/UtilitySpotlight/default.aspx
NOTE: Don’t use the "ostype" or "splevel" parameters of RunUpdates.cmd since they depend on the old sys2file.vbs output of BDD 2.5.
Q. Where can I find more FAQs and other information about Business Desktop Deployment 2007?
A. Additional information can be found at several Microsoft hosted weblogs:
Ben Hunter’s blog: http://blogs.technet.com/benhunter/default.aspx
Michael Niehaus’ blog: http://blogs.technet.com/mniehaus/default.aspx
Richard Smith’s blog: http://blogs.technet.com/richardsmith/default.aspx
Q. Are there Microsoft newsgroups and similar sites that offer support for deployment?
A. The following newsgroups are available with peers, MVP’s, & Microsoft employee support available:
microsoft.public.deployment.desktop
microsoft.public.sms.tools
microsoft.public.office.setup
microsoft.public.usmt
microsoft.public.application_compatibility
Technet forum:Windows Vista Deployment and Imaging
Q. Are there any useful non-Microsoft deployment related information sources?
A. Yes, several such sources are available:
MyITForum BDD Wiki
DeployVista.com
Q. What log files can be evaluated to troubleshoot deployment issues with Windows Vista?
A. The primary log files for Windows Vista setup are detailed in this Knowledge Base article and are:
setupact.log - Contains information about setup actions during the installation.
setuperr.log - Contains information about setup errors during the installation.
Q. Are there any additional details on troubleshooting using the BDD logs?
A. Ben Hunter has posted an excellent article about BDD logs here:
http://blogs.technet.com/benhunter/archive/2007/06/16/bdd-2007-understanding-bdd-logs.aspx
Q. What exactly is Zero Touch Installation?
A. Zero Touch Installation (ZTI) uses SMS 2003 with the Operating System Deployment (OSD) Feature Pack to completely automate the deployment of Windows XP SP2, Windows Vista as well as any needed applications.
Q. What documents are most useful in understanding the configuration and use of Zero Touch Installation?
A. The principal documents shipped with BDD 2007 which detail ZTI are the “Zero Touch Installation Guide”, “Deployment Configuration Guide”, and “Deployment Configuration Samples Guide”.
Q. Where can I find information that detail automation of ZTI deployments?
A. The “Configuration Reference” document details all of the variables that are used in ZTI deployments. The “Deployment Configuration Samples Guide” document gives complete samples of automating ZTI.
Q. Have any videos been made available to assist in configuring Zero Touch Installation?
A. Zero Touch Deployment Video Walkthrough
Q. What exactly is Lite Touch Installation?
A. Lite Touch Installation is an interactive installation and deployment of Windows XP SP2 or Windows Vista complete with application install and any other needed configuration of the final image on destination computers. Lite Touch Installation in BDD 2007 can be automated using a combination of pre-configured configuration files and the BDD Deployment Database.
Q. What documents are most useful in understanding the configuration and use of Lite Touch Installation?
A. The principal documents shipped with BDD 2007 which detail LTI are the “Lite Touch Installation Guide”, “Deployment Configuration Guide”, and “Deployment Configuration Samples Guide”.
Q. Where can I find information that detail automation of LTI deployments?
A. The “Configuration Reference” document details all of the variables that are used in LTI deployments. The “Deployment Configuration Samples Guide” document gives complete samples of automating LTI.
Q. Have any videos been made available to assist in configuring Lite Touch Deployment?
A. Lite Touch Deployment Video Walkthrough
Q. What is the primary tool used to configure BDD for deployment?
A. BDD 2007 includes the Deployment Workbench which where all deployment configuration is performed.
Q. What steps are necessary to configure BDD 2007 for deployment of Windows Vista?
A. After installing the prerequisites mentioned earlier, the basic steps are:
· Use the Add Operating System wizard to add Windows Vista source media
· Use the New Build Wizard to configure a build with this newly added Vista source
· Use the New Deployment Point Wizard to create a new Lab build
Q. What steps are necessary to configure BDD 2007 for deployment of Windows XP SP2?
· Use the Add Operating System wizard to add Windows XP SP2 source media
· Use the New Build Wizard to configure a build with this newly added XP source
Q. Is additional software required to support the System Management Server 2003 Operating System Deployment (OSD) Feature Pack Update?
A. Yes, SMS 2003 OSD uses an older version of Windows PE, so Windows PE 2004 or Windows PE 2005 must also be added to the Deployment Workbench. (Note: WinPE 2005 is not specifically supported by SMS 2003 OSD)
Q. What is the primary documentation source for configuring a Windows Vista unattended installation?
A. The Unattended Windows Setup Reference in the Windows AIK is the most complete reference for Windows Vista unattended installation.
Q. What is the primary documentation source for configuring a Windows XP SP2 unattended installation?
A. In the \Support\Tools folder on the Windows 2000/XP/2003 product CDs is a compressed folder named Deploy.cab. This file contains various tools that can be used for deploying Windows using unattended and Sysprep installs. To install these tools, insert a product CD, open My Computer, and double-click on \Support\Tools\Deploy.cab to display its contents:
Q. Is there one document that details the basic installation of BDD 2007?
A. Yes, the previously mentioned “Quick Start Guide” document and the “Getting Started Guide” document in the documentation folder under the base BDD 2007 installation folder are the principal documents that outline basic installation considerations.
Q. To what operating systems can I install the BDD 2007.
A. BDD 2007 can be installed on Windows XP SP2, Windows Vista Business, Enterprise, and Ultimate editions, and Windows Server 2003 SP1 (minimum supported server version)
Q. What are the minimum pre-requisites for BDD 2007 installation?
A. Before using BDD 2007 for the first time, the host machine for the BDD installation should have the following software installed:
· Microsoft Windows Installer 3.1. Download Windows Installer 3.1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en.
· Microsoft .NET Framework 2.0. The Windows AIK distribution media includes the .NET Framework 2.0 installation file. Alternatively, download the .NET Framework 2.0 from the following addresses:
· x86. http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&DisplayLang=en
· x64. http://www.microsoft.com/downloads/details.aspx?FamilyID=b44a0000-acf8-4fa1-affb-40e78d788b00&DisplayLang=en
· Microsoft Management Console (MMC) 3.0. Download MMC 3.0 from the following addresses (MMC 3.0 is already native to Windows Vista):
· Windows Server 2003 x86. http://www.microsoft.com/downloads/info.aspx?na=22&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%3d4c84f80b-908d-4b5d-8aa8-27b962566d9f%26DisplayLang%3den
· Windows Server 2003 x64 Edition. http://www.microsoft.com/downloads/info.aspx?na=22&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%3db65b9b17-5c6d-427c-90aa-7f814e48373b%26DisplayLang%3den
· Windows XP Professional x86. http://www.microsoft.com/downloads/info.aspx?na=22&p=2&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%3d61fc1c66-06f2-463c-82a2-cf20902ffae0%26DisplayLang%3den
· Windows XP Professional x64 Edition. http://www.microsoft.com/downloads/info.aspx?na=22&p=4&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%3d1391d79c-9699-487a-bbc5-f5471fae7169%26DisplayLang%3den
· Windows Script Host (WSH) 5.6. Download WSH 5.6 from the following addresses:
· Windows XP and Windows 2000 http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en.
· Windows Sever 2003 http://www.microsoft.com/downloads/details.aspx?FamilyID=887fce82-e3f5-4289-a5e3-6cbb818623aa&DisplayLang=en
Q. Is there certain software that may not be native to a Windows Client operating system that needs to be installed on Destination computers?
A. Yes, the BDD scripts and processes expect the following minimum client software beyond the base OS supported by BDD 2007:
· Windows Internet Explorer® 5.0 or later
· WSH 5.6 (http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en)
· Microsoft Core Extensible Markup Language (MSXML) Services 3.0 (http://www.microsoft.com/downloads/details.aspx?FamilyID=28494391-052b-42ff-9674-f752bdca9582&DisplayLang=en)
· Before running the Windows Deployment Wizard on destination computers that are running Microsoft Windows 2000, ensure that the file msvcp60.dll is installed. To install this file, download Vcredist.exe from http://support.microsoft.com/default.aspx?scid=kb;en-us;259403; then, extract the file on a computer running Windows XP Professional. (This program will not run in Windows 2000.) Copy the extracted contents to the %SYSTEMROOT%\System32 folder of the computer running Windows 2000.
Q. What is the Solution Accelerator for Business Desktop Deployment (BDD) 2007?
A. The Solution Accelerator for BDD contains guidance, sample templates, and technology files (such as scripts and configuration files) to facilitate deployment of Windows client operating systems such as Windows XP SP2 and Windows Vista. It presents deployment guidance as feature team guides that thoroughly explain each deployment process.
Q. Where is the best source for information for Windows Vista Deployment?
A. http://technet.microsoft.com/en-us/windowsvista/aa905061.aspx
Q. What is the single central Microsoft deployment resource?
A. http://www.microsoft.com/desktopdeployment/default.aspx
Q. Where can I download BDD 2007?
A. http://go.microsoft.com/fwlink/?linkid=62043
Q. This download is dated 6/21/2007 – what has changed since the original release of BDD 2007 in 2006?
A. This updated release of BDD 2007 is an update rollup release and is detailed in this Knowledge Base article: http://support.microsoft.com/?id=937191
Q. Can I install this updated BDD 2007 update rollup over an earlier install of BDD 2007 w/o losing any configuration information?
A. Yes, follow the instructions in the above Knowledge Base article # 937191 and use a command line like the following to install the patch over your previous installation:
msiexec /update BDD2007_x86_Patch1.msp REINSTALL=ALL REINSTALLMODE=as /quiet
Q. Is there a quick-start or other similar document for BDD 2007 to assist in first time installation?
A. The BDD 2007 download package contains a number of useful documents for initial installation & configuration, but a newly released “Quick Start for BDD 2007” document is available for download at the same location as the BDD 2007 download above, but is not included in the download.
Q. Is the source code available for BDD 2007?
A. The source code for the BDD 2007 Deployment Workbench and various utility programs (written in C# and C++) is now available on the Microsoft Download Center. See http://www.microsoft.com/downloads/details.aspx?FamilyID=6a67f884-d629-4962-bd0a-c51bad560354&displaylang=en for the download.
Q. What are the system requirements for BDD 2007?
A. Set the below table for details:
Lite-Touch Installation
Zero-Touch Installation
Required Infrastructure
A local area network (LAN) with at least one server and sufficient disk space to store working files and images
Windows Server 2003 with Microsoft Active Directory directory service
Windows DS in legacy mode
SMS 2003 (functional for software distribution) with Service Pack 2 (SP2), the OSD feature pack, and the OSD Update
Required Software
Windows XP Professional
Windows Vista
2007 Office system
Microsoft Operations Manager (MOM) 2005
Microsoft SQL Server 2000
Required Free Software (Download)
· Microsoft User State Migration Toolkit (USMT) 3.01
· Microsoft Application Compatibility Toolkit 5.0
· Windows Automated Installation Kit
· Microsoft Core XML Services (MSXML) 6.0
· Microsoft Management Console 3.0
· Windows Script Host (WSH) 5.6. for Windows XP and Windows 2000 and/or for Windows Sever 2003
· Microsoft .NET Framework 2.0
Windows XP SP2 Deployment Tools
· SMS 2003 Service Pack 2
· SMS 2003 Operating System Deployment Feature Pack
A. The tools for deployment of Windows Vista are primarily contained in the Windows Automated Installation Kit (Windows AIK). Additionally, BDD 2007 takes advantage of the User State Migration Tool 3.0 (USMT), Application Compatibility Toolkit 5.0, BitLocker Drive Preparation Tool, and the Windows Deployment Service on Windows Server 2003.
Q. Is there a similar document to the BDD Quick Start guide that details these additional tools?
A. Yes, the “Windows Vista Deployment Tools Overview” document available from the same BDD 2007 download location above lists these additional tools and describes their general features.
Welcome to our new blog! In case you are wondering who the Microsoft Deployment Team is we are also known as the Business Desktop Deployment Team (BDD) or Windows Server Deployment (WSD) team. We plan on using this blog as a place to easily update FAQ and troubleshooting items relating to BDD and BDD.Next which for right now is named "Deployment 4." We also wanted to provide a more consolidated view to the many other great sources of information out there such as Ben Hunter's blog, Michael Niehaus ' blog, Richard Smith's blog, DeployVista.com, and the myITforum BDD/OSD wiki so you will often see us linking to these other great blog posts and articles as we find them.
Thanks for joining us and we look forward to serving you better through this blog!
-Tim