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).
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 http://www.microsoft.com/deployment.
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 microsoft.com/deployment 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 downloads.microsoft.com, keyword “Microsoft Deployment.”
What new features does Microsoft Deployment contain?
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.
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.
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:
· 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
· 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
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.
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.
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 microsoft.com/deployment.
We have received a number of emails and questions on how to receive support from Premier Support for Microsoft Deployment. There have been several of you who have been routed to the incorrect support person while trying to receive support for Microsoft Deployment. We apologize for your frustration and inconvenience.
To get routed to the correct support person, follow these instructions. Please note that support for Microsoft Deployment is done on via callback with response times generally ranging between 1 and 4 hours depending on the severity of your issue and the other issues in the queue.
To receive support:
a) Call the support number (1-800-936-3500) http://www.microsoft.com/services/microsoftservices/srv_premier.mspx) or
b) Submit a web incident http://support.microsoft.com/select/default.aspx?target=assistance&c1=508&
c) Clearly state that you have a BDD/MDT issue. (If you talk about deployment they will be routed to a different queue. ).
Thank you and please let us know if you have any problems receiving support in the future.
Source Code for Microsoft Deployment Toolkit 2008 has been released
We have released Microsoft Deployment Toolkit 2008 (build number 4.1.523.0) source code for customers and partners who want to make modifications, enhancements, or bug fixes to MDT’s components. Source Code is current as of the March 2008 release of Microsoft Deployment Toolkit.
Source code for MDT 2008 can be downloaded from Microsoft download center: http://go.microsoft.com/fwlink/?LinkId=117775
We've received several questions over the past few days regarding the Help, About Microsoft Deployment Workbench showing 4.1 even after the upgrade to MDT 2008 Update 1:
The reason why the Help, About Microsoft Deployment Workbench shows Version 4.1 is due to caching that can occur with certain DLL's. In this case the value of the previous installation of that screen can be found here:
HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\@C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.WorkbenchResources.dll,-105
If you previously had MDT 2008 installed the value was cached in this location and unfortunately does not update properly after the installation of MDT 2008 Update 1.
So how do you determine if you have the correct version installed? The correct version of MDT 2008 Update 1 is 4.2.523.40. This can be found by going into Add/Remove Programs. You should see an entry like the following:
If the About window really bothers you, you can delete the registry entry mentioned above and it will then update with the correct version number. :)
We recently had the honor of sitting down with Technet Radio and recording a series of FAQ's about MDT 2008 and a brief discussion on the next version of MDT.
You can download the podcast directly from here:
WMA
MP3 High Bandwidth
MP3 Low Bandwidth
Enjoy!
Get ready to deploy Windows 7 and Windows Server 2008 R2 with Microsoft Deployment Toolkit 2010 Beta 2.
The Windows® 7 and Windows Server® 2008 R2 launches are just around the corner. As you prepare to deploy these operating systems, get a jump start with Microsoft® Deployment Toolkit (MDT) 2010 Beta 2. Leverage this Solution Accelerator to achieve efficient, cost-effective deployment of Windows 7 and Windows Server 2008 R2.
MDT 2010 is the next version of Microsoft Deployment Toolkit, a Solution Accelerator for operating system and application deployment. New features such as flexible driver management, optimized user interface workflow, and Windows PowerShell™ can simplify deployment and make your job easier. MDT 2010 will support deployment of Windows 7 and Windows Server 2008 R2 in addition to deployment of Windows Vista®, Windows Server 2008, Windows Server 2003, and Windows XP. Join the beta now!
Microsoft Deployment Toolkit is the recommended process and toolset for automating desktop and server deployment. MDT provides you with the following benefits:
New Functionality
Microsoft Deployment Toolkit 2010 Beta 2 is a significant upgrade over MDT 2010 Beta 1. MDT 2010 Beta 2 adds the following new features and functionality:
Deployment Workbench Enhancements
Powershell Capabilities
Task Sequence and Script Enhancements
Configuration Manager Enhancements
Next Steps
Microsoft Deployment Toolkit (MDT) 2010 Beta 2 is now available! To invite customers and partners to join the Beta program, forward them the information in this e-mail message.
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
The development team has isolated issues in the initial Microsoft Deployment RC1 build. Toolkit was throwing errors when Configure ConfigMgr Integration, Configure Management Pack or Configure WDS PXE Filter features were invoked. The errors occur because two files were not properly signed in the Microsoft Deployment RC1 release. We have released an updated build which contains these signed files. Please download the latest installers from Connect web site.
If you would like to work around the issue without reinstalling Microsoft Deployment , you can refer to steps given at Microsoft Deployment team blog site.
Thank you for your patience and your diligence in testing Microsoft Deployment. Please make sure to submit bug reports on Connect Feedback site.
A new update for the Microsoft Deployment Toolkit is currently under development. This new version will provide new capabilities such as:
Want to know more about these new capabilities? You can find out more at next week’s MMS 2010 conference sessions:
BG01: MDT 2010 Update 1 + ConfigMgr 2007 OSD: Even More “Better Together” Thursday, April 22 – 2:30 PM-3:45 PM Veronese 2501A
OE01: Ask the Experts: Microsoft Deployment Toolkit (MDT) 2010 Tuesday, April 20 – 5:30 PM-6:30 PM Marco Polo 702
Want to be notified when the beta version of MDT 2010 Update 1 is available? Sign up today at the Connect website using the following instructions and you’ll receive an e-mail as soon as it is available:
1. Access http://connect.microsoft.com.
2. Sign on using any valid Live ID.
3. From the Connection Directory, find the “Solution Accelerators” connection.
4. Apply for the “Microsoft Deployment Toolkit” program. Approval is automatic.
The Solution Accelerators team is pleased to announce Microsoft Deployment Toolkit (MDT) 2012 Beta 2 is available for download on Connect now.
New features and enhancements make large-scale desktop and server deployments smoother than ever! For System Center Configuration Manager customers, MDT 2012 Beta 2 provides an improved, extensible wizard and designer for customizing deployment questions. MDT 2012 makes full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment. MDT 2012 integrates with configuration templates from the Security Compliance Manager (SCM) tool to ensure a secure Windows installation from the beginning of the deployment. Download the latest version of MDT and improve your deployment experience. Existing MDT users will find more reliability and flexibility with the many small enhancements and bug fixes and a smooth and simple upgrade process.
The latest version of MDT offers new User-Driven Installation components and extensibility for Configuration Manager 2007 and Configuration Manager 2012. MDT 2012 offers integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for Lite Touch Installation remote control and diagnostics. Beta users now also have the ability to migrate MDT 2012 task sequences from Configuration Manager 2007 to Configuration Manager 2012. MDT 2012 offers improved support for Configuration Manager 2012 while still supporting Configuration Manager 2007. New monitoring capabilities for currently running deployments ease Lite Touch Installation through an improved deployment wizard user experience, and enhanced partitioning support ensures that deployments work regardless of the current structure.
For System Center Configuration Manager customers:
For Lite Touch Installation:
For all customers:
Join the MDT 2012 Beta 2.
Tell us what you think! Test drive our beta release and send us your constructive feedback. We value your input; this is the perfect opportunity to be heard. The MDT 2012 Beta 2 will be available for beta download through January 2012.
Tell your peers and customers about Solution Accelerators! Please forward this to anyone who wants to learn more about OS deployment with MDT, and Microsoft Solution Accelerators.
Already using the Microsoft Deployment Toolkit? We’d like to hear about your experiences. Please send comments and suggestions to satfdbk@microsoft.com.
Microsoft Deployment Toolkit Team Blog
Deployment TechCenter
Business Desktop Deployment (BDD) and Microsoft Deployment Toolkit (MDT) Archive
Microsoft System Center
Microsoft Solution Accelerators
In addition to all the Microsoft Deployment Toolkit-related sessions being conducted by the MDT team listed in a previous posting, there are several additional ones that you will want to check out during the week:
BF33 WDS Internals - Mastering the Windows Deployment Service Monday, April 19 3:00 PM - 4:15 PM, Titian 2301A Speaker: Johan Arwidmark
Johan will show how to use, configure, and troubleshoot Windows Deployment Services. He will also show how MDT 2010 uses WDS.
BC06 Deploying Windows 7 with MDT 2010: A Demo Extravaganza Monday, April 19 4:30 PM - 5:45 PM, Veronese 2501A Speaker: Richard Smith
Richard will guide you through the whole Windows deployment lifecycle, using MDT for image creation and image deployment – nine hours of demos squeezed into one 75 minute session.
IF06 Deploying Windows Server 2008 R2 with MDT 2010 Tuesday, April 20 11:45 AM - 1:00 PM, Ballroom A Thursday, April 22 2:30 PM - 3:45 PM, Ballroom A Speaker: Joey Snow
In this instructor-led lab, Joey Snow will walk you through the process of deploying Windows Server 2008 R2 using MDT 2010.
BE21 Notes from the Field: MDT 2010 Deployment Scenarios Thursday, April 22 11:45 AM - 1:00 PM, Titian 2301A Speakers: Doug Klokow, Joseph Paradi
Doug and Joseph will show how MDT is being used and customized in real-world Windows 7 deployment projects.
BC33 Building the perfect Master Image using MDT 2010 Friday, April 23 8:30 AM - 9:45 AM, Bellini 2101A Speaker: Johan Arwidmark
Johan will provide tips and tricks to help you create the perfect master image of Windows 7.
BE32 Branch Office hydration using MDT 2010 Friday, April 23 10:00 AM - 11:15 AM, Titian 2303 Speaker: Mikael Nystrom
Mikael will show how to use MDT 2010 to “hydrate” a set of branch office virtual machines using MDT 2010.
For those of you who have already joined the Microsoft Deployment connection and tested the Microsoft Deployment Toolkit (MDT) 2010 Update 1 beta release, thank you so much for your participation.
Please take a moment to share your thoughts and suggestions on your experiences with the features in the software and how to improve them. Download the MDT 2010 Update 1 Beta, and then complete this brief survey before June 22, 2010. You will be automatically entered into the MDT Beta Feedback Survey Sweepstakes and have a chance to win one of four Amazon Gift Cards, each valued at $25 USD. We will also randomly select one winner to receive a $200 USD Amazon Gift Card.
To participate in the MDT 2010 Update 1 Beta survey, please click the following URL:
https://connect.microsoft.com/site14/Survey/Survey.aspx?SurveyID=11098
For those of you who have not yet joined the Microsoft Deployment connection, there is still time to join, download the beta, provide your feedback, and complete the survey. See the details at http://blogs.technet.com/b/msdeployment/archive/2010/05/11/microsoft-deployment-toolkit-2010-update-1-now-in-beta-release.aspx.
Thanks,
Solution Accelerators Team
Sponsor This survey is sponsored by the Microsoft Solution Accelerators Team. You can contact us at satfdbk@microsoft.com.
* For complete sweepstakes rules, please see https://connect.microsoft.com/site14/content/content.aspx?ContentID=17485
Are you passionate about creating software that is essential to the adoption of Microsoft’s “Big bet” products and services such as Windows Azure, the next version of Windows, Office 365, Windows Intune, Hyper-V Cloud, and System Center 2012? Are you seeking an opportunity to join a small startup-oriented, fast-paced, agile team where you will fully leverage your exceptional technical skills towards the task of shaping the vision, planning, engineering and shipping of production-ready software?
The Solution Accelerators Team is seeking a technically sharp, results-driven, customer-focused Senior Software Development Engineer who is looking to make a huge impact on future versions of the Microsoft Deployment Toolkit (www.microsoft.com/mdt) and new client and datacenter related solutions.
For more information, see the full job posting:
https://careers.microsoft.com/jobdetails.aspx?jid=70102
The Microsoft Management Summit 2010 conference kicks off Monday, April 19th in Las Vegas, and the MDT team will be well represented with team members attending and presenting throughout the week. Be sure to check out these break-out sessions, instructor-led labs, and birds-of-a-feather sessions:
IE01 Getting Started with Microsoft Deployment Toolkit 2010 (ILL) Monday, April 19 10:30 AM - 11:45 AM, Ballroom A Tuesday, April 20 2:15 PM - 3:30 PM, Ballroom A Speaker: Mary Anne Blake, Senior Program Manager
A great lab for those just getting started with MDT 2010, walking through many of the common scenarios that IT administrators need to perform.
IE02 Advanced Deployment Scenarios Using the Microsoft Deployment Toolkit 2010 Monday, April 19 1:30 PM - 2:45 PM, Ballroom A Wednesday, April 21 4:00 PM - 5:15 PM, Ballroom A Speaker(s): Rajat Kumar, Senior Program Manager
An in-depth lab for those that know MDT 2010 and want to take it further by leveraging databases, web services, and customized wizards.
OE01 Ask the Experts: Microsoft Deployment Toolkit (MDT) 2010 Tuesday, April 20 5:30 PM - 6:30 PM, Marco Polo 702 Moderator: Michael Niehaus, Senior Software Development Engineer
This is your chance to ask questions to the team that is working on MDT 2010 Update 1 and its new features. Come early to ensure you get a seat.
BC32 A Drivers Saga - The Control Freak meets The Dynamic Developer Wednesday, April 21 11:45 AM - 1:00 PM, Veronese 2405 Speakers: Johan Arwidmark, Consultant; Michael Niehaus, Senior Software Development Engineer
This is the first time Johan (the “Control Freak”) and Michael (the “Dynamic Developer”) have presented together, speaking about techniques for managing drivers for OS deployment.
BC07 Troubleshooting Windows 7 Deployments Thursday, April 22 10:15 AM - 11:30 AM, Bellini 2101A Speakers: Michael Niehaus, Senior Software Development Engineer
Examine some of the common problems encountered when deploying Windows 7, and learn how to troubleshoot these using all the available logs and tools.
BG01 MDT 2010 Update 1 + ConfigMgr 2007 OSD: Even More "Better Together" Thursday, April 22 2:30 PM - 3:45 PM, Veronese 2501A Speakers: Chris Adams, Senior Program Manager Lead; Michael Niehaus, Senior Software Development Engineer
Learn about the new features in MDT 2010 Update 1, including an in-depth overview of the new “User-Driven Installation” deployment scenario for ConfigMgr 2007.
BE04 Enabling Dynamic Windows 7 Deployments with Configuration Manager 2007 and MDT 2010 Thursday, April 22 4:00 PM - 5:15 PM, Veronese 2501A Speaker: Michael Niehaus, Senior Software Development Engineer
Explore how ConfigMgr 2007 and MDT 2010 work together to enhance the Windows 7 deployment process, providing more capabilities without more images or task sequences.
For those attending TechEd North America from June 6th (for pre-conference session) through the 10th, there will be a variety of sessions that feature the Microsoft Deployment Toolkit:
WCL317 | Troubleshooting Microsoft Deployment Toolkit 2010 Lite Touch Wednesday, June 9 | 8:00 AM - 9:15 AM | Rm 276 Speaker: Johan Arwidmark
WCL311 | Migrate Your Windows XP Machines to Windows 7 Using Free Microsoft Deployment Tools Wednesday, June 9 | 1:30 PM - 2:45 PM | Rm 261 Speaker: Rhonda Layfield
WCL403 | Unleash the Power of Microsoft Deployment Toolkit 2010 Wednesday, June 9 | 3:15 PM - 4:30 PM | Rm 356 Speaker: Michael Niehaus
MGT316 | Windows 7 Deployment en Masse Thursday, June 10 | 8:00 AM - 9:15 AM | Auditorium A Speakers: Jason Sandys, Johan Arwidmark
WSV332 | Windows Server 2008 R2 Deployment with Microsoft Deployment Toolkit (MDT) Thursday, June 10 | 9:45 AM - 11:00 AM | Rm 391 Speaker: Mikael Nystrom
If you haven’t yet registered for the conference or for the all-day pre-conferences (including one on Windows 7 deployment, above), there is still time! Access the registration page at http://northamerica.msteched.com/registration for all the details.
In addition to the breakout sessions mentioned previously, there are some interactive sessions involving MDT 2010 that might interest TechEd attendees:
WCL03-INT | Windows 7 Deployments: What's in the Toolbox? (Weapons of Mass Deployment) Monday, June 7 | 2:45 PM - 4:00 PM | Rm 352 Speakers: Jeremy Chapman, Michael Niehaus, Steve Campbell
WCL01-INT | How to Launch and Prepare Information Workers for Windows 7 Tuesday, June 8 | 3:15 PM - 4:30 PM | Rm 352 Speakers: Anthony Smith, Steve Campbell
WCL07-INT | Meet the Deployment Guys Wednesday, June 9 | 9:45 AM - 11:00 AM | Rm 353 Speakers: Jeremy Chapman, Michael Niehaus, Steve Campbell
These interactive sessions are smaller and more intimate, allowing you to bring your own questions and drive the discussion however you see fit. The first session is designed to explore all the various Windows 7 deployment tools that are available, the second will focus on preparing users for the new Windows 7 features, while the last session should be open to any Windows and Office deployment topic.
In addition to these interactive sessions and the previous list of breakout sessions, also check out this session:
WCL205 | Windows 7 Deployment Tips from Early Adopters Tuesday, June 8 | 1:30 PM - 2:45 PM | Auditorium A Speakers: Baldwin Ng, Bruce Jones, Eric Craig, Jeremy Chapman, Juan Gaviria, Stephen Rose
That session will focus on the experiences of customers that are already deploying Windows 7 in their enterprises.
Because application compatibility is always a big concern for enterprises, you may also want to attend these:
WCL204 | What Everyone Should Know about Application Compatibility Monday, June 7 | 2:45 PM - 4:00 PM | Auditorium C Speakers: Aaron Margosis, Chris Jackson
WCL319 | What You Need to Know about Migrating from Internet Explorer 6 to Internet Explorer 8 Tuesday, June 8 | 3:15 PM - 4:30 PM | Rm 387 Speakers: Chris Jackson, Matt Heller
WCL401 | Inside the Application Compatibility Toolkit 5.6: Finding, Testing, and Fixing Applications on Windows 7 Wednesday, June 9 | 9:45 AM - 11:00 AM | Rm 287 Speaker: Chris Jackson
WCL301 | Case of the App Compat Bug Wednesday, June 9 | 11:45 AM - 1:00 PM | Rm 295 Speaker: Aaron Margosis
See you in New Orleans.
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
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.
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 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. 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 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 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
Some of your favorite deployment guys including Ben Hunter, Richard Smith, Adam Shepherd, Daniel Oxley and more have teamed up to create a blog called Deployment Guys. They are just getting started but already have some good information on their blog. Make sure you subscribe to:
http://blogs.technet.com/deploymentguys