Using the Microsoft Deployment Toolkit | Installation (Computer Programs) | Operating System

Microsoft Deployment Toolkit 2010 Update 1

®

Using the Microsoft Deployment Toolkit

Published: July 2010 For the latest information, please see microsoft.com/technet/SolutionAccelerators.

The information in this document and any document referenced herein is provided for informational purposes only, is provided AS IS AND WITH ALL FAULTS and cannot be understood as substituting for customized service and information that might be developed by Microsoft Corporation for a particular user based upon that user’s particular environment. RELIANCE UPON THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN IS AT THE USER’S OWN RISK. © 2010 Microsoft Corporation. All rights reserved. If the user of this work is using the work SOLELY FOR NON-COMMERCIAL PURPOSES INTERNALLY WITHIN A COMPANY OR ORGANIZATION, then this work is licensed under the Creative Commons Attribution-NonCommercial License. To view a copy of this license, visit http://creativecommons.org/licenses/bync/2.5 or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. MICROSOFT CORPORATION PROVIDES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION CONTAINED IN THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN. Microsoft Corporation provides no warranty and makes no representation that the information provided in this document or any document referenced herein is suitable or appropriate for any situation, and Microsoft Corporation cannot be held liable for any claim or damage of any kind that users of this document or any document referenced herein may suffer. Your retention of and/or use of this document and/or any document referenced herein constitutes your acceptance of these terms and conditions. If you do not accept these terms and conditions, Microsoft Corporation does not provide you with any right to use any part of this document or any document referenced herein. Complying with the applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights or other intellectual property rights covering subject matter within this document. Except as provided in any separate written license agreement from Microsoft, the furnishing of this document does not give you, the user, any license to these patents, trademarks, copyrights or other intellectual property. Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Microsoft, Access, Active Directory, ActiveX, BitLocker, Excel, Hyper-V, Internet Explorer, Outlook, Silverlight, SQL Server, Visual Basic, Visual C++, Windows, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

3

Contents

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

4

Introduction to Using the Microsoft Deployment Toolkit...............................................1

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

5

Feedback......................................................................................................................4

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

6

Planning MDT 2010 Deployments.....................................................................................5

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

7

Overview of the MDT 2010 Deployment Process.........................................................5

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

8

Planning Checklist.........................................................................................................6

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

9

Estimating MDT 2010 Storage Requirements...............................................................8

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

10

Estimating Storage Requirements for Computers Running MDT 2010

8

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

11

Estimating Storage Requirements for MDT 2010 Deployment Shares

8

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

12

Estimating Storage Requirements for System Center Configuration Manager Distribution Points 10

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

13

Estimating Storage Requirements for User State Migration Data

10

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

14

Estimating Storage Requirements for Target Computer Backup 11

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

15

Planning for Application Deployment..........................................................................12

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

16

Defining Operating System Components and Settings...............................................12

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

..............................com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 17 Choosing a Deployment Method................................13 Solution Accelerators microsoft..............

.................com/technet/SolutionAccelerators ..........................................13 Solution Accelerators microsoft...............Using the Microsoft Deployment Toolkit: Contents 18 Evaluating Network Requirements......

.Using the Microsoft Deployment Toolkit: Contents 19 Using Reference Computers in MDT 2010 Deployments......com/technet/SolutionAccelerators ...................................14 Solution Accelerators microsoft...

.................. Thin........Using the Microsoft Deployment Toolkit: Contents 20 Choosing Thick.......15 Solution Accelerators microsoft................. or Hybrid Images..com/technet/SolutionAccelerators .....................

.Using the Microsoft Deployment Toolkit: Contents 21 Identifying Deployment Scenarios........................17 Solution Accelerators microsoft.............com/technet/SolutionAccelerators ...........................................

...........Using the Microsoft Deployment Toolkit: Contents 22 Planning for BitLocker Drive Encryption.........................18 Solution Accelerators microsoft........com/technet/SolutionAccelerators ............................

..Using the Microsoft Deployment Toolkit: Contents 23 Evaluating Target Computer Readiness........................................com/technet/SolutionAccelerators ............19 Solution Accelerators microsoft..................

Using the Microsoft Deployment Toolkit: Contents 24 Verify Target Computer Readiness for Running MDT 2010 Scripts 19 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 25 Verify Adequate Target Computer Resources 19 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 26 Identify Differences in 64-bit and 32-bit Deployments 20 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.....21 Solution Accelerators microsoft...........................Using the Microsoft Deployment Toolkit: Contents 27 Planning Performance and Power Management................com/technet/SolutionAccelerators ..........

..........................................Using the Microsoft Deployment Toolkit: Contents 28 Planning Target Computer Security...................22 Solution Accelerators microsoft..........com/technet/SolutionAccelerators ........

..... ZTI......................22 Solution Accelerators microsoft.................. or UDI Deployments.....Using the Microsoft Deployment Toolkit: Contents 29 Choosing LTI.....com/technet/SolutionAccelerators ..................

25 Solution Accelerators microsoft....Using the Microsoft Deployment Toolkit: Contents 30 Reviewing Known Issues..... Limitations.. and Recommendations for MDT 2010.com/technet/SolutionAccelerators ...

Using the Microsoft Deployment Toolkit: Contents 31 Review General Known Issues. and Recommendations for MDT 2010 26 Solution Accelerators microsoft. Limitations.com/technet/SolutionAccelerators .

Limitations.com/technet/SolutionAccelerators . and Recommendations That Relate to Windows 7 31 Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Contents 32 Review Known Issues.

and Recommendations that Relate to Disks and Partitioning 33 Solution Accelerators microsoft. Limitations.Using the Microsoft Deployment Toolkit: Contents 33 Review Known Issues.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 34 Review Known Issues.com/technet/SolutionAccelerators . Limitations. and Recommendations That Relate to BitLocker Drive Encryption 34 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 35 Review Known Issues. Limitations. and Recommendations for LTI Deployments 35 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 36 Review Known Issues.com/technet/SolutionAccelerators . Limitations. and Recommendations for ZTI Deployments 35 Solution Accelerators microsoft.

Limitations. and Recommendations for the Upgrade Computer Deployment Scenario 36 Solution Accelerators microsoft.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 37 Review Known Issues.

Using the Microsoft Deployment Toolkit: Contents 38 Review Known Issues. and Recommendations for Running Task Sequences on Target Computers 36 Solution Accelerators microsoft.com/technet/SolutionAccelerators . Limitations.

Using the Microsoft Deployment Toolkit: Contents 39 Review Known Issues. Limitations. and Recommendations for Saving and Restoring User Information37 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

....................................com/technet/SolutionAccelerators ..Using the Microsoft Deployment Toolkit: Contents 40 Installing or Upgrading to MDT 2010..............................38 Solution Accelerators microsoft............

...............Using the Microsoft Deployment Toolkit: Contents 41 Reviewing Known Issues...........38 Solution Accelerators microsoft................................................. Limitations..com/technet/SolutionAccelerators . and Recommendations for Installing or Upgrading to MDT 2010....................

.....com/technet/SolutionAccelerators ......................................Using the Microsoft Deployment Toolkit: Contents 42 Installing a New Instance of MDT 2010.......39 Solution Accelerators microsoft......................

......................................................39 Solution Accelerators microsoft.............com/technet/SolutionAccelerators ..........................Using the Microsoft Deployment Toolkit: Contents 43 Upgrading to MDT 2010...

..............com/technet/SolutionAccelerators ..................Using the Microsoft Deployment Toolkit: Contents 44 Checking for Updates to MDT 2010 Components...............40 Solution Accelerators microsoft.........

..........com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 45 Performing LTI Deployments.42 Solution Accelerators microsoft...........................................................................

..................................com/technet/SolutionAccelerators ...Using the Microsoft Deployment Toolkit: Contents 46 Preparing the LTI Deployment Environment.........................42 Solution Accelerators microsoft...

Using the Microsoft Deployment Toolkit: Contents 47 Install or Upgrade to MDT 2010 for LTI Deployments 42 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 48 Install Components Required by MDT 2010 and LTI 44 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 49 Obtain the Software Required by the LTI Deployment Process 45 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.................Using the Microsoft Deployment Toolkit: Contents 50 Preparing for LTI Deployment to the Reference Computer...........com/technet/SolutionAccelerators .46 Solution Accelerators microsoft..............

47 Solution Accelerators microsoft.........Using the Microsoft Deployment Toolkit: Contents 51 Deploying to and Capturing an Image of the Reference Computer in LTI.....com/technet/SolutionAccelerators ......

Using the Microsoft Deployment Toolkit: Contents 52 Create the LTI Bootable Media 48 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 53 Complete the Windows Deployment Wizard 48 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 54 Add the Captured Image of the Reference Computer to Deployment Workbench 50 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

......................Using the Microsoft Deployment Toolkit: Contents 55 Preparing for LTI Deployment to Target Computers.com/technet/SolutionAccelerators ..............................50 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 56 Prepare for the New Computer Deployment Scenario to Target Computers Using LTI 51 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 57 Prepare for a Refresh Computer Deployment Scenario to Target Computers Using LTI 52 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 58 Prepare for a Replace Computer Deployment Scenario to Target Computers Using LTI 53 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 59 Prepare for an Upgrade Computer Deployment Scenario to Target Computers Using LTI 55 Solution Accelerators microsoft.

.........................Using the Microsoft Deployment Toolkit: Contents 60 Deploying Captured Images to Target Computers in LTI.......56 Solution Accelerators microsoft........com/technet/SolutionAccelerators ......

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 61 Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using LTI 57 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 62 Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using LTI 57 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 63 Deploy Captured Images to Target Computers in the Replace Computer Deployment Scenario Using LTI 58 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 64 Deploy Captured Images to Target Computers in the Upgrade Computer Deployment Scenario Using LTI 61 Solution Accelerators microsoft.

.......Using the Microsoft Deployment Toolkit: Contents 65 Managing LTI Deployments in Deployment Workbench........................com/technet/SolutionAccelerators ....63 Solution Accelerators microsoft..............

..........Using the Microsoft Deployment Toolkit: Contents 66 Managing Deployment Shares in Deployment Workbench........63 Solution Accelerators microsoft....com/technet/SolutionAccelerators .....................

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 67 Create a New Deployment Share in Deployment Workbench 64 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 68 Open an Existing Deployment Share in Deployment Workbench 66 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 69 Upgrade an Existing Deployment Share in Deployment Workbench 67 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 70 Configure a Deployment Share in Deployment Workbench 70 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 71 Copy a Deployment Share 84 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 72 Close a Deployment Share in Deployment Workbench84 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 73 Update a Deployment Share in Deployment Workbench 85 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 74 Create Bootable Devices from MDT 2010 Boot Images 87 Solution Accelerators microsoft.

.............com/technet/SolutionAccelerators .88 Solution Accelerators microsoft..............Using the Microsoft Deployment Toolkit: Contents 75 Configuring Operating Systems in Deployment Workbench.............

....................95 Solution Accelerators microsoft......com/technet/SolutionAccelerators ...........Using the Microsoft Deployment Toolkit: Contents 76 Configuring Applications in Deployment Workbench................

Using the Microsoft Deployment Toolkit: Contents 77 Create a New Application in Deployment Workbench 96 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 78 View and Configure an Application in Deployment Workbench 101 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 79 Copy an Application in Deployment Workbench 108 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 80 Move an Application in Deployment Workbench 108 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 81 Rename an Application in Deployment Workbench 109 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 82 Delete an Application from Deployment Workbench 109 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 83 Manage Folders for Applications in Deployment Workbench 109 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 84 Enable or Disable an Application in Deployment Workbench 109 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 85 Prevent an Application from Being Visible in the Windows Deployment Wizard 109 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 86 Configure the Computer to Restart After Application Installation 109 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 87 Customize Application Installation in Task Sequences 110 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

........................113 Solution Accelerators microsoft.com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 88 Configuring Packages in Deployment Workbench......................

Using the Microsoft Deployment Toolkit: Contents 89 Import a New Package into Deployment Workbench 114 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 90 Modify an Existing Package in Deployment Workbench 115 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 91 Copy a Package in Deployment Workbench 117 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 92 Move a Package in Deployment Workbench 117 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 93 Rename a Package in Deployment Workbench 117 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 94 Delete a Package from Deployment Workbench 117 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 95 Manage Folders for Packages in Deployment Workbench 118 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 96 Enable or Disable a Package in Deployment Workbench 118 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 97 Prevent a Package from Being Visible in the Windows Deployment Wizard 118 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 98 Customize Package Installation in Task Sequences 118 Solution Accelerators microsoft.

.............com/technet/SolutionAccelerators ...........................Using the Microsoft Deployment Toolkit: Contents 99 Configuring Device Drivers in Deployment Workbench....121 Solution Accelerators microsoft..

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 100 Import Device Drivers into Deployment Workbench 122 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 101 Modify Existing Device Drivers in Deployment Workbench 123 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 102 Copy Device Drivers in Deployment Workbench 126 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 103 Move Device Drivers in Deployment Workbench 126 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 104 Rename Device Drivers in Deployment Workbench 127 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 105 Delete Device Drivers from Deployment Workbench 127 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 106 Manage Folders for Device Drivers in Deployment Workbench 127 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 107 Enable or Disable Device Drivers in Deployment Workbench 127 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 108 Deploy Specific Device Drivers to Target Computers in LTI 127 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 109 Configuring Task Sequences in Deployment Workbench...........com/technet/SolutionAccelerators ..........127 Solution Accelerators microsoft......................

Using the Microsoft Deployment Toolkit: Contents 110 Create a New Task Sequence in Deployment Workbench 128 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 111 Modify an Existing Task Sequence in Deployment Workbench 132 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 112 Copy Task Sequences in Deployment Workbench 141 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 113 Move Task Sequences in Deployment Workbench 141 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 114 Rename Task Sequences in Deployment Workbench 141 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 115 Delete Task Sequences from Deployment Workbench 141 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 116 Manage Folders for Task Sequences in Deployment Workbench 141 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 117 Enable or Disable a Task Sequence in Deployment Workbench 142 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 118 Prevent a Task Sequence from Being Visible in the Windows Deployment Wizard 142 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 119 Modify the Unattended Setup Answer File Associated with the Task Sequence 142 Solution Accelerators microsoft.

..................com/technet/SolutionAccelerators ...142 Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Contents 120 Performing Common Management Tasks in Deployment Workbench..

Using the Microsoft Deployment Toolkit: Contents 121 Manage Folders in Deployment Workbench 143 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 122 View Item Properties in Deployment Workbench 146 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 123 Copy Items in Deployment Workbench 147 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 124 Move Items in Deployment Workbench 148 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 125 Rename Items in Deployment Workbench 150 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 126 Delete Items from Deployment Workbench 151 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.................com/technet/SolutionAccelerators ..Using the Microsoft Deployment Toolkit: Contents 127 Performing Advanced Configuration Tasks in Deployment Workbench.153 Solution Accelerators microsoft..

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 128 Manage Selection Profiles 153 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 129 Manage Linked Deployment Shares159 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 130 Manage MDT 2010 Deployment Media 165 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 131 Manage the MDT DB 184 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

....................Using the Microsoft Deployment Toolkit: Contents 132 Configuring LTI Task Sequence Steps in Deployment Workbench.com/technet/SolutionAccelerators ...184 Solution Accelerators microsoft.....

Using the Microsoft Deployment Toolkit: Contents 133 Configure Task Sequence Step Conditions 185 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 134 Configure Disk Task Sequence Steps 191 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 135 Configure Network Task Sequence Steps 195 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 136 Configure Server Role Task Sequence Steps for LTI 201 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 137 Configure the Check Bios Task Sequence Step for the List of Incompatible BIOS Versions 201 Solution Accelerators microsoft.

..........................................com/technet/SolutionAccelerators ...........203 Solution Accelerators microsoft......Using the Microsoft Deployment Toolkit: Contents 138 Running the Windows Deployment Wizard........

.......com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 139 Performing ZTI Deployments Using System Center Configuration Manager...216 Solution Accelerators microsoft..

....Using the Microsoft Deployment Toolkit: Contents 140 Preparing the ZTI Deployment Environment.216 Solution Accelerators microsoft..............com/technet/SolutionAccelerators ............................................

Using the Microsoft Deployment Toolkit: Contents 141 Prepare the Prerequisite Infrastructure for ZTI Deployments 216 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 142 Install or Upgrade to MDT 2010 for ZTI Deployments 217 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 143 Obtain the Software Required by the ZTI Deployment Process 218 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 144 Enable Configuration Manager Console Integration 218 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.............219 Solution Accelerators microsoft.........com/technet/SolutionAccelerators ...............Using the Microsoft Deployment Toolkit: Contents 145 Preparing for ZTI Deployment to the Reference Computer...

..Using the Microsoft Deployment Toolkit: Contents 146 Deploying to and Capturing an Image of the Reference Computer in ZTI........com/technet/SolutionAccelerators ......220 Solution Accelerators microsoft..

.........................220 Solution Accelerators microsoft....Using the Microsoft Deployment Toolkit: Contents 147 Preparing for ZTI Deployment to Target Computers.com/technet/SolutionAccelerators .....................

Using the Microsoft Deployment Toolkit: Contents 148 Prepare for the New Computer Deployment Scenario to Target Computers Using ZTI 221 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 149 Prepare for the Refresh Computer Deployment Scenario to Target Computers Using ZTI 222 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 150 Prepare for the Replace Computer Deployment Scenario to Target Computers Using ZTI 223 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

......225 Solution Accelerators microsoft..................com/technet/SolutionAccelerators .....Using the Microsoft Deployment Toolkit: Contents 151 Deploying Captured Images to Target Computers in ZTI...............

Using the Microsoft Deployment Toolkit: Contents 152 Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using ZTI 226 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 153 Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using ZTI 227 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 154 Deploy Captured Images to Target Computers in the Replace Computer Deployment Scenario Using ZTI 228 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 155 Managing ZTI Deployments in Configuration Manager Console..............230 Solution Accelerators microsoft...........com/technet/SolutionAccelerators ........

.Using the Microsoft Deployment Toolkit: Contents 156 Creating a ZTI Task Sequence Using MDT 2010 Task Sequence Templates........231 Solution Accelerators microsoft...com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 157 Identify the ZTI Task Sequence Templates in MDT 2010 231 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 158 Identify the Packages and Images Required by the MDT 2010 Task Sequence Templates 232 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 159 Create ZTI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard234 Solution Accelerators microsoft.

com/technet/SolutionAccelerators ....................Using the Microsoft Deployment Toolkit: Contents 160 Managing Operating Systems in Configuration Manager Console..246 Solution Accelerators microsoft.......

...com/technet/SolutionAccelerators ............246 Solution Accelerators microsoft...........Using the Microsoft Deployment Toolkit: Contents 161 Managing Device Drivers in Configuration Manager Console..........

Using the Microsoft Deployment Toolkit: Contents 162 Import Drivers into System Center Configuration Manager 247 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 163 Create a New Driver Package 247 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 164 Add Device Drivers to Operating System and Boot Images 247 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 165 Deploy Specific Device Drivers to Target Computers in ZTI 248 Solution Accelerators microsoft.

..Using the Microsoft Deployment Toolkit: Contents 166 Deploying an Operating System Using Task Sequence Bootable Media....com/technet/SolutionAccelerators ...........248 Solution Accelerators microsoft...

...com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 167 Creating Task Sequence Bootable Media..........................................249 Solution Accelerators microsoft...............

.............................249 Solution Accelerators microsoft...com/technet/SolutionAccelerators .............................................Using the Microsoft Deployment Toolkit: Contents 168 Creating ZTI Boot Images..............

......com/technet/SolutionAccelerators .......251 Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Contents 169 Managing Software Packages in Configuration Manager Console...............

Using the Microsoft Deployment Toolkit: Contents 170 Add Language Packs 252 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 171 Add Software Updates 253 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.....Using the Microsoft Deployment Toolkit: Contents 172 Managing Advertisements in Configuration Manager Console...............255 Solution Accelerators microsoft....com/technet/SolutionAccelerators ...........

...........................................com/technet/SolutionAccelerators .............255 Solution Accelerators microsoft....Using the Microsoft Deployment Toolkit: Contents 173 Manually Adding Computers to the Site Database in Configuration Manager Console ........................................................................

.255 Solution Accelerators microsoft........Using the Microsoft Deployment Toolkit: Contents 174 Managing Computer Collections in Configuration Manager Console...............com/technet/SolutionAccelerators .

........256 Solution Accelerators microsoft.........com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 175 Managing Distribution Points in Configuration Manager Console.......

.....256 Solution Accelerators microsoft......com/technet/SolutionAccelerators ...Using the Microsoft Deployment Toolkit: Contents 176 Configuring ZTI Task Sequence Steps in Configuration Manager Console..

..............................257 Solution Accelerators microsoft.........Using the Microsoft Deployment Toolkit: Contents 177 Configuring Server Role Task Sequence Steps for ZTI.com/technet/SolutionAccelerators ......

.................................258 Solution Accelerators microsoft...............................................com/technet/SolutionAccelerators ....Using the Microsoft Deployment Toolkit: Contents 178 Performing UDI Deployments.....

.........com/technet/SolutionAccelerators ..............258 Solution Accelerators microsoft.......Using the Microsoft Deployment Toolkit: Contents 179 Preparing the UDI Deployment Environment................................

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 180 Prepare the Prerequisite Infrastructure for UDI Deployments 258 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 181 Install or Upgrade to MDT 2010 for UDI Deployments 259 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 182 Obtain the Software Required by the UDI Deployment Process 260 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 183 Enable Configuration Manager Console Integration for UDI 260 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 184 Install and Configure the UDI Web Service 261 Solution Accelerators microsoft.

..............265 Solution Accelerators microsoft...........Using the Microsoft Deployment Toolkit: Contents 185 Preparing for UDI Deployment to the Reference Computer...........com/technet/SolutionAccelerators ....

..Using the Microsoft Deployment Toolkit: Contents 186 Deploying to and Capturing an Image of the Reference Computer Using UDI......com/technet/SolutionAccelerators .267 Solution Accelerators microsoft..

...........267 Solution Accelerators microsoft....................com/technet/SolutionAccelerators ..........Using the Microsoft Deployment Toolkit: Contents 187 Preparing for UDI Deployment to Target Computers.........

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 188 Prepare for the New Computer Deployment Scenario to Target Computers Using UDI 268 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 189 Prepare for the Refresh Computer Deployment Scenario to Target Computers Using UDI 270 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

........271 Solution Accelerators microsoft..............................Using the Microsoft Deployment Toolkit: Contents 190 Deploying Captured Images to Target Computers in UDI...com/technet/SolutionAccelerators ..

Using the Microsoft Deployment Toolkit: Contents 191 Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using UDI 272 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 192 Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using UDI 273 Solution Accelerators microsoft.

..................com/technet/SolutionAccelerators .275 Solution Accelerators microsoft......................................................Using the Microsoft Deployment Toolkit: Contents 193 Managing UDI Deployments...................

.Using the Microsoft Deployment Toolkit: Contents 194 Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates.com/technet/SolutionAccelerators ....276 Solution Accelerators microsoft......

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 195 Identify the UDI Task Sequence Templates in MDT 2010 276 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 196 Identify the Packages and Images Required by the UDI Task Sequence Templates 277 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 197 Create UDI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard277 Solution Accelerators microsoft.

........com/technet/SolutionAccelerators ..Using the Microsoft Deployment Toolkit: Contents 198 Configure the Operating System Deployment (OSD) Setup Wizard Behavior.288 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 199 Create a New Operating System Deployment (OSD) Setup Wizard Configuration File 290 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 200 Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File 290 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 201 Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service 291 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 202 Publish an Operating System Deployment (OSD) Setup Wizard Configuration File to a UDI Web Service 292 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 203 Override the Configuration File Used by the Operating System Deployment (OSD) Setup Wizard 293 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 204 Configure the Welcome Page Behavior Using the UDI Wizard Designer 293 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 205 Configure the Preflight Page Behavior Using the UDI Wizard Designer 295 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 206 Configure the Computer Page Behavior Using the UDI Wizard Designer 298 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 207 Configure the User Configuration Page Behavior Using the UDI Wizard Designer 303 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 208 Configure the Language Page Behavior Using the UDI Wizard Designer 305 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 209 Configure the Volume Page Behavior Using the UDI Wizard Designer 309 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 210 Configure Application Discovery Preflight Check Behavior 312 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 211 Configure Software Installation Behavior Using the Settings and Categories Page in the UDI Wizard Designer 314 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 212 Configure Software Installation Behavior Using the Package Selection Page in the UDI Wizard Designer 316 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 213 Configure Software Installation Behavior Using the OSD Applications Page Behavior in the UDI Wizard Designer 318 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 214 Configure the Summary Page Behavior Using the UDI Wizard Designer 324 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 215 Preview the Operating System Deployment (OSD) Setup Wizard Behavior Using the UDI Wizard Designer 326 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

......com/technet/SolutionAccelerators .................327 Solution Accelerators microsoft..Using the Microsoft Deployment Toolkit: Contents 216 Running the Operating System Deployment (OSD) Setup Wizard.....

.....com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 217 Configuring MDT 2010 Deployments........338 Solution Accelerators microsoft..........................................................

.....Using the Microsoft Deployment Toolkit: Contents 218 Customizing MDT 2010 Configuration Files...........338 Solution Accelerators microsoft............com/technet/SolutionAccelerators ....................................

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 219 Identify the CustomSettings.ini File Syntax 339 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 220 Sections in the CustomSettings.ini File 340 Solution Accelerators microsoft.

ini File 340 Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Contents 221 Properties in the CustomSettings.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 222 Basic CustomSettings.com/technet/SolutionAccelerators .ini File for LTI Deployments 343 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 223 Basic CustomSettings.com/technet/SolutionAccelerators .ini File for ZTI Deployments 345 Solution Accelerators microsoft.

ini File Syntax 349 Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Contents 224 Identify the BootStrap.com/technet/SolutionAccelerators .

...........com/technet/SolutionAccelerators .................349 Solution Accelerators microsoft..........Using the Microsoft Deployment Toolkit: Contents 225 Configuring the Appropriate MDT 2010 Properties...............

351 Solution Accelerators microsoft.............com/technet/SolutionAccelerators .............................Using the Microsoft Deployment Toolkit: Contents 226 Applying MDT 2010 Properties to Groups of Computers..

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 227 Select the Method for Grouping Computers 351 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents

228

Apply the Properties to the Groups 353

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

229

Applying MDT 2010 Properties to Individual Computers..........................................354

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

230

Configuring MDT 2010 Processing Rules.................................................................356

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

231

Configure the Rules in the CustomSettings.ini File

356

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

232

Configure the Rules in the MDT DB 356

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

233

Preparing Disks on Target Computers......................................................................357

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

234

Configure Disk Preparation Task Sequence Steps

357

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

235

Configure Disk Preparation Properties

358

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

236

Saving and Restoring User State Information...........................................................359

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

237

Review User State Information Task Sequence Steps 360

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

238

Configure User State Information Properties 360

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

239

Configure User State Migration XML Control Files

361

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

240

Joining Target Computers to AD DS Domains..........................................................362

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

241

Join Domains Using the Windows Deployment Wizard362

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

242

Join Domains by Modifying the CustomSettings.ini File

363

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

243

Join Domains by Modifying the Unattended.xml File

364

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents 244 Join Domains Using the Recover from Domain Join Failure Task Sequence Step Type 364 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 245 Join Domains Using Offline Domain Join 366 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

............366 Solution Accelerators microsoft.................Using the Microsoft Deployment Toolkit: Contents 246 Deploying Software Updates to Target Computers...com/technet/SolutionAccelerators .....................

Using the Microsoft Deployment Toolkit: Contents 247 Select the Software Update Deployment Strategy 367 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 248 Deploy Software Updates with Windows Update Agent for LTI Deployments 367 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 249 Deploy Software Updates with Deployment Workbench for LTI Deployments 367 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 250 Deploy Software Updates with System Center Configuration Manager for ZTI Deployments 368 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

................com/technet/SolutionAccelerators ...................................Using the Microsoft Deployment Toolkit: Contents 251 Managing Device Drivers.368 Solution Accelerators microsoft........................................

Using the Microsoft Deployment Toolkit: Contents 252 Select the Device Driver Management Strategy 369 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 253 Control Device Driver Deployments for LTI 370 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 254 Control Device Driver Deployments for ZTI 376 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 255 Resolve Device Driver Signing Issues 378 Solution Accelerators microsoft.

.......379 Solution Accelerators microsoft..com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 256 Configure Server Role Task Sequence Steps for LTI and ZTI..........................

Using the Microsoft Deployment Toolkit: Contents 257 Configure AD DS Server Role Task Sequence Step Settings for LTI and ZTI 379 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 258 Configure DNS Server Role Settings for LTI and ZTI 387 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 259 Configure DHCP Server Role Task Sequence Step Settings for LTI and ZTI 389 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 260 Configure Authorize DHCP Task Sequence Step Settings for LTI and ZTI 393 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

....com/technet/SolutionAccelerators .............Using the Microsoft Deployment Toolkit: Contents 261 Copying Content to the Target Computer..............................................394 Solution Accelerators microsoft.....

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 262 Copy Content to Target Computers Using Task Sequence Steps 394 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 263 Copy Content to Target Computers Using $OEM$ Folders 394 Solution Accelerators microsoft.

.........Using the Microsoft Deployment Toolkit: Contents 264 Creating Custom Scripts for MDT 2010.....com/technet/SolutionAccelerators ..........................396 Solution Accelerators microsoft..............................

Using the Microsoft Deployment Toolkit: Contents 265 Develop Custom Scripts 396 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 266 Create New Scripts from a Template 399 Solution Accelerators microsoft.

..................com/technet/SolutionAccelerators ....................Using the Microsoft Deployment Toolkit: Contents 267 Create Custom Preflight Checks for UDI.....405 Solution Accelerators microsoft.........................

................com/technet/SolutionAccelerators .....Using the Microsoft Deployment Toolkit: Contents 268 Performing Deployments Using the MDT DB....................408 Solution Accelerators microsoft.......................

.408 Solution Accelerators microsoft.......Using the Microsoft Deployment Toolkit: Contents 269 Creating a New MDT DB or Connecting to an Existing MDT DB......com/technet/SolutionAccelerators ..................

Using the Microsoft Deployment Toolkit: Contents 270 Create a New MDT DB 409 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 271 Connect to an Existing MDT DB 413 Solution Accelerators microsoft.

...com/technet/SolutionAccelerators .................414 Solution Accelerators microsoft...................................Using the Microsoft Deployment Toolkit: Contents 272 Upgrading an Existing MDT DB...........................

.......com/technet/SolutionAccelerators .............Using the Microsoft Deployment Toolkit: Contents 273 Assigning the Appropriate Permissions to the MDT DB.....415 Solution Accelerators microsoft.....................

.......................Using the Microsoft Deployment Toolkit: Contents 274 Managing Configuration Settings Stored in the MDT DB................com/technet/SolutionAccelerators .415 Solution Accelerators microsoft....

Using the Microsoft Deployment Toolkit: Contents 275 Manage Configuration Settings Stored in the MDT DB Using Deployment Workbench 416 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 276 Manage Configuration Settings Stored in the MDT DB Using SQL Server Management Tools 420 Solution Accelerators microsoft.

..............com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 277 Configuring the MDT 2010 Deployment Process to Access the MDT DB...421 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 278 Configure Access to the MDT DB Using the Configure DB Wizard 421 Solution Accelerators microsoft.

ini File 430 Solution Accelerators microsoft.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 279 Configure Access to the MDT DB by Directly Modifying the CustomSettings.

...........Using the Microsoft Deployment Toolkit: Contents 280 Extending the Schema of the MDT DB.................................................432 Solution Accelerators microsoft...com/technet/SolutionAccelerators ........

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 281 Determine the Tables and Views to Be Modified 433 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 282 Create a Backup of the MDT DB 433 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 283 Modify the Table 434 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 284 Modify and Refresh the Dependent Views 435 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 285 Reference the New Column in the CustomSettings.ini File 436 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 286 Reference the New Column in a Task Sequence Step 437 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

........................438 Solution Accelerators microsoft...............com/technet/SolutionAccelerators .....................Using the Microsoft Deployment Toolkit: Contents 287 Preparing the MDT 2010 Migration Resources..

................438 Solution Accelerators microsoft.............................Using the Microsoft Deployment Toolkit: Contents 288 Creating Additional Shared Folders....com/technet/SolutionAccelerators ...........................

...........com/technet/SolutionAccelerators ......................................Using the Microsoft Deployment Toolkit: Contents 289 Configuring Shared Folder Permissions......438 Solution Accelerators microsoft..............

..439 Solution Accelerators microsoft............................................com/technet/SolutionAccelerators ..Using the Microsoft Deployment Toolkit: Contents 290 Configuring Access to Other Resources.....................

..........com/technet/SolutionAccelerators .........441 Solution Accelerators microsoft...Using the Microsoft Deployment Toolkit: Contents 291 Preparing Windows Deployment Services..............................................

.com/technet/SolutionAccelerators .......Using the Microsoft Deployment Toolkit: Contents 292 Preparing Windows Deployment Services for LTI Deployments.............441 Solution Accelerators microsoft............

Using the Microsoft Deployment Toolkit: Contents 293 Selecting Windows Deployment Services Operational Mode for LTI Deployments 442 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 294 Add LTI Boot Images to Windows Deployment Services 443 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 295 Pre-stage Target Computers for Windows Deployment Services for LTI Deployments 443 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 296 Enable Windows Deployment Services Multicast Deployment for LTI Deployments 444 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.......Using the Microsoft Deployment Toolkit: Contents 297 Preparing Windows Deployment Services for ZTI Deployments......447 Solution Accelerators microsoft................com/technet/SolutionAccelerators ...

.......447 Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Contents 298 Preparing Windows Deployment Services for UDI Deployments......................com/technet/SolutionAccelerators ..

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 299 Deploying Applications Using MDT 2010 and Microsoft Application Virtualization 448 Solution Accelerators microsoft.

...........com/technet/SolutionAccelerators ....................448 Solution Accelerators microsoft.......................................5..Using the Microsoft Deployment Toolkit: Contents 300 Microsoft Application Virtualization 4.

Using the Microsoft Deployment Toolkit: Contents 301 App-V Components 449 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 302 App-V Limitations 451 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.....................................................com/technet/SolutionAccelerators ....................................452 Solution Accelerators microsoft...Using the Microsoft Deployment Toolkit: Contents 303 Planning..........................

Using the Microsoft Deployment Toolkit: Contents 304 Plan the Infrastructure 453 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 305 Plan the App-V Sequencer Environment 454 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 306 Choose a Deployment Method 454 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 307 Use App-V for Thin Images455 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 308 Plan the Client Deployment 457 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 309 Plan for High Availability 460 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 310 Identify Subject Matter Experts 460 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

Using the Microsoft Deployment Toolkit: Contents 311 Choose Applications to Sequence 460 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

.460 Solution Accelerators microsoft.......................................................................................................com/technet/SolutionAccelerators .....Using the Microsoft Deployment Toolkit: Contents 312 Developing.....

Using the Microsoft Deployment Toolkit: Contents 313 Prepare for Development 461 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 314 Sequence Applications 468 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 315 Deploy the App-V Desktop Client 474 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 316 Deploy Applications 479 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 317 Stabilizing................................................483 Solution Accelerators microsoft................................................com/technet/SolutionAccelerators ....................

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 318 Test the Client Environment 484 Solution Accelerators microsoft.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 319 Test Application Distribution 484 Solution Accelerators microsoft.

..............485 Solution Accelerators microsoft.......................................Using the Microsoft Deployment Toolkit: Contents 320 Deploying.......com/technet/SolutionAccelerators ........................................................

Using the Microsoft Deployment Toolkit: Contents 321 Install App-V Servers at Each Site 486 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 322 Implement the Application Distribution Strategy 486 Solution Accelerators microsoft.

Using the Microsoft Deployment Toolkit: Contents 323 Monitor Key App-V Services 486 Solution Accelerators microsoft.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 324 Monitor Key App-V Services Solution Accelerators microsoft.

com/systemcenter/essentials/en/us/default. For more information about: • • Microsoft System Center Essentials. Only MDT 2010 is used in LTI deployments. Windows applies to the Windows 7. support files.aspx#EFG.com/enus/sce/bb734815. properties.microsoft. Additional MDT 2010 Documents for Use in the Deployment Process Document Microsoft Deployment Toolkit Samples Guide Description Provides scenario-based samples of how to solve common deployment issues using MDT 2010. build. Windows XP Professional. see the product home page at http://www. utilities. and databases used in MDT 2010 deployments. Use this document to help solve difficult deployment problems.aspx. and User Driven Installation (UDI) deployment methods. Table 1 lists other documents that will help you perform deployments using MDT 2010 in your organization. Zero Touch Installation (ZTI). Windows XP Tablet PC Edition. This document covers both deployment methods and shows how to customize the deployment process for an organization.Using the Microsoft Deployment Toolkit: Introduction 1 Introduction to Using the Microsoft Deployment Toolkit Microsoft® Deployment Toolkit (MDT) 2010 Update 1 allows you to automate the deployment of computers in your organization. Provides information about the task sequence steps. Use this document to help customize MDT 2010 deployments for your Toolkit Reference . Windows Server 2008. and Windows Server 2003 operating systems unless otherwise noted. while ZTI and UDI deployments are performed using MDT 2010 and Microsoft System Center Configuration Manager 2007. Windows Vista®. see “Detailed comparison with System Center Configuration Manager 2007” at http://technet. MDT 2010 performs deployments by using the Lite Touch Installation (LTI). Most samples include example configuration files and stepby-step processes for implementing the solution. Differences between System Center Essentials and System Center Configuration Manager. ZTI and UDI deployments require System Center Configuration Manager. You can use Microsoft System Center Essentials 2007 to collect inventory and perform patch management for LTI deployments. This document provides guidance on how to plan. Table 1. Windows Server® 2008 R2.microsoft. and deploy Windows® operating systems and applications using MDT 2010. In addition to this document. Note In this document.

reviewing logs. The following sections in this guide help you perform LTI. building. Provides guidance for deploying Windows operating systems and applications using only MDT 2010. and identifying issues by error code.2 Microsoft Deployment Toolkit 2010 Update 1 Document Troubleshooting Reference Description organization. Sections in This Document Section Planning MDT 2010 Deployments Overview Provides guidance for completing the planning tasks in preparation for MDT 2010 deployments. including lists of known issues. Provides guidance for performing a new installation of MDT 2010 or upgrading to MDT 2010 from previous versions of MDT or Microsoft Business Desktop Deployment (BDD). Table 2 lists each section in this guide. microsoft. Provides guidance of how to run the Windows Deployment Wizard to deploy operating systems.com/technet/SolutionAccelerators Installing or Upgrading to MDT 2010 Performing LTI Deployments Managing LTI Deployments in Deployment Workbench Running the Windows Deployment Wizard Solution Accelerators . and perform any infrastructure remediation prior to deployment in a production environment. perform capacity planning. and other deployment elements in the Deployment Workbench. The guidance presented in this section starts immediately after the installation of MDT 2010 and provides the steps for creating a reference computer. capturing an image of the reference computer. and UDI deployments and customize the deployment process. Review this section to help identify prerequisites. and then deploying the captured image to target computers in the organization. and applications to the target computers in your organization. Table 2. including managing operating systems. applications. Provides guidance and step-by-step instructions for managing LTI deployments using the Deployment Workbench. This document is organized to help you through the planning. and deploying processes in your organization. device drivers. ZTI. with a brief overview of each. Provides information to assist in troubleshooting common problems with MDT 2010 deployments. device drivers. the MDT database (MDT DB). and learn how to install MDT 2010 in the environment.

Managing UDI Deployments • Managing the behavior of the Operating System Deployment (OSD) Setup Wizard. The guidance presented in this section starts immediately after the installation of MDT 2010 and provides the steps for creating a reference computer. applications.Using the Microsoft Deployment Toolkit: Introduction 3 Section Performing ZTI Deployments Using System Center Configuration Manager Overview Provides guidance for deploying Windows operating systems and applications using MDT 2010 and System Center Configuration Manager. and then deploying the captured image to target computers in the organization using System Center Configuration Manager. capturing an image of the reference computer. and the Operating System Deployment (OSD) Setup Wizard. Provides guidance and step-by-step instructions for managing ZTI deployments using the Configuration Manager Console. and the Operating System Deployment (OSD) Setup Wizard. Provides guidance and step-by-step instructions for managing UDI deployments using the Configuration Manager Console. and then deploying the captured image to target computers in the organization using the Configuration Manager Console and the Operating System Deployment (OSD) Setup Wizard. the UDI Wizard Designer. device drivers. microsoft. Note Most of the deployment process and step-by-step instructions for ZTI are applicable to UDI. Managing ZTI Deployments in Configuration Manager Console Performing UDI Deployments Provides guidance for deploying Windows operating systems and applications using MDT 2010. device drivers. System Center Configuration Manager. including: • Managing operating systems. including managing operating systems. and other deployment elements in the Configuration Manager Console. capturing an image of the reference computer.com/technet/SolutionAccelerators Solution Accelerators . and other deployment elements in the Configuration Manager Console. applications. Note Most of the deployment process and step-by-step instructions for ZTI are applicable to UDI. The guidance presented in this section starts immediately after the installation of MDT 2010 and provides the steps for creating a reference computer.

System Center Configuration Manager. Provides guidance on how to customize the process for more advanced deployment scenarios. ZTI. Solution Accelerators microsoft. Please provide feedback on the usefulness of this guide by filling out the survey at http://go.com/technet/SolutionAccelerators . Provides guidance on customizing the process for more advanced deployment scenarios. including creating images and configuring for integration with LTI. Provides guidance on preparing Windows Deployment Services for use in initiating the LTI. device drivers.com/fwlink/?LinkID=132579. including a discussion of the MDT 2010 configuration files. and UDI deployment processes. and UDI deployments. including network shared folders and database access. and applications to the target computers in your organization. including deployment of applications with the operating system image or after the image is deployed. ZTI. how to apply configuration settings to groups of computers. and how to apply configuration settings to individual computers. and Microsoft Application Virtualization (App-V). Provides guidance on preparing the appropriate resources used in the MDT 2010 deployment process. Provides guidance on how to deploy applications by using MDT 2010. including how to add entries to and retrieve configuration settings from the MDT DB.microsoft.com. Performing Deployments Using the MDT DB Preparing the MDT 2010 Migration Resources Preparing Windows Deployment Services Deploying Applications Using MDT 2010 and Microsoft Application Virtualization Feedback Please direct questions and comments about this guide to satfdbk@microsoft.2 Microsoft Deployment Toolkit 2010 Update 1 Section Running the Operating System Deployment (OSD) Setup Wizard Configuring MDT 2010 Deployments Overview Provides guidance of how to run the Operating System Deployment (OSD) Setup Wizard to deploy operating systems.

Figure 1 illustrates the high-level LTI.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 2 Planning MDT 2010 Deployments The planning process helps you prepare for deployments in a production environment. The process starts with conceptual designs. Device drivers for reference and target computers. Overview of the MDT 2010 Deployment Process The purpose of MDT 2010 is to help automate the deployment of Windows operating systems and applications to desktop. At a high level. The result of the planning process is a set of design documents that you can use to build an MDT 2010 deployment infrastructure and perform automated operating system and application deployments in a production environment. High-level deployment process The high-level LTI. portable. ZTI. and UDI deployment process is as follows: 1. Collect the files necessary to perform an MDT 2010 deployment. which are proven and refined in a test environment. MDT 2010 automate the deployment process by configuring the unattended Setup files for Windows and packaging the necessary files into a consolidated image file that you then deploy to reference and target computers. ZTI. . including: • • • Windows operating system source files or images. Figure 1. Windows operating system language packs. and server computers in the environment. and UDI deployment processes.

see Estimating MDT 2010 Storage Requirements. These files can require many gigabytes of space. Small organizations might assign each user an individual product key. For more information. and the target computers. distribution points.com/technet/SolutionAccelerators Will you deploy across the network. If you are deploying across the network. see Using Reference Computers in MDT 2010 Deployment. or both? Will you use multicast deployments? What is your imaging and source file strategy? Will you deploy a full set of operating system files or a custom image? How will you handle product keys and licensing? Solution Accelerators . Deploy the captured images of the reference computers to the target computers. see Using Reference Computers in MDT 2010 Deployment. Deploy the system images to the reference computer and capture an image of the reference computer. Create the system images. For more information. Planning Checklist Table 3 provides a planning checklist in the form of a list of questions that you can use to help in the planning process. see Choosing a Deployment Method and Evaluating Network Requirements. use the information provided in the Overview column to help find answers based on your organization’s requirements. For more information. Larger organizations should use Key Management Service (KMS) or Multiple Activation Key microsoft. Table 3. 5. For more information. 3. 4. Planning Checklist Question Where will you store your distribution files? Overview Files for the operating system and applications are stored in deployment shares for LTI and distribution points for ZTI and UDI. and provide regional distribution points. and task sequences to be used in deploying Windows and applications to the reference computers. For each question.3 Microsoft Deployment Toolkit 2010 Update 1 2. Create the configuration settings and task sequences that will deploy the captured images of the reference computers to the target computers. Some organizations might need multiple deployment shares or distribution points for different regional offices. verify that there is sufficient bandwidth between the deployment shares. with removable media. configuration settings.

migrate settings to a new operating system installation. locale. Estimating MDT 2010 Storage Requirements LTI deployments store the system images. ZTI and UDI deployments store these files on System Center Configuration Manager distribution points. time zone. For more information. For more information.com/licensing/existingcustomers/product-activation. For more information. see Identifying Deployment Scenarios. see Identifying Deployment Scenarios. For more information. deploy a new computer. or UDI Deployments. For more information. see Product Activation and Key Information at http://www. see Planning for Application Deployment. replace an existing computer)? Users can select this information at deployment time.microsoft. and other files in deployment shares.aspx. applications. Ultimate. see Planning for BitLocker Drive Encryption. For more information. For more information. For more information. see Estimating Storage Requirements for Target Computer Backup. and administrative password? Will users upgrade their current computer in place. estimate storage requirements for: Solution Accelerators microsoft. see Estimating MDT 2010 Storage Requirements. see Estimating Storage Requirements for User State Migration Data. or get a new computer? Which users will be able to install which applications? Are you going to migrate user state? Do you want to back up computers before deployment? Do you want to use BitLocker® Drive Encryption? Will you deploy 32-bit and 64bit operating systems? Will you deploy different product editions (such as Professional. For more information. To determine your storage needs. For more information.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 4 Question Overview (MAK) activation. Are you going to allow users to choose their own operating system. applications. or you can configure the information ahead of time. or Business)? What type of deployments will be performed (for example. see Estimating MDT 2010 Storage Requirements. see Choosing LTI. ZTI.

Solution Accelerators microsoft. Free space of 1 GB is required on the drive containing the MDT 2010 program files. such as Windows 7. or Windows Server 2008 R2. Windows Server 2003. Create a unique image for each: • Version of the Windows operating system to be deployed. Windows Vista. A separate image is required for each version of Windows. Each System Center Configuration manager distribution point as described in Estimating Storage Requirements for System Center Configuration Manager Distribution Points. Backing up existing computers prior to deployment for Refresh Computer or Upgrade Computer deployment scenarios as described in Estimating Storage Requirements for Target Computer Backup. Each MDT 2010 deployment share as described in Estimating Storage Requirements for MDT 2010 Deployment Shares.com/technet/SolutionAccelerators . • • Estimating Storage Requirements for Computers Running MDT 2010 The computer running MDT 2010 has the following storage requirements: • At least 4 gigabytes (GB) of free space is required on the drive containing the %TEMP% folder if you will create a media images. language packs. Determine the storage requirements for each of the following items in the deployment share: • • • • Windows operating system Operating system language pack Device drivers Applications Determine the size of each image and the number of images required in the deployment. • Estimating Storage Requirements for MDT 2010 Deployment Shares Ensure that sufficient space is available for storing the operating system images. and device drivers used in the Deployment Workbench. Otherwise.5 Microsoft Deployment Toolkit 2010 Update 1 • • • Computers running MDT 2010 as described in Estimating Storage Requirements for Computers Running MDT 2010. 1 GB of free space is required on the drive containing the %TEMP% folder. User state migration data as described in Estimating Storage Requirements for User State Migration Data. You store these images in the MDT 2010 deployment shares created in the Deployment Workbench.

the HAL is dynamically identified at startup. the operating system core is language neutral. but the localized versions generally provided better support for the local languages. however.” in the Solution Accelerators microsoft. Processor type. you may have a separate image for each localized version of Windows. you can use an English version of Windows with Windows Multilingual User Interface (MUI) packs for each language to be supported. each image is unique for the HAL. Estimating Storage Requirements for System Center Configuration Manager Distribution Points Estimate the storage requirements for System Center Configuration Manager distribution points using the same calculations described in Estimating Storage Requirements for MDT 2010 Deployment Shares. see the section. Most server computers have the MultiProc HAL type. The MUI versions provide more flexibility. If the images are distributed to multiple distribution points. A separate image is required for each edition of Windows. or Datacenter. Ultimate. For Windows Vista and later client operating systems. For Windows XP and Windows Server 2003.” in the section. A localized version of Windows contains only that language. and you add one or more language packs to the operating system core. “Planning ConfigMgr Site Systems for Operating System Deployments. Hardware abstraction layer (HAL) type for Windows XP or Windows Server 2003 target operating systems. Enterprise. • Each localized operating system language version required.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 6 • Edition of the Windows operating system to be deployed. However. For Windows Vista and later operating systems. For more information about planning System Center Configuration Manager distribution points. “Distribution Point. When the target operating system is Windows XP or Windows Server 2003. you will need to create separate images for computers with the Advanced ACPI HAL type. such as Chinese simplified or Japanese. such as Tablet PC. Business. A separate image is required for 32-bit and 64-bit versions of Windows. Instead of using localized versions for Windows XP and Windows Server 2003.com/technet/SolutionAccelerators . the storage requirements apply to each distribution point. Current computer hardware typically has of the following Advanced Configuration and Power Interface (ACPI) HAL types: • • • Advanced ACPI UniProc ACPI MultiProc ACPI • • You can create one Windows XP or Windows Server 2003 image that includes both the UniProc ACPI and MultiProc HAL types.

you can estimate the disk space requirements without actually performing the migration. complete the following tasks to estimate the user state migration storage requirements: • Run Scanstate. Store user state migration data in these locations: • On the local computer to reduce the time to deploy Windows as well as network utilization (recommended) Note This option can be used only in a Refresh Computer scenario. Solution Accelerators microsoft. Determine Storage Requirements for User State Migration Data For planning purposes.com/technet/SolutionAccelerators . you can override this behavior with configuration settings in CustomSettings. which is installed with System Center Configuration Manager.ini.exe in the USMT with the /p option to estimate the size of the user state migration data. Providing the shared folder as an alternate storage location makes the deployment process more reliable. Determining the storage requirements for the user state migration data as described in Determine Storage Requirements for User State Migration Data. Create a share on a server designated during the planning process for holding the USMT store files. the deployment scripts attempt to store the information in a shared folder. designate a shared folder in which the deploy process can store the data.7 Microsoft Deployment Toolkit 2010 Update 1 Configuration Manager Documentation Library. MDT 2010 uses values found in CustomSettings. • Determine Where to Store User State Migration Data After determining the storage requirements for the user state migration data. By using the /p option. determine where to store the data. In the event that there is insufficient disk space for the user state data and new image.ini to locate the user state store folder. • On a shared folder located on a local server to provide a consistent method of storing user state migration data or when local storage is not available If user state migration data will be stored locally on the target computers. However. the process attempts to store user state data on the local hard disk for the Replace Computer and Refresh Computer scenarios. Estimating Storage Requirements for User State Migration Data Estimate the amount of storage required for user state migration data that the Windows User State Migration Tool (USMT) saved during the deployment process by: • Determining whether to store the user state migration data locally on the target computers or network shared folders as described in Determine Where to Store User State Migration Data. By default.

and include the dependent software in the deployment plans. Application portfolios include a list of applications and the compatibility status of each application. so include each profile to be migrated.com/technet/SolutionAccelerators • Solution Accelerators . and the total storage requirement is 1. microsoft. For example. Planning for Application Deployment Applications can be deployed as a part of the operating system image or after the operating system is deployed to the target computer. the number of target computers deployed each day. The storage requirements are a function of the average size of the target computer hard disks. or 80 GB × 100 × 7. modify the MDT 2010 deployment process or use an alternative backup method. perform these tasks: • Create an application portfolio. and you want to retain the data for one week. data must be stored for five days. Note By default. For example.500 GB (3 GB × 5 days × 100 users per day). Keep in mind that there may be several profiles (user name folders) on each target computer. if the average user state migration size is 3 GB. if the average target computer hard disk contains 80 GB of data. and then multiplying that result by the number of users to be migrated during the retention period. the MDT 2010 backup process does not back up multiple partitions. you are deploying 100 computers per day. and the length of time you want to retain the backup. If you need to back up multiple partitions. Applications may have dependencies on other applications. You can create this application portfolio by using software-inventory software such as the Application Compatibility Toolkit (ACT) or the Software Inventory feature in System Center Configuration Manager. The backup process creates an image of the disk volume on which the user state migration data is stored. For example. the storage requirements for backups are 56 terabytes (TB). The purpose of this backup is for recovery of user state migration data.exe tool. not to restore the target computer from the image. Calculate the total capacity required by multiplying the average size of the user state migration data by the number of days to retain the data. you can perform a backup of a target computer before deploying the target operating system.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 8 • View the size of the contents of the folders in the user profile. Identify any dependencies between applications. You perform the backup process in MDT 2010 by using the Imagex. Randomly sample targeted computers to determine a typical amount of storage required to back up the user state migration. Identify these dependencies. 100 users are being migrated each day. Estimating Storage Requirements for Target Computer Backup As an optional step in the deployment process for the Refresh Computer and Upgrade Computer scenarios. In preparation for deployment. an application may rely on Microsoft Office Excel® 2007.

Select the components required for the applications and user roles performed on the target computers. This determination includes optional components in all operating systems. Configuration settings. Identify the users approved to install applications. Applications that require a restart of the operating system after installation require additional configuration. determine which operating system components to include and the settings for these components. Group Policy Software Installation or the Software Deployment feature in System Center Configuration Manager. Select configuration settings that meet the business • • • Solution Accelerators microsoft.9 Microsoft Deployment Toolkit 2010 Update 1 • Determine whether to deploy applications with the operating system image or afterwards. These components include Microsoft ActiveX® Data Objects (ADO) support. • • • Defining Operating System Components and Settings As part of establishing a standardized configuration. For each operating system image. Identify applications that require a restart of the operating system. Install only the components that are required to help reduce the attack surface of the target computer and the image size. fonts. you may decide to remove unnecessary Windows operating system components from desktop and portable computer deployments to reduce the security footprint of those computers. For example. Identify the configuration settings for components included in the images. You can install and run applications on the local computer or deploy them dynamically in a virtualized application environment.com/technet/SolutionAccelerators . Determine whether users will install their applications or if the applications need to be installed by deployment technicians. and the necessary drivers and packages. For more information. you can use any software-deployment software. Windows PE components. Ensure that the user installing the application has the appropriate rights and permissions. server roles in Windows Server operating systems. You can select the components for 32-bit and 64-bit versions of Windows PE. and components to include in Windows Preinstallation Environment (Windows PE). see Configure the Computer to Restart After Application Installation. Select the server roles required for the server computers. such as MDT 2010. such as App-V. determine the: • Operating system components. Install only the server roles that are required to help reduce the attack surface of the target computer and the image size. Determine the appropriate method for running applications. If the application is deployed after the operating system is deployed. You can deploy applications as part of the operating system image or after the operating system is deployed to the target computer. Server roles.

some target computers may connect to an intranet remotely or not at all. Temporarily move the target computers to a staging area where the computers can be deployed. You use Windows PE to start the computer from the media. perform one of the following actions: • Temporarily place the appropriate servers (for example. Media. For more information about target computer security. software. persistent connection to the servers used in the deployment process. such as DVDs or USB flash drives (UFDs). However.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 10 and security requirements of the organization.com/technet/SolutionAccelerators . These servers need to be on adjacent subnets to the target computers to ensure high-speed connectivity to the computers. Select this method when the target computers have high-speed. if you want to initiate LTI. computers must have a high-speed. Store user state migration data locally on the target computers. Use media-based deployments for computers connected by wireless networks or networks with slow or unreliable connectivity. or UDI deployment using Windows Deployment Services and multicast deployment. This method uses a network shared folder in which all the deployment files reside. servers hosting the various shared folders or the server running Windows Deployment Services) closer to the target computers for the duration of the migration. For example. persistent connections to the deployment infrastructure. Choosing a Deployment Method Typically. and migration data to computers. you must enable the appropriate network protocols and traffic. MDT 2010 includes the following methods for deploying operating systems and applications using LTI based on the network connectivity: • Deployment share. you Solution Accelerators microsoft. Note Network-based deployments using MDT 2010 are not supported for wireless networks. and then return them to their original location. Select this method when the target computers may be remotely connected or may not have connectivity at all. persistent connections to the deployment infrastructure. target computers have high-speed. • Evaluating Network Requirements Because of the size of the images being distributed to the target computers (500 megabytes [MB] to 4 GB). If the organization cannot provide sufficient network capacity to deploy images. and then connects to the deployment share to perform the deployment. see Planning Target Computer Security. The target computer starts Windows PE. ZTI. • • • In addition to network capacity. This method creates an image that you can use to perform deployments from removable media. Perform automated deployments locally using media deployments in LTI.

so creating the reference images may take longer. and finally deployed to target computers. and other software. Windows Vista and later operating systems. VMs work well for creating reference images. Thick images are monolithic images that contain core applications.com/technet/SolutionAccelerators . creating reference images using virtual machines (VM) can be more difficult. single-processor computers (with ACPI HALs). and security requirements of the organization. language. and other files.11 Microsoft Deployment Toolkit 2010 Update 1 must enable multicast traffic between the MDT 2010 infrastructure and target computers. or Hybrid Images As part of the planning process. For example. You configure the reference computer to comply with the business. reference images created with Hyper-V™ VMs would work on modern dual-core and hyperthreaded machines (with ACPI UniProc or ACPI MultiProc HALs) but not on older. The types of images you can create fall into these categories: • Thick images. technical. Part of the image-development process is installing core applications and language packs on the reference computer before capturing the disk image. software updates. then captured from the reference computer. capture an image of the reference computer that you can then deploy to the target computers. determine the types of images that you will create. Thin. The MDT 2010 deployment process allows for the creation of customized images that are first deployed to a reference computer. packs. Choosing Thick. device drivers. because the HAL issues are not applicable. For example. Using Reference Computers in MDT 2010 Deployments The MDT 2010 deployment process uses the reference computer as a baseline for the configuration of target computers when the deployment process is complete. • Note VMs typically do not have the same performance as physical computers. Only in rare circumstances will you be able to deploy the images from the Windows distribution media unmodified to the reference and target computers. create customized images that include the Windows operating system. After configuring the reference computer. When creating a reference image for: • Windows XP and Windows Server 2003. MDT 2010 manages the customization of images so that you can create them with less effort and higher levels of automation. language packs. Instead. the Deployment Workbench in MDT 2010 can automatically inject the appropriate device drivers into images. Solution Accelerators microsoft. applications.

as these components are installed separately from the disk image. • Applications and languages are not immediately available after image deployment is complete. • Reduced initial complexity. • Requires less time than thick images to download over network connections. applications. • Requires an increased image maintenance effort. They do require longer installation times. Advantages and Disadvantages of Thick. but they are not as complex to develop and do not require a software-distribution infrastructure. • Potential for increased complexity. • Table 4 lists the advantages and disadvantages of the thick. • Applications and language packs are available immediately after deployment is complete. Thin • Can be more complex to create initially. Disadvantage • Requires more storage for each image. because additional steps are required during image creation. device drivers. because advanced scripting may be required. Thin. • Requires more time to download over network connections than thin or hybrid images. Hybrid images have most of the advantages of thin images. • Can be more complex than a thick image (but not than a thin image) to create. • Requires less time to than Solution Accelerators .Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 12 • Thin images. such as the Software Deployment feature in System Center Configuration Manager. which can raise initial deployment costs. Thin images contain few if any core applications or language packs. because advanced scripting is not typically required. because any updates to operating systems. which typically takes more network transfer time at the computer. • Requires less storage for each image. thin. Hybrid images mix thin and thick image strategies by installing applications and language packs from a network shared folder. Hybrid images. or language packs requires the creation of a new image. • Reduced image maintenance effort. because all applications and language packs are in the image.com/technet/SolutionAccelerators Hybrid • Requires less storage than thick images for each image. microsoft. and Hybrid Images Method Thick Advantage • Can be simpler to deploy. Table 4. and hybrid images types. because the image contains fewer components. • Does not require softwaredistribution software. however.

Deployment Scenarios Solution Accelerators microsoft. the number of computers in each deployment run. because contains fewer components. Large images have more updating. and so on. The disk-imaging technologies that Microsoft provides do not support multicasting. These costs include the time and labor involved in testing the standard image and the applications that might reside inside it in addition to applications applied after deployment. distribution. • Reduced image maintenance • Potential for increased effort. because the image complexity. maintaining.13 Microsoft Deployment Toolkit 2010 Update 1 Method Advantage Disadvantage thick a thick image to because additional steps are download over network required during image connections. Storage costs.com/technet/SolutionAccelerators . network. Higher levels of automation reduce development costs. Network costs include moving disk images to distribution points and to computers. Even if only a small portion of the image is updated. Test costs also include the development time required to stabilize disk images. disk images. costs increase. and storage costs associated with them. The costs associated with building. Test costs. the entire image must be redistributed. and backup images. • Applications and languages are not immediately available after image deployment is complete. • • • As the size of image files increases. Table 5. Storage costs can be significant depending on the number of disk images. migration data. testing. Development costs include creating a well-engineered image to lower future support costs and improve security and reliability. so network costs scale linearly with the number of distribution points you must replicate and the number of computers in the deployment project. advanced scripting (though • Does not require separate not as advanced as in thin software-distribution software. Storage costs include storing the distribution points. and deploying disk images includes: • Development costs. Network costs. images) may be required. Identifying Deployment Scenarios Table 5 lists the deployment scenarios and provides a brief description of each. creation.

22M. Department of Defense standard 5520.S. and applications are retained. wipe the disk partitions of the original computer. The standard format as performed by Windows operating systems does not perform a secure wipe of the disk as defined by U.com/technet/SolutionAccelerators . Include planning decisions for BitLocker Drive Encryption in your environment. No Upgrade Computer Yes Yes Yes Refresh Computer Yes Yes No Replace Computer Yes No No As part of the Replace Computer deployment scenario. The existing user state migration data is saved from the original computer. If required. Then.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 14 Scenario Description Migrates user state Uses existing target computer No Preserves file system No New Computer A new installation of a Windows operating system is deployed to a new computer. a new installation of Windows is deployed to a new computer. user profile. perform secure wipes of hard disks in target computers using tools provided by non-Microsoft vendors. The existing user state migration data. including computers that must be re-imaged for image standardization or to address a problem. A computer is refreshed. Planning for BitLocker Drive Encryption BitLocker Drive Encryption is included in Windows Vista and later client operating systems. One BitLocker Drive Encryption decision you must make is the Solution Accelerators microsoft. One computer replaces another computer. Finally. The current Windows operating system on the target computer is upgraded to the deployed operating system. the user state data is restored to the new computer.

which Active Directory administrators manage. applications. or the System Center Asset Inventory Service. which each user manages.2 or later. Active Directory® Domain Services (AD DS). evaluate target computer readiness for the deployment of the target operating system. Select this option to centrally store the recovery keys in a network shared folder. For more information on BitLocker Drive Encryption. TPM is a cryptographic hardware chip installed on the target computer. device drivers. Also.aspx. Select this option to store the recovery keys in AD DS. microsoft. which network administrators manage. This is the preferred method if the target computer does not support TPM. Note You can provide a PIN that users can enter in conjunction with TPM.microsoft. such as System Center Configuration Manager. Evaluating Target Computer Readiness As part of the planning process.com/en-us/windows/aa905065. or you can use a UFD to strengthen the security when starting a computer. System Center Essentials. elect the methods users will employ to start their computers after BitLocker Drive Encryption is enabled. In this method.com/technet/SolutionAccelerators • • Solution Accelerators . This is the preferred method if the target computer supports TPM. If the target computer does not support TPM. which must be present in the computer when the computer starts.15 Microsoft Deployment Toolkit 2010 Update 1 storage of the recovery keys. Verifying that target computers have adequate software and hardware system resources as described in Verify Adequate Target Computer Resources. A network folder. Users can start their computers using one of the following methods: • Trusted Platform Module (TPM) version 1. Evaluate target computer readiness for deployment by: • Verifying target computer readiness for running the MDT 2010 scripts as described in Verify Target Computer Readiness for Running MDT 2010 Scripts. Identifying the differences in the deployment process between 32-bit and 64bit computers as described in Identify Differences in 64-bit and 32-bit Deployments. • UFD. Microsoft Assessment and Planning Toolkit. Select this option to store the recovery key on UFDs. a UFD or personal identification number (PIN) must be used to start the computer. You can store BitLocker Drive Encryption recovery keys in: • • • A local folder. Evaluate target computer readiness using automated hardware and software inventory tools. see BitLocker Drive Encryption at http://technet. and other components. the required encryption keys are stored on a UFD.

In any scenario except New Computer (which does not migrate user data). Similarly. These requirements include: • • The target computer has WSH 5. The target computer processor must meet the requirements of the operating system. • Microsoft Data Access Components version 2.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 16 Verify Target Computer Readiness for Running MDT 2010 Scripts Before running the rest of the MDT 2010 scripts. Additional available disk space is required when user state migration data and deployment logs are stored locally on the target computer.com/technet/SolutionAccelerators • • • • • • • • Solution Accelerators .vbs determines that the computer meets the requirements for running the remaining scripts. must be set to YES for the deployment to continue.6 or later installed and running. The OSInstall property. ZTIValidate. Drive C must be the first partition on the first disk of the target computer (Refresh Computer scenario only). Windows Script Host (WSH) version 5. run ZTIPrereq. MSXML versions 4.wsf determines whether the target computer has the appropriate software and hardware system resources to deploy the target operating system.0 or later installed and running.0 and 6. Microsoft XML Core Services (MSXML) version 3.0 (any service pack level) installed and running. The target computer must have sufficient available disk space for the image being deployed to it. the existing operating system must be a client operating system if the new operating system is a client operating system. Script prerequisites include: • • • Windows XP with SP2 or a later Windows client operating system in use. The current operating system on the target computer must be running on the C partition (Refresh Computer scenario only).0 are not compatible with the MDT 2010 scripts.6 or later installed.vbs to ensure that the target computer meets the requirements for running the remaining MDT 2010 scripts. if defined. Note The version of MSXML must be 3. Verify Adequate Target Computer Resources After ZTIPrereq. The target computer must have sufficient free disk space (approximately 150 MB) to hold Windows PE log files.0. only Windows Server 2003 or Windows Server 2008 can be deployed to a computer currently running a server operating system. The target computer memory must meet the requirements of the operating system. microsoft.

see the Windows Deployment Services Help files. The target computer must have a direct network connection to Windows Deployment Services servers and deployment shares. and Windows Server 2008 include a number of features that help improve the performance and power utilization of computers running these operating systems. Upgrade the system resources on these target computers prior to deploying Windows. and 32-bit applications are installed in the Program Files (x86) folder. Check the appropriate folder structure when looking for previously installed applications. On 64-bit versions of Windows. Applications are installed in separate Program Files folders. 64-bit versions of Windows require 64-bit device drivers. if necessary. use a 64-bit version of Windows PE. Windows Vista with SP1. You cannot use 32bit device drivers in 64-bit versions of Windows. causing the deployment process to fail.com/technet/SolutionAccelerators . or 3. You can Solution Accelerators microsoft. If deploying a 64-bit version of Windows 7. 2.1. Identify Differences in 64-bit and 32-bit Deployments Most functions and features found in 32-bit versions of Windows are the same in 64-bit versions of Windows.0. Windows Server 2008 R2.0 do not run 32-bit applications. (Unsupported network connections include virtual private network [VPN] and wireless connections. Use the following command to force Windows Deployment Services to deploy 64-bit versions: WDSUTIL /set-server /architecturediscovery:yes For more information. However.) Note Target computers that attempt to install an image over a VPN or wireless connection will not be able to connect to a deployment share after restarting in Windows PE.17 Microsoft Deployment Toolkit 2010 Update 1 • • The target computer must have sufficient total disk space to hold Windows PE and the image (expanded image size plus 150 MB). Ensure that any compiled applications used by a 64-bit version of Windows PE are 64-bit versions. MDT 2010 may not properly detect that the processor is a 64-bit processor. therefore. 64-bit applications are installed in the Program Files folder. Processor architecture discovery in Windows Deployment Services may need to be forced for 64-bit computers. take the following differences into consideration when deploying 64-bit versions of Windows: • For LTI deployments. • 64-bit versions of Windows PE 2. Use System Center Configuration Manager or another software-inventory tool to help determine whether any existing computers have inadequate system resources. the version of Windows PE must match the version of Windows being deployed. • • • Planning Performance and Power Management Windows 7. Not all 64-bit computers properly report the processor type.

ZTI.mspx Application Power Management Best Practices for Windows Vista at http://www. The Security Solution Accelerators include guidance and tools to help you secure Windows 7. and UDI Deployments LTI deployment Allows selection of the Solution Accelerators ZTI deployment Supports only fully UDI deployment Allows selection of the microsoft. For more information about deploying target computers in a secured configuration using these solution accelerators. Comparison of LTI. and UDI deployments. Table 6.aspx Sustainable Computing: Enforce Power Management Settings in your Organization with Group Policy at http://technet.microsoft. or UDI Deployments LTI. ZTI.microsoft.microsoft. Windows Server 2008 R2.microsoft.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 18 incorporate these improvements as part of the configuration settings you deploy to the target computers using MDT 2010.com/technet/SolutionAccelerators . Windows Vista.aspx. ZTI.com/en-us/performance/default. Choosing LTI. Review the following resources to identify performance and power-management configuration settings to include when performing your target computer deployments: • • • Windows Performance Analysis Developer Center at http://msdn.ini) for deploying target computers.mspx Power Policy Configuration and Deployment in Windows at http://www. ensure that the target computers are deployed in compliance with the requirements in your organization. Table 6 compares LTI. see Security Solution Accelerators at http://technet. Windows Performance Analysis Tools at http://msdn. Microsoft has developed Security Solution Accelerators that can help you deploy your target computers in a secured configuration.microsoft. and Windows Server 2003.com/enus/solutionaccelerators/cc835245.microsoft.aspx.com/enus/magazine/dd252731. Windows XP.com/whdc/system/pnppwr/mobile_bat.mspx • • • Planning Target Computer Security When planning the configuration of the Windows operating systems for target computers.microsoft. ZTI and UDI deployments use the same common set of scripts and configuration files (such as CustomSettings.aspx Mobile Battery Life Solutions: A Guide for Mobile Platform Professionals at http://www.com/whdc/system/pnppwr/powermgmt/PM_apps.com/whdc/system/pnppwr/powermgmt/PMpolicy_Windo ws.com/enus/performance/cc825801. Windows Server 2008.

com/technet/SolutionAccelerators .19 Microsoft Deployment Toolkit 2010 Update 1 LTI deployment level of automation Has minimal infrastructure requirements Supports deployments over a network using a shared folder or locally using removable storage such as a CD. or UFD The deployment process can be initiated manually or automatically using Windows Deployment Services The deployment process is configured using the Deployment Workbench ZTI deployment automated deployments Requires System Center Configuration Manager Supports deployments only from System Center Configuration Manager distribution points The installation process can be initiated by System Center Configuration Manager or Windows Deployment Services The deployment process is configured using the Configuration Manager Console Requires more initial IT administration configuration time Requires no interaction by the user or deployment technician Reduces the risk of introducing configuration errors Users and deployment technicians are not required to have credentials with elevated permissions Users and deployment technicians do not need to know configuration settings prior to initiating the MDT 2010 deployment UDI deployment level of automation Requires System Center Configuration Manager Supports deployments only from System Center Configuration Manager distribution points The installation process can be initiated by System Center Configuration Manager or Windows Deployment Services The deployment process is configured using the Configuration Manager Console and the UDI Wizard Designer. Requires more initial IT administration configuration time Can require interaction by the user or deployment technician Increases the risk of introducing configuration errors Requires users or deployment technicians to have credentials with elevated permissions Requires that users or deployment technicians know some configuration settings prior to initiating the MDT 2010 deployment process Can require less initial information technology (IT) administration configuration time Can require interaction by the user or deployment technician Increases the risk of introducing configuration errors Requires users or deployment technicians to have credentials with elevated permissions Requires that users or deployment technicians know some configuration settings prior to initiating the MDT 2010 deployment process Solution Accelerators microsoft. DVD.

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 20 LTI deployment Can be used with slow connections or in instances where no network connectivity exists Requires little or no infrastructure to support deployment Supports deployment over the network or local to the computer from media Does not require management of target computers using System Center Configuration Manager Supports security policies in which automatic software installation is prohibited Supports deployment to target computers isolated by firewalls Supports the Upgrade Computer deployment scenario ZTI deployment process Requires a high-speed. when do you provide this information? The more information you provide in advance. Table 7. ZTI. Table 7 lists the advantages and disadvantages of performing fully automated deployments (using LTI. persistent connection Requires an infrastructure sufficient to deploy operating system images Supports only network deployments Requires an infrastructure sufficient to deploy operating system images Supports only network deployments Requires that target computers be managed using System Center Configuration Manager Supports only security in which automatic software installation is allowed. you must provide all the information necessary to install Windows and the applications on target computers. the less interaction is required during deployment. or UDI) and partially automated deployments (using LTI or UDI). Requires RPC communication with target computers Does not support the Upgrade Computer or Replace Computer deployment scenarios At some point in the MDT 2010 process. Advantages and Disadvantages of Fully and Partially Automated Deployments Solution Accelerators microsoft. persistent connection UDI deployment Requires a high-speed. Requires remote procedure call (RPC) communication with target computers Does not support the Upgrade Computer deployment scenario Requires that target computers be managed using System Center Configuration Manager Supports only security in which automatic software installation is allowed.com/technet/SolutionAccelerators . The question is.

Limitations. • Users or deployment technicians must have credentials that require elevated permissions. • The risk of introducing configuration errors is increased. Limitations.com/technet/SolutionAccelerators Solution Accelerators . and Recommendations that Relate to Disks and Partitioning. Limitations. • Users or deployment technicians must know some configuration information prior to initiating the MDT 2010 deployment process. and Recommendations That Relate to BitLocker Drive Encryption. because configuration information can be provided interactively. Disadvantages • More time is needed to provide configuration information required for fully automated deployment.21 Microsoft Deployment Toolkit 2010 Update 1 Method Fully Advantages • No interaction with the user or deployment technician is required. and Recommendations That Relate to Windows 7. Reviewing Known Issues. limitations. and Recommendations for MDT 2010. • Credentials to access network resources and that have elevated permissions are stored in configuration files that must be protected. • Users or deployment technicians do not need to know any configuration information prior to initiating the MDT 2010 deployment process. Windows 7 as described in Review Known Issues. BitLocker Drive Encryption as described in Review Known Issues. Disks and partitioning as described in Review Known Issues. and recommendations for: • • • • General issues in MDT 2010 as described in Review General Known Issues. Partially • Interaction with the user or deployment technician is required. Limitations. microsoft. • Less time is required to prepare for deployment. and Recommendations for MDT 2010 Review the know issues. Limitations. • The risk of introducing configuration errors is decreased.

Limitations.0. When you select the Install Language Pack Offline action. “How to Disable the 8. the Deployment Workbench fails to generate the Windows PE image.010.ini file. Limitations.com/technet/SolutionAccelerators .com/kb/121007). Upgrade Computer deployment scenario as described in Review Known Issues. To avoid this problem.3 file names disabled (see the Microsoft Knowledge Base article. and Recommendations for Running Task Sequences on Target Computers. Limitations. when identifying Domain Name System [DNS] and Windows Internet Naming Service [WINS] servers). When creating deployment shares on computers that have 8. • • Review General Known Issues. Windows PE version 3. and Recommendations for LTI Deployments. and Recommendations for ZTI Deployments. limitations.0. Limitations. and recommendations that relate to MDT 2010: • MDT 2010 and MDT 2010 Update 1 support the Windows Automated Installation Kit (Windows AIK) version 2. Saving and restoring user information as described in Review Known Issues. reenable them by setting the • • • • • Solution Accelerators microsoft. Language packs. the account will not have sufficient privileges to access network connections established by administrators.10. and do not add unnecessary zeroes. which will be misevaluated. the Deployment Workbench evaluates it as 10. applications. and Recommendations for the Upgrade Computer Deployment Scenario.” at http://support.3 file names have been disabled. Limitations. When specifying a Run As account.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 22 • • • LTI deployments as described in Review Known Issues. Limitations. and device drivers that are disabled in the Deployment Workbench are not installed.3 Name Creation on NTFS Partitions. ZTI deployments as described in Review Known Issues. they must exclude unnecessary zero prefixes. you must specify a user who is a member of the Administrators group on the server. you must select language pack CAB files within subfolders of the main package. For example. Otherwise. When you specify IP addresses (for example.1. unless you add them manually to the CustomSettings.1.microsoft. and System Center Configuration Manager 2007 with SP2.8. enter IP addresses carefully. Running task sequences on target computers as described in Review Known Issues.10. if the IP address is typed 10. and Recommendations for MDT 2010 The following are a list of known general issues. If 8. and Recommendations for Saving and Restoring User Information.

by opening corresponding logs files and running verification tests— and determine whether they are unexpected. The USMT fails if you enter a path surrounded by quotation marks that also ends in a backslash (\). a summary page displays warnings about errors encountered during the process. Also be aware of preexisting Unattend. Some device drivers can stall the deployment process.xml files in the image. When deploying a custom Windows XP image.” This error does not prevent successful deployment. To work around this problem.) It is possible for deployment to finish but still trigger several errors or warnings if the errors are nonfatal. because a Server Core installation does not include the Windows Internet Explorer® components required.com/technet/SolutionAccelerators • • • • • • • Solution Accelerators . If this happens. you should not name a subfolder Item. To prevent problems. It is useful to inspect these errors and warnings—for example. Specify the correct /FLAGS value when capturing Windows Vista images using ImageX or Windows Deployment Services capture processes. you might receive a warning similar to. to exclude the folders or files from the image. troubleshoot the issues by capturing and adding the image using MDT 2010 to ensure that all prerequisites are configured properly. The error “Cannot Find Driver Path” can appear if you choose to optimize a Windows PE image and select drivers that are not available from the distribution point. or contact the vendor for an updated version of the device driver. network and media deployment shares created in earlier versions of MDT or BDD must have valid shares. and you can disregard the warning. Unable to ensure Sysprep files are the right version. When manually capturing images. select the Completely Regenerate The Boot Images option. and then create a file named Item. simply leave off the final backslash when specifying a folder. (This page is not displayed when conducting the Server Core installation option of the Windows Server 2008 operating system. the following paths will cause an error: • “D:\” microsoft. Add Setup files to the Deployment Workbench by adding a complete operating system distribution or by pointing the Windows Deployment Wizard to the location of source files. avoid creating a subfolder and a file with the same name. When performing an upgrade. where platform is either x86 (for 32 bit) or x64 (for 64 bit). within the Files folder. isolate the device driver and remove it from the target computer.23 Microsoft Deployment Toolkit 2010 Update 1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSyste m\NtfsDisable8dot3NameCreation registry value to 0. “Warning: The \\Server\Share\Operating Systems\XPSP2_CI\i386\winnt32. use the Wimscript. At the completion of MDT 2010 deployment.exe is not available. For example. If custom images captured by directly running ImageX (without using MDT 2010 to capture the image) do not work properly. For example.ini file that MDT 2010 supplies in the \Distribution\tools\_platform folder. • Within a folder.

0.” at http://support.1.com/kb/929761.1 . Windows Vista.4000.1 . The System Preparation Tool (Sysprep) does not support configuring the Internet Explorer home page for Windows XP images.” at http://support. Copy the USMT 3.0.msi files are supported to migrate user data during deployment. Install Windows Installer version 3.ini. “How to add Input Method Editor support to Windows PE 2. these paths will not cause an error: USMT version 3. see the Microsoft Help and Support article. which accompanies the Microsoft Knowledge Base article. For more information. “When you run Wusa. In the Refresh Computer and Upgrade Computer scenarios.msi files to tools\_platform. “Windows Installer 3.com/?id=893803. otherwise.exe together with the /quiet option to try to install certain software packages on a Windows Vista–based computer. Configuring the Internet Explorer home page works only in Windows 7. where platform is either x86 (for 32-bit) or x64 (for 64-bit) in the distribution point. 2. some pages (such as the User Locale and Keyboard Locale pages) do not display text correctly if required fonts are not installed in Windows PE. • Configure the Internet Explorer home page using CustomSettings. 3.com/kb/926181.2435) is available. Some keyboard layouts might require language packs or input method editors that MDT 2010 does not automatically include in the Windows PE startup image. To install Windows Installer 3.microsoft. or by using the Windows Internet Explorer Administration Kit. During LTI deployments to new computers.1 or later. Install package 929761. or Windows XP unattended installation. the installation fails.0.” at http://support.0.microsoft.Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments 24 • • • • • • • • • “D:\folder\” D: D:\ D:\folder\ D:\folder “D:\folder” “D:\\” “D:” However.com/technet/SolutionAccelerators . the same symptoms appear if required fonts are not installed in the operating system being replaced. • • Solution Accelerators microsoft. Perform the following steps to install USMT 3. in the MDT DB.1: 1. MDT 2010 does not verify that the keyboard layout is valid. deployment will fail during USMT installation.1 v2 (3.microsoft.1—and for more information—see the Microsoft Help and Support article.

25

Microsoft Deployment Toolkit 2010 Update 1

A maximum of two WINS server addresses can be added when configuring static IP configuration settings for a network adapter. If more than two WINS server addresses are added using MDT 2010, only the first two WINS server addresses are used. Hash value errors may occur in Systems Center Configuration Manager during download on demand or when creating a media deployment DVD. This can occur if the packages on the distribution points are inconsistent with the information in the System Center Configuration Manager database. To correct this, open Configuration Manager Console, expand the Boot Image or Package nodes, expand Distribution Points, right-click the distribution point, and then click Refresh Distribution Point. When deploying Windows Server 2003 using System Center Configuration Manager, the deployment process does not automatically copy the Windows installation files to the %WinDir%\Source folder, as it does for other deployment methods. As a result, System Center Configuration Manager can display dialog boxes requesting missing DLLs needed to complete a server role installation. As a workaround, add a step to the task sequence to copy the source files and set the registry subkeys that identify the source folder (SourcePath and ServicePackSourcePath in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\s etup). Upgrades from Windows XP to Windows 7 are not supported—only upgrades from Windows Vista to Windows 7. Upgrading from 64-bit editions of Windows XP Professional to 64-bit editions of Windows Vista is not supported. In LTI deployments, you set several kinds of information in the Create Task Sequence Wizard. The user interface does not provide an option to edit this information at a later time. However, you can edit the information directly in the Unattend.xml file (for Windows 7, Windows Vista, Windows Server 2008, or Windows Server 2008 R2) or in Sysprep.inf and Unattend.txt (for Windows XP or Windows Server 2003). The information includes: • • • • Organization name. Full name. Internet Explorer home page. Local Administrator password.

• • •

No user state configuration settings can be or need to be specified using the CustomSettings.ini file for System Center Configuration Manager scenarios. The network location is determined automatically by the Request State Store task. In System Center Configuration Manager deployments, you can install multiple application packages on a computer by specifying them in the CustomSettings.ini file according to the following parameters:

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

26

• • • •

Specify a base variable named PACKAGES in the task sequence in the Install Software task. Each PACKAGES variable name should have a suffix starting with 001. The PACKAGESxxx value should have the format PACKAGEID:ProgramName (use a colon between items). The ProgramName value is case-sensitive. The following is an example of specifying packages in CustomSettings.ini: PACKAGES001=DEP0002B:Install Office 2007 PACKAGES002=DEP00011:Install Office Communicator

In LTI New Computer deployments, applications marked as hidden in the Deployment Workbench are not installed when you do not skip the Application page in the Windows Deployment Wizard and specify the application globally unique identifier (GUID) in CustomSettings.ini. Specify hidden applications using the MandatoryApplications property instead of the Applications property. Close Configuration Manager Console before running the integration option from MDT 2010. Otherwise, some files may not be properly updated. During the Scanstate and Loadstate processes, multiple copies of log files may be created. You can use a new USMT template for excluding the log files or log directories while running Scanstate and Loadstate. New Computer and Replace Computer deployment scenarios format Disk 0 by default. Using MDT 2010 on computers with original equipment manufacturer (OEM) partitions or multiple fixed or external hard disks may require additional configuration and scripting in addition to thorough testing. The Task Sequencer will not accept Extensible Markup Language (XML) files that contain Unicode content (from an XML file encoded as UTF-8). Attempting to do this results in a task sequence failure. The Task Sequencer does not properly deal with encoded UTF-7 data: It does not cause a failure, but it does cause the data to be translated unexpectedly. After uninstalling MDT 2010 using the Control Panel Add or Remove Programs item, the Distribution share directory (if created) must be removed manually. MDT 2010 does not remove files or folders that it did not initially install. When using MDT 2010 extensions (add-in wizards) with System Center Configuration Manager, MDT 2010 must be installed on every System Center Configuration Manager server used to administer operating system deployments. The Priority property in CustomSettings.ini has no maximum line length. However, if the property name is longer than 55 characters when the Configure Database Wizard runs, the wizard will truncate the Priority property, and you will need to manually edit the property. As a workaround, run the Configure Database Wizard before performing any other
microsoft.com/technet/SolutionAccelerators

• •

Solution Accelerators

27

Microsoft Deployment Toolkit 2010 Update 1

customization, or clear the check boxes for queries in the wizard that are not needed. • MDT 2010 RTM supports deployment from a UFD. See the Windows AIK for information about preparing the device, then copy (using the xcopy command) all files and folders from the \Media\content folder to the UFD. Dialing properties that are not configured, even if present in the answer file, include the country code, area code, long-distance access, and dialing rules. To work around this issue, configure dialing rules by creating and testing a .reg file in a lab environment, and then import that .reg file as a custom task during the task sequence. When deploying an image that has never been started or that is missing the \ %SystemRoot%\Prefetch directory, updates installed using Setup.exe or PkgMgr.exe can fail. As a workaround, create the \%SystemRoot%\Prefetch directory in the operating system image. This error does not occur when you build the image using Windows Vista with SP1 or later. The media International Organization for Standardization (ISO) image must be smaller than 2.2 GB for media deployment to a VM running in Microsoft Virtual PC versions prior to Microsoft Virtual PC 2007 or Virtual Server 2005 R2. If the ISO image is larger than 2.2 GB, the deployment may result in an error. This limitation no longer exists in Virtual PC 2007, Virtual Server 2005 R2, or Hyper-V.

Review Known Issues, Limitations, and Recommendations That Relate to Windows 7
The following is a list of known issues, limitations, and recommendations that relate to Windows 7: • Deployment will fail on Windows 7 computers configured for a language other than English when the Windows Media Player Network Sharing Service is run. As a workaround, stop the Windows Media Player Network Sharing Service until after deployment is complete. You can use AD DS to back up BitLocker Drive Encryption and TPM data. Recovery information includes the recovery password for each encrypted value, the TPM owner password, and the information necessary to associate recovery information with computers and volumes. Another option is to save a package containing the keys used to encrypt data in addition to the recovery password required to access those keys. For more information, see “Configuring Active Directory to Back up Windows BitLocker Drive Encryption and Trusted Platform Module Recovery Information” in the Microsoft Download Center at http://www.microsoft.com/downloads/details.aspx? FamilyID=3a207915-dfc3-4579-90cd-86ac666f61d4. When enabling BitLocker Drive Encryption, key files are generated as hidden, read-only system files. To see them, set the Windows Explorer option to show hidden and system files.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

28

BitLocker Drive Encryption during LTI deployment requires at least two partitions. The first partition is the primary partition and can be any size; it stores operating system files and user data. In BitLocker Drive Encryption terminology, this is called the boot partition. For Windows Vista, the second partition should be at least 2 GB; for Windows 7, it should be at least 300 MB. This partition stores startup files required during the first phase of startup and is called the system partition. For Windows Vista, LTI deployment automatically configures the required system partition if you are deploying BitLocker Drive Encryption. A BitLocker partition is created for all Windows 7 deployments, regardless of whether you are deploying BitLocker Drive Encryption. In Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2, if a user with a limited account maps a drive (such as drive Z) to the MDT 2010 distribution point (\\server\distribution$, where server is the name of the computer hosting the distribution point), runs LiteTouch.vbs, and then provides Administrator credentials in the User Credentials dialog box, MDT 2010 displays the error, “Cannot find script file ‘Z:\Scripts\LiteTouch.wsf’ because the account that the user provided in the User Credentials dialog box cannot access the mapped drive created by the limited user account.” To resolve this issue, use an account with Administrator credentials to map the drive to the distribution point. BitLocker Drive Encryption deployment on a computer running Windows Vista and Windows 7 can fail with the error, “Unable to merge BDEPartition, return code=87,” when the user does not specify a locale. Restarting the computer does not allow the operating system to start. To avoid this error, specify a user language, or edit the CustomSettings.ini file to specify the UILanguage property. For example, you could add UILanguage = en-us to the CustomSettings.ini file. If activating BitLocker Drive Encryption during installation fails in Refresh Computer and Upgrade Computer scenarios, verify that MDT 2010 is able to shrink the partition as required by following these steps: 1. At a command prompt, type diskpart shrink querymax, and note the value displayed. 2. If the value is less than 2,000 MB, then manually defragment the disk. MDT 2010 performs an automatic defragmentation, however, so this might not resolve the problem. 3. If defragmenting the disk does not resolve the issue, back up the computer’s hard disk, create a new partition, and repeat these steps until typing diskpart shrink querymax returns a value greater than 2,000 MB. There might be files in specific areas of the partition that cannot be relocated or removed.

The BDERequired flag is no longer used. All sample templates that enable BitLocker Drive Encryption and that encounter an error will stop by default. You can edit the task sequence to enable deployment to continue if an error occurs.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

29

Microsoft Deployment Toolkit 2010 Update 1

When deploying a new computer or refreshing a computer running a localized edition of Windows XP with a Windows Vista or Windows 7 image that is using a different language, Setup will prompt for the keyboard layout, language, and time and currency settings during the Windows PE phase. As a workaround, import Setup files with the custom image. MDT 2010 supports Windows Vista and Windows 7 language pack selection during deployment for all scenarios if the language packs are configured in the Deployment Workbench. Selecting multiple language packs is possible when deploying Windows Vista Enterprise or Windows Vista Ultimate. When other editions of Windows Vista are deployed, only one language pack can be selected because of Windows Vista licensing restrictions. If the deployment fails in Upgrade Computer scenarios and three or more language packs are selected, try reducing the number of language packs until the deployment succeeds.

Review Known Issues, Limitations, and Recommendations that Relate to Disks and Partitioning
The following is a list of known issues, limitations, and recommendations that relate to disk and partitioning: • • LTI does not support the deployment of the target operating system to logical drives or dynamic disks. Deployments to existing disk partitions created by newer operating system versions are not supported in Refresh Computer deployment scenarios. For example, you cannot deploy Windows Vista with SP1 to partitions created by Windows 7; you cannot deploy Windows XP with SP3 to partitions created by Windows Visa with SP1. However, you can deploy different processor architecture versions to the existing partitions created by the same operating system version. For example, you can deploy a 64-bit version of Windows 7 on a computer that is currently running a 32-bit version of Windows 7 or vice versa. • In the Format and Partition Disk task sequence step types, always configure the logical partitions that will reside on an extended partition immediately after the extended partition. If you do not specify the logical partitions immediately after the extended partition, creating the logical partition sizes using a percentage produces unexpected results. For example, the following partition creation order is incorrect, because the logical partitions (Partition 4 and Partition 5) are not immediately after the extended partition (Partition 2): Partition Partition Partition Partition Partition
Solution Accelerators

1: 2: 3: 4: 5:

Primary Extended Primary Logical Logical
microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

30

Partition 6: Primary Instead, create the partitions in the following order: Partition Partition Partition Partition Partition Partition • 1: 2: 3: 4: 5: 6: Primary Extended Logical Logical Primary Primary

Windows 7 always hides the system volume during deployment, so a drive letter is not assigned to the system volume. For example, if the target computer has one drive with two partitions, Partition_1 and Partition_2, and you deploy Windows 7 to Partition_2, Windows 7 will properly deploy to Partition_ 2. However, a drive letter will not be assigned to Partition_1. After starting Windows PE, the drive letters assigned to each storage device may change. For example, if the destination computer has a CD-ROM assigned to drive D and a hard disk drive assigned to drive E, the hard disk drive will be on drive D and the CD-ROM will be on drive E when Windows PE starts. If a DVD deployment fails, check that the drives have not been reassigned on the target computer. To simplify deployment, save user data to a network location instead of to a local drive. Avoid editing the Unattend.xml files to format or alter the partitions. MDT 2010 might store state and user data on the partition before calling Setup.exe (in LTI scenarios), and instructions added to Unattend.xml would cause Setup to destroy that data, resulting in a deployment failure. While configuring the Format and Partition Disk task, always specify the extended and logical partitions together, and do not add a primary partition inbetween, which gives undesirable results when a logical partition size is configured using a percentage. In other words, do not add a primary partition between an extended and logical partition.

Review Known Issues, Limitations, and Recommendations That Relate to BitLocker Drive Encryption
The following is a list of known issues, limitations, and recommendations that relate to BitLocker Drive Encryption: • In New Computer scenarios on computers running Windows Vista that have BitLocker Drive Encryption disabled (a state in which the volume is still encrypted, but the key is stored in clear text to allow automatic startup), running Diskpart to clean the disk causes the computer to stop responding. To work around this issue, enable BitLocker Drive Encryption again, or turn off BitLocker Drive Encryption to decrypt the volume and ensure that decryption finishes. If the computer stops responding, restart deployment. If a BitLocker Drive Encryption recovery prompt appears after restarting the target computer (because the BitLocker Drive Encryption key required to
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

31

Microsoft Deployment Toolkit 2010 Update 1

unlock the volume could not be obtained), work around the problem by using one of the following approaches: • Remove the media (such as the deployment DVD) while Windows PE is still running. Doing so prevents the operating system from seeing the DVD when it starts. Change the boot order of the computer so that the DVD drive follows the hard disk. Deploy the computer with no startup media; for example, use a Pre-Boot Execution Environment (PXE) deployment.

• •

Review Known Issues, Limitations, and Recommendations for LTI Deployments
The following is a list of known issues, limitations, and recommendations that relate to LTI deployments: • The network credentials specified for accessing network resources (the USMT store location, computer backup location, and so on) are not validated if a user is logged on to the computer using a domain account and if the computer already has a connection established to another share on the same server.

Review Known Issues, Limitations, and Recommendations for ZTI Deployments
The following is a list of known issues, limitations, and recommendations that relate to ZTI deployments: • When deploying computers using System Center Configuration Manager and backing up the computer data locally, computers with two partitions may not be able to retain the backup. To prevent backups from being removed, save to a network location instead of to a local drive. In a System Center Configuration Manager task sequence, the Format and Partition task might not run successfully on a computer if it has only one unformatted partition. To work around this issue, either remove the partition or format it. While installing the Server roles, System Center Configuration Manager might display a prompt for DLLs needed to complete the role installation. If this happens, specify a valid location for the required files. To avoid this step, add a step earlier in the task sequence that copies the required DLLs to the Windows Setup files folder defined in the registry. This folder location is defined in the SourcePath registry value, located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi on\Setup.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

32

Review Known Issues, Limitations, and Recommendations for the Upgrade Computer Deployment Scenario
The following is a list of known issues, limitations, and recommendations that relate to the Upgrade Computer deployment scenario: • • Before using the Windows Deployment Wizard to upgrade a computer, ensure that the local Administrator account is enabled. Some pages might not be displayed if the user changes the options on the domain membership page. The following pages might be affected: • Windows BitLocker Drive Encryption pages. If the user chooses not to perform an image capture and chooses to enable BitLocker Drive Encryption in the Windows Deployment Wizard, and then decides to go back to the Image Capture page and choose Capture, BitLocker Drive Encryption is still enabled. The image capture would be attempted against an encrypted partition. Image Capture page. This page should be displayed only when a user tries to join a workgroup. If the user specifies the path for image capture and goes back to the Domain Join page, and then joins a domain, the Image Capture page will still be displayed. This problem occurs because the image-capture process runs Sysprep and should only be performed on computers not joined to a domain.

Review Known Issues, Limitations, and Recommendations for Running Task Sequences on Target Computers
The following is a list of known issues, limitations, and recommendations for running task sequences on target computers in MDT 2010: • For LTI deployments, ensure that User Account Control (UAC) is disabled for the built-in local Administrator account on the target computers until the task sequence finishes. Running task sequences on computers with UAC enabled for the local Administrator account causes task sequences to fail.
Note UAC should be disabled only for the built-in local Administrator account and enabled for all other accounts. By default, the built-in local Administrator account is excluded from UAC because of the “User Account Control: Admin Approval Mode for the built-in Administrator account” (disabled) policy setting.

For more information about UAC Group Policy settings, see UAC Group Policy Settings at http://technet.microsoft.com/enus/library/dd835564(WS.10).aspx.

Review Known Issues, Limitations, and Recommendations for Saving and Restoring User Information
The following is a list of known issues, limitations, and recommendations for saving and restoring user information in MDT 2010:

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

33

Microsoft Deployment Toolkit 2010 Update 1

For LTI deployments, do not add any of the following USMT command-line parameters to the ScanStateArgs or LoadStateArgs properties, as they cause the saving and restoration of user state information to fail: • • • • • • • • /hardlink /nocompress /encrypt /key /keyfile /vsc /l /i

User state migration data may not be restored properly depending on the disk configuration of the target computer when deploying Windows 7. This issue can occur when the target computer has two physical hard disks, Disk_0 and Disk_1. Disk_0 contains the C volume, which is encrypted using BitLocker Drive Encryption. The MDT 2010 deployment process is configured to deploy a new operating system to Disk_1. The problems in the deployment process occur as follows: • • • • Early the deployment process, the minint and smstasksequence folders are copied to the existing C volume, which is encrypted. Disk_1 is partitioned and formatted properly in preparation for deploying the target operating system. The target operating system is installed on the new partition and disk volume on Disk_1. During the State Restore Phase, the original C volume is not assigned a drive letter, so the task sequence steps in the State Restore Phase cannot access the minint and smstasksequence folders on the BitLocker Drive Encryption–encrypted drive. The restoration of the user state migration data fails.

The result is that the target operating system is installed, but the restoration of the user state migration data fails.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

34

Microsoft Deployment Toolkit 2010 Update 1

Installing or Upgrading to MDT 2010
To prepare for performing deployments using MDT 2010, perform the following tasks: 1. Review the known issues, limitations, and recommendations for preparing disks on target computers in MDT 2010 as described in Reviewing Known Issues, Limitations, and Recommendations for Installing or Upgrading to MDT 2010. 2. Perform any combination of the following steps to ensure that MDT 2010 is installed correctly: • Install a new instance of MDT 2010 on each computer where you want to manage MDT 2010 deployment shares as described in Installing a New Instance of MDT 2010.

Upgrade an existing instance of BDD 2007, MDT 2008, or prerelease version of MDT 2010 to MDT 2010 as described in Upgrading to MDT 2010. 3. Determine whether any updates are available for the components in the Deployment Workbench using the Check Updates Wizard as described in Checking for Updates to MDT 2010 Components.
Note Windows PowerShell™ version 1.0 or later must be installed on any computer on which MDT 2010 is installed for management of LTI or ZTI deployments.

Reviewing Known Issues, Limitations, and Recommendations for Installing or Upgrading to MDT 2010
The following is a list of known issues, limitations, and recommendations for installing MDT 2010: • Ensure that the disk volume that contains the temporary folder that the Deployment Workbench uses has at least 20 GB of available disk space. The Deployment Workbench creates large images and requires temporary storage during the image-creation process. The Deployment Workbench determines the temporary folder to use by performing the following steps: 1. Use the temporary folder specified in the Temp_Dir registry subkey, which is located at HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4. Create the Temp_Dir registry subkey as a REG_SZ type that contains the fully qualified path to the folder to be used as the temporary folder. 2. If the TEMP_DIR registry subkey does not exist, then the Deployment Workbench uses the folder specified in the %TEMP% environment variable.

35

Microsoft Deployment Toolkit 2010 Update 1

Ensure that the disk volume specified in the TEMP_DIR registry subkey or in the %TEMP% environment variable has sufficient available disk space.

Installing a New Instance of MDT 2010
With all the prerequisite software installed, perform the following steps to install MDT 2010 (MicrosoftDeploymentToolkit_platform.msi, where platform is either x86 or x64): 1. Right-click MicrosoftDeploymentToolkit2010_platform.msi, and then click Install. The Microsoft Deployment Toolkit 2010 Setup Wizard starts. 2. Complete the Microsoft Deployment Toolkit 2010 Setup Wizard using the information in Table 8. Table 8. Information for Completing the Microsoft Deployment Toolkit 2010 Setup Wizard On this wizard page Welcome to the Microsoft Deployment Toolkit 2010 Setup Wizard End-User License Agreement Custom Setup Do the following Click Next.

1. Review the license agreement. 2. Click I accept the terms in the License Agreement, and then click Next. 1. Select the desired features. 2. Select the desired destination folder for installing MDT 2010 (which defaults to C:\Program Files\Microsoft Deployment Toolkit), and then click Next. Click Install. Click Finish.

Ready to Install Completing the Microsoft Deployment Toolkit Setup Wizard

Upon completion, MDT 2010 is installed in the target folder you selected during the wizard.

Upgrading to MDT 2010
MDT 2010 automatically uninstalls previous versions of MDT and BDD before installing MDT 2010, including the following versions: • Previous versions of MDT 2010
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Installing or Upgrading to MDT 2010

36

• •

MDT 2008 Update 1 BDD 2007 Update 2

In addition to upgrading the MDT 2010 installation, upgrade any existing MDT 2010 deployment shares, MDT 2008 deployment shares, and BDD 2007 deployment shares. For more information on this process, see Upgrade an Existing Deployment Share in Deployment Workbench.

Checking for Updates to MDT 2010 Components
When you have installed or upgraded to MDT 2010, check the Microsoft Download Center to determine whether updates are available to the components in the Components node in the Deployment Workbench. You update the components using the Check for Updates Wizard. To check for updates to MDT 2010 components 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Information Center/Components. 3. In the Actions pane, click Check for Updates. The Check for Updates Wizard starts. 4. Complete the Check for Updates Wizard using the information in Table 9. Table 9. Information for Completing the Check for Updates Wizard On this wizard page General Settings Do this 1. Select the Connect to the Internet and check for updates check box. If the check box is: • Selected, the wizard connects to Microsoft Download Center to look for updates to the components. • Cleared, the wizard does not connect to Microsoft Download Center to look for updates to the components, and you cannot complete the wizard. 2. Click Next. Review the information in the Details box, and then click Next.
Tip You can click Save Output to save the output of the wizard to a file. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.

Summary Confirmation

Click Finish.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

37

Microsoft Deployment Toolkit 2010 Update 1

After the wizard finishes, the list of available components and versions is updated in the details pane of the Deployment Workbench.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

38

Microsoft Deployment Toolkit 2010 Update 1

Performing LTI Deployments
You perform LTI deployments using only MDT 2010 and supporting components. You can perform LTI deployments over a network or from removable media. This flexibility makes LTI deployments appropriate for a wide range of organizations. Perform LTI deployments by • • • • • Preparing the deployment environment as described in Preparing the LTI Deployment Environment. Preparing for deployment to the reference computer as described in Preparing for LTI Deployment to the Reference Computer. Deploying to and capture a reference computer image as described in Deploying to and Capturing an Image of the Reference Computer in LTI. Preparing for deployment to target computers as described in Preparing for LTI Deployment to Target Computers. Deploying captured images to target computers as described in Deploying Captured Images to Target Computers in LTI.

Preparing the LTI Deployment Environment
After preparing the prerequisite infrastructure for MDT 2010, prepare the LTI deployment environment. To prepare the LTI deployment environment 1. Install a new instance of MDT 2010 on the deployment server, or upgrade an existing instance of BDD 2007 or MDT 2008 to MDT 2010 as described in Installing or Upgrading to MDT 2010. 2. Install the components required by MDT 2010 and the LTI deployment process as described in Install Components Required by MDT 2010 and LTI. 3. Obtain the software that the LTI deployment process requires as described in Obtain the Software Required by the LTI Deployment Process.

Install or Upgrade to MDT 2010 for LTI Deployments
To perform LTI deployments, you must have at least one instance of MDT 2010 running in your environment. If your existing environment has: • No computers currently running MDT 2010 or a previous version of MDT or BDD, then install one or more new instances of MDT 2010 as described in Installing a New Instance of MDT 2010. One or more computers running a previous version of MDT or BDD, then upgrade those instances to MDT 2010 as described in Upgrading to MDT 2010. After the upgrade process is complete:

39

Microsoft Deployment Toolkit 2010 Update 1

Existing BDD 2007 or MDT 2008 media deployment points are upgraded to media items in MDT 2010. However, the items you select in the media deployment point, such as applications, task sequences, driver groups, or package groups, are not preserved. Before updating the media, create folders for each type of item that are not migrated and a selection profile that selects each of those folders. Then, configure the media to use the selection profile and update the media.
Note If you do not create the folders and selection profile, the media item will use the Everything selection profile, which includes all items and may not be the desired configuration.

Existing BDD 2007 or MDT 2008 network deployment points are upgraded to linked deployment shares in MDT 2010. However, some of the items selected in the network deployment point are not preserved, such as applications, task sequences, or package groups. However, driver groups are migrated if they are configured to a value other than All Drivers. A selection profile named Windows PE Drivers for NETWORK is created for the driver group selected for Windows PE device drivers and the linked deployment share is configured to use the migrated selection profile. Before updating the linked deployment share, create folders for each type of item not migrated and a selection profile that selects each of those folders. Configure the linked deployment share to use the selection profile, then replicate the linked deployment share.
Note If you do not create the folders and selection profile, the linked deployment share will use the Everything selection profile, which includes all items and may not be the desired configuration.

Existing BDD 2007 or MDT 2008 LAB deployment points are upgraded to deployment shares in MDT 2010. However, some of the items selected in the LAB deployment point are not preserved, such as applications, task sequences, or package groups. However, driver groups are migrated if they are configured to a value other than All Drivers. A selection profile named Windows PE Drivers for LAB is created for the driver group selected for Windows PE device drivers and the deployment share is configured to use the migrated selection profile.

Boot image settings for MDT 2008 media deployment points are not preserved. Instead, the boot image settings from the parent deployment share are copied to the media. You may need to modify the boot image settings to reflect the original boot image settings. Task sequences are recreated using the LTI task sequence templates in MDT 2010. Custom task sequence steps in task sequences created in BDD 2007 are moved to the Custom Tasks groups in the upgraded task sequence. After the upgrade, you may need to move the custom task sequence steps back into their correct sequence in the task sequence.
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Performing LTI Deployments

40

Install Components Required by MDT 2010 and LTI
The Deployment Workbench is the administration console for LTI. Most of the LTI management tasks are performed in the Deployment Workbench. MDT 2010 also includes a Windows PowerShell provider that allows for the automation of LTI management tasks through the Windows PowerShell command shell using MDT cmdlets.
Note MDT 2010 and MDT 2010 Update 1 support Windows AIK 2.0, Windows PE 3.0, and System Center Configuration Manager 2007 with SP2.

Table 10 lists the top-level nodes in the Deployment Workbench and the types of tasks performed in each node. Table 10. Deployment Workbench Nodes Node Information Center Description Provides access to documentation, displays breaking news about MDT 2010, and lists the components required to use the Deployment Workbench. Lists the deployment shares that this instance of the Deployment Workbench manages. Each deployment share includes operating systems, applications, operating system packages, task sequences, and outof-box drivers populated in the deployment share.

Deployment Shares

The Deployment Workbench automates the download and installation of components used in LTI.
Note If the MDT 2010 computer has Internet connectivity, the Deployment Workbench can automatically download the components.

MDT 2010 uses Windows AIK version 2.0, which includes USMT 4.0 and works for all scenarios except when the target operating system is Windows XP, which USMT 4.0 does not support. In these scenarios, download and use USMT version 3.0 to perform user state migration. To download and install Deployment Workbench components 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Information Center/Components. 3. In the Components pane, in the Available for Download section, click component_name (where component_name is the name of the component you want to download).
Note The offline servicing kernel update, available with the Microsoft TechNet article, “When you use Windows Server 2003 or Windows XP to modify a Windows Vista registry hive,
Solution Accelerators microsoft.com/technet/SolutionAccelerators

the component remains in the Downloaded section. The software that can be deployed includes: • • • • Operating system source files or image files for each operating system to be deployed to the reference and target computers. Operating system packages for the operating systems.microsoft. Device drivers for the reference and target computers that are not included as a part of the operating system. the component is listed in the Downloaded section in the details pane. The Task Sequencer used in MDT 2010 deployments requires that the Create Global Object right be assigned to credentials used to access and run the Deployment Workbench and the deployment process. LTI requires that the: • • Local Administrator account on the target computer be enabled. click Download. On the Check for Updates page of the Check for Updates Wizard. select Check the Internet. In addition. In the details pane. In the details pane. or language packs.com/technet/SolutionAccelerators Solution Accelerators . microsoft. Applications that are to be installed as a part of the operating system image or during the deployment of the reference image. the component appears in the Installed section of the details pane. Also. Obtain the Software Required by the LTI Deployment Process Collect the software to be deployed by LTI. Complete the installation process for the component using the instructions provided for the component. The installation process for the respective component is initiated. such as security updates. 4. and then click Install. Note If there is no Install button. After downloading the component from the Internet. After the component is installed. the Specialized Security – Limited Functionality (SSLF) security profile removes the Create Global Object right and should not be applied to computers being deployed using MDT 2010. is required when using the Deployment Workbench and the Windows AIK on Windows XP with SP2 or Windows Server 2003 with SP1. Tip Check the Internet frequently for updated components. the component cannot be installed or the installation is not necessary. On the Deployment Workbench main menu bar. from the Action menu. click Check for Updates. 5. LTI will import or add this software to deployment shares. This right is typically available to accounts with Administrator-level permissions (unless explicitly removed). click the downloaded component. and then click Check. Local Administrator account be granted the Create Global Objects right. If the component cannot be installed or you did not choose to install it.41 Microsoft Deployment Toolkit 2010 Update 1 Windows Vista registry key flags are removed.com/kb/926044.” at http://support. in the Download section. feature packs.

microsoft. see Estimating Storage Requirements for MDT 2010 Deployment Shares. see Create a New Deployment Share in Deployment Workbench. Ability to have an account automatically log on to the target computer be enabled and not blocked using Group Policy or a local security policy. Thin. Logon banner for the target computers not be enabled using Group Policy or a local security policy. Upgrading an existing deployment share. 2. or Hybrid Images. For more information about determining the number of images required in your organization and subsequently the number of reference computers required. Preparing for LTI Deployment to the Reference Computer For many of the LTI deployment scenarios. or Hybrid Images. If you are deploying thin images and you do not want to create a reference image. Note In some LTI deployment scenarios. For more information about the use of reference computers in MDT 2010–based deployments. Configuring operating system packages as described in Configuring Packages in Deployment Workbench. Create a new deployment share. Later in the LTI deployment process.com/technet/SolutionAccelerators Solution Accelerators . skip the steps that relate to the reference computer. when you want to deploy thin images. you will deploy the captured image of your reference computer to the appropriate target computers. see Upgrade an Existing Deployment Share in Deployment Workbench. including the following: • • • Configuring operating systems as described in Configuring the Operating Systems in Deployment Workbench. you may want to deploy Windows operating systems without creating a reference image—for example. see Choosing Thick. To prepare for deployment to the reference computer 1. Configuring applications as described in View and Configure an Application in Deployment Workbench. see Using Reference Computers in MDT 2010 Deployments. and then capture an image of that computer. Create a reference computer for each image you want to create for deployment to the target computers. For more information about determining which image type to use. For more information about: • • Creating a new deployment share. Thin.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 42 • • • Local Administrator account not have UAC enabled. or upgrade an existing deployment share. Configure the deployment share to contain the appropriate software for deployment to the reference computer. best practice is to create a reference computer as described in Choosing Thick.

updated the deployment share. • The LTI deployment process is unable to perform Sysprep operations on a target computer that is encrypted using BitLocker Drive Encryption.com/technet/SolutionAccelerators . and then capture an image of the reference computer. Solution Accelerators microsoft. Deploying to and Capturing an Image of the Reference Computer in LTI After you have configured the deployment share. start the reference computer with the Windows PE image. operating system packages. 6. device drivers. and applications to the reference computer. Ensure that you do not enable BitLocker Drive Encryption on the reference computer. To deploy to and capture an image of the reference computer 1. Configure any Windows PE options for the deployment share as described in: • Configure the Deployment Share Properties Windows PE x86 Settings Tab. 4.43 Microsoft Deployment Toolkit 2010 Update 1 Configuring device drivers as described in Configuring Device Drivers in Deployment Workbench. 3. Update the deployment share to create the Windows PE images used to start LTI deployment as described in Update a Deployment Share in Deployment Workbench. included in MDT 2010. and created the Windows PE images that include the LTI scripts. • Configure the Deployment Share Properties Windows PE x64 Components Tab. Create a new task sequence that will deploy the target operating system to the reference computer as described in: • • Configuring Task Sequences in Deployment Workbench. The task sequence you created earlier in the process will deploy the target operating system. • Configure the Deployment Share Properties Windows PE x64 Settings Tab. Configuring LTI Task Sequence Steps in Deployment Workbench. Create the LTI bootable media used to start the reference computer as described in Create the LTI Bootable Media. Tip Create the task sequence for deploying to the reference computer based on the Standard Client Task Sequence template. 5. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. • Configure the Deployment Share Properties Windows PE x86 Components Tab. Enable BitLocker Drive Encryption on the target computers only after the target operating system is completely deployed. and complete the Windows Deployment Wizard.

To complete the Windows Deployment Wizard 1. 2. For more information.com/technet/SolutionAccelerators . At the end of the process. Based on the type of computer used for the reference computer.iso and LiteTouchPE_x64. Create the appropriate LTI bootable media from one of these images. Tip To determine the location of the deployment share.wim files (for 64-bit target computers) in the deployment_share\Boot folder (where deployment_share is the network shared folder used as the deployment share). create a UFD. Solution Accelerators microsoft. If the reference computer is a VM. Start the reference computer with the LTI bootable media you created earlier in the process. see Preparing Windows Deployment Services for LTI Deployments. perform one of the following tasks: • • If the reference computer is a physical computer. To create the LTI bootable media 1.iso and LiteTouchPE_x86. the target operating system is deployed on the reference computer. 3. go to deployment_share\Boot (where deployment_share is the network shared folder used as the deployment share). Windows PE starts. CD. Create the LTI Bootable Media You must provide a method for starting the computer with the customized version of Windows PE you created when you updated the deployment share. The Deployment Workbench creates the LiteTouchPE_x86. The LTI bootable media starts Windows PE on the reference computer and initiates the deployment process. In Windows Explorer. view the properties of the share in the Deployment Workbench. or DVD of the ISO file. Complete the Windows Deployment Wizard Start the reference computer with the LTI bootable media you created earlier in the process. Complete the Windows Deployment Wizard to deploy and capture an image of the reference computer as described in Complete the Windows Deployment Wizard. Add the captured reference computer image to the Operating Systems node in the Deployment Workbench as described in Add the Captured Image of the Reference Computer to Deployment Workbench. Note You could also initiate the process by starting the target computer from Windows Deployment Services.wim files (for 32-bit target computers) or the LiteTouchPE_x64. and then the Windows Deployment Wizard starts. and an image of the reference computer is captured.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 44 2. start the VM directly from the ISO file or from a CD or DVD of the ISO file.

Add the Captured Image of the Reference Computer to Deployment Workbench To deploy the captured image of the reference computer to the target computer. The reference computer is now deployed. 4. see the MDT 2010 document. Join a workgroup. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 11 and selecting the values on the other wizard pages that are appropriate to your organization. Note Joining the reference computer to a domain causes problems when deploying the captured image of the reference computer to target computers. The wizard starts. because the LTI process is not able to automatically log on. Information for Completing the Windows Deployment Wizard On this wizard page Select a task sequence to execute on this computer Join the computer to a domain or workgroup Do this Select the task sequence you created for the reference computer deployment. For more information about the errors or warnings. add the captured image to the list of operating systems in the Operating Systems node in the Deployment Workbench. Solution Accelerators microsoft. In the Deployment Summary dialog box. The Import Operating System Wizard copies the operating system files to the deployment_share\Operating Systems\operating_system folder (where deployment_share is the deployment share folder created earlier in the process and operating_system is the name of the operating system added to the deployment share). click Finish. click Details.45 Microsoft Deployment Toolkit 2010 Update 1 2. and record any diagnostic information. The most common symptom of trouble is that the deployment process halts. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. review them. Troubleshooting Reference. 3. and the operating system deployment starts. Specify whether to capture an image Click Capture an image of this reference computer. If any errors or warnings occur. In the Deployment Summary dialog box. At the end of the deployment process. including the WIM file name. and the captured WIM file of the reference computer is stored in the location you specified on the Specify whether to capture an image wizard page. Table 11. the Deployment Summary dialog box appears.com/technet/SolutionAccelerators . and provide the fully qualified Universal Naming Convention (UNC) path for the name of the captured Windows Imaging Format (WIM) image.

com/technet/SolutionAccelerators . prepare Windows Deployment Services to start the appropriate Windows PE images that will in turn start LTI deployment to the target computers as described in Preparing Windows Deployment Services for LTI Deployments (if you are using Windows Deployment Services to start the process). and the MDT DB for each deployment scenario as described in: • Prepare for the New Computer Deployment Scenario to Target Computers Using LTI. 2. • Prepare for a Refresh Computer Deployment Scenario to Target Computers Using LTI.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 46 Add the captured image of the reference computer by completing the operating system import process as described in Import a Previously Captured Image of a Reference Computer. In preparation. and customize the deployment process. ensure that the necessary deployment resources exist. 4. Solution Accelerators microsoft. Prepare network shares for storing migration data and MDT 2010 deployment logs as described in Preparing the MDT 2010 Migration Resources. 3. Information for Completing the Importing a Previously Captured Image of a Reference Computer On this wizard page Image Do this In Source File. • Prepare for a Replace Computer Deployment Scenario to Target Computers Using LTI. Prepare the MDT 2010 task sequences. Preparing for LTI Deployment to Target Computers With the images of the reference computer captured. Table 12. The captured image of the reference computer is added to the list of operating systems in the information pane and is copied to the deployment share. The Import Operating System Wizard finishes. To prepare for deployment to the target computers 1. deploy the images to the target computers. specify the fully qualified path to the WIM file of the captured image of the reference computer. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 12 and selecting the values on the other wizard pages that are appropriate to your organization. create one or more task sequences for deploying the captured images. Create additional deployment shares to help in larger deployments as described in Create a New Deployment Share in Deployment Workbench. the MDT 2010 configuration files. Optionally.

Use the Standard Client Task Sequence or Standard Server Task Sequence templates to deploy the captured image of the reference computer to the target computer. Optionally.com/technet/SolutionAccelerators . To prepare for the New Computer deployment scenario 1. 4. customize the MDT DB to the needs of your organization as described in Performing Deployments Using the MDT DB (if you are using the MDT DB to provide MDT 2010 configuration information). Prepare for the New Computer Deployment Scenario to Target Computers Using LTI In the New Computer deployment scenario. 3. Information for Completing the New Task Sequence Wizard for Performing New Computer Deployment Scenario On this wizard page Select OS Do this Select the captured image of the reference computer. any combination of the deployments scenarios might be necessary.47 Microsoft Deployment Toolkit 2010 Update 1 Depending on the target computers in your organization. Configure the Deployment Share Properties Windows PE x86 Components Tab. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. There is no user migration information to save and restore and no existing file systems to preserve. a new installation of a Windows operating system is deployed to a new computer. Solution Accelerators microsoft. Verify the Windows PE options for each deployment share as described in: • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. Create a new task sequence that will deploy the captured image of the reference computer to the target computer as described in the following list. Configure the Deployment Share Properties Windows PE x64 Settings Tab. Table 13. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 13 and select the values on the other wizard pages that are appropriate to your organization: • • Configuring Task Sequences in Deployment Workbench Configuring LTI Task Sequence Steps in Deployment Workbench Tip Create the task sequence for deploying to the target computer based on the Standard Client Task Sequence or Standard Server Task Sequence templates included in MDT 2010. see Identifying Deployment Scenarios. For more information about the MDT 2010 deployment scenarios. 2.

Create a new task sequence that will deploy the captured image of the reference computer to the target computer as described in the following list. Information for Completing the New Task Sequence Wizard for Performing a Refresh Computer Deployment Scenario On this wizard page Select OS Do this Select the captured image of the reference computer.com/technet/SolutionAccelerators . 3. Use the Standard Client Task Sequence or Standard Server Task Sequence templates to deploy the captured image of the reference computer to the target computer. • Prepare for a Refresh Computer Deployment Scenario to Target Computers Using LTI In the Refresh Computer deployment scenario. 5. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. Replicate Linked Deployment Shares in Deployment Workbench. because the existing file systems on the target computer are not preserved. linked deployment share. a computer is refreshed—that is. 2. customize the MDT DB to the needs of your organization as described in Performing Deployments Using the MDT DB (if you are using the MDT DB to provide MDT 2010 configuration information). ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 14 and select the values on the other wizard pages that are appropriate to your organization: • • Configuring Task Sequences in Deployment Workbench Configuring LTI Task Sequence Steps in Deployment Workbench Tip Create the task sequence for deploying images to the target computer based on the Standard Client Task Sequence or Standard Server Task Sequence templates included in MDT 2010. Update each deployment share. Generate Media Images in Deployment Workbench. You must save and restore the user migration information.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 48 Configure the Deployment Share Properties Windows PE x64 Components Tab. 4. re-imaged for image standardization or to address a problem. Optionally. Table 14. To prepare for the Refresh Computer deployment scenario 1. Verify the Windows PE options for each deployment share as described in: Solution Accelerators microsoft. and media to create the Windows PE images used to start LTI deployment as described in: • • • Update a Deployment Share in Deployment Workbench.

49 Microsoft Deployment Toolkit 2010 Update 1 • • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. Tip Create the task sequence for capturing the user state of the existing target computer based on the Standard Client Task Replace Sequence template included in MDT 2010. a new installation of Windows is deployed to a new computer. Use the: • Standard Client Replace Task Sequence template to save the user state migration data of the existing target computer. Important Run this task sequence on the new target computer after running the task sequence based on the Standard Client Replace Task Sequence template on the existing target computer. Configure the Deployment Share Properties Windows PE x64 Settings Tab. • Standard Client Task Sequence template to deploy the captured image of the reference computer to the new target computer and restore the user state migration data. Then. linked deployment share. Replicate Linked Deployment Shares in Deployment Workbench. The existing user state migration data is saved from the original computer to a network shared folder or removable media. Important Run this task sequence on the existing target computer before running the task sequence based on the Standard Client Task Sequence template on the new target computer. Configure the Deployment Share Properties Windows PE x86 Components Tab. Solution Accelerators microsoft. Configure the Deployment Share Properties Windows PE x64 Components Tab. and media to create the Windows PE images used to start LTI deployment as described in: • • • Update a Deployment Share in Deployment Workbench. Finally.com/technet/SolutionAccelerators . Update each deployment share. the user state data is restored to the new computer. one computer replaces another computer. To prepare for the Replace Computer deployment scenario 1. 5. Generate Media Images in Deployment Workbench. Configuring LTI Task Sequence Steps in Deployment Workbench. Create a new task sequence that will save the user state migration data of the existing target computer as described in: • • Configuring Task Sequences in Deployment Workbench. because the file systems on the new computer are formatted as part of the new installation of Windows. Prepare for a Replace Computer Deployment Scenario to Target Computers Using LTI In the Replace Computer deployment scenario.

Prepare for an Upgrade Computer Deployment Scenario to Target Computers Using LTI In the Upgrade Computer deployment scenario.com/technet/SolutionAccelerators . Configure the Deployment Share Properties Windows PE x64 Settings Tab. Information for Completing the New Task Sequence Wizard for Performing the Refresh Computer Deployment Scenario On this wizard page Select OS Do this Select the captured image of the reference computer.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 50 2. Table 15. Configure the Deployment Share Properties Windows PE x64 Components Tab. 5. customize the MDT DB to the needs of your organization as described in Performing Deployments Using the MDT DB (if you are using the MDT DB to provide MDT 2010 configuration information). 6. Verify the Windows PE options for each deployment share as described in: • • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. You do not need to save Solution Accelerators microsoft. the existing operating system on a computer is upgraded to the newer operating system. Replicate Linked Deployment Shares in Deployment Workbench. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. Optionally. Update each deployment share. linked deployment share. included in MDT 2010. 4. 3. Create a new task sequence that will deploy the captured image of the reference computer to the new target computer and restore the user state migration data saved by the task sequence in the previous step as described in the following list. and media to create the Windows PE images used to start LTI deployment as described in: • • • Update a Deployment Share in Deployment Workbench. Configure the Deployment Share Properties Windows PE x86 Components Tab. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 15 and select the values on the other wizard pages that are appropriate to your organization: • • Configuring Task Sequences in Deployment Workbench Configuring LTI Task Sequence Steps in Deployment Workbench Tip Create the task sequence for deploying to the new target computer based on the Standard Client Task Sequence template. Generate Media Images in Deployment Workbench.

If you do not provide the appropriate product key. Configure the Deployment Share Properties Windows PE x86 Components Tab. Create a new task sequence that will deploy the captured image of the reference computer to the target computer as described in the following list. linked deployment share. 5. Optionally. if one exists. and will cause the deployment process to fail with an invalid product key error. Note Ensure that you provide a Windows 7 or Windows Server 2008 R2 product key when upgrading from Windows Vista or Windows Server 2008. customize the MDT DB to the needs of your organization as described in Performing Deployments Using the MDT DB (if you are using the MDT DB to provide MDT 2010 configuration information). Information for Completing the New Task Sequence Wizard for Performing an Upgrade Computer Deployment Scenario On this wizard page Select OS Do this Select the captured image of the reference computer. 2. respectively. Configure the Deployment Share Properties Windows PE x64 Settings Tab. 4. Update each deployment share. To prepare for the Upgrade Computer deployment scenario 1. ensuring that you specifically follow the configuration setting on the wizard pages listed in Table 16 and select the values on the other wizard pages that are appropriate to your organization: • • Configuring Task Sequences in Deployment Workbench Configuring LTI Task Sequence Steps in Deployment Workbench Tip Create the task sequence for deploying to the target computer based on the Standard Client Task Sequence or Standard Server Task Sequence template included in MDT 2010. and media to create the Windows PE images used to start LTI deployment as described in: Solution Accelerators microsoft. the upgrade process will attempt to use a down-level product key. Table 16. Verify the Windows PE options for each deployment share as described in: • • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. Configure the Deployment Share Properties Windows PE x64 Components Tab.com/technet/SolutionAccelerators . because the existing file systems on the target computer are preserved and the new operating system upgrades the data. Use the Standard Client Task Sequence or Standard Server Task Sequence template to deploy the captured image of the reference computer to the target computer. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. 3.51 Microsoft Deployment Toolkit 2010 Update 1 and restore the user state migration data.

Depending on the target computers in your organization. Deploy Captured Images to Target Computers in the Replace Computer Deployment Scenario Using LTI. see Identifying Deployment Scenarios. Windows PE starts. any combination of the deployment scenarios might be necessary. Replicate Linked Deployment Shares in Deployment Workbench. For more information about the MDT 2010 deployment scenarios. and then the Windows Deployment Wizard starts. 2. Generate Media Images in Deployment Workbench. At the end of the process. Deploy the captured image of the reference computer to target computers for each of the deployment scenarios in your organization as described in: • • • Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using LTI. the captured image of the reference computer is deployed on the target computers. Table 17.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 52 • • • Update a Deployment Share in Deployment Workbench. Information for Completing the Windows Deployment Wizard for the New Computer Deployment Scenario Using LTI Solution Accelerators microsoft. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 17 and select the values on the other wizard pages that are appropriate to your organization. Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using LTI Start the target computer with the LTI bootable media you created earlier in the process or from Windows Deployment Services. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard.com/technet/SolutionAccelerators . Deploying Captured Images to Target Computers in LTI The deployment of the captured images to the target computers is slightly different for LTI. Start the reference computer with the LTI bootable media you created earlier in the process or from Windows Deployment Services. The LTI bootable media starts Windows PE on the target computer and initiates deployment. To complete the Windows Deployment Wizard 1. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using LTI.

see the MDT 2010 document. In the Deployment Summary dialog box. The Windows Deployment Wizard saves the user state migration data of the existing target computer to the location you specify. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using LTI Start the Windows Deployment Wizard on the existing operating system on the target computer to start the Standard Client task sequence or Standard Server task sequence created earlier in the process. The wizard starts. The target computers are now deployed.vbs. microsoft. click Details. click Finish. and record any diagnostic information. Information for Completing the Windows Deployment Wizard for the Refresh Computer Deployment Scenario Using LTI On this wizard page Select a task sequence to execute on this computer Choose a migration type. and the operating system deployment starts. In the Deployment Summary dialog box. Later in the task sequence. Start the Windows Deployment Wizard by connecting to the appropriate deployment share (for example. the Deployment Summary dialog box appears. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. 4. Solution Accelerators Do this Select the task sequence you created for the target computer deployment for the Refresh Computer deployment scenario. Table 18. \\servername\Distribution$\Scripts) and typing cscript litetouch. Troubleshooting Reference. Click Refresh this computer. To complete the Windows Deployment Wizard 1. The Windows Deployment Wizard starts. the user state migration data is restored to the target computer. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 18 and select the values on the other wizard pages that are appropriate to your organization.53 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Select a task sequence to execute on this computer Do this Select the task sequence you created for the target computer deployment for the New Computer deployment scenario.com/technet/SolutionAccelerators . At the end of the process. If any errors or warnings occur. review them. 3. For more information about the errors or warnings. 2.

If any errors or warnings occur. The target computer is now deployed. click Finish. For more information about the errors or warnings. 3. the Deployment Summary dialog box appears. Run the wizard the first time to capture the user state migration data from the existing target computer (old computer). In the Deployment Summary dialog box. see the MDT 2010 document. click Details. Save the User State Migration Data from the Existing Target Computer Using LTI Start the Windows Deployment Wizard on the existing operating system on the target computer to start the Standard Client Replace Task Sequence template created earlier in the process. Troubleshooting Reference.com/technet/SolutionAccelerators . and record any diagnostic information. run it again to deploy the captured image of the reference computer to the new target computer (new computer) and restore the user state saved earlier in the process.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 54 On this wizard page Specify where to save your data and settings. review them. Then. and the operating system deployment starts. Do this Select one of the following options based on the requirements of your organization: • Automatically determine the location • Specify a location The wizard starts. To complete the Windows Deployment Wizard Solution Accelerators microsoft. Deploy the captured image of the reference computer to the new target computer as described in Deploy the Captured Image of the Reference Computer to the New Target Computer Using LTI. In the Deployment Summary dialog box. To deploy captured images of the reference computer 1. Ensure that the user state migration data is stored in a consistent and secure location so that the data can be readily restore later in the LTI process. Save the user state migration data from the existing target computer as described in Save the User State Migration Data from the Existing Target Computer Using LTI. 2. The Windows Deployment Wizard saves the user state migration data of the existing target computer to the location you specify. 4. Deploy Captured Images to Target Computers in the Replace Computer Deployment Scenario Using LTI The Replace Computer deployment scenario requires that you run the Windows Deployment Wizard twice. At the end of the process.

com/technet/SolutionAccelerators . Deploy the Captured Image of the Reference Computer to the New Target Computer Using LTI Start the target computer with the LTI bootable media you created earlier in the process or from Windows Deployment Services. In the Deployment Summary dialog box. review them. Specify where to save a complete computer backup Do this Select the task sequence you created for the target computer in the Replace Computer deployment scenario to save the user state migration data. and then type the fully qualified path to the location in which you want to store the backup. and record any diagnostic information. The Windows Deployment Wizard starts. Table 19. The wizard starts.vbs. At the end of the process. Troubleshooting Reference. This location must be accessible to the new target computer. The user state migration data of the existing target computer is saved. perform a full backup using your organization’s backup software. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 19 and select the values on the other wizard pages that are appropriate to your organization. In the Deployment Summary dialog box. 2. \\servername\Distribution$\Scripts) and typing cscript litetouch. 4. The LTI bootable media starts Solution Accelerators microsoft. and the operating system deployment starts. click Details. the Deployment Summary dialog box appears. 3. click Finish. In the Location box. If any errors or warnings occur. For more information about the errors or warnings. Note This backup is for use in restoring user state migration data that might have been missed. Information for Completing the Windows Deployment Wizard for the Replace Computer Deployment Scenario for Saving User State Migration Data Using LTI On this wizard page Select a task sequence to execute on this computer Specify where to save your data and settings.55 Microsoft Deployment Toolkit 2010 Update 1 1. type the fully qualified path to the location in which you want to store the user state migration data. Click Specify a location. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. see the MDT 2010 document. If you want to have rollback capability for the target computer. not as a rollback method for the target computer. Start the Windows Deployment Wizard by connecting to the appropriate deployment share (for example.

and record any diagnostic information. Deploy Captured Images to Target Computers in the Upgrade Computer Deployment Scenario Using LTI Start the Windows Deployment Wizard on the existing operating system on the target computer to start the Standard Client task sequence or Standard Server task sequence created earlier in the process. click Finish. Windows PE starts. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 20 and select the values on the other wizard pages that are appropriate to your organization. user state is upgrade along with the operating system. The wizard starts. see the MDT 2010 document. and then the Windows Deployment Wizard starts. 3. Click the Specify a location option and type the location of the saved user state migration data in the Location box. Start the reference computer with the LTI bootable media you created earlier in the process or from Windows Deployment Services. If any errors or warnings occur. At the end of the process. To deploy the captured image of the reference computer 1. the Deployment Summary dialog box appears. For the Upgrade Computer deployment scenario. In the Deployment Summary dialog box. Troubleshooting Reference.com/technet/SolutionAccelerators . To complete the Windows Deployment Wizard Solution Accelerators microsoft. Table 20. For more information about the errors or warnings. In the Deployment Summary dialog box. 2. the captured image of the reference computer is deployed to the target computer. review them.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 56 Windows PE on the target computer and initiates LTI deployment. At the end of the process. 4. and the operating system deployment starts. click Details. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. Information for Completing the Windows Deployment Wizard for the Replace Computer Deployment Scenario for Deploying the Captured Image On this wizard page Select a task sequence to execute on this computer Specify whether to restore user data Do this Select the task sequence you created for the target computer for the Replace Computer deployment scenario.

For more information about the errors or warnings. 4. see the MDT 2010 document. click Finish. \\server_name\Distribution$\Scripts) and typing cscript litetouch. 3. Click Upgrade this computer. Solution Accelerators microsoft. Troubleshooting Reference. Start the Windows Deployment Wizard by connecting to the appropriate deployment share (for example. Information for Completing the Windows Deployment Wizard for the Upgrade Computer Deployment Scenario Using LTI On this wizard page Select a task sequence to execute on this computer Choose a migration type Do this Select the task sequence you created for the target computer deployment for the Upgrade computer deployment scenario. 2.57 Microsoft Deployment Toolkit 2010 Update 1 1. If any errors or warnings occur. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. click Details. and the operating system deployment starts. review them. In the Deployment Summary dialog box. In the Deployment Summary dialog box. At the end of the process.vbs. and record any diagnostic information. The Windows Deployment Wizard starts. the Deployment Summary dialog box appears. Table 21. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 21 and select the values on the other wizard pages that are appropriate to your organization.com/technet/SolutionAccelerators . The wizard starts.

. Configuring device drivers as described in Configuring Device Drivers in the Deployment Workbench. operating system packages. Managing Deployment Shares in Deployment Workbench MDT 2010 uses the Deployment Workbench to manage the deployment shares in your organization. Upgrading an existing deployment share to MDT 2010 as described in Upgrade an Existing Deployment Share in Deployment Workbench. and device drivers. Configuring the applications to be deployed as described in Configuring Applications in Deployment Workbench. Performing common administrative tasks as described in Configuring LTI Task Sequence Steps in Deployment Workbench. it does not have to reside on any specific computer. Opening an existing deployment share as described in Open an Existing Deployment Share in the Deployment Workbench. You configure the deployment shares by: • • • Creating a new deployment share as described in Create a New Deployment Share in the Deployment Workbench. You can store a deployment share on a local drive. or in a stand-alone distributed file system (DFS).Using the Microsoft Deployment Toolkit: Managing LTI Deployments 58 Managing LTI Deployments in Deployment Workbench Deployment shares are the repository for all the deployment files used in LTI deployment. Deployment shares contain operating systems. Configuring task sequences as described in Configuring Task Sequences in the Deployment Workbench. Configuring the operating systems as described in Configuring Operating Systems in Deployment Workbench. applications. Performing advanced configuration tasks as described in Performing Advanced Configuration Tasks in Deployment Workbench. Performing common administrative tasks as described in Performing Common Management Tasks in Deployment Workbench. Manage deployment shares in the Deployment Workbench by: • • • • • • • • • Managing shares as described in Managing Deployment Shares in the Deployment Workbench. in a network shared folder. Configuring packages as described in Configuring Packages in the Deployment Workbench.

type share_name (where share_name is the share name for the folder on a local drive specified on the Path wizard page). Complete the New Deployment Share Wizard using the information in Table 22. In the Actions pane. click Browse to find the existing folder on a local drive or network shared folder. 4. Table 22. and then point to All Programs. 3. go to Deployment Workbench/Deployment Shares. and then click Deployment Workbench. In Share name.com/technet/SolutionAccelerators . In the Deployment Workbench console tree. click New Deployment Share.59 Microsoft Deployment Toolkit 2010 Update 1 • • • • • Configuring a deployment share as described in Configure a Deployment Share in the Deployment Workbench. 2. perform the following steps: 1. Solution Accelerators microsoft. Updating a deployment share as described in Update a Deployment Share in the Deployment Workbench. Information for Completing the New Deployment Share Wizard On this wizard page Path Do this In Deployment share path. Based on your security requirements. The New Deployment Share Wizard starts. and then click Next. 2. Share Note This page is displayed only if you entered a path to a folder on a local drive on the Path wizard page. Point to Microsoft Deployment Toolkit. Click Start. and then click Next. Copying a deployment share as described in Copy a Deployment Share. Create a New Deployment Share in Deployment Workbench To create a new deployment share. Closing a deployment share as described in Close a Deployment Share in the Deployment Workbench. Note Alternatively. Note the fully qualified to UNC path to the share being created listed immediately below the Share name box. Creating bootable devices to start LTI from the MDT 2010 boot images as described in Create Bootable Devices from MDT 2010 Boot Images. type path (where path is the fully qualified path to an existing folder on a local drive or a network shared folder created earlier in the deployment process). Note The wizard grants the local group Everyone Full Control access at the share level. 1.

Descriptive Name In Deployment share description. If the check box is: • Selected. Allow Image Capture Allow Admin Password Select or clear the Ask user to set the local Administrator Password check box based on requirements. Note By default. and then click Next. • Cleared. this check box is selected. This check box configures the Windows Deployment Wizard to allow the user to optionally capture an image of the target computer. the password can be configured in the Windows Deployment Wizard. If the check box is: • Selected. type description (where description is a descriptive name that for the deployment share specified on previous wizard pages). • Cleared. and then click Next.com/technet/SolutionAccelerators Solution Accelerators . Select or clear the Ask if an image should be captured check box based on requirements. Note By default. the product key can be configured in the Windows Deployment Wizard. this check box is cleared. the path for storing the image and the image name can be configured in the Windows Deployment Wizard. If the check box is: • Selected. and then click Next.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 60 On this wizard page Do this you may want to restrict the security of the share. This check box configures the Windows Deployment Wizard to allow the user to provide the password for the local Administrator account during the deployment process. This check box configures the Windows Deployment Wizard to allow the user to provide a product key for the target operating system during the deployment process. microsoft. which is usually the reference computer. the password must be set in the MDT 2010 configuration file or database. an image is not capture or the imagecapture information must be set in the MDT 2010 configuration file or database. Allow Product Key Select or clear the Ask user for a product key check box based on your requirements. and then click Next.

Summary Confirmation Review the information in the Details box. Click Start. Start the Open Deployment Share Wizard by: • • • Right-clicking the Deployment Shares node. Tip Click Save Output to save the output of the wizard to a file. In the Deployment Workbench console tree. Click Close. in the Actions pane. and then clicking Open Deployment Share. Clicking the Deployment Shares node.com/technet/SolutionAccelerators . In the Actions pane. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. The Open Deployment Share Wizard starts. Table 23. Point to Microsoft Deployment Toolkit. Note By default. and then. go to Deployment Workbench/Deployment Shares. from the Action menu. and then click Deployment Workbench. and then point to All Programs. type share_path microsoft. 3. click Open Deployment Share. the product key must be set in the MDT 2010 configuration file or database.61 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this • Cleared. Open an Existing Deployment Share in Deployment Workbench The Deployment Workbench can open an existing deployment share using the Open Deployment Share Wizard. 2. Information for Completing the Open Deployment Share Wizard On this wizard page Path Solution Accelerators Do this 1. and then click Next. the new deployment share is created in the target folder you selected in the wizard and appears in the Deployment Workbench. this check box is cleared. Upon completion. and then. clicking Open Deployment Share. In Deployment share path. 4. Complete the Open Deployment Share Wizard using the information in Table 23. Clicking the Deployment Shares node. To open an existing deployment share not already listed in Deployment Workbench 1. clicking Open Deployment Share.

the existing deployment share is upgraded (if required). Click Finish. and the Upgrade the content of the deployment share (if required) check box is selected. Start the wizard by Solution Accelerators microsoft. 2. the Open Deployment Share Wizard will not upgrade the deployment share. Summary Confirmation Review the information in the Details box. Note You can alternatively click Browse to find the local or network shared folder. The deployment share is added to the details pane in the Deployment Workbench. 3. • Cleared. the Open Deployment Share Wizard upgrades the deployment share.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 62 On this wizard page Do this (where share_path is the fully qualified path to the existing deployment share). Upgrade an existing deployment share by: • Opening an existing deployment share that is not already listed in the Deployment Workbench as described in Upgrade Deployment Shares Not Already Listed in Deployment Workbench. Upgrade an Existing Deployment Share in Deployment Workbench MDT 2010 can upgrade an existing BDD 2007 deployment share. • Upgrade Deployment Shares Not Already Listed in Deployment Workbench Upgrade deployment shares not listed in the Deployment Workbench using the Open Deployment Share Wizard. Click Next.com/technet/SolutionAccelerators . or a pre-release version of MDT 2010 deployment share to MDT 2010. Select the Upgrade the content of the deployment share (if required) check box. If the check box is: • Selected. After the wizard finishes. and then click Next. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Tip You can click Save Output to save the output of the wizard to a file. an MDT 2008 deployment share. Upgrading an existing deployment share that is listed in the Deployment Workbench as described in Upgrade Deployment Shares Already Listed in Deployment Workbench.

Clicking the deployment share. In Deployment share path. and then. To upgrade deployment shares that are not already listed in the Deployment Workbench. and then clicking Open Deployment Share. 4. Table 24.63 Microsoft Deployment Toolkit 2010 Update 1 • • • Right-clicking the deployment share. Summary Confirmation Review the information in the Details box. clicking Open Deployment Share. The deployment share is added to the details pane in the Deployment Workbench. and then click Next. Click Finish. and the Upgrade the content of the deployment share (if required) check box is selected. and then point to All Programs. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. in the Actions pane. perform the following steps: 1. Tip Click Save Output to save the output of the wizard to a file. Note Alternatively. Solution Accelerators microsoft. In the Actions pane. 2. The Open Deployment Share Wizard starts. and then. click Open Deployment Share.com/technet/SolutionAccelerators . In the Deployment Workbench console tree. Select the Upgrade the content of the deployment share (if required) check box. Information for Completing the Open Deployment Share Wizard On this wizard page Path Do this 1. type share_path (where share_path is the fully qualified path to the existing deployment share). go to Deployment Workbench/Deployment Shares. and then click Next. clicking Open Deployment Share. 3. Point to Microsoft Deployment Toolkit. Complete the Open Deployment Share wizard using the information in Table 24. from the Actions menu. 2. After the wizard finishes. click Browse to find the local or network shared folder. and then click Deployment Workbench. the existing deployment share is upgraded (if required). Click Start. Clicking the deployment share.

Point to Microsoft Deployment Toolkit. Table 25. clicking Upgrade Deployment Share. 4. To upgrade existing deployment shares already listed in the Deployment Workbench. and then point to All Programs. Click Finish. Clicking the deployment share. 3. Clicking the deployment share. Upgrade Deployment Shares Already Listed in Deployment Workbench Upgrade existing deployment shares already listed in the Deployment Workbench using the Upgrade Deployment Share Wizard. In the Deployment Workbench console tree. any existing installations of previous versions of MDT or BDD must be upgraded to MDT 2010. click Upgrade Deployment Share. Click Start. see Upgrading to MDT 2010. and then clicking Upgrade Deployment Share. Tip Click Save Output to save the output of the wizard to a file. For more information on upgrading any previous installations to MDT 2010.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 64 In addition to upgrading existing deployment shares. and then. Complete the Upgrade Deployment Share wizard using the information in Table 25. the existing deployment share is upgraded and now can be accessed in the Deployment Workbench. in the Actions pane. After the wizard finishes. and then. 2. Solution Accelerators microsoft. and then click Deployment Workbench. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. clicking Upgrade Deployment Share. go to Deployment Workbench/Deployment Shares. Start the wizard by: • • • Right-clicking the deployment share. and then click Next. perform the following steps: 1. In the Actions pane.com/technet/SolutionAccelerators . The Upgrade Deployment Share Wizard starts. from the Actions menu. Information for Completing the Upgrade Deployment Share Wizard On this wizard page Summary Confirmation Do this Review the information in the Details box.

Configure the settings on the Windows PE x86 Settings tab as described in Configure the Deployment Share Properties Windows PE x86 Settings Tab.com/technet/SolutionAccelerators . 2. and then point to All Programs. 3. On the General tab. In the Deployment Workbench console tree. Point to Microsoft Deployment Toolkit. Solution Accelerators microsoft. click Properties. and then click Deployment Workbench. Configure the settings on the Windows PE x64 Settings tab as described in Configure the Deployment Share Properties Windows PE x64 Settings Tab. In the Actions pane. click deployment_share (where deployment_share is the name of the deployment share). configure the settings listed in Table 26 based on the requirements of your organization. To configure the General tab 1. You can update the deployment share properties on the General tab through the deployment_share Properties dialog box (where deployment_share is the name of the deployment share in the Deployment Workbench). go to Deployment Workbench/Deployment Shares. Configure an application in the Deployment Workbench by performing the following tasks in the Application Properties dialog box: • • • • Configure the settings on the General tab as described in Configure the Deployment Share Properties General Tab. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). 4. Click Start. Configure the settings on the Rules tab as described in Configure the Deployment Share Properties Rules Tab.65 Microsoft Deployment Toolkit 2010 Update 1 Configure a Deployment Share in Deployment Workbench You can view the properties of deployment shares beneath the Deployment Shares node in the Deployment Workbench by using the Properties actions as described in View Item Properties in Deployment Workbench. 5. Configure the settings on the Windows PE x86 Components tab as described in Configure the Deployment Share Properties Windows PE x86 Components Tab. Configure the settings on the Windows PE x64 Components tab as described in Configure the Deployment Share Properties Windows PE x64 Components Tab. • • Configure the Deployment Share Properties General Tab The deployment share properties stored on the General tab are mostly configured when you run the New Deployment Share Wizard. In the details pane. and then click OK.

then this text box is empty. Select to configure the Update Deployment Share Wizard to create WIM files and bootable media for 64-bit target computers. For more information about enabling multicastbased deployments. The default value is MDT Deployment Share. Platforms supported: x86 Platforms supported: x64 Enable multicast for this deployment share Select to configure the Update Deployment Share Wizard to create WIM files and bootable media for 32-bit target computers. If you created the deployment share from: • A local path. Text box that contains fully qualified UNC path to the deployment share. Note If you created the deployment share from a local path. then this text box contains the local path used in the creation process. Select to configure Windows Deployment Services to enable multicast deployment of images generated in this deployment share. • An existing network shared folder. This value is used only to enable multicast and is required if you want to do so by selecting the Enable multicast for this deployment share check box.com/technet/SolutionAccelerators Solution Accelerators . If you select this check box. the local path rather than the UNC path is displayed in the details pane of the Deployment Workbench. see Enable Windows Deployment Services Multicast Deployment for microsoft. Note If the deployment share was created from an existing network shared folder. Configuration Settings on the General Tab of Deployment Share Properties Setting Description Description Contains the name of the deployment share displayed in the Deployment Workbench. you must provide values for the Network (UNC) path and Local path boxes. Comments Network (UNC) path Local path Contains the fully qualified path to the local folder in which the deployment share was created. this value is displayed in the details pane of the Deployment Workbench. This value is used only to enable multicast and is required if you want to do so by selecting the Enable multicast for this deployment share check box.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 66 Table 26. Provides information about the deployment share.

In the Deployment Workbench console tree. configure the settings listed in Table 27 based on the requirements of your organization. which is in the deployment share’s Control folder. On the Rules tab.ini Edit Bootstrap. 3. In the details pane. Point to Microsoft Deployment Toolkit. 5. Configure the Deployment Share Properties Rules Tab The deployment share properties stored on the Rules tab are mostly configured when you run the New Deployment Share Wizard. To configure the Rules tab 1.ini. 2. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). see the MDT 2010 document. go to Deployment Workbench/Deployment Shares. For more information about the settings that you can configure on this tab. In the Actions pane. and then click Deployment Workbench. and the deployment share appears in the details pane of the Deployment Workbench. and then click OK. The deployment share configuration settings are saved. The deployment share configuration settings are saved. click deployment_share (where deployment_share is the name of the deployment share). click Properties. These settings reside in CustomSettings.ini Description Contains the current configuration of the CustomSetting.ini file for the deployment share.ini file that the Deployment Workbench generates. Configuration Settings on the Rules Tab of Deployment Share Properties Setting CustomSettings. Toolkit Reference. Click Start. Note The multicast features of MDT 2010 are available using Windows Deployment Services in Windows Server 2008 or later operating systems. Table 27. 4. and then point to All Programs.67 Microsoft Deployment Toolkit 2010 Update 1 Setting Description LTI Deployments. Click to modify the contents of the Bootstrap.com/technet/SolutionAccelerators . Solution Accelerators microsoft. and the deployment share appears in the details pane of the Deployment Workbench.

In the Actions pane.wim file with the image description specified in the Image description text box. the Update Deployment Share Wizard will not create the WIM file. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). Configuration Settings on the Windows PE x86 Settings Tab of Deployment Share Properties Setting Generate a Lite Touch Windows PE WIM file Description Select to configure the Update Deployment Share Wizard to create a Windows PE WIM file that includes the LTI deployment scripts. the Update Deployment Share Wizard creates the LiteTouchPE_x86. Point to Microsoft Deployment Toolkit. and then click OK. 4. On the Windows PE x86 Settings tab. Select to configure the Update Deployment Share Wizard to create a bootable Windows PE ISO file that includes the LTI deployment scripts. click deployment_share (where deployment_share is the name of the deployment share). • Cleared. 2. and then click Deployment Workbench.com/technet/SolutionAccelerators Image description Generate a Lite Touch bootable ISO image Solution Accelerators . and then point to All Programs. In the Deployment Workbench console tree. click Properties. Table 28. To configure the Windows PE x86 Settings tab 1. 5. If the check box is: • Selected. 3. The default value is Lite Touch Windows PE (x86).Using the Microsoft Deployment Toolkit: Managing LTI Deployments 68 Configure the Deployment Share Properties Windows PE x86 Settings Tab The deployment share properties stored on the Windows PE x86 Settings tab are mostly configured when you run the New Deployment Share Wizard. go to Deployment Workbench/Deployment Shares. In the details pane. the Update Deployment Share Wizard creates the ISO file with the name microsoft. Contains the image description for the Windows PE WIM file that the Update Deployment Share Wizard creates. Click Start. If the check box is: • Selected. configure the settings listed in Table 28 based on the requirements of your organization.

microsoft. Note This text box is enabled only if you select Generate a Lite Touch bootable ISO image. the Update Deployment Share Wizard creates the Generic_x86. Note This box is enabled only if you select Generate a generic Windows PE WIM file. ISO file name Contains the file name for the generic Windows PE ISO file that the Update Deployment Share Wizard creates. Image description Contains the image description for the generic Windows PE WIM file that the Update Deployment Share Wizard creates. The default value for this text box is LiteTouchPE_x86. Generate a generic Select to configure the Update Deployment Share Windows PE WIM file Wizard to create a Windows PE WIM file that does not include the LTI deployment scripts. • Cleared.iso. the Update Deployment Share Wizard will not create the WIM file. Note This text box is enabled only if you select Generate a generic Windows PE WIM file. The default value for this text box is Generic Windows PE (x86). Generate a generic bootable ISO image Select to configure the Update Deployment Share Wizard to create a bootable Windows PE ISO file that does not include the LTI deployment scripts.com/technet/SolutionAccelerators Solution Accelerators . the Update Deployment Share Wizard will not create the ISO file.iso file with the image description specified in the ISO file name text box.69 Microsoft Deployment Toolkit 2010 Update 1 Setting Description specified in the ISO file name text box. ISO file name Contains the file name for the Windows PE ISO file that the Update Deployment Share Wizard creates. If the check box is: • Selected. • Cleared. the Update Deployment Share Wizard will not create the ISO file.wim file with the image description specified in the Image description text box. The default value for this text box is Generic_x86.iso. • Cleared. the Update Deployment Share Wizard creates the GenericPE_x86. If the check box is: • Selected.

128. Configures the size of the scratch space in megabytes. or 512 MB. The default value is 32. Table 29. Custom background bitmap file Contains the fully qualified path to the BMP file that is to be used as the custom background bitmap.bmp. 4. Configuration Settings on the Windows PE x86 Components Tab of Deployment Share Properties Setting ADO Solution Accelerators Description Select to add optional ADO components to the microsoft. and the deployment share appears in the details pane of the Deployment Workbench. go to Deployment Workbench/Deployment Shares. Contains the fully qualified path to a folder structure to be included in the Windows PE images. and then click Deployment Workbench. Configure the Deployment Share Properties Windows PE x86 Components Tab The deployment share properties stored on the Windows PE x86 Components tab are mostly configured when you run the New Deployment Share Wizard. In the details pane. Point to Microsoft Deployment Toolkit. In the Actions pane. configure the settings listed in Table 29 based on the requirements of your organization. On the Windows PE x86 Components tab. 3. 5.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 70 Setting Description Note This text box is enabled only if you select Generate a generic bootable ISO image. In the Deployment Workbench console tree. click Properties. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure).com/technet/SolutionAccelerators . 64. you can select a value of 32. click deployment_share (where deployment_share is the name of the deployment share). The default value for the text box is empty. Extra directories to add Scratch space size The deployment share configuration settings are saved. Click Start. 2. The default value for this text box is %INSTALLDIR%\Samples\Background. To configure the Windows PE x86 Components tab 1. and then click OK. and then point to All Programs. 256.

Optional Fonts Select to configure the Update Deployment Share Wizard to include the following fonts: • Chinese (ZH-CN) • Chinese (ZH-HK) • Chinese (ZH-TW) • Japanese (JA-JP) • Korean (KO-KR) Add these fonts when performing an LTI deployment of Windows Server 2008 images and the Setup files are Japanese. the Update Deployment Share Wizard includes the font in the Windows PE images. Add fonts only if necessary. the Update Deployment Share Wizard will not include the font in the Windows PE images. or Chinese. Select to configure the Update Deployment Share Wizard to include all the device drivers in the selection profile specified in the Selection profile box. • Cleared. If the check box is: • Selected. Note Adding fonts to Windows PE boot images increases the size of the images. Selection profile Use to select the device drivers and packages to be included in the Windows PE images based on the selection profile you choose. such as the MDT DB. Korean.com/technet/SolutionAccelerators Include all drivers from the selected driver group Include only drivers of the following types Solution Accelerators . Select to configure the Update Deployment Share Wizard to include only the device drivers in the chosen selection profile that are specified in the following check boxes: microsoft. If the check box for a corresponding font is: • Selected. • Cleared. the ADO components are added to the Windows PE images. These components are necessary for accessing Microsoft SQL Server® databases.71 Microsoft Deployment Toolkit 2010 Update 1 Setting Description Windows PE images. For more information about selection profiles. the ADO components are not added to the Windows PE images. The default value is All Drivers and Packages. see Manage Selection Profiles.

• Cleared. the Update Deployment Share Wizard will not include all video drivers in the selection profile specified in the Selection profile list box in the Windows PE images. Note This check box is enabled only if you select Include only drivers of the following types. Note This check box is enabled only if you select Include only drivers of the following types. • Cleared. the Update Deployment Share Wizard microsoft.com/technet/SolutionAccelerators Solution Accelerators . If the check box is: • Selected. the Update Deployment Share Wizard includes all video drivers in the selection profile specified in the Selection profile box in the Windows PE images. Include all video drivers in the selected group Select to configure the Update Deployment Share Wizard to include all video drivers in the chosen selection profile. the Update Deployment Share Wizard includes all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images. the Update Deployment Share Wizard will not include all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared. Include all mass storage drivers in the selected group Select to configure the Update Deployment Share Wizard to include all mass storage drivers in chosen the selection profile. the Update Deployment Share Wizard includes all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. If the check box is: • Selected. If the check box is: • Selected.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 72 Setting Description • Include all network drivers in the selected group • Include all video drivers in the selected group • Include all mass storage drivers in the selected group • Include all system-class drivers in the selected group Include all network drivers in the selected group Select to configure the Update Deployment Share Wizard to include all network drivers in the chosen selection profile.

and then click Deployment Workbench. and then click OK. configure the settings listed in Table 30 based on the requirements of your organization. • Cleared. 3. the Update Deployment Share Wizard will not include all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images. Point to Microsoft Deployment Toolkit. and then point to All Programs. click deployment_share (where deployment_share is the name of the deployment share).73 Microsoft Deployment Toolkit 2010 Update 1 Setting Description will not include all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images. Configure the Deployment Share Properties Windows PE x64 Settings Tab The deployment share properties stored on the Windows PE x64 Settings tab are mostly configured when you run the New Deployment Share Wizard. 2. In the Actions pane. On the Windows PE x64 Settings tab. The deployment share configuration settings are saved. 5. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). and the deployment share appears in the details pane of the Deployment Workbench. Note This check box is enabled only if you select Include only drivers of the following types. To configure the Windows PE x64 Settings tab 1. In the details pane. In the Deployment Workbench console tree. the Update Deployment Share Wizard includes all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images. 4. If the check box is: • Selected. Note This check box is enabled only if you select Include only drivers of the following types. Solution Accelerators microsoft. Click Start. click Properties. Include all systemclass drivers in the selected group Select to configure the Update Deployment Share Wizard to include all system-class drivers in the chosen selection profile. go to Deployment Workbench/Deployment Shares.com/technet/SolutionAccelerators .

• Cleared. Select to configure the Update Deployment Share Wizard to create a bootable Windows PE ISO file that includes the LTI deployment scripts.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 74 Table 30. If the check box is: • Selected. the Update Deployment Share Wizard creates the GenericPE_x64. Configuration Settings on the Windows PE x64 Settings Tab of Deployment Share Properties Setting Generate a Lite Touch Windows PE WIM file Description Select to configure the Update Deployment Share Wizard to create a Windows PE WIM file that includes the LTI deployment scripts. Contains the file name for the Windows PE ISO file that the Update Deployment Share Wizard creates. the Update Deployment Share Wizard will not create the ISO file. • Cleared.wim file with the image description specified in the Image description box. Note This box is enabled only if you select Generate a Lite Touch bootable ISO image. Image description Solution Accelerators Contains the image description for the generic microsoft. If the check box is: • Selected. the Update Deployment Share Wizard creates the LiteTouchPE_x86. Contains the image description for the Windows PE WIM file that the Update Deployment Share Wizard creates. the Update Deployment Share Wizard will not create the WIM file. the Update Deployment Share Wizard creates the ISO file with the name specified in the ISO file name box. the Update Deployment Share Wizard will not create the WIM file.wim file with the image description specified in the Image description box. • Cleared.com/technet/SolutionAccelerators . If the check box is: • Selected.iso. The default value is Lite Touch Windows PE (x64). Image description Generate a Lite Touch bootable ISO image ISO file name Generate a generic Select to configure the Update Deployment Share Windows PE WIM file Wizard to create a Windows PE WIM file that does not include the LTI deployment scripts. The default value for this text box is LiteTouchPE_x64.

bmp. The default value for this text box is Generic Windows PE (x64).com/technet/SolutionAccelerators . The default value for this text box is Generic_x64. 64. Custom background bitmap file Contains the fully qualified path to the BMP file that is to be used as the custom background bitmap. and the deployment share appears in the details pane of the Deployment Workbench.iso file with the image description specified in the ISO file name box. or 512 MB.75 Microsoft Deployment Toolkit 2010 Update 1 Setting Description Windows PE WIM file that the Update Deployment Share Wizard creates. 128. The default value is 32. The default value for the text box is empty. Configure the Deployment Share Properties Windows PE x64 Components Tab The deployment share properties stored on the Windows PE x64 Components tab are mostly configured when you run the New Deployment Share Wizard. Note This box is enabled only if you select Generate a generic Windows PE WIM file. If the check box is: • Selected. The default value for this text box is %INSTALLDIR%\Samples\Background. the Update Deployment Share Wizard will not create the ISO file.iso. Extra directories to add Scratch space size The deployment share configuration settings are saved. the Update Deployment Share Wizard creates the Generic_x64. Configures the size of the scratch space in megabytes. Note This box is enabled only if you select Generate a generic bootable ISO Windows PE WIM file. Contains the fully qualified path to a folder structure to be included in the Windows PE images. Note This text box is enabled only if the Generate a generic bootable ISO image check box is selected. Generate a generic bootable ISO image Select to configure the Update Deployment Share Wizard to create a bootable Windows PE ISO file that does not include the LTI deployments scripts. ISO file name Contains the file name for the generic Windows PE ISO file that the Update Deployment Share Wizard creates. 256. • Cleared. Solution Accelerators microsoft. you can select a value of 32.

go to Deployment Workbench/Deployment Shares. and then click Deployment Workbench. and then point to All Programs. Click Start. On the Windows PE x86 Components tab. the Update Deployment Share Wizard microsoft. the ADO components are not added to the Windows PE images. configure the settings listed in Table 31 based on the requirements of your organization. Korean. 2. In the Deployment Workbench console tree. Use to configure the Update Deployment Share Wizard to include the following fonts: • Chinese (ZH-CN) • Chinese (ZH-HK) • Chinese (ZH-TW) • Japanese (JA-JP) • Korean (KO-KR) Add these fonts when performing an LTI deployment of Windows Server 2008 images when the Setup files are Japanese. • Cleared. click deployment_share (where deployment_share is the name of the deployment share). The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). or Chinese. 4. such as the MDT DB.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 76 To configure the Windows PE x64 Components tab 1. Configuration Settings on the Windows PE x64 Components Tab of Deployment Share Properties Setting ADO Description Select to add the optional ADO components to the Windows PE images. Table 31. Point to Microsoft Deployment Toolkit. • Cleared. If the check box for a corresponding font is: • Selected. 5. These components are necessary for accessing SQL Server databases. 3. and then click OK. click Properties. If this check box is: • Selected. the ADO components are added to the Windows PE images. In the details pane. the Update Deployment Share Wizard includes the font in the Windows PE images. In the Actions pane.com/technet/SolutionAccelerators Optional Fonts Solution Accelerators .

see Manage Selection Profiles.com/technet/SolutionAccelerators . the Update Deployment Share Wizard includes all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. For more information about selection profiles. Include all drivers from the selected driver group Include only drivers of the following types Include all network drivers in the selected group Include all video drivers in the selected group Solution Accelerators Select to configure the Update Deployment Share Wizard to include all video drivers in the chosen selection profile. Select to configure the Update Deployment Share Wizard to include only the device drivers in the chosen selection profile that are specified in the following check boxes: • Include all network drivers in the selected group • Include all video drivers in the selected group • Include all mass storage drivers in the selected group • Include all system-class drivers in the selected group Select to configure the Update Deployment Share Wizard to include all network drivers in the chosen selection profile. If the check box is: • Selected. • Cleared. Select to configure the Update Deployment Share Wizard to include all the device drivers in the selection profile specified in the Selection profile box. Note This check box is enabled only if you select Include only drivers of the following types. The default value is All Drivers and Packages. If the check box is: microsoft.77 Microsoft Deployment Toolkit 2010 Update 1 Setting Description will not include the font in the Windows PE images. the Update Deployment Share Wizard will not include all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. Note Adding fonts to Windows PE boot images increases the size of the images. Selection profile Selects the device drivers and packages to be included in the Windows PE images based on the selection profile you choose. Add fonts only if necessary.

Note This check box is enabled only if you select include only drivers of the following types. If the check box is: • Selected. Note This check box is enabled only if you select include only drivers of the following types. the Update Deployment Share Wizard includes all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images.com/technet/SolutionAccelerators . Note This check box is enabled only if you select Include only drivers of the following types. the Update Deployment Share Wizard includes all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images. Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 78 Setting Description • Selected. the Update Deployment Share Wizard will not include all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images. and the deployment share appears in the details pane of the Deployment Workbench. • Cleared. • Cleared. The deployment share configuration settings are saved. Include all mass storage drivers in the selected group Select to configure the Update Deployment Share Wizard to include all mass storage drivers in the chosen selection profile. the Update Deployment Share Wizard will not include all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images. Include all systemclass drivers in the selected group Select to configure the Update Deployment Share Wizard to include all system-class drivers in chosen the selection profile. the Update Deployment Share Wizard will not include all video drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared. If the check box is: • Selected. the Update Deployment Share Wizard includes all video drivers in the selection profile specified in the Selection profile box in the Windows PE images.

After you copy the deployment share. Accept the default values unless otherwise specified. 2. see Open an Existing Deployment Share in Deployment Workbench. Start the Close Deployment Share action by performing one of the following tasks: • • • Right-click the deployment share. ensure that you share the folder with the appropriate permissions. and then. For more information about opening deployment shares. 4. Point to Microsoft Deployment Toolkit. and then click Close Deployment Share.79 Microsoft Deployment Toolkit 2010 Update 1 Copy a Deployment Share Deployment shares are local or network shared folders.com/technet/SolutionAccelerators . Information for Completing the Update Deployment Share Wizard Solution Accelerators microsoft. from the Action menu. Close existing deployment shares in the Deployment Workbench using the Close Deployment Share action. and then in the Actions pane. and then click Deployment Workbench. Complete the Update Deployment Share Wizard using the information in Table 32. open it in the Deployment Workbench. and then point to All Programs. Close a Deployment Share in Deployment Workbench Note Closing a deployment share does not remove the local or network shared folder or delete the contents of the local or network shared folder: It only removes the deployment share from the list of deployment shares in the Deployment Shares node in the Deployment Workbench. In the Deployment Workbench console tree. In the details pane. Click Start. When copying a deployment share to another computer. Update a Deployment Share in Deployment Workbench Updating a deployment share creates the Windows PE boot images (WIM and ISO files) necessary to start LTI deployment. click Close Deployment Share. click Update Deployment Share (where deployment_share is the name of the deployment share you want to update). Table 32. 3. such as in Windows Explorer. click deployment_share. Click the deployment share. click Close Deployment Share. and then. You can make a copy of a deployment share using any file-copy process. To update a deployment share in the Deployment Workbench 1. go to Deployment Workbench/Deployment Shares. The Update Deployment Share Wizard starts. Click the deployment share. in the Actions pane.

You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Select one of the following options based on your requirements: • Optimize the boot image updating process. this process takes less time than the Completely regenerate the boot images option. it may also increase the time required to generate the images. and then click Next. • Completely regenerate the boot images. the Optimize the boot image updating process option is selected and the Compress the boot image contents to recover space used by removed or modified content check box is cleared. Click Next. This process can take longer than the Optimize the boot image updating process option. Review the information in the Details box. Select this option when you want to force the creation of new images. You can optionally select the Compress the boot image contents to recover space used by removed or modified content check box to reduce the size of the boot images. and packages) can increase the size of the Windows PE image. This option configures the Update Deployment Share Wizard to create a new version of all the image files.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 80 On this wizard page Options Do this 1. However. components. Selecting this option reduces the image size to the minimum for the current content. Select this option when you want to reduce the amount of time required to update the boot images. Typically. 2.com/technet/SolutionAccelerators Summary Confirmation Solution Accelerators . the process of adding and removing content (such as drivers. By default. This option configures the Update Deployment Share Wizard to update existing versions of the image files. microsoft. Tip You can click Save Output to save the output of the wizard to a file. Over time.

com/technet/SolutionAccelerators Solution Accelerators .wim files (for 64-bit target computers) in the deployment_share\Boot folder (where deployment_share is the network shared folder used as the deployment share) based on the configuration settings on the Windows PE x86 Settings and Windows PE x64 Settings tabs. Note The target computer must support booting from the device to use this method of starting target computers. Note Optionally. Copy the contents of LiteTouchPE_x86. Create Bootable Devices from MDT 2010 Boot Images Starting destination computers using a bootable device (such as a UFD or a USB hard disk) is often quicker and easier than starting computers using Windows Deployment Services or CDs.exe.wim files (for 32-bit target computers) or LiteTouchPE_x64.iso and LiteTouchPE_x64. To create a bootable UFD 1.iso (for 64-bit target computers) to the device by performing one of the following tasks: • Burn the ISO file to a CD. On a computer running Windows Vista or a later operating system. create a bootable device. Run Diskpart. where N is the disk number identified in the previous step: • • • • • • • select disk N clean create partition primary select partition 1 active format fs=fat32 assign • exit 4. such as a UFD or USB hard disk. from the ISO file so that you can start the target computer from the device as described in Create Bootable Devices from MDT 2010 Boot Images. and type the command list disk to determine the disk number associated with the device. Input the following commands. insert the UFD or USB hard disk.iso (for 32-bit target computers) or LiteTouchPE_x64. 2. and then copy its contents to the device using the command: microsoft. 3. The Deployment Workbench starts updating the deployment share and creates the LiteTouchPE_x86.iso and LiteTouchPE_x86.81 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this Click Close.

Copying an operating system as described in Copy an Operating System in the Deployment Workbench. • Alternatively. Table 33. Configure the operating systems in the Deployment Workbench by: • • • • • • • Importing an operating system as described in Import an Operating System into the Deployment Workbench. Import an Operating System into Deployment Workbench You can import operating systems into the Deployment Workbench using the options listed in Table 33. Configuring Operating Systems in Deployment Workbench MDT 2010 uses the Deployment Workbench to manage the operating systems that you can deploy to the reference and target computers in your organization. Viewing an operating system’s properties as described in View Operating System Properties in the Deployment Workbench. Options for Importing Operating Systems into the Deployment Workbench Option Full set of source files Custom image file Solution Accelerators Select this option to import an operating system from Windows distribution media. such as a DVD.* <e>:\*. Deleting an operating system as described in Delete an Operating System from the Deployment Workbench.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 82 xcopy <d>:\*. A WIM image that was previously captured for microsoft. mount the ISO file using a virtual CD program. Managing folders for operating systems as described in Manage Folders for Operating Systems in the Deployment Workbench. or equivalent media source. CD.* /s /e /f where d is the driver letter of the CD and e is the drive letter of the device.com/technet/SolutionAccelerators . Moving an operating system as described in Move an Operating System in the Deployment Workbench.* <e>:\*. Renaming an operating system as described in Rename an Operating System in the Deployment Workbench. You manage this import in the Import Operating System Wizard in the Deployment Workbench.* /s /e /f where d is the driver letter of the CD and e is the drive letter of the device. and then copy its contents to the device using the command: xcopy <d>:\*.

Then. which includes product DVDs. in the Actions pane. Existing WIM images in Windows Deployment Services as described in Import an Operating System from an Existing Windows Deployment Services Image. 2. Start the Import Operating System Wizard using one of the following methods: • In the Deployment Workbench console tree. In the Deployment Workbench console tree. click Import Operating System. import Windows XP and Windows Server 2003 operating systems from slipstreamed sources. click Import Operating System.com/technet/SolutionAccelerators . go to Deployment Workbench/Deployment Shares/deployment_share/Operating Systems Solution Accelerators microsoft. In the Deployment Workbench console tree. CDs. WIM images previously captured from reference computers as described in Import a Previously Captured Image of a Reference Computer. click Import Operating System. Windows Deployment Services images Note Always import operating systems from operating system sources that have the most recent updates. Windows distribution media as described in Import an Operating System from Windows Distribution Media. Point to Microsoft Deployment Toolkit. and Windows Server 2008 operating systems from updated media obtained from Microsoft. and then point to All Programs. Click Start. or folders containing the distribution files. Windows Server 2008 R2. Doing so helps reduces the management effort and network traffic when applying the updates after the target operating system has been deployed. Then. click the Operating System node or a folder beneath the Operating System node. Images that exist on computers running Windows Deployment Services. To import an operating system from Windows distribution media 1. In the Deployment Workbench console tree. and then click Deployment Workbench. click the Operating System node or a folder beneath the Operating System node. or import Windows 7. typically from a reference computer. from the Action menu.83 Microsoft Deployment Toolkit 2010 Update 1 Option Select this option to import an operating system from deployment. Then. Windows Vista. Import the operating system using the Import Operating System Wizard in the Deployment Workbench. click the Operating System node or a folder beneath the Operating System node. • • You can also import operating systems into Deployment Workbench from: • • • Import an Operating System from Windows Distribution Media MDT 2010 allows you to import operating systems into the Deployment Workbench from Windows distribution media. For example.

Note Alternatively. To import an operating system from a previously captured image of a reference computer 1. In the Actions pane. Import a Previously Captured Image of a Reference Computer MDT 2010 allows you to import previously captured images of reference computers or other custom images into the Deployment Workbench. and then click Next. Summary Confirmation Click Finish.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 84 (where deployment_share is the name of the deployment share to which the operating system will be added). and then click Next. and then point to All Programs. The Import Operating System Wizard finishes. type source_folder (where source_folder is the fully qualified path to the folder containing the operating system source files). Destination In Destination directory name. 3. Import the operating system using the Import Operating System Wizard in the Deployment Workbench. The operating system is added to the list of operating systems in the details pane of the Deployment Workbench. Information for Completing the Import Operating System Wizard On this wizard page OS Type Source Do this Click Full set of source files. 4. In Source directory. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Table 34. Click Start. type destination_folder (where destination_folder is the name of the folder in the deployment share that will contain the operating system source files). and then click Next. The Import Operating System Wizard starts. and then click Deployment Workbench. Point to Microsoft Deployment Toolkit. Tip Click Save Output to save the output of the wizard to a file. Click Next.com/technet/SolutionAccelerators . click Import Operating System. click Browse to find the source folder. Solution Accelerators microsoft. Complete the Import Operating System Wizard using the information in Table 34.

The Import Operating System Wizard starts. and then click Next. • Copy Windows Vista or Windows Server 2008 setup files from the specified path. Table 35. Setup Select one of the following options based on your requirements. Select this option to copy the Setup files from a folder containing the Windows Vista or Windows Server 2008 Setup files when those files are not available in another operating system in the Deployment Workbench.com/technet/SolutionAccelerators . In the Deployment Workbench console tree. • Copy Windows XP or Windows Server 2003 Sysprep files from the specified path. 3. In Sysprep directory. Select this option to copy the Sysprep files from a folder containing the Windows XP or Windows Server 2003 Sysprep or DEPLOY. Complete the Import Operating System Wizard using the information in Table 35.85 Microsoft Deployment Toolkit 2010 Update 1 2. Select this option when no Setup files for a Windows Vista or Windows Server 2008 image or Sysprep files for a Windows XP or Windows Server 2003 image will be copied. In Setup source directory. 4.CAB files required to install the image specified. type or click Browse to find the folder containing the Setup files. Note Alternatively. click Import Operating System. and then click Next: • Setup and Sysprep files are not needed. type source_file (where source_file is the fully qualified path to the WIM image file containing the operating system source files). In the Actions pane. go to Deployment Workbench/Deployment Shares/deployment_share/Operating Systems (where deployment_share is the name of the deployment share to which the operating system will be added). Information for Completing the Import Operating System Wizard On this wizard page OS Type Source Do this Click Custom image file. and then click Next. Click Browse to find the folder containing the Sysprep files. click Browse to find the source WIM image. In Source file. Solution Accelerators microsoft.

To resolve this issue. In the Deployment Workbench console tree.wim. and then click Deployment Workbench. 2. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.com/technet/SolutionAccelerators . Tip Click Save Output to save the output of the wizard to a file. rc = 31 ZTI ERROR – Non-zero return code by LTIApply. and then click Next. wim_file is the name of the WIM file. Import the operating system using the Import Operating System Wizard in the Deployment Workbench. go to Deployment Workbench/Deployment Shares/deployment_share/Operating Systems Solution Accelerators microsoft. the wizard fails with an error similar to the following: Setup failed applying image F:\Deploy\Operating Systems\W2K8R2RTM\W2K8R2RTM. If you attempt to import a custom image that does not have an Edition ID. and then point to All Programs. rc = 31. add an Edition ID to the image by running the following command (where edition_id is the appropriate SKU ID as defined in the original factory image or in the Windows AIK. To import an operating system from an existing image in Windows Deployment Services 1. Point to Microsoft Deployment Toolkit. type destination_folder (where destination_folder is the name of the folder in the deployment share that will contain the operating system source files). The Import Operating System Wizard finishes.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 86 On this wizard page Do this Note The default option is Setup and Sysprep files are not needed. Destination In Destination directory name. and new_image_description is the new description for the image): imagex /flags <edition_id> /info <wim_file> 1 <new_image_name> <new_image_description> Import an Operating System from an Existing Windows Deployment Services Image MDT 2010 allows you to import existing WIM images in Windows Deployment Services into the Deployment Workbench. Click Next. Click Start. The operating system is added to the list of operating systems in the details pane of the Deployment Workbench. new_image_name is the new image name. Summary Confirmation Click Finish.

In the Actions pane. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. click Import Operating System. Tip Click Save Output to save the output of the wizard to a file. type server_name (where server_name is the name of the Windows Deployment Services server that contains the existing WIM images). The operating system is added to the list of operating systems in the details pane but is not is copied to the deployment share. Table 37 lists the configuration settings on the General tab of the operating system Properties dialog box and provides a description of each setting. and only the Operating system name can be modified. Windows 7 ENTERPRISE in microsoft. Table 36. but the image is now available to LTI.87 Microsoft Deployment Toolkit 2010 Update 1 (where deployment_share is the name of the deployment share to which the operating system will be added). The Deployment Workbench leaves the operating system image on the Windows Deployment Services server. and then click Next. Note The configuration settings on the General tab are populated when you import the operating system. The Import Operating System Wizard starts. and then click Next. The Import Operating System Wizard finishes.com/technet/SolutionAccelerators Solution Accelerators . Click Next. In Server name. Table 37. Information for Completing the Import Operating System Wizard On this wizard page OS Type WDS Server Do this Click Custom image file. Configuration Settings on the General Tab of the Operating System Properties Dialog Box Setting Operating system name Description Contains the name of the operating system—for example. No other settings can be modified. 3. View Operating System Properties in Deployment Workbench You view operating system properties beneath the Operating System node in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. 4. Complete the Import Operating System Wizard using the information in Table 36. Summary Confirmation Click Finish.

7921 indicates 7. Windows 7 ENTERPRISE. Solution Accelerators microsoft. Contains True or False. Contains the HAL type for the image—for example. Contains the size of the image in megabytes—for example. Path Image file Image index Image name Image size (MB) HAL Copy an Operating System in Deployment Workbench Copy and paste operating systems and folders beneath the Operating System node in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench.921 MB. or 7. Includes the image name—for example. Contains the languages included in the operating system—for example. Windows IBS. Contains the type of operating system—for example. Contains the path to the operating system relative to the root of the deployment share.wim. Contains the processor architecture of the operating system—for example. which indicates whether the operating system includes the files necessary to perform setup.com/technet/SolutionAccelerators . Contains the path and file name of the operating system relative to the root of the deployment share. acpiapic. Contains a numeric value that indicates the image index for the image—for example. x86. en-us. 1. Contains the description of the operating system —for example. Windows 7 ENTERPRISE.921 GB. Move an Operating System in Deployment Workbench Move operating systems and folders beneath the Operating System node in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 88 Setting Description OS type Platform Languages(s) Includes Setup Description Windows_7_x86_Build_7100 install.

Manage Folders for Operating Systems in Deployment Workbench You can manage folders beneath the Operating Systems node in the Deployment Workbench to create hierarchical groupings of operating systems. Solution Accelerators microsoft. Configure the applications in the Deployment Workbench by: • • • • • • • • Creating a new application as described in Create a New Application in Deployment Workbench. Viewing and configuring an application as described in View and Configure an Application in Deployment Workbench. see Manage Selection Profiles. Managing folders for applications as described in Manage Folders for Applications in Deployment Workbench. Deleting an application as described in Delete an Application from Deployment Workbench.com/technet/SolutionAccelerators . Delete an Operating System from Deployment Workbench Delete operating systems and folders beneath the Operating System node in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. The Delete Selected Items Wizard allows deletion of individual operating system files or entire folder structures.89 Microsoft Deployment Toolkit 2010 Update 1 Rename an Operating System in Deployment Workbench Rename operating systems and folders beneath the Operating System node in the Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench. Moving an application as described in Move an Application in Deployment Workbench. Configuring Applications in Deployment Workbench MDT 2010 uses the Deployment Workbench to manage the applications deployed to the reference and target computers in your organization. Copying an application as described in Copy an Application in Deployment Workbench. For more information on: • • Managing folders. see Manage Folders in Deployment Workbench. Renaming an application as described in Rename an Application in Deployment Workbench. Enabling or disabling an application as described in Enable or Disable an Application in Deployment Workbench. Selection profiles.

Options for Creating a New Application Option Application with source files Select this option to create an application when The application source files are not available to the destination computer when installing the operating system build or when they must be customized. but the bundle itself does not install anything. Configuring the computer to restart as described in Configure the Computer to Restart After Application Installation. When you select this option. Then. the application files are copied to the deployment share. In the Deployment Workbench console tree. • • You can create a new application in the Deployment Workbench for: Solution Accelerators microsoft. Application without source files or elsewhere on the network Application bundle Start the New Application Wizard using one of the following methods: • In the Deployment Workbench console tree. click New Application. no application source files are copied to the deployment share. the deployment process installs the application from another location on the network. in the Actions pane. A list of applications that you must install in a particular order. click the Applications node or a folder beneath the Applications node. When you select this option. The application source files are available during installation of the operating system build or to run a command that requires no application source files.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 90 • • • Preventing an application from being visible as described in Prevent an Application from Being Visible in the Windows Deployment Wizard. Table 38. Then. click New Application. click the Applications node or a folder beneath the Applications node. You import operating systems into the Deployment Workbench using the New Application Wizard. and the deployment process installs the application from the deployment share. Instead. Create a New Application in Deployment Workbench You can create new applications in the Deployment Workbench using one of the options listed in Table 38. from the Action menu. In the Deployment Workbench console tree. This list is specified as dependencies for the application bundle. click New Application. click the Applications node or a folder beneath the Applications node. Customizing application installation as described in Customize Application Installation in Task Sequences.com/technet/SolutionAccelerators . Then.

Click Next. • Create a New Application That Is Deployed from the Deployment Share MDT 2010 allows you to use the New Application Wizard in the Deployment Workbench to create new applications that are deployed from the deployment share. go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which the application will be added). To create a new application that is deployed from the deployment share 1. Click Start. 4. In Language. 1. Applications to be deployed from another network shared folder as described in Create a New Application That Is Deployed from Another Network Shared Folder. Point to Microsoft Deployment Toolkit. 2. and then click Deployment Workbench. In Application Name. type language (where language is the language of the application). The New Application Wizard starts. Information for Completing the New Application Wizard On this wizard page Application Type Details Do this Click Application with source files. 2.91 Microsoft Deployment Toolkit 2010 Update 1 • • Applications to be deployed from the deployment share as described in Create a New Application That Is Deployed from the Deployment Share. 5. In the Actions pane. 4. and then point to All Programs. 3. Table 39. In the Deployment Workbench console tree. microsoft. Deploying application dependencies as described in Create a New Application for Deploying Application Dependencies. The New Application Wizard copies source files for this type of applications to the deployment share. type version (where version is the version of the application). and then click Next. In Version. click New Application. type application_name (where application_name is the descriptive name of the application).com/technet/SolutionAccelerators Solution Accelerators . In Publisher. 3. type publisher_name (where publisher_name is the name of the application’s publisher). Complete the New Application Wizard using the information in Table 39.

type destination_folder (where destination_folder is the name of the folder in the deployment share that will contain the application source files). In Command line. the wizard moves the source files to the deployment share. Select or clear the Move the files to the deployment share instead of copying them check box based on your requirements. Solution Accelerators microsoft. and then click Next. 2. 2. Click Next. In Working directory. If the check box is: • Selected. this check box is cleared. Note By default. 3. The application is added to the list of operating systems in the details pane in the Deployment Workbench. Destination In Specify the name of the directory that should be created. In Source directory. type command_line (where command_line is the command line to be run to start the installation of the application. Note Alternatively. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 92 On this wizard page Source Do this 1. The New Application Wizard finishes. Command Details Summary Confirmation Click Finish. Tip Click Save Output to save the output of the wizard to a file. 1. click Browse to find the source folder. type working_directory (where working_directory is the fully qualified or relative path for the folder designated as the working directory for the application). This check box determines whether the wizard copies or moves the application source files to the deployment share. including any command-line parameters). Click Next. the wizard copies the source files to the deployment share. and then click Next.com/technet/SolutionAccelerators . • Cleared. type source_folder (where source_folder is the fully qualified path to the folder containing the application source files).

In Version. click New Application. 1. microsoft. 3. type application_name (where application_name is the descriptive name of the application). Click Start. Click Next. In Command line. In Application Name. The New Application Wizard starts. type publisher_name (where publisher_name is the name of the application’s publisher).93 Microsoft Deployment Toolkit 2010 Update 1 Create a New Application That Is Deployed from Another Network Shared Folder MDT 2010 allows for the creation of new applications that you deploy from a network shared folder other than the deployment share. type command_line (where command_line is the command line to be run to start the installation of the application. 2. 2. In Working directory. Point to Microsoft Deployment Toolkit. In Publisher. and then point to All Programs. type version (where version is the version of the application). 4. go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which the application will be added). 1. In the Deployment Workbench console tree. 4. To create a new application that is deployed from a network shared folder other than the deployment share 1. Create a new application using the New Application Wizard in the Deployment Workbench. In Language.com/technet/SolutionAccelerators Command Details Solution Accelerators . 2. 5. The New Application Wizard does not copy the source files for this type of application. 3. including any command-line parameters). In the Actions pane. Complete the New Application Wizard using the information in Table 40. Information for Completing the New Application Wizard On this wizard page Application Type Details Do this Click Application without source files or elsewhere on the network. type working_directory (where working_directory is the fully qualified or relative path for the folder designated as the working directory for the application). type language (where language is the language of the application). Table 40. and then click Next. and then click Deployment Workbench.

Complete the New Application Wizard by using the information in Table 41. The New Application Wizard finishes. In the Actions pane. The New Application Wizard does not copy source files to the deployment share.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 94 On this wizard page Summary Confirmation Do this 3. 1. 3. Information for Completing the New Application Wizard On this wizard page Application Type Details Do this Click Application bundle. 4.com/technet/SolutionAccelerators Solution Accelerators . go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which the application will be added). 4. Tip Click Save Output to save the output of the wizard to a file. In the Deployment Workbench console tree. Create a New Application for Deploying Application Dependencies MDT 2010 allows for the creation of new applications used to deploy only the dependencies for an application instead of installing the application itself. type application_name (where application_name is the descriptive name of the application). Create a new application using the New Application Wizard in the Deployment Workbench. click New Application. In Language. and then click Next. 2. Click Finish. In Application Name. type version (where version is the version of the application). Table 41. and then point to All Programs. Point to Microsoft Deployment Toolkit. In Publisher. Click Next. To create a new application for deploying application dependencies 1. The application is added to the list of operating systems in the details pane of the Deployment Workbench. 3. The New Application Wizard starts. Click Start. Click Next. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. type publisher_name (where publisher_name is the name of the application’s publisher). 2. type language (where language microsoft. In Version. and then click Deployment Workbench.

Summary Confirmation Click Next. Click Start. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Configure properties on the Dependencies tab as described in Configure the Application Properties on the Dependencies Tab. Tip Click Save Output to save the output of the wizard to a file. 2. The application is added to the list of operating systems in the details pane of the Deployment Workbench. and then point to All Programs. In the Deployment Workbench console tree. Click Next. Configure the Application Properties General Tab The application properties stored on the General tab are mostly configured when the New Application Wizard runs. Click Finish.com/technet/SolutionAccelerators . go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which the application will be added). Configure an application in the Deployment Workbench by performing the following steps in the Application Properties dialog box: • • • • Configure properties on the General tab as described in Configure the Application Properties on the General Tab. Configure the properties on the Office Products tab as described in Configure the Application Properties on the Office Products Tab. Update the application properties on the General tab through the application_name Properties dialog box (where application_name is the name of the application in the Deployment Workbench). and then click Deployment Workbench.95 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this is the language of the application). Configure properties on the Details tab as described in Configure the Application Properties on the Details Tab. Solution Accelerators microsoft. To configure the General tab for application properties 1. 5. View and Configure an Application in Deployment Workbench View the properties of applications beneath the Applications node in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. Point to Microsoft Deployment Toolkit. The New Application Wizard finishes.

Contains the version number of the application. The application_name Properties dialog box opens (where application_name is the name of the application to configure). If the check box is: • Selected. Language Contains the language of the application. Provides information about the application. Note Enter the language in this box. In the Actions pane. 5. Comments Display name Short name Version Publisher Contains the name of the application’s publisher. it is not validated against the actual application version number but is provided for informational purposes. click Properties. the value in Name is displayed in the Windows Deployment Wizard. Note Enter the publisher in this box. Note Enter the version number in this box. this value is also displayed in the Windows Deployment Wizard. On the General tab. configure the settings listed in Table 42 based on the requirements of your organization. (Optional) Contains the name displayed in the Windows Deployment Wizard instead of the value in Name.com/technet/SolutionAccelerators Solution Accelerators . click application_name (where application_name is the name of the application to configure). If no value is specified. it is not validated against the actual application language but is provided for informational purposes. Table 42.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 96 3. the Windows Deployment Wizard will microsoft. it is not validated against the actual application version number but is provided for informational purposes. In the details pane. 4. If Display name is not configured. Source directory Hide this application in the Deployment Wizard Configures the folder in which the source of the application files resides. Contains the name of the folder in which the application resides. and then click OK. Select to control when this application appears in the Windows Deployment Wizard. Configuration Settings on the General Tab of Application Properties Setting Name Description Contains the name of the application displayed in the Deployment Workbench.

5. The application configuration settings are saved. 3. Point to Microsoft Deployment Toolkit. Table 43. Click Start. other wizards and dialog boxes in the Deployment Workbench are able to select this application. Configure the Application Properties Details Tab The application configuration settings stored on the Details tab are initially configured when the New Application Wizard runs. configure the settings listed in Table 43 based on the requirements of your organization. click Properties. Enable this application Select to control when this application is available to other wizards and dialog boxes in the Deployment Workbench. and then click Deployment Workbench. 2. If the check box is: • Selected. the Windows Deployment Wizard displays this application. and the modifications are displayed in the details pane of the Deployment Workbench. The application_name Properties dialog box opens (where application_name is the name of the application to configure). Configuration Settings on the Details Tab of Application Properties Solution Accelerators microsoft. In the Deployment Workbench console tree. • Cleared. Update the application properties on the Details tab through the application_name Properties dialog box (where application_name is the name of the application in the Deployment Workbench). other wizards and dialog boxes in the Deployment Workbench are unable to select this application. 4. click application_name (where application_name is the name of the application to configure). and then point to All Programs. go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which the application will be added). • Cleared. In the Actions pane. and then click OK. On the Details tab.97 Microsoft Deployment Toolkit 2010 Update 1 Setting Description not display this application. To configure the Details tab for application properties 1. In the details pane.com/technet/SolutionAccelerators .

or quiet. The other available option is This can run on any platform. The other available option is Standard application. This text box is enabled only when you select Standard application. the target computer restarts after installing the application. Quiet install command Working directory Uninstall registry key name Reboot the computer after installing this application This can run on any platform Select to configure the application to run on any supported 32-bit or 64-bit Windows operating system. If the check box is: • Selected. Solution Accelerators microsoft. Configures the working directory of the application and is enabled only when you select Standard application. Note This check box is cleared by default. and other options listed on this tab. the target computer will not restart after installing the application. This can run only on the specified client platforms The application configuration settings are saved.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 98 Setting Application bundle Standard application Description Select to configure the application to install application dependencies but not the application. Select to configure the MDT 2010 deployment process to restart the target computer after installing this application. installation of the application. Select to configure the application to run on any supported 32-bit or 64-bit Windows operating system. used to determine whether the application is already installed on the target computer.com/technet/SolutionAccelerators . and the modifications are displayed in the details pane of the Deployment Workbench. it assumes that the application is already installed and skips the installation of the application and any dependencies. • Cleared. a command line. Configures the registry subkey HKEY_LOCAL_MACHINE\Software\Microsoft\Wind ows\CurrentVersion\Uninstall. This text box is enabled only when you select the Standard application option. The other available option is This can run only on the specified client platforms. Select to configure the application to be a standard application that has source files. The other available option is Application bundle. Configures the command line to run for performing an unattended. If MDT 2010 detects the presence of the subkey.

Note Application dependencies are installed from the top of the list to the bottom.99 Microsoft Deployment Toolkit 2010 Update 1 Configure the Application Properties Dependencies Tab MDT 2010 checks the dependencies of an application before installing the application. Note Application dependencies are installed even if you do not select the dependencies separately from the application. To configure the Dependencies tab for application properties 1. Removes an application dependency from the list of dependencies. 3. When you define more than one application dependency. In the Actions pane. The application_name Properties dialog box opens (where application_name is the name of the application to configure). 5. application dependencies override any rules defined in CustomSettings. and then click OK. MDT 2010 ensures that all application dependencies are installed before installing the application. Also. you can configure the order in which the dependencies are installed. Point to Microsoft Deployment Toolkit. Remove Up Solution Accelerators microsoft. click Properties. Actions on the Dependencies Tab of Application Properties Action Add Description Adds a new application dependency to the list of dependencies. In the details pane. Click Start.com/technet/SolutionAccelerators . thereby ensuring that the dependencies are installed in a specific order. go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which you will add the application). 2. Update the application properties on the Dependencies tab through the application_name Properties dialog box (where application_name is the name of the application in the Deployment Workbench). In the Deployment Workbench console tree. 4. configure the settings by performing one of the actions in Table 44 based on the requirements of your organization. Table 44. You can add any applications that already exist in the deployment share. On the Dependencies tab.ini or in the MDT DB. click application_name (where application_name is the name of the application you are configuring). Moves an application dependency higher in the sequence of installed dependencies. Similarly. and then point to All Programs. and then click Deployment Workbench.

and the modifications are displayed in the details pane of the Deployment Workbench. Configure the Application Properties Office Products Tab The application properties stored on the Office Products tab are mostly configured when the New Application Wizard runs. 4. and then point to All Programs. 2. 3. Click Start. and then click Deployment Workbench. configure the settings listed in Table 45 based on the requirements of your organization. Update the application properties on the Office Products tab through the application_name Properties dialog box (where application_name is the name of the application in the Deployment Workbench).Using the Microsoft Deployment Toolkit: Managing LTI Deployments 100 Action Down Description Moves an application dependency lower in the sequence of installed dependencies. 2007 Office system Setup installs the same language as the target operating system. The application configuration settings are saved. On the Office Products tab. Solution Accelerators microsoft. and then click OK. click Properties. Note Application dependencies are installed from the top of the list to the bottom. Configuration Settings on the Office Products Tab of Application Properties Setting Office 2007 product to install Office 2007 languages Description Selects the 2007 Microsoft Office system products to be installed.com/technet/SolutionAccelerators . The application_name Properties dialog box opens (where application_name is the name of the application to configure). Table 45. In the Deployment Workbench console tree. In the Actions pane. Note By default. click application_name (where application_name is the name of the application to configure). In the details pane. 5. go to Deployment Workbench/Deployment Shares/deployment_share/Applications (where deployment_share is the name of the deployment share to which the application will be added). Use to select each language included in the source image. Use these check boxes to force the installation of specific language packs. To configure the Office Products tab for application properties 1. Point to Microsoft Deployment Toolkit.

the customer name is provided during 2007 Office system Setup or in an MSP configuration file. If the check box is: • Selected. • Cleared. the Config. the product key is provided during 2007 Office system Setup or in a Windows Installer (MSP) configuration file. select the display level in the associated box to automatically configure the Config.xml for 2007 Office system Setup to provide the customer name.xml file. If the check box is: • Selected. the display level is provided during 2007 Office system Setup or in an MSP configuration file. Select to determine whether the Deployment Workbench configures Config.xml for 2007 Office system Setup to automatically accept the End User License Agreement (EULA) during the setup process. • Cleared. • Cleared.xml file for 2007 Office system Setup to provide a product key.xml file.101 Microsoft Deployment Toolkit 2010 Update 1 Setting Product key Description Select to determine whether the Deployment Workbench configures the Config. If the check box is: • Selected. Select to determine whether the Deployment Workbench configures the Config. enter the customer name in the associated box to automatically configure the Config.com/technet/SolutionAccelerators Customer name Display level Accept EULA Cache only Solution Accelerators .xml file.xml for 2007 Office system Setup to configure the display level of the setup process. EULA acceptance is provided during 2007 Office system Setup or in an MSP configuration file. enter the product key in the associated box to automatically configure the Config. Select to determine whether the Deployment Workbench configures Config. Select to determine whether the Deployment Workbench configures Config. If the check box is: • Selected.xml file is configured to automatically accept the EULA. • Cleared.xml for 2007 Office system Setup to install the local installation source microsoft.

• Cleared. Solution Accelerators microsoft.xml for 2007 Office system Setup to prevent restarting the target computer during the setup process.xml file is configured to prevent a restart of the target computer during 2007 Office system Setup. the Config.xml file is configured to copy the LIS cache during 2007 Office system Setup but not install 2007 Office system products. Rename an Application in Deployment Workbench Rename applications and folders beneath the Applications node in the Deployment Workbench by using the Rename action as described in Rename Items in Deployment Workbench. • Cleared.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 102 Setting Description (LIS) cache to the target computer during the setup process but not install the 2007 Office system. and the modifications are displayed in the details pane of the Deployment Workbench. the target computer can be restarted during 2007 Office system Setup. Add Edit Config.com/technet/SolutionAccelerators . Click to modify the contents of the Config. If the check box is: • Selected. Copy an Application in Deployment Workbench Copy and paste applications and folders beneath the Applications node in the Deployment Workbench by using the Copy and Paste actions as described in Copy Items in Deployment Workbench. If the check box is: • Selected. Move an Application in Deployment Workbench Move applications and folders beneath the Applications node in the Deployment Workbench by using the Cut and Paste actions as described in Move Items in Deployment Workbench. the Config. Always suppress reboot Select to determine whether the Deployment Workbench configures Config. Click to add 2007 Office system language packs.xml file that the Deployment Workbench generates. the LIS cache is copied and 2007 Office system products are installed during 2007 Office system Setup.xml The application configuration settings are saved.

For more information on: • • Managing folders. Selection profiles. Configure the Computer to Restart After Application Installation Restart the target computer after installing an application by selecting the Restart the computer after installing this application check box on the Details tab of the application Properties dialog box. the Deployment Workbench does not enforce this recommendation. see Manage Folders in Deployment Workbench. Prevent an Application from Being Visible in the Windows Deployment Wizard Prevent an application from being visible in the Windows Deployment Wizard by selecting the Hide this application in the Deployment Wizard check box on the General tab of the application Properties dialog box. use the command REBOOT=REALLYSUPPRESS to prevent some Windows Installer–based applications from restarting. or the task sequence will fail. Doing so allows the application to be installed during the task sequence but prevents the application from appearing in the list of available applications.103 Microsoft Deployment Toolkit 2010 Update 1 Delete an Application from Deployment Workbench Delete applications and folders beneath the Applications node in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. add the property Solution Accelerators microsoft. However. For example. Note You should not delete an application when other applications are dependent on it. see Configure the Application Properties General Tab.com/technet/SolutionAccelerators . MDT 2010 must control restarts. To prevent the 2007 Office system from restarting the computer. disable the application. Tip To configure an application so that it can only be installed during a task sequence step. CAUTION Do not allow the application to restart the target computer. as described in Configure the Application Properties General Tab. Selecting this check box causes the Windows Deployment Wizard to restart the target computer after installing the application. Enable or Disable an Application in Deployment Workbench Control whether applications are available to other wizards and dialog boxes in the Deployment Workbench by using the Enable this application check box on the General tab of the application Properties dialog box. For more information on enabling or disabling applications in the Deployment Workbench. The Delete Selected Items Wizard allows deletion of individual applications or entire folder structures. see Manage Selection Profiles. and then continue with the next step in the task sequence. Manage Folders for Applications in Deployment Workbench You can manage folders beneath the Applications node in the Deployment Workbench to create hierarchical groupings of applications.

• Specify in the Applications property in CustomSettings. see the section. For more information on the: • Applications property.ini or the MDT DB.com/technet/SolutionAccelerators . Configuration Settings on the Properties Tab of the Install Application Task Sequence Setting Install multiple applications Description Select to install one or more applications in a single task sequence step. Toolkit Reference. The Install Application task sequence type allows for installation of one or more applications in a single task sequence step using one of the configuration options listed in Table 46. Table 46. Install single application Solution Accelerators Select to install one or more applications in a single task sequence step.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 104 SETUP_REBOOT=NEVER to the Config.” in the MDT 2010 document.xml file or the MST file created by using the Office Customization Tool. Some of task sequence templates included in MDT 2010 have the Install Applications task sequence step in the State Restore group. which is based on the Install Application task sequence type. see the section. “MandatoryApplications.” in the MDT 2010 document. Customize Application Installation in Task Sequences Adding applications in the Applications node in a deployment share through the Deployment Workbench is the simplest method of deploying most applications. This configuration option allows installation of any applications that you: • Select in the Windows Deployment Wizard. You use the Application to install box in microsoft. see Configure the Application Properties Details Tab. • MandatoryApplications property. Toolkit Reference. For more information on how to configure MDT 2010 to restart the target computer after installing an application. Note This configuration option is the default selection for the Install Applications task sequence step.ini or the MDT DB. MDT 2010 task sequences deploy applications by using the Install Application task sequence type. The default values in this box are 0 and 3010 for the task sequence step in the templates included in MDT 2010. You use the Success codes box in conjunction with this option to identify the application installation return codes that indicate a successful application deployment. • Specify in the MandatoryApplications property in CustomSettings. “Applications.

105

Microsoft Deployment Toolkit 2010 Update 1

Setting

Description conjunction with this option to select the application to install, including any application dependencies for the selected application.

Customize the application-deployment process in the task sequences by: • Configuring the existing Install Applications task sequence step in the State Restore group as described in Configure an Existing Install Applications Task Sequence Step. Creating a new task sequence step based on the Install Application task sequence type as described in Create a New Task Sequence Step for Installing Applications.

Configure an Existing Install Applications Task Sequence Step
Configure an existing Install Applications task sequence step by modifying the configuration settings on the Properties tab of the task sequence step. To configure an existing Install Applications task sequence step 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share to which the application will be added). 3. In the details pane, click task_sequence (where task_sequence is the name of the task sequence to configure). 4. In the Actions pane, click Properties. The task_sequence Properties dialog box opens (where task_sequence is the name of the application to configure). 5. In the task_sequence Properties dialog box (where task_sequence is the name of the application you want to configure), click the Task Sequence tab. 6. In the hierarchy of the task sequence, go to State Restore/Install Applications. 7. On the Properties tab, configure the settings listed in Table 47 based on the requirements of your organization, and then click OK. Table 47. Configuration Settings on the Properties Tab of the Install Applications Task Sequence Setting Name Description Configures the name of the task sequence step displayed in the task sequence hierarchy.
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

106

Setting Description Install multiple applications

Description Configures the description text for the task sequence step. Select to configure the task sequence step to install any applications that you: • Select in the Windows Deployment Wizard. • Specify in the Applications property in CustomSettings.ini or the MDT DB. • Specify in the MandatoryApplications property in CustomSettings.ini or the MDT DB. Configures the list of success codes for the applicationinstallation software. Each success code is separated by a space. This text box is only enabled when you select the Install multiple applications option. Configures the task sequence step to install only the application listed in the Application to install box. Configures the application to be installed when you select the Install a single application option. Select the application to install by clicking Browse. This text box is enabled only when you select Install a single application.

Success codes

Install a single application Application to install

The updated task sequence appears in the details pane of the Deployment Workbench.

Create a New Task Sequence Step for Installing Applications
In most instances, the existing Install Applications task sequence step is sufficient for installing applications to target computers. However, there are instances in which the existing Install Applications task sequence step may not be sufficient for your organization’s requirements, or you may need to install an application at a different sequence in the task sequence. For example, the installation process for some device drivers is performed more like an application installation than the typical installation process for a traditional device driver. You can install these device drivers by creating a new task sequence step based on the Install Application task sequence type.
Tip Disable the existing Install Applications step in the task sequence, and add all applications manually using the task sequence controls. The benefits of this approach are that you can easily select and insert applications into the task sequence in any order necessary, simplifying management of a large number of applications.

To create a new task sequence step for installing applications

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

107

Microsoft Deployment Toolkit 2010 Update 1

1. Create a new task sequences step based on the Install Application type at the appropriate place in the task sequence hierarchy as described in Configure the Task Sequence Properties Task Sequence Tab. 2. Configure the new task sequence step to deploy one or more applications as described in Configure an Existing Install Applications Task Sequence Step.

Configuring Packages in Deployment Workbench
Packages in MDT 2010 are operating system software installed on the target computers and stored in CAB or MSU files, such as security updates, service packs, feature packs, or language packs. Manage the packages to be deployed to the reference and target computers in your organization using the Deployment Workbench. You configure packages in the Deployment Workbench in a deployment share’s Packages node by: • • • • • • • • • • Importing a new package as described in Import a New Package into Deployment Workbench. Modifying an existing package as described in Modify an Existing Package in Deployment Workbench. Copying a package as described in Copy a Package in Deployment Workbench. Moving a package as described in Move a Package in Deployment Workbench. Renaming a package as described in Rename a Package in Deployment Workbench. Deleting a package as described in Delete a Package from Deployment Workbench. Managing folders for packages as described in Manage Folders for Packages in Deployment Workbench. Enabling or disabling a package Enable or Disable a Package in Deployment Workbench. Preventing a package from being visible as described in Prevent a Package from Being Visible in Deployment Workbench. Customizing package installation as described in Customize Package Installation in Task Sequences.

Import a New Package into Deployment Workbench
Import packages into the Deployment Workbench by using the Import OS Packages Wizard. Start the Import OS Packages Wizard using one of the following methods: • In the console tree, click the Packages node or a folder beneath the Packages node. Then, in the Actions pane, click Import OS Packages.
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

108

• •

In the console tree, click the Packages node or a folder beneath the Packages node. Then, from the Action menu, click Import OS Packages. In the console tree, click the Packages node or a folder beneath the Packages node, and then click Import OS Packages.

To import a new package 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Packages (where deployment_share is the name of the deployment share to which you will add the application). 3. In the Actions pane, click Import OS Packages. The Import OS Packages Wizard starts. 4. Complete the Import OS Packages Wizard using the information in Table 48. Table 48. Information for Completing the Import OS Packages Wizard On this wizard page Specify Directory Do this In Package source directory, type path (where path is the fully qualified path to the folder that contains the package you want to import), and then click Next.
Note You can alternatively click Browse to find the folder on a local drive or network shared folder.

Summary Confirmation

View the information in the Details box, and then click Next.
Tip You can click Save Output to save the output of the wizard to a file. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.

Click Finish. The Import OS Packages Wizard finishes. The package is added to the list of packages in the details pane of the Deployment Workbench.

Modify an Existing Package in Deployment Workbench
Modify packages in the Packages node in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. The package properties are mostly configured when you run the Import OS Packages Wizard. Update the package properties on the General tab through the package_name Properties dialog box (where package_name is the name of the application in Deployment Workbench).
Solution Accelerators microsoft.com/technet/SolutionAccelerators

109

Microsoft Deployment Toolkit 2010 Update 1

To modify an existing package 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Packages (where deployment_share is the name of the deployment share in which you will configure the package). 3. In the details pane, click package_name (where package_name is the name of the package you want to configure). 4. In the Actions pane, click Properties. The package_name Properties dialog box opens (where package_name is the name of the package you want to configure). 5. On the General tab, configure the settings listed in Table 49 based on the requirements of your organization, and then click OK. Table 49. Configuration Settings on the General Tab of the Package Properties Setting Name Description Contains the name of the package displayed in the Deployment Workbench. If Display name is not configured, this value is also displayed in the Windows Deployment Wizard. Provides information about the package. (Optional) Contains the name displayed in the Windows Deployment Wizard instead of the value in Name. If no value is specified, the value in Name is displayed in the Windows Deployment Wizard. Type of package, which typically includes the following high-level types of packages: • Language packs • Quick Fix Engineering patches • Feature packs
Note The package type in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Comments Display name

Type

Processor architecture

Target processor architecture for the package; it can be x86, x64, or ia64.
Note The processor architecture in this box is automatically determined by the Deployment Workbench and cannot be modified.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

110

Setting Language

Description Contains the language of the application.
Note The language in this box is automatically determined by the Deployment Workbench and cannot be modified.

Keyword

Used to identify the version of the language pack.
Note The keyword in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Public key token

Contains the public key token that MDT 2010 uses to updated the unattended.xml file.
Note The public key token in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Version

Contains the version number of the package.
Note The version number in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Product name

Contains the name of the product for which the package is intended.
Note The product name in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Product version

Contains the version number of the product for which the package is intended.
Note The product version number in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Package path

Contains the path of the package relative to the root of the deployment share.
Note The path in this text box is automatically determined by the Deployment Workbench and cannot be modified.

Hide this package in the Deployment Wizard

Select to control when this package appears in the Windows Deployment Wizard. If the check box is: • Selected, the Windows Deployment Wizard will not display this package. • Cleared, the Windows Deployment Wizard displays this package. Select to control when this package is available to other wizards and dialog boxes in the Deployment Workbench. If the check box is:
microsoft.com/technet/SolutionAccelerators

Enable (approve) this package

Solution Accelerators

111

Microsoft Deployment Toolkit 2010 Update 1

Setting

Description • Selected, other wizards and dialog boxes in the Deployment Workbench are able to select this package. • Cleared, other wizards and dialog boxes in the Deployment Workbench are unable to select this package.

The package configuration settings are saved, and the modifications are displayed in the details pane of the Deployment Workbench.

Copy a Package in Deployment Workbench
You can copy and paste packages and folders beneath the Packages node in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench.

Move a Package in Deployment Workbench
You can move packages and folders beneath the Packages node in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench.

Rename a Package in Deployment Workbench
You can rename packages and folders beneath the Packages node in the Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench.

Delete a Package from Deployment Workbench
You can delete packages and folders beneath the Applications node in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual package or entire folder structures.

Manage Folders for Packages in Deployment Workbench
You can manage folders beneath the Packages node in the Deployment Workbench to create hierarchical groupings of operating system packages. For more information on: • • Managing folders, see Manage Folders in Deployment Workbench. Selection profiles, see Manage Selection Profiles.

Enable or Disable a Package in Deployment Workbench
You can control whether packages are available to other wizards and dialog boxes in the Deployment Workbench by selecting the Enable (approve) this package check box on the General tab of the package Properties dialog box.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

112

Tip If you want to configure a package so that it can only be installed during a task sequence step, disable the application. Doing so allows the package to be installed during the task sequence but prevents the application from appearing in the list of available package.

For more information on enabling or disabling packages in the Deployment Workbench, see Configuring Packages in Deployment Workbench.

Prevent a Package from Being Visible in the Windows Deployment Wizard
You can prevent a package from being visible in the Windows Deployment Wizard by selecting the Hide this application in the Deployment Wizard check box on the General tab of the application Properties dialog box. For more information on preventing packages from appearing in the Windows Deployment Wizard, see Configuring Packages in Deployment Workbench.

Customize Package Installation in Task Sequences
Adding packages in a deployment share’s Packages node through the Deployment Workbench is the simplest method for deploying most packages. MDT 2010 task sequences deploy packages using the Install Updates Offline task sequence type. Some of task sequence templates included in MDT 2010 have the Apply Patches task sequence step in the Preinstall/Refresh only group, which is based on the Install Updates Offline task sequence type. The Install Updates Offline task sequence type allows you to install one or more packages in a single task sequence step using selection profiles, which allow one or more packages to be selected and deployed as a unit. For more information managing selection profiles, see Manage Selection Profiles. Customize the package deployment process in your task sequences by: • Configuring the existing Apply Patches task sequence step in the Preinstall group as described in Configure an Existing Apply Patches Task Sequence Step. Creating a new task sequence step based on the Install Updates Offline task sequence type as described in Create a New Task Sequence Step for Installing Packages. Adding language packs to task sequence steps as described in Add Language Packs to Task Sequence Steps.

Configure an Existing Apply Patches Task Sequence Step
You configure an existing Apply Patches task sequence step by modifying the configuration settings on the Properties tab of the task sequence step. To configure an existing Apply Patches task sequence step 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

113

Microsoft Deployment Toolkit 2010 Update 1

2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share to which you will add the application). 3. In the details pane, click task_sequence (where task_sequence is the name of the task sequence you want to configure). 4. In the Actions pane, click Properties. The task_sequence Properties dialog box opens (where task_sequence is the name of the application you want to configure). 5. In the task_sequence Properties dialog box, click the Task Sequence tab (where task_sequence is the name of the application you want to configure). 6. In the hierarchy of the task sequence, go to Preinstall/Apply Patches. 7. On the Properties tab, configure the settings listed in Table 50 based on the requirements of your organization, and then click OK. Table 50. Configuration Settings on the Properties Tab of the Install Applications Task Sequence Step Setting Name Description Selection profile Description Configures the name of the task sequence step displayed in the task sequence hierarchy. Configures the description text for the task sequence step. Used to select the selection profile that contains the updates you want to deploy in this task sequence step. The selection profile can contain one or more packages to be deployed.

The updated task sequence appears in the details pane of the Deployment Workbench.

Create a New Task Sequence Step for Installing Packages
In most instances, the existing Apply Patches task sequence step is sufficient for installing packages to target computers. However, there are instances in which the existing Apply Patches task sequence step may not be sufficient for your requirements or you may need to install a package at a different place in the task sequence. For example, the packages may need to be installed in a specific order or may have dependencies, such as installing a service pack before installing hotfixes. First, create folders and selection profiles for each grouping of packages that you wanted to install separately, Then, install the groups of packages by creating a new task sequence step for each group based on the Install Updates Offline– type task sequence step.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

114

Tip You can disable the existing Apply Patches step in the task sequence and add all packages manually using the task sequence controls. The benefits of this approach is that you easily select and insert packages into the task sequence in any order necessary. This simplifies management of a large number of packages.

To create a new task sequence step for installing packages 1. Create a new task sequences step based on the Install Updates Offline type at the appropriate place in the task sequence hierarchy as described in Configure the Task Sequence Properties Task Sequence Tab. 2. Configure the new task sequence step to deploy one or more packages by selecting the appropriate selection profile containing the packages to be installed as described in Configure an Existing Install Applications Task Sequence Step.

Add Language Packs to Task Sequence Steps
Language packs are one of the types of packages available in MDT 2010 and enable a multilingual Windows environment. Windows Vista is language neutral, and all language and locale resources are added to Windows Vista through language packs (Lp.cab files). By adding one or more language packs to Windows Vista, those languages can be enabled when installing the operating system. As a result, the same Windows Vista image can be deployed to regions with different language and locale settings, reducing development and deployment time. See the following references for additional information about language packs in Windows Vista: • • • For instructions on installing language packs during deployment, see Running the Windows Deployment Wizard. For the configuration properties for installing language packs automatically, see the MDT 2010 document, Toolkit Reference. For more information about Windows Vista language packs, see “Manage Language Packs for Windows” in the Windows AIK.

If installing Windows XP MUI language packs, add each language pack as an application to the distribution share. Then, install the language pack as part of the task sequence, or allow the user to choose a language pack during deployment. For language packs, create a subgroup called Language Packs in the State Restore group, and then add language packs to it. Doing so installs language packs automatically, keeps them organized, and provides control over the installation order. To prevent users from seeing language packs in the list of applications during deployment, in the Application Properties dialog box (where Application is the name of the language pack added to the distribution share), clear the Enable this application check box.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

115

Microsoft Deployment Toolkit 2010 Update 1

Configuring Device Drivers in Deployment Workbench
Integrate device drivers for the reference and target computers into Windows PE and the target operating system unless these components are included in Windows PE or the target operating system. The Deployment Workbench helps centralize and automate device driver management and integration for LTI by providing a centralized repository of device drivers, ensuring that the proper device drivers are deployed. The Deployment Workbench also automates the injection of the appropriate device drivers into Windows PE images that the Deployment Workbench generates. MDT 2010 supports different strategies for device driver management. For more information about device driver management strategies, see Managing Device Drivers. Configure device drivers in the Deployment Workbench in a deployment share’s Out-of-Box node by: • • • • • • • • • Importing device drivers as described in Import Device Drivers into Deployment Workbench. Modifying existing device drivers as described in Modify Existing Device Drivers in Deployment Workbench. Copying device drivers as described in Copy Device Drivers in Deployment Workbench. Moving device drivers as described in Move Device Drivers in Deployment Workbench. Renaming device drivers as described in Rename Device Drivers in Deployment Workbench. Deleting device drivers as described in Delete Device Drivers from Deployment Workbench. Managing folders for device drivers as described in Manage Folders for Device Drivers in Deployment Workbench. Enabling or disabling device drivers as described in Enable or Disable Device Drivers in Deployment Workbench. Deploy specific device drivers to target computers for LTI deployments as described in Deploy Specific Device Drivers to Target Computers in LTI.

Import Device Drivers into Deployment Workbench
Import device drivers into the Deployment Workbench using the Import Drivers Wizard. Start the Import Drivers Wizard using one of the following methods: • • In the console tree, click the Out-of-Box Drivers node or a folder beneath the Out-of-Box Drivers node. Then, in the Actions pane, click Import Drivers. In the console tree, click the Out-of-Box Drivers node or a folder beneath the Out-of-Box Drivers node. Then, from the Action menu, click Import Drivers.
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

116

In the console tree, click the Out-of-Box Drivers node or a folder beneath the Out-of-Box Drivers node, and then click Import Drivers.

To import device drivers 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Out-of-box Drivers node (where deployment_share is the name of the deployment share to which you will add the device drivers) or a folder beneath that node. 3. In the Actions pane, click Import Drivers. The Import Driver Wizard starts. 4. Complete the Import Driver Wizard using the information in Table 51. Table 51. Information for Completing the Import Driver Wizard On this wizard page Specify Directory Do this 1. In Driver source directory, type path (where path is the fully qualified path to the folder that contains the device drivers you want to import).
Note You can alternatively click Browse to find the folder on a local drive or network shared folder.

2. Select or clear the Import drivers even if they are duplicates of an existing driver check box based on the requirements of your organization. If the check box is: • Selected, the wizard will import the drivers even if the same drivers already exist. • Cleared, the wizard will not import the drivers if the same drivers already exist.
Tip In most instances, do not select this check box, as doing so increases the size of the deployment share and makes driver management more complex.

3. Click Next. Summary Confirmation Click Next.
Tip You can click Save Output to save the output of the wizard to a file. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.

Click Finish.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

117

Microsoft Deployment Toolkit 2010 Update 1

The Import Drivers Wizard finishes. The device drivers are added to the list of device drivers in the details pane of the Deployment Workbench.

Modify Existing Device Drivers in Deployment Workbench
Modify device drivers in the Out-of-Box Drivers node in the Deployment Workbench using the Properties action as described in View Item Properties in Deployment Workbench. Configure device drivers in the Deployment Workbench by performing the following steps in the device driver Properties dialog box: • • Configure properties on the General tab as described in Configure the Device Driver Properties General Tab. View properties on the Details tab as described in View the Device Driver Properties Details Tab.

Configure the Device Driver Properties General Tab
The device driver properties stored on the General tab are mostly configured when you run the Import Device Drivers Wizard. Update the device driver properties on the General tab through the driver_name Properties dialog box (where driver_name is the name of the device driver in the Deployment Workbench). To modify existing device drivers properties on the General tab 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Out-of-Box Drivers (where deployment_share is the name of the deployment share in which you will configure the device driver). 3. In the details pane, click driver_name (where driver_name is the name of the device driver you want to configure). 4. In the Actions pane, click Properties. The driver_name Properties dialog box opens (where driver_name is the name of the device driver you want to configure). 5. On the General tab, configure the settings listed in Table 52 based on the requirements of your organization, and then click OK. Table 52. Configuration Settings on the General Tab of the Device Driver Properties Setting Driver name Description Contains the name of the device driver displayed in the Deployment Workbench and the Windows Deployment Wizard. Provides information about the device driver.
microsoft.com/technet/SolutionAccelerators

Comments
Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

118

Setting Platforms: x86

Description Select to control whether this device driver is for 32-bit operating system. If the check box is: • Selected, the device driver is available for deployment to 32-bit operating systems. • Cleared, the device driver is unavailable for deployment to 32-bit operating systems.
Note If the Deployment Workbench incorrectly detects the platforms that the device driver supports, you can clear the platform selection. For example, if the Deployment Workbench incorrectly detects 32-bit and 64-bit device drivers, clear the x64 selection; the driver will then only be used for 32-bit deployments.

Platforms: x64

Select to control whether this device driver is for 64-bit operating system. If the check box is: • Selected, the device driver is available for deployment to 64-bit operating systems. • Cleared, the device driver is unavailable for deployment to 64-bit operating systems.
Note If the Deployment Workbench incorrectly detects the platforms that the device driver supports, you can clear the platform selection. For example, if the Deployment Workbench incorrectly detects 32-bit and 64-bit device drivers, clear the x64 selection; the driver will then only be used for 32-bit deployments.

Enable this driver

Select to control whether this device driver is available to other wizards and dialog boxes in the Deployment Workbench. If the check box is: • Selected, the device driver is available to other wizards and dialog boxes in the Deployment Workbench. • Cleared, the device driver is unavailable to other wizards and dialog boxes in the Deployment Workbench.

The device driver configuration settings are saved, and the modifications are displayed in the details pane of the Deployment Workbench.

View the Device Driver Properties Details Tab
The device driver properties stored on the Details tab are configured when you run the Import Device Drivers Wizard. All the information on the Details tab is read only and cannot be modified. View the device driver properties on the Details tab through the driver_name Properties dialog box (where driver_name is the name of the device driver in the Deployment Workbench).

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

119

Microsoft Deployment Toolkit 2010 Update 1

To view existing device drivers properties on the Details tab 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Out-of-Box Drivers (where deployment_share is the name of the deployment share in which you will configure the device driver). 3. In the details pane, click driver_name (where driver_name is the name of the device driver you want to configure). 4. In the Actions pane, click Properties. The driver_name Properties dialog box opens (where driver_name is the name of the device driver you want to configure). 5. On the Details tab, view the settings listed in Table 53, and then click OK.
Note The configuration settings on the Details tab are automatically determined by the Deployment Workbench and cannot be modified.

Table 53. Configuration Settings on the Details Tab of the Device Driver Properties Setting Manufacturer Version Driver date Driver type (class) INF path Supported OS versions Hash Supported PnP IDs This driver is WHQL signed Description Contains the name of the device driver manufacturer. Contains the version number of the device driver. Contains the date of the device driver. Contains the class of the device driver, such as system or boot. Contains the path to the device drive file relative to the root of the deployment share. Contains a comma-separated list of the Windows operating system versions that the device driver supports. Contains the encrypted hash of every file that is part of the driver package. Contains a list of the plug-and-play IDs that the device driver supports. Select to indicate whether the device driver is signed by the Windows Hardware Quality Labs (WHQL). For device drivers that pass the WHQL tests, Microsoft creates a digitally signed certification file that allows installation on 64-bit versions of Windows Vista and prevents 32-bit
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

120

Setting

Description versions of Windows Vista and all versions of Windows XP from displaying a warning message that the driver has not been certified by Microsoft. If the check box is: • Selected, the device driver has been signed by the WHQL. • Cleared, the device driver has not been signed by the WHQL.

Copy Device Drivers in Deployment Workbench
You can copy and paste device drivers and folders beneath the Out-of-Box Drivers node in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench.

Move Device Drivers in Deployment Workbench
You can move device drivers and folders beneath the Out-of-Box Drivers node in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench.

Rename Device Drivers in Deployment Workbench
You can rename device drivers and folders beneath the Out-of-Box Drivers node in the Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench.

Delete Device Drivers from Deployment Workbench
You can delete device drivers and folders beneath the Out-of-Box Drivers node in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual packages or entire folder structures.

Manage Folders for Device Drivers in Deployment Workbench
You can manage folders beneath the Out-of-Box Drivers node in the Deployment Workbench to create hierarchical groupings of device drivers. For more information on: • • Managing folders, see Manage Folders in Deployment Workbench. Selection profiles, see Manage Selection Profiles.

Enable or Disable Device Drivers in Deployment Workbench
You can control whether device drivers are available to other wizards and dialog boxes in the Deployment Workbench by selecting the Enable this driver check box on the General tab of the device driver Properties dialog box.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

121 Microsoft Deployment Toolkit 2010 Update 1 Note If you disable a device driver. Copying task sequences as described in Copy Task Sequences in Deployment Workbench. Task sequences in MDT 2010 use the same task sequence engine as System Center Configuration Manager. see Select the Device Driver Management Strategy. Modifying an existing task sequence as described in Modify an Existing Task Sequence in Deployment Workbench. For more information about strategies for device driver management. configure the LTI deployment process to install specific drivers to target computers as described in Control Device Driver Deployments for LTI. System Center Configuration Manager is not required to perform LTI deployments. Configure task sequences in the Deployment Workbench in a deployment share’s Packages node by: • • • • • • • • Creating a new task sequence as described in Create a New Task Sequence in Deployment Workbench. Then. Use the Deployment Workbench to manage the task sequences used to perform deployments to the reference and target computers in your organization. Managing folders for task sequences as described in Manage Folders for Task Sequences in Deployment Workbench. For more information on enabling or disabling device drivers in the Deployment Workbench. microsoft. Deleting task sequences as described in Delete Task Sequences from Deployment Workbench. see Modify Existing Device Drivers in Deployment Workbench. Configuring Task Sequences in Deployment Workbench Task sequences in MDT 2010 contain the steps to be performed during LTI. Renaming task sequences as described in Rename Task Sequences in Deployment Workbench. the driver is never installed. Moving task sequences as described in Move Task Sequences in Deployment Workbench. Deploy Specific Device Drivers to Target Computers in LTI By default. the target operating system uses Plug-andPlay IDs to identify the device drivers that are needed for the devices on the target computers. Enabling or disabling a task sequence as described in Enable or Disable a Task Sequence in Deployment Workbench. To change this default behavior. LTI deployments include all device drivers in Windows PE and deploy them to the target computers.com/technet/SolutionAccelerators Solution Accelerators . However.

you can modify task sequences created from the templates to meet the requirements of your organization. Backs up the system entirely. In the console tree. backs up the user state. and then click New Task Sequence. and wipes the disk. including desktop and portable computers. click the Task Sequences node or a folder beneath the Task Sequences node. click the Task Sequences node or a folder beneath the Task Sequences node. Start the New task Sequence Wizard using one of the following methods: • In the console tree. • Create a New Task Sequence in Deployment Workbench Using the New Task Sequence Wizard in the Deployment Workbench to create new task sequences. Table 54.com/technet/SolutionAccelerators Solution Accelerators . from the Action menu. Task Sequence Templates Template Capture Only Standard Client Task Sequence Standard Client Replace Task Sequence Custom Task Sequence Standard Server Task Sequence Litetouch OEM Task Sequence Description Captures only an image of the reference computer. Table 54 lists the task sequence templates in MDT 2010. In many instances. In the console tree. Creates the default task sequence for deploying operating system images to client computers. and then. Modifying the unattended setup answer file for a task sequence as described in Modify the Unattended Setup Answer File Associated with the Task Sequence.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 122 • Preventing task sequences from being visible in the Windows Deployment Wizard as described in Prevent a Task Sequence from Being Visible in the Windows Deployment Wizard. Creates the default task sequence for deploying operating system images to server computers. and then. Pre-loads operating systems images on computers in a staging environment prior to deploying the target computers in the production environment (typically by a computer OEM). in the Actions pane. click New Task Sequence. • • MDT 2010 includes task sequence templates that you can use for common deployment scenarios. However. Creates a customized task sequence that does not install an operating system. click New Task Sequence. click the Task Sequences node or a folder beneath the Task Sequences node. microsoft. you can use the templates without any modification to the task sequence.

and then click Deployment Workbench. Click Start. type task_sequence_id (where task_sequence_id is a unique identifier for the task sequence you are creating).com/technet/SolutionAccelerators . To create a new task sequence 1. Level is the service pack level (SP1. Although you can select the Litetouch OEM Task Sequence template from other deployment shares. Tip Although you can change a task sequence’s name and comments later. 3. In Task sequence name. In the Deployment Workbench console tree. 3. you cannot change a task sequence’s ID. Complete the New Task Sequence Wizard using the information in Table 55. The New Task Sequence Wizard starts. create a naming scheme to use in creating task sequence IDs that will provide meaningful information about each task sequence. An example naming scheme is VersionEdition-Level-Label. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share to which you will add the task sequence). Edition is the operating system edition (Enterprise. and Label is a descriptive label that identifies the customizations. Ultimate). 4. SP2). where Version is the operating system version (win2003. click New Task Sequence. 2. the task sequence will not finish successfully. Before creating task sequences. 2. and then point to All Programs. In the Actions pane. Table 55. Solution Accelerators microsoft. win2007). Point to Microsoft Deployment Toolkit. Note Select the Litetouch OEM task sequence only when performing deployments using removable media–based deployments you create in the Media node in the Deployment Workbench. Standard. In Task sequence ID. type task_sequence_name (where task_sequence_name is a descriptive name for the task sequence you are creating). type task_sequence_comment (where task_sequence_comment is text that describes the purpose or usage of the task sequence). Information for Completing the New Task Sequence Wizard On this wizard page General Settings Do this 1.123 Microsoft Deployment Toolkit 2010 Update 1 Template Description Post OS Installation Task Performs installation tasks after the operating Sequence system has been deployed to the target computer. In Task sequence comments.

2.com/fwlink/?LinkID=75674. select task_sequence. and then click Next. • Specify the product key for this operating system. and then click Next. MAK product keys are used by Microsoft Volume Licensing customers. • Specify a multiple activation key (MAK) for activating this operating system. select operating_system (where operating_system is the operating system in the Operating Systems node in the Deployment Workbench that you want to deploy to the resource or target computer). In The following operating system images are available to be deployed with this task sequence. when the product key will be provided in the Windows Deployment Wizard. In The following task sequence templates are available.com/technet/SolutionAccelerators Solution Accelerators . OS Settings 1. Select one to use. type organization_name (where organization_name is the name of the microsoft. type user_full_name (where user_full_name is the name of the user of the target computer). Windows Server 2008. 1. see Windows Vista Volume Activation 2. Select the one you would like to use as a starting point.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 124 On this wizard page Select Template Do this 4.0 Technical Guidance at http://go. Click Next. or when using volume licenses that are activated using KMS. Click one of the following options based on the requirements of your organization: • Do not specify a product key at this time. Select this option when a product key is not required when deploying Windows Vista. Select OS Specify Product Key 2. In Full Name. Click Next. Note For more information about Volume Activation and product keys in MDT 2010. In Organization. Select this option when deploying Windows XP or Windows Server 2003 Volume Licensing keys or retail product keys. Select this option when deploying Windows Vista or later operating systems using MAK product keys in the deployment. or later operating systems.microsoft.

Point to Microsoft Deployment Toolkit. Configure task sequences in the Deployment Workbench by performing the following steps in the task sequence Properties dialog box: • • • Configure properties on the General tab as described in Configure the Task Sequence Properties General Tab. Summary Confirmation The New Task Sequence Wizard finishes. Modify an Existing Task Sequence in Deployment Workbench Modify task sequences in the Task Sequences node in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. Click Start. The package is added to the list of packages in the details pane of the Deployment Workbench. type password (where password is the password to be assigned to the built-in Administrator account on the reference or target computer). Configure properties on the Task Sequence tab as described in Configure the Task Sequence Properties Task Sequence Tab. and then point to All Programs. Click Next. Click Finish. 4. Admin Password In Administrator Password and Please confirm Administrator Password. and then click Deployment Workbench. 3.125 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this organization). Configure properties on the OS Info tab as described in Configure the Task Sequence Properties OS Info Tab. In Internet Explorer Home Page. Configure the Task Sequence Properties General Tab The task sequence properties stored on the General tab are mostly configured when you run the New Task Sequence Wizard. and then click Next. Click Next. Update the task sequence properties on the General tab through the task_sequence_name Properties dialog box (where task_sequence_name is the name of the task sequence in the Deployment Workbench). Solution Accelerators microsoft. type home_url (where home_url is the Uniform Resource Locator [URL] of the website to be the default site when starting Internet Explorer). To modify existing task sequence properties on the General tab 1.com/technet/SolutionAccelerators .

You can type any version number that is appropriate for your organization’s versioning standards. In the Actions pane. Contains the version number of the task sequence. On the General tab. Select to configure the task sequence to run on any supported 32-bit or 64-bit Windows operating system. 5. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). Task sequence name Contains the name of the task sequence displayed in the Deployment Workbench and the Windows Deployment Wizard. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). the Windows Deployment Wizard will microsoft. and then click OK. In the Deployment Workbench console tree. 4. Configuration Settings on the General Tab of Task Sequence Properties Setting Task sequence ID Description Contains the task sequence identifier that the New Task Sequence Wizard provided. Table 56. If the check box is: • Selected. Note The information in this text box is automatically generated by Deployment Workbench and cannot be modified. Comments Task sequence version Provides information about the task sequence. In the details pane. 3. The other available option is This can run only any platform.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 126 2. Select to control when this task sequence appears in the Windows Deployment Wizard.com/technet/SolutionAccelerators This can run on any platform This can run only on the specified client platforms Hide this task sequence in the Deployment Wizard Solution Accelerators . The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). configure the settings listed in Table 56 based on the requirements of your organization. click Properties. Select to configure the task sequence to run on any supported 32-bit or 64-bit Windows operating system. The other available option is This can run only on the specified client platforms.

The Task Sequence tab contains areas and other controls that you use to: • • • Configure steps and sequences as described in Configure the Task Sequence Steps and Step Sequence. Configure the Task Sequence Steps and Step Sequence The Task Sequence tab contains a hierarchical representation of the task sequence steps and their sequence. The task sequence configuration settings are saved. You use task sequence step groups to control the processing of one or more task sequence steps as a unit. the Windows Deployment Wizard displays this task sequence. • Cleared.127 Microsoft Deployment Toolkit 2010 Update 1 Setting Description not display this task sequence. If the check box is: • Selected.com/technet/SolutionAccelerators . Enable this task sequence Select to control when this task sequence is available to other wizards and dialog boxes in the Deployment Workbench. You can organize multiple groups and task sequence steps to create a hierarchy of groups and task sequence steps. Configure the task sequence steps and step sequence by selecting one of the following options from the menu bar at the top of the hierarchical representation: Solution Accelerators microsoft. you can update the task sequence properties on the Task Sequence tab through the task_sequence_name Properties dialog box (where task_sequence_name is the name of the task sequence in the Deployment Workbench). • Cleared. You can organize one or more task sequence steps by creating a group. and the modifications are displayed in the details pane of the Deployment Workbench. other wizards and dialog boxes in the Deployment Workbench cannot select this task sequence. Configure the Task Sequence Properties Task Sequence Tab The task sequence properties stored on the Task Sequence tab are mostly configured when you run the New Task Sequence Wizard. Task sequence steps are organized into a hierarchical folder structure based on deployment phases. Configure step properties as described in Configure the Task Sequence Step Properties. Configure step options as described in Configure the Task Sequence Step Options. other wizards and dialog boxes in the Deployment Workbench can select this task sequence. However.

Select to add a task sequence step group or step to the task sequence. Select to configure a task sequence step to be processed earlier in the deployment process. The categories of task sequence steps that you can add are listed in Table 58 along with the task sequence step types in each category. see the corresponding section in the MDT 2010 document.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 128 • Add. the task sequence step will be performed before the entire group and will be removed from the group.com/technet/SolutionAccelerators . • Up. Table 57. If another task sequence group immediately precedes the group. Solution Accelerators microsoft. Task Sequence Step Categories and Types Category Task sequence step types in this category General • • • • • • • • Run Command Line Set Task Sequence Variable Restart computer Gather Install Updates Offline Validate Install Application Inject drivers Disks Images Settings • Format and Partition Disk • Enable BitLocker • Install Operating System • Apply Network Settings • Capture Network Settings • Recover From Domain • • • • • Install Roles and Features Configure DHCP Configure DNS Configure ADDS Authorize DHCP Roles • Remove. you also remove all the task sequence steps in that group. For more information about each of the task sequence step types listed in Table 57. Note If you move the first task sequence step in a task sequence group up. Important If you remove a task sequence group. The move is reflected in the task sequence hierarchy. the task sequence step will become the last step in the preceding group. Toolkit Reference. Select to remove the currently highlighted task sequence step or group.

In addition to these properties. the task sequence step will become the first step in the following group. 5. To modify existing task sequence steps and step sequence 1. In the details pane. Configure the Task Sequence Step Properties On the Properties tab. Select to configure a task sequence step to be processed earlier in the deployment process. Task sequence steps are different for each task sequence step type. Packages. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure).129 Microsoft Deployment Toolkit 2010 Update 1 • Down. Table 58. see Customize Package Installation in Task Sequences. Click Start. 2. and then click Deployment Workbench. and then click OK. Table 58 lists the properties common to task sequence groups and steps. see Customize Application Installation in Task Sequences. The configuration settings for: • • Task sequence groups are the same for all groups. in the task sequence hierarchy. most task sequence steps have properties that are specific to the task sequence type. Point to Microsoft Deployment Toolkit. and the modifications are displayed in the details pane of the Deployment Workbench. In the Actions pane. On the Task Sequence tab. you configure the properties for task sequence groups or individual task sequence steps.com/technet/SolutionAccelerators . click Properties. 3. Note If you move the last task sequence step in a task sequence group down. In the Deployment Workbench console tree. For more information about customizing task sequence steps for installing: • • Applications. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). The task sequence configuration settings are saved. configure the task sequence steps and step sequences based on the requirements of your organization. Properties Common to Task Sequence Groups and Steps Solution Accelerators microsoft. the task sequence step will be performed after the entire group and will be removed from the group. 4. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). If another task sequence group immediately follows the group. and then point to All Programs.

click the Properties tab. configure the task sequence group or individual step based on the requirements of your organization. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). 6. In the Deployment Workbench console tree.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 130 Setting Type Description Contains the task sequence type. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). which is always set to Group for task sequence groups or to the types listed in Table 57. you configure settings that control how the task sequence step runs. determine whether the step should continue in the event of an error. In the details pane. These settings allow you to disable the step. and then point to All Programs. click Properties. and then click Deployment Workbench. 4. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure).com/technet/SolutionAccelerators . On the Task Sequence tab. Click Start. and any conditions for running the step. 3. specify the return codes for the step that indicate success. Name Description For more information about: • • Configuring specific task sequence step types. The configuration settings on the Options tab for: Solution Accelerators microsoft. Contains the name of the task sequence group or step displayed in the task sequence hierarchy. see the section for corresponding task sequence steps in the MDT 2010 document. Provides descriptive information about the task sequence group or step. The properties for each task sequence type. in the task sequence hierarchy. see the corresponding section in Configuring Task Sequences in Deployment Workbench. In the Actions pane. To modify existing task sequence group and individual step properties 1. Toolkit Reference. Configure the Task Sequence Step Options On the Options tab. 5. Point to Microsoft Deployment Toolkit. and then click OK. On the Properties tab. 2.

Click Start. Table 59. and then click OK. the task sequence group or step runs during the task sequence. configure the task sequence group or individual step sequences based on the requirements of your organization. In the details pane. 5. 4. Contains the list of numeric codes that indicate whether the task sequence step finished successfully. Success codes Solution Accelerators microsoft. 7. if you configure a condition for a task sequence group. that condition affects all the task sequence steps within the group. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence).com/technet/SolutionAccelerators . Point to Microsoft Deployment Toolkit. Note Success codes are not available in task sequence step groups. An individual task sequence step affect only that step. If the check box is: • Selected. 3. click the Options tab. Configuration Settings on the Task Sequence Tab of Task Sequence Properties Setting Disable this step Description Select to control whether the task sequence step runs during the task sequence. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). configure the settings listed in Table 59 based on the requirements of your organization.131 Microsoft Deployment Toolkit 2010 Update 1 • • A task sequence group affect all the steps with the group. click Properties. and then point to All Programs. • Cleared. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). On the Task Sequence tab. On the Task Sequence tab. To modify existing task sequence group and individual step options 1. 2. 6. and then click Deployment Workbench. in the task sequence hierarchy. the task sequence group or step is not run during the task sequence. On the Options tab. In the Deployment Workbench console tree. For example. In the Actions pane. and then click OK.

the step runs. • Cleared. and Edit buttons to modify the conditions under which the group of tasks runs. • A Windows Management Instrumentation (WMI) Query Language (WQL) query within a WMI namespace.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 132 Setting Continue on error Description Select to control whether the task sequence should continue when the task sequence group or step encounters an error. the task sequence will not continue if the group or step encounters an error. The criteria can be based on: • An IF statement. In the Deployment Workbench console tree. 2. and then point to All Programs. Click Start. see Configure a Conditional Task Sequence Step. You update the task sequence properties on the OS Info tab through the task_sequence_name Properties dialog box (where task_sequence_name is the name of the task sequence in the Deployment Workbench). Condition list box For more information about conditions in task sequence steps. To modify existing task sequence properties on the OS Info tab 1.com/technet/SolutionAccelerators . Point to Microsoft Deployment Toolkit. and then click Deployment Workbench. Note Any conditions configured for a group affect all the tasks within a group. Configure the Task Sequence Properties OS Info Tab The task sequence properties stored on the OS Info tab are mostly configured when you run the New Task Sequence Wizard. Solution Accelerators microsoft. If the check box is: • Selected. • A task sequence variable. Contains any conditional criteria for running this step. Use the Add. the task sequence continues if the group or step encounters an error. • The version of the target operating system. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). If no criteria are specified. Remove. Add criteria for determining when the group of tasks should (or should not) run.

Configuration Settings on the OS Info Tab of Task Sequence Properties Setting Operating system description Description Contains the name of the operating system that you provided when creating the task sequence— for example Windows 7 ENTERPRISE. Note The information in this text box is automatically generated by the Deployment Workbench and cannot be modified. 4. The following list describes the architecture types running the Deployment Workbench and catalogs that you can create for each architecture: • Deployment Workbench running on x86. Build Contains the build number of the operating system. The Deployment Workbench cannot create catalog files for some Windows images of different architecture types. Note The information in this text box is automatically generated by the Deployment Workbench and cannot be modified. Table 60. configure the settings listed in Table 60 based on the requirements of your organization. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). and then click OK.com/technet/SolutionAccelerators Solution Accelerators .xml Click to modify the contents of the Unattended. In the details pane. On the OS Info tab.133 Microsoft Deployment Toolkit 2010 Update 1 3. Note The information in this text box is automatically generated by the Deployment Workbench and cannot be modified. In the Actions pane. 5. Platform Contains the processor architecture of the operating system—for example. Creates catalogs for x86 and x64 Windows images • Deployment Workbench running on x64. Edit Unattend. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). click Properties.xml file that the Deployment Workbench generates for Windows Vista or later operating systems. Creates catalogs only for x64 Windows images microsoft. x86.

Edit Sysprep. Delete Task Sequences from Deployment Workbench Delete task sequences and folders beneath the Task Sequences node in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench.txt that the Deployment Workbench generates for Windows XP and Windows Server 2003 operating systems.txt Click to modify the contents of the Unattend. Note The Get Operating System Catalog Wizard may appear if an operating system does not yet have a catalog. You will see a progress bar in the Get Operating System Catalog Wizard.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 134 Setting Description Note The Get Operating System Catalog Wizard may appear if an operating system does not yet have a catalog. and the modifications are displayed in the details pane of the Deployment Workbench. Copy Task Sequences in Deployment Workbench You can copy and paste task sequences and folders beneath the Task Sequences node in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench. The wizard may take a few minutes to finish.inf Click to modify the contents of the Sysprep.com/technet/SolutionAccelerators . but no user interaction is required. Move Task Sequences in Deployment Workbench Move task sequences and folders beneath the Task Sequences node in the Deployment Workbench by using the Cut and Paste actions as described in Move Items in Deployment Workbench.inf file that the Deployment Workbench generates for Windows XP and Windows Server 2003 operating systems. The wizard may take a few minutes to finish. Solution Accelerators microsoft. Edit Unattend. The task sequence configuration settings are saved. Rename Task Sequences in Deployment Workbench Rename task sequences and folders beneath the Task Sequences node in the Deployment Workbench by using the Rename action as described in Rename Items in Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual task sequences or entire folder structures. but no user interaction is required. A progress bar appears in the wizard.

Selection profiles.chm) and the Microsoft Windows Preinstallation Reference (Ref. there are instances in which you may need to modify the unattended setup answer file for a task sequence directly. see the Windows Automated Installation Kit User’s Guide in the Windows AIK. see Manage Selection Profiles. Solution Accelerators microsoft. Unattend. Enable or Disable a Task Sequence in Deployment Workbench You can control whether task sequences are available to other wizards and dialog boxes in the Deployment Workbench using the Enable this task sequence check box on the General tab of the package Properties dialog box as described in Configuring Task Sequences in Deployment Workbench. such as when you modify a configuration parameter that is not exposed in the Deployment Workbench or in the Windows Deployment Wizard. Modify the Unattended Setup Answer File Associated with the Task Sequence MDT 2010 automatically updates the unattended setup answer file (Unattend. Sysprep.inf and Unattend. see Configure the Task Sequence Properties OS Info Tab.xml) for a task sequence based on the configuration settings you provide in the Deployment Workbench and in the Windows Deployment Wizard. see Manage Folders in Deployment Workbench.cab file in the Support\Tools folder on the Windows installation media. For more information on: • • Managing folders.xml. Prevent a Task Sequence from Being Visible in the Windows Deployment Wizard You can prevent a task sequence from being visible in the Windows Deployment Wizard using the Hide this task sequence in the Deployment Wizard check box on the General tab of the application Properties dialog box as described in Configuring Task Sequences in Deployment Workbench.135 Microsoft Deployment Toolkit 2010 Update 1 Manage Folders for Task Sequences in Deployment Workbench You can manage folders beneath the Task Sequences node in the Deployment Workbench to create hierarchical groupings of task sequences.xml on the OS Info tab of the task sequence Properties dialog box. For more information about: • • • Modifying the unattended setup answer file in the Deployment Workbench.com/technet/SolutionAccelerators . However. see the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy. both of which are in the Deploy. Directly modify the unattended setup answer file for a task sequence by clicking Edit Unattend.txt.chm).

the following tasks are common to all items in the Deployment Workbench: • • • • • • Managing folders as described in Manage Folders in Deployment Workbench Viewing item properties as described in View Item Properties in Deployment Workbench Copying items as described in Copy Items in Deployment Workbench Moving items as described in Move Items in Deployment Workbench Renaming items as described in Rename Items in Deployment Workbench Deleting items as described in Delete Items from Deployment Workbench Manage Folders in Deployment Workbench You use folders to organize applications. Start the New Folder Wizard using one of the following methods: • In the console tree. click New Folder. such as device driver groups. Folders allow you to create hierarchies for organizing items as well as subsets of items that you can include in selection profiles.com/technet/SolutionAccelerators Solution Accelerators . Although some management are unique to each type of item. device drivers. microsoft. Note Folders are similar in concept to the groups that existed in previous versions of BDD and MDT. Management tasks for folders include: • • • • • • • Creating a new folder as described in Create a New Folder in Deployment Workbench. Renaming a folder as described in Rename a Folder in Deployment Workbench. and other items in the Deployment Workbench. Modifying an existing folder as described in Modify an Existing Folder in Deployment Workbench. click a node or a folder.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 136 Performing Common Management Tasks in Deployment Workbench You use the Deployment Workbench to perform many of the common management tasks. Enabling or disabling a folder as described in Enable or Disable a Folder in Deployment Workbench. in the Actions pane. operating systems. Deleting a folder as described in Delete a Folder in Deployment Workbench. Moving a folder as described in Move a Folder in Deployment Workbench. Create a New Folder in Deployment Workbench Create folders in the Deployment Workbench using the New Folder Wizard. Then. Copying a folder as described in Copy a Folder in Deployment Workbench.

subfolders. Point to Microsoft Deployment Toolkit. Solution Accelerators microsoft. Click Start. 3. Select or clear the Enable this folder check box based on the needs of your organization. and then point to All Programs. In Folder name.137 Microsoft Deployment Toolkit 2010 Update 1 • • In the console tree. In the console tree. Review the information. To create a new folder 1. Then.com/technet/SolutionAccelerators . You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. 3. 2. Table 61. go to Deployment Workbench/Deployment Shares/deployment_share/node_or_folder (where deployment_share is the name of the deployment share in which you will create the folder and node_or_folder is the name of the node or folder in which you will create the folder). type folder_comment (where folder_comment is text that describes the user of the folder in the deployment share). and content can be included in selection profiles • Cleared. right-click a node or a folder. type folder_name (where folder_name is the name of the folder you want to create). the folder. 2. Click Next. Tip You can click Save Output to save the output of the wizard to a file. In the Deployment Workbench console tree. After the New Folder Wizard finishes. In Folder comment. and content cannot be included in selection profiles. If this check box is: • Selected. Information for Completing the New Folder Wizard On this wizard page General Settings Do this 1. The New Folder Wizard starts. subfolders. Then. then click Next. Summary Confirmation Click Finish. click New Folder. click New Folder. the folder. 4. and then click Deployment Workbench. the new folder appears in the deployment share in the Deployment Workbench. from the Action menu. click New Folder. In the Actions pane. Complete the New Folder Wizard using the information in Table 61. 4. click a node or a folder.

you cannot select the folder in selection profiles. Select to enable or disable the folder. The folder configuration settings are saved. 5. Provides information about the folder. and then click Deployment Workbench. click Properties. and then point to All Programs. On the General tab. Configuration Settings on the General Tab of Folder Properties Setting Name Comments Enable this folder Description Contains the name of the folder that is displayed in the Deployment Workbench. Solution Accelerators microsoft. If the check box is: • Selected.com/technet/SolutionAccelerators . 2. Point to Microsoft Deployment Toolkit. Table 62. The folder properties are mostly configured when you run the New Folder Wizard. configure the settings listed in Table 62 based on the requirements of your organization. In the details pane. 4. • Cleared. Update the folder properties on the General tab through the folder_name Properties dialog box (where folder_name is the name of the folder in the Deployment Workbench). In the Deployment Workbench console tree. Click Start. In the Actions pane.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 138 Modify an Existing Folder in Deployment Workbench Modify existing folders in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. go to Deployment Workbench/Deployment Shares/deployment_share/node_or_folder (where deployment_share is the name of the deployment share in which you will modify the folder and node_or_folder is the name of the node or folder that contains the folder to be modified). and then click OK. To modify an existing folder 1. the modifications are displayed in the details pane of the Deployment Workbench. 3. you can select the folder in selection profiles. The folder_name Properties dialog box opens (where folder_name is the name of the folder to be modified). click folder_name (where folder_name is the name of the folder you want to modify).

In the details pane. Enable or Disable a Folder in Deployment Workbench You can control whether folders are available to other wizards and dialog boxes in the Deployment Workbench using the Enable this folder check box on the General tab of the folder Properties dialog box. and then click Properties. click an item. Click Start.139 Microsoft Deployment Toolkit 2010 Update 1 Copy a Folder in Deployment Workbench You can copy and paste folders in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share in which you will copy the item and item_type is the type of item you will copy. device drivers. 2. in the Actions pane. In the Deployment Workbench console tree.com/technet/SolutionAccelerators . such as an operating system or device driver). Solution Accelerators microsoft. click Properties. Point to Microsoft Deployment Toolkit. Then. The Delete Selected Items Wizard allows you to delete individual folders or an entire hierarchy of folders. from the Action menu. and then click Deployment Workbench. In the details pane. and then point to All Programs. double-click an item. see Modify an Existing Folder in Deployment Workbench. Rename a Folder in Deployment Workbench You can rename folders in Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench. For more information on enabling or disabling folders in the Deployment Workbench. click an item. Move a Folder in Deployment Workbench You can move folders in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench. Delete a Folder from Deployment Workbench You can delete a folder in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. right-click an item. View Item Properties in Deployment Workbench You can view the properties of operating systems. Then. To set the properties of an item in a deployment share 1. In the details pane. click Properties. and other items from the Deployment Workbench using one of the following methods: • • • • In the details pane.

Paste the item that you have copied using one of the following methods: To copy and paste items in a deployment share Solution Accelerators microsoft. In the details pane. click the target location. Then. click Paste. click Properties. Name already exists in the target deployment share. from the Action menu. click Paste. In the details pane. the configuration settings for the source item will be applied to the target item. If you want to create a duplicate of an item. in the Actions pane. click an item. The item Properties dialog box is displayed (where item is the name of the item you selected). • You can copy items by using: • • Copy Items Using the Cut and Paste Actions You can copy an item using the Cut and Paste actions in the Deployment Workbench. In the details pane. Then. click Copy. Drag-and-drop functionality as described in Copy Items Using Drag-and-Drop Functionality. an error is generated.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 140 3. including the name (if the items do not already have the same name). and other items within a deployment share or between two deployments shares. right-click the target location. click item (where item is the name of the item to be renamed). In the Actions pane. and then click Paste. In the details pane. Cut and Paste actions. Then. Copy Items in Deployment Workbench Use the Deployment Workbench to copy operating systems. In the details pane.com/technet/SolutionAccelerators . and then click Copy. Copy the item from the source location using one of the following methods: • • • • • • In the details pane. as described in Copy Items Using the Cut and Paste Actions. click Copy. right-click an item. in the Actions pane. click the target location. the Deployment Workbench creates a link to the original item instead of creating a separate copy of the item. This reduces the size of the deployment share. import the item again in the target folder. device drivers. Then. from the Action menu. When you copy an item. 4. click an item. When you copy an item between deployment shares and an item with the same: • GUID already exists in the target deployment share. In the details pane. because two items of the same type cannot have the same name.

and then point to All Programs. and then release the mouse button. In the Deployment Workbench console tree. click Paste. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share to which you will copy the item and item_type is the type of item you will copy. In the details pane. You can move items by using: • Cut and Paste actions as described in Move Items Using the Cut and Paste Actions. Move Items in Deployment Workbench Use the Deployment Workbench to move operating systems. 5. Point to Microsoft Deployment Toolkit. click item (where item is the name of the item to be copied). and other items within a deployment share or between two deployments shares. The item is copied to the target location in the details pane of the Deployment Workbench. Solution Accelerators microsoft. press CTRL. 2. go to target_folder (where target_folder is the name of the folder where you want to copy the item). In the details pane. Click Start. In the Actions pane. 6. 3. and then click Deployment Workbench. In the Deployment Workbench console tree. 4. Copy Items Using Drag-and-Drop Functionality You can copy items by dragging an item from the source location to the target location. Point to Microsoft Deployment Toolkit. The new copy of the item appears in the details pane of the Deployment Workbench. In the Actions pane. and then point to All Programs. Click Start. To copy items in the Deployment Workbench using drag-and-drop functionality 1. 2.com/technet/SolutionAccelerators . device drivers. In the details pane. such as an operating system or device driver). click Copy. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share in which you will copy the item and item_type is the type of item you will copy. such as an operating system or device driver). and then click Deployment Workbench.141 Microsoft Deployment Toolkit 2010 Update 1 1. 3. drag item (where item is the name of the item to be copied) to the target location.

In the details pane. Click Start. Point to Microsoft Deployment Toolkit. in the Actions pane. click the target location. click Paste. click Cut. Move Items Using Drag-and-Drop Functionality You can move items by dragging them from the source location to the target location. in the Actions pane. Then. In the details pane. and then click Cut. Cut the item from the source location using one of the following methods: • • • • • • In the details pane. Then. In the details pane. In the details pane. click Paste. click the target location. Solution Accelerators microsoft. Point to Microsoft Deployment Toolkit. in the Actions pane. To move items in the Deployment Workbench using drag-and-drop functionality 1. click an item. right-click the target location. In the details pane. and then click Paste. 3. and then click Deployment Workbench. such as an operating system or device driver).Using the Microsoft Deployment Toolkit: Managing LTI Deployments 142 • Drag-and-drop functionality as described in Move Items Using Drag-and-Drop Functionality. click Cut. and then point to All Programs. click Paste. and then point to All Programs. Paste the item that you have cut using one of the following methods: To move items in the Deployment Workbench using the Cut and Paste actions 1. and then click Deployment Workbench. 4. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share to which you will move the item and item_type is the type of item you will move. In the details pane. from the Action menu. Then. Then. click Cut. In the Deployment Workbench console tree.com/technet/SolutionAccelerators . Click Start. Then. click an item. The item is moved to the target location. Then. right-click an item. Move Items Using the Cut and Paste Actions You can move an item using the Cut and Paste in the Deployment Workbench. 2. click item (where item is the name of the item to be renamed). in the Actions pane. go to target_location (where target_location is the name of the location to which you want to move the item). from the Action menu. In the details pane.

In the details pane. The item is moved to the target location. and other items from the Deployment Workbench using the Delete Selected Items Wizard. In the details pane. and other items in the Deployment Workbench by using one of the following methods: • • • In the details pane. 2. click Rename. Then. right-click an item. click Delete. In the Deployment Workbench console tree. and then point to All Programs. Start the Delete Selected Items Wizard using one of the following methods: • In the details pane. Then. 3. and then click Deployment Workbench. To rename an item in a deployment share 1. such as an operating system or device driver). and then click Rename. click Rename. The new name of the item appears in the details pane of the Deployment Workbench. Then. Click Start. Then. and then press ENTER. in the Actions pane. in the Actions pane. such as an operating system or device driver). Because the Copy and Paste actions in the Deployment Workbench create a link to the original item rather than a separate copy.com/technet/SolutionAccelerators Solution Accelerators . So. In the details pane. the Deployment Workbench automatically renames any copies of an item in other folders. device drivers. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share in which you will rename the item and item_type is the type of item you will rename. in the Actions pane. click an item. drag item (where item is the name of the item to be moved) to the target location. In the details pane. Point to Microsoft Deployment Toolkit. In the details pane. 4. In the Deployment Workbench console tree. click an item. Rename Items in Deployment Workbench You can rename operating systems. from the Action menu. device drivers. click item (where item is the name of the item to be renamed).143 Microsoft Deployment Toolkit 2010 Update 1 2. microsoft. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share to which you will move the item and item_type is the type of item you will move. 3. type new_item_name (where new_item_name is the new name of the item). Delete Items from Deployment Workbench You can delete operating systems. when you rename an item. click Rename. click an item.

This check box allows you to delete: • Not only the immediate contents of a folder but also the content from subfolders. then the item and all items that have the same source file are deleted. • Selected and the selected item not a folder. Table 63. • Multiple items that have the same source file—for example. click Delete. Click Start. and then click Deployment Workbench. You can also delete items that have copies in multiple folders. go to Deployment Workbench/Deployment Shares/deployment_share/item_type (where deployment_share is the name of the deployment share to which you will add Solution Accelerators microsoft. and all the contents of all subfolders are deleted.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 144 • • In the details pane. such as an operating system or device driver) if no remaining items reference the folder. 2. only the selected item is deleted. then the folder. the selected item and all copies in other folders are deleted. Information for Completing the Delete Selected Items Wizard Check box Completely delete these items. In the Deployment Workbench console tree. To delete an item from a deployment share 1. • Cleared. In the details pane. such as Server-Core or Server-Enterprise. if you have an operating system image file that contains multiple operating system editions. only the selected item is deleted. including all copies of an item that might exist in other folders. and then click Delete. If this check box is: • Selected and the selected item is a folder. all subfolders or other items that have the same source file are unaffected. as well as multiple items that have the same source file Description Select to delete an item. You can delete individual items or folders that contain one or more items or subfolders. Point to Microsoft Deployment Toolkit. Note When you delete an item from the Deployment Workbench. all copies in other folders are unaffected. the corresponding file or folder is also deleted in the depoyment_share\item_type\item_subfolder (where deployment_share is the name of the deployment share and item_type is the type of item you are deleting. and then point to All Programs. click an item. • Cleared. The Delete Selected Items Wizard’s Options page includes the check boxes shown in Table 63.com/technet/SolutionAccelerators . If this check box is: • Selected. from the Action menu. even if there are copies in other folders Recursively delete the contents of folders. right-click an item. Then. subfolders.

or a device driver). The Delete Selected Items Wizard starts. 3. such as a folder. Tip You can click Save Output to save the output of the wizard to a file. In the details pane. Click Next. Information for Completing the Delete Selected Items Wizard On this wizard page Options Do this 1. an operating system. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. 5. this check box is cleared. click Delete. Select or clear the Completely delete these items. the item and other affected items are removed from the Deployment Workbench and from the deployment share. 4. 2. Performing Advanced Configuration Tasks in Deployment Workbench The Deployment Workbench includes advanced configuration options that extend the features provided in basic LTI deployments. and support deployments from stand-alone media without the need to connect to a deployment share. Click Next. Summary Confirmation Click Finish. as well as multiple items that have the same source file check box based on your requirements. such as an operating system or device driver). Select or clear the Recursively delete the contents of folders. After the Delete Selected Items Wizard finishes. Complete the Delete Selected Items Wizard using the information in Table 64. even if there are copies in other folders check box based on your requirements. this check box is cleared. support deployments in larger organizations.com/technet/SolutionAccelerators . click item (where item is the name of the item to be deleted.145 Microsoft Deployment Toolkit 2010 Update 1 the operating system and item_type is the type of item you are deleting. By default. These configuration options provide more granular selection of the content you want to include in the deployment. Table 64. Solution Accelerators microsoft. By default. In the Actions pane. 3.

Includes no folders or items in the Deployment Workbench. Use selection profiles to group items. operating system packages. Managing the MDT DB as described in Manage the MDT DB. and then use those groupings of items: • • • • • To include the appropriate device drivers and packages for Windows PE. including all applications and device drivers. including all device drivers. operating system packages. and task sequences.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 146 Advanced configuration tasks that you can perform include: • • • • Managing selection profiles as described in Manage Selection Profiles. Holds all folders from the Out-of-Box Drivers node in the Deployment Workbench. device drivers. Default Selection Profiles in Deployment Workbench Selection profile Everything Description Holds all folders from all nodes in the Deployment Workbench. device drivers. operating systems.com/technet/SolutionAccelerators All Drivers All Drivers and Packages Nothing Sample Solution Accelerators . As the basis for creating linked deployment shares. To identify the operating system packages to deploy in the Install Updates Offline task sequence step type. and task sequences. Holds all folders from the Applications and Out-of-Box Drivers nodes in the Deployment Workbench. including all applications. Managing deployment media as described in Manage MDT 2010 Deployment Media. MDT 2010 creates the default selection profiles listed in Table 65. A sample selection profile that shows how to select a subset of the items and include all folders from the microsoft. Table 65. To include the appropriate device drivers for the target operating system in the Inject Drivers task sequence step type. including applications. Managing linked deployment shares as described in Manage Linked Deployment Shares. As the basis for creating MDT 2010 deployment media. Manage Selection Profiles Selection profiles allow you to select one or more folders in the Deployment Workbench that contain one or more items in the Deployment Workbench. operating systems.

2. In the console tree. from the Action menu. and then click New Selection Profile. Create a New Selection Profile in Deployment Workbench Create selection profiles in the Deployment Workbench using the New Selection Profile Wizard. Copy a selection profile as described in Copy a Selection Profile in Deployment Workbench. in the Actions pane. click New Selection Profile.com/technet/SolutionAccelerators . Click Start. Rename a selection profile as described in Rename a Selection Profile in Deployment Workbench. To create a new selection profile 1. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Selection Profiles (where deployment_share is the name of the deployment share to which you will add the application). and then point to All Programs. Start the New Selection Profile Wizard using one of the following methods: • • • In the console tree. Then. Solution Accelerators microsoft. Identify the differences between selection provides and groups as described in Identify the Relationship Between Selection Profiles and Groups. Delete a selection profile as described in Delete a Selection Profile from Deployment Workbench. click New Selection Profile. click the Selection Profiles node. Point to Microsoft Deployment Toolkit.147 Microsoft Deployment Toolkit 2010 Update 1 Selection profile Description Packages and Task Sequences nodes in the Deployment Workbench. Move a selection profile as described in Move a Selection Profile in Deployment Workbench. Then. In the Deployment Workbench console tree. This selection profile includes all operating system packages and task sequences. Manage selection profiles by completing the following tasks in the Deployment Workbench: • • • • • • • Create a new selection profile as described in Create a New Selection Profile in Deployment Workbench. and then click Deployment Workbench. Modify an existing selection profile as described in Modify an Existing Selection Profile in Deployment Workbench. right-click the Selection Profiles node. click the Selection Profiles node. In the console tree.

Click Next. In Select the folders that should be included in this selection profile. and then point to All Programs.com/technet/SolutionAccelerators . 3. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Point to Microsoft Deployment Toolkit.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 148 3. type comment (where comment is descriptive text that provides information about the selection profile). In Selection profile name. However. The selection profile is added to the list of selection profiles in the details pane of the Deployment Workbench. click New Selection Profile. The New Selection Profile Wizard finishes. you can update the selection profile properties on the General tab of the profile_name Properties dialog box (where profile_name is the name of the selection profile in the Deployment Workbench). type profile_name (where profile_name is the name of the new profile). Folders Summary Confirmation Click Finish. and then click Deployment Workbench. Information for Completing the New Selection Profile Wizard On this wizard page General Settings Do this 1. and then click Next. Review in the information in Details. Click Start. select folders (where folders is the name of the folders that contain the Deployment Workbench items you want to include in this selection profile). Modify an Existing Selection Profile in Deployment Workbench Modify existing selection profiles in the Deployment Workbench’s Selection Profiles node using the Properties actions as described in View Item Properties in Deployment Workbench. Solution Accelerators microsoft. Table 66. and then click Next. In Selection profile comments. Complete the New Selection Profile Wizard using the information in Table 66. The New Selection Profile Wizard starts. In the Actions pane. Tip You can click Save Output to save the output of the wizard to a file. To configure the General tab for package properties 1. 2. The selection profile properties are mostly configured when you run the New Selection Profile Wizard. 4.

In the Deployment Workbench console tree. In the details pane. In the Actions pane. Comments Folders The selection profile configuration settings are saved. Table 67. On the General tab. and then click OK. Configuration Settings on the General Tab of Package Properties Setting Name Description Contains the name of the selection displayed in the Deployment Workbench and the Windows Deployment Wizard. and the depoyment_share\Control\SelectionProfiles. 3. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Selection Profiles (where deployment_share is the name of the deployment share where you will configure the package). 4. 5. Copy a Selection Profile in Deployment Workbench You can copy and paste selection profiles in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench. configure the settings listed in Table 67 based on the requirements of your organization. Rename a Selection Profile in Deployment Workbench You can rename selection profiles in the Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench. click Properties. Provides information about the selection profile.com/technet/SolutionAccelerators . click profile_name (where profile_name is the name of the selection profile you want to configure). the modifications are displayed in the details pane of the Deployment Workbench. Move a Selection Profile in Deployment Workbench You can move selection profiles in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench.xml file (where deployment_share is the name of the deployment share) is updated with the selection profile configuration settings. Solution Accelerators microsoft.149 Microsoft Deployment Toolkit 2010 Update 1 2. The profile_name Properties dialog box opens (where profile_name is the name of the selection profile you want to configure). Hierarchical list of the folders and their selection status.

xml For example.xml OperatingSystemGroups. The contents of this file are similar to how groups were stored in MDT 2008 Update 1.xml.xml SelectionProfileGroups. including: • • • • • • • • ApplicationGroups.xml TaskSequenceGroups. The relationship between items and folders in a selection profile is stored in the following files in the deployment_share\Control folder (where deployment_share is the location of the deployment share): • itemGroups.xml LinkedDeploymentShareGroups. There is a separate file for each type of item.xml file generated when you created the selection profile: <groups> … <group_quid="{e5143c1c-24e4-466d-9b56-b0db693c8619} " enable="True"> <Name>WinPEAndFullOS</Name> … <Member>{1eca45a5-d7ef-475a-bb0d7f7747f16b3a}</Member> • SelectionProfiles. and other tasks. consider a selection profile for device drivers called WinPEAndFullOS that are stored in a folder created immediately beneath the Out-of-Box Drivers node. The Delete Selected Items Wizard allows you to delete individual selection profiles.xml MediaGroups. The following code is an excerpt from the DriverGroups. such as operating systems. Identify the Relationship Between Selection Profiles and Groups Use selection profiles to create groups of Deployment Workbench items.xml. define content to include in a linked deployment share. define the content to include for media deployments. or applications.xml DriverGroups. The following code is an excerpt Solution Accelerators microsoft. device drivers. This file contains the definitions for all the selection profiles defined for the deployment share.xml PackageGroups.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Managing LTI Deployments 150 Delete a Selection Profile from Deployment Workbench You can delete a selection profile in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. Use the selection profiles to specify device drivers.

Because of the introduction of folders in MDT 2010.” in the MDT 2010 document.xml file generated when you created the WinPEAndFullOS selection profile: <selectionProfile quid="{46a3e6a2-694c-4c2f-afd8a2986e6e252e}" enable="True"> <Name>Drivers Safe For WinPE</Name> <Comments>Include Driver packages safe for WinPE. For more information on this property.</Definition> </selectionProfile> By default. A selection profile determines the items to be linked. you can choose whether to merge or replace content in the target deployment share./SelectionProfile&gt.&lt. see the section. regardless of what you specify in the selection profile. For example. Toolkit Reference. “CustomxxxSelectionProfile. is empty). The reverse is true if you want to use a group. If you specify both selection profiles and groups in the CustomSettings. In this way. you can use selection profiles and groups to perform most deployments. you can make changes to one deployment share. For more information on this property. because the default group includes all items.” in the MDT 2010 document.&lt. LTI uses all items. “NoSubFoldersForGroups.com/technet/SolutionAccelerators . In most instances. if you do not specify a selection profile or group in the CustomSettings. When creating the link between the deployment shares. Manage Linked Deployment Shares Linked deployment shares in MDT 2010 allow you to provide a logical connection between two deployment shares: a source and a target deployment share. and then easily update other deployment shares based on the selection profiles you chose when creating the linked deployment shares.Include path="Out-of-Box Drivers\WinPEAndFullOS" /&gt. LTI uses all the items from both the selection profile and the group.&lt. groups include all folders and subfolders by default. To restrict the items to a selection profile. see the section. You can override this behavior using the NoSubFoldersForGroups property.</Comments> <ReadOnly>True</ReadOnly> <Definition>&lt.ini file or in the MDT DB.Include path="Out-of-Box Drivers\WinPEOnly" /&gt.ini file or the MDT DB. Using linked deployment shares. specify a group that contains no items (that is. However.SelectionProfile&gt. if you specify a selection profile and use the default group (which includes all items). Toolkit Reference. the end result is that LTI uses all items. Solution Accelerators microsoft. the CustomxxxSelectionProfile property is available for more advanced scenarios—such as if you want to exclude a parent folder but include a child folder.151 Microsoft Deployment Toolkit 2010 Update 1 from the SelectionProfile. you can easily replicate an entire deployment share or portions of a deployment share to another deployment share.

Start the New Linked Deployment Share Wizard using one of the following methods: • • • In the console tree. click New Linked Deployment Share. click New Linked Deployment Share. and then click Deployment Workbench. Then. In the console tree. To create a new linked deployment share 1. and then point to All Programs. Modify an existing linked deployment share as described in Modify an Existing Linked Deployment Share in Deployment Workbench. The New Linked Deployment Share Wizard starts. Move a linked deployment share as described in Move a Linked Deployment Share in Deployment Workbench. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Linked Deployment Share (where deployment_share is the name of the deployment share you want to configure).Using the Microsoft Deployment Toolkit: Managing LTI Deployments 152 Manage linked deployment shares by performing the following tasks in the Deployment Workbench: • • • • • • • Create a new linked deployment share as described in Create a New Linked Deployment Share in Deployment Workbench. click the Linked Deployment Share node. from the Action menu. Replicate linked deployment shares as described in Replicate Linked Deployment Shares in Deployment Workbench. Solution Accelerators microsoft. In the Deployment Workbench console tree. Complete the New Linked Deployment Share Wizard using the information in Table 68. Create a New Linked Deployment Share in Deployment Workbench Create new linked deployment shares in the Deployment Workbench using the New Linked Deployment Share Wizard. and then click New Linked Deployment Share. Delete a linked deployment share as described in Delete a Linked Deployment Share from Deployment Workbench. 3. Copy a linked deployment share as described in Copy a Linked Deployment Share in Deployment Workbench. In the console tree. in the Actions pane. 4. click New Linked Deployment Share.com/technet/SolutionAccelerators . Click Start. Point to Microsoft Deployment Toolkit. right-click the Linked Deployment Share node. 2. Rename a linked deployment share as described in Rename a Linked Deployment Share in Deployment Workbench. click the Linked Deployment Share node. Then. In the Actions pane.

USMT. including the Scripts. Tip You can click Save Output to save the output of the microsoft.com/technet/SolutionAccelerators . 2. and then click Next. Under Selection profile. 3. Note You can alternatively click Browse to find the network shared folder. and $OEM$ folders. Information for Completing the New Linked Deployment Share Wizard On this wizard page General Settings Do this 1. Selecting this option also copies the standard folders from the source deployment share. 5. type comment (where comment is descriptive text that provides information about the linked deployment share). • Replace the contents of the target deployment share folders with those selected. In Selection profile. and $OEM$ folders. 4. In Comments. By default. Summary Confirmation Solution Accelerators Review in the information in Details. Select to configure the wizard to copy the content in the selection profile into an existing target deployment share without deleting or overwriting any folders or items in the target deployment share. Tools. In Linked deployment share UNC path. USMT. Select to configure the wizard to copy the content in the selection profile into an existing target deployment share and overwrite any existing folders or items in the target deployment share. Tools. the Merge the selected content into the target deployment share option is selected. type unc_path (where unc_path is the fully qualified UNC path to the target deployment share). click profile (where profile is the name of the selection profile that will be used to establish the items to be linked between the source and target deployment shares). including the Scripts. click one of the following options based on your requirements: • Merge the selected content into the target deployment share. Selecting this option also copies the standard folders from the source deployment share. Click Next.153 Microsoft Deployment Toolkit 2010 Update 1 Table 68.

Using the Microsoft Deployment Toolkit: Managing LTI Deployments 154 On this wizard page Do this wizard to a file. In the details pane. The linked_deployment_share Properties dialog box opens (where linked_deployment_share is the name of the selection profile you want to configure). click linked_deployment_share (where linked_deployment_share is the name of the linked deployment share you want to configure). configure the settings listed in Table 69 based on the requirements of your organization. and then point to All Programs. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Point to Microsoft Deployment Toolkit. and then click OK. 3. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Linked Deployment Share (where deployment_share is the name of the deployment share in which you will configure the package). Table 69. Click Start. and then click Deployment Workbench. 5. On the General tab. Configuration Settings on the General Tab of Linked Deployment Share Properties Setting Link identifier Solution Accelerators Description Contains the identifier of the linked deployment microsoft. you can update the linked deployment share properties on the General tab of the linked_deployment_share Properties dialog box (where linked_deployment_share is the name of the linked deployment share in the Deployment Workbench). Click Finish. In the Actions pane. However. and the linked deployment share is added to the list of linked deployments shares in the details pane of the Deployment Workbench. 2. Modify an Existing Linked Deployment Share in Deployment Workbench Modify existing linked deployment share in the Deployment Workbench’s Linked Deployment Shares node using the Properties actions as described in View Item Properties in Deployment Workbench. The linked deployment share properties are configured when you run the New Linked Deployment Share Wizard. click Properties. The New Linked Deployment Share Wizard finishes. In the Deployment Workbench console tree.com/technet/SolutionAccelerators . 4. To modify an existing linked deployment share 1.

Click to configure the wizard to copy the content in the selection profile into an existing target deployment share and overwrite any existing folders or items in the target deployment share. If this check box is: • Selected. including the Scripts. This check box is cleared by default. If this check box is: • Selected. including the Scripts. • Cleared. Contains the selection profile that identifies the content to be replicated between the source and target deployment shares. Tools. USMT. Comments Linked deployment share UNC path Choose a selection profile Merge the selected content into the target deployment share Provides information about the linked deployment share. $OEM$) to this linked deployment share Automatically update boot images after replicating content to this linked deployment share Solution Accelerators . the standard folders are copied to the linked deployment share. Click to configure the wizard to copy the content in the selection profile into an existing target deployment share without deleting or overwriting any folders or items in the target deployment share. Note The identifier in this text box is automatically generated by the Deployment Workbench and cannot be modified. Tools. Selecting this option also copies the standard folders from the source deployment share. Contains the fully qualified UNC path to the target deployment share. and $OEM$ folders. USMT. USMT.com/technet/SolutionAccelerators Replace the contents of the target deployment share folders with those selected Copy standard folders (Scripts.155 Microsoft Deployment Toolkit 2010 Update 1 Setting Description share. Selecting this option also copies the standard folders from the source deployment share. Tools. the standard folders are not copied to the linked deployment share. Select to configure the Replicate to Linked Deployment Share Wizard to share. and $OEM$ folders. Select to configure the Replicate to Linked Deployment Share Wizard to automatically update any boot images in the linked deployment share after the content is replicated from the source deployment share. the boot images in the linked deployment share are automatically updated microsoft.

Using the Microsoft Deployment Toolkit: Managing LTI Deployments 156 Setting Description when replication is complete. This check box is cleared by default. • Cleared. changes that other users make in the linked deployment share may be overwritten and lost during the replication process. • Cleared. Move a Linked Deployment Share in Deployment Workbench You can move linked deployment shares in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench. the linked deployment share is opened in single-user mode as replication is performed and replication performance is improved. The modifications are displayed in the details pane in the Deployment Workbench. Solution Accelerators microsoft. the linked deployment share is not opened in single-user mode as replication is performed and replication performance is unimproved. the linked deployment share is configured to generate 32-bit and 64-bit boot images. If this check box is: • Selected. Access the linked deployment share in single-user mode in order to improve replication performance Select to configure the Replicate to Linked Deployment Share Wizard to open the linked deployment share in single-user mode while replicating the content to the linked deployment share.com/technet/SolutionAccelerators . Open the linked deployment share in the Deployment Workbench to change this default behavior as described in Open an Existing Deployment Share in Deployment Workbench. Note By default. This check box is cleared by default. Single-user mode improves replication performance. Note If you select this check box. The linked deployment share configuration settings are saved. the boot images in the linked deployment share are not automatically updated when replication is complete. Copy a Linked Deployment Share in Deployment Workbench You can copy and paste linked deployment shares in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench.

4. Table 70. In the Actions pane. The Replicate to Linked Deployment Share Wizard starts. The replication process starts automatically and is displayed on the Progress wizard page. Tip You can click Save Output to save the output of the microsoft. Complete the Replicate to Linked Deployment Share Wizard using the information in Table 70.com/technet/SolutionAccelerators . 3. Note By default. To replicate content to a linked deployment share 1. In the details pane. Ensure that sufficient storage exists for the linked deployment share prior to running the Replicate to Linked Deployments Share Wizard. Delete a Linked Deployment Share from Deployment Workbench You can delete a linked deployment shares in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual linked deployment shares. Replicate Linked Deployment Shares in Deployment Workbench You can replicate the content from the source deployment share to the linked deployment shares in the Deployment Workbench using the Replicate to Linked Deployments Share Wizard. 2. Point to Microsoft Deployment Toolkit.157 Microsoft Deployment Toolkit 2010 Update 1 Rename a Linked Deployment Share in Deployment Workbench You can rename linked deployment shares in the Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench. Open the linked deployment share in the Deployment Workbench to change this default behavior as described in Open an Existing Deployment Share in Deployment Workbench. 5. and then point to All Programs. and then click Deployment Workbench. click linked_deployment_share (where linked_deployment_share is the name of the linked deployment share you want to configure). Information for Completing the Replicate to Linked Deployment Share Wizard On this wizard page Progress Confirmation Solution Accelerators Do this View the progress of the replication process. Click Start. In the Deployment Workbench console tree. click Replicate Content. the linked deployment share is configured to generate 32-bit and 64-bit boot images. as the wizard does not verify that sufficient storage exists prior to replicating the content. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Linked Deployment Share (where deployment_share is the name of the deployment share where you will add the application).

Rename media as described in Rename Media in Deployment Workbench. You can store the media on a DVD. without connecting to a deployment share.com/technet/SolutionAccelerators Solution Accelerators .Using the Microsoft Deployment Toolkit: Managing LTI Deployments 158 On this wizard page Do this wizard to a file. as well. or other portable device. When Windows PE starts. The Replicate to Linked Deployments Share wizard finishes. the replication is actually performed in two passes: The first pass copies new items into the linked deployment share. Copy media as described in Copy Media in Deployment Workbench. generate bootable WIM images that allow the deployment to be performed from portable media devices locally available on the target computer. the replication appears to have occurred twice. Manage deployment media by performing the following tasks in the Deployment Workbench: • • • • • • • • Create new deployment media as described in Create New Deployment Media in Deployment Workbench. You determine the items to be included on the media in a selection profile you specify when you create the media. Modify existing media as described in Modify Existing Media in Deployment Workbench. However. and the second pass deletes any items that are no longer needed in the linked deployment share. The Deployment Workbench automatically includes Windows PE in the media WIM image so that Windows PE is started from the media available to the target computer. Manage MDT 2010 Deployment Media Media in MDT 2010 allow you to perform LTI deployments solely from local media. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Generate media images as described in Generate Media Images in Deployment Workbench. Create bootable devices from deployment media as described in Create Bootable Devices from Deployment Media. Click Finish. After you create the media. USB hard disk. The folders and the content you specified in the selection profile in the linked deployment share are replicated from the source deployment share to the target deployment share. Delete media as described in Delete Media from Deployment Workbench. Depending on the configuration of the linked deployment share. the folders and content on the target deployment share are merged or replaced. the Windows Deployment Wizard is automatically started. Move media as described in Move Media in Deployment Workbench. microsoft. Note If you view the output of the wizard.

right-click the Media node. type media_path (where media_path is the fully qualified path to an empty local or network shared folder that is the source folder for creating the media). 2. Then. click New Media. 3. In the Actions pane. click New Media. 4. click the Media node. Start the New Media Wizard using one of the following methods: • • • In the console tree. Click Next. 2. In the console tree. Summary Confirmation Review in the information in Details. In the Deployment Workbench console tree. Point to Microsoft Deployment Toolkit.com/technet/SolutionAccelerators Solution Accelerators . Note You can alternatively click Browse to find the folder on a local drive or network shared folder. and then click Deployment Workbench. Tip You can click Save Output to save the output of the wizard to a file. type comment (where comment is descriptive text that provides information about the media). click the Media node. in the Actions pane. and then click New Media. Then. In the console tree. 3. click profile (where profile is the name of the selection profile that will be used to establish the items to be stored on the media). The New Media Wizard starts. and then point to All Programs. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share to which you will add the application). To create new deployment media 1. Table 71. click New Media. In Media path. Click Start. In Comments. and then click Next. In Selection profile. Information for Completing the New Media Wizard On this wizard page General Settings Do this 1. from the Action menu. Complete the New Media Wizard using the information in Table 71. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard microsoft. 4.159 Microsoft Deployment Toolkit 2010 Update 1 Create New Deployment Media in Deployment Workbench Create new deployment media in the Deployment Workbench using the New Media Wizard.

Click Finish. The media are added to the list of media in the details pane of the Deployment Workbench. and some base folders are created.com/technet/SolutionAccelerators . Point to Microsoft Deployment Toolkit. To modify existing media properties on the General tab 1. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Solution Accelerators microsoft. However. Configure media in the Deployment Workbench by performing the following steps in the media Properties dialog box: • • • • Configure properties on the General tab as described in Configure the Media Properties General Tab. In the Deployment Workbench console tree. Configure the settings on the Windows PE x64 Settings tab as described in Configure the Media Properties Windows PE x64 Settings Tab.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 160 On this wizard page Do this tasks. you can update the linked deployment share properties on the General tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). and then point to All Programs. The folders and content you specified in the selection profile are copied to the Deploy folder when the Update Media Content Wizard runs. 2. The media_path\Content\Deploy folder is created (where media_path is the name of the media path you specified in the wizard). Configure the settings on the Windows PE x64 Components tab as described in Configure the Media Properties Windows PE x64 Components Tab. The New Media Wizard finishes. Configure the settings on the Windows PE x86 Components tab as described in Configure the Media Properties Windows PE x86 Components Tab. Configure properties on the Rules tab as described in Configure the Media Properties Rules Tab. Configure the settings on the Windows PE x86 Settings tab as described in Configure the Media Properties Windows PE x86 Settings Tab. Modify Existing Media in Deployment Workbench Modify existing media in the Media node in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. Click Start. and then click Deployment Workbench. • • Configure the Media Properties General Tab The media properties on the General tab are configured when you run the New Media Wizard.

Note The identifier in this text box is automatically generated by the Deployment Workbench and cannot be modified.161 Microsoft Deployment Toolkit 2010 Update 1 Configuration/Media (where deployment_share is the name of the deployment share in which you will configure the media). a menu appears from which you can specify which boot image to use. In the details pane. When started. Note Selecting both the x86 and x64 check boxes generates a dual-boot ISO file. Contains the selection profile that identifies the content to be included in the WIM and ISO image files that the Deployment Workbench generates. The ISO file is created in microsoft. Note Selecting both the x86 and x64 check boxes generates a dual-boot ISO file. Configuration Settings on the General Tab of Media Properties Setting Media identifier Description Contains the identifier of the media. Select to configure the Update Media Content Wizard to create WIM files and bootable media for 32-bit target computers. In the Actions pane. Comments Media path Provides information about the media. When started. 3. Generate a Lite Touch bootable ISO image Select to configure the Update Media Content Wizard to create ISO files that you can use to boot VMs or create bootable DVDs. a menu appears from which you can specify which boot image to use. Table 72. On the General tab. then you can specify the name of the ISO file to be generated in the ISO file name text box.com/technet/SolutionAccelerators Solution Accelerators . Selection profile Platforms supported: x86 Platforms supported: x64 Select to configure the Update Media Content Wizard to create WIM files and bootable media for 64-bit target computers. click media (where media is the name of the media you want to configure). 4. 5. The media Properties dialog box opens (where media is the name of the media you want to configure). configure the settings listed in Table 72 based on the requirements of your organization. click Properties. If this check box is selected. and then click OK. Contains the fully qualified UNC path to the target folder for the media source files and generated images.

The media configuration settings are saved. Point to Microsoft Deployment Toolkit. click media (where media is the name of the media you want to configure).Using the Microsoft Deployment Toolkit: Managing LTI Deployments 162 Setting Description the media_folder folder (where media_folder is the name of the folder that you specified for the media).ini Description Contains the current configuration of the CustomSetting. click Properties. 2. and the content in the media_folder folder (where media_folder is the name of the folder that you specified for the media) is updated.ini file for the deployment media Click to modify the contents of the Bootstrap. and then point to All Programs. Solution Accelerators microsoft. The media Properties dialog box opens (where media is the name of the media you want to configure). configure the settings listed in Table 73 based on the requirements of your organization. and the content in the media_folder folder is updated (where media_folder is the name of the folder that you specified for the media). In the details pane. However. Table 73. 5. In the Actions pane. To modify existing media properties on the Rules tab 1. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share in which you will configure the media). 3. 4. On the Rules tab.com/technet/SolutionAccelerators . and then click Deployment Workbench.ini Edit Bootstrap. In the Deployment Workbench console tree. The modifications are displayed in the details pane of the Deployment Workbench. and then click OK. Click Start. you can update the linked deployment share properties on the Rules tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). The modifications are displayed in the details pane of the Deployment Workbench.ini file that the Deployment Workbench generates for the deployment media The media configuration settings are saved. Configure the Media Properties Rules Tab The media properties on the Rules tab are configured when you run the New Media Wizard. Configuration Settings on the Rules Tab of Media Properties Setting CustomSettings.

163

Microsoft Deployment Toolkit 2010 Update 1

Configure the Media Properties Windows PE x86 Settings Tab The media properties on the Windows PE x86 Settings tab are configured when you run the New Media Wizard. However, you can update the linked deployment share properties on the Windows PE x86 tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). To configure the Windows PE x86 Settings tab 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share in which you will configure the media). 3. In the details pane, click media (where media is the name of the media you want to configure). 4. In the Actions pane, click Properties. The media Properties dialog box opens (where media is the name of the media you want to configure). 5. On the Windows PE x86 Settings tab, configure the settings listed in Table 74 based on the requirements of your organization, and then click OK. Table 74. Configuration Settings on the Windows PE x86 Settings Tab of Media Properties Setting Generate a Lite Touch Windows PE WIM file Description Select to configure the Update Media Content Wizard to create a Windows PE WIM file that includes the LTI deployment scripts. If the check box is: • Selected, the Update Media Content Wizard creates the LiteTouchPE_x86.wim file with the image description specified in the Image description text box. • Cleared, the Update Media Content Wizard will not create the WIM file. Contains the image description for the Windows PE WIM file that the Update Media Content Wizard creates. The default value is Lite Touch Windows PE (x86). Select to configure the Update Media Content Wizard to create a bootable Windows PE ISO file that includes the LTI deployment scripts. If the check box is:
microsoft.com/technet/SolutionAccelerators

Image description

Generate a Lite Touch bootable ISO image

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

164

Setting

Description • Selected, the Update Media Content Wizard creates the ISO file with the name specified in the ISO file name text box. • Cleared, the Update Media Content Wizard will not create the ISO file.

ISO file name

Contains the file name for the Windows PE ISO file that the Update Media Content Wizard creates. The default value for this text box is LiteTouchPE_x86.iso.
Note This text box is enabled only if you select Generate a Lite Touch bootable ISO image.

Generate a generic Select to configure the Update Media Content Windows PE WIM file Wizard to create a Windows PE WIM file that does not include the LTI deployment scripts. If the check box is: • Selected, the Update Media Content Wizard creates the GenericPE_x86.wim file with the image description specified in the Image description text box. • Cleared, the Update Media Content Wizard will not create the WIM file. Image description Contains the image description for the generic Windows PE WIM file that the Update Media Content Wizard creates. The default value for this text box is Generic Windows PE (x86).
Note This text box is enabled only if you select Generate a generic Windows PE WIM file.

Generate a generic bootable ISO image

Select to configure the Update Media Content Wizard to create a bootable Windows PE ISO file that does not include the LTI deployment scripts. If the check box is: • Selected, the Update Media Content Wizard creates the Generic_x86.iso file with the image description specified in the ISO file name text box. • Cleared, the Update Media Content Wizard will not create the ISO file.
Note This box is enabled only if you select Generate a generic Windows PE WIM file.

ISO file name

Contains the file name for the generic Windows PE ISO file that the Update Media Content Wizard creates. The default value for this
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

165

Microsoft Deployment Toolkit 2010 Update 1

Setting

Description text box is Generic_x86.iso.
Note This text box is enabled only if you select Generate a generic bootable ISO image.

Custom background bitmap file

Contains the fully qualified path to the BMP file that is to be used as the custom background bitmap. The default value for this text box is %INSTALLDIR%\Samples\Background.bmp. Contains the fully qualified path to a folder structure to be included in the Windows PE images. The default value for the text box is empty. Configures the size of the scratch space in megabytes; you can select a value of 32, 64, 128, 256, or 512 MB. The default value is 32.

Extra directories to add

Scratch space size

The media configuration settings are saved, and the media appears in the details pane of the Deployment Workbench. Configure the Media Properties Windows PE x86 Components Tab The media properties on the Windows PE x86 Components tab are configured when you run the New Media Wizard. However, you can update the linked deployment share properties on the Windows PE x86 Components tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). To configure the Windows PE x86 Components tab 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share in which you will configure the media). 3. In the details pane, click media (where media is the name of the media you want to configure). 4. In the Actions pane, click Properties. The media Properties dialog box opens (where media is the name of the media you want to configure). 5. On the Windows PE x86 Components tab, configure the settings listed in Table 75 based on the requirements of your organization, and then click OK. Table 75. Configuration Settings on the Windows PE x86 Components Tab of Media Properties
Solution Accelerators microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

166

Setting ADO

Description Select to add optional ADO components to the Windows PE images. These components are necessary for accessing SQL Server databases, such as the MDT DB. If the check box is: • Selected, the ADO components are added to the Windows PE images. • Cleared, the ADO components are not added to the Windows PE images. Select to configure the Update Media Content Wizard to include the following fonts: • Chinese (ZH-CN) • Chinese (ZH-HK) • Chinese (ZH-TW) • Japanese (JA-JP) • Korean (KO-KR) Add these fonts when performing an LTI deployment of Windows Server 2008 images and the Setup files are Japanese, Korean, or Chinese. If the check box for a corresponding font is: • Selected, the Update Media Content Wizard includes the font in the Windows PE images. • Cleared, the Update Media Content Wizard will not include the font in the Windows PE images.
Note Adding fonts to Windows PE boot images increases the size of the images. Add fonts only if necessary.

Optional Fonts

Selection profile

Use to select the device drivers and packages to be included in the Windows PE images based on the selection profile you choose. The default value is All Drivers and Packages. For more information about selection profiles, see Manage Selection Profiles. Select to configure the Update Media Content Wizard to include all the device drivers in the selection profile specified in the Selection profile box.

Include all drivers from the selected driver group

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

167

Microsoft Deployment Toolkit 2010 Update 1

Setting Include only drivers of the following types

Description Select to configure the Update Media Content Wizard to include only the device drivers in the chosen selection profile that are specified in the following check boxes: • Include all network drivers in the selected group • Include all video drivers in the selected group • Include all mass storage drivers in the selected group • Include all system-class drivers in the selected group Select to configure the Update Media Content Wizard to include all network drivers in the chosen selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all network drivers in the selection profile specified in the Selection profile box in the Windows PE images.
Note This check box is enabled only if you select Include only drivers of the following types.

Include all network drivers in the selected group

Include all video drivers in the selected group

Select to configure the Update Media Content Wizard to include all video drivers in the chosen selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all video drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all video drivers in the selection profile specified in the Selection profile list box in the Windows PE images.
Note This check box is enabled only if you select Include only drivers of the following types.

Include all mass storage drivers in the selected group

Select to configure the Update Media Content Wizard to include all mass storage drivers in chosen the selection profile. If the check box is: • Selected, the Update Media Content Wizard
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

168

Setting

Description includes all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images.
Note This check box is enabled only if you select Include only drivers of the following types.

Include all systemclass drivers in the selected group

Select to configure the Update Media Content Wizard to include all system-class drivers in the chosen selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images.
Note This check box is enabled only if you select Include only drivers of the following types.

The media configuration settings are saved, and the media appears in the details pane of the Deployment Workbench. Configure the Media Properties Windows PE x64 Settings Tab The media properties on the Windows PE x64 Settings tab are configured when you run the New Media Wizard. However, you can update the linked deployment share properties on the Windows PE x64 Settings tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). To configure the Windows PE x64 Settings tab 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share in which you will configure the media). 3. In the details pane, click media (where media is the name of the media you want to configure).
Solution Accelerators microsoft.com/technet/SolutionAccelerators

169

Microsoft Deployment Toolkit 2010 Update 1

4. In the Actions pane, click Properties. The media Properties dialog box opens (where media is the name of the media you want to configure). 5. On the Windows PE x64 Settings tab, configure the settings listed in Table 76 based on the requirements of your organization, and then click OK. Table 76. Configuration Settings on the Windows PE x64 Settings Tab of Media Properties Setting Generate a Lite Touch Windows PE WIM file Description Select to configure the Update Media Content Wizard to create a Windows PE WIM file that includes the LTI deployment scripts. If the check box is: • Selected, the Update Media Content Wizard creates the LiteTouchPE_x86.wim file with the image description specified in the Image description box. • Cleared, the Update Media Content Wizard will not create the WIM file. Contains the image description for the Windows PE WIM file that the Update Media Content Wizard creates. The default value is Lite Touch Windows PE (x64). Select to configure the Update Media Content Wizard to create a bootable Windows PE ISO file that includes the LTI deployment scripts. If the check box is: • Selected, the Update Media Content Wizard creates the ISO file with the name specified in the ISO file name box. • Cleared, the Update Media Content Wizard will not create the ISO file. Contains the file name for the Windows PE ISO file that the Update Media Content Wizard creates. The default value for this text box is LiteTouchPE_x64.iso.
Note This box is enabled only if you select Generate a Lite Touch bootable ISO image.

Image description

Generate a Lite Touch bootable ISO image

ISO file name

Generate a generic Select to configure the Update Media Content Windows PE WIM file Wizard to create a Windows PE WIM file that does not include the LTI deployment scripts. If the check box is: • Selected, the Update Media Content Wizard
Solution Accelerators microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

170

Setting

Description creates the GenericPE_x64.wim file with the image description specified in the Image description box. • Cleared, the Update Media Content Wizard will not create the WIM file.

Image description

Contains the image description for the generic Windows PE WIM file that the Update Media Content Wizard creates. The default value for this text box is Generic Windows PE (x64).
Note This box is enabled only if you select Generate a generic bootable ISO Windows PE WIM file.

Generate a generic bootable ISO image

Select to configure the Update Media Content Wizard to create a bootable Windows PE ISO file that does not include the LTI deployments scripts. If the check box is: • Selected, the Update Media Content Wizard creates the Generic_x64.iso file with the image description specified in the ISO file name box. • Cleared, the Update Media Content Wizard will not create the ISO file.
Note This box is enabled only if you select Generate a generic Windows PE WIM file.

ISO file name

Contains the file name for the generic Windows PE ISO file that the Update Media Content Wizard creates. The default value for this text box is Generic_x64.iso.
Note This text box is enabled only if the Generate a generic bootable ISO image check box is selected.

Custom background bitmap file

Contains the fully qualified path to the BMP file that is to be used as the custom background bitmap. The default value for this text box is %INSTALLDIR%\Samples\Background.bmp. Contains the fully qualified path to a folder structure to be included in the Windows PE images. The default value for the text box is empty. Configures the size of the scratch space in megabytes; you can select a value of 32, 64, 128, 256, or 512 MB. The default value is 32.

Extra directories to add

Scratch space size

The media configuration settings are saved, and the media appears in the details pane of the Deployment Workbench.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

171

Microsoft Deployment Toolkit 2010 Update 1

Configure the Media Properties Windows PE x64 Components Tab The media properties on the Windows PE x64 Components tab are configured when you run the New Media Wizard. However, you can update the linked deployment share properties on the Windows PE x64 Components tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). To configure the Windows PE x64 Components tab 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share in which you will configure the media). 3. In the details pane, click media (where media is the name of the media you want to configure). 4. In the Actions pane, click Properties. The media Properties dialog box opens (where media is the name of the media you want to configure). 5. On the Windows PE x86 Components tab, configure the settings listed in Table 77 based on the requirements of your organization, and then click OK. Table 77. Configuration Settings on the Windows PE x64 Components Tab of Media Properties Setting ADO Description Select to add the optional ADO components to the Windows PE images. These components are necessary for accessing SQL Server databases, such as the MDT DB. If this check box is: • Selected, the ADO components are added to the Windows PE images. • Cleared, the ADO components are not added to the Windows PE images. Use to configure the Update Media Content Wizard to include the following fonts: • Chinese (ZH-CN) • Chinese (ZH-HK) • Chinese (ZH-TW) • Japanese (JA-JP) • Korean (KO-KR) Add these fonts when performing an LTI
microsoft.com/technet/SolutionAccelerators

Optional Fonts

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

172

Setting

Description deployment of Windows Server 2008 images when the Setup files are Japanese, Korean, or Chinese. If the check box for a corresponding font is: • Selected, the Update Media Content Wizard includes the font in the Windows PE images. • Cleared, the Update Media Content Wizard will not include the font in the Windows PE images.
Note Adding fonts to Windows PE boot images increases the size of the images. Add fonts only if necessary.

Selection profile

Selects the device drivers and packages to be included in the Windows PE images based on the selection profile you choose. The default value is All Drivers and Packages. For more information about selection profiles, see Manage Selection Profiles. Select to configure the Update Media Content Wizard to include all the device drivers in the selection profile specified in the Selection profile box. Select to configure the Update Media Content Wizard to include only the device drivers in the chosen selection profile that are specified in the following check boxes: • Include all network drivers in the selected group • Include all video drivers in the selected group • Include all mass storage drivers in the selected group • Include all system-class drivers in the selected group Select to configure the Update Media Content Wizard to include all network drivers in the chosen selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all network drivers in the selection profile specified in the Selection profile box in
microsoft.com/technet/SolutionAccelerators

Include all drivers from the selected driver group Include only drivers of the following types

Include all network drivers in the selected group

Solution Accelerators

173

Microsoft Deployment Toolkit 2010 Update 1

Setting

Description the Windows PE images.
Note This check box is enabled only if you select Include only drivers of the following types.

Include all video drivers in the selected group

Select to configure the Update Media Content Wizard to include all video drivers in the chosen selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all video drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all video drivers in the selection profile specified in the Selection profile box in the Windows PE images.
Note This check box is enabled only if you select include only drivers of the following types.

Include all mass storage drivers in the selected group

Select to configure the Update Media Content Wizard to include all mass storage drivers in the chosen selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all mass storage drivers in the selection profile specified in the Selection profile box in the Windows PE images.
Note This check box is enabled only if you select include only drivers of the following types.

Include all systemclass drivers in the selected group

Select to configure the Update Media Content Wizard to include all system-class drivers in chosen the selection profile. If the check box is: • Selected, the Update Media Content Wizard includes all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images. • Cleared, the Update Media Content Wizard will not include all system-class drivers in the selection profile specified in the Selection profile box in the Windows PE images.
Note This check box is enabled only if you select Include only drivers of the following types.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

174

The media configuration settings are saved, and the media appears in the details pane of the Deployment Workbench.

Copy Media in Deployment Workbench
You can copy and paste media in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in Deployment Workbench.

Move Media in Deployment Workbench
You can move media in the Deployment Workbench using the Cut and Paste actions as described in Move Items in Deployment Workbench.

Rename Media in Deployment Workbench
You can rename media in the Deployment Workbench using the Rename action as described in Rename Items in Deployment Workbench.

Delete Media from Deployment Workbench
You can delete media in the Deployment Workbench using the Delete Selected Items Wizard as described in Delete Items from Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual media.

Generate Media Images in Deployment Workbench
You can generate media images of the media content in the Deployment Workbench using the Update Media Content Wizard. The Update Media Content Wizard creates WIM file images of the media content that you can use to perform stand-alone LTI deployments from media. Ensure that sufficient storage exists for the folder containing the media content prior to running the Update Media Content Wizard, as the wizard does not verify that sufficient storage exists prior to generating the media content.
Note The Update Media Content Wizard opens the media path in single-user mode, which assumes that no other users are simultaneously making updates to the files and folders in the media path. If other users make changes while the Update Media Content Wizard runs, those changes may be overwritten and lost during the generation process.

To generate media images of media content 1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench. 2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Media (where deployment_share is the name of the deployment share to which you will add the application). 3. In the details pane, click media (where media is the name of the media for which you want to generate the media). 4. In the Actions pane, click Update Media Content.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

175

Microsoft Deployment Toolkit 2010 Update 1

The Update Media Content Wizard starts. The replication process starts automatically and is displayed on the Progress wizard page. 5. Complete the Update Media Content Wizard using the information in Table 78. Table 78. Information for Completing the Update Media Content Wizard On this wizard page Progress Confirmation Do this View the progress of the replication process.
Tip You can click Save Output to save the output of the wizard to a file. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.

Click Finish.
Note If you view the output of the wizard, the generation process appears to have occurred twice. However, the process is actually performed in two passes: The first pass copies new items into the media target folders, and the second pass deletes any items that are no longer needed in the media target folders.

The Update Media Content Wizard finishes, and the following files are created: • An ISO file in the media_folder folder (where media_folder is the name of the folder that you specified for the media) Generating the ISO file is an option that you configure by selecting the Generate a Lite Touch bootable ISO image check box on the General tab of the media Properties dialog box. Clear this check box to reduce the time needed to generate the media unless you need to create bootable DVDs or start VMs from the ISO file. • WIM files in the media_folder\Content\Deploy\Boot folder (where media_folder is the name of the folder that you specified for the media).

The folders and the content you specified in the selection profile in the linked deployment share are stored in the image files. You can also create a bootable device that contains a copy of the media_folder\Content folder (where media_folder is the name of the folder you specified for the media) so that you can start a target computer from a UFD or USB hard disk. For more information, see Create Bootable Devices from Deployment Media.

Create Bootable Devices from Deployment Media
You may need to deploy images to target computers using a bootable device (such as a UFD or a USB hard disk) when the target computer does not have a high-speed, persistent connection to a deployment share.
Note The target computer must support starting from the device to use this method.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

176

To create bootable devices from deployment media 1. On a computer running Windows Vista or a later operating system, insert the UFD or USB hard disk. 2. Run Diskpart.exe, and type list disk to determine the disk number associated with the device. 3. Type the following commands, where N is the disk number identified in step 2: • • • • • • • select disk N clean create partition primary select partition 1 active format fs=ntfs assign

• exit 4. Copy the contents of the media_folder\Content folder (where media_folder is the name of the folder you specified in the media) to the device.

Manage the MDT DB
The MDT DB augments the configuration that CustomSettings.ini provides for both LTI and ZTI deployments. The MDT DB allows you to centrally manage configuration settings for the target computers. Although you can perform largescale deployments using the CustomSettings.ini file, the MDT DB can help reduce the effort need to manage such deployments. For more information on managing the MDT DB, see Performing Deployments Using the MDT DB.

Configuring LTI Task Sequence Steps in Deployment Workbench
Configure LTI task sequences steps in the Deployment Workbench by: • • • • Configuring LTI task sequence step conditions as described in Configure Task Sequence Step Conditions. Configuring LTI task sequence steps that perform disk-related actions as described in Configure Disk Task Sequence Steps. Configuring LTI task sequence steps that perform network-related actions as described in Configure Network Task Sequence Steps. Configuring LTI task sequence steps that perform server role-related actions as described in Configure Server Role Task Sequence Steps for LTI.
microsoft.com/technet/SolutionAccelerators

Solution Accelerators

177

Microsoft Deployment Toolkit 2010 Update 1

Configuring the Check Bios task sequence step to include a list of incompatible BIOS versions as described in Configure the Check Bios Task Sequence Step for the List of Incompatible BIOS Versions.

Configure Task Sequence Step Conditions
In certain scenarios, consider conditionally running a task sequence step based on defined criteria. Configure task sequence step conditions on the Options tab of a task sequence step. Add any combinations of these conditions to determine whether the task sequence step should run. For example, you could use the values of a task sequence variable and of a registry setting to determine whether a task sequence step should run. Configure conditional task sequence steps by performing any combination of the following actions: • • Add one or more IF statements to a task sequence step condition as described in Add IF Statements to Task Sequence Step Conditions. Add one or more task sequence variables to a task sequence step condition as described in Add Task Sequence Variables to Task Sequence Step Conditions. Add one or more target operating system versions to a task sequence step condition as described in Add Operating System Versions to Task Sequence Step Conditions. Add one or more WMI query results to a task sequence step condition as described in Add WMI Queries to Task Sequence Step Conditions. Add the value of one or more registry settings to a task sequence step condition as described in Add Registry Settings to Task Sequence Step Conditions. Add the test for software installed on the target computer to a task sequence step condition as described in Add a Test for Installed Software to Task Sequence Step Conditions. Add the test for various folder properties to a task sequence step condition as described in Add a Test for Folder Properties to Task Sequence Step Conditions. Add the test for various file properties to a task sequence step condition as described in Add a Test for File Properties to Task Sequence Step Conditions.

• •

Add IF Statements to Task Sequence Step Conditions
All task sequence conditions include one or more IF statements, which are the foundation for creating conditional task sequence steps. A task sequence step condition can include only one IF statement, but you can nest multiple IF statements beneath the top-level IF statement to create more complex conditions.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

178

You test an IF statement based on the conditions listed in Table 79, which you configure in the IF Statement Properties dialog box. Table 79. Conditions Available in IF Statements Condition All conditions Any conditions None Select this option to run the task sequence if All the conditions beneath this IF statement must be true. Any the conditions beneath this IF statement are true. None the conditions beneath this IF statement are true.

Complete the condition for running the task sequence step by adding other criteria to the conditions (for example, task sequence variables or values in a registry setting). To add an IF statement condition to a task sequence step 1. On the step Option tab (where step is the name of the task sequence step to configure), click Add, and then click If statement. 2. In the If Statement Properties dialog box, click condition (where condition is one of the conditions listed in Table 79), and then click OK.

Add Task Sequence Variables to Task Sequence Step Conditions
Create conditions based on any task sequence variable (including those that MDT 2010 defines). These variables also include the environment variables available in the operating system. To configure a condition based on a task sequence variable, provide the following information in the Task Sequence Variable Condition dialog box: • Variable. The name of the task sequence variable to include as a condition. This name must match the exact spelling of the variable but is not casesensitive. Condition. This can be exists (which is true if the variable exists, regardless of its value) or a standard logical operator. Value. The value of the task sequence variable to use in the condition.

• •

To add a Task Sequence Variable condition to a task sequence step 1. On the step Options tab (where step is the name of the task sequence step to configure), click Add, and then click Task Sequence Variable. 2. In the Task Sequence Variable Condition dialog box, in the Variable box, type variable (where variable is the name of the task sequence variable). 3. In the Task Sequence Variable Condition dialog box, in the Condition box, click condition (where condition is the logical operation to use in the condition as listed in Table 79).
Solution Accelerators microsoft.com/technet/SolutionAccelerators

click condition (where condition is the logical operation to use in the condition). Within each namespace is a collection of classes that correspond to a managed resource. microsoft. in the Operating system box. see the WMI Scripting Primer at http://www. refers to a specific WMI namespace. and then click OK.mspx? mfr=true. click architecture (where architecture is the name of the operating system architecture). A version of Windows Condition. Add WMI Queries to Task Sequence Step Conditions You can use WMI queries in a task sequence condition. networks. A logical operator To add an Operating System Version condition to a task sequence step 1. You can also write scripts that use the WMI scripting library to work with WMI and create a wide range of systems management and monitoring scripts. To configure a condition based on a WMI condition.com/technet/SolutionAccelerators Solution Accelerators . either x86 or x64 Operating System. applications. Add Operating System Versions to Task Sequence Step Conditions Create conditions based on the operating system version by providing the following information in the Task Sequence OS Condition dialog box: • • • Architecture. in the Architecture box. In the Task Sequence OS Condition dialog box. provide the following information in the Task Sequence WMI Condition dialog box: • WMI namespace. The default. In the Task Sequence OS Condition dialog box. and monitor configuration settings on desktop and server systems. click Add. In the Task Sequence Variable Condition dialog box. control. in the Condition box. and then click OK.179 Microsoft Deployment Toolkit 2010 Update 1 4. and then click Operating System Version.microsoft. type value (where value is the value of the task sequence variable). change. WMI allows you to query. \root\cimv2. 3. click the operating system to use. In the Task Sequence OS Condition dialog box. Based on industry standards. and other enterprise components. 4. On the step Option tab (where step is the name of the task sequence step to configure). 2.com/technet/scriptcenter/guide/sas_wmi_overview. For more information about WMI. The name of the instruction set on which the operating system is designed. WMI is the primary management technology for Windows operating systems and enables consistent and uniform management. Namespaces are grouped hierarchically and are similar to the way folders are grouped in the operating system. in the Value box. and monitoring of systems throughout the enterprise.

which can be one of the following: microsoft. In the Task Sequence WMI Condition dialog box. based on defined criteria. such as AND or OR Value name. The registry contains two basic elements: keys and values. Add Registry Settings to Task Sequence Step Conditions Evaluate registry settings during the task sequence. The value type. using backslashes (\) to indicate levels of hierarchy. A logical operator. The name of the value to use in the condition Value type.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 180 • WQL query.com/technet/SolutionAccelerators Solution Accelerators . The subtree of the registry key. system information or querying computers could be accessed across a network. This dialog box contains the query that runs when the conditions are met. WMI is generally queried in two ways: by retrieving an entire WMI object or by using a Structured Query Language (SQL)–like query. type the query script to be run. 3. which in turn can contain further subkeys. choose whether to run additional processes. Base the condition on one of the following: • • • • • • • • HKEY_CURRENT_USER HKEY_LOCAL_MACHINE HKEY_USERS HKEY_CURRENT_CONFIG Key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows refers to the subkey Windows of the subkey Microsoft of the key Software of the subtree HKEY_LOCAL_MACHINE. in the WMI namespace box. but including backslashes so makes the values difficult to distinguish from their key paths. Each key can contain subkeys. To add a WMI query result condition to a task sequence step 1. and then click Query WMI. 2. In the Task Sequence WMI Condition dialog box. in the WQL query box. Registry values are name–data pairs stored within but referenced separately from these keys. Keys are referenced with a syntax similar to Windows path names. For example. type WMI namespace. provide the following information in the Registry Setting dialog box: • Root key. On the step Option tab (where step is the name of the task sequence step to configure). • To configure a condition based on a registry setting condition. all of which might contain values. In the query. • Registry keys are similar to folders. click Add. and then click OK. The value of the registry key to use in the condition Condition. Value names can contain backslashes.

In the Registry Setting dialog box. 3. In the Registry Setting dialog box. In the Registry Setting dialog box. click Add. and then click Installed Software. You can use this information to match a specific product using both the product code and the upgrade code. in the MSI file box. or you can use it to match any version of this product using only the upgrade code. The product information will be extracted from the MSI file and populate the respective boxes. The value of the value type for the provided registry key to use in the condition To add a Registry Setting condition to a task sequence step 1. click Value type. and then click OK. In the Registry Setting dialog box. 7. type the value for which testing will occur. in the Value box. in the Value name box. in the Root key box. 2. in the Key box. In the Registry Setting dialog box.com/technet/SolutionAccelerators . click Root key. in the Value type box. click OK. To add an Installed Software condition to a task sequence step 1. click Add. 2. In the Registry Setting dialog box. 5. Solution Accelerators microsoft. In the Installed Software dialog box. In the Installed Software dialog box. On the step Option tab (where step is the name of the task sequence step to configure). in the Condition box. 6.181 Microsoft Deployment Toolkit 2010 Update 1 • • • • REG_SZ REG_EXPAND_SZ REF_DWORD Value. In the Installed Software dialog box. 4. click condition (where condition is the logical operation to use in the condition). 3. On the step Option tab (where step is the name of the task sequence step to configure). browse to the specific MSI file associated with the installed software. type the name of the Value name. select one of the two following conditions: • Match this specific product (Product Code and Upgrade Code) • Match any version of this product (Upgrade Code only) 4. type key (where key is the remainder of the registry key minus the subtree). and then click Registry Setting. Add a Test for Installed Software to Task Sequence Step Conditions You can evaluate installed software based on the product information provided in the Microsoft Installer (MSI) file.

click Add. The path of the file being tested Version. (Optional) A logical operator Date. On the step Option tab (where step is the name of the task sequence step to configure). (Optional) The time stamp of the file To add a File Properties condition to a task sequence step 1. To configure a condition based on a folder’s property. (Optional) The date of the file Time. Otherwise. In addition to evaluating the path of the file to be tested. go to the folder to be tested. set the condition of the value. 4. test for its time stamp under a number of conditions. in the Path box. To configure a condition based on a file property.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 182 Add a Test for Folder Properties to Task Sequence Step Conditions You can evaluate folders based on folder properties. and set the time. click Add. clear the Check the timestamp check box so that the additional condition will not be tested for. In addition to evaluating the path of the folder to be tested. (Optional) The time stamp of the file To add a Folder Properties condition to a task sequence step 1. and then click Folder Properties. 3. set a date. provide the following information on the File Properties dialog box: • • • • • Path. test for its version and time stamp under a number of conditions. The path of the folder to test. 2. On the step Option tab (where step is the name of the task sequence step to configure). (Optional) The date of the file Time. click OK. In the Folder Properties dialog box. Add a Test for File Properties to Task Sequence Step Conditions You can evaluate files based on the file properties. select the Check the timestamp check box. provide the following information on the Folder Properties dialog box: • • • • Path. (Optional) One of the logical operators Date.com/technet/SolutionAccelerators . and then click File Properties. In the Folder Properties dialog box. In the Folder Properties dialog box. Solution Accelerators microsoft. Condition. to check the time stamp of the file. (Optional) Version of the file being tested Condition.

Configure the disk settings in the Deployment Workbench or in the Configuration Manager Console. select the Check the version check box. and type the version number to be tested for. In the File Properties dialog box. In the File Properties dialog box. select the Check the timestamp check box. In the details pane. To configure task sequence steps based on the Format and Partition Disk task sequence step type 1. Configure Disk Task Sequence Steps You can customize task sequences to configure the disk settings on the target computer. For Windows XP and Windows Server 2003. 3. 5. and set the time. 3. Point to Microsoft Deployment Toolkit. In the File Properties dialog box. set the condition of the value. Otherwise. if you want to check the version of the file. 2. Otherwise. Custom disk partitions are only supported in New Computer scenarios. in the Path box. To configure task sequence steps that perform disk-related functions. MDT 2010 only supports installing the operating system to Disk 0 Partition 1. In the Deployment Workbench console tree. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). Click Start.183 Microsoft Deployment Toolkit 2010 Update 1 2. In the File Properties dialog box. browse to the file to be tested. to check the time stamp of the file. and then point to All Programs. set the condition of the value.com/technet/SolutionAccelerators . 4. clear the Check the version check box so that the additional condition will not be tested for. Note LTI does not support the deployment of the target operating system to logical drives or dynamic disks. and then click Deployment Workbench. set a date. perform the following steps: • • Configure the Format and Partition Disk task sequence step types as described in Configure Format and Partition Disk Task Sequence Steps Configure Enable BitLocker task sequence step types as described in Configure Enable BitLocker Task Sequence Steps Configure Format and Partition Disk Task Sequence Steps Task sequence steps based on the Format and Partition Disk task sequence step type allow the creation of multiple partitions and are typically used to create secondary partitions for storing data. clear the Check the timestamp check box so that the additional condition will not be tested for. Solution Accelerators microsoft. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). click OK.

com/technet/SolutionAccelerators . Contains the type of partition type. Configuration Settings on the Properties Tab of Format and Partition Disk Task Sequence Step Type Setting Type Name Comments Disk number Description Contains the task sequence type. Contains the name of the task sequence step that appears in the task sequence hierarchy. which is always set to Format and Partition Disk. Provides descriptive information about the task sequence step. The Confirm Partition Delete dialog box is displayed in which you can confirm (Yes) or cancel (No) the deletion. configure the settings listed in Table 80 based on the requirements of your organization. in the task sequence hierarchy. Table 80. On the Task Sequence tab. 5. Configure the settings in Table 81 based on the requirements of your organization. the disk number is zero-based. In the Actions pane. and then click OK. Click to display the Partition Properties dialog box for the partition selected in the Volume box For information about completing the Partition Properties dialog box. Click to create a new partition definition and access the Partition Properties dialog box. go to task_sequence_step. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). see Table 81. For information about completing the Partition Properties dialog box. and then click OK. Solution Accelerators microsoft. Click to delete the partition selected in the Volume box. 6.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 184 4. Contains a list of the disk volumes to create on the partition. which means the first disk will be number zero (0). Disk type Volume Create new partition button Partition properties button Partition delete button Table 81 lists the configuration settings for the Partition Properties dialog box. see Table 81. click Properties. which can be Standard (MBR) or GPT. On the Properties tab. Includes the disk number to be partitioned and formatted. and then click the Properties tab.

Select to configure the task sequence step to format the partition by performing a quick format. specify the size of the partition in the Size box. Select to configure the task sequence step to create a partition based on a percentage of the remaining free disk space. Select to configure the task sequence step to create a partition of a specific size. Contains the file system for the format process. which can be Primary or Extended. BitLocker Drive Encryption is a fulldisk encryption feature included in Windows Vista and Windows Server 2008 Solution Accelerators microsoft. • Cleared. Partition type Use a percentage of remaining free space Use specific size Make this a boot partition File system Quick format Variable Configure Enable BitLocker Task Sequence Steps Use this task to enable the BitLocker task. the partition is not configured as the boot partition. specify the percentage in the Size(%)box. the partition format is performed using the quick format process. which appears in the Volume box on the Partition and Format Disk task sequence step type’s Properties tab. Contains the type of partition to be created. Select to configure the task sequence step to configure the partition as the boot partition of the target computer. Contains the name of a task sequence variable used to store the drive letter assigned to the partition. the partition is configured as the boot partition.185 Microsoft Deployment Toolkit 2010 Update 1 Table 81. Configuration Settings on the Partition Properties Dialog Box Setting Partition name Description Contains the name of the partition. If the check box is: • Selected. the partition format is performed using the standard format process. Note MDT 2010 automatically creates an additional partition for new computers when deploying Windows 7 or when BitLocker Drive Encryption has been requested. If you select this option. which can be NTFS or FAT32. If the check box is: • Selected. If you select this option.com/technet/SolutionAccelerators . • Cleared.

mspx?mfr=true.ini file. enable the BitLocker task. government.microsoft.com/technet/SolutionAccelerators Solution Accelerators . The most common configurations are: • • • One partition: 100% One partition and some unallocated space In the Windows Deployment Wizard. BitLocker Drive Encryption is available only in the Enterprise and Ultimate editions of Windows 7 and Windows Vista Enterprise. In addition.com/WindowsVista/en/library/58358421-a7f5-4c97ab41-2bcc61a58a701033. a block cipher adopted as an encryption standard by the U. see BitLocker Drive Encryption Frequently Asked Questions at http://technet2. This requires that the Enable BitLocker task be enabled in the task sequence used for deployment. In the CustomSettings.S. Windows Server 2008 R2. set the following properties: • • • • • • • BDEInstall=TPM BdeInstallSuppress=NO BDeWaitForEncryption=False BDEDriveSize=2000 BDEDriveLetter=S: BDEKeyLocation=C: SkipBitLocker=YES • For more information about enabling BitLocker Drive Encryption. perform the following steps: • • Configure Capture Network Settings task sequence steps as described in Configure Capture Network Settings Task Sequence Steps Configure Apply Network Settings task sequence steps as described in Configure Apply Network Settings Task Sequence Steps microsoft. Select one of the following methods of enabling BitLocker Drive Encryption: • In a task sequence. configure the BitLocker page. Configure Network Task Sequence Steps You can customize task sequences in the Deployment Workbench to configure the network settings on the target computer.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 186 designed to protect data by providing encryption for entire volumes. also known as Rijndael. To configure task sequence steps that perform network-related functions. and Windows Server 2008. which is necessary for New Computer scenarios but not in Refresh Computer or Update Computer scenarios. The AES algorithm in Cipher-block Chaining mode with a 128-bit key is often combined with the Elephant diffuser for additional security. configure the partition in the Format and Partition task. By default. it uses the Advanced Encryption Standard (AES).

187 Microsoft Deployment Toolkit 2010 Update 1 Configure Capture Network Settings Task Sequence Steps Task sequence steps based on the Capture Network Settings task sequence step allow you to capture network configuration settings for all network adapters on the target computer that have statically configured IP addresses for Refresh Computer deployment scenarios.ini file or in the MDT DB. On the Properties tab. Configuration Settings on the Properties Tab of the Capture Network Settings Task Sequence Step Type Setting Type Name Description Contains the task sequence type. In the details pane. Click Start. which is always set to Capture Network Settings Contains the name of the task sequence step that appears in the task sequence hierarchy microsoft. Note The settings captured by sequence steps based on the Capture Network Settings task sequence step in the Refresh Computer deployment scenario override any IP configuration settings specified in the CustomSettings. On the Task Sequence tab. Table 82. Point to Microsoft Deployment Toolkit. The LTI task sequence templates provided with MDT 2010 do not include a task sequence step based on the Capture Network Settings task sequence step type. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). In the Actions pane. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). 6. in the task sequence hierarchy. add a task sequence step based on the Capture Network Settings task sequence step type in the State Capture phase. and then point to All Programs. 2. 4. For Refresh Computer deployment scenarios. In the Deployment Workbench console tree. configure the settings listed in Table 82 based on the requirements of your organization. and then click the Properties tab. 3. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). click Properties. and then click Deployment Workbench. go to task_sequence_step (where task_sequence_step is the name of a task sequence that is a Capture Network Settings task sequence step type). and then click OK. 5.com/technet/SolutionAccelerators Solution Accelerators . To configure task sequence steps based on the Capture Network Settings task sequence step type 1.

com/technet/SolutionAccelerators . and then point to All Programs. Click Start. For each network adapter in the target computer. In the Actions pane. 5. configure the existing task sequence step instead of creating a new task sequence step. 2. The network settings that this task sequence step type configures are the same settings configured in the properties of a network adapter. On the Task Sequence tab. Solution Accelerators microsoft. 3. go to task_sequence_step (where task_sequence_step is the name of a task sequence that is an Apply Network Setting task sequence step type). To configure task sequence steps based on the Apply Network Settings task sequence step type 1. Point to Microsoft Deployment Toolkit. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). in the task sequence hierarchy. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). the Apply Network Settings task sequence step type configures the task sequence step that in turn configures the network adapters on the target computer to use Dynamic Host Configuration Protocol (DHCP) for configuration. and then click the Properties tab. and then click Deployment Workbench. In the Deployment Workbench console tree. 4. Note Network configuration settings the Capture Network Settings task sequence step captures in the State Capture phase override any configuration settings you specify in this task sequence type. In the details pane.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 188 Setting Description Description Provides descriptive information about the task sequence step Configure Apply Network Settings Task Sequence Steps Task sequence steps based on the Apply Network Settings task sequence step type allow the configuration of network settings for each network adapter in the target computer. configure the corresponding network settings. go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share where you will configure the task sequence). In most instances. If no configuration settings are specified. Some of the MDT 2010 task sequence templates include a task sequence step in the State Restore phase named Apply Network Settings. click Properties.

For information about completing the tabs of the Network Settings dialog box. and then click OK. see Tables 84. Contains the name of the task sequence step that appears in the task sequence hierarchy. Table 84. 85. Provides descriptive information about the task sequence step. which is always set to Capture Network Settings.com/technet/SolutionAccelerators Obtain an IP address automatically Use the following IP address Solution Accelerators . confirm (Yes) or cancel (No) the deletion. Configuration Settings on the Properties Tab of the Apply Network Settings Task Sequence Step Type Setting Type Name Description Create new network adapter setting button Description Contains the task sequence type. and 86. Click to display the Network Settings dialog box for the network adapter you selected. see Tables 84. configure the settings listed in Table 83 based on the requirements of your organization. Click to create a new network adapter setting definition and access the Network Settings dialog box. On the Properties tab. 85. Click to delete the network adapter setting you selected. which appears in the box on the Apply Network Settings task sequence step type’s Properties tab. Configure the settings in Table 84 based on the requirements of your organization. Configuration Settings on the General tab of the Network Settings Dialog Box Setting Name Description Contains the name of the network adapter. For information about completing the tabs of the Network Settings dialog box. Select to configure the task sequence step to configure the IP address of the network adapter on the target computer using the values you microsoft. Select to configure the task sequence step to configure the IP address of the network adapter on the target computer using DHCP. and 86. and then click OK. Table 83.189 Microsoft Deployment Toolkit 2010 Update 1 6. Network adapter setting properties button Network adapter settings delete button Table 84 lists the configuration settings for the General tab of the Network Settings dialog box. In the Confirm Adapter Delete dialog.

Modify the IP address and cost metric for a gateway an existing entry. Add the IP address and cost metric for a gateway to the list box. • Properties. Note This box is enabled only if you select Use the following IP address. • Delete. Configuration Settings on the DNS tab of the Network Settings Dialog Box Setting Obtain DNS server automatically Use the following DNS Servers Description Select to configure the task sequence step to configure the DNS settings of the network adapter on the target computer using DHCP. • Delete. Delete an existing entry. Delete an existing entry. Select to configure the task sequence step to configure the DNS settings of the network adapter on the target computer using the values specified in the DNS Server addresses in order of use box. • Properties. Gateway Settings Contains a list of gateway IP addresses and routing cost metrics to be configured for the network adapter. Note This box is enabled only if you select Use the following IP address. microsoft. Table 85 lists the configuration settings for the DNS tab of the Network Settings dialog box. Table 85. Add an IP address and subnet mask combination to the list box.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 190 Setting Description specify in the Network Settings and Gateway Settings boxes. Click one of the following to modify the IP addresses and subnet masks in this list: • Add. Modify the IP address and subnet mask for an existing entry. Click one of the following to modify the gateway IP address and routing cost metric in this list: • Add. Network Settings Contains a list of IP addresses and subnet masks to be configured for the network adapter.com/technet/SolutionAccelerators Solution Accelerators . Configure the settings in Table 85 based on the requirements of your organization. and then click OK.

and then click OK. the IP address of the network adapter is not registered using the suffix listed in DNS Suffix. Delete an existing entry. • Properties. DNS Suffix Register this connection’s address in DNS Use this connection’s suffix in DNS registration Select to configure the network adapter to register the network adapter’s IP address using the suffix listed in DNS Suffix. the IP address of the network adapter is registered in DNS. Add the DNS Server IP address to the list box. Table 86 lists the configuration settings for the WINS tab of the Network Settings dialog box. Note By default. Table 86. • Cleared. • Cleared.191 Microsoft Deployment Toolkit 2010 Update 1 Setting DNS Server addresses in order of use Description Contains a list of DNS server IP addresses to be configured for the network adapter. Click one of the following to modify the list of DNS servers: • Add. Configuration Settings on the WINS tab of the Network Settings Dialog Box Setting WINS server addresses in order of use Description Contains a list of WINS server IP addresses to be configured for the network adapter. Click one of the following to modify the list of WINS servers: • Add. • Delete. this check box is selected.com/technet/SolutionAccelerators Solution Accelerators . Contains the DNS domain name suffix to be added to any DNS queries. this check box is cleared. the IP address of the network adapter is not registered in DNS. Note By default. the IP address of the network adapter is registered using the suffix listed in DNS Suffix. Configure the settings in Table 86 based on the requirements of your organization. Select to configure the network adapter to register the network adapters IP address of the primary DNS server. Modify the DNS server IP address for an existing entry. Add the WINS server IP address to the microsoft. If the check box is: • Selected. If the check box is: • Selected.

Modify the WINS server IP address for an existing entry. The other options are Default and Disable NetBIOS over TCP/IP. Default Select to configure the network adapter to use the default NetBIOS over TCP/IP settings of the target operating system. Delete an existing entry. see Configure Server Role Task Sequence Steps for LTI and ZTI. Enable LMHOSTS lookup Select to configure the network adapter to enable lookups in the LMHOSTS file on the target computer. this check box is cleared. Select to disable NetBIOS over TCP/IP for the network adapter. Enable NetBIOS over TCP/IP Disable NetBIOS over TCP/IP Configure Server Role Task Sequence Steps for LTI LTI can help automate the deployment of server roles in Windows Server 2008. For more information about configuring server role task sequence steps for LTI. If the check box is: • Selected. which include: • • • AD DS. • Cleared. The other options are Default and Enable NetBIOS over TCP/IP. DHCP Server. • Delete. Select to enable NetBIOS over TCP/IP for the network adapter. Note By default. the LMHOSTS file is used for Network basic input/output system (NetBIOS) name resolution on the network adapter. Solution Accelerators microsoft. Configure LTI task sequence steps to deploy the supported server roles. • Properties.com/technet/SolutionAccelerators . The process for configuring the server role task sequence steps is similar for LTI and ZTI.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 192 Setting Description box. The other options are Enable NetBIOS over TCP/IP and Disable NetBIOS over TCP/IP. DNS Server. the LMHOSTS file is not used for NetBIOS name resolution on the network adapter.

Run ZTIBIOS_Extract_Utility.vbs on a target computer that has an incompatible BIOS. Modify ZTIBIOSCheck. The ZTIBIOSCheck.) Computer Manufacturer Model Date The ZTIBIOSCheck.xml file. Attributes to Update in the ZTIBIOSCheck. To use the ZTIBIOS_Extract_Utility.xml file into Notepad.xml file listed in Table 87 for each incompatible BIOS version. Update the attributes in the ZTIBIOSCheck. Solution Accelerators microsoft.xml file contains the source for a script (ZTIBIOS_Extract_Utility.xml file to contain the list of BIOS versions incompatible with the target operating system in the operating system build.xml for each task sequence created in the Deployment Workbench. Table 87. Modify the ZTIBIOSCheck. 3. including any references to possible updates to the BIOS version Manufacturer of the target computer with an incompatible BIOS version (This value must match the value stored in the BIOS. The Check BIOS task runs the ZTIBIOSCheck.wsf script.xml File Attribute Description Description Text description of the target computer that has an incompatible BIOS version.xml file resides in the deployment_share\Scripts folder (where deployment_share is the name of the folder that is the root of the deployment share). 4.vbs) that can help extract the attributes listed in Table 87. which checks the BIOS version of the target computers against the list of incompatible BIOS versions in the ZTIBIOSCheck.vbs utility to extract attributes on a target computer 1.vbs.193 Microsoft Deployment Toolkit 2010 Update 1 Configure the Check Bios Task Sequence Step for the List of Incompatible BIOS Versions The default task order for a task sequence includes the Check BIOS task in the Non-Replace group in the Validation group.com/technet/SolutionAccelerators . Save the script source in Notepad as ZTIBIOS_Extract_Utility. Start Microsoft Notepad.) Date of the BIOS of the target computer with an incompatible BIOS version (This value must match the value stored in the BIOS. 2.) Model of the target computer with an incompatible BIOS version (This value must match the value stored in the BIOS. Copy the script source from ZTIBIOSCheck.

xml to include the BIOS based on the attributes retrieved in the previous steps.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Managing LTI Deployments 194 5. Update ZTIBIOSCheck. Solution Accelerators microsoft.

Initiate the Windows Deployment Wizard. Initiate the deployment from Windows Deployment Services. If these folders are not removed. If a previous deployment was terminated because of an error. or using a DVD. The logic for displaying (or not displaying) a wizard page is noted for each wizard page in the following steps. Replace Computer. Verify that the folders in Table 88 no longer exist on the target computer. target_drive:\_SMSTaskSequenc e 2. or Windows Deployment Services.ini. New Computer. removable device. from local drives. Start the target computer with LTI bootable media from a CD. or Refresh Computer) uses a different process. these folders might still exist on the target computer. Initiate the Windows Deployment Wizard manually or by using Windows Deployment Services. These folders exist on target_drive (where target_drive is the drive on the target computer that has the most available disk space). To deploy the new operating system to the target computer using the Windows Deployment Wizard 1. The Windows Deployment Wizard creates and uses the folders listed in Table 88 during the deployment process. run the Windows Deployment Wizard. The Windows Deployment Wizard displays wizard pages based on the deployment scenario you selected and the configuration options you specified in CustomSettings. DVD. a network share. the process will continue from the point where the previous process terminated instead of starting from the beginning. Remove these folders before initiating a new deployment. Each deployment scenario (Upgrade Computer. The deployment process prompts for any configuration settings not already specified. Table 88. This folder contains state information specific to the Task Sequencer. a.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 195 Running the Windows Deployment Wizard To initiate the deployment of Windows to target computers. . Folders to Remove Before Initiating the Windows Deployment Wizard Folder target_drive:\MININT Description This folder is preserved through the deployment process and contains deployment state information (such as user state migration information and log files).

Open a Command Prompt window in Windows PE for troubleshooting prior to completing the LTI deployment process. Table 90. Use this wizard page to select deployment shares based on a site or a UNC path to a specific server. Select the keyboard layout for Windows PE prior to completing the LTI deployment process. 3. Connect to the appropriate deployment share (for example. Configure with Static IP Configure the IP configuration settings for Address Windows PE when DHCP configuration is not available. click one of the options listed in Table 90 based on the environment’s requirements.com/technet/SolutionAccelerators . Table 89.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 196 b. 4. Welcome Windows Deployment Wizard Page Options Option Run the Deployment Wizard to install a new Operating System Exit to Command Prompt Keyboard Layout Select this option to Start the Deployment Wizard and complete the LTI deployment process. This wizard appears when the conditions in Table 89 are met. Click this button to open the Configure Static IP Network Settings dialog box. the Windows Deployment console automatically sets this value.vbs. Note The IP configuration settings configured in the Configure Static IP Network Settings dialog box override any IP configuration settings specified in the CustomSettings.). Welcome to the Windows Deployment Wizard Page Conditions Property DeployRoot Condition Begins when the DeployRoot property equals “ ” (blank) or X:\. and then type cscript litetouch. and then click Next. Solution Accelerators microsoft. select the method for locating the deployment share. Typically. and then click Next. Reboot Restarts the target computer without completing the LTI deployment process.ini file or in the MDT DB. Sites are logical groupings of one or more deployment shares. On the Welcome Windows Deployment page. On the Welcome to the Windows Deployment Wizard page. \\server_name\Distribution$\Scripts).

Assign a specific license key for installation or retail activation. Table 91. Assign a MAK to the target computer and activate the computer over the Internet. This wizard appears when the conditions in Table 91 are met. The first character in the property is less than 6 (which indicates a Windows Vista or Windows Server 2008 build). and then click Next. Product Key Options Option No product key is required Activate the machine with a Multiple Activation Key (MAK) Select this option to Assign product keys to target computers using a KMS key. Note All supported operating systems could have task sequences listed. Not equal to REPLACE. . On the Specify the product key needed to install this operating system page. Although task sequences based on the Litetouch OEM task sequence template can be selected from other deployment shares. Table 92. ensure that the deployment is being performed from a removable media (MEDIA) deployment share. in the Product key box.197 Microsoft Deployment Toolkit 2010 Update 1 4. Solution Accelerators microsoft. the task sequence will not finish successfully. Specify the Product Key Needed to Install This Operating System Page Conditions Property SkipProductKey DeploymentType ImageBuild Condition Not equal to YES. Use a specific product key 6. type product_key (where product_key is the product key to be assigned to the target computer). On the Select a task sequence to execute on this computer page. In the Multiple activation key box. beneath The following task sequences are available section.com/technet/SolutionAccelerators . type product_key (where product_key is the product key to be assigned to the target computer). and then click Next (see Table 92). type mak (where mak is the MAK to be assigned to the target computer). click one of the options listed in Table 94 based on your environment’s requirements. 5. select task_sequence (where task_sequence is the name of the task sequence to run). In the Product_key box. On the Choose a migration type page. Note If a task sequence based on the Litetouch OEM task sequence template appears in the list.

Table 93. and then click Next. • Restore user state migration data on the same computer. Upgrade this computer 7. Table 94.com/technet/SolutionAccelerators . Migration Type Options Option Refresh this computer Select this option to • Optionally. The wizard appears when the conditions in Table 95 are met. Note The upgrade process will fail on target computers that have users logged on using Remote Desktop sessions. including operating system and applications. Upgrade the existing computer using the upgrade features that the new operating system supports. click one of the options listed in Table 96 based on your environment’s requirements. Configure the Computer Name Page Conditions Property SkipDestinationDisk DeploymentType Solution Accelerators Condition Not equal to YES Not equal to NEWCOMPUTER or REPLACE or microsoft.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 198 This wizard appears when the conditions in Table 93 are met. The Choose a migration type wizard page is not displayed for the New Computer scenario. Note Although it is not a migration scenario. save the existing user state migration data. you can use the New Computer scenario to deploy a new operating system to a new computer. Choose a Migration Type Page Conditions Property SkipDeploymentType DeploymentType OSGUID Condition Not equal to YES Not equal to NEWCOMPUTER or REPLACE or CUSTOM Not equal to blank Note This wizard page appears if the selected task sequence is deploying an operating system. • Deploy the desktop standard environment. Table 95. On the Configure the Target Partition page. Ensure that no users are connected to the target computer by Remote Desktop before initiating the Windows Deployment Wizard.

Specify Computer Membership Configuration Solution Accelerators microsoft. Join the Computer to a Domain or Workgroup Page Conditions Property PrePopulateDomainMembershi p SkipDomainMembership DeploymentType Condition Equal to TRUE Not equal to YES Not equal to REPLACE or UPGRADE Table 99. click one of the options listed in Table 99 based on your environment’s requirements. Configure the Computer Name Page Conditions Property SkipComputerName DeploymentType Condition Not equal to YES Not equal to NEWCOMPUTER or REPLACE or CUSTOM 9. On the Join the computer to a domain or workgroup page. Table 97. in the Computer name box.199 Microsoft Deployment Toolkit 2010 Update 1 Property ImageBuild CheckForDisk Condition CUSTOM Equal to 6 Not equal to TRUE Table 96. On the Configure the computer name page.com/technet/SolutionAccelerators . This wizard appears when the conditions in Table 97 are met. and then click Next. 8. Migration Type Questions Option Destination Disk Destination Partition Select this option to Select the destination disk number where the operating system is to be deployed. This wizard appears when the conditions in Table 98 are met. Select the destination partition number where the operating system is to be deployed. type computer_name (where computer_name is the computer name to assign to the target computer). Table 98. and then click Next.

In the User Name box. User State Backup Options Option Automatically Solution Accelerators Select this option to • Allow the MDT 2010 scripts and process microsoft. In the Organizational Unit box. Join a Windows workgroup. In the Domain box. type organizational_unit (where organizational_unit is the name of the organizational unit [OU] in the AD DS domain in which the computer account will be created).com/technet/SolutionAccelerators . 4. Table 100. This wizard appears when the conditions in Table 100 are met. type domain (where domain is the name of the domain in the user account specified in the User Name box is located).Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 200 For this option Join a domain Perform this task to Join an existing AD DS domain: 1. In the Domain box. 3. type password (where password is the password for the user account specified in the User Name box). In the Password box. Specify Where to Save Your Data and Settings Page Conditions Property SkipUserData DeploymentType Condition Not equal to YES Not equal to NEWCOMPUTER or REPLACE or CUSTOM Table 101. • In the Workgroup box. Join a workgroup 10. click one of the options listed in Table 101 based on your environment’s requirements. type domain (where domain is the name of the domain to be joined). type user_name (where user_name is the name of a user account that has sufficient permissions to create the computer account in the domain). and then click Next. On the Specify where to save your data and settings page. type workgroup (where workgroup is the name of the workgroup to join). 5. 2.

In the Location box. On the Specify whether to restore user data page. Specify a location Do not save data and settings Discard any existing user state migration data or deploy a new computer with no existing data. click one of the options listed in Table 103 based on your environment’s requirements. Save the user state migration data to a specific location. 11. Specify Whether to Restore User Data Page Conditions Property SkipUserData DeploymentType Condition Not equal to YES Equal to NEWCOMPUTER Table 103. and then click Next. click one of the options listed in Table 105 based on requirements. On the Specify where to save a complete computer backup page. This wizard appears when the conditions in Table 102 are met. type location (where location is the fully qualified path to the location in which the user state migration back files are stored). • Optionally.201 Microsoft Deployment Toolkit 2010 Update 1 Option determine the location Select this option to rules to automatically determine the best location based on local available disk space on the target computer. User State Restore Options Option Do not restore user data and settings Specify a location Select this option if The migration type is New Computer and there is no user state migration data to restore. In the Location box. click Browse to go to the location. Note Alternatively. The migration type is Replace Computer. 12. Solution Accelerators microsoft. and then click Next. select the Allow data and settings to be stored locally when possible check box to give preference to storing the data locally. type location (where location is the fully qualified path to the locations for storing the user state migration data). Table 102.com/technet/SolutionAccelerators .

In the Location box. Use the Windows Complete PC Backup for enhanced disaster recovery protection after migration is complete. Specify Where to Save a Complete Computer Backup Page Conditions Property SkipComputerBackup DeploymentType Condition Not equal to YES Equal to REFRESH Table 105.com/technet/SolutionAccelerators . Note Windows Complete PC Backup is a feature of Windows Vista only. Table 104. On the Specify the product key needed to install this operating system page. Table 106. select the Allow data and settings to be stored locally when possible check box to give preference to storing the data locally. • Optionally. Computer Image Backup Options Option Automatically determine the location Select this option to • Allow the MDT 2010 scripts and process rules to automatically determine the best location based on local available disk space on the target computer. MDT 2010 uses the ImageX utility during migration because it works on all platforms that MDT 2010 supports. and then click Next. Specify a location Do not back up the existing computer The Windows Deployment Wizard uses the ImageX utility to perform the backup. type location (where location is the fully qualified path to the locations for storing the computer backup). it is designed to create a backup of the target computer to assist in recovering user state migration information that might not have been captured correctly.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 202 This wizard appears when the conditions in Table 104 are met. Discard any existing data on the target computer or deploy a new computer with no existing data. 13. in the Product key box. ImageX is not intended to be used as a part of the overall backup and disaster recovery process. This wizard appears when the conditions in Table 106 are met. Instead. type product_key (where product_key is the product key to be assigned to the target computer). Save the computer image backup to a specific location. Specify the Product Key Needed to Install This Operating System Page Conditions Solution Accelerators microsoft.

click one of the options listed in Table 109 based on your environment’s requirements. Table 108. For Windows 7 Ultimate. For all other Windows versions. you can include additional language packs. click the language pack to be installed. some problems in displaying fonts might occur. However. Not equal to REPLACE or CUSTOM. Locale Options In this box Language to install Select The default language for the target operating system. Windows Vista Enterprise. you can select more than one language.203 Microsoft Deployment Toolkit 2010 Update 1 Property SkipProductKey DeploymentType Condition Not equal to YES Not equal to REPLACE or CUSTOM 14. Table 107. 15. The first character in the property is equal to 6 (which indicates the Windows Vista build). This wizard appears when the conditions in Table 108 are met. On the Languages and other preferences page. Windows 7 Enterprise. Language and other preferences Page Conditions Property SkipLocaleSelection DeploymentType ImageBuild Condition Not equal to YES. and then click Next. and then click Next.com/technet/SolutionAccelerators Solution Accelerators . if the languages are not already installed in the earlier version of Windows or Windows PE. and all editions of Windows Server 2008. microsoft. in the Packages box. This wizard appears when the conditions in Table 107 are met. select only one language. and there are active packages to display to the user. Windows Vista Ultimate. Packages Page Conditions Property SkipPackageDisplay DeploymentType ImageBuild Condition Not equal to YES Not equal to REPLACE or CUSTOM The first character in the property is equal to 6 (which indicates the Windows Vista build). Note In an Upgrade Computer scenario. Table 109. On the Packages page.

and then click Next. Keyboard layout to be used with the target operating system. click the time zone in which the target computer is located. and then click Next. This wizard appears when the conditions in Table 110 are met.com/technet/SolutionAccelerators . select the appropriate applications to deploy. Administrator Password Page Conditions Property SkipAdminPassword DeploymentType Condition Not equal to YES Not equal to REPLACE or CUSTOM Solution Accelerators microsoft. 16. and then click Next. On the Administrator Password page. Table 112. Table 110. On the Select one or more applications to install page. Table 111. This wizard page appears when the conditions in Table 112 are met. This wizard appears when the conditions in Table 111 are met. Select One or More Applications to Install Page Conditions Property DeploymentType SkipAppsOnUpgrade Condition Not equal to REPLACE or UPGRADE Not equal to YES IsThereAtLeastOneApplicationPresen Greater than one t SkipApplications Not equal to YES 18. in the Administrator Password and Please confirm Administrator Password boxes.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 204 In this box Time and currency format Keyboard layout Select The default locale for the target operating system. Set the Time Zone Page Conditions Property SkipTimeZone DeploymentType Condition Not equal to YES Not equal to REPLACE or CUSTOM 17. type password (where password is the password for the local built-in Administrator account on the target computer). On the Set the Time Zone page .

com/technet/SolutionAccelerators . store the image in the location specified. Deploy the target operating system to the target computer without capturing a Sysprep image of the computer. Then. On the Specify whether to capture an image page. click one of the options listed in Table 116 based on your environment’s requirements. Table 113. Copy the required Sysprep files to the target computer. microsoft. Table 115. Not equal to YES. Specify the BitLocker Configuration Page Conditions Property SkipBitLocker DeploymentType DoCapture ImageBuild ImageFlags Solution Accelerators Condition Not equal to YES. and then click Next. Image Capture Options Option Capture an image of this reference computer Select this option to Run Sysprep. type file_name (where file_name is the name of the image file). This wizard appears when the conditions in Table 113 are met. and then capture an image of the target computer. but do not initiate Sysprep.205 Microsoft Deployment Toolkit 2010 Update 1 19. Prepare to capture the machine Do not capture an image of this computer 20. Equal to ENTERPRISE or ULTIMATE. Specify Whether to Capture an Image Page Conditions Property SkipCapture DeploymentType JoinDomain Condition Equal to NO Equal to NEWCOMPUTER Equal to “” Table 114. click one of the options listed in Table 114 based on requirements. In the File name box. In the Location box. The first character in the property is equal to 6 (which indicates the Windows Vista build). type location (where location is the fully qualified path to the location for storing the image of the target computer). This wizard appears when the conditions in Table 115 are met. On the Specify the BitLocker configuration page. and then click Next. Equal to REPLACE or CUSTOM.

• To use TPM with a startup key. Note The default setting for BitLocker Drive Encryption is enabled. select Enable BitLocker using only an External Startup Key. Then. Enable BitLocker using Activate BitLocker Drive Encryption and use TPM TPM version 1. in the Pin box. Complete the Specify credentials for connecting to network shares page based on the information in Table 118. select the drive on which the external startup key resides. select Enable BitLocker using TPM and a startup key. BitLocker Drive Encryption Configuration Options Option Do not enable BitLocker for this computer Select this option to Deploy the new operating system without activating BitLocker Drive Encryption. Table 117. in the box. select Enable BitLocker using TPM only. select one of the following options for using TPM: • To use TPM only.2 or later. 21. type pin (where pin is the BitLocker Drive Encryption PIN for the target computer). Enable BitLocker using Enable BitLocker Drive Encryption. in the box.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 206 Table 116. • To use TPM with a PIN. 48-character external key. and then click Next. • To use only an External Startup Key. Specify Credentials for Connecting to Network Shares Page Conditions Property UserID_isDirty UserID DeploymentType DeploymentMethod Condition Equal to TRUE Equal to “” Not equal to REPLACE Not equal to MEDIA Solution Accelerators microsoft. select the drive on which the startup key resides. This wizard appears when the conditions in Table 117 are met. and use a only an external key randomly generated. select Enable BitLocker using TPM and a PIN.com/technet/SolutionAccelerators .

com/technet/SolutionAccelerators . password (where password is the password for the user account specified in the User Name box). The Windows Deployment Wizard finishes. Note To expand the details of this deployment. Credentials Options Option User Name Type user_name (where user_name is the user name of the account that has the appropriate permissions for the network shared folders that the deployment scripts use). domain (where domain is the name of the domain in which the user account. These shared folders include folders used to store user state migration data or image backups of the target computer. specified in the User Name box. Solution Accelerators microsoft. is located).207 Microsoft Deployment Toolkit 2010 Update 1 You use these credentials to access network shared folders used during the deployment process. click Details. and then click Begin. and deployment of the new operating system begins. Review the information on the Ready to begin page. Password Domain 22. Table 118.

Deploying to and capturing an image of the reference computer in ZTI as described in Deploying to and Capturing an Image of the Reference Computer in ZTI. or upgrade an existing instance of MDT 2008 to MDT 2010 as described in Install or Upgrade to MDT 2010 for ZTI. Ensure that your new or existing System Center Configuration Manager infrastructure is specifically optimized for the Operating System Deployment feature. 2. or from removable media. To prepare the MDT 2010 deployment environment for ZTI deployments 1. Deploying captured images to the target computer in ZTI as described in Deploying Captured Images to Target Computers in ZTI. Install a new instance of MDT 2010 on the deployment server. Preparing for ZTI deployment to the reference computer as described in Preparing for ZTI Deployment to the Reference Computer. Preparing the prerequisite infrastructure as described in Prepare the Prerequisite Infrastructure for ZTI Deployments. 3. within a Windows workgroup. Perform ZTI deployments by: • • • Preparing the ZTI deployment environment as described in Preparing the ZTI Deployment Environment. Obtain the software that ZTI requires as described in Obtain the Software Required by the ZTI Deployment Process. Enable the Configuration Manager Console integration with MDT 2010 as described in Enable Configuration Manager Console Integration.208 Microsoft Deployment Toolkit 2010 Update 1 Performing ZTI Deployments Using System Center Configuration Manager You perform ZTI deployments using System Center Configuration Manager and MDT 2010 within an AD DS domain. Prepare the Prerequisite Infrastructure for ZTI Deployments ZTI deployments require that a properly configured System Center Configuration Manager infrastructure exist prior to installing MDT 2010 and performing deployments. 4. Preparing for ZTI deployment to the target computers as described in Preparing for ZTI Deployments to Target Computers. you are ready to prepare the MDT 2010 deployment environment for ZTI. . • • Preparing the ZTI Deployment Environment After you have prepared the prerequisite infrastructure for MDT 2010.

see Configuration Manager Supported Configurations at http://technet. You can modify these ZTI task sequences. This wizard must be run after the upgrade to register the new components and install the ZTI new task sequence templates. One or more computers running a previous version of MDT or BDD. For more information about: • Hardware and software requirements for System Center Configuration Manager. create a new ZTI task sequence. see the section. If your existing environment has: • No computers currently running MDT 2010 or a previous version of MDT or BDD.com/technet/SolutionAccelerators . Ensure any ZTI task sequences created prior to the upgrade use the Microsoft Deployment Toolkit Files package that existed prior to the upgrade.aspx.com/en-us/library/bb680717. • Install or Upgrade to MDT 2010 for ZTI Deployments The first step in performing ZTI deployments is to have at least one instance of MDT 2010 running in your environment. Configuring a System Center Configuration Manager infrastructure to support ZTI deployments. • • • • Solution Accelerators microsoft. If you had previously installed and configured the PXE filter to support the unknown computer capability in previous versions of MDT. upgrade those instances to MDT 2010 as described in Upgrading to MDT 2010. install one or more new instances of MDT 2010 as described in Installing a New Instance of MDT 2010. Run the Remove PXE Filter Wizard.microsoft. This support is now provided in System Center Configuration Manager 2007 R2 and has been removed in MDT 2010. To use the new MDT 2010 task sequence actions or steps. but you cannot use any of the new MDT 2010 task sequence actions or steps.” in the MDT 2010 document. The existing Microsoft Deployment Toolkit Files package can be used for any ZTI task sequences created prior to the upgrade.0 or later must be installed on any computer on which MDT 2010 is installed for management of ZTI deployments.209 Microsoft Deployment Toolkit 2010 Update 1 Note Windows PowerShell version 1. Quick Start Guide for Microsoft System Center Configuration Manager 2007. but a new Microsoft Deployment Toolkit Files package must be created for new ZTI task sequences. Ensure you create a new Microsoft Deployment Toolkit Files package for any new ZTI task sequences you create. Install MDT 2010 on each computer that has the Configuration Manager Console installed and that you will use to create or edit task sequences that MDT 2010 generates. After the upgrade process is complete: • Run the Configure ConfigMgr Integration Wizard. “Step 1: Prepare the Prerequisite Infrastructure.

such as security updates.mof) file that contains the new class definitions. 3. type ConfigMgr_site_code (where ConfigMgr_site_code is the System Center Configuration Manager site code that installs MDT 2010 integration).com/technet/SolutionAccelerators . Enable Configuration Manager Console Integration Before you can use the System Center Configuration Manager integration features of MDT 2010. Solution Accelerators microsoft. Applications that are to be installed as a part of the operating system image or during the deployment of the reference image. Note The Configuration Manager Console should be closed when performing this procedure. In the Site Server Name dialog box. This software will be imported or added to deployment shares unless it already exists in the deployment share. In the Site Code dialog box. USMT source files used to create a software package that is deployed to the target computers to capture user state migration data. You add these classes by compiling a Managed Object Format (. Note MDT 2010 and MDT 2010 Update 1 support Windows AIK 2.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 210 Obtain the Software Required by the ZTI Deployment Process Collect the software needed during the ZTI deployment process. and System Center Configuration Manager 2007 with SP2. This wizard copies the appropriate System Center Configuration Manager integration files to the Configuration Manager 2007_root (where Configuration Manager 2007_root is the folder in which System Center Configuration Manager or the Configuration Manager Console is installed).0. and then click OK. Required software includes: • • • • • Operating system source files for each operating system to be deployed to the reference and target computers. Device drivers for the reference and target computers that are not included as part of the operating system. The Configure Configuration Manager 2007 Integration Wizard starts.0. and then click Configure ConfigMgr 2007 Integration. To run the Configure Configuration Manager 2007 Integration Wizard 1. Windows PE 3. 2. feature packs. Point to Microsoft Deployment Toolkit. Click Start. type ConfigMgr_server_name (where ConfigMgr_server_name is the name of the System Center Configuration Manager server on which to install MDT 2010 integration). and then point to All Programs. The wizard also adds WMI classes for the new MDT 2010 custom actions. and language packs. Operating system packages for the operating systems. run the Configure Configuration Manager 2007 Integration Wizard.

3. Later in the ZTI deployment process.ini file for the task sequence by specifying DoCapture=YES. Note The ZTI deployment process is unable to perform Sysprep operations on a target computer that is encrypted by using BitLocker Drive Encryption. and then capturing an image of that computer. Create a reference computer for each image that you want to create for deployment to the target computers. To prepare for deployment to the reference computer 1. Note Most production networks have multiple distribution points. select the appropriate distribution points for the network. Do not enable BitLocker Drive Encryption on the reference computer. Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Sequence Wizard in Configuration Manager Console as described in Creating a ZTI Task Sequence using MDT 2010 Task Sequence Templates. Configure System Center Configuration Manager to contain the appropriate software for deployment to the reference computer. Solution Accelerators microsoft. you will deploy the captured image of your reference computer to the appropriate target computers. you must at least add the DoCapture property to the Customsettings. For more information about the use of reference computers in MDT 2010 deployments. When performing this step in a production environment.211 Microsoft Deployment Toolkit 2010 Update 1 Preparing for ZTI Deployment to the Reference Computer Regardless of the ZTI deployment scenario you are performing. Tip Create the task sequence for deploying to the reference computer based on the Client Task Sequence or Server Task Sequence template included in MDT 2010. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. always start by creating a reference computer. see Estimating Storage Requirements for System Center Configuration Manager Distribution Points.com/technet/SolutionAccelerators . including the following: • • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. 2. see Using Reference Computers in MDT 2010 Deployments. For more information about determining the number of images required in your organization (and subsequently the number of reference computers required). 4. 5. Ensure that the distribution points for the packages and operating system images that the new ZTI task sequence uses are distributed properly as described in Managing Distribution Points in Configuration Manager Console. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. and enable BitLocker Drive Encryption on the target computers only after the target operating system is completely deployed. Important If you are capturing an image of the reference computer.

select the appropriate distribution points for the network. prepare Windows Deployment Services to start the appropriate Windows PE images that will in turn start the ZTI deployment process to the Solution Accelerators microsoft. 2. Create an advertisement for the reference computer task sequence as described in Managing Advertisements in Configuration Manager Console. When performing this step in a production environment. advertise the task sequence to the reference computer and start the reference computer with the bootable Windows PE image created earlier in the process. and customize the MDT 2010 deployment process. 2. To deploy to and capture an image of the reference computer 1. 5.com/technet/SolutionAccelerators . 3. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. Prepare network shares for storing migration data and MDT 2010 deployment logs as described in Preparing the MDT 2010 Migration Resources. Optionally. deploy them to the target computers. The task sequence created earlier will deploy the target operating system. Create a collection that contains the reference computer as described in Managing Computer Collections in Configuration Manager Console. and then capture an image of the reference computer. device drivers. To prepare for ZTI deployment to target computers 1. ensure that the necessary deployment resources exist.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 212 6. and applications to the reference computer. Deploying to and Capturing an Image of the Reference Computer in ZTI After the distribution points are updated. Note Most production networks have multiple distribution points. Start the reference computer with the task sequence bootable media disk as described in Deploying an Operating System Using Task Sequence Bootable Media. In preparation for deploying the captured images to the target computers. operating system packages. Create a task sequence bootable media disk by using the Task Sequence Media Wizard as described in Creating Task Sequence Bootable Media. Add the reference computer to the System Center Configuration Manager site database as described in Manually Adding Computers to the Site Database in Configuration Manager Console. create one or more task sequences for deploying the captured images. 4. Preparing for ZTI Deployment to Target Computers After the images of the reference computers are captured.

microsoft. There is no user migration information to save and restore and no existing file systems to preserve. Create additional distribution points to help in larger deployments as described in Managing Distribution Points in Configuration Manager Console. see Identifying Deployment Scenarios. and specify the fully qualified UNC path to the WIM image captured from the reference computer. the MDT 2010 configuration files. but ensure that you specifically follow the configuration settings on the wizard pages listed in Table 119 and select the appropriate values on the other wizard pages based on your organization’s requirements. Tip Create the task sequence for deploying to the reference computer based on the Client Task Sequence or Server Task Sequence template included in MDT 2010. Information for Completing the Create Microsoft Deployment Task Sequence Wizard for Performing New Computer Deployment Scenario Using ZTI On this wizard page OS Image Do this Select Create a new OS image. and the MDT DB for each deployment scenario as described in the following: • • • Prepare for the New Computer Deployment Scenario to Target Computers Using ZTI Prepare for the Refresh Computer Deployment Scenario to Target Computers Using ZTI Prepare for the Replace Computer Deployment Scenario to Target Computers Using ZTI Depending on the target computers in your organization. Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager Console as described in Creating a ZTI Task Sequence using MDT 2010 Task Sequence Templates. you deploy a new installation of a Windows operating system to a new computer. 4.213 Microsoft Deployment Toolkit 2010 Update 1 target computers as described in Preparing Windows Deployment Services for ZTI Deployments.com/technet/SolutionAccelerators Solution Accelerators . For more information about MDT 2010 deployment scenarios. any combination of these deployments scenarios might be necessary. To prepare for the New Computer deployment scenario to target computers 1. Prepare the ZTI task sequences. Table 119. 3. Use the Client Task Sequence template to deploy the captured image of the reference computer to the target computer. Prepare for the New Computer Deployment Scenario to Target Computers Using ZTI In the New Computer deployment scenario.

Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager console as described in Creating a ZTI Task Sequence Using MDT 2010 Task Sequence Templates. 7. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. Ensure that the distribution points for the packages and operating system images that the new ZTI task sequence uses are distributed properly as described in Managing Distribution Points in Configuration Manager Console. When performing this step in a production environment.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 214 2. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console.com/technet/SolutionAccelerators . including computers that must be re-imaged for image standardization or to address a problem. 6. Tip Create the task sequence for deploying to the reference computer based on the Client Task Sequence or Server Task Sequence template included in MDT 2010. select the appropriate distribution points for the network. Note Most production networks have multiple distribution points. Prepare for the Refresh Computer Deployment Scenario to Target Computers Using ZTI In the Refresh Computer deployment scenario. but ensure that you follow the configuration settings on the wizard pages listed in Table 120 and select the appropriate values on the other wizard pages for your organization’s requirements. select the appropriate distribution points for the network. Configure System Center Configuration Manager to contain the appropriate software for deployment to the target computer. Solution Accelerators microsoft. 4. 3. Use the Client Task Sequence template to deploy the captured image of the reference computer to the target computer. To prepare for the Refresh Computer deployment scenario to target computers 1. When performing this step in a production environment. 5. Note Most production networks have multiple distribution points. There is user migration information to save and restore but no existing file systems to preserve. including: • • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. a computer is refreshed. Optionally. customize the MDT DB to the needs of your organization as described in Performing Deployments Using the MDT DB (if you are using the MDT DB to provide MDT 2010 configuration information).

When performing this step in a production environment. Ensure that the distribution points for the packages and operating system images that the new ZTI task sequence uses are distributed properly as described in Managing Distribution Points in Configuration Manager Console. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. Information for Completing the Create Microsoft Deployment Task Sequence Wizard for Performing New Computer Deployment Scenario Using ZTI On this wizard page OS Image Do this Select Create a new OS image.215 Microsoft Deployment Toolkit 2010 Update 1 Table 120. When performing this step in a production environment. Configure System Center Configuration Manager to contain the appropriate software for deployment to the target computer. • Performing Deployments Using the MDT DB. Use the: Solution Accelerators microsoft. and specify the fully qualified UNC path to the WIM image captured from the reference computer. Prepare for the Replace Computer Deployment Scenario to Target Computers Using ZTI In the Replace Computer deployment scenario. a new installation of Windows is deployed to a new computer. one computer replaces another computer. select the appropriate distribution points for the network. Finally. 2. the user state data is restored to the new computer. Note Most production networks have multiple distribution points. 5. Note Most production networks have multiple distribution points. 4. including: • • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. Important You must establish a computer association record for each existing target computer and each new target computer prior to performing the deployment to the target computer. 6. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. Optionally. customize the MDT 2010 configuration files or the MDT DB to the needs of your organization as described in: • Configuring MDT 2010 Deployments. Create a computer association record that associates the existing target computer and the new target computer.com/technet/SolutionAccelerators . select the appropriate distribution points for the network. Then. There are no existing file systems to preserve. 3. The existing user state migration data is saved from the existing target computer.

Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 216 • Client Replace Task Sequence template to save the user state migration of the existing target computer. Important Run this task sequence after running the task sequence based on the Client Replace Task Sequence template on the existing target computer.com/technet/SolutionAccelerators Solution Accelerators .” in Configuration Manager Documentation Library. but ensure that you specifically follow the configuration settings on the wizard pages listed in Table 121 and select the appropriate values on the other wizard pages for your organization’s requirements. Information for Completing the Create Microsoft Deployment Task Sequence Wizard for Performing New Computer Deployment Scenario Using ZTI On this wizard page OS Image Do this Select Create a new OS image. Tip Create the task sequence for deploying to the reference computer based on the Client Task Replace Sequence template included in MDT 2010. Table 121. 2. • Client Task Sequence template to deploy the captured image of the reference computer to the new target computer and restore the user state migration data. Create a computer association between the existing target computer and the new target computer as described in the section. 3. “How to Create a Computer Association for Side-by-Side Migration. microsoft. Configure System Center Configuration manager to contain the appropriate software for deployment to the target computer. Create a new task sequence that will deploy the captured image of the reference computer to the target computer. Important Run this task sequence before running the task sequence based on the Client Task Sequence template on the new target computer. which is installed with System Center Configuration Manager. and specify the fully qualified UNC path to the WIM image captured from the reference computer. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 3. Tip Create the task sequence for deploying to the reference computer based on the Client Replace Task Sequence template included in MDT 2010. To prepare for the Replace Computer deployment scenario to target computers 1. Create a new task sequence that will save the user state migration data of the existing target computer as described in Creating a ZTI Task Sequence Using MDT 2010 Task Sequence Templates. and restore the user state migration data saved by the Client Replace Task Sequence as described in Creating a ZTI Task Sequence Using MDT 2010 Task Sequence Templates.

Solution Accelerators microsoft. select the appropriate distribution points for the network. 5. 4. Customize the task sequences to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration manager Console. 2. as described in Manually Adding Computers to the Site Database in Configuration Manager Console. select the appropriate distribution points for the network. Deploying Captured Images to Target Computers in ZTI The deployment of the captured images to the target computers is slightly different for each MDT 2010 deployment scenario using ZTI. and ensure that the collection includes the target computers requiring the corresponding deployment scenario. • 7. Ensure that the distribution points for the packages and operating system images that the new ZTI task sequence uses are distributed properly as described in Managing Distribution Points in Configuration Manager Console. To deploy the capture image of the reference computer to the target computers 1. Note Most production networks have multiple distribution points. When performing this step in a production environment. “How to Deploy Operating Systems Using Unknown Computer Support. Note Create a collection for each MDT 2010 deployment scenario to be performed. Customize the MDT 2010 configuration files or the MDT DB to the needs of your organization as described in: • Configuring MDT 2010 Deployments.com/technet/SolutionAccelerators . Note Most production networks have multiple distribution points. Add the target computer to the System Center Configuration Manager site database: • • Manually. Deploy the captured image of the reference computer to target computers for each respective deployment scenario in your organization.” in Configuration Manager Documentation Library. Create a collection that contains the target computers as described in Managing Computer Collections in Configuration Manager Console. which is installed with System Center Configuration Manager. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console.217 Microsoft Deployment Toolkit 2010 Update 1 Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. When performing this step in a production environment. 6. Automatically as described in the section. • Performing Deployments Using the MDT DB.

Prepare Windows Deployment Services to start the appropriate Windows PE images that will in turn start the ZTI deployment process to the target computers as described in Preparing Windows Deployment Services for ZTI Deployments. Complete the Task Sequence Wizard. Create an advertisement for the target computer task sequences as described in Managing Advertisements in Configuration Manager Console. Depending on the target computers in your organization. Deploy the captured reference computer image to the target computers for each deployment scenario as described in: • • • Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using ZTI. any combination of deployments scenarios might be necessary. For more information about the MDT 2010 deployment scenarios. Note This wizard will not appear if you configure ZTI to perform a PXE boot and have configured a mandatory advertisement or if only one task sequence is advertised to the target computer. 2. Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using ZTI Start the target computer with the task sequence bootable media created earlier in the process or from Windows Deployment Services. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using ZTI. ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 122 and select the appropriate values on the other wizard pages for your organization’s requirements.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 218 3. Either method starts Windows PE on the target computer and initiates the ZTI deployment process. To deploy the capture images to the target computers in the New Computer Deployment Scenario Using ZTI 1. 5. Solution Accelerators microsoft. The Task Sequence Wizard starts. Deploy Captured Images to Target Computers in the Replace Computer Deployment Scenario Using ZTI. At the end of the process.com/technet/SolutionAccelerators . Start the target computer with the task sequence bootable media created earlier in the process or from Windows Deployment Services. see Identifying Deployment Scenarios. the captured image of the reference computer is deployed on the target computer. 4 Provide a method for starting the target computers by doing any combination of the following: • • Create a task sequence bootable media disk using the Task Sequence Media Wizard as described in Creating Task Sequence Bootable Media.

The task sequence restarts the computer. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using ZTI Start ZTI by running the Configuration Manager advertisement for capturing the user state migration data you created earlier in the process. The target computer is now deployed.219 Microsoft Deployment Toolkit 2010 Update 1 Table 122. Deploy the captured image of the reference computer to the new target computer as described in Deploy the Captured Image to the New Target Solution Accelerators microsoft. run the Task Sequence Wizard to deploy the captured image of the reference computer to the new target computer (new computer) and restore the user state saved earlier in the process. To deploy the capture images to the target computers in the Refresh Computer Deployment Scenario Using ZTI • Run the Configuration Manager advertisement for capturing the Refresh Computer deployment scenario that you created earlier in the deployment process. The task sequence runs in the current operating system to capture user state migration data. This task sequence runs in the current operating system on the existing target computer. starts Windows PE. starts the new operating system. The wizard starts. restores the user state migration data. First. installs any packages. Save the user state migration data from the existing target computer as described in Save the User State Migration Data from the Existing Target Computer Using ZTI. run the advertisement for the task sequence you created to capture the user state migration data from the existing target computer (old computer). Second. Deploy Captured Images to Target Computers in the Replace Computer Deployment Scenario Using ZTI The Replace Computer deployment scenario requires two separate steps to complete the migration. the task sequence restarts the computer. and performs any other actions configured in the task sequence. 2.com/technet/SolutionAccelerators . and then initiates installation of the new operating system. Information for Completing the Task Sequence Wizard in the New Computer Deployment Scenario Using ZTI On this wizard page Select a Task Sequence Do this Select the task sequence you created for the target computer deployment for the New Computer deployment scenario. and the operating system deployment starts. Finally. To deploy captured images of the reference computer to target computers 1. installs any applications.

Table 123. Complete the Task Sequence Wizard. the captured image of the reference computer is deployed on the target computer. To deploy the capture images to the target computers in the Replace Computer Deployment Scenario Using ZTI • Run the Configuration Manager advertisement for capturing the Refresh Computer deployment scenario that you created earlier in the process. Start the reference computer with the ZTI bootable media created earlier in the process or from Windows Deployment Services. The ZTI bootable media starts Windows PE on the target computer and initiates the ZTI.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 220 Computer with the User State Migration Data from the Existing Computer Using ZTI. Save the User State Migration Data from the Existing Target Computer Using ZTI Start the ZTI deployment process by running the Configuration Manager advertisement for capturing the user state migration data that you created earlier in the process. ensuring that you follow the configuration settings for the wizard pages listed in Table 123 and select values on the other wizard pages for your organization’s requirements. Deploy the Captured Image to the New Target Computer with the User State Migration Data from the Existing Computer Using ZTI Start the target computer with the ZTI bootable media created earlier in the process or from Windows Deployment Services. Information for Completing the Task Sequence Wizard for the Replace Computer Deployment Scenario for Deploying the Captured Image Using ZTI Solution Accelerators microsoft. and the user state migration data is restored from the Configuration Manager state migration point. Note This wizard will not appear if you configure ZTI to perform a PXE boot and have configured a mandatory advertisement or if only one task sequence is advertised to the target computer. 2. To complete the Windows Deployment Wizard in the Replace Computer deployment scenario for deploying the captured image 1. The task sequence runs in the current operating system to capture user state migration data. the user state migration data of the existing target computer is saved to the Configuration Manager state migration point. This task sequence runs in the current operating system on the existing target computer. and then the Windows Deployment Wizard starts. Windows PE starts. At the end of the deployment process.com/technet/SolutionAccelerators . At the end of the task sequence.

The wizard starts. The new target computer is deployed with the user state from the existing target computer automatically restored to the new target computer. Solution Accelerators microsoft.com/technet/SolutionAccelerators . and the operating system deployment starts.221 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Select a Task Sequence Do this Select the task sequence you created for the target computer deployment in the Replace Computer deployment scenario to deploy the captured image of the reference computer to the new target computer.

Managing computer collections for ZTI as described in Managing Computer Collections in Configuration Manager Console. Managing device drivers for ZTI deployments in the Configuration Manager Console as describe in Managing Device Drivers in Configuration Manager Console. You use the Deployment Workbench in ZTI deployments only to configure the MDT DB. Manage ZTI deployments in the Configuration Manager Console by: • Creating a new task sequence for ZTI deployments using the Create Microsoft Deployment Task Sequence Wizard as described in Creating a ZTI Task Sequence Using MDT 2010 Task Sequence Templates.222 Microsoft Deployment Toolkit 2010 Update 1 Managing ZTI Deployments in Configuration Manager Console You manage ZTI deployments through the Configuration Manager Console. Creating boot images for use with ZTI using the Create Image Using Microsoft Deployment Wizard as described in Creating ZTI Boot Images. Configuring ZTI task sequence steps that perform server role–related actions as described in Configuring Server Role Task Sequence Steps for ZTI. Managing distribution points for ZTI as described in Managing Distribution Points in Configuration Manager Console. • • • • • • • • • • • • . Managing operating systems for ZTI deployments in the Configuration Manager Console as described in Managing Operating Systems in Configuration Manager Console. Manually adding computers to the site database for ZTI as described in Manually Adding Computers to the Site Database in Configuration Manager Console. The wizards used to configure ZTI are integrated into the Configuration Manager Console. Managing software packages for ZTI in the Configuration Manager Console as described in Managing Software Packages in Configuration Manager Console. Managing advertisements for ZTI as described in Managing Advertisements in Configuration Manager Console. Creating task sequence bootable media for ZTI as described in Creating Task Sequence Bootable Media. Deploying an operating system using task sequence bootable media as described in Deploying an Operating System Using Task Sequence Bootable Media. Configuring individual ZTI task sequence steps as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console.

MDT 2010 includes task sequence templates that you can use to deploy the reference and target computers. Deploy the image captured after the OEM Preload Task Sequence (Pre-OEM) completed on the target computers. Task Sequence Templates Included in MDT 2010 Template File name Select this template to Deploy to target computers for all scenarios except the Replace Computer scenario. Table 124. Identifying the packages and images that the MDT 2010 task sequence templates require as described in Identify the Packages and Images Required by the MDT 2010 Task Sequence Templates.xml SCCM_CLIENT_POST– OEM. • Identify the ZTI Task Sequence Templates in MDT 2010 Table 124 lists the task sequences templates included in MDT 2010. Solution Accelerators microsoft. Deploy to target computers for the Replace Computer scenario.223 Microsoft Deployment Toolkit 2010 Update 1 Creating a ZTI Task Sequence Using MDT 2010 Task Sequence Templates Use the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager Console to create task sequences in System Center Configuration Manager that are integrated with MDT 2010.xml Deploy to the reference computer to prepare the reference computer for the OEM capture process. Creating ZTI task sequences as described in Create ZTI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard.xml Sequence Client Replace Task Sequence OEM Preload Task Sequence (PostOEM) OEM Preload Task Sequence (Pre-OEM) SCCM_ClientReplace. Client Task SCCM_Client. The template files are located in the install_folder\SCCM folder (where install_folder is the folder in which MDT 2010 was installed). Create ZTI task sequences using the MDT 2010 task sequence templates by: • • Identifying the ZTI task sequence templates that are a part of MDT 2010 as described in Identify the ZTI Task Sequence Templates in MDT 2010.com/technet/SolutionAccelerators . and a description of the template. the file name for each template.xml SCCM_CLIENT_PRE–OEM.

Identify the Packages and Images Required by the MDT 2010 Task Sequence Templates Table 125 lists the packages and images that the task sequence templates in MDT 2010 require. These packages and images must exist (or be created) for the task sequences to run correctly.exe for Windows Vista or later operating systems). Microsoft SCCM_Custom. Contains unattended files and customsettings.ini. All the files required to install the operating system (using WINNT32 for Windows XP and Windows Server 2003 or Setup. Note Always use the Import Microsoft Deployment Task Sequence Wizard to import the task sequence templates. Table 125.xml Deploy to target computers for all scenarios. Packages and Images Required by the Task Sequence Templates Included in MDT 2010 This package or image Boot image package Contains the Boot image used to initiate the ZTI deployment process and in the middle of the process when performing the Refresh Computer deployment scenario.xml Deploymen t Custom Task Sequence Standard Server Task Sequence SCCM_Server. USMT files used to capture and restore user state. System Center Configuration Manager client installation files. Microsoft Deployment Files package OS image package OS install package Client package USMT package Custom Settings package Solution Accelerators microsoft.com/technet/SolutionAccelerators . Although you can manually import the task sequence templates.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 224 Template File name Select this template to Create a task sequence that can be customizable to meet the needs of your organization. doing so is not recommended. Script and tools necessary for the MDT 2010 task sequence templates for System Center Configuration Manager. Image of the target operating system to be deployed to the target computer.

see the section. The Create Microsoft Deployment Task Sequence Wizard substitutes the packages and images selected for the placeholders in the task sequence templates.com/technet/SolutionAccelerators • • • Solution Accelerators . For more information about configuring a task sequence step based on this type. “About Software Update Deployments. consider creating and including the following elements in the task sequences to provide similar functionality in the Deployment Workbench: • Software distribution packages. security updates. see the section. which is included with System Center Configuration Manager. This package includes any software that will be installed as part of the operating system deployment (similar to the Applications node in the Deployment Workbench). and service packs) that will be installed as part of the operating system deployment (similar to the OS Packages node in the Deployment Workbench). In addition to the packages and images that the task sequence templates require. Custom software distribution packages in System Center Configuration Manager. You can use these software update packages as: • Without modification by using the Software Updates feature in System Center Configuration Manager. These packages include any Windows package files that contain software updates (such as language packs. see the section. Windows package file (software update) packages. These packages are created as packages and programs in System Center Configuration Manager.225 Microsoft Deployment Toolkit 2010 Update 1 This package or image Sysprep files package Contains the Contains the specific Sysprep files defined for a package. which is included with System Center Configuration Manager. which is only required when capturing an image of a computer running Windows XP or Windows Server 2003. Note You can use the generic boot images (WIM files) that the Deployment Workbench generates in ZTI deployments. you cannot use the LTI LiteTouch boot images (WIM files) that the Deployment Workbench generates in ZTI deployments. After completing the wizard. “Tasks for Software Distribution. For more information on using these packages in the Software Updates feature. see Configuring ZTI Task Sequence Steps in Configuration Manager Console.” in Configuration Manager microsoft. However. The task sequence templates contain placeholders for each package and image listed in Table 125. Installed directly by ZTI using the Install Updates Offline task sequence step type.” in Configuration Manager Documentation Library. The Create Microsoft Deployment Task Sequence Wizard can automatically create these packages and images or can use existing packages and images. For more information on how to create these packages. For more information on how to create these packages.” in Configuration Manager Documentation Library. the new created task sequence references the appropriate packages and images. “Tasks for Software Distribution.

Point to Microsoft System Center. To create a ZTI task sequence using the Create Microsoft Deployment Task Sequence Wizard 1. After completing the wizard. Click Start. Table 126. microsoft. You can specify device driver categories in an Auto Apply Drivers task sequence step type to limit which drivers are installed. Note Always use the Create Microsoft Deployment Task Sequence Wizard to create task sequences based on the MDT 2010 task sequence templates. select task_sequence_template (where task_sequence_template is the task sequence template to be selected from Table 124). Although you can manually import the task sequence templates. Complete the Create Microsoft Deployment Task Sequence Wizard using the information in Table 126.com/technet/SolutionAccelerators Solution Accelerators .Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 226 Documentation Library. Create ZTI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard The Create Microsoft Deployment Task Sequence Wizard substitutes the packages and images selected for the placeholders in the task sequence templates. For more information about how to include device drivers in the operating system image. doing so is not recommend. 3. In the Actions pane. see the section. • Device driver package. The Create Microsoft Deployment Task Sequence Wizard starts. “How to Install Drivers on a Configuration Manager Client Using a Task Sequence. 4.” in Configuration Manager Documentation Library. In the Configuration Manager Console console tree. go to Site Database/Computer Management/Task Sequences. Information for Completing the Create Microsoft Deployment Task Sequence Wizard On this wizard page Choose Template Do this 1. and then click ConfigMgr Console. which is included with System Center Configuration Manager. point to Configuration Manager 2007. In The following SCCM task sequence templates are available. and then point to All Programs. or you can install all device drivers using an Apply driver package task sequence step type. Accept the default values unless otherwise specified. 2. click Create Microsoft Deployment Task Sequence. System Center Configuration Manager uses driver packages to control the distribution of drivers to distribution points. which is included with System Center Configuration Manager. the new task sequence references the appropriate packages and images.

in User name. type comment (where comment is descriptive text that describes the purpose of the task sequence). The other option is Join a domain. Click Next. In Password and Confirm password. c. d. In Organization name. b. 4. type organization_name (where microsoft. Click Join a domain. type task_sequence_name (where task_sequence_name is the name of the task sequence displayed in the Configuration Manager Console). 3. If you select this option. perform the following steps: a.227 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Choose Template: General Do this 2. The other option is Join a workgroup. and then click OK. 2. In Domain. In Task sequence name. type workgroup_name (where workgroup_name is the name of the workgroup to join). type domain_name (where domain_name is the name of the workgroup to join). Select Join a workgroup. type user_name (where user_name is the name of the registered user that appears in the Windows operating system properties). If you select this option. Click Next. in Workgroup. type domain_name\user_name (where user_name is the name of the user account used to join the computer to the domain and domain_name is the name of the domain in which the user account resides. In Task sequence comments. type password (where password is the password for the user account). In the Windows User Account dialog box.com/technet/SolutionAccelerators Choose Template: Details Solution Accelerators . Click Set. 3. In User name. This account must be a member of the Domain Admins group in the domain or have sufficient delegated permissions). 1. The Windows User Account dialog box appears. 2. 1.

The other option is Create a new boot image package. 5. 3. d. Click Next. 2. If you select this option. In Product key. 6. in User name. Select Specify an existing boot image. perform the following steps: a. If you select this option. In the Windows User Account dialog box. type password (where password is the password for the user account). The other option is This task sequence may be used to capture and image. Choose Template: Capture Settings 1. perform the following steps: a. Click Next. The Windows User Account dialog box appears. type unc_path (where unc_path is the fully qualified UNC path for the location of the WIM file. Select This task sequence will never be used to capture and image. type product_key (where product_key is the product key for operating system). b. type domain_name\user_name (where user_name is the name of the user account that has Write permission to the folder specified in Capture destination and domain_name is the name of the domain in which the user account resides).com/technet/SolutionAccelerators Boot Image Solution Accelerators . In Select a Package dialog box. In Capture destination. c. Click Set. b. Click Browse. In Password and Confirm password. The other option is This task sequence will never be used to capture and image.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 228 On this wizard page Do this organization_name is the name of the registered organization that appears in the Windows operating system properties). including the name of the WIM file). Select This task sequence may be used to capture and image. 1. and then click OK. click microsoft. The Select a Package dialog box appears.

4. 3. type package_name (where package_name is the name to be given to the boot image package). Click Next. Ensure that the Configuration Manager service account has the appropriate permission on this network shared folder. Select or clear the ADO check box if you want to add ADO components to the boot image. 3. In Comments. Click Next. In Version. If the check box is: • Selected. By default. 2. in Package source to be created. The Configuration Manager service account must have permission to modify the contents of this UNC path to update the boot images.229 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this package_name (where package_name is the name of the existing boot image). the ADO components are added to Solution Accelerators microsoft. 2. click platform (where platform is the platform architecture for the boot image— x86 or X64). Tip You can also click Browse to locate the UNC path. type comment_text (where comment_text is descriptive information about the boot image package). Boot Image: Image Options Note This wizard page appears only if you select Create a new boot image package on the Boot Image wizard page. type version_number (where version_number is the version number to be assigned to the boot image package). The other option is Create a new boot image package. Boot Image: General Settings Note This wizard page appears only if you select Create a new boot image package on the Boot Image wizard page. Select Create a new boot image package. If you select this option. In Name. In Platform. 1. 2. and then click OK. which is needed to access SQL Server databases such as the MDT DB. 1.com/technet/SolutionAccelerators . type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). this check box is selected.

Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 230 On this wizard page Do this the boot image. perform the following steps: a. MDT Package 1. Japanese [JA-JP]. the media hook files are not added to the boot image. Hypertext Markup Language Application (HTA). XML. If you select this option. The Select a Package dialog box appears. Note Alternatively. In the Select a Package dialog box. The other option is Create a new Microsoft Deployment Toolkit files package. which can be Chinese [ZH-CN]. 5. Chinese [ZH-HK]. The other option is Specify an existing Microsoft Deployment Toolkit files package. If you select this option. Chinese [ZH-TW]. b. • Cleared. Select Create a new Microsoft Deployment Toolkit files package. 6. the ADO components are not added to the boot image. Click Next. 2. or Korean [KO-KR]) to add support for the optional fonts. Click Browse. the media hook files are added to the boot image. Select or clear the Add media hook files to enable the Deployment Wizard for this boot media check box. 3. type unc_path (where unc_path is the fully qualified UNC path for the location of microsoft. Select or clear the font check box (where font is the name of the font to be added. click package_name (where package_name is the name of the existing package). type unc_path (where unc_path is the fully qualified UNC path to the bitmap file that you want to use as the background). • Cleared.com/technet/SolutionAccelerators Solution Accelerators . Note Scripting. Select Specify an existing Microsoft Deployment Toolkit files package. in Package source to be created. and then click OK. In Custom background bitmap file (UNC Path). If the check box is: • Selected. click Browse to find the bitmap file. and WMI support are always added to the boot image. 4.

3. If you want to deploy an image with a different index. MDT Package: MDT Details Note This wizard page appears only if you select Create a new Microsoft Deployment Toolkit files package on the MDT Package wizard page. 1. 4. if you select a SKU that is different from the default SKU. Select Specify an existing OS image. In Name. Specify an existing OS installation package. Note The ZTI task sequence templates always configure the Apply Operating System Image task sequence step to deploy the image index equal to 1. In Version. Click Next. remove the following section from Unattend. OS Image On this wizard page. Tip You can also click Browse to locate the UNC path. OS image packages are created from WIM files either from distribution media or from custom WIM files you have created. 2. In Comments.xml in the Settings package: <MetaData> <Key>/image/index</Key> <Value>1</Value> </MetaTag> 1. Click Next.com/technet/SolutionAccelerators . 3. type version_number (where version_number is the version number to be assigned to the Microsoft Deployment Toolkit files package). change the configuration of the Apply Operating System Image task sequence step. Also. type package_name (where package_name is the name to be given to the Microsoft Deployment Toolkit files package). you can select (or create) OS image packages or OS install packages. type comment_text (where comment_text is descriptive information about the Microsoft Deployment Toolkit files package).231 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this the folder in which the package source will be stored). Solution Accelerators microsoft. OS install packages contain all the necessary files to install the operating system. The other options are Create a new OS image. such as the contents of a Windows XP CD.

type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the WIM file is located. If you select this option. If you select this option. perform the following steps: a. Create a new OS image. Specify an existing OS installation package. or Specify Solution Accelerators microsoft. In Select a Package dialog box. Select Create a new OS install package. Create a new OS image. b. and then click OK. If you select this option. click package_name (where package_name is the name of the existing package). including the name of the WIM file). Tip You can also click Browse to locate the WIM file. In the Select a Package dialog box. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). Select Specify an existing OS installation package.com/technet/SolutionAccelerators . Click Browse. The Select a Package dialog box appears. b. perform the following steps: a. Select Create a new OS image. 2. Tip You can also click Browse to locate the UNC path.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 232 On this wizard page Do this or Create a new OS install package. Click Browse. In Package source folder to be created. The Select a Package dialog box appears. click package_name (where package_name is the name of the existing package). or Create a new OS install package. 4. In OS image file (WIM) location. b. or Create a new OS install package. The other options are Specify an existing OS image. perform the following steps: a. and then click OK. The other options are Specify an existing OS image. The other options are Specify an existing OS image. 3.

1. type version_number (where version_number is the version number to be assigned to the package). In Comments. type package_name (where package_name is the name to be given to the package). In Comments. Tip You can also click Browse to locate the UNC path. OS Image: Install Source Note This wizard page appears only if you select Create a new OS install package on the OS Image wizard page. perform the following steps: a. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). If you select this option. Click Next. 4. 2. Tip You can also click Browse to locate the UNC path. b. type comment_text (where comment_text is descriptive information about Solution Accelerators microsoft. 3. In Version. In Name. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). 2. which are then used to create the package. Click Next. 5. In Version. 1.com/technet/SolutionAccelerators . Note The OS installation folder contents are copied from the specified UNC location to the package source folder. In OS installation folder location. In Name. type version_number (where version_number is the version number to be assigned to the package). 3. type package_name (where package_name is the name to be given to the package). In Package source folder to be created. type comment_text (where comment_text is descriptive information about the package).233 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this an existing OS installation package. OS Image: Image Details Note This wizard page appears only if you select Create a new OS image on the OS Image wizard page.

Click Next.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 234 On this wizard page Do this the package). Select Specify an existing ConfigMgr client package. Client Package 1. The other option is Specify an existing ConfigMgr client package. In the Select a Package dialog box. 3. 2. and then click OK. The other option is Create a new USMT package. In Path to USMT executables and related. see the section. b. Note You cannot specify the location for storing the user state migration data in the CustomSettings. Select Specify an existing USMT package. which is installed with System Center Configuration Manager. USMT Package 1. Click Browse. perform the following steps: a. click package_name (where package_name is the name of the existing package). If you select this option. click package_name (where package_name is the name of the existing package). and then click OK.” in Configuration Manager Documentation Library. For more information. Select Create a new ConfigMgr client package. Select Create a new USMT package. “How to Capture and Restore User State. The Request state store task automatically determines the state migration point to use for storing user state migration data. If you select this option. 2.ini file for ZTI. The Select a Package dialog box appears.com/technet/SolutionAccelerators . type path (where path is the fully qualified Solution Accelerators microsoft. Click Next. b. The other option is Create a new ConfigMgr client package. In the Select a Package dialog box. The other option is Specify an existing USMT package. 4. If you select this option. perform the following steps: a. perform the following steps: a. Click Browse. The Select a Package dialog box appears.

Click Browse. perform the following steps: a. USMT Package: USMT Details Note This wizard page appears only if you select Create a new USMT package on the USMT Package wizard page. type manufacturer_name (where manufacturer_name is the name of the software manufacturer in the package). 3. Click Next. In Manufacturer. Tip You can also click Browse to locate the path. see the Managing Roaming User Data Deployment Guide at http://technet.aspx. In the Select a Package dialog box. For more information on using roaming profiles. The other option is Create a new settings package.10). Click Next. 3. not network copies. In Language.com/enus/library/cc766489(WS. 1. 5.235 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this path for the location of the folder in which the USMT source files are located). Note USMT can only back up and restore locally cached user profiles. In Package source to be created. click package_name (where package_name is microsoft. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). type version_number (where version_number is the version number to be assigned to the package). 4.microsoft. In Name.com/technet/SolutionAccelerators Solution Accelerators . In Version. The Select a Package dialog box appears. Settings Package 1. type package_name (where package_name is the name to be given to the package). If you select this option. b. 6. Select Specify an existing settings package. In Comments. type comment_text (where comment_text is descriptive information about the package). Select this option for Windows Vista or later operating systems. b. type language (where language is the language of the package). Tip You can also click Browse to locate the UNC path. 2.

5. 3. 3. In Manufacturer.com/technet/SolutionAccelerators . Sysprep Package 1. 6. The other options are Specify an existing Sysprep package and Create a new settings package. and then click OK. Select Specify an existing Sysprep package. 2. Solution Accelerators microsoft. 1. type language (where language is the language of the package). In Version. Select No Sysprep package is required. In Language. Tip You can also click Browse to locate the UNC path.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 236 On this wizard page Do this the name of the existing package). If you select this option. 2. Click Create a new settings package. If you select this option. type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package). in Package source to be created. type package_name (where package_name is the name to be given to the package). perform the following steps: a. Settings Package: Settings Details Note This wizard page appears only if you select Create a new settings package on the Settings Package wizard page. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). The other option is Specify an existing settings package. Click Browse. Click Next. The other options are No Sysprep package is required and Create a new settings package. 2. type version_number (where version_number is the version number to be assigned to the package). Click Next. In Comments. In Name. type comment_text (where comment_text is descriptive information about the package). 4.

Click Next. 1. type version_number (where version_number is the version number to be assigned to the package). In the Select a Package dialog box. If you select this option.237 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this The Select a Package dialog box appears. 3. Click Next. 2. 4. In Path to Sysprep executables and related. In Language. click package_name (where package_name is the name of the existing package). type language (where language is the language of the package). b. In Name. 6. type package_name (where package_name is the name to be given to the package). 5. In Package source to be created. 3. The other option is Specify an existing settings package. perform the following steps: a. and then click OK. Sysprep Package: Sysprep Details Note This wizard page appears only if you select Create a new Sysprep package on the Sysprep Package wizard page. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). b.com/technet/SolutionAccelerators . type path (where path is the fully qualified path for the location of the folder in which the Sysprep source files reside). 4. In Version. Tip You can also click Browse to locate the path. In Comments. Summary Click Next. Select Create a new Sysprep package. Solution Accelerators microsoft. In Manufacturer. Tip You can also click Browse to locate the UNC path. type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package). type comment_text (where comment_text is descriptive information about the package).

see the section. see the section. Deploying specific device drivers to target computers for ZTI deployments as described in Deploy Specific Device Drivers to Target Computers in ZTI. • Import Drivers into System Center Configuration Manager To import drivers into System Center Configuration Manager. For more information about managing operating systems in the Configuration Manager Console. “Import New Driver Wizard. The Create Microsoft Deployment Task Sequence Wizard closes when the task sequence is created. Managing Operating Systems in Configuration Manager Console The Operating System Images node in the Configuration Manager Console displays a list of the Operating System Deployment image packages that you have created. Create a New Driver Package A driver package contains the content associated with one or more device drivers. You must add device drivers to a driver package and copy them to a distribution point before System Center Configuration Manager clients can install them. Managing Device Drivers in Configuration Manager Console Manage device drivers in the Configuration Manager Console by: • • • Importing the device drivers into System Center Configuration Manager as described in Import Drivers into System Center Configuration Manager. Creating a new driver package that contains the device drivers as described in Create a New Driver Package. use the Import New Driver Wizard. see the section. which is installed with System Center Configuration Manager. For information about creating a new driver package. For information about this wizard.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 238 The Summary wizard page displays a status bar that shows the progress of the tasks defined in the wizard.com/technet/SolutionAccelerators . Solution Accelerators microsoft. “Operating System Deployment: Operating System Images Node.” in Configuration Manager Documentation Library. which is installed with System Center Configuration Manager. and—when you select an operating system image package from the Operating System Images results pane— specific actions that you can run for that package. Adding device drivers and device driver packages to operating systems and boot images as described in Add Device Drivers to Operating System and Boot Images. the actions that you can run.” in Configuration Manager Documentation Library.

239 Microsoft Deployment Toolkit 2010 Update 1 “How to Create a New Driver Package. Solution Accelerators microsoft.” in Configuration Manger Documentation Library. For information about adding device drivers to boot images. For information about managing the driver catalog. The driver catalog helps manage the cost and complexity of deploying an operating system in an environment that contains different types of computers and devices. see the section. Only add valid device drivers that are intended for use with Windows Vista. because the version of Windows PE is Windows Vista based. Add Device Drivers to an Operating System Add new device drivers to an existing operating system image using the Task Sequence Editor. For information about adding device drivers to an operating system. “How to Add Windows Device Drivers to a Boot Image. Only mass storage device drivers and network adapter device drivers should be added to boot images. Add device drivers from the driver catalog to existing boot images as described in Add Device Drivers to a Boot Image.” in Configuration Manager Documentation Library. “How to Manage the Driver Catalog. see the section. you can add the them to existing operating systems and boot images. To allow System Center Configuration Manager to search in the driver catalog for the new device drivers.” in Configuration Manager Documentation Library. Add Device Drivers to Operating System and Boot Images When you have added device drivers to the driver catalog. see the section. which is installed with System Center Configuration Manager. add a Auto Apply Drivers task sequence step to an existing task sequence.com/technet/SolutionAccelerators . Storing device drivers in the driver catalog and not with each individual operating system image greatly reduces the number of operating system images you need. which is installed with System Center Configuration Manager. which is installed with System Center Configuration Manager. “How to Install Drivers on a Configuration Manager 2007 Client Using a Task Sequence. To add device drivers to operating systems and boot images • • Add device drivers from the driver catalog to existing operating systems as described in Add Device Drivers to an Operating System. Add Device Drivers to a Boot Image You can add Windows device drivers that you have imported into the driver catalog to one or more boot images. because other types of drivers are not needed and will increase the size of the boot image.” in Configuration Manager Documentation Library. which is installed with System Center Configuration Manager.

CD. For more information about strategies for device driver management. CD. You can create new boot images for ZTI using the Create Image using Microsoft Solution Accelerators microsoft. For more information about how to deploy an operating system using task sequence bootable media. Deploying an Operating System Using Task Sequence Bootable Media To initiate ZTI deployment from bootable media. However. see the section “How to Deploy an Operating System Image Using Media” in Configuration Manager Documentation Library. the target operating system uses Plug-and-Play IDs to identify the device drivers needed for the devices on the target computers. see Select the Device Driver Management Strategy. configure the ZTI deployment process to install specific drivers to target computers as described in Manage Device Driver Deployment for ZTI. For more information about how to create task sequence bootable media. provide a method for starting the computer with Windows PE and the necessary software by creating the task sequence bootable media disk. Then. see the section. You can start the target computer from a UFD. or DVD. Note The ZTI deployment process can also be initiated by starting the target computer from Windows Deployment Services.” in Configuration Manager Documentation Library.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 240 Deploy Specific Device Drivers to Target Computers in ZTI By default. “How to Create Task Sequence Bootable Media. which is installed with System Center Configuration Manager. However. Note The ZTI deployment process can also be initiated by starting the target computer from Windows Deployment Services. start the target computer with the bootable media. or DVD.com/technet/SolutionAccelerators . and then starts ZTI. ZTI deploys all device drivers to the target computers. The boot process starts Windows PE. for reference computers it may be easier to start the ZTI deployment process from bootable media. Creating ZTI Boot Images Some situations call for you to create a new boot image for the ZTI process without running the Create Microsoft Deployment Task Sequence Wizard. which is installed with System Center Configuration Manager. for reference computers it may be easier to start the ZTI deployment process from bootable media. To change this default behavior. Creating Task Sequence Bootable Media To initiate the ZTI deployment process from bootable media. Use the Task Sequence Media Wizard in Configuration Manager console to create bootable media for storage on a UFD.

In Name. Accept the default values unless otherwise specified. 3.com/technet/SolutionAccelerators Solution Accelerators . type package_version (where package_version is version number that you want to assign to the package). click Browse to find the network shared folder. In Version. 3. Note Alternatively.241 Microsoft Deployment Toolkit 2010 Update 1 Deployment Wizard in the Boot Images node in the Configuration Manager Console. To create a ZTI boot image 1. In Package source folder to be created (UNC) path. 2. 2. General Settings 1. The Create Image using Microsoft Deployment Wizard starts. type package_name (where package_name is descriptive name displayed in the Configuration Manager Console). Point to Microsoft System Center. The Configuration Manager service account must have permission to modify the contents of this UNC path to update the boot images. go to Site Database/Computer Management/Operating System Deployment/Boot Images. Table 127. Complete the Create Image Using Microsoft Deployment Wizard using the information in Table 127. 4. point to System Center Configuration Manager 2007. In Comments. In the Actions pane. type package_comments microsoft. In the Configuration Manager Console. 2. The Configuration Manager Console starts. type unc_path (where unc_path is the fully qualified UNC path to the folder you want to use as the source for the boot image package). and then click ConfigMgr Console. Click Start. click Create Image using Microsoft Deployment. Information for Completing the Create Image using Microsoft Deployment Wizard On this wizard page Package Source Do this 1. Ensure that the Configuration Manager service account has the appropriate permission on this network shared folder. Click Next. and then point to All Programs.

the media hook files are added to the boot image. Japanese [JAJP]. Select or clear the Add media hook files to enable the Deployment Wizard for this boot media check box. If the check box is: • Selected. the ADO components are added to the boot image. and WMI support are always added to the boot image. In Platform. Chinese [ZH-HK]. Click Next. In Custom background bitmap file (UNC Path). If the check box is: • Selected. 2. 2.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 242 On this wizard page Do this (where package_comments is text that describes the purpose of the boot image). • Cleared. click Browse to find the bitmap file. HTA. the ADO components are not added to the boot image. Chinese [ZH-TW]. Review the information in Details. Image Options 1. Click Next. or Korean [KO-KR]) to add support for the optional fonts. 3. type unc_path (where unc_path is the fully qualified UNC path to the bitmap file that you want to use as the background). Summary 1. Select or clear the font check box (where font is the name of the font to be added. click platform (where platform is the platform architecture for the boot image—x86 or X64). 4. which are needed to access SQL Server databases such as the MDT DB. 6. Select or clear the ADO check box if you want to add ADO components to the boot image. which can be Chinese [ZH-CN]. • Cleared. 4.com/technet/SolutionAccelerators . Note Alternatively. XML. 5. Click Next. Solution Accelerators microsoft. Note The Scripting. the media hook files are not added to the boot image.

Solution Accelerators microsoft. Note All language packs in the same System Center Configuration Manager package are deployed together. Repeat steps 2 and 3 for each language pack that you want to be a part of the package. Managing Software Packages in Configuration Manager Console Manage software packages in the Configuration Manager Console by: • • Adding language packs as described in Add Language Packs. If you want to deploy different combinations of language packs. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. create multiple System Center Configuration Manager packages. Create a folder that will contain the package source for the language pack (. Click Close. Before adding language packs.cab files that you can add to System Center Configuration Manager packages either offline or online. Note Create this folder where previously created packages are stored or where space is available. 3. To create a System Center Configuration Manager package that contains one or more language packs 1.cab file). Create a subfolder beneath the folder you created in step 1 for the language pack (. the new boot image appears in the details pane in the Configuration Manager Console. 4.cab file). create a System Center Configuration Manager package that contains one or more language packs. 2.com/technet/SolutionAccelerators . however. Note Language packs already in .243 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Confirmation Do this Tip You can click Save Output to save the output of the wizard to a file. Add the language pack (. Adding software updates as described in Add Software Updates.cab format are available for download from the Microsoft Volume Licensing website.cab file) downloaded from Microsoft into the subfolder created in step 2. After the Create Image Using Microsoft Deployment Wizard finishes. Add Language Packs Language packs are .

Right-click task_sequence (where task_sequence is the name of the task sequence you want to edit). Click Add. In the Configuration Manager Console tree. and Windows Server 2008 1. click Next. Click Enable binary differential replication. go to Operating System Deployment/Task Sequence. and then click Install Language Packs Offline. On the Security page. 5. 12. Type the path to the source directory. In the Name box. To add language packs online to Windows 7. Type the relevant information in the Name and Description boxes. On the Distribution Settings page.com/technet/SolutionAccelerators . 4. and then click Edit. 7. click Next. and then click Set to set the source directory. In the Configuration Manager Console. then click Close. Right-click Packages. 2. 3. Windows Vista. type language_pack_name (where language_pack_name is a descriptive name of the language pack). and Windows Server 2008 1. under the Postinstall phase. 6. Note When used with MDT 2010. 6. and then click OK. To add language packs offline to Windows 7. go to the Setup Windows and ConfigMgr task. click Next. and thus the image can be modified offline—not in the currently booted operating system. go to Computer Management/Software Distribution/Packages. On the Summary page. Right-click task_sequence (where task_sequence is the name of the task sequence you want to edit). 2. and then click Browse to select an appropriate language pack package to install. and then close the Task Sequence Editor. On the Reporting page. click Next. Windows Vista. 8. the term offline means that the computer is booted into Windows PE. 10. Click OK to save the settings. click Next. 9. 13. In the Task Sequence Editor dialog box. and then click OK. On the Data Access page. and then click Edit. Click This package contains source files. In the Configuration Manager Console. and then click New Package.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 244 5. 7. Windows Server 2008 R2. go to Operating System Deployment/Task Sequence. 14. Click the task immediately above this task so that the new added task will be positioned immediately before the Setup Windows and ConfigMgr task. and then click Next. Windows Server 2008 R2. Solution Accelerators microsoft. click MDT. 11.

5. Right-click task_sequence (where task_sequence is the name of the task sequence you want to edit). click Add.aspx. Beneath the Postinstall phase. Solution Accelerators microsoft. and then click Edit.com/en-us/library/bb693754.com/enus/library/bb693776. such as MSI. click MDT. 3. Note Only updates in CAB files are supported using the Install Updates Offline task sequence type. Click the task immediately above this task so that the new added task will be positioned just above the Setup Windows and ConfigMgr task. Note When used in MDT 2010.com/en-us/library/bb632835. Add Software Updates Use System Center Configuration Manager to add updates—online or offline— during the task sequence. For detailed information on software updates using System Center Configuration Manager. and then click Browse to select a language pack package to install. Type the relevant information in the Name and Description boxes. 2. click MDT. 6. Create a Deployment Management item using the Deploy Package Wizard. 5.microsoft. Manage software updates in System Center Configuration Manager using a server configured as a software update point. the term online means that the computer is booted into an operating system but run as an Administrator user so that final configurations can be made to the running operating system. go to Computer Management/Task Sequence. and then click Browse to select an appropriate updates package to install. add the updates to a Deployment Management item. see Download Updates Wizard at http://technet. Type the relevant information in the Name and Description boxes. 4. or executable (EXE) files. see About Software Update Deployment Packages at http://technet. In the Configuration Manager Console. under the State Restore phase. Click OK to save the settings. Use deployment packages to deploy software updates. see Tasks for Software Updates at http://technet. go to the Restart Computer task. and then click Install Language Packs Online. For more information about configuration and deployment of software update packages. In the Task Sequence Editor dialog box. Other formats of update files are ignore. and then click Install Updates Offline.com/technet/SolutionAccelerators .microsoft.aspx. MSP. 6. locate the Setup Windows and ConfigMgr task. For more information on deploying packages and deployment management.245 Microsoft Deployment Toolkit 2010 Update 1 3. and then close the Task Sequence Editor. To add offline updates to Windows Vista or later operating systems 1. In the Task Sequence Editor dialog box.microsoft.aspx. Click Add. To install operating system updates online. 4.

7. In the Task Sequence Editor dialog box. Type the relevant information in the Name and Description boxes. Right-click task_sequence (where task_sequence is the name of the task sequence you want to edit). Solution Accelerators microsoft. Windows Server 2003. click General. 6.com/technet/SolutionAccelerators . you must advertise the task sequences to the target computers. In the Configuration Manager Console. Managing Advertisements in Configuration Manager Console In ZTI deployments. Click OK to save the settings. Click the Restart Computer task. Note The Software Update Point role and Windows Server Update Services (WSUS) must be properly configured to work with this task sequence step type. and then close the Task Sequence Editor. computers must exist in the System Center Configuration Manager site database before you can advertise a task sequence to the computer. and then click Install Software Updates. see the following sections in Configuration Manager Documentation Library. This step is only necessary when creating custom task sequences.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 246 7. and then click Edit. Advertise the task sequence to the collection that includes the reference computer or target computers. To add online updates to Windows XP. 2. For more information about advertising task sequences. In the Configuration Manager Console. Windows Server 2008. go to the State Restore phase. 5. Click OK to save the settings. Click Add. However. 3. and then close the Task Sequence Editor. for reference computers. go to Computer Management/Task Sequence. 4. 1. which is installed with System Center Configuration Manager: • • “Advertisements Home Page” “How to Advertise Task Sequences” Manually Adding Computers to the Site Database in Configuration Manager Console In ZTI deployments. or Windows Vista Note The task sequence templates in MDT 2010 include the Install Software Updates task sequence step to perform online updates. create an advertisement for the task sequences. it is easier to manually add the reference computer to the site database. System Center Configuration Manager 2007 R2 includes a feature for automatically adding target computers to the site database. and then click Browse to select an appropriate updates package to install.

In System Center Configuration Manager. which is installed with System Center Configuration Manager: • • “About Distribution Points” “How to Designate a Distribution Point” Configuring ZTI Task Sequence Steps in Configuration Manager Console After you create a ZTI task sequence using the Create Microsoft Deployment Task Sequence Wizard. update the distribution points where these images and packages are stored. collections are a grouping of one or more computers. see the following sections in Configuration Manager Documentation Library. distribution points are the repository for the files being deployed to the reference and target computers. The Configuration Manager Console allows you to: Solution Accelerators microsoft.” in Configuration Manager Documentation Library. which is installed with System Center Configuration Manager. Managing Computer Collections in Configuration Manager Console In ZTI deployments.247 Microsoft Deployment Toolkit 2010 Update 1 For more information about manually adding computers to the site database. For more information about managing computer collections. For more information about managing distribution points. “How to Add a New Computer to the Configuration Manager Database. Configure distribution points for the operating system images and software packages that ZTI uses. you can customize it using the Configuration Manager Console. see the following sections in Configuration Manager Documentation Library. the task sequences must be advertised to a collection of target computers.com/technet/SolutionAccelerators . ensuring that each reference and target computer has a persistent. Your organization may have more than one distribution point. see the section. which is installed with System Center Configuration Manager: • • • “Collections Overview” “About Collections” “How to Manage Collections” Managing Distribution Points in Configuration Manager Console In ZTI deployments. If you make any changes to the operating system images and software packages that ZTI uses. high-speed connection to a distribution point.

For more information about configuring server role task sequence steps for ZTI. see the section. DNS Server. Configure ZTI task sequence steps to deploy the supported server roles.” in Configuration Manager Documentation Library. You perform these tasks using the standard methods available in the Configuration Manager Console. • Configuring Server Role Task Sequence Steps for ZTI ZTI can help automate the deployment of server roles in Windows Server 2008. Modify existing task sequence steps. see Configure Server Role Task Sequence Steps for LTI and ZTI.com/technet/SolutionAccelerators . which is installed with System Center Configuration Manager.” in Configuration Manager Documentation Library. see the section. “How to Edit an Existing Task Sequence. For more information about: • Configuring ZTI task sequence steps using the Configuration Manager Console.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 248 • • • Add new task sequence steps. which is installed with System Center Configuration Manager. Solution Accelerators microsoft. which include: • • • AD DS. Task sequences. “About Task Sequences. The process for configuring the server role task sequence steps is similar for ZTI and LTI. DHCP Server. Delete existing task sequence steps.

• • Preparing the UDI Deployment Environment After you have prepared the prerequisite infrastructure for MDT 2010. To prepare the MDT 2010 deployment environment for UDI deployments 1. within a Windows workgroup. or upgrade an existing instance of MDT 2008 to MDT 2010 as described in Install or Upgrade to MDT 2010 for UDI. or from removable media. Ensure that your new or existing System Center Configuration Manager infrastructure is specifically optimized for the Operating System Deployment feature. . Preparing the prerequisite infrastructure as described in Prepare the Prerequisite Infrastructure for UDI Deployments. Install a new instance of MDT 2010 on the deployment server. Obtain the software that UDI requires as described in Obtain the Software Required by the UDI Deployment Process. Preparing for UDI deployment to the target computers as described in Preparing for UDI Deployments to Target Computers. Deploying to and capturing an image of the reference computer in UDI as described in Deploying to and Capturing an Image of the Reference Computer in UDI. Install and configure the UDI web service. 3. Enable Configuration Manager Console integration with MDT 2010 as described in Enable Configuration Manager Console Integration. 2. you are ready to prepare the MDT 2010 deployment environment for UDI. which provides support for the Application Discovery feature in UDI as described in Install and Configure the UDI Web Service. Perform UDI deployments by: • • • Preparing the UDI deployment environment as described in Preparing the UDI Deployment Environment. 4. Prepare the Prerequisite Infrastructure for UDI Deployments UDI deployments require that a properly configured System Center Configuration Manager infrastructure exist prior to installing MDT 2010 and performing deployments. Deploying captured images to the target computer in UDI as described in Deploying Captured Images to Target Computers in UDI. Preparing for UDI deployment to the reference computer as described in Preparing for UDI Deployment to the Reference Computer. 5.249 Microsoft Deployment Toolkit 2010 Update 1 Performing UDI Deployments You perform UDI deployments using System Center Configuration Manager and MDT 2010 within an AD DS domain.

this support is now provided in System Center Configuration Manager 2007 R2 and has been removed in MDT 2010.aspx.0 or later must be installed on any computer on which MDT 2010 is installed for management of UDI deployments. Quick Start Guide for User Driven Installation. Ensure you create a new Microsoft Deployment Toolkit Files package for any new UDI task sequences you create. Run the Remove PXE Filter Wizard. Configuring a System Center Configuration Manager infrastructure to support UDI deployments. but a new Microsoft Deployment Toolkit Files package must be created for new UDI task sequences. After the upgrade process is complete: • Run the Configure ConfigMgr Integration Wizard. see the section.” in the MDT 2010 document. “Step 1: Prepare the Prerequisite Infrastructure. install one or more new instances of MDT 2010 as described in Installing a New Instance of MDT 2010.microsoft. but you cannot use any of the new MDT 2010 task sequence actions or steps. Ensure any UDI task sequences created prior to the upgrade use the Microsoft Deployment Toolkit Files package that existed prior to the upgrade. • Install or Upgrade to MDT 2010 for UDI Deployments The first step in performing UDI deployments is to have at least one instance of MDT 2010 running in your environment. This wizard must be run after the upgrade to register the new components and install the UDI new task sequence templates. • • • • Solution Accelerators microsoft. see Configuration Manager Supported Configurations at http://technet. If your existing environment has: • No computers currently running MDT 2010 or a previous version of MDT or BDD. For more information about: • Hardware and software requirements for System Center Configuration Manager. The existing Microsoft Deployment Toolkit Files package can be used for any UDI task sequences created prior to the upgrade.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 250 Note Windows PowerShell version 1. Install MDT 2010 on each computer that has the Configuration Manager Console installed and that you will use to create or edit task sequences that MDT 2010 generates. create a new UDI task sequence.com/technet/SolutionAccelerators .com/en-us/library/bb680717. upgrade those instances to MDT 2010 as described in Upgrading to MDT 2010. If you had previously installed and configured the PXE filter to support the unknown computer capability in previous versions of MDT. You can modify these UDI task sequences. One or more computers running a previous version of MDT or BDD. To use the new MDT 2010 task sequence actions or steps.

USMT source files used to create a software package that is deployed to the target computers to capture user state migration data. To run the Configure Configuration Manager 2007 Integration Wizard 1. You add these classes by compiling a Managed Object Format (. Operating system packages for the operating systems.mof) file that contains the new class definitions. and then click Configure ConfigMgr 2007 Integration. This wizard copies the appropriate System Center Configuration Manager integration files to the Configuration Manager 2007_root (where Configuration Manager 2007_root is the folder in which System Center Configuration Manager or the Configuration Manager Console is installed). type ConfigMgr_site_code (where ConfigMgr_site_code is the System Center Configuration Manager site code that installs MDT 2010 integration). run the Configure Configuration Manager 2007 Integration Wizard. Note MDT 2010 and MDT 2010 Update 1 support Windows AIK 2. feature packs. type ConfigMgr_server_name (where ConfigMgr_server_name is the name of the System Center Configuration Manager server on which to install MDT 2010 integration). Note The Configuration Manager Console should be closed when performing this procedure. and System Center Configuration Manager 2007 with SP2. Applications that are to be installed as a part of the operating system image or during the deployment of the reference image. Required software includes: • • • • • Operating system source files for each operating system to be deployed to the reference and target computers. and then click OK. and language packs. 3. Windows PE 3.com/technet/SolutionAccelerators . In the Site Code dialog box. The wizard also adds WMI classes for the new MDT 2010 custom actions. This software will be imported or added to deployment shares unless it already exists in the deployment share. The Configure Configuration Manager 2007 Integration Wizard starts. such as security updates. 2. Device drivers for the reference and target computers that are not included as part of the operating system.251 Microsoft Deployment Toolkit 2010 Update 1 Obtain the Software Required by the UDI Deployment Process Collect the software needed during the UDI deployment process. Solution Accelerators microsoft.0. and then point to All Programs. Click Start.0. In the Site Server Name dialog box. Enable Configuration Manager Console Integration for UDI Before you can use the System Center Configuration Manager integration features of MDT 2010. Point to Microsoft Deployment Toolkit.

Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 252 Install and Configure the UDI Web Service UDI supports the ability to automatically discover the applications installed on existing computers in the Refresh Computer deployment scenario. 4. Configure user access for publishing to the UDI web service as described in Configure Publishing Access to the UDI Web Service.NET Framework version 3. the Operating System Deployment (OSD) Setup Wizard identifies the applications installed on the target computer. Troubleshoot installation and configuration problems with the UDI web service as described in Troubleshoot the UDI Web Service. Verify that the target computer meets or exceeds the UDI web service prerequisites as described in Verify the Prerequisites for the UDI Web Service. Install the UDI web service using the UDI Web Services and Database Installation Wizard as described in Install the UDI Web Service.5 is installed. The URL Rewrite Module. To install and configure the UDI web service 1. The Web Services (IIS) server role is installed with the role services listed in Table 128. During the Application Discovery preflight check on the target computer. You can install and configure the UDI web service on one or more computers to provide fault tolerance and scalability. 2.com/technet/SolutionAccelerators . 3. Table 128. The UDI web service acts as a central repository for the applications to be discovered during the Application Discovery preflight check. ensure that the target computer meets or exceeds the following prerequisites: • • • • Microsoft SQL Server 2008 Standard or Enterprise is installed on the same computer or is accessible on another computer. Information for Installing the Web Services (IIS) Server Role Role service Web Server Common HTTP Features Static Content Default Document Directory Browsing Solution Accelerators Status Installed Installed Installed Installed Installed microsoft. Verify the Prerequisites for the UDI Web Service Before installing the UDI web service. Microsoft .

253 Microsoft Deployment Toolkit 2010 Update 1 Role service HTTP Errors HTTP Redirection Application Development ASP.com/technet/SolutionAccelerators Client Certificate Mapping Authentication Not installed .NET Extensibility ASP CGI ISAPI Extensions ISAPI Filters Server Side Includes Health and Diagnostics HTTP Logging Logging Tools Request Monitor Tracing Custom Logging ODBC Logging Security Basic Authentication Windows Authentication Digest Authentication IIS Client Certificate Mapping Authentication URL Authorization Request Filtering IP and Domain Restriction Performance Static Content Compression Dynamic Content Compression Management Tools IIS Management Console Solution Accelerators Status Installed Installed Installed Installed Installed Not installed Not installed Installed Installed Not installed Installed Installed Installed Installed Installed Not installed Not installed Installed Not installed Installed Not installed Not installed Not installed Installed Not installed Installed Installed Not installed Installed Installed microsoft.NET .

and then click Next. and the OSD database in SQL Server. To install the UDI web service 1. Table 129. and then point to All Programs. Point to Microsoft Deployment Toolkit. which UDI deployments use. Accept the default values unless otherwise specified.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 254 Role service IIS Management Scripts and Tools Management Service IIS 6 Management Compatibility IIS 6 Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console FTP Publishing Service FTP Server FTP Management Console Status Not installed Not installed Installed Installed Installed Not installed Not installed Not installed Not installed Not installed Install the UDI Web Service Install the UDI web service using the UDI Web Services and Database Installation Wizard. This wizard creates the OSDConfigService virtual directory in Microsoft Internet Information Services (IIS). Click Start. Click I accept the terms in the License Agreement. Click Next. Information for Completing the UDI Web Services and Database Installation Wizard On this wizard page UDI Web Services & Database Installation Wizard Read the Microsoft Software License Terms Custom Setup Solution Accelerators Do this Click Next. 2. and then click Install UDI Config Service. The virtual directories are databases that the UDI web service uses to store setup configuration that UDI employs.com/technet/SolutionAccelerators . microsoft. The UDI Web Services and Database Installation Wizard starts. the OSDConfigServiceSimple virtual directory in IIS. Complete the UDI Web Services and Database Installation Wizard using the information in Table 129.

Save the Web. c. and then go to installation_folder (where installation_folder is the folder in which you installed the UDI web service). type sql_server (where sql_server is the name of the computer running SQL Server instance). Configure Publishing Access to the UDI Web Service By default. On the computer on which the UDI web service is installed. the UDI Web Services and Database Installation Wizard allows anonymous users to publish to the UDI web service from the UDI Wizard Designer. In SQL Server. a. Click Next. In the Create folder dialog box. In the Change current destination folder dialog box. <authorization> <remove users="*" roles="" verbs="" /> <add accessType="Allow" roles="Authenticated Users" /> </authorization> 4. In the Web.config file for the web service. To configure publishing access to the UDI web service 1. Click OK. Open the Web. Name the new folder. You can configure the users who can publish to the UDI web service by modifying the Web. 2. Configuration Web Services Database Ready to Install The OSD Setup wizard has completed successfully The UDI Web Services and Database Installation Wizard finishes. Click Install. Click Browse. modify the value for roles to include the appropriate security group based on the publishing needs of your organization.255 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Requirements OSD Designer Web Services Do this Click Next. 3. d. and the UDI web service and database are installed and configured on the computer. open Windows Explorer. Solution Accelerators microsoft. Click Finish.config file.com/technet/SolutionAccelerators .config file. in the <authorization> element. 1. b. 2. click Create a new folder.config file. click Yes.

NET mappings are properly registered by running aspnet_regiis.com/technet/SolutionAccelerators . To prepare for deployment to the reference computer 1. For more information about determining the number of images required in your organization (and subsequently the number of reference computers required). try the following solutions: • A 404. Create a reference computer for each image that you want to create for deployment to the target computers. For more information about the use of reference computers in MDT 2010 deployments.50727 folder from an elevated Command Prompt window.NET\Framework\v3. you will deploy the captured image of your reference computer to the appropriate target computers. 6.exe –i in the %Windir %\Microsoft. see Using Reference Computers in MDT 2010 Deployments. perform the following troubleshooting tasks to help resolve the problem: • Open the URL for the UDI web service in Internet Explorer.svc extension. • • When connecting to the UDI web service from Windows Server 2008. and then capturing an image of that computer.NET mappings.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 256 5. see Estimating Storage Requirements for System Center Configuration Manager Distribution Points. Doing so should register the ASP. Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Solution Accelerators microsoft.0\Windows Communication Foundation folder from an elevated Command Prompt window. In addition.NET\Framework\v2. If you encounter an error. Start the website that contains the UDI web service folder. you can use existing operating system images in WIM format.3 HTTP error is typically the result of Windows Communications Foundation (WCF) Multipurpose Internet Mail Extensions (MIME) types not being registered correctly. Later in the UDI deployment process. add the UDI web service site to the Local intranet zone in Internet Explorer. always start by creating a reference computer.exe –i in the %Windir %\Microsoft. as the web service requires.0. Troubleshoot the UDI Web Service If you have problems connecting to the UDI web service. Ensure that the Microsoft ASP. Stop the website that contains the UDI web service folder. Preparing for UDI Deployment to the Reference Computer Regardless of the UDI deployment scenario you are performing. Doing so should register the WCF MIME type for the . Ensure that the WCF MIME types are registered correctly by running ServiceModelReg.

Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. which is the same process for UDI and ZTI deployments. including the following: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. Do not enable BitLocker Drive Encryption on the reference computer. Tip Create the task sequence for deploying to the reference computer based on the UserDriven Installation task sequence template included in MDT 2010. Note The UDI deployment process is unable to perform Sysprep operations on a target computer that is encrypted by using BitLocker Drive Encryption. Important If you are capturing an image of the reference computer. and enable BitLocker Drive Encryption on the target computers only after the target operating system is completely deployed. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. which is the same process for UDI and ZTI deployments. When performing this step in a production environment.ini file for the task sequence by specifying DoCapture=YES. that the new UDI task sequence uses are properly distributed to the assigned distribution points as described in Managing Distribution Points in Configuration Manager Console. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. select the appropriate distribution points for the network. Note Most production networks have multiple distribution points. Solution Accelerators microsoft. • 4. which is the same process for UDI and ZTI deployments. select the appropriate distribution points for the network. When performing this step in a production environment. which is the same process for UDI and ZTI deployments. Customize the Operating System UDI Task Sequence Steps in Configuration Manager Console Deployment (OSD) Setup Wizard configuration files to the needs of your organization as described in Configure the Operating System Deployment (OSD) Setup Wizard Behavior 7. you must at least add the DoCapture property to the Customsettings.257 Microsoft Deployment Toolkit 2010 Update 1 Sequence Wizard in Configuration Manager Console as described in Creating a UDI Task Sequence using MDT 2010 Task Sequence Templates. Ensure that all packages. including operating system deployment packages. Configure System Center Configuration Manager to contain the appropriate software for deployment to the reference computer. which is the same process for UDI and ZTI deployments. Note Most production networks have multiple distribution points. 2. 6. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. 3.com/technet/SolutionAccelerators . 5.

To prepare for UDI deployment to target computers 1. deploy them to the target computers. and then capture an image of the reference computer. create one or more task sequences for deploying the captured images. Create an advertisement for the reference computer task sequence as described in Managing Advertisements in Configuration Manager Console. Create a collection that contains the reference computer as described in Managing Computer Collections in Configuration Manager Console. Add the reference computer to the System Center Configuration Manager site database as described in Manually Adding Computers to the Site Database in Configuration Manager Console. 2. prepare Windows Deployment Services to start the appropriate Windows PE images that will in turn start the UDI deployment process to the target computers as described in Preparing Windows Deployment Services for UDI Deployments. ensure that the necessary deployment resources exist. 3. which is the same process for UDI and ZTI deployments. Prepare network shares for storing migration data and MDT 2010 deployment logs as described in Preparing the MDT 2010 Migration Resources. which is the same process for UDI and ZTI deployments. To deploy to and capture an image of the reference computer 1.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 258 Deploying to and Capturing an Image of the Reference Computer Using UDI After the distribution points are updated. Preparing for UDI Deployment to Target Computers After the images of the reference computers are captured. which is the same process for UDI and ZTI deployments. and customize the MDT 2010 deployment process. Solution Accelerators microsoft. In preparation for deploying the captured images to the target computers. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. 5. 2. Create a task sequence bootable media disk by using the Task Sequence Media Wizard as described in Creating Task Sequence Bootable Media. and applications to the reference computer. operating system packages.com/technet/SolutionAccelerators . The task sequence created earlier will deploy the target operating system. 4. Start the reference computer with the task sequence bootable media disk as described in Deploying an Operating System Using Task Sequence Bootable Media. advertise the task sequence to the reference computer and start the reference computer with the bootable Windows PE image created earlier in the process. Optionally. device drivers.

Prepare the UDI task sequences. the MDT 2010 configuration files. which is the same process for UDI and ZTI deployments. Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager Console as described in Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates. Use the User-Driven Installation task sequence template to deploy the captured image of the reference computer to the target computer. Create additional distribution points to help in larger deployments as described in Managing Distribution Points in Configuration Manager Console. and specify the fully qualified UNC path to the WIM image captured from the reference computer. Prepare for the Refresh Computer Deployment Scenario to Target Computers Using UDI. There is no user migration information to save and restore and no existing file systems to preserve. you deploy a new installation of a Windows operating system to a new computer. To prepare for the New Computer deployment scenario to target computers 1. and the MDT DB for each deployment scenario as described in the following sections: • Prepare for the New Computer Deployment Scenario to Target Computers Using UDI. see Identifying Deployment Scenarios. For more information about MDT 2010 deployment scenarios. which is the same process for UDI and ZTI deployments.259 Microsoft Deployment Toolkit 2010 Update 1 3. microsoft. Table 130.com/technet/SolutionAccelerators Solution Accelerators . but ensure that you specifically follow the configuration settings on the wizard pages listed in Table 130 and select the appropriate values on the other wizard pages based on your organization’s requirements. any combination of these deployments scenarios might be necessary. Information for Completing the Create Microsoft Deployment Task Sequence Wizard for Performing New Computer Deployment Scenario Using UDI On this wizard page OS Image Do this Select Create a new OS image. Prepare for the New Computer Deployment Scenario to Target Computers Using UDI In the New Computer deployment scenario. Tip Create the task sequence for deploying to the reference computer based on the UserDriven task sequence template included in MDT 2010. which is the same process for UDI and ZTI deployments. the Operating System Deployment (OSD) Setup Wizard configuration files. • Depending on the target computers in your organization. 4.

Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. Optionally. which is the same process for UDI and ZTI deployments. 7. select the appropriate distribution points for the network. When performing this step in a production environment. Ensure that all packages. 5. which is the same process for UDI and ZTI deployments. Configure System Center Configuration Manager to contain the appropriate software for deployment to the reference computer. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. 3. Solution Accelerators microsoft. 9. Note Most production networks have multiple distribution points. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. that the new UDI task sequence uses are properly distributed to the assigned distribution points as described in Managing Distribution Points in Configuration Manager Console. When performing this step in a production environment. customize the MDT DB to the needs of your organization as described in Performing Deployments Using the MDT DB (if you are using the MDT DB to provide MDT 2010 configuration information). Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console.com/technet/SolutionAccelerators . select the appropriate distribution points for the network. Note Most production networks have multiple distribution points. that the new UDI task sequence uses are properly distributed to the assigned distribution points as described in Managing Distribution Points in Configuration Manager Console. 6. 8. select the appropriate distribution points for the network. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. Note Most production networks have multiple distribution points. including operating system deployment packages. Customize the Operating System Deployment (OSD) Setup Wizard configuration files to the needs of your organization as described in Configure the Operating System Deployment (OSD) Setup Wizard Behavior. • 4.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 260 2. including operating system deployment packages. When performing this step in a production environment. Ensure that all packages.

which is the same process for UDI and ZTI deployments. There is user migration information to save and restore but no existing file systems to preserve. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 3. To prepare for the Refresh Computer deployment scenario to target computers 1. a computer is refreshed. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. 4. including computers that must be re-imaged for image standardization or to address a problem. Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager console as described in Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. which is the same process for UDI and ZTI deployments. but ensure that you follow the configuration settings on the wizard pages listed in Table 131 and select the appropriate values on the other wizard pages for your organization’s requirements. Solution Accelerators microsoft. Optionally. which is the same process for UDI and ZTI deployments.com/technet/SolutionAccelerators • . customize the MDT 2010 configuration files or the MDT DB to the needs of your organization as described in: • Configuring MDT 2010 Deployments. and specify the fully qualified path to the WIM image captured from the reference computer. Configure System Center Configuration Manager to contain the appropriate software for deployment to the target computer. Table 131. Tip Create the task sequence for deploying to the reference computer based on the UserDriven task sequence template included in MDT 2010. Information for Completing the Create Microsoft Deployment Task Sequence Wizard for Performing Refresh Computer Deployment Scenario Using UDI On this wizard page OS Image Do this Select Create a new OS image. Use the User-Driven task sequence template to deploy the captured image of the reference computer to the target computer. • Performing Deployments Using the MDT DB.261 Microsoft Deployment Toolkit 2010 Update 1 Prepare for the Refresh Computer Deployment Scenario to Target Computers Using UDI In the Refresh Computer deployment scenario. 2.

” in Configuration Manager Documentation Library. 6. which is the same process for UDI and ZTI deployments. that the new UDI task sequence uses are properly distributed to the assigned distribution points as described in Managing Distribution Points in Configuration Manager Console. Note Most production networks have multiple distribution points. and ensure that the collection includes the target computers requiring the corresponding deployment scenario. Configure the behavior of the Operating System Deployment (OSD) Setup Wizard to the needs of your organization as described in Configure the Operating System Deployment (OSD) Setup Wizard Behavior. Add the target computer to the System Center Configuration Manager site database: • Manually. Deploy the captured image of the reference computer to target computers for each respective deployment scenario in your organization. When performing this step in a production environment. which is the same process for UDI and ZTI deployments. Ensure that all packages. which is installed with System Center Configuration Manager. select the appropriate distribution points for the network. which is the same process for UDI and ZTI deployments. 2. Create a collection that contains the target computers as described in Managing Computer Collections in Configuration Manager Console. To deploy the capture image of the reference computer to the target computers 1. When performing this step in a production environment. including operating system deployment packages. Note Create a collection for each MDT 2010 deployment scenario to be performed. then this step is not necessary. Note Most production networks have multiple distribution points. which is the same process for UDI and ZTI deployments. as described in Manually Adding Computers to the Site Database in Configuration Manager Console. Deploying Captured Images to Target Computers in UDI The deployment of the captured images to the target computers is slightly different for each MDT 2010 deployment scenario using UDI. 7. Automatically as described in the section. “How to Deploy Operating Systems Using Unknown Computer Support. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. • Note If the target computers already exist in the System Center Configuration Manager Site database. select the appropriate distribution points for the network.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 262 5. Solution Accelerators microsoft.

Prepare Windows Deployment Services to start the appropriate Windows PE images that will in turn start the UDI deployment process to the target computers as described in Preparing Windows Deployment Services for UDI Deployments. Either method starts Windows PE on the target computer and initiates the UDI deployment process. Deploy the captured reference computer image to the target computers for each deployment scenario as described in: • • Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using UDI. Note This wizard will not appear if you configure UDI to perform a PXE boot and have configured a mandatory advertisement or if only one task sequence is advertised to the target computer. Solution Accelerators microsoft.263 Microsoft Deployment Toolkit 2010 Update 1 3. 2. At the end of the process. 5. The Task Sequence Wizard starts. the captured image of the reference computer is deployed on the target computer. 4 Provide a method for starting the target computers by doing any combination of the following: • Create a task sequence bootable media disk using the Task Sequence Media Wizard as described in Creating Task Sequence Bootable Media. any combination of deployments scenarios might be necessary. To deploy the capture images to the target computers in the New Computer Deployment Scenario Using UDI 1. Complete the Task Sequence Wizard.com/technet/SolutionAccelerators . ensuring that you specifically follow the configuration settings on the wizard pages listed in Table 132 and select the appropriate values on the other wizard pages for your organization’s requirements. which is the same process for UDI and ZTI deployments. see Identifying Deployment Scenarios. Create an advertisement for the target computer task sequences as described in Managing Advertisements in Configuration Manager Console. Start the target computer with the task sequence bootable media created earlier in the process or from Windows Deployment Services. which is the same process for UDI and ZTI deployments. Deploy Captured Images to Target Computers in the New Computer Deployment Scenario Using UDI Start the target computer with the task sequence bootable media created earlier in the process or from Windows Deployment Services. which is the same process for UDI and ZTI deployments. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using UDI. • Depending on the target computers in your organization. For more information about the MDT 2010 deployment scenarios.

OSDResults. The task sequence starts. 2. 3. as described in Running the Operating System Deployment (OSD) Setup Wizard. the OSD Results program. and the operating system deployment starts. installs any applications. The task sequence restarts the computer. Finally. Eventually. The task sequence runs in Windows PE to capture user state migration data. starts Windows PE. To deploy the capture images to the target computers in the Refresh Computer Deployment Scenario Using UDI 1. Complete the Operating System Deployment (OSD) Setup Wizard by selecting the appropriate values on the wizard pages for your organization’s requirements. the task sequence starts the Operating System Deployment (OSD) Setup Wizard. The task sequence restarts the computer. installs any packages. The target computer is now deployed. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using UDI Start UDI by running the Configuration Manager advertisement for capturing the user state migration data you created earlier in the process. Eventually the task sequence starts the Operating System Deployment (OSD) Setup Wizard. starts the new operating system.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 264 Table 132. Information for Completing the Task Sequence Wizard in the New Computer Deployment Scenario Using ZTI On this wizard page Select a Task Sequence Do this Select the task sequence you created for the target computer deployment for the New Computer deployment scenario. run the Configuration Manager advertisement for capturing the Refresh Computer deployment scenario that you created earlier in the deployment process. and then initiates installation of the new operating system. and performs any other actions configured in the task sequence. On the target computer. This task sequence runs in the current operating system on the existing target computer.com/technet/SolutionAccelerators . Solution Accelerators microsoft. restores the user state migration data. Complete the Operating System Deployment (OSD) Setup Wizard by selecting the appropriate values on the wizard pages for your organization’s requirements as described in Running the Operating System Deployment (OSD) Setup Wizard. runs and displays the results of the deployment.exe. The wizard starts.

Using the Microsoft Deployment Toolkit: Managing UDI Deployments 265 Managing UDI Deployments You manage UDI deployments through the Configuration Manager Console and the UDI Wizard Designer. which is the same process for UDI and ZTI deployments. Managing operating systems for UDI deployments in the Configuration Manager Console as described in Managing Operating Systems in Configuration Manager Console. Deploying an operating system using task sequence bootable media as described in Deploying an Operating System Using Task Sequence Bootable Media. Managing advertisements for UDI as described in Managing Advertisements in Configuration Manager Console. Manually adding computers to the site database for UDI as described in Manually Adding Computers to the Site Database in Configuration Manager Console. Managing computer collections for UDI as described in Managing Computer Collections in Configuration Manager Console. Creating task sequence bootable media for UDI as described in Creating Task Sequence Bootable Media. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. The wizard used to create UDI task sequences are integrated into the Configuration Manager Console. Manage UDI deployments by: • Creating a new task sequence for UDI deployments using the Create Microsoft Deployment Task Sequence Wizard as described in Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. Creating boot images for use with UDI using the Create Image Using Microsoft Deployment Wizard as described in Creating ZTI Boot Images. which is the same process for UDI and ZTI deployments. Managing device drivers for UDI deployments in the Configuration Manager Console as describe in Managing Device Drivers in Configuration Manager Console. which is the same process for UDI and ZTI deployments. • • • • • • • • • . which is the same process for UDI and ZTI deployments. You use the Deployment Workbench in UDI deployments only to configure the MDT DB. Managing software packages for UDI in the Configuration Manager Console as described in Managing Software Packages in Configuration Manager Console. You can use the UDI Wizard Designer to configure the behavior of the Operating System Deployment (OSD) Setup Wizard. which is the same process for UDI and ZTI deployments.

The template files are located in the install_folder\SCCM folder (where install_folder is the folder in which MDT 2010 was installed).com/technet/SolutionAccelerators Solution Accelerators . Configuring UDI task sequence steps that perform server role–related actions as described in Configuring Server Role Task Sequence Steps for ZTI. and a description of the template.xml Select this template to Deploy to target computers using UDI for all scenarios except the Replace Computer microsoft. • Identify the UDI Task Sequence Templates in MDT 2010 Table 133 lists the UDI task sequences templates included in MDT 2010. the file name for each template. UDI Task Sequence Templates Included in MDT 2010 Template UserDriven Installation Task File name SCCM_UDI. which is the same process for UDI and ZTI deployments. Identifying the packages and images that the UDI task sequence templates require as described in Identify the Packages and Images Required by the UDI Task Sequence Templates.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 266 • Managing distribution points for UDI as described in Managing Distribution Points in Configuration Manager Console. which is the same process for UDI and ZTI deployments. Table 133. MDT 2010 includes task sequence templates that you can use to deploy the reference and target computers. Configuring the Operating System Deployment (OSD) Setup Wizard behavior by customizing the Operating System Deployment (OSD) Setup Wizard configuration file as described in Configure the Operating System Deployment (OSD) Setup Wizard Behavior • • • Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates Use the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager Console to create task sequences in System Center Configuration Manager that are integrated with MDT 2010. Creating UDI task sequences as described in Create UDI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard. which is the same process for UDI and ZTI deployments. Configuring individual UDI task sequence steps as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. Create UDI task sequences using the MDT 2010 task sequence templates by: • • Identifying the UDI task sequence templates that are a part of MDT 2010 as described in Identify the UDI Task Sequence Templates in MDT 2010.

Note Any configuration values provided in the Operating System Deployment (OSD) Setup Wizard or in task sequence variables will override values specified in this wizard. Click Start. doing so is not recommended. click Create Microsoft Deployment Task Sequence. Although you can manually create the task sequences. as described in Identify the Packages and Images Required by the MDT 2010 Task Sequence Templates. doing so is not recommend. Accept the default values unless otherwise specified.267 Microsoft Deployment Toolkit 2010 Update 1 Template Sequence File name Select this template to scenario. In the Configuration Manager Console console tree. point to Configuration Manager 2007. Information for Completing the Create Microsoft Deployment Task Sequence Wizard for Creating a UDI Task Sequence On this wizard page Choose Template Do this 1. Note Always use the Create Microsoft Deployment Task Sequence Wizard to create task sequences based on the MDT 2010 task sequence templates. and then point to All Programs. Identify the Packages and Images Required by the UDI Task Sequence Templates The UDI task sequence templates require the same packages and images as required by ZTI deployments. Point to Microsoft System Center. Note Always use the Create Microsoft Deployment Task Sequence Wizard to create task sequences. select task_sequence_template (where microsoft. go to Site Database/Computer Management/Task Sequences. In the Actions pane. Table 134. To create a UDI task sequence using the Create Microsoft Deployment Task Sequence Wizard 1. After completing the wizard. Create UDI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard The Create Microsoft Deployment Task Sequence Wizard substitutes the packages and images selected for the placeholders in the task sequence templates. the new task sequence references the appropriate packages and images. 3. 2. Complete the Create Microsoft Deployment Task Sequence Wizard for creating a UDI task sequence using the information in Table 134.com/technet/SolutionAccelerators Solution Accelerators . and then click ConfigMgr Console. Although you can manually import the task sequence templates. 4. In The following SCCM task sequence templates are available. The Create Microsoft Deployment Task Sequence Wizard starts.

b. 3. Click Next. Click Join a domain. 1. Choose Template: General 1. 2.com/technet/SolutionAccelerators Choose Template: Details Solution Accelerators .Using the Microsoft Deployment Toolkit: Managing UDI Deployments 268 On this wizard page Do this task_sequence_template is the task sequence template to be selected from Table 132). type user_name (where user_name is the name of the registered user that appears in the Windows operating system microsoft. Select Join a workgroup. This account must be a member of the Domain Admins group in the domain or have sufficient delegated permissions). In Task sequence comments. If you select this option. Click Next. In User name. type password (where password is the password for the user account). type comment (where comment is descriptive text that describes the purpose of the task sequence). The Windows User Account dialog box appears. 3. 2. in User name. In Domain. Click Set. and then click OK. In Task sequence name. perform the following steps: a. In the Windows User Account dialog box. The other option is Join a workgroup. in Workgroup. The other option is Join a domain. In Password and Confirm password. type workgroup_name (where workgroup_name is the name of the workgroup to join). type domain_name\user_name (where user_name is the name of the user account used to join the computer to the domain and domain_name is the name of the domain in which the user account resides. 2. d. type task_sequence_name (where task_sequence_name is the name of the task sequence displayed in the Configuration Manager Console). If you select this option. c. type domain_name (where domain_name is the name of the workgroup to join).

In Password and Confirm password. This feature is found only in microsoft. and then click OK. Click Set. including the name of the WIM file). Click Next. b. in User name. In the Windows User Account dialog box.vbs script. In Capture destination. type domain_name\user_name (where user_name is the name of the user account that has Write permission to the folder specified in Capture destination and domain_name is the name of the domain in which the user account resides). type organization_name (where organization_name is the name of the registered organization that appears in the Windows operating system properties). c. which allows the user to confirm partitioning and formatting the disks on the target computer. type unc_path (where unc_path is the fully qualified UNC path for the location of the WIM file. In Product key. In Organization name. Click Next. The Windows User Account dialog box appears. if required).269 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this properties). 2. 4. type product_key (where product_key is the product key for operating system. The other option is This task sequence will never be used to capture and image. type password (where password is the password for the user account). 3. perform the following steps: a. Select This task sequence may be used to capture and image. d. Note UDI task sequences start with the Confirmation to Partition Disk task sequence step. 6. Choose Template: Capture Settings 1. 5. If you select this option.com/technet/SolutionAccelerators Boot Image Solution Accelerators . The other option is This task sequence may be used to capture and image. Select This task sequence will never be used to capture and image. The task sequence step runs the ZTIConfirmDiskpart.

type package_name (where package_name is the name to be given to the boot image package). Boot Image: Image Options Solution Accelerators Note This wizard page appears only if you select Create a new boot image package on the Boot Image wizard page. The Select a Package dialog box appears. The other option is Create a new boot image package. 2. in Package source to be created. In Version. In Select a Package dialog box. If you select this option. In Comments. click package_name (where package_name is the name of the existing boot image). 1. b. Click Browse.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 270 On this wizard page Do this boot images created in MDT 2010 Update 1 and later. 3. Tip You can also click Browse to locate the UNC path. and then click OK. 1. type comment_text (where comment_text is descriptive information about the boot image package). The Configuration Manager service account must have permission to modify the contents of this UNC path to update the boot images. microsoft. type version_number (where version_number is the version number to be assigned to the boot image package). Select Specify an existing boot image. 4. perform the following steps: a. Boot Image: General Settings Note This wizard page appears only if you select Create a new boot image package on the Boot Image wizard page. Click Next. 3. If you select this option. 2. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). In Name. Click Next. Ensure that the Configuration Manager service account has the appropriate permission on this network shared folder. The other option is Create a new boot image package.com/technet/SolutionAccelerators . Select Create a new boot image package.

• Cleared. or Korean [KO-KR]) to add support for the optional fonts. Japanese [JA-JP]. The other option is Create a new Microsoft Deployment Toolkit files package. type unc_path (where unc_path is the fully qualified UNC path to the bitmap file that you want to use as the background). Chinese [ZH-HK]. If the check box is: • Selected. • Cleared. 5. 3. the ADO components are not added to the boot image. click Browse to find the bitmap file. click platform (where platform is the platform architecture for the boot image— x86 or X64). Click Browse. Select or clear the Add media hook files to enable the Deployment Wizard for this boot media check box. the media hook files are added to the boot image.271 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this 1. The Select a Package dialog box appears. the media hook files are not added to the boot image. In Platform. this check box is selected. If the check box is: • Selected. which can be Chinese [ZH-CN]. Click Next. Note Scripting. In the Select a Package dialog box. Note Alternatively. Select or clear the ADO check box if you want to add ADO components to the boot image. By default. Chinese [ZH-TW]. b. 4. which is needed to access SQL Server databases such as the MDT DB. HTA. perform the following steps: a.com/technet/SolutionAccelerators Solution Accelerators . MDT Package 1. If you select this option. click package_name (where package_name is the name of the existing package that is microsoft. XML. the ADO components are added to the boot image. 2. In Custom background bitmap file (UNC Path). and WMI support are always added to the boot image. 6. Select Specify an existing Microsoft Deployment Toolkit files package. Select or clear the font check box (where font is the name of the font to be added.

Select Create a new Microsoft Deployment Toolkit files package. MDT Package: MDT Details Note This wizard page appears only if you select Create a new Microsoft Deployment Toolkit files package on the MDT Package wizard page. OS install packages contain all the necessary files to install the operating system. Tip You can also click Browse to locate the UNC path. Also. OS image packages are created from WIM files either from distribution media or from custom WIM files you have created. Click Next. you can select (or create) OS image packages or OS install packages. in Package source to be created. If you want to deploy an image with a different index. and then click OK. 3. In Version. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). 4.xml in the Settings package: <MetaData> Solution Accelerators microsoft. If you select this option. if you select a SKU that is different from the default SKU.com/technet/SolutionAccelerators . remove the following section from Unattend. Click Next. type package_name (where package_name is the name to be given to the Microsoft Deployment Toolkit files package). 2. OS Image On this wizard page. type comment_text (where comment_text is descriptive information about the Microsoft Deployment Toolkit files package). 2. change the configuration of the Apply Operating System Image task sequence step. 1. type version_number (where version_number is the version number to be assigned to the Microsoft Deployment Toolkit files package). Note The UDI task sequence templates always configure the Apply Operating System Image task sequence step to deploy the image index equal to 1. In Name. The other option is Specify an existing Microsoft Deployment Toolkit files package. In Comments.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 272 On this wizard page Do this based on MDT 2010 Update 1). 3.

In Select a Package dialog box. b. click package_name (where package_name is the name of the existing package). If you select this option. Specify an existing OS installation package. Click Browse. or Create a new OS install package. or Create a new OS install package. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the WIM file is located. perform the following steps: a. perform the following steps: a. Select Specify an existing OS installation package. Solution Accelerators microsoft. Click Browse. In OS image file (WIM) location. Select Specify an existing OS image. The Select a Package dialog box appears. Tip You can also click Browse to locate the WIM file. The other options are Specify an existing OS image. perform the following steps: a.273 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this <Key>/image/index</Key> <Value>1</Value> </MetaTag> 1. The other options are Create a new OS image. The Select a Package dialog box appears. 2. including the name of the WIM file). In Package source folder to be created.com/technet/SolutionAccelerators . If you select this option. or Create a new OS install package. and then click OK. Specify an existing OS installation package. The other options are Specify an existing OS image. Create a new OS image. 3. Select Create a new OS image. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). b. Tip You can also click Browse to locate the UNC path. If you select this option.

type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). Click Next. In Package source folder to be created.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 274 On this wizard page Do this b.com/technet/SolutionAccelerators . In OS installation folder location. which are then used to create the package. and then click OK. type version_number (where version_number is the version number to be assigned to the package). or Specify an existing OS installation package. In Name. Create a new OS image. click package_name (where package_name is the name of the existing package). type package_name (where package_name is the name to be given to the package). In Name. In the Select a Package dialog box. 1. b. type package_name (where Solution Accelerators microsoft. type comment_text (where comment_text is descriptive information about the package). The other options are Specify an existing OS image. Tip You can also click Browse to locate the UNC path. perform the following steps: a. 4. Select Create a new OS install package. In Version. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). 3. 2. 5. 4. In Comments. Click Next. OS Image: Image Details Note This wizard page appears only if you select Create a new OS image on the OS Image wizard page. If you select this option. OS Image: Install Source Note This wizard page appears only if you select Create a new OS install package on the OS Image wizard page. 1. Tip You can also click Browse to locate the UNC path. Note The OS installation folder contents are copied from the specified UNC location to the package source folder.

perform the following steps: a. The Request state store task automatically determines the state migration point to use for storing user state migration data.com/technet/SolutionAccelerators . For more information. Click Browse. USMT Package 1. 2. Click Next. see the section. The other option is Create a new ConfigMgr client package. click package_name (where package_name is the name of the existing package). 3. b. 3. Select Specify an existing USMT package. type comment_text (where comment_text is descriptive information about the package). The other option is Create a new USMT package. “How to Capture and Restore User State. click package_name (where package_name is the name of the existing package). Note You cannot specify the location for storing the user state migration data in the CustomSettings. In the Select a Package dialog box. If you select this option. and then Solution Accelerators microsoft. type version_number (where version_number is the version number to be assigned to the package). 4. The Select a Package dialog box appears. In Version. In Comments. In the Select a Package dialog box.ini file for UDI. perform the following steps: a. Select Specify an existing ConfigMgr client package. If you select this option.” in the Configuration Manager Documentation Library.275 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this package_name is the name to be given to the package). Client Package 1. Click Next. Click Browse. and then click OK. The Select a Package dialog box appears. b. 2. The other option is Specify an existing ConfigMgr client package. which is installed with System Center Configuration Manager. Select Create a new ConfigMgr client package.

Note USMT can only back up and restore locally cached user profiles. type comment_text (where comment_text is descriptive information about the package). 2.aspx. b. The other option is Create a new settings package. type manufacturer_name (where manufacturer_name is the name of the software manufacturer in the package). Select Specify an existing settings package. Click Next. 3. For more information on using roaming profiles.microsoft. In the Select a Package dialog box. perform the following steps: a. The Select a Package dialog box appears.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 276 On this wizard page Do this click OK. In Comments. In Version. If you select this option. USMT Package: USMT Details Note This wizard page appears only if you select Create a new USMT package on the USMT Package wizard page. type version_number (where version_number is the version number to be assigned to the package). Select Create a new USMT package. not network copies. type language (where language is the language of the package). 1. In Language. 6. type package_name (where package_name is the name to be given to the package). type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). In Manufacturer. In Name. 5. 2. click microsoft. If you select this option. Settings Package 1.10). in Package source to be created. see the Managing Roaming User Data Deployment Guide at http://technet. Click Browse. Click Next. 3. Tip You can also click Browse to locate the UNC path. The other option is Specify an existing USMT package.com/technet/SolutionAccelerators Solution Accelerators . 4.com/enus/library/cc766489(WS. Select this option for Windows Vista or later operating systems.

type path (where path is the fully qualified path for the location of the folder in which the USMT source files reside). Click Next. 6. In Manufacturer. In Language. Click Create a new settings package. and then click OK. The other option is Specify an existing settings package. In Version. type package_name (where package_name is the name to be given to the package). In Path to USMT executables and related files. type language (where language is the language of the package).com/technet/SolutionAccelerators . 3. type comment_text (where comment_text is descriptive information about the package). 1. In Name. b. Click Next. type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package). Settings Package: Settings Details Note This wizard page appears only if you select Create a new settings package on the Settings Package wizard page. 2. In Comments. type version_number (where version_number is the version number to be assigned to the package). 5. Tip You can also click Browse to locate the UNC path. perform the following steps: a.277 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this package_name (where package_name is the name of the existing package). Tip You can also click Browse to locate the path. type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored). Summary Click Next. 2. 3. In Package source to be created. 4. Solution Accelerators microsoft. If you select this option.

Configure the Operating System Deployment (OSD) Setup Wizard behavior by performing the following steps in the UDI Wizard Designer: • Create a new Operating System Deployment (OSD) Setup Wizard configuration file as described in Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. Configure the UDI Wizard task sequence step to use a file other than the UDIWizard_Config.xml file using the UDI Wizard Designer. Note Create a separate version of the UDIWizard_Config.xml file as described in Override the Configuration File Used by the Operating System Deployment (OSD) Setup Wizard. Configure the behavior for the Preflight page in the UDI Wizard Designer as described in Configure the Behavior for the Preflight Page Using the UDI Wizard Designer. the step also references the UDIWizard_Config. which controls the behavior of the Operating System Deployment (OSD) Setup Wizard and is stored in the Scripts folder of the MDT 2010 files package. Open an existing Operating System Deployment (OSD) Setup Wizard configuration file as described in Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Open an Operating System Deployment (OSD) Setup Wizard configuration file from a UDI web service as described in Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service.xml file for each set of configuration settings for the Operating System Deployment (OSD) Setup Wizard. You can customize the UDIWizard_Config. The Create Microsoft Deployment Task Sequence Wizard closes when the UDI task sequence is created.xml file. Configure the behavior for the Computer page in the UDI Wizard Designer as described in Configure the Behavior for the Computer Page Using the UDI Wizard Designer.com/technet/SolutionAccelerators • • • • • • • Solution Accelerators . When a task sequence step runs the Operating System Deployment (OSD) Setup Wizard.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 278 The Summary wizard page displays a status bar that shows the progress of the tasks defined in the wizard. Configure the Operating System Deployment (OSD) Setup Wizard Behavior The User-Driven Installation task sequence template includes task sequence steps that run the Operating System Deployment (OSD) Setup Wizard. Publish an Operating System Deployment (OSD) Setup Wizard configuration file to a UDI web service as described in Publish an Existing Operating System Deployment (OSD) Setup Wizard Configuration File to a UDI Web Service. microsoft. Configure the behavior for the Welcome page using the UDI Wizard Designer as described in Configure the Welcome Page Behavior Using the UDI Wizard Designer.

• • • • • • • Configure the behavior for the Summary page in the UDI Wizard Designer as described in Configure the Behavior for the Summary Page Using the UDI Wizard Designer. Configure the software installation behavior using the: • Settings and Categories page in the UDI Wizard Designer as described in Configure Software Installation Behavior Using the Settings and Categories Page in the UDI Wizard Designer. Configure the behavior for the Volume page in the UDI Wizard Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer. Create a new Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer.com/technet/SolutionAccelerators .xml file. To create a new Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer Solution Accelerators microsoft. Configure the behavior for the Language page in the UDI Wizard Designer as described in Configure the Behavior for the Language Page Using the UDI Wizard Designer. Package Selection page in the UDI Wizard Designer as described in Configure Software Installation Behavior Using the Package Selection Page in the UDI Wizard Designer. OSD Applications page in the UDI Wizard Designer as described in Configure Software Installation Behavior Using the OSD Applications Page in the UDI Wizard Designer.279 Microsoft Deployment Toolkit 2010 Update 1 • Configure the behavior for the User Configuration page in the UDI Wizard Designer as described in Configure the Behavior for the User Configuration Page in Using UDI Wizard Designer. Preview the behavior of the wizard pages in the Operating System Deployment (OSD) Setup Wizard using the Preview OSDSetupWizard menu item in the UDI Wizard Designer as described in Preview the Operating System Deployment (OSD) Setup Wizard Behavior Using the UDI Wizard Designer. • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File The Operating System Deployment (OSD) Setup Wizard displays wizard pages based on the configuration options specified in the UDIWizard_Config. Tip Create a new MDT 2010 files package and corresponding package source for each unique configuration of the UDIWizard_Config.xml file in the Scripts folder of the MDT 2010 files package specified in the task sequence. Configure the behavior of the Application Discovery preflight check as described in Configure Application Discovery Preflight Check Behavior.

5. In the Save As dialog box. The UDI Wizard Designer starts. In the Open dialog box. and then click Open Configuration.xml file in the Scripts folder of the MDT 2010 files package specified in the task sequence. Open an existing Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer. 4. and then click UDI Wizard Designer. Make the appropriate changes to the configuration file in the UDI Wizard Designer console. To open an existing Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer 1. and then click UDI Wizard Designer. click File. click File. click File. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File The Operating System Deployment (OSD) Setup Wizard displays pages based on the configuration options specified in the UDIWizard_Config. and then point to All Programs. go to folder_path (where folder_path is the fully qualified path to the Scripts folder in the MDT 2010 files package source). Click Start. type file_name (where file_name is the file name for the configuration file). Point to Microsoft Deployment Toolkit. In the UDI Wizard Designer console. 3. Click Start. 5. click file_name (where file_name is the file name for the configuration file). You also need to update the distribution points with the modified MDT 2010 files package as described in Managing Distribution Points in Configuration Manager Console. go to folder_path (where folder_path is the fully qualified path to the Scripts folder in the MDT 2010 files package source). 3. Make the appropriate changes to the configuration file in the UDI Wizard Designer console. 4.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Managing UDI Deployments 280 1. click File. In the UDI Wizard Designer console. In the UDI Wizard Designer console. and then click Save. The UDI Wizard Designer starts. 2. Point to Microsoft Deployment Toolkit. in File name. and then point to All Programs. create a new task sequence or modify an existing task sequence steps to use the appropriate MDT 2010 files package. 2. and then click Open. Solution Accelerators microsoft. In the UDI Wizard Designer console. and then click New Configuration. and then click Save Configuration As. and then click Save Configuration As. After creating the new Operating System Deployment (OSD) Setup Wizard configuration file.

in the list box. 2. After modifying the existing Operating System Deployment (OSD) Setup Wizard configuration file. the configuration file can be updated without having to update Configuration Manager packages.com/technet/SolutionAccelerators . Publish an Operating System Deployment (OSD) Setup Wizard Configuration File to a UDI Web Service The UDI Wizard Designer can also publish the Operating System Deployment (OSD) Setup Wizard configuration file to the UDI web service. Also. type udi_web_service (where udi_web_service is the Uniform Resource Identifier (URI) to the UDI web service where you want to open the configuration file). Click Start. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service The UDI Wizard Designer can open an Operating System Deployment (OSD) Setup Wizard configuration file from a UDI web service. the configuration file can be updated without having to update Configuration Manager packages. and then click Save. In the UDI Wizard Designer console. and then point to All Programs. Publishing to the UDI web service allows centralized management and access to the configuration file. click file_name (where file_name is the file name for the configuration file). In the Open Remote Configuration dialog box. and then click OK. To open an Operating System Deployment (OSD) Setup Wizard configuration file from a UDI web service using the UDI Wizard Designer 1. type file_name (where file_name is the file name for the configuration file). Point to Microsoft Deployment Toolkit. and then click Open Remote Configuration. go to folder_path (where folder_path is the fully qualified path to the Scripts folder in the MDT 2010 files package source). In the Open Remote Configuration dialog box. and then click Connect. A list of available files appears in the list box. In the Save As dialog box. in File name.281 Microsoft Deployment Toolkit 2010 Update 1 6. create a new task sequence or modify an existing task sequence steps to use the appropriate MDT 2010 files package (if necessary). 4. The UDI Wizard Designer starts. Solution Accelerators microsoft. and then click UDI Wizard Designer. You also need to update the distribution points with the modified MDT 2010 files package as described in Managing Distribution Points in Configuration Manager Console. 3. Also. Publishing to the UDI web service allows centralized management and access to the configuration file. in Specify root service URI. click File.

such as OSDSetup-Win7-NYC). Override the Configuration File Used by the Operating System Deployment (OSD) Setup Wizard The Operating System Deployment (OSD) Setup Wizard defaults to using the UDIWizard_Config. go to Computer Management/Task Sequence. In the UDI Wizard Designer console. configure the Application Discovery preflight check to read the configuration from the UDI web service URL as described in Configure Application Discovery Preflight Check Behavior. To publish an Operating System Deployment (OSD) Setup Wizard configuration file to a UDI web service using the UDI Wizard Designer 1. click File. 3.com/technet/SolutionAccelerators . in Tag. Click Start. 3. In the Save Remote Configuration dialog box. and then click OK. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. Right-click task_sequence (where task_sequence is the name of the task sequence you want to edit). 2. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 282 If you publish the configuration file to the UDI web service. in Specify root service URI. The UDI Wizard Designer starts. and then point to All Programs. 2.xml file in the Scripts folder in the MDT 2010 Files package for configuration. and then click UDI Wizard Designer. 4. To override the configuration file that the Operating System Deployment (OSD) Setup Wizard uses 1. click the UDI Wizard task sequence step. and then click Publish Configuration. type udi_web_service (where udi_web_service is the URI to the UDI web service where you want to save the configuration file). Make the appropriate changes to the configuration file in the UDI Wizard Designer console. Beneath the State Capture phase. type tag (where tag is a method of identifying the configuration file. Solution Accelerators microsoft. In the Configuration Manager Console. Open a configuration file as described in one of the following sections: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. 5. You can override the default configuration file that the wizard uses by modifying the UDI Wizard task sequence step to use the /definition parameter. Point to Microsoft Deployment Toolkit. and then click Edit.

Table 135. modify the text as follows (where path is the path to the configuration file which is relative to the Scripts folder and file_name is the name of the configuration file): cscript. 5.exe “%DeployRoot%\Scripts\UDIWizard. substituting State Capture with Preinstall/New Computer Only. Repeat steps 3 and 4. 7. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service.wsf” /definition:path\file_name.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File.wsf. and then point to All Programs. Repeat steps 3 and 4 for any custom task sequence steps that run UDIWizard. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. in the navigation pane. click Wizard. 4. 6. 2. Configure the Welcome Page Behavior Using the UDI Wizard Designer The Welcome page in the Operating System Deployment (OSD) Setup Wizard is contains introductory information and a graphic that can be customized for your organization. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. configure the settings listed in Table 135 based on the requirements of your organization. Note The above text appears on one line. The line wrap seen here is the result of document formatting constraints.xml. Click OK. On the Properties tab for the UDI Wizard task sequence step in Command line. In the UDI Wizard Designer console. To configure the Welcome page behavior using the UDI Wizard Designer 1. and then click UDI Wizard Designer. In the Workspace pane.283 Microsoft Deployment Toolkit 2010 Update 1 4.com/technet/SolutionAccelerators . Click Start. Point to Microsoft Deployment Toolkit. 3. Configure the Welcome page behavior using the UDI Wizard Designer. and then click Welcome Page. Configuration Settings for the Welcome Page in the Workspace Pane Setting Welcome Text Solution Accelerators Description Contains a text message that is displayed on the microsoft.

For example.exe resides and the file name of the graphic image that is displayed on the Welcome page in the Operating System Deployment (OSD) Setup Wizard. Solution Accelerators microsoft. • Silent. • The task sequence variables that relate to the fields on the page are not set. If selected. configure the behavior for other wizard pages. Table 136. then only the file name needs to be specified. Close UDI Wizard Designer. if the file is in the same folder as OSDSetupWizard. 7. If selected. and any configuration settings entered on the page are set. Contains the path relative to the folder in which OSDSetupWizard. 5. Even if this option is selected. Configuration Settings for the Welcome Page in the Tasks Pane Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled. the wizard page will be displayed if: • There are problems with the configuration settings on the page. configure the settings listed in Table 136 based on the requirements of your organization. After completing the settings for this wizard page’s behavior. 6. the wizard page is displayed. • Disabled. the wizard page is not displayed. In the Tasks pane. and any configuration settings on the page are not set. If selected.exe.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Managing UDI Deployments 284 Setting Welcome Banner Description Welcome page in the Operating System Deployment (OSD) Setup Wizard. the wizard page is not displayed when there are no problems with the configuration settings on the page. and then save the Operating System Deployment (OSD) Setup Wizard configuration file.

Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. To configure the Preflight page behavior using the UDI Wizard Designer 1. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. configure the settings listed in Table 137 based on the requirements of your organization. Configure the Preflight page behavior using the UDI Wizard Designer. 3. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. from the top of the list to the bottom of the list. Table 138. 2. In the Tasks pane. and then click Preflight Page. and then point to All Programs. The preflight checks are performed in the order they appear. You can control the items in the list and the order of the list using the tasks in the Tasks pane as described in Table 138. Table 137.com/technet/SolutionAccelerators . Configuration Settings for the Preflight Page in the Workspace Pane Setting Preflight Configuration Description Contains a list of the preflight scripts or other software that are used to determine if the target computer is ready for deployment of the target operating system. Configuration Settings for the Preflight Page in the Tasks Pane Solution Accelerators microsoft. click Wizard. in the navigation pane. You can add one or more items to the list. 5.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. and then click UDI Wizard Designer.285 Microsoft Deployment Toolkit 2010 Update 1 Configure the Preflight Page Behavior Using the UDI Wizard Designer The Preflight page in the Operating System Deployment (OSD) Setup Wizard contains a list of prerequisite (preflight) checks that are performed prior to continuing the UDI deployment process. 4. Theses checks help ensure that the system resources and configuration of the target computer are adequate to perform the deployment. Point to Microsoft Deployment Toolkit. Click Start. configure the settings listed in Table 138 based on the requirements of your organization. In the UDI Wizard Designer console. In the Workspace pane.

If selected.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 286 Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled. and any configuration settings entered on the page are set. Adds a new preflight check to the list using the Preflight Checks dialog box as described in Table 139. Preflight Options Preflight Order • Table 139 lists the configuration settings in the Preflight Checks dialog box. the wizard page will be displayed if: • There are problems with the configuration settings on the page. Move Down. • Edit Preflight. • Disabled. Configuration Settings for the Preflight Checks Dialog Box Solution Accelerators microsoft. the wizard page is not displayed when there are no problems with the configuration settings on the page. Even if this option is selected. Table 139. • Remove Preflight. Removes a selected preflight check from the list. the wizard page is displayed. Controls which items appear in the Preflight Configuration list in the Workspace pane and includes the following tasks: • Add Preflight. • The task sequence variables that relate to the fields on the page are not set. Moves the selected item earlier in the order in which the preflight checks are performed. and any configuration settings on the page are not set. Modifies the configuration settings for a preflight check in the Preflight Checks dialog box as described in Table 139. If selected. If selected. Controls the position of a preflight check in the list and includes the following tasks: • Move Up. • Silent. the wizard page is not displayed. Moves the selected item later in the order in which the preflight checks are performed. • One of the preflight checks encounters an error or warning.com/technet/SolutionAccelerators .

Contains the value for the exit code being defined. Contains the file name of the script or program that is run to perform the preflight check. The program exited with a warning status code. Note Success exit codes do not display an exit message. Contains a text message that is associated with the specific error code. • Exit Code Value. which indicates the target computer may have problems performing the UDI deployment based on the check being performed.com/technet/SolutionAccelerators . • Exit Code Display Message. The program exited with an error status code. configure the behavior for other wizard pages and then save the Operating System Deployment (OSD) Setup Wizard configuration file.287 Microsoft Deployment Toolkit 2010 Update 1 Setting Preflight Check Name Preflight Check Filename Preflight Check Parameters Preflight Exit Code Configuration Description Contains the name of the preflight check. which indicates the target computer is correctly configured for the check being performed. Contains any parameters that are required for the preflight check script or program. Each exit code contains the following information: • Exit Code State. • Error. The program exited with a successful status code. Solution Accelerators microsoft. 6. Close UDI Wizard Designer. After completing the settings for the behavior of this wizard page. • Warning. 7. Identifies the level of success when the program exits and can include one of the following status codes: • Success. which indicates that the target computer is configured incorrectly and cannot perform the UDI deployment based on the check being performed. Contains a list of one or more exit codes for the preflight check script or program.

Point to Microsoft Deployment Toolkit. the user credentials.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. Note By default. the Operating System Deployment (OSD) Setup Wizard will not validate the user credentials. If this check box is: • Selected. 2. Table 140. Configuration Settings for the Computer Page in the Workspace Pane Setting Validate user credentials Description This check box determines whether the Operating System Deployment (OSD) Setup Wizard validates the user credentials entered on the wizard page.com/technet/SolutionAccelerators Solution Accelerators . If this check box is: microsoft. Click Start. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. and domain or workgroup membership. this check box is selected. • Cleared. In the UDI Wizard Designer console. Configure the Computer page behavior using the UDI Wizard Designer. To configure the Computer page behavior using the UDI Wizard Designer 1. 4. configure the settings listed in Table 140 based on the requirements of your organization. In the Workspace pane. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 288 Configure the Computer Page Behavior Using the UDI Wizard Designer The Computer page in the Operating System Deployment (OSD) Setup Wizard contains configuration settings that relate to the computer name. and then click UDI Wizard Designer. and then click Computer Page. 3. click Wizard. and then point to All Programs. in the navigation pane. Verify ownership of the computer object This check box determines if the Operating System Deployment (OSD) Setup Wizard will verify the ownership of the computer object in AD DS. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. the Operating System Deployment (OSD) Setup Wizard will validate the user credentials.

default list. • Set Default Domain. • Cleared. Set invalid characters for computer name Contains a list of the characters that should not be included in a computer name and are considered invalid. Set the contents of the list of invalid characters to a predefined. the Operating System Deployment (OSD) Setup Wizard will not validate the ownership of the computer object. The following buttons affect the contents of the text box: • Clear. Note By default. Clears the contents of the list of invalid characters. The following button affects the contents of the text box: • Clear. the Operating System Deployment (OSD) Setup Wizard will validate the ownership of the computer object. • Default. Clears the contents of the list of characters that generate a warning if included. Note The default values selected here can be overridden if the Computer page and the Domain and OU fields are Domains Organizational Units Solution Accelerators microsoft. • Edit Domain. Modifies the configuration settings for a domain in the Domain Configuration dialog box as described in Table 141. this text box includes the default invalid characters. Adds a domain to the list using the Domain Configuration dialog box as described in Table 141.289 Microsoft Deployment Toolkit 2010 Update 1 Setting Description • Selected.com/technet/SolutionAccelerators . • Delete Domain. Set warning characters for computer name Contains a list of the characters that should create a warning if they are included in a computer name. Contains a list of domains to which computers can be joined and includes the following buttons: • Add Domain. Sets the domain currently selected in the Domains list box as the default domain. Note By default. Deletes a selected domain from the list. Contains a list of organizational units that exist in the selected default domain. this check box is selected.

If selected. Click Connect to connect to the specified domain and obtain a list of the available OUs.com/technet/SolutionAccelerators Specify Alternate Credentials Available OUs Solution Accelerators . and Workgroup fields are enabled. Contains the user name of the account in the domain that is a member of the Domain Admins group in the domain. If selected. Default Workgroup Name Default Selection Contains the workgroup name to use by default. Configuration Settings for the Domain Configuration Dialog Box Setting Domain Description Contains the fully qualified domain name (FQDN) of the domain. Note The default values selected here can be overridden if the Computer page and the Domain. • Workgroup. • Password. Table 141 lists the configuration settings in the Domain Configuration dialog box. If selected. Contains the password for the account specified in the Username text box. Selects if the default membership for the computer and can be one of the following values: • Domain. OU. complete the following text boxes: • Username. the computer will be a member of the default domain and placed in the default OU by default.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 290 Setting Description enabled. the computer will be a member of a workgroup by default. Adds the OU selected in the Available OUs list to the Selected OUs list. Check box that determines whether alternate credentials are necessary for connecting to the domain. Note The default values entered here can be overridden if the Computer page and the Workgroup field are enabled. Removes the OU selected in the Selected microsoft. Table 141. Contains a list of the available OUs in the domain specified in the Domain text box and includes the following buttons: • >>. • <<.

Controls the behavior of the Computer Name text box on the wizard page and includes the following tasks: • Enabled. Contains the distinguished name of the OU selected in the Available OUs list. configure the settings listed in Table 142 based on the requirements of your organization. the wizard page will be displayed if: • There are problems with the configuration settings on the page. and any configuration settings entered on the page are set. and any configuration settings on the page are not set. Allows the contents of the Computer Name text box to be modified. Configuration Settings for the Computer Page in the Tasks Pane Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled. microsoft. In the Tasks pane. the wizard page is displayed. 5. • Silent. the wizard page is not displayed. • The task sequence variables that relate to the fields on the page are not set. the wizard page is not displayed when there are no problems with the configuration settings on the page.291 Microsoft Deployment Toolkit 2010 Update 1 Setting Selected OUs OU Friendly Name OU Distinguished Name Domain Display Name Description OUs list from the Selected OUs list. Contains the friendly name of the OU selected in the Available OUs list. • Disabled.com/technet/SolutionAccelerators Computer Name Field Solution Accelerators . Contains an optional name that is displayed in the Domains list in the Workspace pane. Prevents the contents of the Computer Name text box from being modified. If selected. Even if this option is selected. If selected. • Disabled. Table 142. Contains a list of the OUs that are available for placement of computer objects. If selected.

• Disabled. Prevents the contents of the Workgroup text box from being modified. • Disabled. Allows the contents of the Workgroup text box to be modified. Allows the item selected in the Domain list box to be modified. microsoft. Controls the behavior of the OU list box on the wizard page and includes the following tasks: • Enabled. Moves the selected item earlier in the order in which the OUs appear. Prevents the contents of the User name text box from being modified. Controls the position of an OU in the Organizational Units list and includes the following tasks: • • Move Up. Controls the behavior of the User name text box on the wizard page and includes the following tasks: • Enabled. Moves the selected item later in the order in which the OUs appear.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 292 Setting Domain Field Description Controls the behavior of the Domain list box on the wizard page and includes the following tasks: • Enabled. Controls the behavior of the Workgroup text box on the wizard page and includes the following tasks: • Enabled. Move Down. • Disabled. Controls the behavior of the Password text box on the wizard page and includes the following tasks: • Enabled. Allows the item selected in the OU list box to be modified. • Disabled. • Disabled. Allows the contents of the User Name text box to be modified. Prevents the item selected in the Domain list box from being modified. Prevents the contents of the Password text box from being modified. Prevents the item selected in the OU list box from being modified.com/technet/SolutionAccelerators OU Field User Name Password Workgroup Field OU Order Solution Accelerators . Allows the contents of the Password text box to be modified.

4. in the navigation pane. After completing the settings for the behavior of this wizard page. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. If this check box is: • Selected. the Operating System Deployment (OSD) Setup Wizard will allow the addition of existing accounts to the local Administrators group of the target computer. and then click UDI Wizard Designer. 3. Configure the User Configuration page behavior using the UDI Wizard Designer. In the Workspace pane. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. 7. and then point to All Programs. Configure the User Configuration Page Behavior Using the UDI Wizard Designer The User Configuration page in the Operating System Deployment (OSD) Setup Wizard contains a list of the user accounts that are added to the local Administrators group on the target computer. and then click User Configuration. Click Start.com/technet/SolutionAccelerators Solution Accelerators . To configure the User Configuration page behavior using the UDI Wizard Designer 1. Point to Microsoft Deployment Toolkit.293 Microsoft Deployment Toolkit 2010 Update 1 6. 2. • Cleared. the Operating System Deployment microsoft. Table 143. configure the settings listed in Table 143 based on the requirements of your organization.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. click Wizard. Close UDI Wizard Designer. configure the behavior for other wizard pages and then save the Operating System Deployment (OSD) Setup Wizard configuration file. In the UDI Wizard Designer console. Configuration Settings for the User Configuration Page in the Workspace Pane Setting Allow user to add additional accounts to the local Administrators group Description This check box determines whether the Operating System Deployment (OSD) Setup Wizard allows existing accounts to be added to the local Administrators group of the target computer.

Controls the behavior of the Administrator password and Confirm password text boxes on the wizard page and includes the following tasks: • Enabled. configure the settings listed in Table 144 based on the requirements of your organization. Allows the contents of the Administrator password and Confirm password text boxes to be modified. configure the behavior for other wizard pages. • Disabled. Table 144. the wizard page is displayed and any configuration settings entered on the page are set. the wizard page is not displayed when there are no problems with the configuration settings on the page. 5. this check box is selected. • Disabled. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. If selected. Solution Accelerators microsoft. the wizard page is not displayed and any configuration settings on the page are not set.com/technet/SolutionAccelerators . Admin Password Field 6. Prevents the contents of the Administrator password and Confirm password text boxes from being modified. If selected. Even if this option is selected the wizard page will be displayed if: • There are problems with the configuration settings on the page. Configuration Settings for the User Configuration Page in the Tasks Pane Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled. • Silent. If selected.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 294 Setting Description (OSD) Setup Wizard will not allow the addition of existing accounts to the local Administrators group of the target computer. • The task sequence variables that relate to the fields on the page are not set. In the Tasks pane. Note By default. After completing the settings for the behavior of this wizard page.

and then click UDI Wizard Designer. Close UDI Wizard Designer. in the navigation pane. the keyboard locale. • <<. and then click Language Page. In the Workspace pane. configure the settings listed in Table 145 based on the requirements of your organization. To configure the Language page behavior using the UDI Wizard Designer 1. The following buttons can be used to configure the list of selected languages: • >>. and the time zone. In the UDI Wizard Designer console. Solution Accelerators microsoft. Configure the Language Page Behavior Using the UDI Wizard Designer The Language page in the Operating System Deployment (OSD) Setup Wizard contains the configuration settings for the languages to be installed. Configure the Language page behavior using the UDI Wizard Designer. 4. These pairs of list boxes are used to determine input local. the default input locale.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. 2. Configuration Settings for the Language Page in the Workspace Pane Setting Description Set default language. The left list box contains a list of all the available languages. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. The right list box contains a list of the languages that have been selected for deployment with the target operating system. click Wizard. and then point to All Programs.com/technet/SolutionAccelerators . Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. Click Start. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Point to Microsoft Deployment Toolkit. Adds the language selected in the list of available languages (left list box) to the list of languages to be deployed (right list box). the default language. and time which languages are installed on the target zone information computer. Table 145. Removes the language selected from the list of languages to be deployed (right list box). 3.295 Microsoft Deployment Toolkit 2010 Update 1 7.

the wizard page is not displayed. and no configuration settings on the page are set. Select the default timezone This list box selects the default time zone. In the Tasks pane. If selected. Note The default values selected here can be overridden in the Operating System Deployment (OSD) Setup Wizard if the Language page and the Timezone field are enabled. Table 146.com/technet/SolutionAccelerators Solution Accelerators . and any configuration settings entered on the page are set. • Silent. If selected. • The task sequence variables that relate to the microsoft. Select the default keyboard locale This list box selects the default keyboard locale.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 296 Setting Select the default language Description This list box selects the default language from the list of languages to be deployed (in the right list box at the top of the Workspace pane). Note The default values selected here can be overridden in the Operating System Deployment (OSD) Setup Wizard if the Language page and the Keyboard field are enabled. the wizard page will be displayed if: • There are problems with the configuration settings on the page. Even if this option is selected. If selected. Select the default input locale This list box selects the default input locale. the wizard page is not displayed when there are no problems with the configuration settings on the page. • Disabled. 5. the wizard page is displayed. configure the settings listed in Table 146 based on the requirements of your organization. Note The default values selected here can be overridden in the UDI Wizard if the Language page and the Language field are enabled. Note The default values selected here can be overridden in the Operating System Deployment (OSD) Setup Wizard if the Language page and the Locale field are enabled. Configuration Settings for the Language Page in the Tasks Pane Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled.

if you are installing a French language pack. Controls the behavior of the Language to install list box on the wizard page and includes the following tasks: • Enabled. configure the behavior for other wizard pages. If you add more than one language in the right Set default language. Controls the behavior of the Time zone list box on the wizard page and includes the following tasks: • Enabled. Prevents the contents of the Time zone list box from being modified.com/technet/SolutionAccelerators . For example. Create the task sequence step with a task sequence step condition based on the language pack to be installed specified in the UILanguage task sequence variable. After completing the settings for the behavior of this wizard page. • Disabled. then the Solution Accelerators microsoft. then you need to add a task sequence step for each language to be installed as described in Add Language Packs. Prevents the contents of the Language to install list box from being modified. • Disabled. Allows the contents of the Time and currency format list box to be modified. Controls the behavior of the Time and currency format list box on the wizard page and includes the following tasks: • Enabled. Allows the contents of the Language to install list box to be modified. and time zone information list box. Prevents the contents of the Time and currency format list box from being modified.297 Microsoft Deployment Toolkit 2010 Update 1 Setting Language Field Description fields on the page are not set. Controls the behavior of the Keyboard layout list box on the wizard page and includes the following tasks: • Enabled. Locale Field Keyboard Field Timezone Field 6. Close UDI Wizard Designer. • Disabled. Allows the contents of the Time zone list box to be modified. Prevents the contents of the Keyboard layout list box from being modified. input local. Allows the contents of the Keyboard layout list box to be modified. • Disabled. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. 7.

the Operating System Deployment (OSD) Setup Wizard defaults to formatting the target volume during installation on the target computer. Click Start. Point to Microsoft Deployment Toolkit. In the Workspace pane. 2. In the UDI Wizard Designer console. Table 147.com/technet/SolutionAccelerators . see Available Language Packs. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. 4. Solution Accelerators microsoft. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. To configure the Volume page behavior using the UDI Wizard Designer 1. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 298 condition would be as follows (where fr-FR is the language/culture name for the French language): UILanguage Equals fr-FR For a list of the of available language packs for Windows 7 and Windows Server 2008 R2 and the corresponding language/culture. in the navigation pane. 3. If this check box is: • Selected. click Wizard. and then click UDI Wizard Designer. configure the settings listed in Table 147 based on the requirements of your organization. and then click Volume Page. Configuration Settings for the Volume Page in the Workspace Pane Setting Description Format: Clean all This check box determines if the Operating data on the target System Deployment (OSD) Setup Wizard will volume during install default to formatting the target volume on the target computer. Configure the Volume Page Behavior Using the UDI Wizard Designer The Volume page in the Operating System Deployment (OSD) Setup Wizard contains the configuration settings for the disk volume configuration of the target computer and the image to be deployed to the target computer. and then point to All Programs. Configure the Volume page behavior using the UDI Wizard Designer.

Set volume and disk information Table 148 lists the configuration settings in the Add Index Image dialog box. configure the settings listed in Table 149 based on the requirements of your organization. Table 149. Display volumes with a minimum size of (gigabytes) Contains the value for the minimum disk volume size available in the Operating System Deployment (OSD) Setup Wizard. Only disk volumes that are equal to or greater than the value in this box are displayed in the Operating System Deployment (OSD) Setup Wizard. Table 148. Contains a list of operating system images that will be displayed in the Operating System Deployment (OSD) Setup Wizard and has the following buttons: • Add.com/technet/SolutionAccelerators . Contains the processor architecture of the operating system image and can be either x86 or amd64. Contains the index to the image being deployed from the WIM file. • Delete. this check box is cleared. Note By default. the Operating System Deployment (OSD) Setup Wizard does not default to formatting the target volume during installation on the target computer.299 Microsoft Deployment Toolkit 2010 Update 1 Setting Description • Cleared. WIM Index Architecture 5. In the Tasks pane. Deletes the selected operating system image item from the list. Adds an operating system image item to the list using the Add Image Index dialog box. as described in Table 148. Configuration Settings for the Add Index Image Dialog Box Setting Index Display Name Description Contains the name of the operating system image that will be displayed in the Set volume and disk information list box in the Workspace pane. Configuration Settings for the Volume Page in the Tasks Pane Setting Page Behavior Solution Accelerators Description Controls the behavior for the entire wizard page microsoft.

and any configuration settings entered on the page are set. Allows the contents of the Volume list box to be modified. Even if this option is selected the wizard page will be displayed if: • There are problems with the configuration settings on the page. • Disabled. • Disabled. the wizard page is not displayed when there are no problems with the configuration settings on the page. Allows the contents of the Windows Directory list box to be modified.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 300 Setting Description and can be configured to one of the following values: • Enabled. Allows the contents of the Image Selection list box to be modified.com/technet/SolutionAccelerators Disk Volume Field Windows Directory Field Disk Format Field Solution Accelerators . Controls the behavior of the Volume list box on the wizard page and includes the following tasks: • Enabled. • Disabled. Image Selection Field Controls the behavior of the Image Selection list box on the wizard page and includes the following tasks: • Enabled. Controls the behavior of the Format: Clean all data on the target volume during install check box on the wizard page and includes the following tasks: microsoft. the wizard page is not displayed. If selected. • The task sequence variables that relate to the fields on the page are not set. the wizard page is displayed. and any configuration settings on the page are not set. • Disabled. • Silent. If selected. Prevents the contents of the Windows Directory list box from being modified. Prevents the contents of the Image Selection list box from being modified. If selected. Controls the behavior of the Windows Directory list box on the wizard page and includes the following tasks: • Enabled. Prevents the contents of the Volume list box from being modified.

The Application Discovery preflight check can obtain the list of applications to include in the scan from: • • A file stored in the MDT 2010 Files package in a folder relative to the folder in which the Application Discover preflight check resides. configure the behavior for other wizard pages.com/technet/SolutionAccelerators Solution Accelerators . which is accessed from the OSD Application page in the UDI Wizard Designer as described in Configure Software Installation Behavior Using the OSD Applications Page in the UDI Wizard Designer. The mapping between existing applications and the applications to be deployed is managed on the Mappings tab in the Application Details dialog box.xml • Can reference a UDI web service: / microsoft. The /readcfg: parameter: • Can reference a local file: /readcfg:. Allows the contents of the Format: Clean all data on the target volume during install check box to be modified. Application Discovery Preflight Check Parameters Parameter /readcfg: Description Configures the configuration file to read that includes the list of applications to be included in the scan. • Disabled. The Application Discovery preflight generates an XML file that the Operating System Deployment (OSD) Setup Wizard uses to help the user preselect which applications need to be reinstalled after the operating system image is deployed. 6. Prevents the contents of the Format: Clean all data on the target volume during install check box from being modified. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. Table 150. The UDI web service. Table 150 lists the Application Discovery preflight check parameters that must be configured for the preflight and a description of each parameter. Configure Application Discovery Preflight Check Behavior In the Refresh Computer deployment scenario. the Operating System Deployment (OSD) Setup Wizard contains a preflight check—the Application Discovery preflight check—which scans the target computer for existing applications. Close UDI Wizard Designer.\MyFolder\WoodgroveApps01.. After completing the settings for the behavior of this wizard page. 7.301 Microsoft Deployment Toolkit 2010 Update 1 Setting Description • Enabled.

xml /readcfg: WoodgroveApps01. always refer to the last few entries contained in the log file. The preflight check encountered one or more warnings.log The path specified is relative to the location of the Application Discovery preflight check. The XML file that the Application Solution Accelerators microsoft.com/services /WoodgroveApps. Note You can use the log file to help troubleshoot problems encountered during the Application Discovery preflight check by scanning the log for "Fatal" or "Warning" error codes. The application configuration files can include application items that are preselected in the UDI Wizard Designer. The first successful instance that can be opened is used..com/technet/SolutionAccelerators . When troubleshooting.\MyFolder\WoodgroveApps01. Configures the location to write the output XML file that is used to display the list of applications in the Operating System Deployment (OSD) Setup Wizard: /writecfg:.\MyFolder\WoodgroveAppsFinal. Subsequent instances are only used if previous instances are unavailable.woodgrovebank.xml • Can be provided multiple times: / readcfg:http://www. Table 151. Application Discovery Preflight Check Exit Codes Exit code 0 1 16777216 33554432 Description The preflight check completed successfully.xml The path specified is relative to the location of the Application Discovery preflight check. The preflight check encountered a fatal error during initialization.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 302 Parameter Description readcfg:http://www.woodgrovebank. as follows: /log:. /writecfg: /log: Table 151 lists the exit codes for the Application Discovery preflight check and provides a description of each exit code. Configures the location to write the log file.com/services /woodgroveApps. The preflight check encountered a fatal error while processing configuration.. The path specified is relative to the location of the Application Discovery preflight check.xml Multiple /readcfg: parameters are processed from left to right.

the application is deselected. Any addition applications in the XML file that the Application Discovery preflight check generates are installed next.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. 4. click Application. In the event that an application is selected in the UDI Wizard Designer but is excluded as part of the Application Discovery preflight check. and the Application Discovery preflight check records this change in the log file. In the Workspace pane. configure the settings listed in Table 152 based on the requirements of your organization. This same behavior is also true for any application dependencies for the application selected in the UDI Wizard Designer. To configure the Settings and Categories page using the UDI Wizard Designer 1.303 Microsoft Deployment Toolkit 2010 Update 1 Discovery preflight check generates causes any additional application items to be installed in the following order: 1. Configuration Settings for the Settings and Groups Page in the Workspace Pane Solution Accelerators microsoft. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. path and file name for the XML file that the Application Discovery preflight check creates. Table 152. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. and then click Settings and Groups. and then click UDI Wizard Designer. Point to Microsoft Deployment Toolkit. In the UDI Wizard Designer console. and the application groups. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. Configure Software Installation Behavior Using the Settings and Categories Page in the UDI Wizard Designer The Settings and Categories page in the Operating System Deployment (OSD) Setup Wizard contains the configuration settings that affect application variables. Any dependencies that are excluded as a part of the Application Discovery preflight check are not installed. 3.com/technet/SolutionAccelerators . Configure the Settings and Categories page using the UDI Wizard Designer. Click Start. Applications selected in the UDI Wizard Designer are installed first. and then point to All Programs. 2. 2. in the navigation pane.

In the Tasks pane. If selected. all child groups and applications will be selected or cleared in the Operating System Deployment (OSD) Setup Wizard. • Disabled. Table 153. Group list box 5. and any configuration settings entered on the page are set.exe resides and file name for the file that was generated during the Application Discovery preflight check. If selected. configure the settings listed in Table 153 based on the requirements of your organization. Root Application Group Name Contains the name of the root container for all the application groups specified in the Groups list box. The Install Multiple Applications task sequence step will read the applications variable starting with <base variable name>001 to <base variable name>999.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 304 Setting Base variable name Description Contains the variable name used as the base for creating application variable names. the wizard page is not microsoft. The path and file name specified in this box must match exactly the path specified for the output of the resulting XML file that the Application Discovery preflight check generates. the wizard page is displayed. which is in the format of <base variable name>001. Configuration Settings for the Settings and Groups Page in the Tasks Pane Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled. When this group is selected or cleared in the Operating System Deployment (OSD) Setup Wizard.com/technet/SolutionAccelerators Solution Accelerators . Alternate Application Contains the path relative to the folder in which Configuration Path OSDSetupWizard. Contains a list of all the applications groups and the applications associated with each group. Use the Add Group and Delete Group tasks to modify the contents of this list as described in Table 138. There is a maximum of 999 applications that can be selected through the Operating System Deployment (OSD) Setup Wizard.

Even if this option is selected the wizard page will be displayed if: • There are problems with the configuration settings on the page.305 Microsoft Deployment Toolkit 2010 Update 1 Setting Description displayed. If selected. Note If you delete an application group. Removes a selected application group from the list. • Delete Group. all the applications in the group are also deleted. Configuration Settings for the Group Configuration Dialog Box Setting Group Name Description Contains the name of the application group to be added to the Groups list in the Workspace pane. 6. Configure Software Installation Behavior Using the Package Selection Page in the UDI Wizard Designer The Package Selection page in the Operating System Deployment (OSD) Setup Wizard contains a list of the System Center Configuration Manager packages that are to be included in UDI deployments. Table 154 lists the configuration settings in the Group Configuration dialog box. • The task sequence variables that relate to the fields on the page are not set. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. and any configuration settings on the page are not set. configure the behavior for other wizard pages. Table 154. • Silent. Applications Groups Controls which items appear in the Groups list in the Workspace pane and includes the following tasks: • Add Group. The source for the System Center Configuration Manager packages are the packages in the Site Solution Accelerators microsoft. Adds a new application group to the list using the Group Configuration dialog box. After completing the settings for the behavior of this wizard page. the wizard page is not displayed when there are no problems with the configuration settings on the page. 7. Close UDI Wizard Designer. as described in Table 154.com/technet/SolutionAccelerators .

The following buttons affect the contents of the list box: • >>.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. Configure the Package Selection page using the UDI Wizard Designer. Remove the selected package from the Selected Packages list box. the package must have one or more programs.com/technet/SolutionAccelerators Selected Packages . Click Start. configure the settings listed in Table 155 based on the requirements of your organization. click Application. Adds the selected package in the Available Packages list box to the Selected Packages list box. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. in the navigation pane.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 306 Database\Computer Management\Software Distribution\Packages node in the Configuration Manager Console. Note To add a package to the Available Packages list box. Contains the list of packages that have been selected from the Available Packages list box and are available in the Operating System Deployment (OSD) Setup Wizard. Configuration Settings for the Package Selection Page in the Workspace Pane Setting Configuration Manager Server Name Available Packages Description Contains the name of the System Center Configuration Manager Site Server that manages the packages to be listed in the Available Packages list box. and then point to All Programs. and then click Package Selection. 3. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. 4. Table 155. Contains a list of the packages on the System Center Configuration Manager Site Server specified in the Configuration Manager Server Name box. In the UDI Wizard Designer console. • <<. Point to Microsoft Deployment Toolkit. To configure the Package Selection page using the UDI Wizard Designer 1. and then click UDI Wizard Designer. 2. and the Solution Accelerators microsoft. Operating System Deployment (OSD) Setup Wizard Configuration File. In the Workspace pane.

Point to Microsoft Deployment Toolkit. To configure the OSD Applications page using the UDI Wizard Designer 1. Configuration Settings for the Package Selection Page in the Tasks Pane Setting SMS Data Source: Refresh Description Refreshes the list of available packages based on the current packages configured on the System Center Configuration Manager Site Server specified in the Configuration Manager Server Name box. Click Start. 2. For more information.com/technet/SolutionAccelerators .xml file that you wish to configure) as described in: • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. 5. 6.307 Microsoft Deployment Toolkit 2010 Update 1 Setting Description Allow this program to be installed from the Install Software task sequence without being advertized check box must be selected. 7. After completing the settings for the behavior of this wizard page. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. see “Install Multiple Applications” in Install Software. The Allow this program to be installed from the Install Software task sequence without being advertized check box is on the Advanced tab in the program’s Properties dialog box. and then click UDI Wizard Designer. In the Tasks pane. Solution Accelerators microsoft. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. and then point to All Programs. Table 156. Configure the OSD Applications page using the UDI Wizard Designer. Close UDI Wizard Designer. configure the behavior for other wizard pages. configure the settings listed in Table 156 based on the requirements of your organization. Configure Software Installation Behavior Using the OSD Applications Page Behavior in the UDI Wizard Designer The OSD Applications page in the UDI Wizard Designer contains a list of all the applications that can be installed using the Software Installation page in the Operating System Deployment (OSD) Setup Wizard. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config.

and then click OSD Applications. Table 158. Use the Add. • Edit. Table 160.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 308 Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. configure the settings listed in Table 157 based on the requirements of your organization.com/technet/SolutionAccelerators Application Settings Solution Accelerators . In the Tasks pane. Table 161. 3. 4. • 5. and Table 162. Contains detailed information about the application selected in the Choose the application you would like to enable in OSD list box. Configuration Settings for the OSD Applications Page in the Workspace Pane Setting Choose the application you would like to enable in OSD Application details Description Contains a list of the applications that will be available for deployment to the target computer. as described in Table 158. click Application. Edit and Remote tasks in Applications Items in the Tasks pane to modify the contents of this list. and Table 162. Configuration Settings for the Package Selection Page in the Tasks Pane Setting Application Items Description Controls the contents of the Choose the application you would like to enable in OSD list box in the OSD Application page in the Workspace pane and includes the following tasks: • Add. Table 157. Removes the item selected in the list box. Table 161. In the Workspace pane. Modifies the item selected in the list box using the application_name dialog box (where application_name is the name of the application) as described in Table 159. Table 160. in the navigation pane. Controls if the check box that corresponds to the item selected in the Choose the application you microsoft. • Remove. configure the settings listed in Table 158 based on the requirements of your organization. In the UDI Wizard Designer console. Adds an item to the list box using the application_name dialog box (where application_name is the name of the application) as described in Table 159.

• Clear. This prevents 32-bit installations of the applications. then the Install Software page in the Operating System Deployment (OSD) Setup Wizard will be populated using the XML file. The following buttons affect the content displayed: • Attach. and the Application Details list box does not change the Selection Locked application item state. The following buttons affect the content displayed: • Attach.309 Microsoft Deployment Toolkit 2010 Update 1 Setting Description would like to enable in OSD list box is selected or deselected by default and if the selection can be changed during deployment and includes the following tasks: • Select by default. Table 159 lists the configuration settings on the Applications Details tab in the application_name dialog box (where application_name is the name of the application). • Lock selection. Attaches a specific System Center Configuration Manager program to the microsoft.com/technet/SolutionAccelerators 64-bit Program Properties Solution Accelerators . Toggles the Selection locked application item state for the item selected in the list box. Removes any references to a specific System Center Configuration Manager program to the application for 32-bit installations. Attaches a specific System Center Configuration Manager program to the application for 32-bit installations using the Configuration Manager Packages dialog box. Note If the Alternate Application Configuration Path box on the Settings and Groups page contains has a relative path of an XML file generated by Application Discovery. This enables 32-bit installations of the application. Configuration Settings for the Applications Details Tab in the Application Details Dialog Box Setting 32-bit Program Properties Description Contains the information regarding the application for 32-bit installations. Contains the information regarding the application for 64-bit installations. Toggles the Mark as selected application item state for the item selected in the list box. Table 159.

If this check box is: • Selected. This prevents 64-bit installations of the applications. This list box is used to assign the application to an application group and is displayed in the Group column in the Choose the application you would like to enable in OSD list box on the OSD Application page. Removes any references to a specific System Center Configuration Manager program to the application for 64-bit installations. the state of check box for the microsoft. This check box determines whether the check box for this application can be changed in the Software Installation wizard page of the Operating System Deployment (OSD) Setup Wizard.com/technet/SolutionAccelerators Description Group Mark as selected Selection locked Solution Accelerators . the check box for the application is selected by default. This enables 64-bit installations of the application. If this check box is: • Selected. Contains an informative description of the application that is displayed in the Description column in the Choose the application you would like to enable in OSD list box on the OSD Application page. the check box for the application is cleared by default. • Cleared.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 310 Setting Description application for 64-bit installations using the Configuration Manager Packages dialog box. • Clear. • Cleared. the state of check box for the application cannot be changed on the Software Installation wizard page. Display Name Contains the name of the application that is displayed in the Display Name column in the Choose the application you would like to enable in OSD list box on the OSD Application page. This check box determines whether the check box for this application is selected or cleared by default in the Software Installation wizard page of the Operating System Deployment (OSD) Setup Wizard. The groups are created and managed on the Settings and Groups page in UDI Wizard Designer.

The Add Application Dependencies dialog box has the following settings: • List of applications. Click to select an application as a dependency or exclusion.311 Microsoft Deployment Toolkit 2010 Update 1 Setting Description application can be changed on the Software Installation wizard page. Adds an application dependency or exclusion to the list using the Add Application Dependencies dialog box. Table 161. The following buttons are used to modify the contents of this list: • Add. Contains a list of the applications. Configuration Settings for the Mappings Tab in the Application Details Dialog Box Setting Windows Installer Product Code(s) Description Contains a list of the applications that this application supersedes or replaces. Configuration Settings for the Dependencies Tab in the Application Details Dialog Box Setting Dependencies & Exclusions Description Contains a list of the applications upon which this application depends or which applications cannot be installed with this application. The mapping is based on the Windows Installer product code for the application being microsoft. such as Microsoft Office 2010 replacing the 2007 Office system. • Dependency type. Table 160 lists the configuration settings on the Dependencies tab in the application_name dialog box (where application_name is the name of the application). Table 160.com/technet/SolutionAccelerators Solution Accelerators . Removes the application dependency or exclusion selected in the list. A list box that contains the type of application dependency and can have a value of Require (the application requires the dependent application) or Exclude (the application cannot be installed with the dependent application). Table 161 lists the configuration settings on the Mappings tab in the application_name dialog box (where application_name is the name of the application). • Remove.

Contains the package identifier as defined in the System Center Configuration Manager site database. Table 162. • Product Guid. Removes the mapping selected in the list. Contains the product GUID for the application being replaced. The MSI Matches dialog box has the following settings: • Display Name. Configuration Settings for the Delivery Rules Tab in the Application Details Dialog Box Solution Accelerators microsoft.com/technet/SolutionAccelerators . such as Microsoft Office 2010 replacing the 2007 Office system. The following buttons are used to modify the contents of this list: • Add. • Remove. • Program Name. Table 162 lists the configuration settings on the Delivery Rules tab in the application_name dialog box (where application_name is the name of the application). Removes the mapping selected in the list. Contains the name of the product to be displayed in the list. Adds a mapping to the list using the Configuration Manager Matches dialog box. The following buttons are used to modify the contents of this list: • Add. Contains the name of the product to be displayed in the list. Contains the program name as defined in the System Center Configuration Manager site database and can be selected in the Configuration Manager Packages dialog box. Adds a mapping to the list using the MSI Matches dialog box. • Remove. • Package ID. The mapping is based on the System Center Configuration Manager program and package identifiers for the application being replaced. Configuration Manager Program & Package Identifiers Contains a list of the applications that this application supersedes or replaces.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 312 Setting Description replaced. The Configuration Manager Matches dialog box has the following settings: • Display Name.

Contains the name of the WMI namespace to be used for the WMI query specified in Query.com/technet/SolutionAccelerators Solution Accelerators . • Query. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. Configure the Summary page behavior using the UDI Wizard Designer. Removes the WMI query selected in the list. For more information about creating WMI queries. 2. Click Start. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config.313 Microsoft Deployment Toolkit 2010 Update 1 Setting Description Contains a list of WMI queries that can be performed to determine whether the application should be deployed on the target computer. 7. Close UDI Wizard Designer. Contains the WMI query to be performed in the WMI namespace specified in WMI Namespace. The WMI Filters dialog box has the following settings: • WMI Namespace. Adds a WMI query to the list using the WMI Filters dialog box. After completing the settings for the behavior of this wizard page. Configure the Summary Page Behavior Using the UDI Wizard Designer The Summary page in the Operating System Deployment (OSD) Setup Wizard displays the configuration settings that were selected when running the wizard just prior to performing the UDI deployment. To configure the Summary page behavior using the UDI Wizard Designer 1. see Querying with WQL. 6. and then click UDI Wizard Designer. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. • Remove. Point to Microsoft Deployment Toolkit. The following buttons are used to modify the contents of this list: • Add. and then point to All Programs. configure the behavior for other wizard pages and then save the Operating System Deployment (OSD) Setup Wizard configuration file.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. microsoft.

the wizard page is displayed. Configuration Settings for the Summary Page in the Tasks Pane Setting Page Behavior Description Controls the behavior for the entire wizard page and can be configured to one of the following values: • Enabled. the wizard page will be displayed if: • There are problems with the configuration settings on the page. Preview the Operating System Deployment (OSD) Setup Wizard Behavior Using the UDI Wizard Designer The UDI Wizard Designer includes a preview feature that allows you to preview the Operating System Deployment (OSD) Setup Wizard behavior. click Wizard. configure the behavior for other wizard pages. Close UDI Wizard Designer. and any configuration settings on the page are not set. • Disabled. Point to Microsoft Deployment Toolkit. Even if this option is selected. the wizard page is not displayed. • Silent. Solution Accelerators microsoft. and then point to All Programs. If selected. Table 163. and then click Summary Page. Click Start. configure the settings listed in Table 163 based on the requirements of your organization. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. and any configuration settings entered on the page are set. If selected. If selected. After completing the settings for the behavior of this wizard page. In the Tasks pane. the wizard page is not displayed when there are no problems with the configuration settings on the page.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 314 3. 5.com/technet/SolutionAccelerators . 4. in the navigation pane. To preview the Operating System Deployment (OSD) Setup Wizard behavior using the UDI Wizard Designer 1. and then click UDI Wizard Designer. The preview feature allows you to preview the configuration and behavior settings that you have made in the UDI Wizard Designer. In the UDI Wizard Designer console. 6. • The task sequence variables that relate to the fields on the page are not set.

Navigate through the wizard pages to verify that the configuration settings made in the UDI Wizard Designer are correct.315 Microsoft Deployment Toolkit 2010 Update 1 2. 4. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. from the File menu. click Preview OSDSetupWizard.com/technet/SolutionAccelerators . Solution Accelerators microsoft. In the UDI Wizard Designer console. The Operating System Deployment (OSD) Setup Wizard opens in preview mode. 3. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File.

vbs script. The Operating System Deployment (OSD) Setup Wizard displays wizard pages based on the deployment scenario you selected and the configuration options you specified in UDIWizard_Config. Initiate the task sequence created using the User Driven Installation Task Sequence template and one of the following methods: • • Task sequence bootable media disk using the Task Sequence Media Wizard as described in Creating Task Sequence Bootable Media. and then click Next. The deployment process prompts for any configuration settings not already specified. This feature is found only in boot images created in MDT 2010 Update 1 and later. The task sequence step runs the ZTIConfirmDiskpart. At the appropriate task sequence step. review the information provided on the page. Note UDI task sequences start with the Confirmation to Partition Disk task sequence step. the Operating System Deployment (OSD) Setup Wizard starts. On the Welcome wizard page. 2. which allows you to confirm partitioning and disk formatting on the target computer. Each deployment scenario (New Computer or Refresh Computer) uses a different process. Initiate the Operating System Deployment (OSD) Setup Wizard in a task sequence manually by using Windows Deployment Services or as an advertised program in the Configuration Manager Client. To deploy the new operating system to the target computer using the Operating System Deployment (OSD) Setup Wizard 1. The logic for displaying (or not displaying) a wizard page is noted for each wizard page in the following steps. run the Operating System Deployment (OSD) Setup Wizard. This wizard page is shown if: • The Page Behavior for the Welcome Page is configured to Enabled or Disabled in the UDI Wizard Designer. Complete the Task Sequence Wizard by selecting the appropriate UDI task sequence. and then the Task Sequence Wizard starts. 3. . Windows Deployment Services to start the appropriate Windows PE images that will in turn start the UDI deployment process to the target computers as described in Preparing Windows Deployment Services for UDI Deployments.Using the Microsoft Deployment Toolkit: Operating System Deployment (OSD) Setup Wizard 316 Running the Operating System Deployment (OSD) Setup Wizard To initiate the deployment of Windows to target computers.xml in the Scripts folder of the MDT 2010 files package. Windows PE starts. Initiate the deployment from Windows Deployment Services or using task sequence bootable media.

Configuration Settings on the Preflight Checks Wizard Page Setting Preflight Checks Description Contains the list of preflight checks performed and the status of each check. This wizard page is shown if: • • The Page Behavior for the Preflight Page is configured to Enabled or Disabled in the UDI Wizard Designer. Cancels the wizard and stops the UDI deployment process. On the Preflight Checks wizard page. complete the page using the information in Table 164.317 Microsoft Deployment Toolkit 2010 Update 1 • The Page Behavior for the Welcome Page is configured to Silent. Goes to the next wizard page. Error. the Next button is disabled. Warning. 4. • • Note If any checks have a status of Error. Retry Preflight Checks Back Next Cancel Performs all the preflight checks again. Configure the behavior for the Preflight page in the UDI Wizard Designer as described in Configure the Behavior for the Preflight Page Using the UDI Wizard Designer. but there are problems with required information on the wizard page. The Page Behavior for the Preflight Page is configured to Silent. Indicates that the target computer is configured incorrectly and cannot perform the UDI deployment based on the check being performed. Configure the behavior for the Welcome page using the UDI Wizard Designer as described in Configure the Welcome Page Behavior Using the UDI Wizard Designer. but there are problems with required information on the wizard page.com/technet/SolutionAccelerators Solution Accelerators . and then click Next. Table 164. Goes to the previous wizard page. microsoft. The value in the Status column can be: • Success. Indicates that the target computer is correctly configured for the check being performed. Indicates that the target computer may have problems performing the UDI deployment based on the check being performed.

Note This list box is only enabled if the Domain option is selected. complete the page using the information in Table 165. This wizard page is shown if: • • The Page Behavior for the Computer Page is configured to Enabled or Disabled in the UDI Wizard Designer. The corresponding list box contains a list of domains that can be selected. but there are problems with required information on the wizard page. This list box contains a list of OUs that can be selected where the computer account will be created. The list of domains available in the list box and the default domain are configured in the Domains list box on the Computer Page in the UDI Wizard Designer. Select this option if the target computer is to be a member of a domain. This field can be enabled or disabled using the Enabled or Disabled task in the Computer Name field in the UDI Wizard Designer as described in Configure the Behavior for the Computer Page Using the UDI Wizard Designer. On the Computer wizard page.com/technet/SolutionAccelerators . Table 165. and then click Next. Configure the behavior for the Computer page in the UDI Wizard Designer as described in Configure the Behavior for the Computer Page Using the UDI Wizard Designer. The Page Behavior for the Computer Page is configured to Silent. Configuration Settings on the Computer Wizard Page Setting Computer name Description Contains the computer name that will be assigned to the target computer.Using the Microsoft Deployment Toolkit: Operating System Deployment (OSD) Setup Wizard 318 5. Domain Organization Unit (OU) This field can be enabled or disabled using the Enabled or Disabled task in the OU field in the UDI Wizard Designer as described in Configure Solution Accelerators microsoft. The list of OUs available in the list box and the default OU are configured in the Organizational Units list box on the Computer Page in the UDI Wizard Designer. This field can be enabled or disabled using the Enabled or Disabled task in the Domain field in the UDI Wizard Designer as described in Configure the Behavior for the Computer Page Using the UDI Wizard Designer.

com/technet/SolutionAccelerators .319 Microsoft Deployment Toolkit 2010 Update 1 Setting Description the Behavior for the Computer Page Using the UDI Wizard Designer. complete the page using the information in Table 166. The value entered in this box must match the value in the Password box. User name Contains the user name of the account used to join the computer to the domain and is in the format of domain_name\user_name (where domain_name is the name of the domain and user_name is the user name of the account). Solution Accelerators microsoft. Note This list box is only enabled if the Domain option is selected. Note This list box is only enabled if the Domain option is selected. and then click Next. The default workgroup name is configured in the Default Workgroup Name box on the Computer Page in the UDI Wizard Designer. Note This text box is only enabled if the Workgroup option is selected. Workgroup Select this option if the target computer is to be a member of a workgroup. Confirm password Contains the password for the user name of the account used to join the computer to the domain. Password Contains the password for the user name of the account used to join the computer to the domain. This field can be enabled or disabled using the Enabled or Disabled task in the Workgroup field in the UDI Wizard Designer as described in Configure the Behavior for the Computer Page Using the UDI Wizard Designer. 6. Note This list box is only enabled if the Domain option is selected. Goes to the next wizard page. On the User Configuration wizard page. Cancels the wizard and stops the UDI deployment process. The corresponding text box contains the workgroup name. Back Next Cancel Goes to the previous wizard page. The value entered in this box must match the value in the Confirm password box.

The value entered in this box must match the value in the Confirm password box.Using the Microsoft Deployment Toolkit: Operating System Deployment (OSD) Setup Wizard 320 This wizard page is shown if: • • The Page Behavior for the User Configuration page is configured to Enabled or Disabled in the UDI Wizard Designer. Configuration Settings on the User Configuration Wizard Page Setting Password Description Contains the password for the Administrators local built-in account on the target computer. The value entered in this box must match the value in the Password box. microsoft. Contains the password for the Administrators local built-in account on the target computer. This field can be enabled or disabled using the Allow user to add additional accounts to the local Administrators group option in the UDI Wizard Designer as described in Configure the Behavior for the User Configuration Page in Using UDI Wizard Designer. Table 166.com/technet/SolutionAccelerators Confirm password User name Back Solution Accelerators . Goes to the previous wizard page. The Page Behavior for the User Configuration page is configured to Silent. Configure the behavior for the User Configuration page in the UDI Wizard Designer as described in Configure the Behavior for the User Configuration Page in Using UDI Wizard Designer. This field can be enabled or disabled using the Enabled or Disabled task in the Admin Password field in the UDI Wizard Designer as described in Configure the Behavior for the User Configuration Page in Using UDI Wizard Designer. but there are problems with required information on the wizard page. Each account is separated by a semicolon. Contains the user names of one or more accounts that will be members of the Administrators built-in local group. This field can be enabled or disabled using the Enabled or Disabled task in the Admin Password field in the UDI Wizard Designer as described in Configure the Behavior for the User Configuration Page in Using UDI Wizard Designer.

On the Language wizard page. Cancels the wizard and stops the UDI deployment process. The list of languages available in the list box and the language are configured in the Set default language. This field can be enabled or disabled using the Enabled or Disabled task in the Locale field in the UDI Wizard Designer as described in Configure the Behavior for the Language Page microsoft. and then click Next. but there are problems with required information on the wizard page. 7. Configuration Settings on the Language Wizard Page Setting Language to install Description This list box contains a list of languages that can be deployed on the target computer. and time zone list boxes and the Select the default language list box on the Language page in the UDI Wizard Designer. input locale.com/technet/SolutionAccelerators Time and currency format (Locale) Solution Accelerators . and time zone list boxes and the Select the default input locale list box on the Language page in the UDI Wizard Designer. Configure the behavior for the Language page in the UDI Wizard Designer as described in Configure the Behavior for the Language Page Using the UDI Wizard Designer. complete the page using the information in Table 167. This field can be enabled or disabled using the Enabled or Disabled task in the Language field in the UDI Wizard Designer as described in Configure the Behavior for the Language Page Using the UDI Wizard Designer. input locale. Table 167. This wizard page is shown if: • • The Page Behavior for the Language page is configured to Enabled or Disabled in the UDI Wizard Designer.321 Microsoft Deployment Toolkit 2010 Update 1 Setting Next Cancel Description Goes to the next wizard page. The Page Behavior for the Language page is configured to Silent. The list of locals available in the drop-down list box and the default locale are configured in the Set default language. This list box contains a list of locales (time and currency formats) that can be selected for the target computer.

This field can be enabled or disabled using the Enabled or Disabled task in the Keyboard field in the UDI Wizard Designer as described in Configure the Behavior for the Language Page Using the UDI Wizard Designer. This list box contains a list of keyboard layouts (keyboard locales) that can be selected for the target computer. Goes to the previous wizard page. Time zone Back Next Cancel 8. This field can be enabled or disabled using the Enabled or Disabled task in the Timezone field in the UDI Wizard Designer as described in Configure the Behavior for the Language Page Using the UDI Wizard Designer. Table 168. complete the page using the information in Table 168. This list box contains a list of keyboard layouts (keyboard locales) that can be selected for the target computer. Goes to the next wizard page. The Page Behavior for the Volume page is configured to Silent. and time zone list boxes and the Select the default keyboard local list box on the Language page in the UDI Wizard Designer. and then click Next. Cancels the wizard and stops the UDI deployment process. The default time zone is selected in the Select the default time zone list box on the Language page in the UDI Wizard Designer.com/technet/SolutionAccelerators . but there are problems with required information on the wizard page. On the Volume wizard page. The list of keyboard layouts available in the list box and the default locale are configured in the Set default language. Configuration Settings on the Volume Wizard Page Solution Accelerators microsoft. input locale. This wizard page is shown if: • • The Page Behavior for the Volume page is configured to Enabled or Disabled in the UDI Wizard Designer.Using the Microsoft Deployment Toolkit: Operating System Deployment (OSD) Setup Wizard 322 Setting Keyboard layout Description Using the UDI Wizard Designer. Configure the behavior for the Volume page in the UDI Wizard Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer.

This field can be enabled or disabled using the Enabled or Disabled task in the Disk Volume field on the Volume page in the UDI Wizard Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer. The list of local disk volumes that are available in the list box is configured in the Display volumes with a minimum size of (gigabytes) text box on the Volume page in the UDI Wizard Designer. This field can be enabled or disabled using the Enabled or Disabled task in the Disk Format field on the Volume page in the UDI Wizard Solution Accelerators microsoft. The default selection is configured in the Format: Clean all data on the target volume during install check box on the Volume page in the UDI Wizard Designer.com/technet/SolutionAccelerators . This field can be enabled or disabled using the Enabled or Disabled task in the Windows Directory field on the Volume page in the UDI Wizard Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer. This field can be enabled or disabled using the Enabled or Disabled task in the Image Selection field on the Volume page in the UDI Wizard Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer.323 Microsoft Deployment Toolkit 2010 Update 1 Setting Image Selection Description This list box contains the list of operating system images that can be deployed to the target computer. This list box contains a list of the local folders that contain an existing installation of Windows and is discovered when the wizard runs on the target computer. Volume Windows Directory Format: Clean all This check box determines whether the target data on the target volume on the target computer is formatted prior volume during install to deploying the target operating system. This list box contains a list of local disk volumes that can be selected for the target computer that are larger than a specified minimum volume size. The list of operating system images is configured in the Set volume and disk information list box on the Volume page in the UDI Wizard Designer.

Configure Software Installation Behavior Using the OSD Applications Page in the UDI Wizard Designer. 9. Table 169.Using the Microsoft Deployment Toolkit: Operating System Deployment (OSD) Setup Wizard 324 Setting Description Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer. The list of available applications is configured on the Settings and Groups. and OSD Applications pages in the UDI Wizard Designer. complete the page using the information in Table 169. and then click Next. Configuration Settings on the Install Software Wizard Page Setting Applications Description This hierarchical list of check boxes contains a list of the applications that can be deployed to the target computer. The Page Behavior for the Settings and Groups page is configured to Silent. On the Install Software wizard page. but there are problems with required information on the wizard page. Back Next Cancel Goes to the previous wizard page. Configure the behavior for the Install Software wizard page in the UDI Wizard Designer as described in: • • • Configure Software Installation Behavior Using the Settings and Categories Page in the UDI Wizard Designer. Configure Software Installation Behavior Using the Package Selection Page in the UDI Wizard Designer. Package Selection. This wizard page is shown if: • • The Page Behavior for the Settings and Groups page is configured to Enabled or Disabled in the UDI Wizard Designer.com/technet/SolutionAccelerators Solution Accelerators . Goes to the next wizard page. The applications are grouped by the application groups defined in the Group Name list box on the Settings and Group page in the UDI Wizard Designer. Cancels the wizard and stops the UDI deployment process. The check box for a specific application is set using the Set by default and Lock selection tasks in Application Settings in the UDI Wizard Designer as described in Configure Software Installation Behavior Using the OSD Applications microsoft.

Goes to the previous wizard page. the OSD Results page is displayed just prior to the first user logging on to the target computer. Goes to the next wizard page.com/technet/SolutionAccelerators . Configure the behavior for the Summary page in the UDI Wizard Designer as described in Configure the Behavior for the Summary Page Using the UDI Wizard Designer. Toolkit Reference.exe. and deployment of the new operating system begins. Cancels the wizard and stops the UDI deployment process. and then click Finish. This wizard page is shown if: • • The Page Behavior for the Summary page is configured to Enabled or Disabled in the UDI Wizard Designer. The Operating System Deployment (OSD) Setup Wizard finishes. When the deployment process is complete. Goes to the previous wizard page. For more information about how to configure the OSD Results page. Solution Accelerators microsoft. Cancels the wizard and stops the UDI deployment process. The Page Behavior for the Summary page is configured to Silent. 10. On the Summary wizard page. see the “OSDResults.config File Element Values” section in the MDT 2010 document. Table 170. but there are problems with required information on the wizard page.325 Microsoft Deployment Toolkit 2010 Update 1 Setting Back Next Cancel Description Page in the UDI Wizard Designer. complete the page using the information in Table 170. Finishes the wizard and continues the deployment process to the target computer. Configuration Settings on the Summary Wizard Page Setting Summary Back Finish Cancel Description Contains a list of the configuration setting values and status collected by the wizard.

Customizing the MDT 2010 properties as described in Configuring the Appropriate MDT 2010 Properties. Joining target computers to AD DS domains as described in Joining Target Computers to AD DS Domains.326 Microsoft Deployment Toolkit 2010 Update 1 Configuring MDT 2010 Deployments Configure MDT 2010 deployments by: • • • • • • • • • • • Customizing the CustomSettings. The following section contains code samples that show how easily you can use these scripts to customize the deployment process. Creating custom scripts that integrate with the LTI and ZTI deployment process as described in Creating Custom Scripts for MDT 2010. Managing device drivers in LTI and ZTI deployments as described in Managing Device Drivers. Copying content to the target computers for LTI and ZTI deployments as described in Copying Content to the Target Computer. Creating preflight checks for UDI that are run on the Preflight Checks page in the Operating System Deployment (OSD) Setup Wizard as described in Creating Custom Preflight Checks for UDI.ini and Bootstrap. . • • • Customizing MDT 2010 Configuration Files MDT 2010 is flexible and highly customizable. but the ability to customize deployment to fit your organization’s needs is the core of MDT 2010’s strength. Configuring the MDT 2010 processing rules as described in Configuring MDT 2010 Processing Rules. Saving and restoring the user state migration data using USMT as described in Saving and Restoring User State Information. It includes several tools for getting started. Applying the MDT 2010 properties to groups of computers as described in Applying MDT 2010 Properties to Groups of Computers.ini files as described in Customizing MDT 2010 Configuration Files. Applying the MDT 2010 properties to individual computers as described in Applying MDT 2010 Properties to Individual Computers. Preparing disks on the target computers as described in Preparing Disks on Target Computers. Deploying software updates to the target computers as described in Deploying Software Updates to Target Computers. Configuring server roles for Windows Server operating systems in LTI and ZTI deployments as described in Configure Server Role Task Sequence Steps for LTI and ZTI.

ini files.ini file as described in Identify the CustomSettings.ini File Syntax.ini File Syntax. Configuring the properties in the CustomSettings.ini File Syntax The syntax of the CustomSettings.ini File.ini file for LTI deployments as described in Basic CustomSettings. MACAddress Properties=CustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac UserDataLocation=NONE [00:0F:20:35:DE:AC] CustomProperty=TRUE Solution Accelerators microsoft. Configuring the basic configuration settings for the CustomSettings.ini File.ini file as described in Properties in the CustomSettings. later in this guide. see Basic CustomSettings. • • Identify the CustomSettings.ini file as described in Identify the BootStrap.ini File Customized for ZTI Deployment [Settings] Priority=Default.ini file customized for ZTI. For more information about the CustomSettings.ini File for ZTI Deployments.ini file for ZTI deployments as described in Basic CustomSettings.ini File for ZTI.ini file is similar to many . CustomSettings.com/technet/SolutionAccelerators . Identifying the sections of the CustomSettings.ini file in Listing 1.ini file includes: • • • Sections Properties Settings Listing 1 shows a CustomSettings.ini file as described in Sections in the CustomSettings. A CustomSettings.ini File for LTI Deployments. Identifying the syntax of the BootStrap.327 Microsoft Deployment Toolkit 2010 Update 1 Customize the MDT 2010 configuration files by: • • • • Identifying the syntax of the CustomSettings. Listing 1. Configuring the basic configuration settings for the CustomSettings.

identified by the media access control [MAC] address of the target computer). see Applying MDT 2010 Properties to Individual Computers. For more information. later in this guide. [Settings]). the configuration settings in the [00:0F:20:35:DE:AC] and [00:03:FF:FE:FF:FF] sections are applied to the corresponding computer (in this case. The MDT 2010 scripts require the [Settings] section in CustomSettings. Properties are followed by an equal sign (=). [00:0F:20:35:DE:AC]. see Applying MDT 2010 Properties to Groups of Computers. the sections include [Settings].wsf. Toolkit Reference.com/technet/SolutionAccelerators . An individual computer. These predefined properties are declared in the ZTIGather. These properties are not configured in CustomSettings.ini File Properties are variables to which values must be assigned.ini file to locate the properties. The scripts scan the CustomSettings. In Listing 1. The types of properties that you can use in deploying target computers include properties that are: • Automatically declared in ZTIGather.ini and should be treated as read only. Required Sections Only the [Settings] section is required.ini file include the: • • Required sections as described in Required Sections. For more information. The sections in the CustomSettings. • Properties in the CustomSettings. In Listing 1. the configuration settings in the [Default] section are applied to more than one computer. In Listing 1.ini to locate the reserved properties (Priority and Properties). Optional sections as described in Optional Sections. Optional Sections You use the optional sections in the CustomSettings.ini File Sections are identified by brackets ([]) that surround the section name (for example.wsf file automatically sets the values for these properties. the ZTIGather. and [00:03:FF:FE:FF:FF]. [Default]. In addition. Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 328 [00:03:FF:FE:FF:FF] CustomProperty=FALSE Sections in the CustomSettings.ini file to assign a group of configuration settings to: • A group of computers. later in this guide. All other sections are optional.wsf code and are documented in the MDT 2010 document.

Toolkit Reference. and MDT DB. some properties are unique to ZTI or LTI deployment. These are custom properties that can be declared. the reserved properties perform specific functions in the deployment processing rules. or FALSE. TRUE. Configuring the values for properties as described in Values in the CustomSettings. When a property value is found. LTI deployments also have unique properties.xml file and are documented in the MDT 2010 document. [00:0F:20:35:DE:AC] or [00:03:FF:FE:FF:FF]).xml file. Priority Reserved Property The Priority reserved property determines the sequence and section in which you can find configuration values. However. Configuring the Properties reserved property as described in Properties Reserved Property. These predefined properties are listed in the ZTIGather. SkipCapture. Divide the properties in this file into properties that: • ZTIGather.ini file by: • • • Configuring the Priority reserved property as described in Priority Reserved Property.com/technet/SolutionAccelerators . BootStrap.wsf automatically sets the values for these properties. Section Types for the Priority Property Solution Accelerators microsoft.xml file. which must be treated as read only.wsf automatically assigns values to. the remaining sections are not used for that property.ini file.ini. ZTIGather. Table 171 lists the types of sections that you can reference in the Priority property.ini and is considered modifiable. Configure the CustomSettings. Like ZTI deployments. The way you use properties for ZTI and LTI are identical. Ensure that the value for any property to be used is set in CustomSettings. This is true for property values specified in the CustomSettings.329 Microsoft Deployment Toolkit 2010 Update 1 • Declared in the ZTIGather.wsf and in ZTIGather.xml. or SkipUserData).ini file. the [Default] section is parsed first. • • Declared in the Properties property. Most of the LTI-specific properties relate to the Windows Deployment Wizard (such as SkipAdministratorPassword. In Listing 1. Must be assigned values in CustomSettings. Note Property values must be specified in upper case so that the deployment scripts can properly identify them—for example. Each section is searched in the order specified. Table 171.wsf file retrieves these properties by scanning the ZTIGather. and they are in addition to the properties automatically declared in ZTIGather. YES. and then the section that corresponds to the MAC address of the target computer (in this case. The ZTIGather. Although these properties use the same syntax as other properties.ini File.

Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 330 Type MDT properties You can base sections on Any property known MDT 2010.com/technet/SolutionAccelerators . You can also define custom properties to which you can assign multiple values by adding numerical suffixes. if MySection is included in the Priority property. see “Example: Computer Groupings Selected by Woodgrove Bank” in Select the Method for Grouping Computers. ListProperty(*) defines the custom property as a list of property values instead of a single-valued property. For example. and so on. These user-defined properties are located by ZTIGather. A literal name that references a section. For example. can result in multiple section names being checked (because a computer can have multiple MAC addresses). MDT 2010 would search for properties not previously found in the [MySection] section. and ScanStateArgs is a predefined property.” in the MDT 2010 document. A literal name that you specify in the Priority property. which in turn references other sections. specifying the HostName property causes MDT 2010 to scan for a section with the target computer host name. if the DefaultGateway property is included in the Priority property. userdefined properties to be used in the deployment. In Listing 1. Literal section name Indirect reference Properties Reserved Property The Properties reserved property (shown in Listing 1) defines any custom. like MACAddress. For example. MDT 2010 would search for the [DefaultGateway] section. You create these types of custom properties by adding “(*)” to the end of the property name. For example. These properties are in addition to the predefined properties in MDT 2010. For an example of indirect reference using the DefaultGateway property. Consider the following excerpt from a CustomSettings. If the [DefaultGateway] section references other sections (based on the IP address of the default gateway).ini file in which ListProperty(*) is defined: [Settings] Priority=Default Solution Accelerators microsoft.ini file (or configuration database). CustomProperty is a user-defined property.wsf script in the CustomSettings. For a list of the predefined properties in MDT 2010. Other properties. this is an example of an indirect reference. such as ListProperty001. Toolkit Reference. see “Properties. ListProperty002.

ini file is illustrated in Listing 2. Listing 2. The template version in Listing 2 does not contain sufficient settings to successfully deploy Windows Vista to a target computer.ini. The scripts scan the CustomSettings. where installation_folder is the folder in which MDT 2010 is installed) as a basis for a customized version of CustomSettings.com/technet/SolutionAccelerators .ini file based on the responses provided. Unmodified CustomSettings. the file will be further customized using the Deployment Workbench.ini file (stored in installation_folder\Templates.ini File Values are the configuration settings assigned to the properties. the value assigned to the LoadStateArgs property is: /v:5 /c /lac Note the CustomSettings. even if the value contains spaces.331 Microsoft Deployment Toolkit 2010 Update 1 Property=CustomProperty. However.ini file to locate the values. Basic CustomSettings. the Deployment Workbench uses a template version of the CustomSettings.ini file is different from traditional INI files in that you do not place quotation marks around values. ListProperty(*) [Default] CustomProperty=TRUE ListProperty001=New York City ListProperty002=Chicago Values in the CustomSettings. Values are preceded by an equal sign (=).ini File for LTI Deployments For LTI deployments. Customized CustomSettings.ini File Modified by the Deployment Workbench [Settings] Solution Accelerators microsoft.ini File in the Templates Folder [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac The New Deployment Share Wizard in the Deployment Workbench modifies this template of the CustomSettings. Listing 3. Listing 3 shows the customized version of the CustomSettings.ini file after completing the New Deployment Share Wizard. The template version of the CustomSettings. In Listing 1.

Table 172. For LTI.exe during state capture.wsf parses ZTIGather. ZTIGather. Indicates that the computer is supposed to perform an operating system deployment. In this example. Table 172 explains the properties and corresponding values used in Listing 3. the [Default] section is the only subsection that is parsed for variables. Parameters passed to the Scanstate.com/technet/SolutionAccelerators . Indicates any additional properties to locate. These parameters are passed to Scanstate.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 332 Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac UserDataLocation=NONE SkipAppsOnUpgrade=NO SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES The CustomSettings. This version of the file contains no values unique to a specific target computer.ini Properties in Listing 3 Line in CustomSettings. The properties listed here are in addition to the properties listed in ZTIGather.xml. Explanation of CustomSettings. Properties=MyCustomPropert y [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c Solution Accelerators microsoft. Indicates the start of the [Default] section.ini [Settings] Priority=Default Purpose Indicates the start of the [Settings] section.ini file in Listing 3 contains the property values for all the target computers to be migrated using this version of the file. Establishes the sequence in which the process parses subsections to locate values for the variables.xml to obtain a list of the properties. the target computer–specific configuration values are manually provided during the installation process.exe tool in the USMT.

ini File in the Templates Folder [Settings] Solution Accelerators microsoft.com/technet/SolutionAccelerators . see the corresponding reference section in the MDT 2010 document. If the property is set to YES.exe tool in the USMT. Listing 4. Indicates whether the Allow user to set Administrator Password page in the Windows Deployment Wizard is displayed. These parameters are passed to Loadstate. the Deployment Workbench uses a template version of the CustomSettings. However. the file will be further customized using the Deployment Workbench. Indicates whether the Application to be installed during Upgrade page in the Windows Deployment Wizard is displayed.ini file (stored in installation_folder\Templates. where installation_folder is the folder in which MDT 2010 is installed) as a basis for a customized version of CustomSettings.ini file is illustrated in Listing 4. The template version of the CustomSettings.ini File for ZTI Deployments For ZTI deployments. Indicates where the user state migration data should be saved. Toolkit Reference. If the property is set to YES. the wizard page is skipped and not displayed.333 Microsoft Deployment Toolkit 2010 Update 1 Line in CustomSettings. The template version in Listing 4 does not contain sufficient settings to successfully deploy Windows Vista to a target computer. UserDataLocation=NONE SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=YES SkipProductKey=YES For more information on the individual properties. If the property is set to YES.ini. the wizard page is skipped and not displayed. Indicates whether the Allow user to specify a product key page in the Windows Deployment Wizard is displayed. the wizard page is skipped and not displayed. If the property is set to YES. Basic CustomSettings. The value NONE indicates that the user state migration data should not be saved. Indicates whether the Specify whether to prompt for image capture page in the Windows Deployment Wizard is displayed. the wizard page is skipped and not displayed.exe during state restore. Unmodified CustomSettings.ini LoadStateArgs=/v:5 /c /lac Purpose Parameters passed to the Loadstate.

ini file. After modifying the file. Customized CustomSettings. Modify the version of the template in the package source folder that you specified in Package source to be created on the MDT Package wizard page in the Create Microsoft Deployment Task Sequence Wizard as described in Create ZTI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard. For ZTI.ini File with Target Computer Settings [Settings] Priority=Default. Listing 6.ini File Modified by the Deployment Workbench [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac UserDataLocation=NONE The CustomSettings. This version of the file contains no values that are unique to a specific target computer.ini file shown in Listing 5 contains the property values for all of the target computers to be deployed using this version of the file.ini file based on the responses provided. Listing 5. the Create Microsoft Deployment Task Sequence Wizard copies an unmodified version of the CustomSettings.ini file after completing the New Deployment Share Wizard. Listing 6 shows a modified version of the CustomSettings.com/technet/SolutionAccelerators .ini file to include the target computer– specific configuration values.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 334 Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac The New Deployment Share Wizard in the Deployment Workbench modifies this template version of the CustomSettings. Listing 5 shows the customized version of the CustomSettings. MACAddress Solution Accelerators microsoft. Modify this version of the CustomSettings.ini template with no modifications to the file. update the distribution points for the Microsoft Deployment Files package so that the changes are available to the task sequences. which includes target computer–specific settings. Customized CustomSettings.

Properties=MyCustomProperty Indicates any additional properties to locate. and then the section that corresponds to the MAC address of the target computer (MACAddress) is parsed. the [Default] section is parsed first. ZTIGather. Explanation of CustomSettings. The sections for the target computers ([00:0F:20:35:DE:AC] and [00:03:FF:FE:FF:FF]) contain computer-specific settings.335 Microsoft Deployment Toolkit 2010 Update 1 Properties=MyCustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac UserDataLocation=NONE [00:0F:20:35:DE:AC] MyCustomProperty=TRUE [00:03:FF:FE:FF:FF] MyCustomProperty=FALSE Table 173 explains the properties and corresponding values used in Listing 6. Indicates whether the target computer is authorized to have the operating system installed. Table 173.xml to obtain a list of the properties. Establishes the sequence in which the process parses subsections to locate values for the variables.wsf parses ZTIGather. The properties listed here are in addition to the properties listed in ZTIGather. In this example.ini Properties in Listing 6 Line in CustomSettings.xml. Indicates the start of the [Default] section. MACAddress Purpose Indicates the start of the [Settings] section.com/technet/SolutionAccelerators .ini [Settings] Priority=Default. [Default] OSInstall=Y Solution Accelerators microsoft.

com/technet/SolutionAccelerators Solution Accelerators . logon credentials. The BootStrap. the target computer has a MAC address of [00:0F:20:35:DE:AC]. These parameters are passed to Loadstate. Toolkit Reference. errors and warnings are displayed when running the Windows Deployment Wizard. These parameters are passed to Scanstate.exe tool in the USMT. Use the BootStrap.ini file in the deployment share. In this sample.ini File Syntax In TI deployments. Section that contains all the properties and settings specific to the target computer with the matching MAC address. If not configured correctly. and Windows PE keyboard locale settings. the target computer has a MAC address of [00:03:FF:FE:FF:FF].ini file. Identify the BootStrap.ini file is identical to the CustomSettings. use the BootStrap.ini as follows: • DeployRoot Note Ensure that the DeployRoot property is specified in the BootStrap. The syntax of the BootStrap.ini help the MDT 2010 scripts locate the appropriate MDT 2010 distribution point. In this sample.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 336 Line in CustomSettings.ini ScanStateArgs=/v:5 /o /c Purpose Parameters passed to the Scanstate. Indicates where the user state migration data should be saved.ini file to provide distribution point information. Parameters passed to the Loadstate.exe during state restore.exe during the State Capture Phase. The properties configured in BootStrap.ini file.ini file to specify property settings before accessing the CustomSettings. as the LTI deployment process will not be able to locate the CustomSettings. LoadStateArgs=/v:5 /c /lac UserDataLocation=NONE [00:0F:20:35:DE:AC] [00:03:FF:FE:FF:FF] For more information on the individual properties.exe tool in the USMT.ini file contains a subset of the properties used in CustomSettings.ini file. Section that contains all the properties and settings specific to the target computer with the matching MAC address. The value NONE indicates that the user state migration data should not be saved. • SkipBDDWelcome microsoft. see the corresponding reference section in the MDT 2010 document.

ini file when you create a deployment share. Listing 7. Before configuring the deployment process.ini. see the corresponding section in the MDT 2010 document. For ZTI deployments. Toolkit Reference.ini file in Listing 7.com/technet/SolutionAccelerators . Listing 7 shows the BootStrap. The Deployment Workbench creates the BootStrap. For more information about the standard MDT 2010 configuration files. CustomSettings. BootStrap. After the initial creation. see Customizing MDT 2010 Configuration Files. the remainder of the settings can be provided manually during the deployment process.ini File As Created by the Deployment Workbench for Deployment Shares [Settings] Priority=Default [Default] DeployRoot=\\NYC-BDD-01\Distribution$ Configuring the Appropriate MDT 2010 Properties MDT 2010 uses wizards to create and manage configuration files. The properties selected must include all the configuration settings to be supplied during the deployment process.xml file to identify the appropriate sequence for performing the deployment process. provide a subset of the configuration settings that are provided automatically. provide all configuration settings required to deploy the target operating system. make all further customizations manually.ini file that the Deployment Workbench creates automatically for a deployment share.xml file include: Solution Accelerators microsoft.xml file.337 Microsoft Deployment Toolkit 2010 Update 1 • • • • UserDomain UserID UserPassword KeyboardLocale For more information about each of these properties. You may need to customize the BootStrap. select the properties to reference from the predefined or user-defined properties.ini and BootStrap. The MDT 2010 process occurs in the phases defined in the TS. The Task Sequencer parses the TS. The phases defined in the TS. you can customize configuration files to meet the needs of your organization. For LTI deployments. However.

” in the MDT 2010 document. Post Install Phase. Toolkit Reference. Applying MDT 2010 Properties to Groups of Computers Whenever possible. State Capture Phase.exe command as appropriate. “Properties. Group-based rules allow the same configuration settings to be applied to a group of client computers. including whether there is enough space to do a local USMT state backup.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 338 • Validate Phase. databases. and New Computer). Apply the properties to the groupings of computers as described in Apply the Properties to the Groups. and the local machine to determine how the image installation process should proceed. Select the properties required during each phase of the deployment process. Select the method of grouping multiple computers as described in Select the Method for Grouping Computers. State Restore Phase. • • • • • The TS. use group-based rules to apply most computer configuration settings.xml file.inf file. because these scenarios do not perform the State Capture Phase. Replace Computer. Preinstall Phase. you can supply computer-specific configuration settings using computer-based rules. specifically blocks installation on server operating systems. Invokes the USMT Loadstate. Performs validation checks to make sure that the operating system installation can proceed. Updates the Sysprep. Confirms that the necessary information has been gathered in the State Capture Phase for the Refresh Computer and Upgrade Computer scenarios. In the New Computer and Replace Computer scenarios. or Unattend. the script gathers the necessary information in this phase. 2. Apply properties to groups of computers by performing the following steps: 1. Refresh Computer. see the section. Also. The scripts also invoke the USMT Scanstate. Installs the target operating system on the target computers.exe command to restore the user state that was previously backed up. Sysprep. For more information on each of the properties used in each phase. Install Phase.txt file with information gathered in the previous custom actions based on the operating system being deployed.xml file identifies the appropriate steps in each phase based on each type of deployment scenario (Upgrade Computer. Solution Accelerators microsoft. a backup of the computer can be optionally performed for the Refresh Computer and Upgrade Computer scenarios. Gathers information from the configuration file. After applying group-based rules.

used [DefaultGateway] to designate the configuration settings for a specific Solution Accelerators microsoft. Table 174 lists methods of grouping computers. Woodgrove Bank. Model. and the script will search for the substituted value regardless. if you specify Priority=Make. and the properties that can be used to group the computers. Define locations using the user-defined properties in the [DefaultGateway] section. Apply configuration settings to all target computers when the properties are not in other sections. Note A variety of methods can be used to group computers by hardware configuration. [Dell Computer Corporation]. For example. or DefaultGateway).339 Microsoft Deployment Toolkit 2010 Update 1 Select the Method for Grouping Computers Different methods can be used to group client computers. Example: Computer Groupings Selected by Woodgrove Bank Listing 8 shows an example of how the fictional company. After determining how to group the computers. group computers based on any property that might be applied to a group of computers (such as Make. you can use the DefaultGateway property to designate the IP subnets on which a computer resides within a geographic location. as shown in Listing 8. Using the processing rules in MDT 2010. the script substitutes the value for Make that it determines through a Windows Management Instrumentation (WMI) call and will look for the corresponding section—for example. Table 174. Methods for Grouping Computers Grouping method Description Geographically Group configuration settings based on resources located within a geographic region (such as a shared folder on a computer within a geographic region).com/technet/SolutionAccelerators . Group configuration settings based on hardware attributes (such as the operating system version of the target computer). a description of the method. select the appropriate properties to help group them. computer groupings can be nested. For instance. Group configuration settings based on hardware attributes (such as the make of the computer or processor architecture of the target computer). Properties DefaultGateway Target computer hardware attributes Architecture CapableArchitecture Make Model HALName OSVersion Target computer software attributes Default attributes Default In most instances.

112. Three subnets (172. determine which properties and corresponding configuration settings to apply to each group. 172.3=DALLAS 172.2.111.16. Some examples of properties that are typically applied to groups of computers include: • BackupDir microsoft. In many environments.117.16.0.3.3=NYC 172.3) reside within the NYC location.16. Similar sections exist for the DALLAS and WASHINGTON locations. Properties that can be grouped are those you can apply to multiple computers.1.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 340 location.16.16.16. This is a special case that allows multiple default gateways to point to the same section.3=NYC 172. [NYC].0.3. includes the configuration settings specific to the NYC location.3=WASHINGTON 172. and 172.3=NYC 172.116. Listing 8.3=DALLAS 172.2.com/technet/SolutionAccelerators Solution Accelerators . a one-to-one mapping might be expected between the [DefaultGateway] section and a corresponding section. A separate section.16.16. Using [DefaultGateway] to Designate Location-Specific Configuration Settings [Settings] Priority=DefaultGateway [DefaultGateway] 172.3=WASHINGTON [NYC] UDShare=\\NYC-AM-FIL-01\MigData SLShare=\\NYC-AM-FIL-01\Logs Packages1=NYC00010-Install Packages2=NYC00011-Install Administrator1=WOODGROVEBANK\NYC Help Desk Staff [DALLAS] UDShare=\\DAL-AM-FIL-01\MigData SLShare=\\DAL-AM-FIL-01\Logs Administrator1=WOODGROVEBANK\DAL Help Desk Staff Apply the Properties to the Groups After identifying how to group configuration settings.1.16.16.

Solution Accelerators microsoft.341 Microsoft Deployment Toolkit 2010 Update 1 • • • • • • • • BackupShare CaptureGroups ComputerBackupLocation Packages SLShare UDDir UDShare UDProfiles Properties that are not applied to groups of computers are those specific to a particular computer. The rules for target computers allow the override or augmentation of group-based processing rules based on the priority of the computer-based rules. and Administrator1 are specified for each location. UDShare. The Administrator accounts that Administrator1 (WOODGROVEBANK\NYC Help Desk Staff and WOODGROVEBANK\DAL Help Desk Staff) reference are unique to each respective location. earlier in this guide. For more information about determining the priority of processing rules. The servers that UDShare and SLSShare (NYC-AM-FIL-01 and DAL-AMFIL-01) reference are within each respective location.com/technet/SolutionAccelerators . Examples of properties that are not appropriate to apply to groups of computers include: • • OSDAdapter0IPAddress OSDNewMachineName Example: Group-based Configuration Settings Selected by Woodgrove Bank Listing 8 showed an example in which Woodgrove Bank selects group-based configuration settings: • • • In the NYC and DALLAS locations. determine the method for identifying individual computers and the configuration settings to assign to each computer. location-specific packages are designated by Packages1 and Packages2. • Applying MDT 2010 Properties to Individual Computers After determining the groupings of target computers and configuration settings to be applied to each group. SLShare. In NYC. see Priority Reserved Property.

Listing 9. Product. Properties AssetTag. UUID. After applying group-based rules. select the appropriate properties. 00:03:FF:CB:4E:C2 and 00:0F:20:35:DE:AC).com/technet/SolutionAccelerators . OSSKU Identify the target computer using attributes that are assigned to the computer but not part of the hardware or software configuration. Group-based rules allow the same configuration settings to be applied to a group of computers. Woodgrove used the MAC address of the computer to identify the corresponding configuration settings for the computer (for example. AssetTag SerialNumber Example: Computer Identification Method Selected by Woodgrove Listing 9 shows an example of how Woodgrove Bank identified computer-based configuration settings. The configuration settings for each computer are listed immediately after the section that corresponds to the computer's MAC address. The processing rules allow the identification of computers based on any property that you might apply to an individual of computer (such as AssetTag. As when grouping computers. and Model Target computer software attributes Target computer user-defined attributes Identify the target computer OSVersion. using the software or firmware IsServerOS. UUID. In this instance. and configuration. Table 175 lists the methods of identifying individual computers. After selecting the method for identifying an individual target computer. SerialNumber. MACAddress. use group-based rules for most client computer configuration settings. more than one method is available for identifying individual computers. you can apply computer-specific configuration settings using computer-based rules. and so on). and the properties that you can use to identify the individual computers. Methods for Identifying Individual Computers Identification method Target computer hardware attributes Description Identify the target computer using the hardware configuration. Table 175. MACAddress.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 342 Whenever possible. Make. a description of the method. How Woodgrove Identified Client Computers [00:03:FF:CB:4E:C2] ComputerName=WasW2K Solution Accelerators microsoft.

TTTTTVVVVV-WWWWW-XXXXX-YYYYY.ini file or in the MDT DB. OverRideProductKey is the product key to be assigned to the computer—in this case. microsoft. HPD530-1. AAAAABBBBB-CCCCC-DDDDD-EEEEE. OverRideProductKey is the product key to be assigned to the computer—in this case. ComputerName is the name of the computer after Configuring MDT 2010 Processing Rules MDT 2010 scripts configure computer settings based on rules and configuration settings stored in the CustomSettings. Woodgrove Client Computers and the Corresponding Configuration Settings Target computer [00:03:FF:CB:4E:C2] Settings and description ComputerName is the name of the computer after deployment—in this case. BVMXP. [00:0F:20:35:DE:AC] ComputerName is the name of the computer after deployment—in this case.ini File. 1111122222-33333-44444-55555. Table 176. WasW2K.com/technet/SolutionAccelerators Solution Accelerators . OverRideProductKey is the product key to be assigned to the computer—in this case. Table 176 lists the computer-specific configuration settings applied to each computer. [00:03:FF:FE:FF:FF] deployment—in this case. Configure the MDT 2010 processing rules by completing the following tasks: • Configure the processing rules as described in Configure the Rules in the CustomSettings.343 Microsoft Deployment Toolkit 2010 Update 1 OverRideProductKey= TTTTT-VVVVV-WWWWW-XXXXX-YYYYY [00:0F:20:35:DE:AC] ComputerName=HPD530-1 OverRideProductKey= AAAAA-BBBBB-CCCCC-DDDDD-EEEEE [00:03:FF:FE:FF:FF] ComputerName=BVMXP OverRideProductKey= 11111-22222-33333-44444-55555 Example: Computer-based Configuration Settings Selected by Woodgrove Listing 9 also shows the computer-based configuration settings that Woodgrove Bank selected.

The disk-preparation process includes the following steps: • • • Creating partitions on one or more drives on the target computers Formatting one or more partitions on the target computers Preparing the disks on the target computers for BitLocker Drive Encryption Disk preparation occurs during the State Capture and Preinstall phases in the MDT 2010 deployment process.ini. The disk-preparation steps completed in the Preinstall Phase create and format the partitions on the target computer.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 344 • Configure the processing rules as described in Configure the Rules in the MDT DB. This change helps make the CustomSettings. Configure the Rules in the MDT DB Use the Deployment Workbench to configure the rules for LTI and ZTI deployments in the MDT DB.ini file.ini file. • For information about the MDT DB and using it to perform deployments. Centralizing the configuration for all property settings ensures consistency across all deployment shares. These configuration settings can be in addition to or instead of the group-based rules. The template version of the CustomSettings.com/technet/SolutionAccelerators . configuring group-based settings might be sufficient. you may need to customize the CustomSettings.ini template for LTI deployments only. the MDT 2010 deployment process prepares the disks on the target computer for deployment. add configuration settings unique to a specific client computer. Preparing Disks on Target Computers Prior to deploying the target operating system on a target computer. Storing the configuration settings in the MDT DB removes most of the detail from the CustomSettings.ini file. Depending on the environment. becomes the customized CustomSettings. It is a centralized repository for all property configuration settings. For LTI deployments. For ZTI deployments.ini file more generic so that you can use the same file in multiple deployment shares. The benefits of using the MDT DB include: • It has a more generic version of CustomSettings. along with the organization’s rules.ini. To prepare the disks on target computers in MDT 2010 Solution Accelerators microsoft. The disk-preparation step completed in the State Capture Phase is the disabling of BitLocker Driver Encryption on the target computer. see Performing Deployments Using the MDT DB. Configure the Rules in the CustomSettings.ini File Configure rules in CustomSettings.

Disk Preparation Properties Property BDEDriveLetter Description The drive letter for the partition that is not encrypted with BitLocker Drive Encryption.345 Microsoft Deployment Toolkit 2010 Update 1 • Review the task sequence steps used for saving and restoring user state information as described in Configure Disk Preparation Task Sequence Steps. see the corresponding section for each property in the MDT 2010 document. Table 177. You can configure these properties in CustomSettings. These task sequence templates include the task sequence steps listed in Table 177. which are used to perform disk-preparation steps. Table 178.com/technet/SolutionAccelerators BDEDriveSize BDEInstall BDEInstallSuppress Solution Accelerators . also known as the Sysvol The size of the BitLocker Drive Encryption system partition in megabytes The type of BitLocker Drive Encryption installation you are performing Indicates whether the deployment process microsoft. User State Information Task Sequence Steps Task sequence step Convert Disk to Dynamic Enable BitLocker Description Converts a physical disk from a basic disk type to a dynamic disk type. Toolkit Reference. • Configure Disk Preparation Task Sequence Steps MDT 2010 includes task sequence templates for LTI and ZTI deployments. For more information about the properties in Table 178. Configure the MDT 2010 properties used in saving and restoring user state information as described in Configure Disk Preparation Properties. available in ZTI task sequences only Configures BitLocker Drive Encryption on the target computer. available for LTI and ZTI task sequences Format and Partition Creates partitions and formats disks on the target Disk computer.ini or in the MDT DB. available for LTI and ZTI task sequences Disable BitLocker Disables BitLocker Drive Encryption on the current operating system drive or on a specific drive. available in ZTI task sequences only Configure Disk Preparation Properties Table 178 lists the MDT 2010 properties that control the preparation of disks on the target computers.

or %. the default is none.com/technet/SolutionAccelerators . The default value is MB. GB.) The type of file system for the partition (Valid values are NTFS or FAT32.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 346 Property Description should skip BitLocker Drive Encryption installation BDEKeyLocation BDEPin The location for storing the BitLocker Drive Encryption recovery key and startup key The PIN to be assigned to the target computer when configuring BitLocker Drive Encryption and the BDEInstall or OSDBitLockerMode properties are set to TPMPin A Boolean value that indicates whether the process creates a recovery key for BitLocker Drive Encryption Indicates whether the deployment process should not proceed until BitLocker Drive Encryption has finished the encryption process for all specified drives Disk number to which the image will be deployed The logical drive to which the image will be deployed Disk partition to which the image will be deployed The number of defined partition configurations (The maximum number of partitions you can configure is two.) OSDPartitionsxSize OSDPartitionsxSizeUnits The size of the partition The units of measure for specifying the size of the partition (Valid values are MB.) BDERecoveryKey BDEWaitForEncryption DestinationDisk DestinationLogicalDrive DestinationPartition OSDPartitions OSDPartitionsxBootable OSDPartitionsxFileSystem OSDPartitionsxQuickFormat Indicates whether the partition should be quick formatted (The default is TRUE.) The type of partition to be created The drive letter to be assigned to the partition OSDPartitionsxType OSDPartitionsxVolumeLette rVariable OSDPartitionsxVolumeName The volume name that will be assigned to the Solution Accelerators microsoft.) The partition that should be set to bootable (The default first partition is set to bootable.

ini or the MDT DB for LTI deployments Captures the group membership of the local groups microsoft. Configure the MDT 2010 properties used in saving and restoring user state information as described in Configure User State Information Properties. USMT saves the user state information to a desired location. User State Information Task Sequence Steps Task sequence step Description Generate Application Generates an XML file used to identify documents Migration Files created by applications installed on the target computer Capture User State Captures user state information based on the application migration files that the Generate Application Migration Files task sequence step generates and the user state information properties in CustomSettings. and other user-specific data stored on the target computer. USMT restores this user state information. The MDT 2010 deployment process uses USMT to save and restore user state information. • • Review User State Information Task Sequence Steps MDT 2010 includes task sequence templates for LTI and ZTI deployments. Later.347 Microsoft Deployment Toolkit 2010 Update 1 Property WipeDisk Description partition Indicates whether the disk should be wiped Saving and Restoring User State Information User state information consists of the user profile information. data files. Internet Explorer favorites. During the State Capture Phase in the MDT 2010 deployment process.com/technet/SolutionAccelerators Capture Groups Solution Accelerators . Table 179. To save and restore user state information on target computers in MDT 2010 • Review the task sequence steps used for saving and restoring user state information as described in Review User State Information Task Sequence Steps. These task sequence templates include the task sequence steps listed in Table 179. Customizing the USMT XML control files as described in Customize User State Migration XML Control Files. The MDT 2010 deployment process can automatically capture and restore user state information on the target computers. during the State Restore Phase. which are used to save and restore user state information.

Customize the user state migration XML control files for USMT by performing the following tasks: • Configure the XML control files for USMT for LTI deployments as described in Configure User State Migration XML Control Files for LTI Deployments.exe tool must save during the State Capture Phase The network share in which user state migration data is stored UDProfiles UDShare Configure User State Migration XML Control Files USMT uses the default versions of the migration XML files unless the path to the custom XML control files is indicated. Solution Accelerators microsoft. For more information about the properties in Table 180. Toolkit Reference.exe tool Indicates where the user state migration data should be saved The folder in which the user state migration data is stored (This folder exists beneath the network shared folder specified in the UDShare property.ini file or in the MDT DB.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 348 Task sequence step Description on the target computer based on the user state information properties in CustomSettings.exe tool List of parameters passed to the Scanstate.com/technet/SolutionAccelerators .) A comma-delimited list of user profiles that the Scanstate.ini or the MDT DB Restore User State Restores the user state information that the Capture User State task sequence step saved to the target computer Restores the group membership information that the Capture Groups task sequence step saved to the target computer Restore Groups Configure User State Information Properties Table 180 lists the MDT 2010 properties for LTI deployments that control saving and restoring user state information. Table 180. see the corresponding section for each property in the MDT 2010 document. User State Information Properties for LTI Deployments Property LoadStateArgs ScanStateArgs UserDataLocatio n UDDir Description List of parameters passed to the Loadstate. You can configure these properties in the CustomSettings.

Use the following format for these lines: USMTMigFiles1=MigApp. insert a line in the CustomSettings. you can store the XML control files in a separate package or network shared folder and specify a fully qualified UNC path to the package or network shared folder.xml Note See the MDT 2010 document. insert another line that sets the OSDMigrateMode task sequence variable to Advanced. Use the following format for these lines: OSDMigrateMode=Advanced OSDMigrateConfigFiles=MigApp. If you specify the OSDMigrateConfigFiles property.MigUser.xml The path to the XML control files is relative to the current folder. Joining Target Computers to AD DS Domains One of the final steps in completing the deployment of a target operating system to the target computers is joining the computer to an AD DS domain.com/technet/SolutionAccelerators Solution Accelerators . insert one or more lines in the CustomSettings.xml USMTMigFiles4=MigCustom. Configure User State Migration XML Control Files for LTI Deployments For LTI deployments. update this package each time you modify any of the XML control files. If you keep the XML control files in the USMT package. Toolkit Reference.ini file that contains the OSDMigrateConfigFiles task sequence variable for the USMT migration XML control file that you want to specify. Otherwise.xml USMTMigFiles2=MigUser. Configure User State Migration XML Control Files for ZTI Deployments For ZTI deployments.xml USMTMigFiles3=MigSys. The XML files need to be copied into either the USMT folder or the Scripts folder in the distribution share. Although you can complete this process manually.xml.349 Microsoft Deployment Toolkit 2010 Update 1 • Configure the XML control files for USMT for ZTI deployments as described in Configure User State Migration XML Control Files for ZTI Deployments.xml USMTConfigFile=Config. which will be the location of the USMT package. for details on configuration settings.ini file that contain the USMTMigFiles property for each of the USMT migration XML control files that you want to specify. MDT 2010 supports the following automated methods for joining target computers to AD DS domains: • Using the Windows Deployment Wizard as described in Join Domains Using the Windows Deployment Wizard microsoft.

Solution Accelerators microsoft.xml as described in Join Domains by Modifying the Unattended. Specifies the domain in which the account specified in User Name is located.xml File Using the Recover from Domain Join Failure task sequence step type as described in Join Domains Using the Recover from Domain Join Failure Task Sequence Step Type Using the offline domain join feature in Windows Server 2008 R2 and Windows 7 as described in Join Domains Using Offline Domain Join • Join Domains Using the Windows Deployment Wizard For LTI deployments.ini File Modifying Unattended. Specifies the domain to which the target computer is to be joined. For more information about completing the Join the computer to a domain or workgroup wizard page in the Windows Deploy Wizard. see Complete the Windows Deployment Wizard. Table 181. This text box is enabled only when you select Join a domain. User Name Password Domain Organizational Unit Specifies the OU in which the computer account will be created in the domain specified in Domain. This text box is enabled only when you select Join a domain. Specifies the account to be used in joining the target computer to the domain specified in Domain. Configuration Settings on the Join the computer to a domain or workgroup wizard page for Joining Domain Setting Join a domain Domain Description Select to configure the Windows Deployment Wizard to join the target computer to a domain. This text box is enabled only when you select Join a domain. This text box is enabled only when you select Join a domain.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 350 • • • Modifying CustomSettings.ini as described in Join Domains by Modifying the CustomSettings.com/technet/SolutionAccelerators . Specifies the password for the account specified in User Name. This text box is enabled only when you select Join a domain. Table 181 lists the configuration settings on this wizard page used in joining a domain. the Join the computer to a domain or workgroup wizard page in the Windows Deploy Wizard in MDT 2010 allows you to interactively provide the configuration settings necessary to join a domain.

351 Microsoft Deployment Toolkit 2010 Update 1 Join Domains by Modifying the CustomSettings. Table 182.ini to Modify for Joining a Domain Property DomainAdmin Description The user account credentials used to join the target computer to the domain specified in JoinDomain.com The domain in which the user’s credentials specified in DomainAdmin reside The password used for the domain Administrator account specified in the DomainAdmin property to join the computer to the domain The domain that the target computer joins after the target operating system is deployed (This is the domain in which the computer account for the target computer is created. Properties in CustomSettings.xml file used in the MDT 2010 deployment process. The JoinDomain property can contain alphanumeric characters.ini File You can automate the domain-join process for LTI or ZTI deployments by modifying the properties listed in Table 182 in the CustomSettings. hyphens [-].xml File You can automate the domain-join process for LTI or ZTI deployments by modifying the settings listed in Table 183 in the Unattended. specify as Domain\UserName or UserName@Domain. Table 183. The JoinDomain property cannot be blank or contain spaces.xml to Modify for Joining a Domain Setting Username Domain Password Description The user account credentials used to join the target computer to the domain specified in JoinDomain The domain in which the user’s credentials specified in Username reside The password used for the domain Administrator account specified in the Username setting to join the computer to the domain microsoft. Settings in Unattended.ini file used in the MDT 2010 deployment process.com/technet/SolutionAccelerators Solution Accelerators .) The AD DS OU in the target domain in which the computer account for the target computer is created DomainAdminDomain DomainAdminPasswor d JoinDomain MachineObjectOU Join Domains by Modifying the Unattended. and underscores [_].

go to Deployment Workbench/Deployment Shares/deployment_share/Task Sequences (where deployment_share is the name of the deployment share in which you will configure the task sequence). 2. Select this method when you want the MDT 2010 process to allow the user to retry the domain-join process. click Properties. 4. In the details pane.com/enus/library/cc748842(WS. 3.microsoft. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). Select this method when you want the MDT 2010 process to automatically retry the domain-join process. You can configure the Recover from Domain Join Failure task sequence step type to recover using one of the following methods: • Auto Recover (Rerun Join Domain).aspx. In the Deployment Workbench console tree. Point to Microsoft Deployment Toolkit. Select this method when you want MDT 2010 to stop running the task sequence if the computer has not successfully joined the domain. No Recover (Stop script execution).10). This method automatically terminates the task sequence if the computer has not successfully joined the domain. Click Start. In the Actions pane. and then point to All Programs.com/technet/SolutionAccelerators . Manual Recover (Allow user to Join Domain).Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 352 Setting JoinDomain MachineObjectOU Description The domain that the target computer joins after the target operating system is deployed The AD DS OU in the target domain in which the computer account for the target computer is created For more information about these settings. see Microsoft-WindowsUnattendedJoin at http://technet. This method automatically retries the domain-join process without intervention. and then click Deployment Workbench. • • To configure task sequence steps based on the Recover from Domain Join Failure task sequence step type 1.ini. This method allows the user running the Windows Deployment Wizard to retry the domain-join process. Join Domains Using the Recover from Domain Join Failure Task Sequence Step Type Task sequence steps based on the Recover from Domain Join Failure task sequence step type retry the domain-join process using the configuration information specified in CustomSettings. Solution Accelerators microsoft.

which is always set to Recover from Domain Join Failure Contains name of the task sequence step displayed in the task sequence Provides descriptive information about the task sequence step Select to configure the task sequence step to automatically retry the domain-join process without intervention Select to configure the task sequence step to allow the user to retry the domain-join process Select to configure the task sequence step to stop the task sequence if the computer has not successfully joined the domain Join Domains Using Offline Domain Join Offline domain join is a new process that computers running Windows 7 or Windows Server 2008 R2 can use to join a domain without contacting a domain controller. and then click OK. and then click the Properties tab. configure the settings listed in Table 184 based on the requirements of your organization. 5.com/technet/SolutionAccelerators . go to task_sequence_step. This process makes it possible to join computers to a domain in locations where there is no connectivity to a corporate network. target computers can be joined to the domain when they initially start after the installation of the target operating system.xml file in Windows 7 and Windows Server 2008 R2 includes the Microsoft-WindowsUnattendJoin/Identification/Provisioning section. On the Task Sequence tab.353 Microsoft Deployment Toolkit 2010 Update 1 The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). Using offline domain join. which includes the configuration settings for performing a domain join. On the Properties tab. No additional restart is required to complete the domain-join process.xml file. Solution Accelerators microsoft. 6. in the task sequence hierarchy. The offline domain join is a variant on joining domains by modifying the Unattend. which can significantly reduce the overall time required for wide-scale VM deployments. Table 184. The Unattend. Configuration Settings on the Properties Tab of the Recover from Domain Join Failure Task Sequence Step Type Setting Type Name Comments Auto Recover (Rerun Join Domain) Manual Recover (Allow user to Join Domain) No Recover (Stop script execution) Description Contains the task sequence type.

com/enus/library/dd392267(WS.aspx#BKMK_ODJSteps.microsoft.exe) Step-by-Step Guide at http://technet. • • Select the Software Update Deployment Strategy The software update deployment strategies are based on when the software updates are to be installed. These software updates are required to ensure a consistent configuration baseline for all the target computers. Configuring the Unattended. device drivers.wsf script.com/enus/library/dd392267(WS. see Offline Domain Join (Djoin.10). Deploy Software Updates with Windows Update Agent for LTI Deployments In LTI deployments. Some of the LTI task sequence templates provided in MDT 2010 include the Windows Update (Pre-Application Installation) task sequence step and the Windows Update (Post-Application Installation) task sequence step. see the section. You can install software updates: • • As a part of the image deployed to the target computers. Deploying software updates using the Deployment Workbench for LTI deployments as described in Deploy Software Updates with Deployment Workbench for LTI Deployments. you can install software updates from Windows Update or from WSUS using a task sequence step that runs the ZTIWindowsUpdate. • Deploying Software Updates to Target Computers In addition to the target operating system. and other software components.exe) Step-byStep Guide at http://technet.aspx#BKMK_ODJSteps. you may need to apply software updates to all these software components. “Performing an offline domain join by using an unattended operating system installation.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 354 For more information about: • The offline domain join process. After the target operating system is deployed to the target computers. Solution Accelerators microsoft. Deploying software updates using System Center Configuration Manager for ZTI deployments as described in Deploy Software Updates with System Center Configuration Manager for ZTI Deployments. Deploy software updates to target computers in MDT 2010 by: • • Selecting the appropriate strategies for deploying software updates as described in Select the Software Update Deployment Strategy. applications.microsoft.10). Deploying software updates using Windows Update Agent–based technologies for LTI deployments as described in Deploy Software Updates with Windows Update Agent for LTI Deployments.xml file to perform offline join.com/technet/SolutionAccelerators .” in Offline Domain Join (Djoin.

you can initiate software updates using a task sequence step based on the Install Software Updates task sequence step type.355 Microsoft Deployment Toolkit 2010 Update 1 You can also create a custom task sequence step based on the Run Command Line task sequence step type that runs the following command line: Cscript.com/technet/SolutionAccelerators .exe "%SCRIPTROOT%\ZTIWindowsUpdate. which is based on the Install Updates Offline task sequence step type. You can control the software updates deployed to the target computers by this method using selection profiles. see Create a New Selection Profile in Deployment Workbench. Table 185. The Install Software Updates task sequence type allows you to install only mandatory or all software updates in a single task sequence step using one of the configuration options listed in Table 185. Deploy Software Updates with System Center Configuration Manager for ZTI Deployments In ZTI deployments. create a task sequence step for each selection profile. Configuration Settings on the Properties Tab of the Install Software Updates Type Task Sequence Step Setting Name Description Mandatory Software Updates All Software Updates Description Configures the name of the task sequence step displayed in the task sequence hierarchy Configures the description text for the task sequence step Select to configure the task sequence step to install only mandatory software updates Select to configure the task sequence step to install all software updates.wsf" Deploy Software Updates with Deployment Workbench for LTI Deployments In LTI deployments. and then specify the corresponding selection profile in the task sequence step. including mandatory software updates Solution Accelerators microsoft. If you want to deploy software updates based on multiple selection profiles. For more information on creating selection profiles. Some of the LTI task sequence templates provided in MDT 2010 include the Apply Patches task sequence step. The Install Updates Offline task sequence step allows you to specify a selection profile so that you can specify which software updates to deploy. you can install software updates in the Packages node in the Deployment Workbench for Windows Vista or later operating systems using a task sequence step based on the Install Updates Offline task sequence step type.

aspx. In this strategy. all the drivers are deployed to the target computer. Managing device drivers using System Center Configuration Manager for ZTI deployments as described in Control Device Driver Deployments for ZTI. This requires that you configure the ZTI and LTI process to control which device drivers are deployed to the target computer. Managing Device Drivers Device driver management is a critical component in deploying operating systems to target computers. Include only the device drivers specifically required for the target computer. • Table 186 lists the advantages and disadvantages of these device driver management strategies. Manage device drivers using MDT 2010 by: • • • • Selecting the appropriate strategies for managing device drivers as described in Select the Device Driver Management Strategy. see Install Software Updates at http://technet. Windows PE and the target operating system use Plug-andPlay IDs to identify the device drivers needed for the devices on the target computers. Then. This is the default behavior for LTI and ZTI deployments. Table 186.microsoft.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 356 For more information about the Install Software Updates task sequence type. The proper device drivers must be available to Windows PE and to the target operating system for the deployment to be successful. only the device drivers specific to the target computer are deployed to the target computer. Select the Device Driver Management Strategy The following are the high-level strategies for performing device driver management: • Include all device drivers. • Images require more frequent version Solution Accelerators microsoft. In this strategy. Resolving device driver signing issues as described in Resolve Device Driver Signing Issues.com/enus/library/bb632402. Advantages and Disadvantages of Device Driver Management Strategies Strategy Include all device drivers Advantages • Requires less initial time and effort to identify the appropriate Disadvantages • Images are larger.com/technet/SolutionAccelerators . Managing device drivers using the Deployment Workbench for LTI deployments as described in Control Device Driver Deployments for LTI.

A complex management structure used in the “Include only the device drivers specifically required for the target computer” strategy might be too complex for managing small environments with only two or three different types of computers and cause you to spend a lot of unnecessary time up front. • Can introduce unnecessary management overhead when there are fewer device drivers to manage. Either of these strategies can cause problems if taken to the extreme. select a device driver management strategy that is a hybrid of these strategies and best fits your organization. • Images require less frequent version updates. The high-level approach to device driver management using the Deployment Workbench for LTI deployments is: Solution Accelerators microsoft. • Requires more initial time and effort to identify the appropriate drivers. The “Include all device drivers” strategy might cause problems when trying to manage tens of thousands of device drivers because of the larger download sizes and a higher probability of detecting the wrong device drivers. • Does not work well if there are a large number of device drivers to manage. • All mass storage drivers for Windows XP and Windows Server 2003 are included.357 Microsoft Deployment Toolkit 2010 Update 1 Strategy Advantages drivers. • Works well when there is a large number of device drivers to manage. Control Device Driver Deployments for LTI The goal of managing device drivers for LTI deployments is to help ensure that only the appropriate device drivers are deployed to the target computers without introducing unnecessary effort and management overhead. Include only the device drivers specifically required for the target computer • Ongoing management of device drivers in the image requires less effort. In most instances. because there are more drivers in the image. • Works well when there are fewer device drivers to manage. • Ongoing management of device drivers in the image requires more effort. because there are fewer drivers in the image. • Images are smaller. • Windows XP and Windows Server 2003 images should still include all mass storage drivers.com/technet/SolutionAccelerators . Disadvantages updates.

• • The complexity of the folder structure that you create is based on the level of precision you want for deploying the device drivers. you can select the appropriate folder structure based on task sequence variables later in the process. you could organize your device drivers by creating the following folder structure in the Out-of-Box Drivers node in the Deployment Workbench based on operating systems. Create selection profiles used to select the device drivers for deployment based on the folder structure you created in the previous step as described in Create Selection Profiles to Select the Device Drivers for LTI Deployments. Select this method to deploy only the device drivers to the target computer based on the respective target operating system. Select this method to deploy only the device drivers to the target computers based on the respective processor architecture (32-bit or 64-bit). For example. Create a folder structure in the Out-of-Box Drivers node of the Deployment Workbench to organize the device drivers as described in Create Folders to Organize Device Drivers for LTI Deployments.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 358 1. you may have or expect to have one of the following problems: • Device drivers are being selected for the wrong operating system. the more complex the folder structure. Manufacturer (make) and model of the target computers. Processor architecture of the target computers. Select this method to deploy device drivers to the target computer based on the respective make and model of the target computer. In this case. The more precision you want. and then place the device drivers in the corresponding folders: • • Windows 7 Windows Server 2003 microsoft. Tip If the name of the folder matches the value that the BIOS returned for make and model. You can also select a method for creating folder structures based on specific problems you may be having or to mitigate an existing problem. Configure tasks sequences to deploy the device drivers in the selection profiles as described in Configure Task Sequences to Deploy Device Drivers in Selection Profiles for LTI Deployments. The folder structure groups or categorizes device drivers so that you can select specific groupings or categories of drivers using selection profiles. 3.com/technet/SolutionAccelerators Solution Accelerators . Create Folders to Organize Device Drivers for LTI Deployments Create folder structures in the Out-of-Box Drivers node in the Deployment Workbench to provide the level of control you want for deploying device drivers to target computers. Select any combination of the following methods for creating folder structures: • Target operating system. 2.

you could organize your device drivers by creating the following folder structure in the Out-of-Box Drivers node in the Deployment Workbench based on processor architecture. and processor architecture: make\model\operating_system\architecture Figure 2 illustrates the folder structure Woodgrove Bank created. operating system. In this case.com/technet/SolutionAccelerators . So. and then place the device drivers in the corresponding folders: • • x86 x64 • Device drivers are being selected for the wrong make and model of target computer.359 Microsoft Deployment Toolkit 2010 Update 1 • • • • Windows Server 2008 Windows Vista Windows XP Device drivers are being selected for the wrong processor architecture. In this case. and then place the device drivers in the corresponding folders: • make_01\ …\model_01 …\model_02 …\model_03 • make_02\ …\model_aa …\model_ab • make_03\ …\model_xx …\model_xy Example: Woodgrove Bank Device Driver Folder Structure for LTI Woodgrove Bank has decided that it wants to maintain precise control over the device drivers deployed to target computers. Solution Accelerators microsoft. you could organize your device drivers by creating the following folder structure in the Out-of-Box Drivers node in the Deployment Workbench based on the make and model of the target computer. its IP pros create a folder structure in the Out-of-Box Drivers node in the Deployment Workbench that organizes the device drivers by make and model.

32-bit Device Drivers. selection profiles deploy the device drivers in the selected folder and subfolders.Model A532. Create selection profiles based on the level of control you want to have over the device drivers being deployed. Windows XP 64-bit Device Drivers. By default. in CustomSettings. The LTI deployment process uses selection profiles to determine the device drivers to deploy in the Inject Drivers task sequence step type.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 360 Figure 2.ini. and you have less granular control over the device drivers deployed. Example: Woodgrove Bank Device Driver Selection Profiles for LTI Deployments Solution Accelerators microsoft. such as Windows 7 32-bit and 64-bit Device Drivers. Tip Use selection profile names that allow you to easily identify the device drivers included in them.com/technet/SolutionAccelerators . If you create selection profiles on folders: • • Higher in the folder structure. fewer device drivers are included. and in the MDT DB. and you have more granular control over the device drivers deployed. Lower in the folder structure. more device drivers are included. Device driver folder structure created by Woodgrove Bank Create Selection Profiles to Select the Device Drivers for LTI Deployments Create selection profiles to identify the combination of device drivers that you want to deploy to specific target computers based on the folder structure you created in the Out-of-Box Drivers node in the Deployment Workbench. or Fabrikam .

The LTI deployment process creates the list of device drivers to deploy based on the union of both selection profiles and device driver groups. A specific set of device drivers for the selection profile and the device driver group so that a known set of device drivers is deployed. the CustomSettings. the result will include all device drivers. The Nothing selection profile in the Inject Driver task sequence step. For example.ini file or the MDT DB. Selection profiles and device driver groups are additive.com/technet/SolutionAccelerators . specify: • The Nothing device driver group in the CustomSettings. or the MDT DB to allow the device driver group to control the device drivers deployed to the target computer. the CustomSettings. because the default selection profile and default device driver group include all device drivers. or the MDT DB.361 Microsoft Deployment Toolkit 2010 Update 1 Woodgrove Bank has decided that it wants to maintain precise control over the device drivers deployed to target computers. Device driver groups that can be configured in the CustomSettings.ini file. Selection profiles are exposed to the LTI deployment process as: • • Selection profiles that can be configured in the Deployment Workbench. So. • • The following are strategies for configuring task sequences to control the deployment of device drivers for LTI deployments: Solution Accelerators microsoft.ini file or the MDT DB to allow the selection profile to control the device drivers deployed to the target computer. its IT pros create a selection profile for each leaf-level folder in following folder structure: make\model\operating_system\architecture Woodgrove Bank named the selection profiles based on the folder structure in the format as follows: make–model-operating_system–architecture The following is an example of the Woodgrove Bank selection profile naming convention for 64-bit device drivers for Windows 7 running on a computer with “Fabrikam” as the make and “FK5323” as the model: “Fabrikam–FK5323–Win7–x64” Configure Task Sequences to Deploy Device Drivers in Selection Profiles for LTI Deployments Modify The configuration for your task sequences to reference the selection profiles and deploy the appropriate device drivers to the target computers.ini file. if you specify a selection profile that contains only 64-bit device drivers and leave the default device driver group. To change this behavior. which can cause unpredictable results.

and then used the DriverSelectionProfile task sequence variable in the CustomSettings.ini file for the DriverSelectionProfile task sequence variable: DriverSelectionProfile =%MAKE%-%MODEL%-Win7-%ARCHITECTURE% Note The operating system is a static value for the DriverSelectionProfile task sequence variable. but specify additional device drivers to be added using the DriverGroup task sequence variable. use selection profiles or the DriverGroup task sequence variable. which is in most of the LTI task sequence templates. Its IT pros have created a device driver folder structure and selection profile strategy that allows detailed control of device drivers. Because selection profiles and device driver groups are additive. configure the Inject Driver task sequence step to use the Nothing selection profile. • Example: Woodgrove Bank Device Driver Task Sequence Configuration for LTI Deployments Woodgrove Bank has decided that it wants to maintain precise control over the device drivers deployed to target computers. to use the selection profile.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 362 • For a single selection profile. and then configure each task sequence step with the corresponding selection profile. this method is provided for backward compatibility with previous versions of BDD and MDT. However. For a limited number of selection profiles. The IT pros added the following line in their CustomSettings. If you want to use the DriverGroup task sequence variable for backward compatibility with previous versions of MDT. because the task sequence will deploy only one operating system. add an Inject Driver task sequence step for each selection profile.ini file and the MDT DB to override the selection profile specified in the Inject Driver task sequence step as necessary. If you have multiple all Inject Driver task sequence steps in your task sequence. Note The selection profile you specify in the DriverSelectionProfile task sequence variable overrides all Inject Driver task sequence steps in a task sequence. • • • Configure a single Inject Driver task sequence step in the task sequence (which already exists in most of the LTI task sequence templates). the device drivers specified in the DriverGroup task sequence variable are deployed in addition to the device drivers in the selection profile. Note You can also use the DriverPaths property to specify the UNC path to the folders containing the device drivers to deploy. modify the Inject Driver task sequence step. Configure a single Inject Driver task sequence step in your task sequence. Solution Accelerators microsoft. and then override the selection profile specified in the Inject Driver task sequence step using the DriverSelectionProfile task sequence variable in the CustomSettings. Instead.com/technet/SolutionAccelerators . they all will be overridden. The IT pros configured their task sequences using the Inject Driver task sequence step in their task sequences with the most common configuration in their organization.ini file or the MDT DB.

You can control the device drivers deployed to the target computer based on the device driver categories using the Auto Apply Drivers task sequence step. Device driver categories allow you to specify a category for each device driver you import into the driver catalog. Control the deployment of device drivers by performing the following steps: microsoft. configure the task sequence step to run when the Make and Model task sequence variables equal the make and model for the device driver package. device driver packages are distributed to distribution points so that they are accessible to the target computers. Categories allow you to group device drivers based common characteristics. 3. You can control the device drivers deployed based on the device driver packages using the Apply Driver Package task sequence step. You can create multiple device driver packages to group device drivers to be deployed to the target computer. Create device driver categories based on the level of granularity you want in controlling the device drivers to be deployed. allowing the target operating system to select the device drivers required. • Create multiple device driver packages that are configured in multiple Apply Driver Package task sequence steps. By default. The list that follows provides strategies for configuring task sequences to control the deployment of device drivers for ZTI deployments: • Create multiple device driver categories that are configured in multiple Auto Apply Drivers task sequence steps. Control the deployment of device drivers by performing the following steps: 1. 2. if the device driver packages are based on the make and model of the target computer.363 Microsoft Deployment Toolkit 2010 Update 1 Control Device Driver Deployments for ZTI ZTI deployments use the driver catalog in System Center Configuration Manager as the central repository for device drivers. Configure the task sequence step conditions based on the contents of the device driver package. such as the make and model of target computer. Like software packages. you can organize them by: • Device driver packages. • Most of the ZTI task sequences created using the MDT 2010 task sequence templates include the Auto Apply Drivers task sequence step. After you import device drivers into the driver catalog. Configure the Auto Apply Drivers task sequence step to use the proper combination of device driver categories using the Limit driver matching to only consider drivers in selected categories list box. Device driver categories. Add multiple Auto Apply Drivers task sequence steps based on the number of combination categories you want to deploy. 4. such as all network adapter drivers or by processor architecture. this step configures the task sequence to deploy all device drivers to the target computer. For example.com/technet/SolutionAccelerators Solution Accelerators .

Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 364 1.echo DriverGuid. Configure the task sequence step conditions based on the contents of the device driver package. if the device driver packages are based on the make and model of the target computer. Determine GUIDs for each device driver category you created by running the following script. and then override the selection profile specified in the Auto Apply Drivers task sequence step using the OSDAutoApplyDriverCategoryList task sequence variable in the CustomSettings. 4. 2. configure the task sequence step to run when the Make and Model task sequence variables equal the make and model for the device driver package. For example. 4. • Configure a single Auto Apply Drivers task sequence step in your task sequence. For each device driver package. Configure the Auto Apply Drivers task sequence step to use any of the device driver categories using the Limit driver matching to only consider drivers in selected categories list box. 2. Note The device driver category you select is not important. Control the deployment of device drivers by performing the following steps: 1.ini file or the MDT DB. as the category will be overridden by the OSDAutoApplyDriverCategoryList task sequence variable. Create device driver packages based on the criteria for limiting the device drivers to be deployed. add an Apply Driver Package task sequence step for each category.CategoryInstance_UniqueID Solution Accelerators microsoft.ExecQuery("select CategoryInstance_UniqueID from CMDB_categoryinstance where LocalizedCategoryInstanceName = '" & strDriverCatName & "'") For each DriverGuid in DriverGuids wscript. strServer with you System Center Configuration Manager site server. Configure the Apply Driver Package task sequence step to use the corresponding device driver package. substituting strSiteCode with your site code. 3. Create device driver categories based on the level of granularity you want in controlling the device drivers to be deployed. 3. and strDriverCatName with the name of a device driver category you created: strSiteCode = "NYC" strServer = "CMSERVER" strDriverCatName = "Fabrikam" set objWMIService= GetObject("winmgmts: {impersonationlevel=impersonate}!\\" & strServer & "\root\sms\site_" & strSiteCode) set DriverGUIDS = objWMIService. Add a new or an existing Auto Apply Drivers task sequence step in your task sequence.com/technet/SolutionAccelerators .

and Windows Server 2008. Review the following resources to help you resolve device driver signing issues: • • Driver Signing Requirements for Windows at http://www. Note Deploying mass storage drivers using the Apply Driver Package task sequence step will overwrite any mass storage sections in the sysprep. because the Auto Apply Drivers task sequence requires connectivity to a management point. Windows Vista with SP1. The Auto Apply Drivers task sequence cannot be used for mass storage drivers for these operating systems.microsoft. and the stand-alone media will not attempt a connection to a management point. use an Apply Driver Package task sequence step. because you must explicitly deploy the correct mass storage drivers and only the Apply Driver Package task sequence step can do so. Resolve Device Driver Signing Issues Digital signatures tell you whether a device driver is provided by a legitimate publisher. you might need to modify an INF file for a device driver.com/en-us/library/cc754052(WS. In many instances. Windows Server 2008 R2. New features take advantage of code-signing technologies. there may be instances where you modify the files include with the device drivers and need to sign the device drivers again.microsoft.aspx Solution Accelerators microsoft. In Windows 7.com/whdc/winlogo/drvsign/drvsign. and new requirements for security in the operating system enforce the use of digital signatures for some kinds of code.com/technet/SolutionAccelerators .365 Microsoft Deployment Toolkit 2010 Update 1 Next 5.mspx Device Management and Installation Step-by-Step Guide: Signing and Staging Device Drivers in Windows Vista and Windows Server 2008 at http://technet. Modify the CustomSettings. However. • When performing deployments using stand-alone media. and then sign the device driver. substituting SECTION with the name of a section (such as [Default]) and GUID with the GUID you retrieved in the previous step: [Settings] Properties=OSDAutoAPplyDriverCategoryList [SECTION] OSDAutoApplyDriverCategoryList=DriverCategories:GUID • Deploy mass storage device drivers for Windows XP and Windows Server using an Apply Driver Package task sequence step.inf file. For example.ini file as follows.10). device drivers from vendors are already signed.

Configure task sequence steps in MDT 2010 to deploy the server roles that are supported in MDT 2010. microsoft. An AD DS domain controller is a server that runs AD DS. Configuring the Authorize DHCP task sequence step as described in Configure Authorize DHCP Task Sequence Step Settings for LTI and ZTI. Configuring the DNS Server server role task sequence step as described in Configure DNS Server Role Settings for LTI and ZTI. Configure AD DS Server Role Task Sequence Step Settings for LTI and ZTI AD DS stores directory data and manages communications between users and domains. Configure the AD DS Server Role task sequence step by: • • Deploying a new domain controller in a new forest as described in Deploy a Domain Controller in a New Forest. Deploying a new domain controller in a new domain tree in an existing forest as described in Deploy a New Domain Controller in a New Domain Tree in an Existing Forest. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps.com/technet/SolutionAccelerators • • Solution Accelerators . Deploying a new domain controller in a new domain in an existing forest as described in Deploy a New Domain Controller in a New Domain in an Existing Forest. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. Configure the Windows Server 2008 server role task sequence steps for LTI and ZTI deployments by: • • • • Configuring the AD DS server role task sequence step as described in Configure AD DS Server Role Task Sequence Step Settings for LTI and ZTI.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 366 Configure Server Role Task Sequence Steps for LTI and ZTI MDT 2010 automates the deployment of server roles in Windows Server 2008. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. Configuring the DHCP Server server role task sequence step as described in Configure DHCP Server Role Task Sequence Step Settings for LTI and ZTI. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. Deploying a new domain controller as a replica in an existing domain as described in Deploy a New Domain Controller as a Replica in an Existing Domain. including logon processes. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps. and directory searches. authentication.

Click Add.com. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. click New Forest.367 Microsoft Deployment Toolkit 2010 Update 1 • • Deploying a new read-only domain controller (RODC) in an existing domain as described in Deploy an RODC in an Existing Domain. click Add. 7. You must include the extension of the domain—for example. In the New forest domain DNS name box. Description. deploy a domain controller that contains a new forest environment. type a name for the new domain —for example.com. type a password to use for safe mode recovery. 2.int. . You use this password to recover from a failed AD DS service.net. type the relevant information in the following boxes: • • Name. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain).com might have the NetBIOS name WOODGROVE. Use this option when deploying a new forest environment. and then click Configure ADDS. In the task sequence hierarchy. Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab. In the Recovery (safe mode) password box. Make note of this password in case AD DS must be recovered. Solution Accelerators microsoft. type a name for the NetBIOS.com or any other type of extension. 5. Configuring AD DS advanced properties for domain controllers as described in Configure AD DS Advanced Properties. ZTI in the task sequence hierarchy. For example.com/technet/SolutionAccelerators . click Roles. . and then click Configure ADDS. 4. This name is usually the domain name without . Type a description of the task—for example. the forest domain name woodgrove. . On the Properties tab. woodgrove. 6. 3. Type a name for the task. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. In the NetBIOS name box. In the Create box. Deploy a Domain Controller in a New Forest Using this option. To deploy a domain controller with a new forest 1. click MDT.

In the Existing domain DNS name box.mspx?mfr=true. In the Advanced Properties section. Type a name for the task.com/technet/SolutionAccelerators . The directory services database replicates this domain controller. 5. click MDT. click Roles. Use this option when deploying a new domain controller into an existing environment if replication will obtain the existing domain information from AD DS. click Add. complete the task configuration as described in Configure AD DS Advanced Properties. and Site_Name is the name of the domain). type a password to use for safe mode recovery. type the relevant information in the following boxes: • • Name. type the name of a domain controller the new server will replicate within the existing environment.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. 2. In the Recovery (safe mode) password box. Deploy a New Domain Controller as a Replica in an Existing Domain Using this option. Click Add. 7. In the Create box.microsoft. 8. 4. For more information about DCPROMO command-line options. type the name of an account that has permissions to add a domain controller to the existing network (typically. In the Account box. and then click Configure ADDS. Server_Name Site_Name (where Server_Name is the name of the server. In the Replication source domain controller box. and then click Set.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 368 8. On the Properties tab. 3. Type a description of the task—for example. and then click Configure ADDS. ZTI in the task sequence hierarchy. deploy an existing domain controller as a new domain controller by replicating it into an existing environment. Description. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. Solution Accelerators microsoft. a domain Administrator account). and then click OK. Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab. To deploy a domain controller as a new domain controller replica 1. In the task sequence hierarchy. type the FQDN of an existing domain controller. 6. click New domain controller replica. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. go to http://technet2.

Type a description of the task—for example. type a name for the child domain being created—for example. complete the task configuration as described in Configure AD DS Advanced Properties. In the Existing forest (parent) domain DNS name box. 7.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. click Add. type the NetBIOS name of an existing domain in the network. type the relevant information in the following boxes: • • Name: Type a name for the task. Description. In the task sequence hierarchy.com (where child is the name of the child domain). the domain woodgrove. 4. ZTI in the task sequence hierarchy. Make note of this password in case AD DS must be recovered. In the New domain tree (child) DNS name box.369 Microsoft Deployment Toolkit 2010 Update 1 This password is used to recover from a failed AD DS service. Solution Accelerators microsoft. In the Advanced Properties section. For more information about DCPROMO command-line options. go to http://technet2. 3. Click Add. 2. On the Properties tab. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. child. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. type the name of an existing domain in the network. usually the domain name without . click MDT.com or any other type of extension—for example. 9.com might have the NetBIOS name WOODGROVE. 5. 6.microsoft. In the Create box. click New domain in existing forest. and then click Configure ADDS. deploy a domain controller that contains a new tree into an existing forest environment. Deploy a New Domain Controller in a New Domain Tree in an Existing Forest Using this option. click Roles. To deploy a domain controller with a new domain tree in an existing forest 1. Use this option when deploying a child domain into an existing forest environment.mspx?mfr=true.woodgrove. In the NetBIOS name box.com/technet/SolutionAccelerators . Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab. and then click Configure ADDS. and then click OK.

microsoft. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. complete the task configuration as described in Configure AD DS Advanced Properties. deploy a domain controller that contains a new domain into an existing forest environment. and then click OK. click Roles. In the Advanced Properties section. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. In the task sequence hierarchy. Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 370 8. Use this option when deploying a new child domain into an existing forest environment. Click Add. click MDT. 3. To deploy a domain controller with a new domain in an existing forest 1.com/technet/SolutionAccelerators . ZTI in the task sequence hierarchy. Type a name for the task. 9. and then click Configure ADDS. click Add. Type a description of the task—for example. type the relevant information in the following boxes: • • Name. In the Create box. In the Account box. 11. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). In the Recovery (safe mode) password box. a domain Administrator account). click New domain in existing forest. type the name of an account with permissions to add a domain controller to the existing network (typically. type the name of the domain controller to which the new child domain will replicate. 2. 4. In the Replication source domain controller box. Description. go to http://technet2. and then click Configure ADDS. You use this password to recover from a failed AD DS service. Make note of this password in case AD DS must be recovered. For more information about DCPROMO command-line options.mspx?mfr=true. and then click Set. Solution Accelerators microsoft. 10.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. Deploy a New Domain Controller in a New Domain in an Existing Forest Using this option. type a password to use for safe mode recovery. On the Properties tab.

com might have the NetBIOS name WOODGROVE. 9. deploy a domain controller that contains a read-only replica of the existing domain into an existing forest environment. Solution Accelerators microsoft. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. a domain Administrator account). go to http://technet2. In the NetBIOS name box. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console.371 Microsoft Deployment Toolkit 2010 Update 1 5. In the Recovery (safe mode) password box. click Roles. 11. the domain woodgrove. type a name for the child domain being created—for example. To deploy an RODC in an existing domain 1. and then click OK. click Add. 7. type the name of an account with permissions to add a domain controller to the existing network (typically.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. You use this password to recover from a failed AD DS service.com (where child is the name of the child domain).mspx?mfr=true.com/technet/SolutionAccelerators . 6. and then click Configure ADDS. In the task sequence hierarchy. type the NetBIOS name of an existing domain in the network. child. Add a new task sequence step based on the Configure ADDS task sequence type for: • LTI on the Task Sequence tab. 2. In the Advanced Properties section. In the New domain (child) DNS name box. 10. usually the domain name without . Use this option to deploy a domain controller that contains an un-editable replica of a domain structure into an existing forest environment. Deploy an RODC in an Existing Domain Using this option. 8. type the name of the domain controller to which the new child domain will be replicated. complete the task configuration as described in Configure AD DS Advanced Properties. For more information about DCPROMO command-line options. In the Replication source domain controller box. and then click Set. In the Account box. type the name of an existing domain in the network. In the Existing forest (parent) domain DNS name box. type a password to use for safe mode recovery.microsoft.woodgrove. Make note of this password in case AD DS must be recovered.com or any other type of extension—for example.

5. microsoft. Click Add. go to http://technet2. In the Replication source domain controller box. complete the task configuration as described in Configure AD DS Advanced Properties. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. On the Properties tab. and then click task_sequence_step (where task_sequence_step is the Configure ADDS task sequence step).Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 372 ZTI in the task sequence hierarchy. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. click MDT. In the Advanced Properties section. In the Recovery (safe mode) password box. For more information about DCPROMO command-line options. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). • Configure AD DS Advanced Properties To configure AD DS advanced properties. type the name of an account with permissions to add a domain controller to the existing network (typically. and then click Configure ADDS. 9. and then click OK.mspx?mfr=true. Modify the Configure ADDS task sequence step you created for: • LTI on the Task Sequence tab.microsoft. In the Existing domain DNS name box. You use this password to recover from a failed AD DS service. type a password to use for safe mode recovery. ZTI in the task sequence hierarchy. In the Account box. perform the following steps: 1. click MDT. for example. Click Add. a domain Administrator account). click task_sequence_step (where task_sequence_step is the Configure ADDS task sequence step). In the Create box.com/technet/SolutionAccelerators • Solution Accelerators . 7. and then click Set. type the relevant information in the following boxes: • • Name. In the task sequence hierarchy. Type a name for the task. 3. 2. Make note of this password in case AD DS must be recovered. type the name of an existing DNS server. 8. Type a description of the task. 6. Description.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. type the name of the domain controller to be replicated within the existing environment. click New read-only domain controller (RODC) replica. 4. The directory services database replicates this domain controller.

Contains the fully qualified path on the target computer to the location for the NTDS database. • Functional levels section: • • Folders section: • • • Note If you configure values in the CustomSettings. The default name for a new forest or site is default_first_site. This is the default option and should be selected for new domains or forests and domains without a GC server. use the %DESTINATIONLOGICALDRIVE% task sequence variable instead of the %SYSTEMROOT% variable. Wait for critical replication only. In the Site name box. 4 = Windows Server 2008 R2) Domain Functional Level. click Advanced. 3 = Windows Server 2008. select the following options as required for your environment and AD DS scenario: Options section: • • Install DNS if not already present. the variables are evaluated while running Windows PE. Select this option to populate only the directory services database using replication. Functional Levels.ini file or the MDT DB. however.ini or the MDT DB. You can also configure this value using the SysVolPath property in the CustomSettings. Solution Accelerators microsoft. this value does not appear in the Site name box by default—you must type it. SYSVOL. 4. Make this domain controller a global catalog (GC) server.ini file or the MDT DB. Windows Server 2008 (2 = Windows Server 2003. For LTI deployments. Log Files. You can also configure this value using the LogPath property in the CustomSettings. The %SYSTEMROOT% variable for Windows PE typically is set to X:\WINDOWS. type the name of the site in which to install the domain controller. Contains the fully qualified path on the target computer to the location for the log files. 5. Forest Functional Level. Contains the fully qualified path on the target computer to the location for the Sysvol folder. Windows Server 2008 (2 = Windows Server 2003. The default value is %SYSTEMROOT%NTDS. and Folders sections. Select this option when creating a new forest or new domain. The default value is %SYSTEMROOT %SYSVOL. On the Properties tab. Windows Server 2003. 4 = Windows Server 2008 R2) Database. not the target operating system. Windows Server 2003.ini file or the MDT DB. The default value is %SYSTEMROOT %NTDS. 3 = Windows Server 2008. You can also configure this value using the DatabasePath property in the CustomSettings. In the AD DS Advanced Properties dialog box.com/technet/SolutionAccelerators .373 Microsoft Deployment Toolkit 2010 Update 1 3. so the %SYSTEMROOT% variable will return the SystemRoot folder for Windows PE. in the Options.

For more information about deploying an application in: • • LTI deployments. types. click OK to complete the configuration of the AD DS Advanced Properties dialog box. rather. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. For Windows Server 2003 target operating systems. and then click OK in the Task Name Properties dialog box to complete configuration of the task. ZTI deployments.com/technet/SolutionAccelerators . you can configure standard DNS primary. 2. “Configuring Software Distribution. it is a new installation of DNS zones of all types. Configure DNS Server Role Settings for LTI and ZTI Using this option.msi file resides): msiexec /i unc_path\suptools. add a new task sequence step based on the Run Command Line task sequence type to install the Windows Support Tools for Windows Server 2003. By assigning the DNS server role. Note The Windows Support Tools for Windows Server 2003 must be installed prior to running the Configure DNS task sequence type that you create later in this process. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps.msi /q addlocal=all Alternatively. Run the following command (where unc_path is the fully qualified UNC path to the folder in which the suptools. If you choose this option. 3. This is not a migration process from an existing DNS server. install the Windows Support Tools for Windows Server 2003 as an application. configure and deploy the DNS server role to a new computer or a DNS server operating on an existing computer. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. Add a new task sequence step based on the Configure DNS task sequence type for: Solution Accelerators microsoft.” in the Configuration Manager Documentation Library. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. updates. and stub zones as well as AD DS-integrated primary and stub zones. and multiple zones—all in an automated process. see the section.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 374 Then. There is also an option to manage aging. restart the target computer after installing the Windows Support Tools for Windows Server 2003. included with System Center Configuration Manager. To configure and deploy the DNS server role 1. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. secondary. see Create a New Application in Deployment Workbench.

in Name checking. In the task sequence hierarchy. woodgrove.com). On the Properties tab of the Configure DNS step. in Server Options. 5. In the Change Zone Type dialog box. type a name for the zone (for example. type description (where description is the description of the task and its role in the task sequence). Close the Deployment Workbench. Select the Scavenge stale resource records check box to enable this feature. select the appropriate server options to enable. in Dynamic updates. and then click OK. 16. select one of the following zone types: • • Primary zone Secondary zone • Stub zone 10.375 Microsoft Deployment Toolkit 2010 Update 1 • • LTI on the Task Sequence tab. 4. Click Add. Configure DHCP Server Role Task Sequence Step Settings for LTI and ZTI Using this option. and then click OK. configure and deploy the DHCP server role using MDT 2010. In the Server Properties dialog box. In the DNS Zone Properties dialog box. On the Properties tab. click the yellow Add button. 17. and then click Configure DNS. select one of the following: • None • Nonsecure and Secure 12. click Change. Solution Accelerators microsoft. select the Store the zone in Active Directory check box if DNS will be installed on a domain controller. 15. In the Server Properties dialog box. click Roles. In the Zones section. 9. in DNS zone name. in Name. type name (where name is the name by which the task is identified in the task sequence). click MDT. 8.com/technet/SolutionAccelerators . In Type. click OK. and then click OK. You can configure all the standard options that make up scopes similar to using the standard DHCP console in Windows Server 2008 and Windows Server 2003. ZTI in the task sequence hierarchy. In the Change Zone Type dialog box. 14. click Add. 6. select the appropriate name-checking options to enforce. 11. and then click Configure DNS. 7. click Server Properties. In Description. 13. In the task_sequence Properties dialog box (where task_sequence is the name of the task sequence being edited). In the DNS Zone Properties dialog box.

ZTI in the task sequence hierarchy. On the Properties tab. type the relevant information in the following boxes: • • Name. The name by which the task will be identified in the task sequence list. Note For Windows Server 2003 target operating systems. click Add. 2. if you run the Configure DHCP Server task sequence step in the same task sequence as the Configure DNS task sequence step. ensure that the Configure DHCP Server task sequence step precedes the task sequence step to install the Windows Support Tools for Windows Server 2003. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. scope names). To configure and deploy the DHCP server role 1.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 376 To implement the DHCP server role. In the task sequence hierarchy. and then click Configure DHCP. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. Configuring the DHCP scopes for the DHCP server role as described in Configure DHCP Scopes for the DHCP Server Role. Configure the Configure DHCP Server task sequence step settings by: • • • Configuring the deployment of the DHCP server role as described in Configure Deployment of the DHCP Server Role. 3. click MDT. see Configure DNS Server Role Settings for LTI and ZTI. A description of the task (for example. microsoft. Configuring the DHCP server options for the DHCP server role as described in Configure the DHCP Server Options for the DHCP Server Role. configure the Authorize DHCP task sequence in conjunction with the Configure DHCP Server task sequence. Configure Deployment of the DHCP Server Role Install and configure the DHCP Server role on the target computer by modifying the Configure DHCP Server task sequence step type. click Roles. The Configure DNS task sequence step requires that the support tools be installed. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps. and then click Configure DHCP. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab.com/technet/SolutionAccelerators Solution Accelerators . click Add. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. DHCP scope information. Description. For more information. Add a new task sequence step based on the Configure DHCP Server task sequence type for: • • LTI on the Task Sequence tab.

Details about the IP address the DHCP scopes configured.255.150). click task_sequence_step (where task_sequence_step is the name of the task sequence step). Configure DHCP Scopes for the DHCP Server Role Using this option. Start IP address. Subnet mask. 192. For more information about DHCP scope configuration options and for guidance on using each configuration option.0). The options passed to DHCP clients (for example. ZTI in the task sequence hierarchy. Server options.com/en-us/library/bb727003. and WINS server addresses). see “Chapter 6 – Dynamic Host Configuration Protocol” of TCP/IP Fundamentals for Microsoft Windows at http://technet.0. In the Scope Properties dialog box. 3. 2.168. The ending address of the scope (for example.377 Microsoft Deployment Toolkit 2010 Update 1 • • Scope details. microsoft. 192. Lease duration for DHCP clients.1). The beginning address of the scope (for example. The address of the scope itself (for example. The maximum time a client can keep the IP address that the DHCP server assigns.0. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console.168. On the Properties tab.255.250). The name used to refer to the scope. The mask used for the IP address scope (for example. 4. Scope IP address. default gateway. To configure and deploy DHCP scopes 1. Click OK. In the task sequence hierarchy. Modify the task sequence step you created based on the Configure DHCP task sequence type for: • LTI on the Task Sequence tab. 4. DNS server. End IP address. configure the following options as required for the environment: • • • • • • Scope name. 192. Click task_sequence_step (where task_sequence_step is the name of the task sequence step). configure the DHCP scopes that contain the rules and active scopes used on the DHCP server. 255. click the yellow Add scope button.aspx.0.com/technet/SolutionAccelerators • Solution Accelerators .168. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab.microsoft.

The beginning address for exclusion from a scope (for example. The default gateway given to DHCP clients. in the Exclude IP Address Range section. 046 WINS/NBT Node Type. type the following information to exclude addresses for the scope created on the General tab: • • Start IP address. End IP address.0. woodgove. ZTI in the task sequence hierarchy. configure the following options for the scope created on the General tab: • • • • • 003 Router. in the Server Options section. Solution Accelerators microsoft. The ending address for exclusion from a scope (for example. Click task_sequence_step (where task_sequence_step is the name of the task sequence step). 5. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • • LTI as described in Configure the Task Sequence Properties Task Sequence Tab.2). The WINS node type.168. 044 WINS/NBNS Servers. 006 DNS Servers. On the Properties tab. On the Options tab. 192.168.251). Modify the task sequence step you created based on the Configure DHCP task sequence type for: • LTI on the Task Sequence tab. The DNS domain name given to clients (for example. click task_sequence_step (where task_sequence_step is the name of the task sequence step). Click OK. The DNS server address given to DHCP clients. click Configure. A description of the scope (for administrative reference). including router or default gateway designation.com/technet/SolutionAccelerators • .255). 015 DNS Domain Name.168. The address used for PXE client Bootstrap code. 192. To configure and deploy DHCP server options 1.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 378 • Description. configure the DHCP server options given to DHCP clients. The WINS server IP address (for example. and then configure the following options as required for your environment.com). DNS server IP information. 192. On the Advanced tab. 7. 2. 3.0. 6. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. In the task sequence hierarchy. and WINS server information.0. Configure the DHCP Server Options for the DHCP Server Role Using this option. • 060 PXE Client.

or 47. in the String Value box. Click an IP address.com/technet/SolutionAccelerators . Click 046 WINS/NBT Node Type. Click 003 Router. type the IP address and resolve the name. and then click Remove to remove the highlighted IP address. 6. 7. Click Add to type an IP address. type the PXE client string (typically. For more information about how to determine the correct option for the environment. 9. in the String Value box.com/windowsserver/en/library/e71fac630521-4217-899f-79802bfdb7481033. Click Add to type an IP address. Click an IP address. and then click Remove to remove the highlighted IP address. PXEClient). Note The ZTI task sequence templates that are provided with MDT 2010 do not include an Authorize DHCP task sequence step type. Click 044 WINS/NBNS Servers. Solution Accelerators microsoft. Click Add to type an IP address. and then click Remove to remove the highlighted IP address.com). 8.microsoft. type the IP address and resolve the name. Edit task_sequence_name (where task_sequence_name is the name of the task sequence to which you want to add the task sequence step) for: • LTI as described in Configure the Task Sequence Properties Task Sequence Tab. and then perform the following tasks: • • • In the Server Name box. see the section. Click an IP address.mspx?mfr=true. Click 060 PXE Client. Click 006 DNS Servers. 5. 46. type the IP address and resolve the name. and then.” in WINS Tools and Settings at http://technet2. To authorize the DHCP server role in AD DS 1. type the domain name (for example.379 Microsoft Deployment Toolkit 2010 Update 1 4. and then. woodgrove. Configure Authorize DHCP Task Sequence Step Settings for LTI and ZTI Authorizing the DHCP service within AD DS is imperative to successfully deploying and using DHCP services within a Windows-based network. and then type one of the following codes: 44. “DHCP Options for WINS. and then perform the following steps: • • • In the Server Name box. You must manually add this step type if you want to automatically authorize the DHCP server as a part of the ZTI deployment. and then perform the following tasks: • • • In the Server Name box. Click 015 DNS Domain Name.

Add a new task sequence step based on the Authorize DHCP task sequence type for: • • LTI on the Task Sequence tab. Click Add. Ensure that the Run Command Line task sequence step type occurs prior to any task sequence steps or scripts that depend on the files being copied to the target computers. However. and then click Authorize DHCP. For more information about modifying task sequence steps. perform any combination of the following steps: • • Copy content to the target computer using a task sequence step as described in Copy Content to Target Computers Using Task Sequence Steps. Copy content to the target computer using $OEM$ folders as described Copy Content to Target Computers Using $OEM$ Folders. when deploying Windows Solution Accelerators microsoft. 2. In the Account box.exe command or a similar command to copy the content to the target computer. see Configure the Task Sequence Steps and Step Sequence.com/technet/SolutionAccelerators . type the name of an account with permissions to authorize the DHCP service in AD DS. Retype the password 5. The account that can authorize DHCP. click Roles. Copy Content to Target Computers Using Task Sequence Steps Create a task sequence based on the Run Command Line task sequence step type that runs the xcopy. 4. Copy Content to Target Computers Using $OEM$ Folders MDT 2010 supports using legacy $OEM$ folders to organize and copy supplemental files to the target computers. then click OK again. click MDT. Click Set. type the relevant information in the following boxes: • Name. A description of the task. The name by which the task appears in the task sequence list.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 380 ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. and then click Authorize DHCP. Copying Content to the Target Computer To copy content to target computers. and then type the following information in the relevant boxes: • • Username. in the format domain\user Password. On the Properties tab. • ZTI in the task sequence hierarchy. In the task sequence hierarchy. • Description. click Add. 3. Click OK. The password for the account • Confirm Password.

D. $1. Windows Setup copies the contents of this folder to %SystemRoot% on each destination computer. Create $OEM$ folders in this location to create a custom folder for each platform. E. An $OEM$ folder with Windows XP or Windows Server 2003. microsoft.cab file in the Support\Tools folder on the Windows installation media. both of which are in the Deploy. subfolders. Create $OEM$ folders in this location to create a custom folder for each build. For example. For more information about using: • Data WIM files or $OEM$ folders with Windows Vista or Windows Server 2008. to find an $OEM$ folder: • Control\task_sequence (where task_sequence is the name or ID of the task sequence that MDT 2010 is installing). Drive. Windows Setup copies the contents of this folder to the root of the corresponding drive on each destination computer. the first driver that LTIApply. Windows Setup copies the contents of this folder to %SystemDrive% on each destination computer. and files that this folder contains in the corresponding drive during the setup process. which is at the root of the deployment share and is the default $OEM$ folder if a folder is not found in the previous locations. It replicates all the folders. Create $OEM$ folders in this location to create a custom folder for each operating system. For Windows Setup to copy a file to %SystemRoot%\System32 on each destination computer. Note In an instance where multiple $OEM$ folders have been defined.wsf finds is deployed to the target computer. and so on). It replicates all the folders. subfolders. Windows Setup copies any files put in $OEM$\D to the root of drive D on each destination computer. for example. Operating Systems\Name (where Name is the name of the operating system MDT 2010 is installing). • • • An $OEM$ folder contains supplemental files. $OEM$. Drive is a drive letter (C.chm) and the Microsoft Windows Preinstallation Reference (Ref. The following list describes each folder that you can create within an $OEM$ folder to organize these files: • $$. It replicates all the folders. and files that this folder contains in the %SystemDrive% folder on each destination computer. put the file in $OEM$\$$\System32. see the Windows Automated Installation Kit User’s Guide in the Windows AIK. Platform (where Platform is either x86 or x64). see the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy. in the order specified. This is typically drive C on most computers. and files that this folder contains in the %SystemRoot% folder of each destination computer. data WIM files are preferred over $OEM$ folders. • MDT 2010 looks in the following locations within the deployment share. subfolders.com/technet/SolutionAccelerators • • Solution Accelerators .381 Microsoft Deployment Toolkit 2010 Update 1 Vista or later operating systems.chm).

Use $1 to represent %SystemDrive%. Create new scripts for use in LTI and ZTI deployments from a template as described in Create New Scripts from a Template.wsf files. query the configuration database. this folder contains hardware-specific files that Windows Setup and text-mode setup install on the destination computer during the text-mode phase of the installation process. MDT 2010 scripts leverage this functionality by referencing the ZTIUtility. evaluate environment variables to determine the rules to be used when deploying the images to the target computers. Develop Custom Scripts You can develop new scripts for use in LTI and ZTI deployments. List these files in the [OemBootFiles] section of the answer file.oem file. and then open the Scripts folder. open the installation path of the deployment share. In most installations. The ZTIUtility. The ZTIDataAccess. Before describing how to create a script.wsf file. copy the script to a new file.vbs script. it is best to review how the scripts included with MDT 2010 are constructed. The folders rely on a very specific disk configuration on the destination computer.oem file describes how to load and install these files. For Windows XP and Windows Server 2003. $OEM$\$1 and $OEM$\C write to the same location: the root of drive C. there is no need to modify one of the delivered scripts.vbs]) and Windows Script file (. • TEXTMODE. The standard MDT 2010 script is a . These files may include OEM HALs. Typically. Solution Accelerators microsoft. instead.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 382 Microsoft recommends that these folders not be used.vbs script includes the common routines for database access.wsf) scripts.vbs or . They scan the configuration files. and the Txtsetup. Note Microsoft does not support customized and custom scripts. update it. Creating Custom Scripts for MDT 2010 Scripts provide automation of the image-build and overall deployment process. The log files record the status of the deployment process and can be used to assist in troubleshooting this process: • • Develop new scripts for use in LTI and ZTI deployments as described in Develop Custom Scripts. MDT 2010 uses both Microsoft Visual Basic® Scripting Edition (VBScript [. For examples of scripts that the Deployment Workbench uses. These scripts should be in the form of . which allows references to be made to functions that are contained in other scripts.vbs script and the ZTIDataAccess. and perform many other intricate deployment tasks. If a modification is necessary. The Txtsetup. instead of modifying one of the delivered scripts.com/technet/SolutionAccelerators . The scripts create log files as the scripts automate the deployment process. mass-storage device drivers.vbs script is used to initialize the MDT 2010 environment and setup classes. and thoroughly test the effect of any change.

vbs as described in Environment Class. and provides a web service interface.ini files. creating a single log file for each script and a consolidated log file of all scripts and is defined in ZTIUtility. Process Environment object oNetwork. and is defined in ZTIUtility. Can be used to access web services in scripts instead of configuring the CustomSettings.Item("ComputerName") = "Example" Or. allowing for direct reference from the script. WScript Shell object oEnv.vbs as described in Database Class.ini files.ini or BootStrap.vbs as described in WebService Class. You can specify the parameters for accessing the database in the scripts. to determine whether this is a 32-bit or 64-bit architecture. Provides access to web services and is defined in ZTIDataAccess.vbs as described in Logging Class.vbs as described in Utility Class.ini or BootStrap. The WebService class: • • Is used by ZTIGather. Provides general utility functionality and is defined in ZTIUtility. WScript Network object Environment. For example. Database. Utility. change the computer name to Example using the command: oEnvironment. The scripts define several standard objects that need not be declared in the script: • • • • • oFSO.wsf when processing database rules from the CustomSettings.ini or BootStrap. The Database class: • • Is used by ZTIGather. Provide access to databases and is defined in ZTIDataAccess.383 Microsoft Deployment Toolkit 2010 Update 1 including connecting to and querying databases. Environment Class Reference this class in scripts through the oEnvironment object. You can specify the parameters for accessing the web services in the scripts. File System Object oShell.com/technet/SolutionAccelerators . Provides the logging functionality that all MDT 2010 scripts use.ini or BootStrap.ini files. Configures environment variables gathered through WMI and MDT 2010 rule processing. Can be used to access databases in scripts instead of configuring the CustomSettings.wsf when processing web service rules from the CustomSettings. query the architecture using the command: Solution Accelerators microsoft. Logging.ini files. The following classes are defined that perform several standard tasks: • • • • WebService.

use the command: iRetVal = oUtility.Database = "MDTDB" oDatabase. When creating an informational log entry.Netlib = "DBNMPNTW" oDatabase.Instance = "SQLExpress" oDatabase.com/technet/SolutionAccelerators .Port = "" oDatabase.ScriptName To find the location of a file.Item("Architecture") Logging Class Reference this class in scripts through the oLogging object.Table = "ComputerSettings" oDatabase.SQLServer = "NYC-MDT-01" oDatabase.ini".vbs"/> <script language="VBScript"> Dim oDatabase Dim oRecordset Set oDatabase = new Database oDatabase.CreateEntry "An error occurred". use the command: oUtility.LogTypeError Utility Class Reference this class in scripts through the oUtility object. AssetTag.Parameters = "UUID. use the command: oLogging. SerialNumber. sIniFile) Database Class Reference this class in scripts through the Database class.CreateEntry "Informational message".SQLShare = "DeploymentShare$" Solution Accelerators microsoft.FindFile("CustomSettings.vbs"/> <script language="VBScript" src="ZTIDataAccess. use the command: oLogging.ParameterCondition = "OR" oDatabase. You can create an instance of the object class and connect to a database using following script excerpt: <script language="VBScript" src="ZTIUtility. LogTypeInfo When creating an error log entry.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 384 oEnvironment. MacAddress" oDatabase. To determine the name of the current script.

xml file.net/uszip.vbs"/> <script language="VBScript"> ' //********************************************************* ****************** ' // ***** Script Header ***** Solution Accelerators microsoft.Query WScript. Listing 10 shows a template for creating custom scripts.Echo "Records retrieved: " & oRecordset.Item("USZip") = "98029" oEnvironment.asmx/GetInfoByZIP" oWebService.Parameters = "USZip" Set oXML = oWebService.Echo oXML. You call these scripts by adding them to the Task Sequence Editor and ultimately by adding them to the TS.vbs"/> <script language="VBScript" src="ZTIDataAccess.com/technet/SolutionAccelerators .vbs"/> <script language="VBScript"> Dim oWebService Dim oXML oEnvironment.WebService = "http://www.Item("USZip") = "98029" Set oWebService = new WebService oWebService.webservicex.Query WScript. Custom Script Template <job id="Z-Sample"> <script language="VBScript" src="ZTIUtility.385 Microsoft Deployment Toolkit 2010 Update 1 oDatabase.Echo "Web service response:" WScript. You can create an instance of the object class and connect to a database using following script excerpt: <script language="VBScript" src="ZTIUtility.RecordCount WebService Class Reference this class in scripts through the WebService class.XML Create New Scripts from a Template You can also create scripts for use in the imaging process.Connect Set oRecordset = oDatabase. Listing 10.

Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 386 ' // ' // Solution: Solution Accelerator for Microsoft Deployment ' // File: Z-Sample.com/technet/SolutionAccelerators .wsf [/debug:true] ' // ' // Customer Build Version: 1.0.0 ' // Customer Script Version: 1.0.0 ' // Customer History: ' // ' // ***** End Header ***** ' //********************************************************* ****************** '//--------------------------------------------------------------------------'// '// Global constant and variable declarations '// '//--------------------------------------------------------------------------Option Explicit Dim iRetVal '//--------------------------------------------------------------------------'// End declarations '//--------------------------------------------------------------------------'//--------------------------------------------------------------------------'// Main routine '//--------------------------------------------------------------------------On Error Resume Next Solution Accelerators microsoft.wsf ' // ' // Purpose: Template ' // ' // Usage: cscript Z-Sample.

non-zero '// '// Purpose: Perform main ZTI processing '// '//-------------------------------------------------------------------------Function ZTIProcess() iRetVal = Success ZTIProcess = iRetval '!!!!!!!!!!! End Function </script> </job> At a high level. Create a task sequence step based on the Run Command Line task sequence step type in your task sequence. 2. 4. Follow these guidelines when creating a script: Solution Accelerators microsoft.com/technet/SolutionAccelerators INSERT YOUR CODE HERE !!!!!!!!!!!! . Configure the task sequence step created in the previous step to run your script.387 Microsoft Deployment Toolkit 2010 Update 1 iRetVal = ZTIProcess ProcessResults iRetVal On Error Goto 0 '//-------------------------------------------------------------------------'// '// Function: ZTIProcess() '// '// Input: None '// '// Return: Success .0 '// Failure . Create the script based on the template. complete the following steps to add a custom script: 1. • Package source for the Microsoft Deployment Toolkit Files package. Place the script in the Scripts folder of the: • Deployment share for LTI deployments. 3.

.vbs do not already provide the functionality required before writing a function.. or a beta version of Office 2007 ' // ' //********************************************************* ****************** Option Explicit '//--------------------------------------------------------------------------'// Main routine '//--------------------------------------------------------------------------Dim iRetVal On Error Resume Next Solution Accelerators microsoft.. Only create objects where required.vbs and ZTIDataAccess. Listing 11 shows an example of a script that checks for an Encrypting File System (EFS) key and beta 2007 Office system code on the target computer. Script to Check for EFS Keys or Beta Versions of the 2007 Office System <job id="LTIGetFolder"> <script language="VBScript" src="ZTIUtility.vbs"/> <script language="VBScript"> ' //********************************************************* ****************** ' // ' // Microsoft IT Verify ' // ' // Verify that the local machine is ready for installation.vbs"/> <script language="VBScript" src="WizUtility.com/technet/SolutionAccelerators . Verify that ZTIUtility. because MDT 2010 includes most objects that are needed. ' // ' // Checks to see if you have any EFS Keys.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 388 • • • Always declare variables. Listing 11.

sError ZTIProcess = Success If oEnvironment.389 Microsoft Deployment Toolkit 2010 Update 1 iRetVal = ZTIProcess ProcessResults iRetVal On Error Goto 0 '//-------------------------------------------------------------------------'// '// Function: ZTIProcess() '// '// Input: None '// '// Return: Success ." & vbNewLine & "More info: http://go.com/technet/SolutionAccelerators .RegRead("HKCU\Software\Microsoft\Windows NT\CurrentVersion\EFS\CurrentKeys\CertificateHash") On Error goto 0 if not isempty(CheckForEFS) then sError = "Warning: Please backup your EFS certificate. On Error Resume Next CheckForEFS = empty CheckForEFS = oShell.0 '// Failure .Item("DeploymentType") = "UPGRADE" then ' -------------------------------------------------------' Check for EFS keys in the registry.com/fwlink/?LinkId=79038" Solution Accelerators microsoft.microsoft.non-zero '// '// Purpose: Perform main ZTI processing '// '//-------------------------------------------------------------------------Function ZTIProcess() dim CheckForEFS.

oApplication DIM sQuery Solution Accelerators microsoft.CreateEntry sError.CreateEntry sError.com/technet/SolutionAccelerators . if HasOldOffice then sError = "Warning: Please Manually remove all Beta Office 2007 Components.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 390 oLogging. LogTypeWarning if MsgBox(sError & vbNewLine & "Press OK to continue". vbOKCancel) = vbCancel then ZTIProcess = Failure exit function end if end if end if ZTIProcess = Success End Function Function HasOldOffice DIM oApplications. LogTypeWarning if MsgBox(sError & vbNewLine & "Press OK to continue". vbOKCancel) = vbCancel then ZTIProcess = Failure exit function end if end if ' -------------------------------------------------------' Ensure there are no old versions of Microsoft Office 2007 on the local machine." oLogging.

Solution Accelerators microsoft. sQuery = "(Name LIKE 'Microsoft Office%2007' or Name LIKE 'Microsoft Expression Web') and Version <> '12. The preflight checks are run on the Preflight Checks page in the Operating System Deployment (OSD) Setup Wizard.0.ExecQuery("SELECT * FROM Win32_Product WHERE " & sQuery) HasOldOffice = oApplications.CreateEntry "Old version of: '" & oApplication. "MUI".Name & "' = " & oApplication. MDT 2010 includes some preflight checks for deploying the Windows 7 operating system using UDI. depending on the configuration and system resources of the target computers. However.391 Microsoft Deployment Toolkit 2010 Update 1 ' Enumerate through all applications installed on the local machine.1014'" set oApplications = objWMI. oApplication. "Proof".Count > 0 for each oApplication in oApplications ' Filter out MUI and Proof Packages if instr(1.Name.com/technet/SolutionAccelerators . vbTextCompare ) = 0 then oLogging.Name.4518. vbTextCompare ) = 0 and instr(1. oApplication. you may need to create custom preflight checks. Looking for pre-RTM Office versions.Version . LogTypeWarning end if next end function </script> </job> Create Custom Preflight Checks for UDI The Operating System Deployment (OSD) Setup Wizard runs software known as preflight checks on the target computer to determine whether the computer is properly configured and has the appropriate system resources for the target operating system.

Allow for parameters to be passed to the program. For example.wsf displays all preflight check programs. The wizard starts the preflight check program using a command-line interface. For each exit code. In some instances the preflight check might be applicable to specific target computers. Include detection for the appropriate target operating system architecture. Allow for silent program operation. You specify the command line in the Preflight Check Filename text box in the Preflight Checks dialog box as described in Configure the Preflight Page Behavior Using the UDI Wizard Designer. • • • The exit code information is specified in the Preflight Exit Code Configuration list box in the Preflight Checks dialog box as described in Configure the Preflight Page Behavior Using the UDI Wizard Designer. Return a unique exit code for each condition that can occur within the program. UDIWizard. For each condition that can occur.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 392 Create custom preflight checks for the Operating System Deployment (OSD) Setup Wizard in UDI by following these guidelines: • Start from a Command Prompt window. Any required parameters for the preflight check program must be passed on the command line. Use one of the following methods to ensure that only applicable preflight checks are run on target computers: • The preflight check program would always run but return exit codes that indicate whether the target computer was applicable. • Include detection for the appropriate target operating system. Exit code display message.com/technet/SolutionAccelerators Solution Accelerators . You specify the parameters in the Preflight Check Parameters text box in the Preflight Checks dialog box as described in Configure the Preflight Page Behavior Using the UDI Wizard Designer. you can specify: • • • Exit code state. For example. the preflight check program could return the following exit codes as a subset of other exit codes: microsoft. Exit code value. a preflight check program may be appropriate for Windows 7 RTM but may not be appropriate for Windows 7 with a service pack. The preflight check program should not open any dialog boxes or other windows during normal operation. • By default. The preflight check program should detect the architecture (32 bit or 64 bit) of the target operating system and run only if the target operating system architecture is appropriate. For example. a preflight check program may be appropriate for a 32-bit version of Windows 7 but not for 64bit versions of Windows 7. ensure that the program returns a unique error code. so your program needs to support being started in this way. The preflight check program should detect the target operating system and run only if the target operating system is appropriate.

For example. Or. 1. In this method. The preflight check program encountered an error while running. The preflight check program ran with a warning status. the UDIWizard. The preflight check program ran with a success status but is not applicable for the target computer. or portable computer.wsf script is modified to display preflight check programs that are applicable for the target computer and target operating system.Item("OSCurrentVersion"). The following excerpt from a modified UDIWizard. The preflight check program finished with a success status. the preflight check program may be appropriate only for portable computers. "CustomPreflight1") > 0 then bRemove = true End if End if The following excerpt from a modified UDIWizard.wsf script runs the custom preflight check program named CustomPreflight1 if the operating system is any operating system except Windows XP: If Left(oEnvironment.393 Microsoft Deployment Toolkit 2010 Update 1 • • 0. the UDIWizard. see Creating Custom Scripts for MDT 2010. "CustomPreflight2") > 0 then bRemove = true End if End if For more information about modifying MDT 2010 scripts.Item("Architecture")) = "X86" then If Instr(sFilename. such as desktop. because the program works for the target computer but is not applicable for the target computer.1) = "5" then If Instr(sFilename. 3. the UDIWizard. server.com/technet/SolutionAccelerators . For example.wsf script is modified to filter preflight checks based on the make or model of the target computer or the type of target computer.wsf script runs the custom preflight check program named CustomPreflight2 if the target computer is 64 bit: If UCase(oEnvironment.wsf should only display preflight check programs applicable to 64-bit operating systems when the target operating system is a 64-bit operating system. Solution Accelerators microsoft. the preflight check program may be appropriate for only 64-bit operating systems. 2.wsf script to filter preflight check programs. For example. • • • Modify the UDIWizard.

Configuring the MDT 2010 deployment process to retrieve configuration settings from the MDT DB by changing CustomSettings. or on any other SQL Server computer in your organization. create a new MDT DB or connect to an existing MDT DB in the Deployment Workbench. and stored procedures. on a SQL Server computer on which MDT 2010 is installed. Configure the MDT DB through the Deployment Workbench in MDT 2010 or any other data-management tool that you can use to modify information stored in SQL Server databases. . You create a new MDT DB or connect to an existing the MDT DB database objects using the Advanced Configuration/Database node in the Deployment Workbench. Perform deployments using the MDT DB by: • • • • Creating a new MDT DB or connecting to an existing MDT DB as described in Creating a New MDT DB or Connecting to an Existing MDT DB. you do not need to add any content to the deployment share. you have a centralized repository for managing deployment configuration settings. You can store the MDT DB on the same SQL Server computer that is used for System Center Configuration Manager. The MDT DB contains the database objects that the MDT 2010 deployment process uses.ini as described in Managing Configuration Settings Stored in the MDT DB. Conceptually. the MDT DB is a centralized version of the CustomSettings. The advantage to using the MDT DB is that for larger deployments.394 Microsoft Deployment Toolkit 2010 Update 1 Performing Deployments Using the MDT DB MDT 2010 includes a database—the MDT DB—that you can use to provide configuration settings for LTI or ZTI deployments. create a deployment share in the Deployment Workbench.ini file. Configuring MDT 2010 to access the MDT DB as described in Configuring the MDT 2010 Deployment Process to Access the MDT DB. Note To create and manage the MDT DB for LTI or ZTI deployments. However. Assigning appropriate permissions to the MDT DB as described in Assigning the Appropriate Permissions to the MDT DB. Upgrading the MDT DB from a previous version of BDD or MDT as described in Upgrading an Existing MDT DB. tables. • • Creating a New MDT DB or Connecting to an Existing MDT DB Before you can manage configuration settings in the MDT DB. as ZTI deployments do not require it. such as views. Extending the schema of the MDT DB as described in Extending the Schema of the MDT DB. for ZTI deployments.

and then create the MDT DB database objects in the database. create the MDT DB in the new database using the Deployment Workbench. In SQL Server name. 2. Create the MDT DB in an Existing Database If you want to store the MDT DB in a SQL Server database that database administrator (DBA) manages. Complete the New DB Wizard using the information in Table 187. Click Start. 3. To create the MDT DB in an existing database 1. Point to Microsoft Deployment Toolkit. A new database as described in Create the MDT DB in a New Database. The DBA creates the database and grants you DBA permission on the it. type instance_name (where microsoft. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database (where deployment_share is the name of the deployment share in which you will add the application). In the Deployment Workbench console tree. Note To create the MDT DB. 2. 4. and then grant you the appropriate permissions to create the MDT DB objects in the new database. You can create the MDT DB in: • • An existing database as described in Create the MDT DB in an Existing Database. Connect to an existing MDT DB as described in Connect to an Existing MDT DB.com/technet/SolutionAccelerators Solution Accelerators . When the database has been created. Create a New MDT DB Create a new MDT DB. the db_owner database role must exist in the database that the DBA created. the DBA must create the MDT DB. click New Database. In Instance. Information for Completing the New DB Wizard On this wizard page SQL Server Details Do this 1. type computer_name (where computer_name is the name of the computer running SQL Server). and then point to All Programs. and then click Deployment Workbench. In the Actions pane. 5. Table 187.395 Microsoft Deployment Toolkit 2010 Update 1 Create a new MDT DB or connect to an existing MDT DB by performing one of the following tasks: • • Create a new MDT DB as described in Create a New MDT DB. The New DB Wizard starts.

5. and microsoft. If Windows PE is not connecting to the database using this protocol. Click Next. Click Next. select network_library (where network_library is the network library used to communicate with SQL Server and can be either Named Pipes or TCP/IP Sockets). you can leave Instance blank. In Port. If you are using the default value. This text box is required for Window PE to connect to the database using the Windows Integrated Security with Named Pipes protocol. Click Next. establishing a network connection to the server so that Windows Integrated Security in SQL Server authenticates correctly. type SQLExpress for the instance name. In Network Library. In Database. select database_name (where database_name is the name of the database in which you want to store the MDT DB). If you are using Microsoft SQL Server Express. 3. type port_number (where port_number is the TCP port number for the SQL Server instances if different than the default value). 4. If you are using SQL Server installed as the default instance.com/technet/SolutionAccelerators Summary Solution Accelerators . you can leave SQL Share blank. SQL Share 1. you can leave Port blank. type share_name (where share_name is the name of a network shared folder on the computer specified on the SQL Server Details wizard page). 2. 2. 3. In SQL Share. Select Create (or recreate) the tables and views in an existing database.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 396 On this wizard page Do this instance_name is the name of SQL Server instance on the computer running SQL Server). Review the information in the Details box. the information in the existing MDT DB tables and views will be lost. Windows PE connects to the network shared folder. Note If you select a database that has an existing MDT DB. Database 1.

and then click Deployment Workbench. you can create the new MDT DB. Create the MDT DB in a New Database In instances where you are the SQL Server DBA or have the necessary permissions. The New DB Wizard finishes. you need the sysadmin or dbcreator server roles. In the Deployment Workbench console tree. click New Database. 2. Point to Microsoft Deployment Toolkit. In SQL Server name. 3. type computer_name (where computer_name is the name of the computer running SQL Server). 3. In the Actions pane.397 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Confirmation Do this then click Next. you can leave Instance blank. The database configuration information is listed in the details pane of the Deployment Workbench. Click Finish. Complete the New DB Wizard using the information in Table 188. type SQLExpress for the instance name. and then point to All Programs. Table 188. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database (where deployment_share is the name of the deployment share in which you will add the application). If you are using SQL Server Express. 4. Note To create the MDT DB. Information for Completing the New DB Wizard On this wizard page SQL Server Details Do this 1. To create the MDT DB in a new database 1. Click Start.com/technet/SolutionAccelerators Solution Accelerators . 2. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. type instance_name (where instance_name is the name of the SQL Server instance on the computer running SQL Server). In Port. and then create the MDT DB database objects in the new database using the Deployment Workbench. If you are using SQL Server installed as the default instance. The New DB Wizard starts. type port_number (where microsoft. Tip You can click Save Output to save the output of the wizard to a file. In Instance.

2. 4. Solution Accelerators microsoft. 3. type share_name (where share_name is the name of a network shared folder on the computer specified on the SQL Server Details wizard page).Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 398 On this wizard page Do this port_number is the TCP port number for the SQL Server instance if different than the default value). Click Next. In SQL Share. Windows PE connects to the network shared folder. In Network Library. 5. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. This text box is required for Window PE to connect to the database using the Windows Integrated Security with Named Pipes protocol. If Windows PE is not connecting to the database using this protocol.com/technet/SolutionAccelerators . 2. establishing a network connection to the server so that Windows Integrated Security in SQL Server authenticates correctly. type database_name (where database_name is the name of the database in which you want to store the MDT DB). select network_library (where network_library is the network library used to communicate with SQL Server and can be either Named Pipes or TCP/IP Sockets). Click Next. Review the information in the Details box. The database configuration information is shown in the details pane of the Deployment Workbench. The New DB Wizard finishes. Click Next. Database 1. 1. Select Create a new database. Tip You can click Save Output to save the output of the wizard to a file. and then click Next. SQL Share Summary Confirmation Click Finish. you can leave SQL Share blank. In Database.

3. and then configure CustomSettings. If you are using SQL Server installed as the default instance. Click Start. 5. 3. and then click Deployment Workbench. 2. you must be a user in the MDT DB and be granted the db_datareader database role. select network_library (where network_library is the network library used to communicate with SQL Server and can be either Named Pipes or TCP/IP Sockets). In Port. If you are using SQL Server Express. Information for Completing the New DB Wizard On this wizard page SQL Server Details Do this 1. Note To connect to an existing MDT DB.ini to access the MDT DB.399 Microsoft Deployment Toolkit 2010 Update 1 Connect to an Existing MDT DB You can connect the Deployment Workbench to an existing MDT DB. type SQL Express for the instance name. In Network Library. which allows you to copy. Click Next. To connect to an existing MDT DB 1. Point to Microsoft Deployment Toolkit. you can leave Instance blank. In Instance. and then point to All Programs. Table 189. click New Database. If you are using the default value. In the Actions pane. the MDT DB to another SQL Server instance. The New DB Wizard starts. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database (where deployment_share is the name of the deployment share in which you will add the application). you can leave Port blank. In the Deployment Workbench console tree. 4. 2. type computer_name (where computer_name is the name of the computer running SQL Server). Select Use an existing database that already microsoft. Complete the New DB Wizard using the information in Table 189.com/technet/SolutionAccelerators Database Solution Accelerators . 4. or replicate. 1. In SQL Server name. type instance_name (where instance_name is the name of SQL Server instance on the computer running SQL Server). type port_number (where port_number is the TCP port number for the SQL Server if different than the default value).

The upgrade process preserves any schema modification in the existing MDT DB when you upgrade to the new MDT DB. Upgrading an Existing MDT DB The MDT DB is automatically upgraded from a previous version of BDD or MDT when you upgrade the deployment share. In SQL Share. Tip You can click Save Output to save the output of the wizard to a file. you can manually upgrade the MDT DB using the UpgradeMDTDatabaseSchema Windows PowerShell cmdlet. The database configuration information is shown in the details pane of the Deployment Workbench. Summary Confirmation Click Finish. In Database. This text box is required for Window PE to connect to the database using the Windows Integrated Security with Named Pipes protocol. Windows PE connects to the network shared folder. Review the information in the Details box. 2. you can leave SQL Share blank. SQL Share 1. If for some reason the existing MDT DB is not upgraded when you upgrade the deployment share. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. select database_name (where database_name is the name of the existing MDT DB). type share_name (where share_name is the name of a network shared folder on the computer specified on the SQL Server Details wizard page). establishing a network connection to the server so that Windows Integrated Security in SQL Server authenticates correctly. Solution Accelerators microsoft. Click Next. and then click Next. If Windows PE is not connecting to the database using this protocol. Click Next.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 400 On this wizard page Do this contains the required tables and views. 2.com/technet/SolutionAccelerators . The New DB Wizard finishes. 3.

Table 190.com/technet/SolutionAccelerators . Table 190 lists the types of tasks to be performed and the corresponding SQL Server server roles and database roles required to perform them.microsoft. The tables contain configuration settings that are accessible through the views. you may need different permissions on the MDT DB.401 Microsoft Deployment Toolkit 2010 Update 1 Assigning the Appropriate Permissions to the MDT DB Depending on the tasks to be performed. Roles and Required Roles To perform this task Create a new MDT DB from an existing database Create a new MDT DB and database at the same time Connect to an existing MDT DB You need these roles db_owner database role in the MDT DB sysadmin or dbcreator server role in the SQL Server instance in which the MDT DB resides db_datareader database role in the MDT DB or rights to the individual tables and views in the MDT DB db_ddladmin database role in the MDT DB db_datawrite database role in the MDT DB or rights to the individual tables and view in the MDT DB db_datareader database role in the MDT DB or rights to the individual tables and views in the MDT DB Modify the schema of the MDT DB Modify the configuration information stored in the MDT DB View the configuration information stored in the MDT DB For more information on how to assign these permissions see Adding a Member to a Predefined Role at http://msdn. Solution Accelerators microsoft. You can manage the configuration settings stored in the MDT DB using any combination of the following methods: • Manage configuration settings stored in the MDT DB using the Deployment Workbench as described in Manage Configuration Settings Stored in the MDT DB Using Deployment Workbench.com/en-us/library/aa905184.aspx. Managing Configuration Settings Stored in the MDT DB The MDT DB contains tables and views that the MDT 2010 deployment process can query.

applications. A group of computers based on the tasks performed by the users of the target computers (using the Role property). SerialNumber. packages. The Deployment Workbench manages the updates to the corresponding tables in the MDT DB. applications. packages.com/technet/SolutionAccelerators . applications.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 402 • Manage configuration settings stored in the MDT DB using SQL Server database tools as described in Manage Configuration Settings Stored in the MDT DB Using SQL Server Management Tools. Locations. Associate property settings. use standard SQL Server database tools as described in Manage Configuration Settings Stored in the MDT DB Using SQL Server Management Tools. Associate property settings. Table 191 lists the nodes beneath the Database node and describes when to make configuration settings in each node. UUID. because items in the other nodes can be associated with roles. roles. or MACAddress properties. You can use the nodes in Table 191 to make configuration settings that are stored in the MDT DB. and Administrator-level accounts with a location. and Administrator-level accounts with target computers that are of the same make and model. roles. Roles Locations Make and Model Note Create the items in the Roles node before creating items beneath the other nodes (Computers. Table 191. applications. Associate property settings. and Make and Model). Solution Accelerators microsoft. A group of computers using the DefaultGateway property of the target computers to identify a geographic location. Nodes Beneath the Database Node in a Deployment Share Node Computers Use this node to define Specific target computers based on one of these properties: AssetTag. Note Managing configuration settings stored in the MDT DB using the Deployment Workbench is good when adding a limited number of entries or managing individual entries. If you want to make bulk additions or updates to the MDT DB. packages. and Administrator-level accounts with a computer. A group of computers using the Make and Model properties of the target computers. roles. and Administrator-level accounts with a role. Manage Configuration Settings Stored in the MDT DB Using Deployment Workbench You can manage the configuration settings stored in the MDT DB using the nodes beneath the Database node in a Deployment Workbench deployment share. packages. Associate property settings.

click the Identity tab. Click the Administrators tab. Point to Microsoft Deployment Toolkit. Manage make and model–based configuration settings as described in Manage Make and Model–based Configuration Settings in Deployment Workbench. perform the following steps: 1. Click Start. Click the Packages tab. 4. Point to Microsoft Deployment Toolkit. Click the Details tab. 7. and then configure the relevant property values identified earlier in the process. 5. Click Start. 9. 6. In the Actions pane. type role_name (where role_name is the name of the role). 3. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database/Roles (where deployment_share is the name of the deployment share where you will manage the configuration settings). In the Properties dialog box. configure the accounts to be made members of the local Administrators group on the target computers.com/technet/SolutionAccelerators . In the Deployment Workbench console tree. and then click Deployment Workbench. In the Role name box. Click the Applications tab. and then configure the packages to install and the order of the package installation. Manage Computer-based Configuration Settings in Deployment Workbench To manage computer-based configuration settings. and then click Deployment Workbench. and then point to All Programs. Manage Role-based Configuration Settings in Deployment Workbench To manage role-base configuration settings. Solution Accelerators microsoft. 2. 8. click New. Manage location-based configuration settings as described in Manage Location-based Configuration Settings in Deployment Workbench. and then point to All Programs. perform the following steps: 1. and then configure the applications to install and the order of the application installation. and then click OK.403 Microsoft Deployment Toolkit 2010 Update 1 To manage the configuration settings stored in the MDT DB using the Deployment Workbench • • • • Manage role-base configuration settlings as described in Manage Role-based Configuration Settings in Deployment Workbench. Manage computer-based configuration settings as described in Manage Computer-based Configuration Settings in Deployment Workbench.

UUID.com/technet/SolutionAccelerators . 4. configure the accounts to be made members of the local Administrators group on the target computers. and then configure the roles to associate with the computer. In the Deployment Workbench console tree. 8. Click the Packages tab. 9. 7. you can specify any of the MAC addresses. and then click OK. type the information listed in Table 192. serial number. Click the Applications tab. Click the Details tab. and MACAddress properties. Note You only need to provide one of the methods for identifying the new computer from the list of the AssetTag. Table 192. Information to Complete the Identity Tab for a New Computers Item In this box Description Asset tag UUID Serial number Type The user-friendly description of the computer The asset tag or inventory control tag assigned to the computer The universally unique identifier (UUID) assigned to the target computer The serial number assigned to the target computer MAC address The MAC address assigned to the target computer (If the target computer has multiple network adapters. Click the Administrators tab. Solution Accelerators microsoft. and MAC address. 3. and then configure the applications to install and the order of the application installation. on the Identity tab. and then configure the appropriate property values identified earlier in the process. and then configure the packages to install and the order of the package installation. 5. In the Actions pane. see the AssetTag. UUID.) For more information about the values for asset tag. Toolkit Reference. In the Properties dialog box. UUID. Click the Roles tab. 6. SerialNumber. SerialNumber. click New. MDT 2010 identifies the target computer by any MAC address. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database/Computers (where deployment_share is the name of the deployment share in which you will manage the configuration settings). and MACAddress properties in the MDT 2010 document.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 404 2.

6.405 Microsoft Deployment Toolkit 2010 Update 1 Manage Location-based Configuration Settings in Deployment Workbench To manage location-base configuration settings. type location_name (where location_name is the user-friendly name to associate with the location) 5. Click Start. Click the Administrators tab. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database/Locations (where deployment_share is the name of the deployment share in which you will manage the configuration settings). and then click Deployment Workbench. In the Deployment Workbench console tree. In the Properties dialog box. Solution Accelerators microsoft. Click the Applications tab. In the Actions pane. Click the Packages tab. Manage Make and Model–based Configuration Settings in Deployment Workbench To manage make and model–based configuration settings. on the Identity tab. click New. and then configure the appropriate property values identified earlier in the process. 7. perform the following steps: 1. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database/Make and Model (where deployment_share is the name of the deployment share in which you will manage the configuration settings). type the IP addresses for all default gateways that exist within the location. 9. and then configure the roles to associate with the computer. in the Location box. 4. Click the Details tab. In the Properties dialog box. Click Start. click the Identity tab. 8. and then point to All Programs. and then point to All Programs. configure the accounts to be made members of the local Administrators group on the target computers. and then click Deployment Workbench. In the Actions pane. 3. 2. in the Default gateways box. Point to Microsoft Deployment Toolkit. on the Identity tab. Click the Roles tab. click New. In the Deployment Workbench console tree. 4.com/technet/SolutionAccelerators . 3. 2. Point to Microsoft Deployment Toolkit. perform the following steps: 1. and then click OK. and then configure the applications to install and the order of the application installation. 10. and then configure the packages to install and the order of the package installation. In the Properties dialog box.

bcp utility (Bcp.exe). update. views. 7. Click the Administrators tab. 11. and then configure the applications to install and the order of the application installation. see the section.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 406 5. and other database objects in the MDT DB to determine the tables that you want to update. and then click OK. type make_name (where make_name is the exact make [manufacturer] name returned by the BIOS of the target computer using WMI). Microsoft Office Access® or Office Excel have data-manipulation features that allow you to directly modify tables in the MDT DB using tools with which you are already familiar. or delete entries in tables in the MDT DB. type model_name (where model_name is the exact model name returned by the BIOS of the target computer using WMI). and then configure the packages to install and the order of the package installation. 6. Transact-SQL language in SQL Server. For more information on the tables and views in the MDT DB. However. Click the Roles tab. configure the accounts to be made members of the local Administrators group on the target computers. In the Make box. The Transact-SQL language allows you to add. Solution Accelerators microsoft. Click the Details tab. and then configure the roles to associate with the computer. 8. In the Model box. and then configure the appropriate property values identified earlier in the process. Toolkit Reference. Click the Packages tab. • • You can review the tables. use SQL Server database management tools. Click the Applications tab. if you need to add hundreds of entries (such as adding the configuration settings for the target computers) or if you want to perform a bulk update to the configuration settings. 9.com/technet/SolutionAccelerators .” in the MDT 2010 document. Manage Configuration Settings Stored in the MDT DB Using SQL Server Management Tools Managing the configuration settings stored in the MDT DB using the Deployment Workbench is good for management of a limited number of database entries. “Tables and Views in the Deployment Workbench Database. 10. Perform bulk import and update of configuration settings in the MDT DB using: • Microsoft Office system applications. This bulk import/export tool allows you to import configuration settings to and export configuration settings from the tables in the MDT DB.

In most instances.com/technet/SolutionAccelerators .ini file as described in Configure Access to the MDT DB by Directly Modifying the CustomSettings. Point to Microsoft Deployment Toolkit. Directly modify the CustomSettings. views. use the Configure DB Wizard to modify the CustomSettings. click Configure Database Rules. To configure CustomSettings. Solution Accelerators microsoft.ini to allow the MDT 2010 deployment process to access the MDT DB using any combination of the following methods: • • Run the Configure DB Wizard in the Deployment Workbench as described in Configure Access to the MDT DB Using the Configure DB Wizard. Only make direct modifications to the CustomSettings. The disadvantage of using the Configure DB Wizard is that it does not allow you to access any additional database objects that you have created. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Configuration/Database (where deployment_share is the name of the deployment share to which you will add the application). In the Deployment Workbench console tree. views.ini. and then click Deployment Workbench. However.ini for database queries using the Configure DB Wizard in the Deployment Workbench 1. Run the Configure DB Wizard for each deployment share defined in the Deployment Workbench that will be updated. 2.ini file. The advantages of using this wizard is that it helps reduce the: • • Possibility of configuration errors in the CustomSettings. Configure Access to the MDT DB Using the Configure DB Wizard The Configure DB Wizard in Deployment Workbench provides a graphical interface for configuring the MDT 2010 deployment process to access the MDT DB.ini File. the wizard recognizes any columns that you have added to the existing tables and views. or stored procedures. Click Start.ini file if you have added database objects. 3.ini file. or stored procedures. such as tables. In the Actions pane. You can modify CustomSettings. and then point to All Programs.407 Microsoft Deployment Toolkit 2010 Update 1 Configuring the MDT 2010 Deployment Process to Access the MDT DB Configure the MDT 2010 deployment process to access the MDT DB and retrieve the configuration settings stored in it by modifying CustomSettings. such as tables.ini file to enable retrieval of configuration settings from the MDT DB. The Configure DB Wizard starts. Effort required to modify the CustomSettings.

Complete the Computer Options wizard page using the information in Table 193. Complete the Location Options wizard page using the information in Table 194. Query the settings configured on the Details tab of the location item’s Properties dialog box. 5. Query the roles associated with the location on the Roles tab of the location item’s Properties dialog box. and then click Next. Query for administrators to be assigned for this location Solution Accelerators Query the accounts that are to be made members of the local Administrators group on the target computers within the location microsoft. Query for administrators to be assigned to this computer Query the accounts that are to be made members of the local Administrators group on the target computer as configured on the Administrators tab of the computer item’s Properties dialog box. Query for location-specific settings Query for roles assigned for this location Query for applications to be Query the applications to be installed on installed for this location the target computers within the location configured on the Applications tab of the location item’s Properties dialog box.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 408 4. Table 194.com/technet/SolutionAccelerators . Query the roles associated with the computer on the Roles tab of the computer item’s Properties dialog box. and then click Next. Information to Complete the Computer Options Wizard Page Select this check box Query for computerspecific settings Query for roles assigned to this computer To do this Query the settings configured on the Details tab of the computer item’s Properties dialog box. Query for applications to be Query the applications to be installed on installed on this computer the computer as configured on the Applications tab of the computer item’s Properties dialog box. Information to Complete the Location Options Wizard Page Select this check box Query for location names based on default gateways To do this Query for location names based on the IP addresses of the default gateways configured on the Identity tab of the location item’s Properties dialog box. Table 193.

7. 6. Information to Complete the Role Options Wizard Page Select this check box Query for role-specific settings To do this Query the settings configured on the Details tab of the role item’s Properties dialog box.409 Microsoft Deployment Toolkit 2010 Update 1 Select this check box To do this configured on the Administrators tab of the location item’s Properties dialog box. and then click Next. Table 195.com/technet/SolutionAccelerators . and then click Finish. Query for administrators to be assigned to machines with this make and model Query the accounts that are to be made members of the local Administrators group on the target computer with the make and model as configured on the Administrators tab of the make and model item’s Properties dialog box. Table 196. Complete the Make/Model Options wizard page using the information in Table 195. Information to Complete the Make/Model Options Wizard Page Select this check box Query for model-specific settings Query for roles assigned to computers with this make and model To do this Query the settings configured on the Details tab of the make and model item’s Properties dialog box. Solution Accelerators microsoft. Query for applications to be Query the applications to be installed on installed on computers with the target computers with the make and this make and model model as configured on the Applications tab of the make and model item’s Properties dialog box. Query the roles associated with the make and model on the Roles tab of the make and model item’s Properties dialog box. Complete the Role Options wizard page using the information in Table 196. Query for applications to be Query the applications to be installed on installed for this role computers that perform this role as configured on the Applications tab of the role item’s Properties dialog box.

MacAddress ParameterCondition=OR Solution Accelerators microsoft. When the Configure DB Wizard has finished. LSettings. 8. Default Properties=MyCustomProperty [Default] OSInstall=Y UserDataLocation=NETWORK SkipAppsOnUpgrade=YES SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES [CSettings] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerSettings Parameters=UUID. On the Summary wizard page. Locations. LAdmins.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 410 Select this check box Query for administrators to be assigned for this role To do this Query the accounts that are to be made members of the local Administrators group on computers that perform this role as configured on the Administrators tab of the role item’s Properties dialog box. RApps. CApps. LRoles. RSettings. the CustomSettings. Listing 12. MMAdmins. CAdmins. RAdmins. SerialNumber. RPackages. MMRoles.ini File After the Configure DB Wizard Has Finished [Settings] Priority=CSettings. and then click Finish.ini file is configured to perform the selected queries. MMSettings. Listing 12 provides an example of the CustomSettings. and then click Next. LPackages. MMApps. LApps. CRoles. review the information. On the Confirmation wizard page.com/technet/SolutionAccelerators . CPackages. The CustomSettings. 9. AssetTag.ini file after the Configure DB Wizard has finished. review the information in the Details box. MMPackages.

AssetTag. SerialNumber. AssetTag. MacAddress ParameterCondition=OR Order=Sequence [CAdmins] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerAdministrators Parameters=UUID. AssetTag. SerialNumber.411 Microsoft Deployment Toolkit 2010 Update 1 [CPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerPackages Parameters=UUID. SerialNumber. SerialNumber. MacAddress ParameterCondition=OR Order=Sequence [CApps] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerApplications Parameters=UUID.com/technet/SolutionAccelerators . MacAddress Solution Accelerators microsoft. MacAddress ParameterCondition=OR [CRoles] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerRoles Parameters=UUID. AssetTag.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 412 ParameterCondition=OR [Locations] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=Locations Parameters=DefaultGateway [LSettings] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationSettings Parameters=DefaultGateway [LPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationPackages Parameters=DefaultGateway Order=Sequence [LApps] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationApplications Parameters=DefaultGateway Order=Sequence [LAdmins] Solution Accelerators microsoft.

413 Microsoft Deployment Toolkit 2010 Update 1 SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationAdministrators Parameters=DefaultGateway [LRoles] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationRoles Parameters=DefaultGateway [MMSettings] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelSettings Parameters=Make. Model Order=Sequence [MMApps] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW Solution Accelerators microsoft.com/technet/SolutionAccelerators . Model [MMPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelPackages Parameters=Make.

Model [MMRoles] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelRoles Parameters=Make.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 414 SQLShare=Client Table=MakeModelApplications Parameters=Make. Model [RSettings] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=RoleSettings Parameters=Role [RPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=RolePackages Parameters=Role Order=Sequence Solution Accelerators microsoft.com/technet/SolutionAccelerators . Model Order=Sequence [MMAdmins] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelAdministrators Parameters=Make.

see: • For more information about customizing tables and views in the configuration database.415 Microsoft Deployment Toolkit 2010 Update 1 [RApps] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=RoleApplications Parameters=Role Order=Sequence [RAdmins] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=RoleAdministrators Parameters=Role For more information about customizing the MDT DB. “Automating Deployment by Location” in the MDT 2010 document. Microsoft Deployment Toolkit Samples Guide.” in the MDT 2010 document.com/technet/SolutionAccelerators . “Properties.” in the MDT 2010 document. Solution Accelerators microsoft. see: • • • • “Automating Deployment to a Specific Computer” in the MDT 2010 document. Microsoft Deployment Toolkit Samples Guide. For more information about customizing each property. see: • The section. Microsoft Deployment Toolkit Samples Guide. Toolkit Reference. Microsoft Deployment Toolkit Samples Guide. Toolkit Reference. “Automating Deployment by Role” in the MDT 2010 document. The corresponding section for each property in the section. “Automating Deployment by Computer Make and Model” in the MDT 2010 document. “Tables and Views in the Deployment Workbench Database.

type SQLExpress for the instance name. If you are using: • SQL Server installed as the default instances. you cannot specify the StoredProcedure property. However. which is used when performing user authentication using Windows Integrated Authentication with Named Pipes protocol.ini to return the proper query results. Specifies the name of the MDT DB in the SQL Server instance specified in the Instance property. “Properties. you cannot specify the Table property. Specifies the network library to be used in connecting to the MDT DB specified in the Database property and can be either Named Pipes (DBNDPNTW) or TCP/IP Sockets (DBMSSOCN). microsoft. Properties That Are Used to Create an SQL Query Property SQLServer Instance Description Specifies the name of the computer running SQL Server to use in the query Specifies the name of the SQL Server instance on the computer specified in the SQLServer property. If you specify the Table property. too: You must specify one or the other. Specifies a network shared folder on the computer specified in the SQLServer property. see the corresponding section for each property in the section. if you need to create custom queries for information. requires minimal knowledge about how the CustomSettings.ini file is modified. you can leave Instance blank. Toolkit Reference. you can modify CustomSettings.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 416 Configure Access to the MDT DB by Directly Modifying the CustomSettings. For more information on the properties in Table 197.” in the MDT 2010 document. Table 197. Specifies the stored procedure to be used in the query.ini file that are used to build an SQL query. Specifies the table or view to be used in the query. and minimizes the risk of configuration errors. too: You must specify one or the other.com/technet/SolutionAccelerators Database Netlib SQLShare Table StoredProcedure Solution Accelerators . • SQL Server Express. Table 197 lists the MDT 2010 properties that are used to create the query. The Configure DB Wizard creates entries in the CustomSettings. If you specify the StoredProcedure property.ini File The Configure DB Wizard in the Deployment Workbench provides the method that requires the least effort.

417 Microsoft Deployment Toolkit 2010 Update 1 Property Parameters Description Specifies the selection criteria for returning rows from the query. AssetTag. Conceptually.ini File After the Configure DB Wizard Has Finished [Settings] Priority=CSettings. MacAddress ParameterCondition=OR The Priority line in the CustomSettings. Default [Default] OSInstall=YES [CSettings] SQLServer=NYC-SQL-01 Instance=SQLEXPRESS Database=MDTDB Netlib=DBNMPNTW SQLShare=SQL$ Table=ComputerSettings Parameters=UUID. Most of these properties in Table 197 were configured when you created the MDT DB.ini file contains the Computers value. Note The SQL query that these properties create returns all columns from the table or view specified in the Table property.ini file that creates an SQL query that returns all the configuration information in the Computers view for a computer that matches the SerialNumber or AssetTag of the computer being deployed. SerialNumber.com/technet/SolutionAccelerators . If you want to use a Boolean OR operation. which directs MDT 2010 to process the [CSettings] section later in the CustomSettings. Listing 13 provides an example of CustomSettings.ini file. this property is the ORDER BY clause in an SQL SELECT statement. The CustomSettings. You can select either Boolean AND (the default) or OR operations. Listing 13. Conceptually. this property is the WHERE clause in an SQL SELECT statement. The properties in the [CSettings] section performs the Solution Accelerators microsoft. you must specify ParameterCondition=OR. ParameterCondition Specifies the Boolean operation to be performed when you specify more than one selection criterion in the Parameters property. Order Specifies the sort order of the rows returned from the query.

” in the MDT 2010 document.” in the MDT 2010 document. roles. there may be instances in which you need to extend the information associated with one or more of the entities in the MDT DB.ini file as described in Reference the New Column in the CustomSettings. Extending the Schema of the MDT DB Although the MDT DB contains most of the common configuration settings that you would need in your deployment. Modify and refresh the views that are dependent on the table and in which you want to return the new column in the result set as described in Modify and Refresh the Dependent Views. such as the computer name or IP address of the target computer. see the section.ini File. such as computers. or the makes and models. “Tables and Views in the Deployment Workbench Database. If you extend the schema for the tables. Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 418 query and returns the result set from the query to be used during the MDT 2010 deployment process. You extend the schema for the: • • Tables using the Microsoft SQL Server Management Studio or the ALTER TABLE Transact-SQL statement. “Tables and Views in the Deployment Workbench Database. Views using the SQL Server Management Studio or the ALTER VIEW Transact-SQL statement. For more information on the tables and views in the MDT DB. 4. Reference the new column in the CustomSettings. see the section. you must extend the schema for one or more of the tables and views in the MDT DB. review the tables and views in the MDT DB to determine which you need to modify. To extend the schema of the MDT DB. Determine the tables and views to be modified by reviewing the schema of the MDT DB as described in Determine the Tables and Views to Be Modified. Modify the tables using SQL Server Management Studio or the ALTER Transact-SQL statement as described in Modify the Table. locations. 5. you might also need to modify the views that depend on those tables.com/technet/SolutionAccelerators . Toolkit Reference. You can review the tables and views in the MDT DB to determine the columns you want to reference in the Parameters property. Create a task sequence step that references the new column as described in Reference the New Column in a Task Sequence Step. To extend the schema of the MDT DB 1. 6. Toolkit Reference. Create a backup of the existing MDT DB as described in Create a Backup of the MDT DB. For more information on the tables and views in the MDT DB. 2. 3. If so.

see the section. The table most commonly modified is Settings.com/technet/SolutionAccelerators Solution Accelerators . included with SQL Server. see “How to: Insert Columns into Tables (Visual Database Tools)” in SQL Server Books Online. Tip To determine which views are dependent on a table. included with SQL Server. Retrieve the information through the LocationSettings view. For more information on how to perform database backups using this method. Create a backup of the MDT DB using: • SQL Server Management Studio. because they already return all columns. see the documentation for your backup solution. Existing SQL Server backup solution in your organization.419 Microsoft Deployment Toolkit 2010 Update 1 Determine the Tables and Views to Be Modified Determine the tables and views to be modified by reviewing the schema of the tables and views in the MDT DB. the bank’s IT pros need to add an antivirus server configuration setting for each location that they define in the MDT DB. or contact your DBA. To do this. Create a Backup of the MDT DB As a best practice. For more information on how to add a column using SQL Server Management Studio. such as the ComputerSettings or LocationSettings. Example: How Woodgrove Bank Determined the Tables and Views to Be Modified Woodgrove Bank has decided that it needs to configure the antivirus server based on the location of a target computer. For more information on the tables and views in the MDT DB. and then clicking Edit. Note the views provided with MDT 2010 do not require modification. For more information on how to perform database backups using this method. microsoft. You add new columns to tables in the MDT DB using: • SQL Server Management Studio. “Tables and Views in the Deployment Workbench Database.” in the MDT 2010 document. see “How to: Back Up a Database (SQL Server Management Studio)” in SQL Server Books Online. create a backup of the MDT DB before modifying the tables and views in it. To make the antivirus server information available. • Modify the Table You modify the table by adding new columns to it. Toolkit Reference. look at the Transact-SQL statements used to create the view by right-clicking the view. which is common to all views. they must: • • Modify the Settings table.

see “ALTER TABLE (Transact-SQL)” in SQL Server Books Online. The columns that you will add to the table. For more information on how to add a column using SQL Server Management Studio.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 420 • ALTER TABLE Transact-SQL statement. • To add a new column to a table. included with SQL Server. see the section. you would add the new column to custom views that you have created. see the documentation for the corresponding tool. If you have not created custom views. you need to know: • • • • • For more information on how to determine what to use for each item in the previous list. Other SQL Server management tools. Information for the AVServer Column Property Name Allow Nulls Data Type Value AVServer Yes char(20) Modify and Refresh the Dependent Views After the column has been added to the table. “Table Column Properties (SQL Server Management Studio). For more information on how to add a column using the ALTER TABLE Transact-SQL statement. The default value for the new column (optional). The SQL data type for each column you will add to the table. Table 198. Check constraints for the new column (optional). If the new column allows Null values. For more information on how to perform this task using other SQL Server management tools. included with SQL Server. because all these views already return all columns. “Working Solution Accelerators microsoft. The AVServer column will contain the computer name of the antivirus server for each location specified in the LocationIdentity table. Example: How Woodgrove Bank Modified Tables Woodgrove Bank will add a new column to the Settings table called AVServer. Modify the dependent views in the MDT DB using: • SQL Server Management Studio.com/technet/SolutionAccelerators . Note the views provided with MDT 2010 do not require modifications. Woodgrove Bank has decided to create the AVServer column using the information in Table 198.” in SQL Server Books Online. modify any views you want to display for the newly created column. Typically. see the section. you can skip this step.

This step may not be necessary if CustomSettings. perform the following steps: 1. The SQL SELECT statement used to create the view.” in SQL Server Books Online. included with SQL Server. Woodgrove Bank ran the sp_refreshview stored procedure to refresh the ComputerSettings. 2. included with SQL Server. Example: How Woodgrove Bank Modified the Dependent Views Woodgrove Bank does not need to modify any views. However. as the LocationSettings view already returns all columns from the Settings table.” in SQL Server Books Online. The sp_refreshview stored procedure is required to update views when the columns in dependent tables or views have changed. see the section. • To modify the dependent view. For more information on how to drop a view using the ALTER VIEW Transact-SQL statement. This reference initiates the query defined in the query section that you will create in a later step.421 Microsoft Deployment Toolkit 2010 Update 1 with Views (Visual Database Tools). ”Modifying Views. refresh all views that reference modified tables by running the sp_refreshview stored procedure. "sp_refreshview (TransactSQL). LocationSettings. Add the new column name to the Properties line in the CustomSettings. Even if the views do not require modification.” in SQL Server Books Online.ini already has an existing query for the view or table referenced in the query. or RoleSettings views. • ALTER VIEW Transact-SQL statement. configure the CustomSettings. if required. Solution Accelerators microsoft. if required. see the documentation for the corresponding tool. included with SQL Server. For more information about the sp_refreshview stored procedure. This allows all the views to return the computer name of the antivirus server. Add a reference to the query section on the Priority line in the CustomSettings. “ALTER View (Transact-SQL). see the section. For more information on how to perform this task using other SQL Server management tools. which reference the Settings table.ini File After you have added the column to the table and modified the appropriate views.ini file. To reference the new column in the CustomSettings. see the section. MakeModelSettings. you need to know: • • For more information on determining what to use of each of the items in the previous list. The columns that you will add to the view. included with SQL Server.ini file.” in SQL Server Books Online. Other SQL Server management tools.com/technet/SolutionAccelerators .ini file to reference the new column. Reference the New Column in the CustomSettings.ini file.

Create a query section that was referenced in step 1. You reference the new column as a task sequence variable in the task sequence step.ini File to Retrieve Antivirus Server for Woodgrove Bank [Settings] Priority=LSettings. you are ready to reference the new column in a task sequence step. the task sequence variable will be named Zip_Code. 3. The task sequence variable can then be referenced in a task sequence step. all Woodgrove Bank needs to do is add AVServer to the Priority line so that MDT 2010 creates a task sequence variable of the same name. The variable will have the same name as the column.ini File Woodgrove Bank queries the LocationSettings view to return the antivirus server for a particular location.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 422 This reference informs MDT 2010 to resolve the value for AVServer and create a task sequence variable of the same name. CustomSettings. Default Properties=AVServer [Default] OSInstall=YES [LSettings] SQLServer=NYC-SQL-01 Instance=SQLExpress Database=MDTDB Netlib=DBNMPNTW SQLShare=SQL$ Table=LocationSettings Parameters=DefaultGateway Reference the New Column in a Task Sequence Step Now that the CustomSettings. Listing 14. which queries the appropriate table or view. The LSettings query already exists in the CustomSettings. Example: How Woodgrove Bank Referenced the New Column in a Task Sequence Step Solution Accelerators microsoft.com/technet/SolutionAccelerators . As shown in Listing 14.ini file is modified to return the configuration settings from the new column. if you create a column named Zip_Code. For example.ini file after running the Configure DB Wizard. Example: How Woodgrove Bank Referenced the New Column in the CustomSettings.

the antivirus server name can be provided by using the –server parameter and referencing the new column name as a task sequence variable (%AVSERVER%).exe -server %AVSERVER% Solution Accelerators microsoft. As a part of the antivirus setup program.423 Microsoft Deployment Toolkit 2010 Update 1 Woodgrove Bank creates a custom task sequence step to run the antivirus setup program. The command line used to run the antivirus setup program is: avsetup.com/technet/SolutionAccelerators .

configure the appropriate shared folder permissions. Table 199. Use any name for these shared folders. the remainder of the deployment process refers to these shared folders by these names. Configuring shared folder permissions as described in Configuring Shared Folder Permissions. create additional shared folders in which to store the user state migration data and the deployment logs. Shared Folders and Their Descriptions Shared folder Description MigData Logs Stores the user state migration data during the LTI deployment process. Stores the deployment logs during the LTI or ZTI deployment process. Note The files in Table 199 are recommended shared folder names. Prepare the MDT 2010 migration resources by: • • • Creating additional shared folders as described in Creating Additional Shared Folders. deployment scripts connect to the deployment shares and shared folders. Configuring Shared Folder Permissions After creating additional shared folders listed in Table 199. However. To configure the shared folder permissions for the folders listed in Table 199 . Only the target computer creating the user state migration information and the deployment logs should have access to these folders. Ensure that unauthorized users are unable to access user state migration information and the deployment logs. Creating Additional Shared Folders Before starting the deployment.424 Microsoft Deployment Toolkit 2010 Update 1 Preparing the MDT 2010 Migration Resources During deployment to the target computers. This folder is optional for either deployment. Table 199 lists the shared folders that must be created and describes the purpose of each. Configuring access to other resources as described in Configuring Access to Other Resources. Create accounts for the scripts to use when accessing these resources.

2. The resources include application or database servers (such as Microsoft SQL Server 2005 or Microsoft Exchange Server 2003). Configuring Access to Other Resources In addition to the shared folders just created. 12. In Windows Explorer. In the Enter the object name to select box. and then click OK. 6. click This folder only. click Advanced. 9. 3. in the Apply onto list. On the Permissions tab. On the Permissions tab. type Authenticated Users. 5. click Add. and then click Properties. In the Security dialog box.com/technet/SolutionAccelerators . in the Permissions list. 4. click Remove. In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). you may want to further restrict the user accounts that can access the shared folder. type CREATOR OWNER. Solution Accelerators microsoft. click Add. On the Permissions tab. In the Enter the object name to select box. clear the Allow inheritable permissions from the parent to propagate to this object and all child objects check box.425 Microsoft Deployment Toolkit 2010 Update 1 1. This action allows domain computers and domain users to access the subfolders they create. click Allow for the Full Control permission. in the Permissions list. The permissions set in these steps work for both LTI and ZTI deployments. You can restrict user accounts for: • • LTI deployments by substituting Authenticated Users in the steps above with each account you want to have access. in the Apply onto list. Repeat steps 10–13 for each group that will receive Administrator privileges. 13. click Subfolders and files only. On the Security tab. and then click OK. the MDT 2010 scripts might require access to other resources. click Allow for the Create Folders/Append Data permission. In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). and then click OK. In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). 7. In some instances. and then click OK. 10. right-click shared_folder (where shared_folder is one of the shared folders listed in Table 156). ZTI deployments by substituting Authenticated Users in the steps above with the network access account in System Center Configuration Manager. 8. 11.

MDT 2010 deployment share for LTI deployments. use the same credentials listed above. UserPassword.com/technet/SolutionAccelerators . Any resources accessed using the ZTIConnect. see the MDT 2010 document. Note Other connections to the same servers. Grant access to the following resources: • • • Any resources on application or database servers for LTI or ZTI deployments. and Database properties. Configure access to the deployment share created in the Deployment Workbench. Note For further guidance on using the ZTIConnect. such as Named Pipes and RPC.Using the Microsoft Deployment Toolkit: Preparing Migration Resources 426 Access is granted to the credentials specified in the: • • • UserID. Configure access to resources that are referenced using the ZTIConnect. Network access account used by the System Center Configuration Manager Client for ZTI deployments. Windows Deployment Wizard for LTI deployments. SQLShare.wsf script for LTI or ZTI deployments. Use the ZTIConnect.wsf script.wsf script. Microsoft Deployment Toolkit 2010 Samples Guide. and UserDomain properties for LTI deployments.wsf script to establish these connections. Configure access to applications or databases that are accessed through the SQLServer. Solution Accelerators microsoft.

com/enus/library/cc772106WS. For these scenarios.” at http://go. Preparing Windows Deployment Services for LTI Deployments You can use Windows Deployment Services in LTI deployments in the following ways: • Start Windows PE on the target computers.10). • For more information about setting up and configuring Windows Deployment Services. You can create custom WIM images in the Deployment Workbench that you can deploy directly to target computers using Windows Deployment Services.aspx. The white paper.com/fwlink/?LinkId=81031. Prepare Windows Deployment Services for LTI deployments by: .microsoft. see: • • • Windows Deployment Services at http://technet. included in Windows Deployment Services. Install images created in the Deployment Workbench on the target computers. The Windows Deployment Services Help file. These boot images can be Windows PE images or custom images that can deploy operating systems directly to the target computers. The beginning of the New Computer deployment scenario and the second half of the Replace Computer deployment scenario both start the target computer in Windows PE.Using the Microsoft Deployment Toolkit: Preparing Windows Deployment Services 427 Preparing Windows Deployment Services You can use Windows Deployment Services in conjunction with MDT 2010 to automatically initiate boot images on target computers. Prepare Windows Deployment Services for use with MDT 2010 by: • • • Preparing Windows Deployment Services for use in LTI deployments as described in Preparing Windows Deployment Services for LTI Deployments. “Deploying and Managing the Windows Deployment Services Update on Windows Server 2003.microsoft. Preparing Windows Deployment Services for use in ZTI deployments as described in Preparing Windows Deployment Services for ZTI Deployments. you can automate starting Windows PE using Windows Deployment Services. Preparing Windows Deployment Services for use in UDI deployments as described in Preparing Windows Deployment Services for UDI Deployments.

Note This mode is supported only in Windows Server 2003. Table 200 compares the operational modes of Windows Deployment Services.Using the Microsoft Deployment Toolkit: Preparing Windows Deployment Services 428 • Selecting the operational mode for Windows Deployment Services for LTI deployments as described in Selecting Windows Deployment Services Operational Mode for LTI Deployments. not in Windows Server 2008 or later server operating systems. This configuration supports only: • Windows PE as the boot operating system. not in Windows Server 2008 or later server operating systems. This configuration supports only: • OSChooser or Windows PE as the boot operating system. Windows Deployment Services Operating Modes Mode Legacy Description Functionally equivalent to Remote Installation Service (RIS). Riprep.com/technet/SolutionAccelerators Solution Accelerators . Table 200. This configuration supports only: • OSChooser as the boot operating system. Native Provides only Windows Deployment Services–specific support. run Windows Deployment Services in Mixed or Native mode. Pre-staging target computers in Windows Deployment Services for LTI deployments as described in Pre-stage Target Computers for Windows Deployment Services for LTI Deployments. • • • Selecting Windows Deployment Services Operational Mode for LTI Deployments Windows Deployment Services is responsible for initiating the deployment process for PXE boot-enabled target computers. • Images created by Risetup. or WIM. Note This mode is supported only in Windows Server 2003. To use Windows Deployment Services for LTI. microsoft. Enabling Windows Deployment Services multicast deployment of images in Windows Deployment Services for LTI deployments as described in Enable Windows Deployment Services Multicast Deployment for LTI Deployments. • Administration using the normal RIS tools or Windows Deployment Services management tools. Mixed Allows compatibility with RIS and Windows Deployment Services. • Images created by Remote Installation Service Setup (Risetup) and Remote Installation Preparation (Riprep). • Administration using the normal RIS tools. Adding boot images created in the Deployment Workbench for LTI deployments to Windows Deployment Services as described in Add LTI Boot Images to Windows Deployment Services.

You can add LTI boot images to Windows Deployment Services using the Windows Deployment Services management console or the WDSUTIL. Note If Windows Deployment Services is configured to respond to any computer (known or unknown). Add LTI Boot Images to Windows Deployment Services You can add the LTI boot image WIM files in the Boot folder of a deployment share to Windows Deployment Services. the computer accounts exist in AD DS domains (also called known computers). Pre-stage Target Computers for Windows Deployment Services for LTI Deployments You can pre-stage PXE client computers in AD DS domains. Depending on the Windows Deployment Services configuration. When target computers are pre-staged. If you pre-stage the target computers. Instead. Note Responding to unknown computers is the preferred method for LTI deployments. Target computers that are not pre-staged do not have computer accounts in AD DS domains (also called unknown computers).” in Windows Deployment Services Help. You can configure Windows Deployment Services to respond to computers that are known or unknown. LTI uses the computer name and credentials configured in the task sequence or through the rules process. you may need to pre-stage the target computers. not in Windows Server 2008 or later server operating systems. Doing so allows Windows Deployment Services to automatically initiate LTI deployment by starting LTI boot images. Solution Accelerators microsoft.10).com/technet/SolutionAccelerators . • Administration using the Windows Deployment Services management tools.aspx.429 Microsoft Deployment Toolkit 2010 Update 1 Mode Description • Images created by WIM. For more information about adding an LTI boot image to Windows Deployment Services. Note This mode is supported only in Windows Server 2003. LTI is unable to use the pre-staged computer account. Doing so authorizes Windows Deployment Services to deploy operating system images to the target computer. Only Windows Deployment Services can use the pre-staged computer accounts. LTI will not use a pre-staged computer account when joining the domain. You do not need to add operating system images from the Deployment Workbench.microsoft.exe tool.com/enus/library/cc732961(WS. because it is the simplest method. Note Add the LTI boot images only to Windows Deployment Services. see: • • “Add an Image. which is included in Windows Deployment Services. How to Manage Images at http://technet. pre-staging the target computers is not necessary.

mspx. Images stored in Windows Deployment Services cannot be deployed using multicast transfer. 7. Click Start. review the information displayed. 5. In the Computer’s unique ID (GUID/UUID) box. 2. 6. This option designates a specific server to service the computer. multicasting support is disabled in MDT 2010. type guid_uuid (where guid_uuid is the GUID/UUID of the computer). Solution Accelerators microsoft. This option specifies that this computer can be serviced by any RIS/Windows Deployment Services server. In the Host server dialog box. select one of the following options. and then click Next. 3. and then click Next: • Any available remote installation server. right-click organizational_unit (where organizational_unit is the name of the OU that will contain the target computer). In the New Object – Computer dialog box. By default. “Locate the GUID for client computers.microsoft. Note For more information on locating the GUID for target computers. Specify the FQDN of the server running Windows Deployment Services. and then click Active Directory Users and Computers. which reduces the amount of network traffic required when multiple computers need to receive the same image. In the console tree. type computer_name (where computer_name is the name of the target computer). 4. select the This is a managed computer check box. The images are transferred to the target computers using multicast from the deployment share. Note MDT 2010 supports only the multicast transfer of images stored in the LTI$ distribution share. in the Computer name box. the Deployment Workbench creates a multicast namespace for the deployment share. point to New. see the Microsoft TechNet document. Close all open windows.com/technet/SolutionAccelerators . point to Administrative Tools. • Enable Windows Deployment Services Multicast Deployment for LTI Deployments Multicast deployment of LTI operating systems using Windows Deployment Services allows multiple computers to receive a single copy of an image. The following remote installation server. For LTI deployments.” at http://technet2. not from a Windows Deployment Services share. In the New Object – Computer dialog box. and then click Computer.com/WindowsServer/en/library/c2d81caf-dd93-4f4b-bc2d907c0413805c1033. and then click Finish. In the Managed dialog box.Using the Microsoft Deployment Toolkit: Preparing Windows Deployment Services 430 To pre-stage the target computers for Windows Deployment Services 1. and then click Next.

MDT 2010 can automatically configure Windows Deployment Services to support multicast deployments. as other client computers request the same image. Then. In this scenario. Solution Accelerators microsoft. a multicast transmission of the selected image begins. MDT 2010 and the deployment share are installed on a separate computer from the one running Windows Server 2008 or a later server operating system with the Windows Deployment Services role as described in Enable Multicast Deployments with MDT 2010 Installed on a Different Computer from Windows Deployment Services. you must configure Windows Deployment Services manually. • Note The Multicasting feature in MDT 2010 is only supported in Windows Server 2008 or later server operating systems. Enable Multicast Deployments with MDT 2010 Installed on the Same Computer as Windows Deployment Services In this scenario. Note If the computer on which MDT 2010 is installed is running Windows Server 2003. In this scenario. MDT 2010 supports multicast-based deployments when MDT 2010 and the deployment share are installed on: • The computer running Windows Deployment Services.431 Microsoft Deployment Toolkit 2010 Update 1 The multicast types available for use in LTI deployments include: • Auto-Cast. Install Windows Server 2008 or a later server operating system on the computer that is to be the deployment server. MDT 2010 is installed on a computer running Windows Server 2008 or a later server operating system with the Windows Deployment Services role as described in Enable Multicast Deployments with MDT 2010 Installed on the Same Computer as Windows Deployment Services. as soon as an applicable client computer requests an installation image. In this option. • A computer other than the computer Windows Deployment Services is running on. Note You cannot use these scenarios to allow multicast for boot images. To enable multicast deployments with MDT 2010 installed on the same computer as Windows Deployment Services 1. MDT 2010 is installed on a computer running Windows Server 2008 or a later server operating system with the Window Deployment Services server role. they are joined to the transmission that has already started. This option sets the start criteria for the transmission based on the number of client computers requesting an image or a specific day and time. Note If MDT 2010 is installed on a separate computer. as the multicast client is not loaded until after Windows PE is running. Scheduled-Cast. In this scenario. you must install the Remote Server Administration Tools feature so that the WDSUTIL command-line utility is available.com/technet/SolutionAccelerators . LTI only uses multicast to transfer operating system WIM files.

In the deployment_share Properties dialog box (where deployment_share is the name of an existing deployment share).0 on the computer that is to be the deployment server. remotely run the WDSUTIL command on the computer running Windows Deployment Services and Windows Server 2008 or the later server operating system. 3. Install MDT 2010 on the same computer as in step 3. right-click deployment_share (where deployment_share is the name of an existing deployment share for which multicast deployments will be enabled). To enable multicast deployments with MDT 2010 Installed on a different computer than Windows Deployment Services 1. select the Enable multicast for this deployment share check box. and then press ENTER (where remote_server is the name of the computer running Windows Server 2008 or the later server operating system with the Windows Deployment Services Solution Accelerators microsoft. Install Windows AIK version 2. 4. Install MDT 2010 on the computer that is to be the deployment server. and then click Properties. Install Windows Server 2008 or a later server operating system on the computer hosting the deployment share.0 on a computer other than the computer hosting the deployment share. Install the Windows Deployment Services server role on the computer that is to be the deployment server. and then click OK. Note The Network (UNC) path and Local Path text boxes on the General tab must contain valid paths for multicasting to function properly. On the computer hosting the deployment share. Windows Deployment Services and Windows Server 2008 or a later server operating system are all installed on the computer acting as the deployment server. type the following command. 5. 2. In the details pane. Install the Windows Deployment Services server role on the computer hosting the deployment share.com/technet/SolutionAccelerators . 3. In the Actions pane. When completed. 6. In this configuration. 8. click Deployment Shares. Enable Multicast Deployments with MDT 2010 Installed on a Different Computer from Windows Deployment Services In this scenario. the Deployment Workbench creates an Auto-Cast Windows Deployment Services multicast transmission from the deployment share. but MDT 2010 is installed on another computer. 7. Install Windows AIK 2. on the General tab. In the Deployment Workbench console tree. 5.Using the Microsoft Deployment Toolkit: Preparing Windows Deployment Services 432 2. Start the Deployment Workbench. in a Command Prompt window. 4. 9. click Update Deployment Share.

com/technet/SolutionAccelerators . which in turn allows target computers to boot images that System Center Configuration Manager manages using PXE. Preparing Windows Deployment Services for UDI Deployments Prepare Windows Deployment Services for UDI deployments using the same process for ZTI deployments as described in Preparing Windows Deployment Services for ZTI Deployments. Solution Accelerators microsoft. in Configuration Manager Documentation Library. set a System Center Configuration Manager PXE service point on the computer on which Windows Deployment Services is installed. Preparing Windows Deployment Services for ZTI Deployments For ZTI deployments. the WDSUTIL tool creates an Auto-Cast Windows Deployment Services multicast transmission from the deployment share. Doing so allows System Center Configuration Manager to directly service PXE boot requests received by Windows Deployment Services as a PXE service point. • Note In addition to the methods described here. included with System Center Configuration Manager. you can use traditional Windows Deployment Services methods for responding to PXE boot requests. included with System Center Configuration Manager. For more information.exe /new-namespace /friendlyname:"BDD Share Deploy$" /server:remote_server /namespace:"Deploy$" /contentprovider:WDS /configstring:"deploy_share_path" /namespacetype:AutoCast When completed. see the Windows Deployment Services Help file included with Windows Deployment Services. For more information about preparing Windows Deployment Services for ZTI deployments.433 Microsoft Deployment Toolkit 2010 Update 1 server role and deploy_share_path is the fully qualified path to the root of the deployment share). wdsutil. see: • “How to Deploy an Operating System Image Using PXE” in Configuration Manager Documentation Library. “How to Configure the PXE Service Point.

including: • The “App-V 4.com/enus/appvirtualization/cc843994. which is available at http://technet. The “Virtual Application Management with Microsoft Application Virtualization 4.5 and System Center Configuration Manager 2007 R2” white paper.microsoft.5 Sequencing Guide” white paper.microsoft.microsoft. which is available at http://technet.434 Microsoft Deployment Toolkit 2010 Update 1 Deploying Applications Using MDT 2010 and Microsoft Application Virtualization MDT 2010 can integrate with App-V version 4. which is available at http://technet. This integration allows the automated deployment of virtualized applications as an integral part of the ZTI and LTI deployment processes.com/enus/appvirtualization/cc843994. .5.microsoft.5 Infrastructure Planning and Design” white paper.aspx.com/enus/appvirtualization/cc843994. perform the following steps: • • Identify the components in App-V as described in App-V Components.aspx.aspx. Additional information is available from Microsoft Downloads at http://www.com/downloads.5 App-V allows applications to run in a virtualized application environment on the target computers. • • Microsoft Application Virtualization 4. Identify the limitations of App-V as described in App-V Limitations. To determine how App-V can help you in deploying and managing applications. The “Microsoft Application Virtualization 4.

It relies on components that can be installed on a single server in proof-of-concept installations. beginning from the center of the diagram: • App-V Management Server. Components on which App-V Management Servers rely include: • Management web service. Figure 3 provides a high-level overview of these components in an App-V installation. you can distribute components across other servers. However. App-V full infrastructure components The following list describes each component.435 Microsoft Deployment Toolkit 2010 Update 1 App-V Components App-V full infrastructure has several components. The App-V Management Server manages and streams virtual applications. Figure 3. in cases where components must be scaled or you cannot install dependencies such as IIS on the App-V Management Server. At least one instance of the Management web microsoft. The Management web service controls access to the database.com/technet/SolutionAccelerators Solution Accelerators .

000 active streaming sessions. They can potentially support approximately 10. • App-V Sequencer.0 update is available for Windows Server 2003 and for Windows XP.000 active application streams. This database can be local to the server or can be hosted on a remote database server. App-V has a dedicated packaging utility known as the App-V Sequencer. It streams applications using Real Time Streaming Protocol (RTSP) or Transport Layer Security (TLS) + RTSP (RTSPS) in branch offices where it is not feasible or desirable to install a complete App-V Management Server. IIS and Windows file servers can also be used as streaming servers. App-V Management Console. IIS and file servers are more scalable than App-V Streaming Servers. Clients still communicate with an App-V Management Server located at a central location to obtain publishing information and for reporting.0. IIS servers can stream virtual applications to clients using Hypertext Transfer Protocol (HTTP)/HTTP over Secure Sockets Layer (HTTPS).0 and requires installation of the downloads packaged with the Microsoft Help and Support article. Install the App-V Management Console on computers used for App-V management. and the service requires IIS version 6 and Microsoft . Use the App-V Management Console to manage App-V servers and virtualized applications. Configure the database that hosts the App-V database with fault tolerance and run it on a separate server from other management components. • Database. connect it by a fast network connection and performance test it to make sure that the database server will respond appropriately. Windows file servers can stream virtual application to clients using the Server Message Block (SMB) protocol. If the database will be hosted on a remote SQL Server machine. but they stream applications from the local App-V Streaming Server. install the Management web service on multiple dedicated servers to provide fault-tolerant access to the management services.com/technet/SolutionAccelerators Solution Accelerators . while typical App-V Streaming Servers support approximately 1. The App-V Streaming Server is a slim version of a full App-V Management Server that only performs application delivery. The App-V Sequencer prepares applications for use in virtual environments and separates each application into feature blocks. The App-V Management Server or App-V Streaming Server streams the sequenced application’s feature blocks to the microsoft.microsoft. All App-V management information regarding application publishing and usage tracking is stored in this database.When designing a production App-V environment. The process of packaging an application for use with the App-V infrastructure is known as sequencing.” at http://support. The console requires a connection to the Management web service to effect changes to the configuration information in the App-V data store. The App-V Management Server stores configuration and reporting information in a SQL Server database. • • App-V Streaming Server. “MMC 3.NET version 2.com/kb/907265.Using the Microsoft Deployment Toolkit: Deploying Applications with App-V 436 service is required. The App-V Management Console is based on Microsoft Management Console (MMC) version 3.

It is possible to sequence a plug-in. An App-V Terminal Services Client license is required to run virtualized applications on a terminal server. Sequencing applications is by far the most timeconsuming aspect of application virtualization. thus. App-V applications can be packaged and deployed through Terminal Services. Applications that are part of the operating system cannot be sequenced. Large applications that result in SFT files that exceed 4 GB in size after sequencing are not supported. Application compatibility. which means that applications that run as a service when the computer starts cannot be sequenced into virtual applications. which means that the total size of all files deployed to one client computer cannot exceed 1 TB.com/technet/SolutionAccelerators • • • • • Solution Accelerators . It does. It is possible to remove an application that is no longer used to free space in the cache. App-V Terminal Service Client. Application cache limit. virtualize applications that install services as dependencies. Application size limit. however. Finally. You can install the App-V Management Console and Streaming Server on 64-bit server operating systems. but these components are only supported in Windows 32-bit On Windows 64-bit (WOW64). Support for operating system–integrated applications. consider the following limitations: • Support for 64-bit architectures. It also streams applications from an App-V Management Server or Streaming Server when running in Streaming or Full Infrastructure modes (see Choose a Deployment Method). however. the sequencer and client cannot are not supported on any 64-bit (x64) platforms. • App-V Desktop Client. Applications that start as a service. The App-V Desktop Client license that comes with the Microsoft Desktop Optimization Pack (MDOP) is required to run virtual applications on desktop or portable computers and is independent of the App-V Terminal Services Client license. A 64-bit version of the client is not yet available. A typical example is Internet Explorer. the App-V Desktop Client provides the virtual environment for the sequenced application. microsoft. The client limits the total space used for virtual applications to 1 TB in size.437 Microsoft Deployment Toolkit 2010 Update 1 App-V Desktop Client. SFT files are limited to 4 GB. The client can only start applications after a user has logged on to the client computer. The App-V Desktop Client manages applications on users’ client computers. • App-V Limitations When using App-V in the scope of a larger desktop-deployment project. The current version of App-V is optimized for 32-bit (x86) platforms. App-V can. Application virtualization does not remediate compatibility problems between Windows and legacy applications. The App-V Client for Terminal Services is optimized to run in a Terminal Services environment. such as Microsoft Silverlight™.

Applications with licensing enforcement tied to machine computer. Plan the application virtualization infrastructure. determine the requirements for sequencing applications. Applications that use COM+ or COM DLL surrogate virtualization (DLLhost. App-V cannot virtualize device drivers. 3. Solution Accelerators microsoft. available at http://technet. consider whether to use System Center Configuration Manager and how to service branch offices during deployment. If an application installs a device driver.exe) cannot be virtualized. it may be possible to install the device driver locally and sequence the core application. MAPI resources—for example. In this step. they would typically not run on the same client computer. For example. Virtualized applications that use MAPI will use the MAPI interfaces in the underlying client operating system. When sequenced. Click-once updates. Also. • • • • Planning In this guide. this section briefly discusses infrastructure planning as it relates to the overall deployment project. remediate compatibility problems between two applications. the primary planning focus is on App-V client deployment and application sequencing.com/en-us/appvirtualization/cc843994. COM+ or COM dynamic link library (DLL). Determine where to store applications and prepare the network.Using the Microsoft Deployment Toolkit: Deploying Applications with App-V 438 however. Applications that use “click-once” technology for application updates should not be virtualized by using App-V.5 and System Center Configuration Manager 2007 R2” To plan application virtualization 1. profiles— are shared by all MAPI applications on a client computer rather than isolated. The App-V Sequencer packages applications for deployment as virtualized applications.com/technet/SolutionAccelerators . Plan the application App-V Sequencer environment. • Device drivers. they now can run on the same client computer at the same time. if two applications use a different Java Runtime Engine (JRE) version.aspx: • • • “App-V 4. Also. Additional guidance is available in the following white papers.5 Sequencing Guide” “Virtual Application Management with Microsoft Application Virtualization 4.microsoft. Messaging Application Programming Interface (MAPI) virtualization. 2.5 Infrastructure Planning and Design” “Microsoft Application Virtualization 4. The high-level steps for planning application virtualization as part of a desktop-deployment project are listed below. Applications that tie the license to the system’s MAC address should not be virtualized with App-V. Choose an application deployment method.

For more information. 5. number of applications. System Center Configuration Manager is