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

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

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

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

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

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

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

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

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 .

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 ............Using the Microsoft Deployment Toolkit: Contents 27 Planning Performance and Power Management...................21 Solution Accelerators microsoft...................

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

...........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 ......

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

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

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 .

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

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 .

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.

com/technet/SolutionAccelerators .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 .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.

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

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

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

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

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.

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 .

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

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

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

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

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

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

com/technet/SolutionAccelerators .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 .Using the Microsoft Deployment Toolkit: Contents 81 Rename an Application in Deployment Workbench 109 Solution Accelerators microsoft.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Using the Microsoft Deployment Toolkit: Contents 96 Enable or Disable a Package in Deployment Workbench 118 Solution Accelerators microsoft.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 .

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.

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

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

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

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 .

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..............com/technet/SolutionAccelerators .......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.

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.com/technet/SolutionAccelerators .

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

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

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

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

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

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

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

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

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

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

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

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 .......Using the Microsoft Deployment Toolkit: Contents 138 Running the Windows Deployment Wizard..203 Solution Accelerators microsoft................

......com/technet/SolutionAccelerators ...216 Solution Accelerators microsoft.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.com/technet/SolutionAccelerators .................

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

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

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.......

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

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.

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 .

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.

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

com/technet/SolutionAccelerators .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 .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 ..........

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

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 .

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.

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

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

com/technet/SolutionAccelerators .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.

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........

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

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

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

com/technet/SolutionAccelerators .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.

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

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

..Using the Microsoft Deployment Toolkit: Contents 174 Managing Computer Collections in Configuration Manager Console.....255 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 ............

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

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

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

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

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

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

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

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

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 ..

267 Solution Accelerators microsoft....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........com/technet/SolutionAccelerators ..............Using the Microsoft Deployment Toolkit: Contents 187 Preparing for UDI Deployment to Target Computers....................

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

com/technet/SolutionAccelerators .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............

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 .

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 .

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

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

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 .

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..com/technet/SolutionAccelerators ..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.

com/technet/SolutionAccelerators .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 .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 .

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

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

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 .

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.com/technet/SolutionAccelerators .

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 .

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

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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.com/technet/SolutionAccelerators .

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

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

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 .

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

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

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

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 .

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

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.

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

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

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

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

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

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

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

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

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

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

........................com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Contents 274 Managing Configuration Settings Stored in the MDT DB............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.

.......Using the Microsoft Deployment Toolkit: Contents 277 Configuring the MDT 2010 Deployment Process to Access the MDT DB.......com/technet/SolutionAccelerators ..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.Using the Microsoft Deployment Toolkit: Contents 279 Configure Access to the MDT DB by Directly Modifying the CustomSettings.com/technet/SolutionAccelerators .

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

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

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 .

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

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

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

...........................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 ......Using the Microsoft Deployment Toolkit: Contents 291 Preparing Windows Deployment Services.....................................441 Solution Accelerators microsoft............

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

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

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

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 .

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

.....................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.

.5...................................448 Solution Accelerators microsoft...............................com/technet/SolutionAccelerators ....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 .

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

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

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

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

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

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

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

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

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 .

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

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.

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

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

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.

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

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.

and deploy Windows® operating systems and applications using MDT 2010. Provides information about the task sequence steps. Table 1 lists other documents that will help you perform deployments using MDT 2010 in your organization. Windows applies to the Windows 7. 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.aspx#EFG. properties. In addition to this document. while ZTI and UDI deployments are performed using MDT 2010 and Microsoft System Center Configuration Manager 2007.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. and User Driven Installation (UDI) deployment methods. see the product home page at http://www.microsoft. ZTI and UDI deployments require System Center Configuration Manager. Table 1. Windows Vista®.com/systemcenter/essentials/en/us/default. You can use Microsoft System Center Essentials 2007 to collect inventory and perform patch management for LTI deployments. see “Detailed comparison with System Center Configuration Manager 2007” at http://technet. utilities. Use this document to help solve difficult deployment problems. Zero Touch Installation (ZTI). support files. 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.com/enus/sce/bb734815.aspx. Windows XP Professional. 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. For more information about: • • Microsoft System Center Essentials. Windows Server® 2008 R2. Differences between System Center Essentials and System Center Configuration Manager.microsoft. This document provides guidance on how to plan. and databases used in MDT 2010 deployments. build. This document covers both deployment methods and shows how to customize the deployment process for an organization. Windows XP Tablet PC Edition. Only MDT 2010 is used in LTI deployments. Note In this document.

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

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

Provides guidance on preparing Windows Deployment Services for use in initiating the LTI. 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.com/fwlink/?LinkID=132579. and applications to the target computers in your organization. Provides guidance on how to deploy applications by using MDT 2010. ZTI. how to apply configuration settings to groups of computers.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. Please provide feedback on the usefulness of this guide by filling out the survey at http://go. device drivers. and how to apply configuration settings to individual computers. Provides guidance on preparing the appropriate resources used in the MDT 2010 deployment process.com/technet/SolutionAccelerators . and UDI deployments. including creating images and configuring for integration with LTI. ZTI.com. including network shared folders and database access.microsoft. including how to add entries to and retrieve configuration settings from the MDT DB. and Microsoft Application Virtualization (App-V). Provides guidance on customizing the process for more advanced deployment scenarios. Provides guidance on how to customize the process for more advanced deployment scenarios. Solution Accelerators microsoft. including a discussion of the MDT 2010 configuration files. and UDI deployment processes. System Center Configuration Manager. including deployment of applications with the operating system image or after the image is deployed.

Windows operating system language packs. . including: • • • Windows operating system source files or images. ZTI. and server computers in the environment. which are proven and refined in a test environment. portable. Collect the files necessary to perform an MDT 2010 deployment.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. 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. The process starts with conceptual designs. Figure 1 illustrates the high-level LTI. and UDI deployment processes. and UDI deployment process is as follows: 1. Device drivers for reference and target computers. ZTI. Figure 1. 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. 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. High-level deployment process The high-level LTI. At a high level.

and the target computers. Larger organizations should use Key Management Service (KMS) or Multiple Activation Key microsoft. For more information. and task sequences to be used in deploying Windows and applications to the reference computers. see Estimating MDT 2010 Storage Requirements. with removable media. 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 .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. verify that there is sufficient bandwidth between the deployment shares. For more information. distribution points. see Using Reference Computers in MDT 2010 Deployment. 5. and provide regional distribution points. For each question. 3. use the information provided in the Overview column to help find answers based on your organization’s requirements. Table 3. Some organizations might need multiple deployment shares or distribution points for different regional offices. configuration settings. Deploy the system images to the reference computer and capture an image of the reference computer. see Using Reference Computers in MDT 2010 Deployment. 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. If you are deploying across the network. Create the system images. see Choosing a Deployment Method and Evaluating Network Requirements. These files can require many gigabytes of space. Small organizations might assign each user an individual product key. 4.com/technet/SolutionAccelerators Will you deploy across the network. 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. For more information. For more information. Deploy the captured images of the reference computers to the target computers.

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

Create a unique image for each: • Version of the Windows operating system to be deployed. • • 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. A separate image is required for each version of Windows. such as Windows 7. Solution Accelerators microsoft. and device drivers used in the Deployment Workbench. Otherwise. 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. You store these images in the MDT 2010 deployment shares created in the Deployment Workbench. 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. Free space of 1 GB is required on the drive containing the MDT 2010 program files. Each MDT 2010 deployment share as described in Estimating Storage Requirements for MDT 2010 Deployment Shares.com/technet/SolutionAccelerators . or Windows Server 2008 R2. language packs. User state migration data as described in Estimating Storage Requirements for User State Migration Data. 1 GB of free space is required on the drive containing the %TEMP% folder. Windows Server 2003. Each System Center Configuration manager distribution point as described in Estimating Storage Requirements for System Center Configuration Manager Distribution Points.5 Microsoft Deployment Toolkit 2010 Update 1 • • • Computers running MDT 2010 as described in Estimating Storage Requirements for Computers Running MDT 2010. Windows Vista.

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

Solution Accelerators microsoft. you can estimate the disk space requirements without actually performing the migration. In the event that there is insufficient disk space for the user state data and new image. • 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. 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. However. you can override this behavior with configuration settings in CustomSettings.ini. the deployment scripts attempt to store the information in a shared folder. the process attempts to store user state data on the local hard disk for the Replace Computer and Refresh Computer scenarios. complete the following tasks to estimate the user state migration storage requirements: • Run Scanstate. Create a share on a server designated during the planning process for holding the USMT store files.com/technet/SolutionAccelerators .7 Microsoft Deployment Toolkit 2010 Update 1 Configuration Manager Documentation Library. Determining the storage requirements for the user state migration data as described in Determine Storage Requirements for User State Migration Data. Providing the shared folder as an alternate storage location makes the deployment process more reliable.exe in the USMT with the /p option to estimate the size of the user state migration data. 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. By default. Determine Storage Requirements for User State Migration Data For planning purposes. determine where to store the data. 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. which is installed with System Center Configuration Manager.ini to locate the user state store folder. By using the /p option. designate a shared folder in which the deploy process can store the data.

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

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

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

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

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

and backup images. images) may be required. Higher levels of automation reduce development costs. distribution. • Applications and languages are not immediately available after image deployment is complete. 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. disk images. Storage costs include storing the distribution points. Test costs. and deploying disk images includes: • Development costs. The costs associated with building. costs increase. Large images have more updating. Network costs. 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. • Reduced image maintenance • Potential for increased effort. Test costs also include the development time required to stabilize disk images. the entire image must be redistributed. the number of computers in each deployment run. • • • As the size of image files increases. and so on. network. and storage costs associated with them. Table 5. Deployment Scenarios Solution Accelerators microsoft.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.com/technet/SolutionAccelerators . because contains fewer components. Identifying Deployment Scenarios Table 5 lists the deployment scenarios and provides a brief description of each. testing. Storage costs can be significant depending on the number of disk images. migration data. Network costs include moving disk images to distribution points and to computers. advanced scripting (though • Does not require separate not as advanced as in thin software-distribution software. maintaining. because the image complexity. creation. Storage costs. Even if only a small portion of the image is updated. The disk-imaging technologies that Microsoft provides do not support multicasting.

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

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

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

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

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

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.com/technet/SolutionAccelerators . DVD.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.

the less interaction is required during deployment. or UDI) and partially automated deployments (using LTI or UDI). Table 7 lists the advantages and disadvantages of performing fully automated deployments (using LTI. persistent connection UDI deployment Requires a high-speed.com/technet/SolutionAccelerators . 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. you must provide all the information necessary to install Windows and the applications on target computers. Table 7. when do you provide this information? The more information you provide in advance. 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. ZTI. The question is.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. 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.

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

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

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

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

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

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

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

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

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

Specify whether to capture an image Click Capture an image of this reference computer. The most common symptom of trouble is that the deployment process halts. 4. The wizard starts. 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). Solution Accelerators microsoft. The reference computer is now deployed. review them. 3. Troubleshooting Reference.45 Microsoft Deployment Toolkit 2010 Update 1 2. because the LTI process is not able to automatically log on. 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. Note Joining the reference computer to a domain causes problems when deploying the captured image of the reference computer to target computers. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. For more information about the errors or warnings.com/technet/SolutionAccelerators . 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. see the MDT 2010 document. Add the Captured Image of the Reference Computer to Deployment Workbench To deploy the captured image of the reference computer to the target computer. add the captured image to the list of operating systems in the Operating Systems node in the Deployment Workbench. 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. and provide the fully qualified Universal Naming Convention (UNC) path for the name of the captured Windows Imaging Format (WIM) image. click Finish. In the Deployment Summary dialog box. Table 11. Join a workgroup. and record any diagnostic information. and the operating system deployment starts. click Details. the Deployment Summary dialog box appears. If any errors or warnings occur. At the end of the deployment process. including the WIM file name.

specify the fully qualified path to the WIM file of the captured image of the reference computer. and the MDT DB for each deployment scenario as described in: • Prepare for the New 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. 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. • Prepare for a Refresh Computer Deployment Scenario to Target Computers Using LTI. The Import Operating System Wizard finishes. and customize the deployment process. Create additional deployment shares to help in larger deployments as described in Create a New Deployment Share in Deployment Workbench. 3. Information for Completing the Importing a Previously Captured Image of a Reference Computer On this wizard page Image Do this In Source File. Solution Accelerators microsoft. • Prepare for a Replace Computer Deployment Scenario to Target Computers Using LTI. 2. the MDT 2010 configuration files. To prepare for deployment to the target computers 1. In preparation. Preparing for LTI Deployment to Target Computers With the images of the reference computer captured. create one or more task sequences for deploying the captured images. deploy the images to the target computers. Table 12. Prepare the MDT 2010 task sequences. 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. Prepare network shares for storing migration data and MDT 2010 deployment logs as described in Preparing the MDT 2010 Migration Resources. 4. 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).com/technet/SolutionAccelerators . Optionally. ensure that the necessary deployment resources exist.

3. 4. 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. see Identifying Deployment Scenarios. There is no user migration information to save and restore and no existing file systems to preserve. 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. 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). Configure the Deployment Share Properties Windows PE x64 Settings Tab. 2. To prepare for the New Computer deployment scenario 1. 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. 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. a new installation of a Windows operating system is deployed to a new computer.47 Microsoft Deployment Toolkit 2010 Update 1 Depending on the target computers in your organization. Optionally. Configure the Deployment Share Properties Windows PE x86 Components Tab. Solution Accelerators microsoft. For more information about the MDT 2010 deployment scenarios. Prepare for the New Computer Deployment Scenario to Target Computers Using LTI In the New Computer deployment scenario. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments.com/technet/SolutionAccelerators . Table 13.

Verify the Windows PE options for each deployment share as described in: Solution Accelerators microsoft.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 48 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. re-imaged for image standardization or to address a problem. linked deployment share. 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. Table 14. 5. Update each deployment share. 2. a computer is refreshed—that is. • Prepare for a Refresh Computer Deployment Scenario to Target Computers Using LTI In the Refresh Computer deployment scenario. Optionally.com/technet/SolutionAccelerators . Generate Media Images in Deployment Workbench. Replicate Linked Deployment Shares in Deployment Workbench. You must save and restore the user migration information. To prepare for the Refresh Computer deployment scenario 1. 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. 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. 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. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. 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). 3. because the existing file systems on the target computer are not preserved.

To prepare for the Replace Computer deployment scenario 1. Generate Media Images in Deployment Workbench. Prepare for a Replace Computer Deployment Scenario to Target Computers Using LTI In the Replace Computer deployment scenario. 5. • 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. because the file systems on the new computer are formatted as part of the new installation of Windows. 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. one computer replaces another computer. the user state data is restored to the new computer. Solution Accelerators microsoft. Configure the Deployment Share Properties Windows PE x64 Components Tab. 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. Update each deployment share.com/technet/SolutionAccelerators . Configure the Deployment Share Properties Windows PE x64 Settings Tab. a new installation of Windows is deployed to a new computer. Replicate Linked Deployment Shares 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. 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. and media to create the Windows PE images used to start LTI deployment as described in: • • • Update a Deployment Share in Deployment Workbench. linked deployment share. Configuring LTI Task Sequence Steps in Deployment Workbench. Configure the Deployment Share Properties Windows PE x86 Components Tab. Then. Finally.49 Microsoft Deployment Toolkit 2010 Update 1 • • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. The existing user state migration data is saved from the original computer to a network shared folder or removable media. Use the: • Standard Client Replace Task Sequence template to save the user state migration data of the existing target computer.

Using the Microsoft Deployment Toolkit: Performing LTI Deployments 50 2. Optionally. Configure the Deployment Share Properties Windows PE x64 Components Tab. 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).com/technet/SolutionAccelerators . Prepare for an Upgrade Computer Deployment Scenario to Target Computers Using LTI In the Upgrade Computer deployment scenario. linked deployment share. 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. included in MDT 2010. 3. 6. 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. Generate Media Images in Deployment Workbench. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. 4. the existing operating system on a computer is upgraded to the newer operating system. You do not need to save 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. Table 15. Verify the Windows PE options for each deployment share as described in: • • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. 5. Replicate Linked Deployment Shares in Deployment Workbench. 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. Configure the Deployment Share Properties Windows PE x86 Components Tab. Update each deployment share.

3. Optionally. To prepare for the Upgrade Computer deployment scenario 1. Note Ensure that you provide a Windows 7 or Windows Server 2008 R2 product key when upgrading from Windows Vista or Windows Server 2008. 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. Configure the Deployment Share Properties Windows PE x86 Components Tab. 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. 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. Configure the Deployment Share Properties Windows PE x64 Components Tab. Update each deployment share.com/technet/SolutionAccelerators . and will cause the deployment process to fail with an invalid product key error. respectively. if one exists. Verify the Windows PE options for each deployment share as described in: • • • • Configure the Deployment Share Properties Windows PE x86 Settings Tab. because the existing file systems on the target computer are preserved and the new operating system upgrades the data. 2. If you do not provide the appropriate product key.51 Microsoft Deployment Toolkit 2010 Update 1 and restore the user state migration data. 4. linked deployment share. 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. 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). 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. 5. Table 16. Configure the Deployment Share Properties Windows PE x64 Settings Tab.

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

the user state migration data is restored to the target computer.com/technet/SolutionAccelerators . The Windows Deployment Wizard starts. and record any diagnostic information. At the end of the process.vbs. For more information about the errors or warnings. If any errors or warnings occur. Table 18. 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. Later in the task sequence. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. Troubleshooting Reference. Click Refresh this computer. The wizard starts. The target computers are now deployed. Solution Accelerators Do this Select the task sequence you created for the target computer deployment for the Refresh Computer deployment scenario. 3. The Windows Deployment Wizard saves the user state migration data of the existing target computer to the location you specify. click Finish. Start the Windows Deployment Wizard by connecting to the appropriate deployment share (for example. 4. In the Deployment Summary dialog box. the Deployment Summary dialog box appears. 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. click Details. and the operating system deployment starts. microsoft. 2. In the Deployment Summary dialog box.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. review them. \\servername\Distribution$\Scripts) and typing cscript litetouch. To complete the Windows Deployment Wizard 1. 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. see the MDT 2010 document.

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. 3. 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. and record any diagnostic information. and the operating system deployment starts. In the Deployment Summary dialog box. In the Deployment Summary dialog box. review them. 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. If any errors or warnings occur. 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. To deploy captured images of the reference computer 1. For more information about the errors or warnings. At the end of the process. 4. The Windows Deployment Wizard saves the user state migration data of the existing target computer to the location you specify.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 54 On this wizard page Specify where to save your data and settings. To complete the Windows Deployment Wizard Solution Accelerators microsoft. Troubleshooting Reference. Then. click Details. The target computer is now deployed. 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. 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. the Deployment Summary dialog box appears. click Finish. 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. 2. Run the wizard the first time to capture the user state migration data from the existing target computer (old computer).com/technet/SolutionAccelerators . see the MDT 2010 document.

Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. The user state migration data of the existing target computer is saved. The LTI bootable media starts Solution Accelerators microsoft. 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. 3. click Finish.com/technet/SolutionAccelerators . not as a rollback method for the target computer. the Deployment Summary dialog box appears. and the operating system deployment starts. see the MDT 2010 document. 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. Table 19. In the Location box. and then type the fully qualified path to the location in which you want to store the backup. Start the Windows Deployment Wizard by connecting to the appropriate deployment share (for example. type the fully qualified path to the location in which you want to store the user state migration data.vbs.55 Microsoft Deployment Toolkit 2010 Update 1 1. This location must be accessible to the new target computer. 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. For more information about the errors or warnings. click Details. Note This backup is for use in restoring user state migration data that might have been missed. perform a full backup using your organization’s backup software. 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. In the Deployment Summary dialog box. \\servername\Distribution$\Scripts) and typing cscript litetouch. At the end of the process. If any errors or warnings occur. The wizard starts. The Windows Deployment Wizard starts. If you want to have rollback capability for the target computer. 2. Troubleshooting Reference. review them. Click Specify a location. 4. In the Deployment Summary dialog box. and record any diagnostic information.

3. Troubleshooting Reference. For more information about the errors or warnings. click Details. Start the reference computer with the LTI bootable media you created earlier in the process or from Windows Deployment Services. and then the Windows Deployment Wizard starts. In the Deployment Summary dialog box. At the end of the process. 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. 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. the Deployment Summary dialog box appears. see the MDT 2010 document. review them. and record any diagnostic information.Using the Microsoft Deployment Toolkit: Performing LTI Deployments 56 Windows PE on the target computer and initiates LTI deployment. click Finish. 4. user state is upgrade along with the operating system. For the Upgrade Computer deployment scenario. The wizard starts. the captured image of the reference computer is deployed to the target computer. At the end of the process.com/technet/SolutionAccelerators . In the Deployment Summary dialog box. If any errors or warnings occur. Table 20. To complete the Windows Deployment Wizard Solution Accelerators microsoft. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. 2. To deploy the captured image of the reference computer 1. Windows PE starts. Click the Specify a location option and type the location of the saved user state migration data in the Location box. and the operating system deployment starts. 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.

4. Complete the Windows Deployment Wizard as described in Running the Windows Deployment Wizard. Start the Windows Deployment Wizard by connecting to the appropriate deployment share (for example. the Deployment Summary dialog box appears. click Details. In the Deployment Summary dialog box.57 Microsoft Deployment Toolkit 2010 Update 1 1.vbs. review them. and record any diagnostic information. 3. \\server_name\Distribution$\Scripts) and typing cscript litetouch. The Windows Deployment Wizard starts. Troubleshooting Reference. At the end of the process. Click Upgrade this computer. click Finish. Solution Accelerators microsoft. In the Deployment Summary dialog box. 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. 2. The wizard starts.com/technet/SolutionAccelerators . 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. and the operating system deployment starts. If any errors or warnings occur. Table 21. see the MDT 2010 document. For more information about the errors or warnings.

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

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

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. the password can be configured in the Windows Deployment Wizard. Note By default. If the check box is: • Selected. which is usually the reference computer. an image is not capture or the imagecapture information must be set in the MDT 2010 configuration file or database. the password must be set in the MDT 2010 configuration file or database. and then click Next. the product key can be configured in the Windows Deployment Wizard. this check box is cleared. Allow Image Capture Allow Admin Password Select or clear the Ask user to set the local Administrator Password check box based on requirements. this check box is selected. and then click Next. If the check box is: • Selected.com/technet/SolutionAccelerators Solution Accelerators . • Cleared. the path for storing the image and the image name can be configured in the Windows Deployment Wizard. This check box configures the Windows Deployment Wizard to allow the user to optionally capture an image of the target computer. microsoft. Descriptive Name In Deployment share description. Select or clear the Ask if an image should be captured check box based on requirements. Note By default. and then click Next. type description (where description is a descriptive name that for the deployment share specified on previous wizard pages). • Cleared.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. Allow Product Key Select or clear the Ask user for a product key check box based on your requirements. If the check box is: • Selected. 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. and then click Next.

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

the Open Deployment Share Wizard upgrades the deployment share. The deployment share is added to the details pane in the Deployment Workbench. Start the wizard by Solution Accelerators microsoft. 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 Deployment Shares Not Already Listed in Deployment Workbench Upgrade deployment shares not listed in the Deployment Workbench using the Open Deployment Share Wizard. Select the Upgrade the content of the deployment share (if required) check box. • Cleared. an MDT 2008 deployment share. and the Upgrade the content of the deployment share (if required) check box is selected. and then click Next. Upgrading an existing deployment share that is listed in the Deployment Workbench as described in Upgrade Deployment Shares Already Listed in Deployment Workbench. 3. Tip You can click Save Output to save the output of the wizard to a file.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). Summary Confirmation Review the information in the Details box. 2. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.com/technet/SolutionAccelerators . Click Finish. After the wizard finishes. Click Next. the existing deployment share is upgraded (if required). the Open Deployment Share Wizard will not upgrade the deployment share. or a pre-release version of MDT 2010 deployment share to MDT 2010. Upgrade an Existing Deployment Share in Deployment Workbench MDT 2010 can upgrade an existing BDD 2007 deployment share. If the check box is: • Selected. 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. click Browse to find the local or network shared folder. 4. clicking Open Deployment Share.com/technet/SolutionAccelerators . Complete the Open Deployment Share wizard using the information in Table 24. and then point to All Programs. In Deployment share path. Clicking the deployment share. To upgrade deployment shares that are not already listed in the Deployment Workbench. The Open Deployment Share Wizard starts. click Open Deployment Share. In the Deployment Workbench console tree. in the Actions pane. Tip Click Save Output to save the output of the wizard to a file. Clicking the deployment share. Information for Completing the Open Deployment Share Wizard On this wizard page Path Do this 1. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. and then click Deployment Workbench. clicking Open Deployment Share. Click Start. the existing deployment share is upgraded (if required). Click Finish. from the Actions menu. Point to Microsoft Deployment Toolkit. and the Upgrade the content of the deployment share (if required) check box is selected. and then. go to Deployment Workbench/Deployment Shares.63 Microsoft Deployment Toolkit 2010 Update 1 • • • Right-clicking the deployment share. and then. 2. Table 24. Select the Upgrade the content of the deployment share (if required) check box. and then click Next. In the Actions pane. After the wizard finishes. and then click Next. perform the following steps: 1. Note Alternatively. type share_path (where share_path is the fully qualified path to the existing deployment share). Solution Accelerators microsoft. Summary Confirmation Review the information in the Details box. 2. and then clicking Open Deployment Share. 3.

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

On the General tab. 4. 5. click Properties. 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. Configure the settings on the Windows PE x64 Settings tab as described in Configure the Deployment Share Properties Windows PE x64 Settings 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. 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. Configure the settings on the Windows PE x86 Components tab as described in Configure the Deployment Share Properties Windows PE x86 Components Tab. Solution Accelerators microsoft. and then click Deployment Workbench.com/technet/SolutionAccelerators . and then point to All Programs. To configure the General tab 1. configure the settings listed in Table 26 based on the requirements of your organization. Configure the settings on the Windows PE x64 Components tab as described in Configure the Deployment Share Properties Windows PE x64 Components Tab. 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). Click Start. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). In the Actions pane. go to Deployment Workbench/Deployment Shares. and then click OK. click deployment_share (where deployment_share is the name of the deployment share). In the Deployment Workbench console tree. Point to Microsoft Deployment Toolkit. 2. 3. Configure the settings on the Windows PE x86 Settings tab as described in Configure the Deployment Share Properties Windows PE x86 Settings Tab. In the details pane.

• An existing network shared folder. Note If you created the deployment share from a local path. the local path rather than the UNC path is displayed in the details pane of the Deployment Workbench. If you created the deployment share from: • A local path. Comments Network (UNC) path Local path Contains the fully qualified path to the local folder in which the deployment share was created. see Enable Windows Deployment Services Multicast Deployment for microsoft. 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. 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. 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. Select to configure Windows Deployment Services to enable multicast deployment of images generated in this deployment share. Select to configure the Update Deployment Share Wizard to create WIM files and bootable media for 64-bit target computers. 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. this value is displayed in the details pane of the Deployment Workbench. The default value is MDT Deployment Share. If you select this check box. then this text box contains the local path used in the creation process. Provides information about the deployment share. you must provide values for the Network (UNC) path and Local path boxes. For more information about enabling multicastbased deployments. Text box that contains fully qualified UNC path to the deployment share.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 66 Table 26. Note If the deployment share was created from an existing network shared folder. then this text box is empty.com/technet/SolutionAccelerators Solution Accelerators .

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

click Properties.wim file with the image description specified in the Image description text box. • Cleared. click deployment_share (where deployment_share is the name of the deployment share). In the details pane. and then click OK. the Update Deployment Share Wizard creates the LiteTouchPE_x86. configure the settings listed in Table 28 based on the requirements of your organization. 5. the Update Deployment Share Wizard creates the ISO file with the name microsoft. 4. Select to configure the Update Deployment Share Wizard to create a bootable Windows PE ISO file that includes the LTI deployment scripts. go to Deployment Workbench/Deployment Shares. 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. Table 28. The default value is Lite Touch Windows PE (x86). 2. If the check box is: • Selected. In the Deployment Workbench console tree.com/technet/SolutionAccelerators Image description Generate a Lite Touch bootable ISO image Solution Accelerators . To configure the Windows PE x86 Settings tab 1. Click Start. and then click Deployment Workbench. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). and then point to All Programs. If the check box is: • Selected. Point to Microsoft Deployment Toolkit. 3. 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.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. On the Windows PE x86 Settings tab. In the Actions pane.

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

In the details pane. Configures the size of the scratch space in megabytes. or 512 MB. Point to Microsoft Deployment Toolkit. The default value is 32. click Properties.bmp. Contains the fully qualified path to a folder structure to be included in the Windows PE images. 3. go to Deployment Workbench/Deployment Shares. you can select a value of 32. 64. configure the settings listed in Table 29 based on the requirements of your organization. 4. In the Deployment Workbench console tree. 256. Table 29. 5. To configure the Windows PE x86 Components tab 1. and then click OK.com/technet/SolutionAccelerators . and then point to All Programs. 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. 2. 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). Custom background bitmap file Contains the fully qualified path to the BMP file that is to be used as the custom background bitmap. On the Windows PE x86 Components tab. Extra directories to add Scratch space size The deployment share configuration settings are saved. 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. The default value for this text box is %INSTALLDIR%\Samples\Background. 128. The default value for the text box is empty. Click Start. In the Actions pane. and then click Deployment Workbench.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.

see Manage Selection Profiles. the Update Deployment Share Wizard will not include the font in the Windows PE images.com/technet/SolutionAccelerators Include all drivers from the selected driver group Include only drivers of the following types Solution Accelerators . If the check box is: • Selected. the ADO components are added to the Windows PE images. If the check box for a corresponding font is: • Selected. Note Adding fonts to Windows PE boot images increases the size of the images. Select to configure the Update Deployment Share Wizard to include all the device drivers in the selection profile specified in the Selection profile box. such as the MDT DB. • Cleared. 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. These components are necessary for accessing Microsoft SQL Server® databases. 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. Add fonts only if necessary. 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.71 Microsoft Deployment Toolkit 2010 Update 1 Setting Description Windows PE images. The default value is All Drivers and Packages. the ADO components are not added to the Windows PE images. Korean. • Cleared. For more information about selection profiles. or Chinese. the Update Deployment Share Wizard includes the font in the Windows PE images.

• Cleared. 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. the Update Deployment Share Wizard includes all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. 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. 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. 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. 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. If the check box is: • Selected. 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. • Cleared. If the check box is: • Selected. • Cleared.com/technet/SolutionAccelerators Solution Accelerators .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. 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 microsoft.

configure the settings listed in Table 30 based on the requirements of your organization.com/technet/SolutionAccelerators . The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). 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. 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. The deployment share configuration settings are saved. Solution Accelerators microsoft. Note This check box is enabled only if you select Include only drivers of the following types. 2. and then click OK. 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. Note This check box is enabled only if you select Include only drivers of the following types. and then point to All Programs. In the details pane. 3. • Cleared. To configure the Windows PE x64 Settings tab 1. Point to Microsoft Deployment Toolkit. 4. If the check box is: • Selected. go to Deployment Workbench/Deployment Shares. and then click Deployment Workbench. 5.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. Click Start. click Properties. click deployment_share (where deployment_share is the name of the deployment share). and the deployment share appears in the details pane of the Deployment Workbench. In the Actions pane. 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. On the Windows PE x64 Settings tab.

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

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

In the Deployment Workbench console tree. the ADO components are not added to the Windows PE images. 4.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 76 To configure the Windows PE x64 Components tab 1. Point to Microsoft Deployment Toolkit. and then click Deployment Workbench. 5. or Chinese. On the Windows PE x86 Components tab. The deployment_share Properties dialog box opens (where deployment_share is the name of the deployment share you want to configure). go to Deployment Workbench/Deployment Shares. These components are necessary for accessing SQL Server databases. 3. In the Actions pane. such as the MDT DB. configure the settings listed in Table 31 based on the requirements of your organization. the Update Deployment Share Wizard microsoft.com/technet/SolutionAccelerators Optional Fonts Solution Accelerators . the ADO components are added to the Windows PE images. Korean. Table 31. • Cleared. If the check box for a corresponding font is: • Selected. In the details pane. the Update Deployment Share Wizard includes the font in the Windows PE images. Click Start. 2. If this check box is: • Selected. 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. and then point to All Programs. and then click OK. 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. click Properties. • Cleared. click deployment_share (where deployment_share is the name of the deployment share).

see Manage Selection Profiles. • Cleared. Note Adding fonts to Windows PE boot images increases the size of the images. If the check box is: • Selected. Selection profile Selects the device drivers and packages to be included in the Windows PE images based on the selection profile you choose. the Update Deployment Share Wizard includes all network drivers in the selection profile specified in the Selection profile box in the Windows PE images. Add fonts only if necessary. Note This check box is enabled only if you select Include only drivers of the following types.com/technet/SolutionAccelerators .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. 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 all the device drivers in the selection profile specified in the Selection profile box. If the check box is: microsoft. 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. The default value is All Drivers and Packages.

Using the Microsoft Deployment Toolkit: Managing LTI Deployments 78 Setting Description • Selected. Solution Accelerators microsoft.com/technet/SolutionAccelerators . 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 includes all video 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. Note This check box is enabled only if you select Include only drivers of the following types. • Cleared. 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. The deployment share configuration settings are saved. Note This check box is enabled only if you select include only drivers of the following types. • Cleared. If the check box is: • Selected. 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. 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. • Cleared. Note This check box is enabled only if you select include only drivers of the following types. If the check box is: • Selected. 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. 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 video drivers in the selection profile specified in the Selection profile box in the Windows PE images.

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

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

iso and LiteTouchPE_x64.iso (for 32-bit target computers) or LiteTouchPE_x64. 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.wim files (for 32-bit target computers) or LiteTouchPE_x64. Input the following commands.iso (for 64-bit target computers) to the device by performing one of the following tasks: • Burn the ISO file to a CD.exe. Copy the contents of LiteTouchPE_x86.81 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this Click Close. To create a bootable UFD 1. and then copy its contents to the device using the command: microsoft. 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. 2. 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. The Deployment Workbench starts updating the deployment share and creates the LiteTouchPE_x86. create a bootable device.iso and LiteTouchPE_x86. Note The target computer must support booting from the device to use this method of starting target computers. Note Optionally. such as a UFD or USB hard disk.com/technet/SolutionAccelerators Solution Accelerators . Run Diskpart. On a computer running Windows Vista or a later operating system.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. 3. insert the UFD or USB hard disk. and type the command list disk to determine the disk number associated with the device.

or equivalent media source. Table 33.* /s /e /f where d is the driver letter of the CD and e is the drive letter of the device. • Alternatively. Deleting an operating system as described in Delete an Operating System from the Deployment Workbench. and then copy its contents to the device using the command: xcopy <d>:\*. Import an Operating System into Deployment Workbench You can import operating systems into the Deployment Workbench using the options listed in Table 33. Copying an operating system as described in Copy an Operating System in the Deployment Workbench. such as a DVD.* /s /e /f where d is the driver letter of the CD and e is the drive letter of the device. Configure the operating systems in the Deployment Workbench by: • • • • • • • Importing an operating system as described in Import an Operating System into the Deployment Workbench. A WIM image that was previously captured for microsoft. 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.* <e>:\*.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 82 xcopy <d>:\*. 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. 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.com/technet/SolutionAccelerators . mount the ISO file using a virtual CD program. Viewing an operating system’s properties as described in View Operating System Properties in the Deployment Workbench. Moving an operating system as described in Move an Operating System in the Deployment Workbench. CD.* <e>:\*. Managing folders for operating systems as described in Manage Folders for Operating Systems in the Deployment Workbench.

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

Summary Confirmation Click Finish. 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. Information for Completing the Import Operating System Wizard On this wizard page OS Type Source Do this Click Full set of source files. click Browse to find the source folder. Complete the Import Operating System Wizard using the information in Table 34. and then click Next.com/technet/SolutionAccelerators . Click Start. Table 34. Point to Microsoft Deployment Toolkit. In Source directory. 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. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. The operating system is added to the list of operating systems in the details pane of the Deployment Workbench. and then click Next. and then click Deployment Workbench. type destination_folder (where destination_folder is the name of the folder in the deployment share that will contain the operating system source files). Import the operating system using the Import Operating System Wizard in the Deployment Workbench. To import an operating system from a previously captured image of a reference computer 1. Tip Click Save Output to save the output of the wizard to a file. The Import Operating System Wizard starts. 4.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). click Import Operating System. Note Alternatively. The Import Operating System Wizard finishes. Click Next. 3. and then point to All Programs. and then click Next. In the Actions pane. Solution Accelerators microsoft.

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.com/technet/SolutionAccelerators . 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). • Copy Windows XP or Windows Server 2003 Sysprep files from the specified path. Setup Select one of the following options based on your requirements. Complete the Import Operating System Wizard using the information in Table 35.CAB files required to install the image specified. type source_file (where source_file is the fully qualified path to the WIM image file containing the operating system source files). In Setup source directory. The Import Operating System Wizard starts. In the Actions pane. 3. and then click Next. Table 35. In the Deployment Workbench console tree. Information for Completing the Import Operating System Wizard On this wizard page OS Type Source Do this Click Custom image file. • Copy Windows Vista or Windows Server 2008 setup files from the specified path. click Import Operating System. Solution Accelerators microsoft. and then click Next. Note Alternatively. type or click Browse to find the folder containing the Setup files. and then click Next: • Setup and Sysprep files are not needed. 4. click Browse to find the source WIM image. 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. 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. Click Browse to find the folder containing the Sysprep files. In Source file.

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 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. The Import Operating System Wizard finishes. new_image_name is the new image name.wim. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. go to Deployment Workbench/Deployment Shares/deployment_share/Operating Systems Solution Accelerators microsoft. and then click Next. Summary Confirmation Click Finish. Point to Microsoft Deployment Toolkit. the wizard fails with an error similar to the following: Setup failed applying image F:\Deploy\Operating Systems\W2K8R2RTM\W2K8R2RTM. and then click Deployment Workbench. The operating system is added to the list of operating systems in the details pane of the Deployment Workbench. Click Start. Destination In Destination directory name. rc = 31. rc = 31 ZTI ERROR – Non-zero return code by LTIApply. To resolve this issue. To import an operating system from an existing image in Windows Deployment Services 1. In the Deployment Workbench console tree. Import the operating system using the Import Operating System Wizard in the Deployment Workbench. 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. wim_file is the name of the WIM file. If you attempt to import a custom image that does not have an Edition ID. 2. Click Next.com/technet/SolutionAccelerators . and then point to All Programs.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. Tip Click Save Output to save the output of the wizard to a 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. The Import Operating System Wizard finishes. Information for Completing the Import Operating System Wizard On this wizard page OS Type WDS Server Do this Click Custom image file. and then click Next. In the Actions pane. Note The configuration settings on the General tab are populated when you import the operating system. Tip Click Save Output to save the output of the wizard to a file.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). Table 36. Table 37 lists the configuration settings on the General tab of the operating system Properties dialog box and provides a description of each setting. The Import Operating System Wizard starts. 3. Summary Confirmation Click Finish. but the image is now available to LTI. In Server name. Click Next.com/technet/SolutionAccelerators Solution Accelerators . or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. 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. Complete the Import Operating System Wizard using the information in Table 36. The operating system is added to the list of operating systems in the details pane but is not is copied to the deployment share. and then click Next. click Import Operating System. type server_name (where server_name is the name of the Windows Deployment Services server that contains the existing WIM images). The Deployment Workbench leaves the operating system image on the Windows Deployment Services server. 4. Table 37. Windows 7 ENTERPRISE in microsoft. and only the Operating system name can be modified. No other settings can be modified.

en-us.com/technet/SolutionAccelerators . Contains the processor architecture of the operating system—for example. Contains the path to the operating system relative to the root of the deployment share. Windows IBS. x86. 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. Contains the languages included in the operating system—for example. Contains the path and file name of the operating system relative to the root of the deployment share. which indicates whether the operating system includes the files necessary to perform setup. Contains the HAL type for the image—for example. 7921 indicates 7.921 GB. or 7. Contains a numeric value that indicates the image index for the image—for example. Includes the image name—for example.wim. Windows 7 ENTERPRISE. Contains the type of operating system—for example. Contains True or False.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. Solution Accelerators microsoft. acpiapic.921 MB. Contains the size of the image in megabytes—for example. 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. Contains the description of the operating system —for example. 1. Windows 7 ENTERPRISE.

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.com/technet/SolutionAccelerators . Viewing and configuring an application as described in View and Configure an Application in Deployment Workbench. Configure the applications in the Deployment Workbench by: • • • • • • • • Creating a new application as described in Create a New Application in Deployment Workbench. For more information on: • • Managing folders. Copying an application as described in Copy an Application in Deployment Workbench. Solution Accelerators microsoft. Deleting an application as described in Delete an Application from Deployment Workbench. Renaming an application as described in Rename an Application in Deployment Workbench. 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. Managing folders for applications as described in Manage Folders for Applications in Deployment Workbench. Enabling or disabling an application as described in Enable or Disable an Application in Deployment Workbench. Selection profiles. see Manage Selection Profiles. see Manage Folders in Deployment Workbench. The Delete Selected Items Wizard allows deletion of individual operating system files or entire folder structures. 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.

and the deployment process installs the application from the deployment share.com/technet/SolutionAccelerators . You import operating systems into the Deployment Workbench using the New Application Wizard. click the Applications node or a folder beneath the Applications node. click the Applications node or a folder beneath the Applications node. in the Actions pane. from the Action menu. the application files are copied to the deployment share. but the bundle itself does not install anything. Then. When you select this option. Then. The application source files are available during installation of the operating system build or to run a command that requires no application source files. no application source files are copied to the deployment share. 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. Customizing application installation as described in Customize Application Installation in Task Sequences. • • You can create a new application in the Deployment Workbench for: Solution Accelerators microsoft. click New Application. Then. click the Applications node or a folder beneath the Applications node. 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. In the Deployment Workbench console tree.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. click New Application. In the Deployment Workbench console tree. A list of applications that you must install in a particular order. the deployment process installs the application from another location on the network. When you select this option. 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. Table 38. Configuring the computer to restart as described in Configure the Computer to Restart After Application Installation. click New Application. Instead. This list is specified as dependencies for the application bundle.

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

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

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. 5. Table 40. 4. In Language. type command_line (where command_line is the command line to be run to start the installation of the application. In Application Name. In the Deployment Workbench console tree. 2. 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). type version (where version is the version of the application). Click Start. type language (where language is the language of the application). click New Application. Complete the New Application Wizard using the information in Table 40. 1. In Working directory. Create a new application using the New Application Wizard in the Deployment Workbench. and then point to All Programs.com/technet/SolutionAccelerators Command Details Solution Accelerators . The New Application Wizard starts. 2. 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 publisher_name (where publisher_name is the name of the application’s publisher). Click Next.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. In Command line. 2. 4. and then click Deployment Workbench. In Version. To create a new application that is deployed from a network shared folder other than the deployment share 1. 3. In Publisher. and then click Next. type application_name (where application_name is the descriptive name of the application). including any command-line parameters). In the Actions pane. Point to Microsoft Deployment Toolkit. 1. 3. microsoft. The New Application Wizard does not copy the source files for this type of application.

In the Deployment Workbench console tree. In Language. The New Application Wizard finishes. 2. type publisher_name (where publisher_name is the name of the application’s publisher). In Publisher. Create a new application using the New Application Wizard in the Deployment Workbench. 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. Click Next. In Version. Click Next. and then click Deployment Workbench. In Application Name.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 94 On this wizard page Summary Confirmation Do this 3. 1. Click Start. Click Finish. Complete the New Application Wizard by using the information in Table 41. and then point to All Programs. 4.com/technet/SolutionAccelerators Solution Accelerators . or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Tip Click Save Output to save the output of the wizard to a file. and then click Next. The New Application Wizard does not copy source files to the deployment share. Table 41. Information for Completing the New Application Wizard On this wizard page Application Type Details Do this Click Application bundle. 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. 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). 2. Point to Microsoft Deployment Toolkit. 4. type application_name (where application_name is the descriptive name of the application). 3. type version (where version is the version of the application). type language (where language microsoft. 3. click New Application. In the Actions pane. The New Application Wizard starts.

Point to Microsoft Deployment Toolkit. 2. Click Next. and then click Deployment Workbench. 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. Configure the Application Properties General Tab The application properties stored on the General tab are mostly configured when the New Application Wizard runs. The New Application Wizard finishes. 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).95 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this is the language of the application). Configure properties on the Dependencies tab as described in Configure the Application Properties on the Dependencies Tab. To configure the General tab for application properties 1. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Click Finish. Summary Confirmation Click Next. and then point to All Programs. Click Start. Configure properties on the Details tab as described in Configure the Application Properties on the Details Tab. 5. In the Deployment Workbench console tree. Tip Click Save Output to save the output of the wizard to a file. The application is added to the list of operating systems in the details pane of the Deployment Workbench. 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. Solution Accelerators microsoft.com/technet/SolutionAccelerators . 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).

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

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

and other options listed on this tab. a command line. 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.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. or quiet. Select to configure the MDT 2010 deployment process to restart the target computer after installing this application. • Cleared. installation of the application. and the modifications are displayed in the details pane of the Deployment Workbench. If the check box is: • Selected. Configures the registry subkey HKEY_LOCAL_MACHINE\Software\Microsoft\Wind ows\CurrentVersion\Uninstall. the target computer restarts after installing the application. This text box is enabled only when you select Standard application. the target computer will not restart after installing the application. it assumes that the application is already installed and skips the installation of the application and any dependencies. The other available option is Application bundle. This text box is enabled only when you select the Standard application option. Select to configure the application to be a standard application that has source files. Note This check box is cleared by default. This can run only on the specified client platforms The application configuration settings are saved.com/technet/SolutionAccelerators . Solution Accelerators microsoft. The other available option is Standard application. The other available option is This can run on any platform. 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. Configures the working directory of the application and is enabled only when you select Standard application. The other available option is This can run only on the specified client platforms. Configures the command line to run for performing an unattended. If MDT 2010 detects the presence of the subkey.

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

Note By default. Table 45. 2007 Office system Setup installs the same language as the target operating system. 5.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 100 Action Down Description Moves an application dependency lower in the sequence of installed dependencies. The application configuration settings are saved. Solution Accelerators microsoft. Use to select each language included in the source image. 3. The application_name Properties dialog box opens (where application_name is the name of the application to configure). 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. Click Start. In the Deployment Workbench console tree. click application_name (where application_name is the name of the application to configure). Note Application dependencies are installed from the top of the list to the bottom. and then point to All Programs.com/technet/SolutionAccelerators . and then click Deployment Workbench. 4. and then click OK. 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). Point to Microsoft Deployment Toolkit. In the details pane. 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). 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. 2. In the Actions pane. click Properties. and the modifications are displayed in the details pane of the Deployment Workbench. To configure the Office Products tab for application properties 1. configure the settings listed in Table 45 based on the requirements of your organization. Use these check boxes to force the installation of specific language packs. On the Office Products tab.

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

xml file is configured to prevent a restart of the target computer during 2007 Office system Setup. • Cleared. Click to modify the contents of the Config.com/technet/SolutionAccelerators .xml file is configured to copy the LIS cache during 2007 Office system Setup but not install 2007 Office system products. Add Edit Config. 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 LIS cache is copied and 2007 Office system products are installed during 2007 Office system Setup.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. 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.xml for 2007 Office system Setup to prevent restarting the target computer during the setup process. Always suppress reboot Select to determine whether the Deployment Workbench configures Config.xml file that the Deployment Workbench generates. 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. Solution Accelerators microsoft. the Config. the Config. • Cleared. If the check box is: • Selected.xml The application configuration settings are saved. Click to add 2007 Office system language packs. the target computer can be restarted during 2007 Office system Setup. If the check box is: • Selected.

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. 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.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. For more information on: • • Managing folders. MDT 2010 must control restarts. For more information on enabling or disabling applications in the Deployment Workbench. Doing so allows the application to be installed during the task sequence but prevents the application from appearing in the list of available applications. Selecting this check box causes the Windows Deployment Wizard to restart the target computer after installing the application. For example. CAUTION Do not allow the application to restart the target computer. However. see Manage Selection Profiles. see Configure the Application Properties General Tab. as described in Configure the Application Properties General Tab. see Manage Folders in Deployment Workbench.com/technet/SolutionAccelerators . disable the application. To prevent the 2007 Office system from restarting the computer. Tip To configure an application so that it can only be installed during a task sequence step. The Delete Selected Items Wizard allows deletion of individual applications or entire folder structures. add the property Solution Accelerators microsoft. 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. Selection profiles. the Deployment Workbench does not enforce this recommendation. 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. Note You should not delete an application when other applications are dependent on it. and then continue with the next step in the task sequence. use the command REBOOT=REALLYSUPPRESS to prevent some Windows Installer–based applications from restarting. or the task sequence will fail.

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

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

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

you can use the templates without any modification to the task sequence. • • MDT 2010 includes task sequence templates that you can use for common deployment scenarios. 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. microsoft. click New Task Sequence. click New Task Sequence. click the Task Sequences node or a folder beneath the Task Sequences node. Creates the default task sequence for deploying operating system images to server computers. from the Action menu. Table 54 lists the task sequence templates in MDT 2010. Creates the default task sequence for deploying operating system images to client computers. backs up the user state. In the console tree. and then click New Task Sequence. Backs up the system entirely. and then.com/technet/SolutionAccelerators Solution Accelerators . 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 many instances. Start the New task Sequence Wizard using one of the following methods: • In the console tree. including desktop and portable computers. in the Actions pane. you can modify task sequences created from the templates to meet the requirements of your organization. Creates a customized task sequence that does not install an operating system. Table 54. click the Task Sequences node or a folder beneath the Task Sequences node. In the console tree. Modifying the unattended setup answer file for a task sequence as described in Modify the Unattended Setup Answer File Associated with the Task Sequence. However. and wipes the disk. click the Task Sequences node or a folder beneath the Task Sequences node. and then. • Create a New Task Sequence in Deployment Workbench Using the New Task Sequence Wizard in the Deployment Workbench to create new task sequences.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.

and Label is a descriptive label that identifies the customizations. you cannot change a task sequence’s ID. 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 the Deployment Workbench console tree. Before creating task sequences. create a naming scheme to use in creating task sequence IDs that will provide meaningful information about each task sequence. type task_sequence_id (where task_sequence_id is a unique identifier for the task sequence you are creating). SP2). Click Start. To create a new task sequence 1. Standard. where Version is the operating system version (win2003. The New Task Sequence Wizard starts. Tip Although you can change a task sequence’s name and comments later. In Task sequence comments. 3. In Task sequence name. In the Actions pane. Solution Accelerators microsoft. 3. type task_sequence_name (where task_sequence_name is a descriptive name for the task sequence you are creating). In Task sequence ID. win2007). 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). 2. Complete the New Task Sequence Wizard using the information in Table 55. 4. and then click Deployment Workbench. 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. click New Task Sequence. and then point to All Programs. Level is the service pack level (SP1. Point to Microsoft Deployment Toolkit.com/technet/SolutionAccelerators . Table 55. the task sequence will not finish successfully. Although you can select the Litetouch OEM Task Sequence template from other deployment shares. Edition is the operating system edition (Enterprise. 2. Ultimate). type task_sequence_comment (where task_sequence_comment is text that describes the purpose or usage of the task sequence).

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

Admin Password In Administrator Password and Please confirm Administrator Password. Click Start. type password (where password is the password to be assigned to the built-in Administrator account on the reference or target computer). 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). To modify existing task sequence properties on the General tab 1. 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. type home_url (where home_url is the Uniform Resource Locator [URL] of the website to be the default site when starting Internet Explorer). Summary Confirmation The New Task Sequence Wizard finishes. 4. Configure properties on the OS Info tab as described in Configure the Task Sequence Properties OS Info Tab. and then click Deployment Workbench. 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. Click Next. The package is added to the list of packages in the details pane of the Deployment Workbench.com/technet/SolutionAccelerators . and then point to All Programs. Configure properties on the Task Sequence tab as described in Configure the Task Sequence Properties Task Sequence Tab.125 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this organization). and then click Next. Solution Accelerators microsoft. Click Finish. 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. 3. Point to Microsoft Deployment Toolkit.

If the check box is: • Selected. In the Deployment Workbench console tree. In the Actions pane. 4. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure).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 . 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. the Windows Deployment Wizard will microsoft. 5. Note The information in this text box is automatically generated by Deployment Workbench and cannot be modified. and then click OK. Select to control when this task sequence appears in the Windows Deployment Wizard. On the General tab. Select to configure the task sequence to run on any supported 32-bit or 64-bit Windows operating system. Comments Task sequence version Provides information about the task sequence. 3. You can type any version number that is appropriate for your organization’s versioning standards. click Properties. The other available option is This can run only on the specified client platforms. Task sequence name Contains the name of the task sequence displayed in the Deployment Workbench and the Windows Deployment Wizard. configure the settings listed in Table 56 based on the requirements of your organization. Select to configure the task sequence to run on any supported 32-bit or 64-bit Windows operating system.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 126 2. Contains the version number of the task sequence. In the details pane. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). The other available option is This can run only any platform. 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).

127 Microsoft Deployment Toolkit 2010 Update 1 Setting Description not display this task sequence. 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. • Cleared. 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. The task sequence configuration settings are saved. However. Configure the Task Sequence Steps and Step Sequence The Task Sequence tab contains a hierarchical representation of the task sequence steps and their sequence. • Cleared. and the modifications are displayed in the details pane of the Deployment Workbench. You can organize one or more task sequence steps by creating a group. If the check box is: • Selected. 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). Configure step options as described in Configure the Task Sequence Step Options. Enable this task sequence Select to control when this task sequence is available to other wizards and dialog boxes in the Deployment Workbench. the Windows Deployment Wizard displays this task sequence.com/technet/SolutionAccelerators . other wizards and dialog boxes in the Deployment Workbench cannot select this task sequence. other wizards and dialog boxes in the Deployment Workbench can select this task sequence. 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. You use task sequence step groups to control the processing of one or more task sequence steps as a unit. 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 organize multiple groups and task sequence steps to create a hierarchy of groups and task sequence steps.

For more information about each of the task sequence step types listed in Table 57. Toolkit Reference. 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. Select to add a task sequence step group or step to the task sequence. If another task sequence group immediately precedes the group.com/technet/SolutionAccelerators . Select to remove the currently highlighted task sequence step or group.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 128 • Add. Select to configure a task sequence step to be processed earlier in the deployment process. Note If you move the first task sequence step in a task sequence group up. see the corresponding section in the MDT 2010 document. the task sequence step will become the last step in the preceding group. Table 57. The move is reflected in the task sequence hierarchy. 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. you also remove all the task sequence steps in that group. Important If you remove a task sequence group. the task sequence step will be performed before the entire group and will be removed from the group. • Up. Solution Accelerators microsoft.

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

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

An individual task sequence step affect only that step. that condition affects all the task sequence steps within the group.131 Microsoft Deployment Toolkit 2010 Update 1 • • A task sequence group affect all the steps with the group. Success codes Solution Accelerators microsoft. On the Task Sequence tab. the task sequence group or step runs during the task sequence. 3. 7. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). and then point to All Programs. 2. In the details pane. • Cleared. Point to Microsoft Deployment Toolkit.com/technet/SolutionAccelerators . For example. 4. To modify existing task sequence group and individual step options 1. and then click Deployment Workbench. On the Options tab. click the Options tab. In the Actions pane. 6. Contains the list of numeric codes that indicate whether the task sequence step finished successfully. if you configure a condition for a task sequence group. Table 59. 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 Deployment Workbench console tree. configure the settings listed in Table 59 based on the requirements of your organization. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). the task sequence group or step is not run during the task sequence. in the task sequence hierarchy. On the Task Sequence tab. and then click OK. configure the task sequence group or individual step sequences based on the requirements of your organization. Note Success codes are not available in task sequence step groups. If the check box is: • Selected. Click Start. click Properties. and then click OK. 5. 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 continues if the group or step encounters an error. and then click Deployment Workbench. Add criteria for determining when the group of tasks should (or should not) run. Note Any conditions configured for a group affect all the tasks within a group. Contains any conditional criteria for running this step. If the check box is: • Selected. • A Windows Management Instrumentation (WMI) Query Language (WQL) query within a WMI namespace. The criteria can be based on: • An IF statement. 2. the step runs. Point to Microsoft Deployment Toolkit. see Configure a Conditional Task Sequence Step. Remove. Solution Accelerators microsoft.com/technet/SolutionAccelerators . the task sequence will not continue if the group or step encounters an error. If no criteria are specified. In the Deployment Workbench console tree. and Edit buttons to modify the conditions under which the group of tasks runs. Use the Add. • Cleared. To modify existing task sequence properties on the OS Info tab 1. and then point to All Programs. 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). Click Start. 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. Condition list box For more information about conditions in task sequence steps. 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).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 version of the target operating system. • A task sequence variable.

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

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. and the modifications are displayed in the details pane of the Deployment Workbench. Edit Sysprep. The Delete Selected Items Wizard allows you to delete individual task sequences or entire folder structures.txt that the Deployment Workbench generates for Windows XP and Windows Server 2003 operating systems. but no user interaction is required. The wizard may take a few minutes to finish. A progress bar appears in the wizard. 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. but no user interaction is required.txt Click to modify the contents of the Unattend.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. You will see a progress bar in the Get Operating System Catalog Wizard. 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. 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.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.com/technet/SolutionAccelerators . Edit Unattend.inf Click to modify the contents of the Sysprep. Solution Accelerators microsoft. The task sequence configuration settings are saved. Note The Get Operating System Catalog Wizard may appear if an operating system does not yet have a catalog.

such as when you modify a configuration parameter that is not exposed in the Deployment Workbench or in the Windows Deployment Wizard. 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.xml) for a task sequence based on the configuration settings you provide in the Deployment Workbench and in the Windows Deployment Wizard.txt. see the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy.cab file in the Support\Tools folder on the Windows installation media. both of which are in the Deploy. Directly modify the unattended setup answer file for a task sequence by clicking Edit Unattend. Sysprep. Modify the Unattended Setup Answer File Associated with the Task Sequence MDT 2010 automatically updates the unattended setup answer file (Unattend. see Configure the Task Sequence Properties OS Info Tab. there are instances in which you may need to modify the unattended setup answer file for a task sequence directly.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. see the Windows Automated Installation Kit User’s Guide in the Windows AIK. For more information about: • • • Modifying the unattended setup answer file in the Deployment Workbench.xml. Solution Accelerators microsoft. see Manage Selection Profiles. Selection profiles. For more information on: • • Managing folders.chm). 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. However.com/technet/SolutionAccelerators . see Manage Folders in Deployment Workbench. Unattend.xml on the OS Info tab of the task sequence Properties dialog box.inf and Unattend.chm) and the Microsoft Windows Preinstallation Reference (Ref.

Copying a folder as described in Copy a Folder in Deployment Workbench. Start the New Folder Wizard using one of the following methods: • In the console tree. in the Actions pane. such as device driver groups. Enabling or disabling a folder as described in Enable or Disable a Folder in Deployment Workbench. Then. Renaming a folder as described in Rename a Folder in Deployment Workbench. Management tasks for folders include: • • • • • • • Creating a new folder as described in Create a New Folder in Deployment Workbench.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. Folders allow you to create hierarchies for organizing items as well as subsets of items that you can include in selection profiles. click New Folder. click a node or a folder. 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. Deleting a folder as described in Delete a Folder in Deployment Workbench. Modifying an existing folder as described in Modify an Existing Folder in Deployment Workbench. operating systems. and other items in the Deployment Workbench. device drivers. microsoft.com/technet/SolutionAccelerators Solution Accelerators . Create a New Folder in Deployment Workbench Create folders in the Deployment Workbench using the New Folder Wizard. Note Folders are similar in concept to the groups that existed in previous versions of BDD and MDT. Moving a folder as described in Move a Folder in Deployment Workbench. Although some management are unique to each type of item.

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

The folder_name Properties dialog box opens (where folder_name is the name of the folder to be modified). On the General tab. Provides information about the folder. Point to Microsoft Deployment Toolkit.com/technet/SolutionAccelerators . • Cleared.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. The folder configuration settings are saved. The folder properties are mostly configured when you run the New Folder Wizard. Click Start. If the check box is: • Selected. Table 62. and then point to All Programs. 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). 5. In the Actions pane. 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). click Properties. Select to enable or disable the folder. In the Deployment Workbench console tree. configure the settings listed in Table 62 based on the requirements of your organization. 2. you cannot select the folder in selection profiles. the modifications are displayed in the details pane of the Deployment Workbench. 3. Solution Accelerators microsoft. you can select the folder in selection profiles. and then click Deployment Workbench. In the details pane. 4. 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. To modify an existing folder 1. click folder_name (where folder_name is the name of the folder you want to modify). and then click OK.

from the Action menu. click an item. click an item. In the details pane. For more information on enabling or disabling folders in the Deployment Workbench. Point to Microsoft Deployment Toolkit. 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. device drivers. Solution Accelerators microsoft. 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. and then point to All Programs. click Properties. To set the properties of an item in a deployment share 1.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. In the details pane. see Modify an Existing Folder in Deployment Workbench. View Item Properties in Deployment Workbench You can view the properties of operating systems. and then click Deployment Workbench. such as an operating system or device driver). in the Actions pane. Then. double-click an item. 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. and other items from the Deployment Workbench using one of the following methods: • • • • In the details pane. Click Start. right-click an item. The Delete Selected Items Wizard allows you to delete individual folders or an entire hierarchy of folders. 2. click Properties. 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. 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.com/technet/SolutionAccelerators . Then. In the details pane. In the Deployment Workbench console tree. and then click Properties.

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

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

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

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

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

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

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

This selection profile includes all operating system packages and task sequences. Then. In the console tree. Rename a selection profile as described in Rename a Selection Profile in Deployment Workbench.com/technet/SolutionAccelerators . To create a new selection profile 1. Modify an existing selection profile as described in Modify an Existing Selection Profile in Deployment Workbench. click the Selection Profiles node. Identify the differences between selection provides and groups as described in Identify the Relationship Between Selection Profiles and Groups. 2. right-click the Selection Profiles node. In the console tree. Then. and then point to All Programs. click New Selection Profile. click the Selection Profiles node. Copy a selection profile as described in Copy a Selection Profile in Deployment Workbench. Solution Accelerators microsoft. 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). Create a New Selection Profile in Deployment Workbench Create selection profiles in the Deployment Workbench using the New Selection Profile Wizard. in the Actions pane. click New Selection Profile. from the Action menu. 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.147 Microsoft Deployment Toolkit 2010 Update 1 Selection profile Description Packages and Task Sequences nodes in the Deployment Workbench. In the Deployment Workbench console tree. Point to Microsoft Deployment Toolkit. Start the New Selection Profile Wizard using one of the following methods: • • • In the console tree. and then click Deployment Workbench. Move a selection profile as described in Move a Selection Profile in Deployment Workbench. Click Start. Delete a selection profile as described in Delete a Selection Profile from Deployment Workbench. and then click New Selection Profile.

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

the modifications are displayed in the details pane of the Deployment Workbench. In the Actions pane. 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.com/technet/SolutionAccelerators . and the depoyment_share\Control\SelectionProfiles. Hierarchical list of the folders and their selection status. 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. 3. 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. On the General tab. and then click OK. Provides information about the selection profile. 4. In the Deployment Workbench console tree. In the details pane.xml file (where deployment_share is the name of the deployment share) is updated with the selection profile configuration settings. click profile_name (where profile_name is the name of the selection profile you want to configure). click Properties. Comments Folders The selection profile configuration settings are saved.149 Microsoft Deployment Toolkit 2010 Update 1 2. 5. configure the settings listed in Table 67 based on the requirements of your organization. The profile_name Properties dialog box opens (where profile_name is the name of the selection profile you want to configure). 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. Table 67. Solution Accelerators microsoft. 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).

or applications.xml TaskSequenceGroups.com/technet/SolutionAccelerators .xml OperatingSystemGroups.xml LinkedDeploymentShareGroups. Identify the Relationship Between Selection Profiles and Groups Use selection profiles to create groups of Deployment Workbench items. The following code is an excerpt Solution Accelerators microsoft.xml SelectionProfileGroups. 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 DriverGroups. and other tasks. including: • • • • • • • • ApplicationGroups. device drivers. define the content to include for media deployments.xml MediaGroups. Use the selection profiles to specify device drivers. This file contains the definitions for all the selection profiles defined for the deployment share. consider a selection profile for device drivers called WinPEAndFullOS that are stored in a folder created immediately beneath the Out-of-Box Drivers node.xml For example. The contents of this file are similar to how groups were stored in MDT 2008 Update 1. The Delete Selected Items Wizard allows you to delete individual selection profiles. The following code is an excerpt from the DriverGroups.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.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. There is a separate file for each type of item. define content to include in a linked deployment share.xml.xml PackageGroups. such as operating systems.xml.

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

4. Solution Accelerators microsoft. Replicate linked deployment shares as described in Replicate Linked Deployment Shares in Deployment Workbench. click the Linked Deployment Share node. Move a linked deployment share as described in Move a Linked Deployment Share in Deployment Workbench. 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.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 New Linked Deployment Share. 2. Then. in the Actions pane. Complete the New Linked Deployment Share Wizard using the information in Table 68. In the Actions pane. Rename a linked deployment share as described in Rename a Linked Deployment Share in Deployment Workbench. In the console tree. from the Action menu. Copy a linked deployment share as described in Copy a Linked Deployment Share in Deployment Workbench. In the console tree. Point to Microsoft Deployment Toolkit. right-click the Linked Deployment Share node. click New Linked Deployment Share. In the Deployment Workbench console tree.com/technet/SolutionAccelerators . and then click Deployment Workbench. 3. click the Linked Deployment Share node. The New Linked Deployment Share Wizard starts. and then click New Linked Deployment Share. Then. Click Start. click New Linked Deployment Share. and then point to All Programs. 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). Delete a linked deployment share as described in Delete a Linked Deployment Share from Deployment Workbench. Start the New Linked Deployment Share Wizard using one of the following methods: • • • In the console tree. Modify an existing linked deployment share as described in Modify an Existing Linked Deployment Share in Deployment Workbench. To create a new linked deployment share 1.

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

In the Deployment Workbench console tree. 2. and the linked deployment share is added to the list of linked deployments shares in the details pane of the Deployment Workbench. 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. In the details pane. and then click 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 in which you will configure the package). You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. click linked_deployment_share (where linked_deployment_share is the name of the linked deployment share you want to configure). Click Finish. configure the settings listed in Table 69 based on the requirements of your organization. Click Start.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 154 On this wizard page Do this wizard to a file. In the Actions pane. and then point to All Programs.com/technet/SolutionAccelerators . 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). 4. and then click OK. Point to Microsoft Deployment Toolkit. However. 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. 5. The linked_deployment_share Properties dialog box opens (where linked_deployment_share is the name of the selection profile you want to configure). click Properties. The linked deployment share properties are configured when you run the New Linked Deployment Share Wizard. Table 69. To modify an existing linked deployment share 1. The New Linked Deployment Share Wizard finishes. 3.

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

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 modifications are displayed in the details pane in the Deployment Workbench. Note By default. Single-user mode improves replication performance. changes that other users make in the linked deployment share may be overwritten and lost during the replication process. the linked deployment share is configured to generate 32-bit and 64-bit boot images. The linked deployment share configuration settings are saved.com/technet/SolutionAccelerators . 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. the linked deployment share is opened in single-user mode as replication is performed and replication performance is improved. This check box is cleared by default. Solution Accelerators microsoft. 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. the boot images in the linked deployment share are not automatically updated when replication is complete. • Cleared. 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. the linked deployment share is not opened in single-user mode as replication is performed and replication performance is unimproved. This check box is cleared by default. If this check box is: • Selected. • Cleared. Note If you select this check box.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 156 Setting Description when replication is complete.

Click Start. Point to Microsoft Deployment Toolkit. The Delete Selected Items Wizard allows you to delete individual linked deployment shares. In the Deployment Workbench console tree.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. Table 70. To replicate content to a linked deployment share 1. the linked deployment share is configured to generate 32-bit and 64-bit boot images. 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. In the Actions pane. click Replicate Content. Ensure that sufficient storage exists for the linked deployment share prior to running the Replicate to Linked Deployments Share Wizard. 5. as the wizard does not verify that sufficient storage exists prior to replicating the content. Note By default. 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. and then point to All Programs. Tip You can click Save Output to save the output of the microsoft.com/technet/SolutionAccelerators . The replication process starts automatically and is displayed on the Progress wizard page. 4. 3. Complete the Replicate to Linked Deployment Share Wizard using the information in Table 70. click linked_deployment_share (where linked_deployment_share is the name of the linked deployment share you want to configure). In the details pane. and then click Deployment Workbench. The Replicate to Linked Deployment Share Wizard starts. 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. 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. 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). 2.

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

from the Action menu. click New Media. click the Media node. Summary Confirmation Review in the information in Details. click New Media. Click Next. In Media path. Point to Microsoft Deployment Toolkit. 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). and then point to All Programs. 4.com/technet/SolutionAccelerators Solution Accelerators . click New Media. and then click Deployment Workbench. Complete the New Media Wizard using the information in Table 71. 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). Information for Completing the New Media Wizard On this wizard page General Settings Do this 1. In Selection profile. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard microsoft. type comment (where comment is descriptive text that provides information about the media). Then. 3. To create new deployment media 1. In the console tree. Table 71. Note You can alternatively click Browse to find the folder on a local drive or network shared folder. and then click New Media. In the console tree. In the Actions pane. In Comments. right-click the Media node.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. Then. 2. Click Start. 3. 2. Start the New Media Wizard using one of the following methods: • • • In the console tree. in the Actions pane. 4. and then click Next. 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). The New Media Wizard starts. In the Deployment Workbench console tree. Tip You can click Save Output to save the output of the wizard to a file.

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

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

Click Start. Point to Microsoft Deployment Toolkit. and then point to All Programs.ini file that the Deployment Workbench generates for the deployment media The media configuration settings are saved. The modifications are displayed in the details pane of the Deployment Workbench. Solution Accelerators microsoft. In the Deployment Workbench console tree. The media configuration settings are saved.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). 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. 3. In the Actions pane. To modify existing media properties on the Rules tab 1. Configuration Settings on the Rules Tab of Media Properties Setting CustomSettings. 5. click Properties. 2.com/technet/SolutionAccelerators . click media (where media is the name of the media you want to configure). The modifications are displayed in the details pane of the Deployment Workbench. 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). In the details pane. On the Rules tab. Configure the Media Properties Rules Tab The media properties on the Rules tab are configured when you run the New Media Wizard.ini Edit Bootstrap. configure the settings listed in Table 73 based on the requirements of your organization. The media Properties dialog box opens (where media is the name of the media you want to configure). Table 73. and then click Deployment Workbench. However. 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).ini Description Contains the current configuration of the CustomSetting.ini file for the deployment media Click to modify the contents of the Bootstrap. and then click OK. 4. 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).

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

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

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

In the Installed Software dialog box. in the Value box. in the Key box. In the Registry Setting dialog box. In the Registry Setting dialog box. click Add. In the Installed Software dialog box. 7. You can use this information to match a specific product using both the product code and the upgrade code. On the step Option tab (where step is the name of the task sequence step to configure). click Root key. In the Registry Setting dialog box. In the Installed Software dialog box. 5. type the name of the Value name. To add an Installed Software condition to a task sequence step 1. On the step Option tab (where step is the name of the task sequence step to configure). 3. and then click OK.com/technet/SolutionAccelerators . Solution Accelerators microsoft.181 Microsoft Deployment Toolkit 2010 Update 1 • • • • REG_SZ REG_EXPAND_SZ REF_DWORD Value. click condition (where condition is the logical operation to use in the condition). type the value for which testing will occur. in the Root key box. In the Registry Setting dialog box. click Add. click Value type. and then click Installed Software. and then click Registry Setting. The product information will be extracted from the MSI file and populate the respective boxes. click OK. 6. 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. 4. 2. In the Registry Setting dialog box. 2. or you can use it to match any version of this product using only the upgrade code. type key (where key is the remainder of the registry key minus the subtree). 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. 3. in the MSI file box. browse to the specific MSI file associated with the installed software. in the Condition box. 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. in the Value name box. in the Value type box. In the Registry Setting dialog box.

(Optional) Version of the file being tested Condition. select the Check the timestamp check box. (Optional) One of the logical operators Date. (Optional) The date of the file Time. The path of the file being tested Version. click OK. click Add. The path of the folder to test. (Optional) The date of the file Time. In addition to evaluating the path of the file to be tested. (Optional) The time stamp of the file To add a File Properties condition to a task sequence step 1. Condition. 4. click Add. In addition to evaluating the path of the folder to be tested. in the Path box. 3. go to the folder to be tested. On the step Option tab (where step is the name of the task sequence step to configure). and set the time. test for its version and time stamp under a number of conditions. clear the Check the timestamp check box so that the additional condition will not be tested for. provide the following information on the Folder Properties dialog box: • • • • Path.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. set a date. On the step Option tab (where step is the name of the task sequence step to configure). set the condition of the value. (Optional) A logical operator Date. Otherwise. 2. Solution Accelerators microsoft. provide the following information on the File Properties dialog box: • • • • • Path. and then click File Properties. 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. To configure a condition based on a file property. and then click Folder Properties. In the Folder Properties dialog box.com/technet/SolutionAccelerators . (Optional) The time stamp of the file To add a Folder Properties condition to a task sequence step 1. In the Folder Properties dialog box. to check the time stamp of the file. test for its time stamp under a number of conditions. To configure a condition based on a folder’s property.

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

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

com/technet/SolutionAccelerators . If you select this option. • Cleared. BitLocker Drive Encryption is a fulldisk encryption feature included in Windows Vista and Windows Server 2008 Solution Accelerators microsoft. Contains the file system for the 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.185 Microsoft Deployment Toolkit 2010 Update 1 Table 81. Contains the type of partition to be created. Contains the name of a task sequence variable used to store the drive letter assigned to the partition. Select to configure the task sequence step to format the partition by performing a quick format. specify the percentage in the Size(%)box. the partition is not configured as the boot partition. Select to configure the task sequence step to create a partition of a specific size. • Cleared. Select to configure the task sequence step to create a partition based on a percentage of the remaining free disk space. the partition format is performed using the standard format process. If the check box is: • Selected. which can be Primary or Extended. If the check box is: • Selected. Configuration Settings on the Partition Properties Dialog Box Setting Partition name Description Contains the name of the partition. Select to configure the task sequence step to configure the partition as the boot partition of the target computer. the partition is configured as the boot partition. which can be NTFS or FAT32. 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. which appears in the Volume box on the Partition and Format Disk task sequence step type’s Properties tab. specify the size of the partition in the Size box. the partition format is performed using the quick format process.

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

On the Task Sequence tab. 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). 5. 2. and then click OK. and then click the Properties tab. 6. To configure task sequence steps based on the Capture Network Settings task sequence step type 1. In the Actions pane. For Refresh Computer deployment scenarios. In the details pane. and then point to All Programs. add a task sequence step based on the Capture Network Settings task sequence step type in the State Capture phase. configure the settings listed in Table 82 based on the requirements of your organization. 4. 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. Point to Microsoft Deployment Toolkit. The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure).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. 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). in the task sequence hierarchy. 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.com/technet/SolutionAccelerators Solution Accelerators . and then click Deployment Workbench. In the Deployment Workbench console tree. which is always set to Capture Network Settings Contains the name of the task sequence step that appears in the task sequence hierarchy microsoft. Table 82.ini file or in the MDT DB. 3. On the Properties tab. click Properties. Configuration Settings on the Properties Tab of the Capture Network Settings Task Sequence Step Type Setting Type Name Description Contains the task sequence type. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). Click Start.

The task_sequence_name Properties dialog box opens (where task_sequence_name is the name of the task sequence you want to configure). and then click Deployment Workbench. and then click the Properties tab. In the Deployment Workbench console tree. Point to Microsoft Deployment Toolkit. configure the corresponding network settings. On the Task Sequence tab. For each network adapter in the target computer. in the task sequence hierarchy. To configure task sequence steps based on the Apply Network Settings task sequence step type 1. 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. Solution Accelerators microsoft. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). Some of the MDT 2010 task sequence templates include a task sequence step in the State Restore phase named Apply Network Settings. If no configuration settings are specified. and then point to All Programs. 4. The network settings that this task sequence step type configures are the same settings configured in the properties of a network adapter.com/technet/SolutionAccelerators . In most instances. In the details pane. click Properties. 5. 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). 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).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. 3. In the Actions pane. Click Start. 2. configure the existing task sequence step instead of creating a new task sequence step. 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.

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

• Delete. Click one of the following to modify the IP addresses and subnet masks in this list: • Add. Configure the settings in Table 85 based on the requirements of your organization. Table 85. • Properties. Modify the IP address and cost metric for a gateway an existing entry. microsoft. Delete an existing entry. and then click OK. Delete an existing entry. Table 85 lists the configuration settings for the DNS tab of the Network Settings dialog box. • Delete. 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. Note This box is enabled only if you select Use the following IP address. Network Settings Contains a list of IP addresses and subnet masks to be configured for the network adapter. 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. Click one of the following to modify the gateway IP address and routing cost metric in this list: • Add.com/technet/SolutionAccelerators Solution Accelerators . Modify the IP address and subnet mask for an existing entry.Using the Microsoft Deployment Toolkit: Managing LTI Deployments 190 Setting Description specify in the Network Settings and Gateway Settings boxes. Add the IP address and cost metric for a gateway to the list box. Add an IP address and subnet mask combination to the list box. • Properties. 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.

• Properties. Configure the settings in Table 86 based on the requirements of your organization. Click one of the following to modify the list of DNS servers: • Add. If the check box is: • Selected. Add the WINS server IP address to the microsoft. this check box is cleared. Add the DNS Server IP address to the list box. Table 86. Select to configure the network adapter to register the network adapters IP address of the primary DNS server. 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. • Cleared. Note By default. and then click OK. this check box is selected. the IP address of the network adapter is registered using the suffix listed in DNS Suffix. Table 86 lists the configuration settings for the WINS tab of the Network Settings dialog box. If the check box is: • Selected.com/technet/SolutionAccelerators Solution Accelerators . 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. • Delete.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. Modify the DNS server IP address for an existing entry. Contains the DNS domain name suffix to be added to any DNS queries. the IP address of the network adapter is not registered using the suffix listed in DNS Suffix. Delete an existing entry. • Cleared. Note By default. the IP address of the network adapter is not registered in DNS. the IP address of the network adapter is registered in DNS. Click one of the following to modify the list of WINS servers: • Add.

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

xml file into Notepad. Start Microsoft Notepad.xml file to contain the list of BIOS versions incompatible with the target operating system in the operating system build.vbs.xml File Attribute Description Description Text description of the target computer that has an incompatible BIOS version. Copy the script source from ZTIBIOSCheck.xml file listed in Table 87 for each incompatible BIOS version. Table 87.xml for each task sequence created in the Deployment Workbench.wsf script. 4. The ZTIBIOSCheck.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 . Update the attributes in the ZTIBIOSCheck. The Check BIOS task runs the ZTIBIOSCheck.vbs utility to extract attributes on a target computer 1. Modify ZTIBIOSCheck. 3. Save the script source in Notepad as ZTIBIOS_Extract_Utility. which checks the BIOS version of the target computers against the list of incompatible BIOS versions in the ZTIBIOSCheck.xml file. Modify the ZTIBIOSCheck.vbs) that can help extract the attributes listed in Table 87.vbs on a target computer that has an incompatible BIOS.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).) Model of the target computer with an incompatible BIOS version (This value must match the value stored in the BIOS.xml file contains the source for a script (ZTIBIOS_Extract_Utility.) Computer Manufacturer Model Date The ZTIBIOSCheck. Solution Accelerators microsoft. To use the ZTIBIOS_Extract_Utility. 2. Run ZTIBIOS_Extract_Utility.) Date of the BIOS of the target computer with an incompatible BIOS version (This value must match the value stored in the BIOS. Attributes to Update in the ZTIBIOSCheck. 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.

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

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

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

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

and then click Next. Note The upgrade process will fail on target computers that have users logged on using Remote Desktop sessions. Migration Type Options Option Refresh this computer Select this option to • Optionally. Upgrade the existing computer using the upgrade features that the new operating system supports. you can use the New Computer scenario to deploy a new operating system to a new computer. 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.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 198 This wizard appears when the conditions in Table 93 are met. • Deploy the desktop standard environment. The Choose a migration type wizard page is not displayed for the New Computer scenario. Upgrade this computer 7. 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. Note Although it is not a migration scenario. 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. Table 95. Table 94. save the existing user state migration data. • Restore user state migration data on the same computer. including operating system and applications.com/technet/SolutionAccelerators . Table 93. The wizard appears when the conditions in Table 95 are met.

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

Join a Windows workgroup. type domain (where domain is the name of the domain in the user account specified in the User Name box is located). In the Domain box. Table 100. 5.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. 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. click one of the options listed in Table 101 based on your environment’s requirements. In the Password box. type password (where password is the password for the user account specified in the User Name box). In the User Name box. In the Organizational Unit box. 2. • In the Workgroup box. This wizard appears when the conditions in Table 100 are met. In the Domain box. type workgroup (where workgroup is the name of the workgroup to join). 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 . Join a workgroup 10. type domain (where domain is the name of the domain to be joined). User State Backup Options Option Automatically Solution Accelerators Select this option to • Allow the MDT 2010 scripts and process microsoft. On the Specify where to save your data and settings page. 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). 4. 3. and then click Next.

11. type location (where location is the fully qualified path to the location in which the user state migration back files are stored). click one of the options listed in Table 105 based on requirements. Note Alternatively. Specify Whether to Restore User Data Page Conditions Property SkipUserData DeploymentType Condition Not equal to YES Equal to NEWCOMPUTER Table 103. type location (where location is the fully qualified path to the locations for storing the user state migration data). The migration type is Replace Computer. click Browse to go to the location. select the Allow data and settings to be stored locally when possible check box to give preference to storing the data locally. • Optionally. This wizard appears when the conditions in Table 102 are met. On the Specify whether to restore user data page. In the Location box. Table 102. Save the user state migration data to a specific location. In the Location box. 12. and then click Next. click one of the options listed in Table 103 based on your environment’s requirements. Solution Accelerators microsoft. On the Specify where to save a complete computer backup page.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. 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.com/technet/SolutionAccelerators . and then click Next. 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.

Discard any existing data on the target computer or deploy a new computer with no existing data. Table 104. Specify the Product Key Needed to Install This Operating System Page Conditions Solution Accelerators microsoft. in the Product key box. 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. This wizard appears when the conditions in Table 106 are met. Specify Where to Save a Complete Computer Backup Page Conditions Property SkipComputerBackup DeploymentType Condition Not equal to YES Equal to REFRESH Table 105. Table 106. Instead. Note Windows Complete PC Backup is a feature of Windows Vista only. Save the computer image backup to a specific location. Specify a location Do not back up the existing computer The Windows Deployment Wizard uses the ImageX utility to perform the backup. 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 computer backup). and then click Next. Use the Windows Complete PC Backup for enhanced disaster recovery protection after migration is complete. MDT 2010 uses the ImageX utility during migration because it works on all platforms that MDT 2010 supports.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 202 This wizard appears when the conditions in Table 104 are met. ImageX is not intended to be used as a part of the overall backup and disaster recovery process. On the Specify the product key needed to install this operating system page.com/technet/SolutionAccelerators . 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. 13. • Optionally. type product_key (where product_key is the product key to be assigned to the target computer). In the Location box.

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

Table 110. 16. This wizard appears when the conditions in Table 111 are met. Administrator Password Page Conditions Property SkipAdminPassword DeploymentType Condition Not equal to YES Not equal to REPLACE or CUSTOM Solution Accelerators microsoft. On the Administrator Password page.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. click the time zone in which the target computer is located. select the appropriate applications to deploy.com/technet/SolutionAccelerators . Table 112. This wizard page appears when the conditions in Table 112 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. Table 111. On the Set the Time Zone page . and then click Next. and then click Next. type password (where password is the password for the local built-in Administrator account on the target computer). Keyboard layout to be used with the target operating system. This wizard appears when the conditions in Table 110 are met. and then click Next. On the Select one or more applications to install page. Set the Time Zone Page Conditions Property SkipTimeZone DeploymentType Condition Not equal to YES Not equal to REPLACE or CUSTOM 17. in the Administrator Password and Please confirm Administrator Password boxes.

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

2 or later. select Enable BitLocker using TPM only. • To use TPM with 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. select Enable BitLocker using TPM and a PIN. select one of the following options for using TPM: • To use TPM only. 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 Enable BitLocker using only an External Startup Key. Enable BitLocker using Enable BitLocker Drive Encryption. This wizard appears when the conditions in Table 117 are met. in the box. type pin (where pin is the BitLocker Drive Encryption PIN for the target computer). 21. • To use only an External Startup Key. in the Pin box. 48-character external key. Note The default setting for BitLocker Drive Encryption is enabled. and use a only an external key randomly generated. Then. select the drive on which the startup key resides. select Enable BitLocker using TPM and a startup key. • To use TPM with a PIN. in the box. Table 117.com/technet/SolutionAccelerators . select the drive on which the external startup key resides. Enable BitLocker using Activate BitLocker Drive Encryption and use TPM TPM version 1.Using the Microsoft Deployment Toolkit: Running the Windows Deployment Wizard 206 Table 116. Complete the Specify credentials for connecting to network shares page based on the information in Table 118. and then click Next.

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

Enable the Configuration Manager Console integration with MDT 2010 as described in Enable Configuration Manager Console Integration. To prepare the MDT 2010 deployment environment for ZTI deployments 1. Preparing for ZTI deployment to the target computers as described in Preparing for ZTI Deployments to Target Computers. 4. Obtain the software that ZTI requires as described in Obtain the Software Required by the ZTI Deployment Process. Preparing the prerequisite infrastructure as described in Prepare the Prerequisite Infrastructure for ZTI Deployments. 3. Perform ZTI deployments by: • • • Preparing the ZTI deployment environment as described in Preparing the ZTI Deployment Environment. • • Preparing the ZTI Deployment Environment After you have prepared the prerequisite infrastructure for MDT 2010. 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. Preparing for ZTI deployment to the reference computer as described in Preparing for ZTI Deployment to the Reference Computer. Deploying captured images to the target computer in ZTI as described in Deploying Captured Images to Target Computers in ZTI. 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. 2. Ensure that your new or existing System Center Configuration Manager infrastructure is specifically optimized for the Operating System Deployment feature. . or upgrade an existing instance of MDT 2008 to MDT 2010 as described in Install or Upgrade to MDT 2010 for ZTI. or from removable media. within a Windows workgroup.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. you are ready to prepare the MDT 2010 deployment environment for ZTI. Install a new instance of MDT 2010 on the deployment server.

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

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

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

To prepare for ZTI deployment to target computers 1. To deploy to and capture an image of the reference computer 1. 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. deploy them to the target computers. 3. Create a collection that contains the reference computer as described in Managing Computer Collections in Configuration Manager Console. 2. ensure that the necessary deployment resources exist. Optionally. create one or more task sequences for deploying the captured images. and then capture an image of the reference computer. 5. Start the reference computer with the task sequence bootable media disk as described in Deploying an Operating System Using Task Sequence Bootable Media. and applications to the reference computer. advertise the task sequence to the reference computer and start the reference computer with the bootable Windows PE image created earlier in the process. 4. Note Most production networks have multiple distribution points. When performing this step in a production environment. 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. 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.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 212 6. Preparing for ZTI Deployment to Target Computers After the images of the reference computers are captured. In preparation for deploying the captured images to the target computers. Prepare network shares for storing migration data and MDT 2010 deployment logs as described in Preparing the MDT 2010 Migration Resources. 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. Create an advertisement for the reference computer task sequence as described in Managing Advertisements in Configuration Manager Console. 2. device drivers.com/technet/SolutionAccelerators . Deploying to and Capturing an Image of the Reference Computer in ZTI After the distribution points are updated. The task sequence created earlier will deploy the target operating system. and customize the MDT 2010 deployment process.

com/technet/SolutionAccelerators Solution Accelerators . Prepare the ZTI task sequences. and specify the fully qualified UNC path to the WIM image captured from the reference computer. any combination of these deployments scenarios might be necessary. 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. Create additional distribution points to help in larger deployments as described in Managing Distribution Points in Configuration Manager Console. the MDT 2010 configuration files. microsoft. There is no user migration information to save and restore and no existing file systems to preserve. Use the Client Task Sequence template to deploy the captured image of the reference computer to the target computer. you deploy a new installation of a Windows operating system to a new computer. 3. Prepare for the New Computer Deployment Scenario to Target Computers Using ZTI In the New Computer deployment scenario. 4. 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. For more information about MDT 2010 deployment scenarios. To prepare for the New Computer deployment scenario to target computers 1. 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. Table 119. 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. see Identifying Deployment Scenarios. 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.213 Microsoft Deployment Toolkit 2010 Update 1 target computers as described in Preparing Windows Deployment Services for ZTI Deployments.

5. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. Note Most production networks have multiple distribution points. select the appropriate distribution points for the network. 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). Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. 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. To prepare for the Refresh Computer deployment scenario to target computers 1. select the appropriate distribution points for the network. 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. including computers that must be re-imaged for image standardization or to address a problem. 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. Solution Accelerators microsoft. 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. Prepare for the Refresh Computer Deployment Scenario to Target Computers Using ZTI In the Refresh Computer deployment scenario. When performing this step in a production environment. 7. 4. Optionally. 3. including: • • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 214 2. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. There is user migration information to save and restore but no existing file systems to preserve. Configure System Center Configuration Manager to contain the appropriate software for deployment to the target computer. 6. a computer is refreshed. When performing this step in a production environment. Use the Client Task Sequence template to deploy the captured image of the reference computer to the target computer. Note Most production networks have multiple distribution points.com/technet/SolutionAccelerators .

and specify the fully qualified UNC path to the WIM image captured from the reference computer. Optionally. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console.215 Microsoft Deployment Toolkit 2010 Update 1 Table 120. including: • • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 2. 3. When performing this step in a production environment. The existing user state migration data is saved from the existing target computer. 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. 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. select the appropriate distribution points for the network. There are no existing file systems to preserve. select the appropriate distribution points for the network.com/technet/SolutionAccelerators . Then. 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. one computer replaces another computer. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. 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. 6. 5. • Performing Deployments Using the MDT DB. 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. 4. the user state data is restored to the new computer. Use the: Solution Accelerators microsoft. Finally. When performing this step in a production environment. Note Most production networks have multiple distribution points. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. Note Most production networks have multiple distribution points. Configure System Center Configuration Manager to contain the appropriate software for deployment to the target computer.

Tip Create the task sequence for deploying to the reference computer based on the Client Task Replace Sequence template included in MDT 2010. 2. microsoft. which is installed with System Center Configuration Manager. Create a new task sequence that will deploy the captured image of the reference computer to the target computer. Create a computer association between the existing target computer and the new target computer as described in the section. 3. Tip Create the task sequence for deploying to the reference computer based on the Client Replace Task Sequence template included in MDT 2010.” in Configuration Manager Documentation Library. Important Run this task sequence before running the task sequence based on the Client Task Sequence template on the new target computer. 3. 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. “How to Create a Computer Association for Side-by-Side Migration. Important Run this task sequence after running the task sequence based on the Client Replace Task Sequence template on the existing target computer. Table 121.com/technet/SolutionAccelerators Solution Accelerators . including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 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. Configure System Center Configuration manager to contain the appropriate software for deployment to the 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. 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 specify the fully qualified UNC path to the WIM image captured from the reference computer. • 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. 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.

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. which is installed with System Center Configuration Manager. 2.217 Microsoft Deployment Toolkit 2010 Update 1 Configuring device drivers as described in Managing Device Drivers 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. select the appropriate distribution points for the network. • Performing Deployments Using the MDT DB. Note Create a collection for each MDT 2010 deployment scenario to be performed. When performing this step in a production environment. Deploy the captured image of the reference computer to target computers for each respective deployment scenario in your organization. Customize the task sequences to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration manager Console. 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 . Automatically as described in the section. and ensure that the collection includes the target computers requiring the corresponding deployment scenario. “How to Deploy Operating Systems Using Unknown Computer Support. • 7. Add the target computer to the System Center Configuration Manager site database: • • Manually. 5. 4. as described in Manually Adding Computers to the Site Database in Configuration Manager Console. Create a collection that contains the target computers as described in Managing Computer Collections in Configuration Manager Console. select the appropriate distribution points for the network. Update the distribution points so that any changes to the packages are distributed properly as described in Managing Distribution Points in Configuration Manager Console. 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.” in Configuration Manager Documentation Library. Solution Accelerators microsoft. 6. Note Most production networks have multiple distribution points.

the captured image of the reference computer is deployed on the target computer. Create an advertisement for the target computer task sequences as described in Managing Advertisements in Configuration Manager Console. For more information about the MDT 2010 deployment scenarios. The Task Sequence Wizard starts.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 218 3. 2. Solution Accelerators microsoft. 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.com/technet/SolutionAccelerators . Start the target computer with the task sequence bootable media created earlier in the process or from Windows Deployment Services. To deploy the capture images to the target computers in the New Computer Deployment Scenario Using ZTI 1. 5. 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. 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. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using ZTI. 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. any combination of deployments scenarios might be necessary. Either method starts Windows PE on the target computer and initiates the ZTI deployment process. see Identifying Deployment Scenarios. Deploy Captured Images to Target Computers in the Replace 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. Complete the Task Sequence Wizard. Depending on the target computers in your organization. At the end of the 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 ZTI.

To deploy captured images of the reference computer to target computers 1. The wizard starts. and the operating system deployment starts. The task sequence restarts the computer. 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. installs any packages. installs any applications.219 Microsoft Deployment Toolkit 2010 Update 1 Table 122. 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. This task sequence runs in the current operating system on the existing target computer. 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.com/technet/SolutionAccelerators . starts the new operating system. 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. First. the task sequence restarts the computer. 2. starts Windows PE. The target computer is now deployed. restores the user state migration data. 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. 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. and performs any other actions configured in the task sequence. run the advertisement for the task sequence you created to capture the user state migration data from the existing target computer (old computer). and then initiates installation of the new operating system. Finally. Second. The task sequence runs in the current operating system to capture user state migration data. 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.

Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 220 Computer with the User State Migration Data from the Existing Computer Using ZTI. and then the Windows Deployment Wizard starts. 2. At the end of the deployment process. and the user state migration data is restored from the Configuration Manager state migration point. 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. Information for Completing the Task Sequence Wizard for the Replace Computer Deployment Scenario for Deploying the Captured Image Using ZTI Solution Accelerators microsoft. 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. To complete the Windows Deployment Wizard in the Replace Computer deployment scenario for deploying the captured image 1. 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. 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.com/technet/SolutionAccelerators . the captured image of the reference computer is deployed on the target computer. Start the reference computer with the ZTI bootable media created earlier in the process or from Windows Deployment Services. 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. This task sequence runs in the current operating system on the existing target computer. Windows PE starts. 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. Complete the Task Sequence Wizard. At the end of the task sequence. Table 123. The ZTI bootable media starts Windows PE on the target computer and initiates the ZTI.

and the operating system deployment starts. The wizard starts.com/technet/SolutionAccelerators . Solution Accelerators microsoft. The new target computer is deployed with the user state from the existing target computer automatically restored to the new target computer.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.

Deploying an operating system using task sequence bootable media as described in Deploying an Operating System Using Task Sequence Bootable Media.222 Microsoft Deployment Toolkit 2010 Update 1 Managing ZTI Deployments in Configuration Manager Console You manage ZTI deployments through the Configuration Manager Console. 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. • • • • • • • • • • • • . Creating task sequence bootable media for ZTI as described in Creating Task Sequence Bootable Media. Manually adding computers to the site database for ZTI as described in Manually Adding Computers to the Site Database in Configuration Manager Console. Managing software packages for ZTI in the Configuration Manager Console as described in Managing Software Packages in Configuration Manager Console. Managing distribution points for ZTI as described in Managing Distribution Points in 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 individual ZTI task sequence steps as described in Configuring ZTI Task Sequence Steps 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. The wizards used to configure ZTI are integrated into the Configuration Manager Console. Managing device drivers for ZTI deployments in the Configuration Manager Console as describe in Managing Device Drivers in Configuration Manager Console. Configuring ZTI task sequence steps that perform server role–related actions as described in Configuring Server Role Task Sequence Steps for ZTI. You use the Deployment Workbench in ZTI deployments only to configure the MDT DB. Managing computer collections for ZTI as described in Managing Computer Collections in Configuration Manager Console. Managing advertisements for ZTI as described in Managing Advertisements in Configuration Manager Console.

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. MDT 2010 includes task sequence templates that you can use to deploy the reference and target computers. Table 124.xml Deploy to the reference computer to prepare the reference computer for the OEM capture process. • Identify the ZTI Task Sequence Templates in MDT 2010 Table 124 lists the task sequences templates included in MDT 2010. The template files are located in the install_folder\SCCM folder (where install_folder is the folder in which MDT 2010 was installed). Deploy the image captured after the OEM Preload Task Sequence (Pre-OEM) completed on the target computers.xml SCCM_CLIENT_PRE–OEM. the file name for each template.com/technet/SolutionAccelerators . Client Task SCCM_Client. Solution Accelerators microsoft. Deploy to target computers for the Replace Computer scenario. 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. Creating ZTI task sequences as described in Create ZTI Task Sequences Using the Create Microsoft Deployment Task Sequence Wizard.xml SCCM_CLIENT_POST– OEM. 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 Sequence Client Replace Task Sequence OEM Preload Task Sequence (PostOEM) OEM Preload Task Sequence (Pre-OEM) SCCM_ClientReplace. 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. and a description of the template.

Note Always use the Import Microsoft Deployment Task Sequence Wizard to import the task sequence templates.exe for Windows Vista or later operating systems). Microsoft Deployment Files package OS image package OS install package Client package USMT package Custom Settings package Solution Accelerators microsoft. Contains unattended files and customsettings. System Center Configuration Manager client installation files.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. All the files required to install the operating system (using WINNT32 for Windows XP and Windows Server 2003 or Setup. Table 125. These packages and images must exist (or be created) for the task sequences to run correctly. USMT files used to capture and restore user state.com/technet/SolutionAccelerators . 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. Although you can manually import the task sequence templates. doing so is not recommended.ini. Image of the target operating system to be deployed to the target computer. Script and tools necessary for the MDT 2010 task sequence templates for System Center Configuration Manager.xml Deploy to target computers for all scenarios.xml Deploymen t Custom Task Sequence Standard Server Task Sequence SCCM_Server. Microsoft SCCM_Custom. 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.

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

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

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

In Product key. 5. click microsoft. 1. The Select a Package dialog box appears. In the Windows User Account dialog box. Select Specify an existing boot image. perform the following steps: a. 2. including the name of the WIM file). The Windows User Account dialog box appears. In Select a Package dialog box. If you select this option. type unc_path (where unc_path is the fully qualified UNC path for the location of the WIM file. Choose Template: Capture Settings 1. In Password and Confirm password. 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). The other option is This task sequence may be used to capture and image.com/technet/SolutionAccelerators Boot Image Solution Accelerators . The other option is Create a new boot image package. type password (where password is the password for the user account). 6. c. Select This task sequence will never be used to capture and image. Click Set. b. Click Next. 3. perform the following steps: a. Select This task sequence may be used to capture and image. and then click OK. Click Next.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). d. Click Browse. type product_key (where product_key is the product key for operating system). If you select this option. The other option is This task sequence will never be used to capture and image. b. In Capture destination. in User name.

type comment_text (where comment_text is descriptive information about the boot image package). Select Create a new boot image package. Click Next. In Platform. 1. the ADO components are added to Solution Accelerators microsoft. 1. 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. If the check box is: • Selected. 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. 2. in Package source to be created. and then click OK. 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. Tip You can also click Browse to locate the UNC path. this check box is selected. 2. The other option is Create a new boot image package. In Version. By default. 2. Ensure that the Configuration Manager service account has the appropriate permission on this network shared folder. click platform (where platform is the platform architecture for the boot image— x86 or X64). If you select this option.com/technet/SolutionAccelerators . type version_number (where version_number is the version number to be assigned to the boot image package). In Comments. type package_name (where package_name is the name to be given to the boot image package). 3. 3. which is needed to access SQL Server databases such as the MDT DB.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). Click Next. Select or clear the ADO check box if you want to add ADO components to the boot image. 4. The Configuration Manager service account must have permission to modify the contents of this UNC path to update the boot images.

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

change the configuration of the Apply Operating System Image task sequence step.231 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Do this the folder in which the package source will be stored). 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. 3. OS Image On this wizard page. The other options are Create a new OS image. 2. if you select a SKU that is different from the default SKU. OS install packages contain all the necessary files to install the operating system. remove the following section from Unattend. Click Next.xml in the Settings package: <MetaData> <Key>/image/index</Key> <Value>1</Value> </MetaTag> 1. Also. 3. Click Next. such as the contents of a Windows XP CD. Select Specify an existing OS image. type version_number (where version_number is the version number to be assigned to the Microsoft Deployment Toolkit files package). type package_name (where package_name is the name to be given to the Microsoft Deployment Toolkit files 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 Comments. In Name.com/technet/SolutionAccelerators . In Version. 1. Specify an existing OS installation package. type comment_text (where comment_text is descriptive information about the Microsoft Deployment Toolkit files package). 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. Solution Accelerators microsoft. 4. you can select (or create) OS image packages or OS install packages.

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

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

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

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

in Package source to be created. 3. In Language. 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. In Manufacturer. Click Next.Using the Microsoft Deployment Toolkit: Managing ZTI Deployments 236 On this wizard page Do this the name of the existing package). and then click OK. In Name. In Comments. 2. Click Create a new settings package. Select No Sysprep package is required. In Version. Click Next. If you select this option. type package_name (where package_name is the name to be given to the package). 1. 5. Sysprep Package 1. Solution Accelerators microsoft. Select Specify an existing Sysprep package. perform the following steps: a. The other option is Specify an existing settings package. 3.com/technet/SolutionAccelerators . If you select this option. 2. The other options are Specify an existing Sysprep package and Create a new settings package. Click Browse. 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 comment_text (where comment_text is descriptive information about the package). type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package). 6. 2. Tip You can also click Browse to locate the UNC path. type language (where language is the language of the package). type version_number (where version_number is the version number to be assigned to the package). The other options are No Sysprep package is required and Create a new settings package.

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

Solution Accelerators microsoft. The Create Microsoft Deployment Task Sequence Wizard closes when the task sequence is created. • 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.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. 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. “Operating System Deployment: Operating System Images Node.com/technet/SolutionAccelerators . see the section. 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. Creating a new driver package that contains the device drivers as described in Create a New Driver Package. which is installed with System Center Configuration Manager. For information about creating a new driver 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.” in Configuration Manager Documentation Library. “Import New Driver Wizard. Create a New Driver Package A driver package contains the content associated with one or more device drivers. which is installed with System Center Configuration Manager. use the Import New Driver Wizard. 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. 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. the actions that you can run.” in Configuration Manager Documentation Library. 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. see the section. For information about this wizard.

For information about adding device drivers to boot images. 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. because the version of Windows PE is Windows Vista based. “How to Add Windows Device Drivers to a Boot Image. “How to Manage the Driver Catalog. 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. To allow System Center Configuration Manager to search in the driver catalog for the new device drivers. which is installed with System Center Configuration Manager.” in Configuration Manager Documentation Library. you can add the them to existing operating systems and boot images. Add Device Drivers to an Operating System Add new device drivers to an existing operating system image using the Task Sequence Editor. which is installed with System Center Configuration Manager. “How to Install Drivers on a Configuration Manager 2007 Client Using a Task Sequence.” in Configuration Manager Documentation Library. see the section. see the section.” in Configuration Manger Documentation Library. 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. which is installed with System Center Configuration Manager. 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. which is installed with System Center Configuration Manager. 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. Only add valid device drivers that are intended for use with Windows Vista. because other types of drivers are not needed and will increase the size of the boot image. For information about adding device drivers to an operating system. Add Device Drivers to Operating System and Boot Images When you have added device drivers to the driver catalog. see the section.239 Microsoft Deployment Toolkit 2010 Update 1 “How to Create a New Driver Package.com/technet/SolutionAccelerators . Solution Accelerators microsoft. Only mass storage device drivers and network adapter device drivers should be added to boot images. add a Auto Apply Drivers task sequence step to an existing task sequence.

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

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

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

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

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

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

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

The Configuration Manager Console allows you to: Solution Accelerators microsoft. In System Center Configuration Manager. For more information about managing computer collections. Managing Computer Collections in Configuration Manager Console In ZTI deployments. high-speed connection to a distribution point.com/technet/SolutionAccelerators . you can customize it using the Configuration Manager Console. Your organization may have more than one distribution point. 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. “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. ensuring that each reference and target computer has a persistent.247 Microsoft Deployment Toolkit 2010 Update 1 For more information about manually adding computers to the site database.” in Configuration Manager Documentation Library. collections are a grouping of one or more computers. see the section. update the distribution points where these images and packages are stored. 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. the task sequences must be advertised to a collection of target computers. 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. see the following sections in Configuration Manager Documentation Library. which is installed with System Center Configuration Manager. For more information about managing distribution points.

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

Preparing the prerequisite infrastructure as described in Prepare the Prerequisite Infrastructure for UDI Deployments. Preparing for UDI deployment to the target computers as described in Preparing for UDI Deployments to Target Computers. Perform UDI deployments by: • • • Preparing the UDI deployment environment as described in Preparing the UDI Deployment Environment. within a Windows workgroup. Enable Configuration Manager Console integration with MDT 2010 as described in Enable Configuration Manager Console Integration. 2. Preparing for UDI deployment to the reference computer as described in Preparing for UDI Deployment to the Reference Computer. or upgrade an existing instance of MDT 2008 to MDT 2010 as described in Install or Upgrade to MDT 2010 for UDI. Obtain the software that UDI requires as described in Obtain the Software Required by the UDI Deployment Process. or from removable media. To prepare the MDT 2010 deployment environment for UDI deployments 1. Install and configure the UDI web service. 5. Install a new instance of MDT 2010 on the deployment server. 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. Ensure that your new or existing System Center Configuration Manager infrastructure is specifically optimized for the Operating System Deployment feature. • • Preparing the UDI Deployment Environment After you have prepared the prerequisite infrastructure for MDT 2010. 3. . 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.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. 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.

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

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

3. The URL Rewrite Module.5 is installed. Table 128.NET Framework version 3. You can install and configure the UDI web service on one or more computers to provide fault tolerance and scalability. 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. 2. Configure user access for publishing to the UDI web service as described in Configure Publishing Access to the UDI Web Service. The Web Services (IIS) server role is installed with the role services listed in Table 128. Microsoft . To install and configure the UDI web service 1. 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. 4. The UDI web service acts as a central repository for the applications to be discovered during the Application Discovery preflight check. Verify that the target computer meets or exceeds the UDI web service prerequisites as described in Verify the Prerequisites for the UDI Web Service. 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. Install the UDI web service using the UDI Web Services and Database Installation Wizard as described in Install the UDI Web Service. Verify the Prerequisites for the UDI Web Service Before installing the UDI web service. During the Application Discovery preflight check on the target computer.com/technet/SolutionAccelerators .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.

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 .com/technet/SolutionAccelerators Client Certificate Mapping Authentication Not installed .253 Microsoft Deployment Toolkit 2010 Update 1 Role service HTTP Errors HTTP Redirection Application Development ASP.

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. and the OSD database in SQL Server. Complete the UDI Web Services and Database Installation Wizard using the information in Table 129. Table 129. This wizard creates the OSDConfigService virtual directory in Microsoft Internet Information Services (IIS). Accept the default values unless otherwise specified. and then point to All Programs.com/technet/SolutionAccelerators . The virtual directories are databases that the UDI web service uses to store setup configuration that UDI employs. 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. and then click Install UDI Config Service. Point to Microsoft Deployment Toolkit. Click Start. the OSDConfigServiceSimple virtual directory in IIS. microsoft. The UDI Web Services and Database Installation Wizard starts. Click I accept the terms in the License Agreement. To install the UDI web service 1. and then click Next. which UDI deployments use. 2.

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

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

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

Create a collection that contains the reference computer as described in Managing Computer Collections in Configuration Manager Console. 5. operating system packages. Optionally. To deploy to and capture an image of the reference computer 1. which is the same process for UDI and ZTI deployments. 2. advertise the task sequence to the reference computer and start the reference computer with the bootable Windows PE image created earlier in the process. Prepare network shares for storing migration data and MDT 2010 deployment logs as described in Preparing the MDT 2010 Migration Resources. and applications to the reference computer. 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 then capture an image of the reference computer. Start the reference computer with the task sequence bootable media disk as described in Deploying an Operating System Using Task Sequence Bootable Media. Solution Accelerators microsoft. Create an advertisement for the reference computer task sequence as described in Managing Advertisements in Configuration Manager Console. which is the same process for UDI and ZTI deployments. ensure that the necessary deployment resources exist.com/technet/SolutionAccelerators . which is the same process for UDI and ZTI deployments. and customize the MDT 2010 deployment process. 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. device drivers. The task sequence created earlier will deploy the target operating system. 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. which is the same process for UDI and ZTI deployments. deploy them to the target computers. 3.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. 4. Create a task sequence bootable media disk by using the Task Sequence Media Wizard as described in Creating Task Sequence Bootable Media. In preparation for deploying the captured images to the target computers. To prepare for UDI deployment to target computers 1. 2. create one or more task sequences for deploying the captured images.

To prepare for the New Computer deployment scenario to target computers 1. For more information about MDT 2010 deployment scenarios. you deploy a new installation of a Windows operating system to a new computer. Use the User-Driven Installation task sequence template to deploy the captured image of the reference computer to the target computer.com/technet/SolutionAccelerators Solution Accelerators . There is no user migration information to save and restore and no existing file systems to preserve. which is the same process for UDI and ZTI deployments. 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. 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. Prepare the UDI task sequences. the MDT 2010 configuration files. 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. Prepare for the New Computer Deployment Scenario to Target Computers Using UDI In the New Computer deployment scenario. the Operating System Deployment (OSD) Setup Wizard configuration files. Tip Create the task sequence for deploying to the reference computer based on the UserDriven task sequence template included in MDT 2010. 4. 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. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. see Identifying Deployment Scenarios. Create additional distribution points to help in larger deployments as described in Managing Distribution Points in Configuration Manager Console. 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. Table 130. any combination of these deployments scenarios might be necessary.259 Microsoft Deployment Toolkit 2010 Update 1 3. • Depending on the target computers in your organization. microsoft.

9. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. 3. select the appropriate distribution points for the network. which is the same process for UDI and ZTI deployments. Note Most production networks have multiple distribution points. which is the same process for UDI and ZTI deployments. including operating system deployment packages. Update the distribution points so that any changes to the packages 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. When performing this step in a production environment. 6. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. Ensure that all packages. which is the same process for UDI and ZTI deployments. Solution Accelerators microsoft. When performing this step in a production environment. 7. When performing this step in a production environment. 5. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 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. select the appropriate distribution points for the network. 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. 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.com/technet/SolutionAccelerators . Note Most production networks have multiple distribution points. Ensure that all packages. including operating system deployment packages. select the appropriate distribution points for the network.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 260 2. 8. 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). Optionally. • 4. 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. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console.

Optionally.com/technet/SolutionAccelerators • . 3. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. 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.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. customize the MDT 2010 configuration files or the MDT DB to the needs of your organization as described in: • Configuring MDT 2010 Deployments. Table 131. 2. 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. 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. 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. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 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. There is user migration information to save and restore but no existing file systems to preserve. To prepare for the Refresh Computer deployment scenario to target computers 1. including computers that must be re-imaged for image standardization or to address a problem. which is the same process for UDI and ZTI deployments. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. which is the same process for UDI and ZTI deployments. a computer is refreshed. • Performing Deployments Using the MDT DB. Solution Accelerators microsoft. 4.

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

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. • Depending on the target computers in your organization. which is the same process for UDI and ZTI deployments. Deploy Captured Images to Target Computers in the Refresh Computer Deployment Scenario Using UDI. 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.263 Microsoft Deployment Toolkit 2010 Update 1 3. 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. To deploy the capture images to the target computers in the New Computer Deployment Scenario Using UDI 1. which is the same process for UDI and ZTI deployments. 5. At the end of the process. Solution Accelerators microsoft. Complete the Task Sequence Wizard. Either method starts Windows PE on the target computer and initiates the UDI deployment process.com/technet/SolutionAccelerators . the captured image of the reference computer is deployed on the target computer. 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. Start the target computer with the task sequence bootable media created earlier in the process or from Windows Deployment Services. 2. 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. see Identifying Deployment Scenarios. Create an advertisement for the target computer task sequences as described in Managing Advertisements in Configuration Manager Console. 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. For more information about the MDT 2010 deployment scenarios. any combination of deployments scenarios might be necessary. The Task Sequence Wizard starts.

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

which is the same process for UDI and ZTI deployments.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. which is the same process for UDI and ZTI deployments. 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. Managing device drivers for UDI deployments in the Configuration Manager Console as describe in Managing Device Drivers 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. 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. Managing software packages for UDI in the Configuration Manager Console as described in Managing Software Packages in Configuration Manager Console. You use the Deployment Workbench in UDI deployments only to configure the MDT DB. Managing computer collections for UDI as described in Managing Computer Collections in Configuration Manager Console. 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. Deploying an operating system using task sequence bootable media as described in Deploying an Operating System Using 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. You can use the UDI Wizard Designer to configure the behavior of the Operating System Deployment (OSD) Setup Wizard. 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. Managing advertisements for UDI as described in Managing Advertisements in Configuration Manager Console. which is the same process for UDI and ZTI deployments.

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. Configuring individual UDI task sequence steps as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. 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. the file name for each template.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 266 • Managing distribution points for UDI as described in Managing Distribution Points in Configuration Manager Console. 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 UDI task sequence steps that perform server role–related actions as described in Configuring Server Role Task Sequence Steps for ZTI. • Identify the UDI Task Sequence Templates in MDT 2010 Table 133 lists the UDI task sequences templates included in MDT 2010. 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. 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. and a description of the template. MDT 2010 includes task sequence templates that you can use to deploy the reference and target computers.com/technet/SolutionAccelerators Solution Accelerators . Table 133.xml Select this template to Deploy to target computers using UDI for all scenarios except the Replace Computer microsoft. 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).

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. Table 134. In the Actions pane. Note Always use the Create Microsoft Deployment Task Sequence Wizard to create task sequences. 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. Although you can manually import the task sequence templates.com/technet/SolutionAccelerators Solution Accelerators . 2. 3. and then click ConfigMgr Console. doing so is not recommended. In The following SCCM task sequence templates are available.267 Microsoft Deployment Toolkit 2010 Update 1 Template Sequence File name Select this template to scenario. Although you can manually create the task sequences. After completing the wizard. Note Always use the Create Microsoft Deployment Task Sequence Wizard to create task sequences based on the MDT 2010 task sequence templates. point to Configuration Manager 2007. Accept the default values unless otherwise specified. as described in Identify the Packages and Images Required by the MDT 2010 Task Sequence Templates. click Create Microsoft Deployment Task Sequence. To create a UDI task sequence using the Create Microsoft Deployment Task Sequence Wizard 1. Point to Microsoft System Center. the new task sequence references the appropriate packages and images. and then point to All Programs. go to Site Database/Computer Management/Task Sequences. doing so is not recommend. In the Configuration Manager Console console tree. 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. 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. Complete the Create Microsoft Deployment Task Sequence Wizard for creating a UDI task sequence using the information in Table 134. select task_sequence_template (where microsoft. Click Start. 4. The Create Microsoft Deployment Task Sequence Wizard starts.

Choose Template: General 1.com/technet/SolutionAccelerators Choose Template: Details Solution Accelerators . In Task sequence comments. 3. The other option is Join a workgroup. In Password and Confirm password. In User name. type password (where password is the password for the user account). d. In Domain. 1. 2. In the Windows User Account dialog box. Click Set. The Windows User Account dialog box appears. 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. If you select this option. This account must be a member of the Domain Admins group in the domain or have sufficient delegated permissions). type domain_name (where domain_name is the name of the workgroup to join). b. 3. Click Next. and then click OK. type task_sequence_name (where task_sequence_name is the name of the task sequence displayed in the Configuration Manager Console). In Task sequence name. If you select this option. in User name. Select Join a workgroup. Click Next. c. 2. type user_name (where user_name is the name of the registered user that appears in the Windows operating system microsoft. in Workgroup.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 workgroup_name (where workgroup_name is the name of the workgroup to join). 2. Click Join a domain. perform the following steps: a. type comment (where comment is descriptive text that describes the purpose of the task sequence). The other option is Join a domain.

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

In Name. and then click OK.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. 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. The other option is Create a new boot image package. type version_number (where version_number is the version number to be assigned to the boot image package).com/technet/SolutionAccelerators . In Version. 1. 3. If you select this option. Ensure that the Configuration Manager service account has the appropriate permission on this network shared folder. In Select a Package dialog box. In Comments. Click Next. 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. Click Next. b. type package_name (where package_name is the name to be given to the boot image package). perform the following steps: a. The Configuration Manager service account must have permission to modify the contents of this UNC path to update the boot images. The other option is Create a new boot image 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). If you select this option. Select Specify an existing boot image. 3. Select Create a new boot image package. click package_name (where package_name is the name of the existing boot image). 2. 4. 2. microsoft. The Select a Package dialog box appears. 1. Tip You can also click Browse to locate the UNC path. Click Browse. in Package source to be created. type comment_text (where comment_text is descriptive information about the boot image package).

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

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

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

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). Select Create a new OS install package. b. 1. 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). 2. In OS installation folder location. Tip You can also click Browse to locate the UNC path. In Comments. 3. 5. Click Next. In Name. type package_name (where Solution Accelerators microsoft.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). 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. or Specify an existing OS installation package. Tip You can also click Browse to locate the UNC path. In the Select a Package dialog box.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 274 On this wizard page Do this b. If you select this option. Note The OS installation folder contents are copied from the specified UNC location to the package source folder. In Name. perform the following steps: a. Create a new OS image. OS Image: Image Details Note This wizard page appears only if you select Create a new OS image on the OS Image wizard page. 4. In Version. and then click OK. which are then used to create the package. 1. type comment_text (where comment_text is descriptive information about the package). In Package source folder to be created. 4. Click Next. The other options are Specify an existing OS image.

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

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

b. perform the following steps: a. Click Next. 3. type comment_text (where comment_text is descriptive information about 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. In Version. 2. 1.com/technet/SolutionAccelerators . 3. Click Next. type package_name (where package_name is the name to be given to the package). In Name. Solution Accelerators microsoft. The other option is Specify an existing settings package. 6. 4. 5. Tip You can also click Browse to locate the path. In Comments. If you select this option. type version_number (where version_number is the version number to be assigned to the package). In Language. 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 path (where path is the fully qualified path for the location of the folder in which the USMT source files reside). In Path to USMT executables and related files.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). type language (where language is the language of the package). Tip You can also click Browse to locate the UNC path. and then click OK. Summary Click Next. Click Create a new settings package. type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package). 2. In Package source to be created. In Manufacturer.

xml file for each set of configuration settings for the Operating System Deployment (OSD) Setup Wizard. 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. 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. The Create Microsoft Deployment Task Sequence Wizard closes when the UDI task sequence is created. 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. 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 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. 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. Note Create a separate version of the UDIWizard_Config. 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. You can customize the UDIWizard_Config. microsoft.xml file.xml file as described in Override the Configuration File Used by the Operating System Deployment (OSD) Setup Wizard. 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.com/technet/SolutionAccelerators • • • • • • • Solution Accelerators .xml file 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. 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 UDI Wizard task sequence step to use a file other than the UDIWizard_Config.

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. • • • • • • • 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. 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. 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. Tip Create a new MDT 2010 files package and corresponding package source for each unique configuration of the UDIWizard_Config. 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.com/technet/SolutionAccelerators . Create a new Operating System Deployment (OSD) Setup Wizard configuration file 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.xml file in the Scripts folder of the MDT 2010 files package specified in the task sequence. • 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. Configure the behavior of the Application Discovery preflight check as described in Configure Application Discovery Preflight Check Behavior. 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. To create a new Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer Solution Accelerators microsoft.xml file.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.

Point to Microsoft Deployment Toolkit. 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. In the Save As dialog box. and then point to All Programs. 2. To open an existing Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer 1. create a new task sequence or modify an existing task sequence steps to use the appropriate MDT 2010 files package. and then click UDI Wizard Designer. and then click Save Configuration As. click File. and then click New Configuration.xml file in the Scripts folder of the MDT 2010 files package specified in the task sequence. Make the appropriate changes to the configuration file in the UDI Wizard Designer console. and then click UDI Wizard Designer. click File. go to folder_path (where folder_path is the fully qualified path to the Scripts folder in the MDT 2010 files package source). 5. 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). 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. In the UDI Wizard Designer console. 4. click File. In the Open dialog box. 4. Click Start. The UDI Wizard Designer starts. 2. click File. Open an existing Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer. and then click Open Configuration.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 280 1. The UDI Wizard Designer starts. Point to Microsoft Deployment Toolkit. type file_name (where file_name is the file name for the configuration file). 5. In the UDI Wizard Designer console. After creating the new Operating System Deployment (OSD) Setup Wizard configuration file. In the UDI Wizard Designer console. Click Start. and then click Open. Make the appropriate changes to the configuration file in the UDI Wizard Designer console. and then click Save. 3. and then click Save Configuration As. 3. click file_name (where file_name is the file name for the configuration file). in File name. In the UDI Wizard Designer console. Solution Accelerators microsoft.com/technet/SolutionAccelerators .

and then click Open Remote Configuration. In the Open Remote Configuration dialog box. Publishing to the UDI web service allows centralized management and access to the configuration file. in File name. The UDI Wizard Designer starts. 3. the configuration file can be updated without having to update Configuration Manager packages. In the Save As dialog box. create a new task sequence or modify an existing task sequence steps to use the appropriate MDT 2010 files package (if necessary). and then click Save. Publishing to the UDI web service allows centralized management and access to 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. In the Open Remote Configuration dialog box. 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). and then point to All Programs. and then click OK. click file_name (where file_name is the file name for the configuration file). and then click Connect. In the UDI Wizard Designer console. in Specify root service URI. Point to Microsoft Deployment Toolkit. 4. Also. 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. click File. After modifying the existing Operating System Deployment (OSD) Setup Wizard configuration file. go to folder_path (where folder_path is the fully qualified path to the Scripts folder in the MDT 2010 files package source). To open an Operating System Deployment (OSD) Setup Wizard configuration file from a UDI web service using the UDI Wizard Designer 1. in the list box.com/technet/SolutionAccelerators . A list of available files appears in the list box. the configuration file can be updated without having to update Configuration Manager packages. Solution Accelerators microsoft. type file_name (where file_name is the file name for the configuration file). 2.281 Microsoft Deployment Toolkit 2010 Update 1 6. 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. Click Start. and then click UDI Wizard Designer. Also.

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

in the navigation pane. and then click UDI Wizard Designer. 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. 6. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. click Wizard. Click Start.wsf” /definition:path\file_name. Table 135. 3. and then point to All Programs. 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.wsf. Configure the Welcome page behavior using the UDI Wizard Designer. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. Click OK.xml.exe “%DeployRoot%\Scripts\UDIWizard. In the Workspace pane. To configure the Welcome page behavior using the UDI Wizard Designer 1. 7.283 Microsoft Deployment Toolkit 2010 Update 1 4. The line wrap seen here is the result of document formatting constraints. 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. 5. and then click Welcome Page. 4. configure the settings listed in Table 135 based on the requirements of your organization. substituting State Capture with Preinstall/New Computer Only. Point to Microsoft Deployment Toolkit. Repeat steps 3 and 4. Repeat steps 3 and 4 for any custom task sequence steps that run UDIWizard.com/technet/SolutionAccelerators . Note The above text appears on one line. In the UDI Wizard Designer console. 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. On the Properties tab for the UDI Wizard task sequence step in Command line.

If selected.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. Table 136. 7. • Disabled. then only the file name needs to be specified. configure the settings listed in Table 136 based on the requirements of your organization. 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. Solution Accelerators microsoft. Even if this option is selected. In the Tasks pane. the wizard page is not displayed. Close UDI Wizard Designer. 5.exe. the wizard page will be displayed if: • There are problems with the configuration settings on the page. Contains the path relative to the folder in which OSDSetupWizard. configure the behavior for other wizard pages. For example. If selected. and any configuration settings on the page are not set. After completing the settings for this wizard page’s behavior. the wizard page is not displayed when there are no problems with the configuration settings on the page. 6. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. and any configuration settings entered on the page are set. • Silent. If selected. if the file is in the same folder as OSDSetupWizard. the wizard page is displayed.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 284 Setting Welcome Banner Description Welcome page in the Operating System Deployment (OSD) Setup Wizard. • The task sequence variables that relate to the fields on the page are not set.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. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. configure the settings listed in Table 137 based on the requirements of your organization. in the navigation pane. and then click UDI Wizard Designer. configure the settings listed in Table 138 based on the requirements of your organization. 3. In the Workspace pane. click Wizard. In the UDI Wizard Designer console.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. and then point to All Programs. Configuration Settings for the Preflight Page in the Tasks Pane Solution Accelerators microsoft. Click Start. 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. To configure the Preflight page behavior using the UDI Wizard Designer 1. The preflight checks are performed in the order they appear. Table 137. 2. In the Tasks pane. Table 138. 4. 5. You can add one or more items to the list. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. and then click Preflight Page. Theses checks help ensure that the system resources and configuration of the target computer are adequate to perform the deployment. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File.com/technet/SolutionAccelerators . Configure the Preflight page behavior using the UDI Wizard Designer. from the top of the list to the bottom of the list. Point to Microsoft Deployment Toolkit.

• Disabled. the wizard page is not displayed. If selected. and any configuration settings on the page are not set. • The task sequence variables that relate to the fields on the page are not set.com/technet/SolutionAccelerators . Even if this option is selected. Moves the selected item later in the order in which the preflight checks are performed. Configuration Settings for the Preflight Checks Dialog Box Solution Accelerators microsoft. If selected. If selected. Controls the position of a preflight check in the list and includes the following tasks: • Move Up. Removes a selected preflight check from the list. the wizard page will be displayed if: • There are problems with the configuration settings on the page. • Remove Preflight. • Silent. • One of the preflight checks encounters an error or warning. Move Down. • Edit Preflight. Adds a new preflight check to the list using the Preflight Checks dialog box as described in Table 139. Moves the selected item earlier in the order in which the preflight checks are performed. Modifies the configuration settings for a preflight check in the Preflight Checks dialog box as described in Table 139.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. Controls which items appear in the Preflight Configuration list in the Workspace pane and includes the following tasks: • Add Preflight. Table 139. the wizard page is not displayed when there are no problems with the configuration settings on the page. Preflight Options Preflight Order • Table 139 lists the configuration settings in the Preflight Checks dialog box. the wizard page is displayed.

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

If this check box is: microsoft. and domain or workgroup membership. and then click UDI Wizard Designer. configure the settings listed in Table 140 based on the requirements of your organization. the user credentials. this check box is selected.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. the Operating System Deployment (OSD) Setup Wizard will validate the user credentials.com/technet/SolutionAccelerators Solution Accelerators .xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. 3. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. If this check box is: • Selected. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. In the UDI Wizard Designer console. 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. in the navigation pane. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Point to Microsoft Deployment Toolkit. • Cleared. Note By default. In the Workspace pane. and then click Computer Page. Click Start. 4. Table 140. To configure the Computer page behavior using the UDI Wizard Designer 1. 2. and then point to All Programs. the Operating System Deployment (OSD) Setup Wizard will not validate the user credentials. 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. Configure the Computer page behavior using the UDI Wizard Designer. click Wizard.

The following button affects the contents of the text box: • Clear. • Default. The following buttons affect the contents of the text box: • Clear. this check box is selected. Sets the domain currently selected in the Domains list box as the default domain. Modifies the configuration settings for a domain in the Domain Configuration dialog box as described in Table 141. Contains a list of domains to which computers can be joined and includes the following buttons: • Add Domain. Note By default.com/technet/SolutionAccelerators . default list.289 Microsoft Deployment Toolkit 2010 Update 1 Setting Description • Selected. Clears the contents of the list of characters that generate a warning if included. the Operating System Deployment (OSD) Setup Wizard will not validate the ownership of the computer object. • Edit Domain. Clears the contents of the list of invalid characters. Deletes a selected domain from the list. Set the contents of the list of invalid characters to a predefined. the Operating System Deployment (OSD) Setup Wizard will validate the ownership of the computer object. • 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. 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. Contains a list of organizational units that exist in the selected default domain. • Set Default Domain. • Cleared. Adds a domain to the list using the Domain Configuration dialog box as described in Table 141. this text box includes the default invalid characters. Note By default. 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.

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

Table 142. and any configuration settings on the page are not set. Even if this option is selected.com/technet/SolutionAccelerators Computer Name Field Solution Accelerators . the wizard page is not displayed. Contains a list of the OUs that are available for placement of computer objects. configure the settings listed in Table 142 based on the requirements of your organization. Controls the behavior of the Computer Name text box on the wizard page and includes the following tasks: • Enabled. 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. and any configuration settings entered on the page are set. the wizard page will be displayed if: • There are 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. • Disabled. Prevents the contents of the Computer Name text box from being modified. • The task sequence variables that relate to the fields on the page are not set. 5. If selected. Allows the contents of the Computer Name text box to be modified. microsoft. • Disabled. In the Tasks pane. If selected. Contains an optional name that is displayed in the Domains list in the Workspace pane. the wizard page is not displayed when there are no problems with the configuration settings on the page. • Silent. the wizard page is displayed. If selected. Contains the friendly name of the OU selected in the Available OUs list. Contains the distinguished name of the OU selected in the Available OUs list.

Allows the item selected in the OU list box to be modified.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. Allows the item selected in the Domain list box to be modified. • Disabled. Move Down. Controls the behavior of the User name text 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. Prevents the contents of the Password text box from being modified. 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. Moves the selected item later in the order in which the OUs appear.com/technet/SolutionAccelerators OU Field User Name Password Workgroup Field OU Order Solution Accelerators . Controls the behavior of the Password text box on the wizard page and includes the following tasks: • Enabled. Controls the position of an OU in the Organizational Units list and includes the following tasks: • • Move Up. • Disabled. • Disabled. Allows the contents of the User Name text box to be modified. Prevents the item selected in the OU list box from being modified. Prevents the contents of the Workgroup text box from being modified. Prevents the item selected in the Domain list box from being modified. microsoft. • Disabled. Prevents the contents of the User name text box from being modified. • Disabled. Allows the contents of the Password text box to be modified. Allows the contents of the Workgroup text box to be modified.

and then point to All Programs.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File.com/technet/SolutionAccelerators Solution Accelerators . 4. and then click User Configuration. the Operating System Deployment microsoft. 7. Table 143. click Wizard. configure the settings listed in Table 143 based on the requirements of your organization. To configure the User Configuration page behavior using the UDI Wizard Designer 1. In the UDI Wizard Designer console. 2. If this check box is: • Selected.293 Microsoft Deployment Toolkit 2010 Update 1 6. 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. • Cleared. Configure the User Configuration page behavior using the UDI Wizard Designer. configure the behavior for other wizard pages and then save the Operating System Deployment (OSD) Setup Wizard configuration file. and then click UDI Wizard Designer. Click Start. After completing the settings for the behavior of this wizard page. 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. 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. In the Workspace pane. 3. the Operating System Deployment (OSD) Setup Wizard will allow the addition of existing accounts to the local Administrators group of the target computer. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. in the navigation pane. Point to Microsoft Deployment Toolkit. Close UDI Wizard Designer.

If selected. 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. • Disabled. the wizard page is not displayed when there are no problems with the configuration settings on the page. configure the behavior for other wizard pages. Admin Password Field 6. Prevents the contents of the Administrator password and Confirm password text boxes from being modified. the wizard page is not displayed and any configuration settings on the page are not set. If selected. If selected. • Disabled. the wizard page is displayed and any configuration settings entered on the page are set. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. Allows the contents of the Administrator password and Confirm password text boxes to be modified. • Silent. Solution Accelerators microsoft. 5. configure the settings listed in Table 144 based on the requirements of your organization. Even if this option is selected the wizard page will be displayed if: • There are problems with the configuration settings on the page. Controls the behavior of the Administrator password and Confirm password text boxes on the wizard page and includes the following tasks: • Enabled. this check box is selected.com/technet/SolutionAccelerators . In the Tasks pane.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. After completing the settings for the behavior of this wizard page. • The task sequence variables that relate to the fields on the page are not set. Table 144. Note By default.

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

If selected.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. • Disabled.com/technet/SolutionAccelerators Solution Accelerators . • The task sequence variables that relate to the microsoft. the wizard page is not displayed. and no configuration settings on the page are set. 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. Select the default input locale This list box selects the default input locale. the wizard page is displayed. 5. If selected. Note The default values selected here can be overridden in the UDI Wizard if the Language page and the Language 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. Select the default keyboard locale This list box selects the default keyboard locale. 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. Select the default timezone This list box selects the default time zone. the wizard page is not displayed when there are no problems with the configuration settings on the page. Even if this option is selected. • Silent. configure the settings listed in Table 146 based on the requirements of your organization. Table 146. and any configuration settings entered on the page are set. If selected. the wizard page will be displayed if: • There are problems with the configuration settings on the page. In the Tasks pane.

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

Solution Accelerators microsoft. click Wizard.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. Click Start. In the UDI Wizard Designer console. and then click UDI Wizard Designer. Configure the Volume page behavior using the UDI Wizard Designer. In the Workspace pane. Point to Microsoft Deployment Toolkit. Table 147. 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. If this check box is: • Selected. To configure the Volume page behavior using the UDI Wizard Designer 1. 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. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. configure the settings listed in Table 147 based on the requirements of your organization. and then click Volume Page. 3. in the navigation pane. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. see Available Language Packs. the Operating System Deployment (OSD) Setup Wizard defaults to formatting the target volume during installation on the target computer.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. 4. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. 2.com/technet/SolutionAccelerators . and then point to All Programs.

com/technet/SolutionAccelerators . WIM Index Architecture 5.299 Microsoft Deployment Toolkit 2010 Update 1 Setting Description • Cleared. Deletes the selected operating system image item from the list. 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. In the Tasks pane. Contains the processor architecture of the operating system image and can be either x86 or amd64. 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. Contains the index to the image being deployed from the WIM file. 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. the Operating System Deployment (OSD) Setup Wizard does not default to formatting the target volume during installation on the target computer. as described in 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. 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. • Delete. Adds an operating system image item to the list using the Add Image Index dialog box. Table 149. Table 148. this check box is cleared. Note By default.

If selected. Allows the contents of the Volume list box to be modified. • Disabled. • Silent. Even if this option is selected the wizard page will be displayed if: • There are problems with the configuration settings on the page. If selected. 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. Controls the behavior of the Volume list box on the wizard page and includes the following tasks: • Enabled. • Disabled. Prevents the contents of the Windows Directory list box from being modified. the wizard page is displayed. and any configuration settings entered on the page are set. If selected. 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 task sequence variables that relate to the fields on the page are not set.com/technet/SolutionAccelerators Disk Volume Field Windows Directory Field Disk Format Field Solution Accelerators . • Disabled. Controls the behavior of the Windows Directory list box on the wizard page and includes the following tasks: • Enabled. Allows the contents of the Image Selection list box to be modified. Prevents the contents of the Volume list box from being modified. the wizard page is not displayed. the wizard page is not displayed when there are no problems with the configuration settings on the page. • Disabled. and any configuration settings on the page are not set. Image Selection Field Controls the behavior of the Image Selection list box on the wizard page and includes the following tasks: • Enabled. Prevents the contents of the Image Selection list box from being modified.

• Disabled. Allows the contents of the Format: Clean all data on the target volume during install check box to be modified. Table 150.301 Microsoft Deployment Toolkit 2010 Update 1 Setting Description • Enabled. Configure Application Discovery Preflight Check Behavior In the Refresh Computer deployment scenario. The /readcfg: parameter: • Can reference a local file: /readcfg:. and then save the Operating System Deployment (OSD) Setup Wizard configuration file.com/technet/SolutionAccelerators Solution Accelerators .. configure the behavior for other wizard pages. The mapping between existing applications and the applications to be deployed is managed on the Mappings tab in the Application Details dialog box. After completing the settings for the behavior of this wizard page. 6. 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. the Operating System Deployment (OSD) Setup Wizard contains a preflight check—the Application Discovery preflight check—which scans the target computer for existing applications. 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. 7.xml • Can reference a UDI web service: / microsoft. Table 150 lists the Application Discovery preflight check parameters that must be configured for the preflight and a description of each parameter. 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. Close UDI Wizard Designer. Prevents the contents of the Format: Clean all data on the target volume during install check box from being modified. The UDI web service.\MyFolder\WoodgroveApps01. 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.

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

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

the wizard page is not microsoft.exe resides and file name for the file that was generated during the Application Discovery preflight check. In the Tasks pane. The Install Multiple Applications task sequence step will read the applications variable starting with <base variable name>001 to <base variable name>999. Root Application Group Name Contains the name of the root container for all the application groups specified in the Groups list box. 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. configure the settings listed in Table 153 based on the requirements of your organization.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. Contains a list of all the applications groups and the applications associated with each group. which is in the format of <base variable name>001. • Disabled. Group list box 5. There is a maximum of 999 applications that can be selected through the Operating System Deployment (OSD) Setup Wizard. If selected.com/technet/SolutionAccelerators Solution Accelerators . Table 153. When this group is selected or cleared in the Operating System Deployment (OSD) Setup Wizard. If selected. all child groups and applications will be selected or cleared in the Operating System Deployment (OSD) Setup Wizard. Alternate Application Contains the path relative to the folder in which Configuration Path OSDSetupWizard. Use the Add Group and Delete Group tasks to modify the contents of this list as described in Table 138. 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. and any configuration settings entered on the page are set.

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

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

and then point to All Programs. 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. see “Install Multiple Applications” in Install Software. configure the settings listed in Table 156 based on the requirements of your organization. 5. Configure the OSD Applications page using the UDI Wizard Designer.com/technet/SolutionAccelerators . Solution Accelerators microsoft. 7. configure the behavior for other wizard pages. For more information. 2. 6.xml file that you wish to configure) as described in: • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. After completing the settings for the behavior of this wizard page. Click Start. In the Tasks pane. and then click UDI Wizard Designer. 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. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Close UDI Wizard Designer. Point to Microsoft Deployment Toolkit. 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.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. and then save the Operating System Deployment (OSD) Setup Wizard configuration file. Table 156. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. To configure the OSD Applications page using the UDI Wizard Designer 1.

as described in Table 158. 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. In the UDI Wizard Designer console. • 5. 4. configure the settings listed in Table 158 based on the requirements of your organization. Table 161. Table 160. Contains detailed information about the application selected in the Choose the application you would like to enable in OSD list box. and then click OSD Applications. 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 160. • Edit. configure the settings listed in Table 157 based on the requirements of your organization. In the Tasks pane. In the Workspace pane. in the navigation pane. Table 161.com/technet/SolutionAccelerators Application Settings Solution Accelerators . Table 158. Controls if the check box that corresponds to the item selected in the Choose the application you microsoft. and Table 162. 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. and Table 162. 3.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 308 Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. Table 157. click Application. Use the Add. 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. Removes the item selected in the list box. • Remove. Edit and Remote tasks in Applications Items in the Tasks pane to modify the contents of this list.

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. This prevents 32-bit installations of the applications. Removes any references to a specific System Center Configuration Manager program to the application for 32-bit installations. The following buttons affect the content displayed: • Attach. 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. • Lock selection. 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). Toggles the Mark as selected application item state for the item selected in the list box. This enables 32-bit installations of the application. Attaches a specific System Center Configuration Manager program to the application for 32-bit installations using the Configuration Manager Packages dialog box. Attaches a specific System Center Configuration Manager program to the microsoft. • Clear. Toggles the Selection locked application item state for the item selected in the list box. Table 159. then the Install Software page in the Operating System Deployment (OSD) Setup Wizard will be populated using the XML file.com/technet/SolutionAccelerators 64-bit Program Properties Solution Accelerators . 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. and the Application Details list box does not change the Selection Locked application item state.

This enables 64-bit installations of the application. • Clear. the check box for the application is selected by default. The groups are created and managed on the Settings and Groups page in UDI Wizard Designer. • Cleared. the check box for the application is cleared by default.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 310 Setting Description application for 64-bit installations using the Configuration Manager Packages dialog box. 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. This prevents 64-bit installations of the applications. the state of check box for the application cannot be changed on the Software Installation wizard page. 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. 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 . 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 state of check box for the microsoft. Removes any references to a specific System Center Configuration Manager program to the application for 64-bit installations. • Cleared. If this check box is: • Selected.

such as Microsoft Office 2010 replacing the 2007 Office system. 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. 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. Adds an application dependency or exclusion to the list using the Add Application Dependencies dialog box. 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). • Dependency type. The Add Application Dependencies dialog box has the following settings: • List of applications. Contains a list of the applications. Removes the application dependency or exclusion selected in the list. Table 161. • Remove. Click to select an application as a dependency or exclusion. The mapping is based on the Windows Installer product code for the application being microsoft. Table 160. 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). The following buttons are used to modify the contents of this list: • Add. 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).com/technet/SolutionAccelerators Solution Accelerators .311 Microsoft Deployment Toolkit 2010 Update 1 Setting Description application can be changed on the Software Installation wizard page.

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

configure the behavior for other wizard pages and then save the Operating System Deployment (OSD) Setup Wizard configuration file. and then click UDI Wizard Designer. 7. Removes the WMI query selected in the list. Close UDI Wizard Designer. and then point to All Programs. The following buttons are used to modify the contents of this list: • Add. see Querying with WQL. 6. Click Start. The WMI Filters dialog box has the following settings: • WMI Namespace. Contains the name of the WMI namespace to be used for the WMI query specified in Query. After completing the settings for the behavior of this wizard page.com/technet/SolutionAccelerators Solution Accelerators . • Query. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. Contains the WMI query to be performed in the WMI namespace specified in WMI Namespace. For more information about creating WMI queries. Configure the Summary page behavior using the UDI Wizard Designer.xml file that you wish to configure) as described in: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. microsoft. Adds a WMI query to the list using the WMI Filters dialog box. 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. Point to Microsoft Deployment Toolkit. To configure the Summary page behavior using the UDI Wizard Designer 1.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. 2. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. • Remove.

Point to Microsoft Deployment Toolkit. To preview the Operating System Deployment (OSD) Setup Wizard behavior using the UDI Wizard Designer 1. Solution Accelerators microsoft. the wizard page is not displayed. • Disabled. the wizard page will be displayed if: • There are problems with the configuration settings on the page. the wizard page is displayed. and then point to All Programs. 5. • Silent. and then click Summary Page. configure the settings listed in Table 163 based on the requirements of your organization. If selected. In the UDI Wizard Designer console. and any configuration settings on the page are not set. 4. In the Tasks pane. If selected. Table 163. 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. and then click UDI Wizard Designer. and any configuration settings entered on the page are set. 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. Click Start. click 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. in the navigation pane.com/technet/SolutionAccelerators . If selected. Even if this option is selected. After completing the settings for the behavior of this wizard page. 6. The preview feature allows you to preview the configuration and behavior settings that you have made in the UDI Wizard Designer. • The task sequence variables that relate to the fields on the page are not set. configure the behavior for other wizard pages.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 314 3. Close UDI Wizard Designer.

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

review the information provided on the page. Each deployment scenario (New Computer or Refresh Computer) uses a different process.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. Note UDI task sequences start with the Confirmation to Partition Disk task sequence step. 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. 3.xml in the Scripts folder of the MDT 2010 files package.vbs script. the Operating System Deployment (OSD) Setup Wizard starts. which allows you to confirm partitioning and disk formatting on the target computer. Complete the Task Sequence Wizard by selecting the appropriate UDI task sequence. Initiate the deployment from Windows Deployment Services or using task sequence bootable media. The deployment process prompts for any configuration settings not already specified. run the Operating System Deployment (OSD) Setup Wizard. The task sequence step runs the ZTIConfirmDiskpart. 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. On the Welcome wizard page. Windows PE starts. and then click Next. and then the Task Sequence Wizard starts. 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. This wizard page is shown if: • The Page Behavior for the Welcome Page is configured to Enabled or Disabled in the UDI Wizard Designer. 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. . The logic for displaying (or not displaying) a wizard page is noted for each wizard page in the following steps. To deploy the new operating system to the target computer using the Operating System Deployment (OSD) Setup Wizard 1. This feature is found only in boot images created in MDT 2010 Update 1 and later. At the appropriate task sequence step. 2.

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

com/technet/SolutionAccelerators . The Page Behavior for the Computer Page is configured to Silent. 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 list box contains a list of OUs that can be selected where the computer account will be created. This wizard page is shown if: • • The Page Behavior for the Computer Page is configured to Enabled or Disabled in the UDI Wizard Designer. but there are problems with required information on the wizard page. 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. Configuration Settings on the Computer Wizard Page Setting Computer name Description Contains the computer name that will be assigned to the target computer. and then click Next. The corresponding list box contains a list of domains that can be selected.Using the Microsoft Deployment Toolkit: Operating System Deployment (OSD) Setup Wizard 318 5. 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. 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. Note This list box is only enabled if the Domain option is selected. complete the page using the information in Table 165. Select this option if the target computer is to be a member of a domain. On the Computer wizard page. Table 165. 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.

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

but there are problems with required information on the wizard page. 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.com/technet/SolutionAccelerators Confirm password User name Back Solution Accelerators . 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. Each account is separated by a semicolon. 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. Table 166. The value entered in this box must match the value in the Password box. The value entered in this box must match the value in the Confirm password box. Contains the password for the Administrators local built-in account on the target computer. 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. Goes to the previous wizard page.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. 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. microsoft.

and then click Next. input locale. 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 wizard page is shown if: • • The Page Behavior for the Language page is configured to Enabled or Disabled in the UDI Wizard Designer. input locale. 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. and time zone list boxes and the Select the default language list box on the Language page in the UDI Wizard Designer. 7. Table 167. complete the page using the information in Table 167.com/technet/SolutionAccelerators Time and currency format (Locale) Solution Accelerators .321 Microsoft Deployment Toolkit 2010 Update 1 Setting Next Cancel Description Goes to the next wizard page. 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 input locale list box on the Language page in the UDI Wizard Designer. 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. but there are problems with required information on the wizard page. On the Language wizard page. Cancels the wizard and stops the UDI deployment process. The Page Behavior for the Language page is configured to Silent. 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. The list of languages available in the list box and the language are configured in the Set default language.

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

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. 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 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.com/technet/SolutionAccelerators .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 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. 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. 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. 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. 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 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.

Configure Software Installation Behavior Using the Package Selection Page in the UDI Wizard Designer. Package Selection. but there are problems with required information on the wizard page. 9. Back Next Cancel Goes to the previous wizard page. complete the page using the information in Table 169. On the Install Software 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. 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. 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. The list of available applications is configured on the Settings and Groups. and OSD Applications pages in the UDI Wizard Designer.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 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. Goes to the next wizard page. 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. The Page Behavior for the Settings and Groups page is configured to Silent.com/technet/SolutionAccelerators Solution Accelerators . Configure Software Installation Behavior Using the OSD Applications Page in the UDI Wizard Designer. and then click Next. Table 169. Cancels the wizard and stops the UDI deployment process.

config File Element Values” section in the MDT 2010 document. 10. and then click Finish.325 Microsoft Deployment Toolkit 2010 Update 1 Setting Back Next Cancel Description Page in the UDI Wizard Designer. On the Summary wizard page. This wizard page is shown if: • • The Page Behavior for the Summary page is configured to Enabled or Disabled in the UDI Wizard Designer. Goes to the next wizard page. Finishes the wizard and continues the deployment process to the target computer.exe. Table 170. Goes to the previous wizard page. 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. and deployment of the new operating system begins. When the deployment process is complete. but there are problems with required information on the wizard page. the OSD Results page is displayed just prior to the first user logging on to the target computer.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. see the “OSDResults. For more information about how to configure the OSD Results page. Toolkit Reference. Cancels the wizard and stops the UDI deployment process. Goes to the previous wizard page. Solution Accelerators microsoft. The Page Behavior for the Summary page is configured to Silent. Cancels the wizard and stops the UDI deployment process. complete the page using the information in Table 170. The Operating System Deployment (OSD) Setup Wizard finishes.

Managing device drivers in LTI and ZTI deployments as described in Managing Device Drivers. . • • • Customizing MDT 2010 Configuration Files MDT 2010 is flexible and highly customizable.326 Microsoft Deployment Toolkit 2010 Update 1 Configuring MDT 2010 Deployments Configure MDT 2010 deployments by: • • • • • • • • • • • Customizing the CustomSettings. 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. Configuring the MDT 2010 processing rules as described in Configuring MDT 2010 Processing Rules. Preparing disks on the target computers as described in Preparing Disks on Target Computers. Joining target computers to AD DS domains as described in Joining Target Computers to AD DS Domains. Applying the MDT 2010 properties to individual computers as described in Applying MDT 2010 Properties to Individual Computers. Applying the MDT 2010 properties to groups of computers as described in Applying MDT 2010 Properties to Groups of Computers. Customizing the MDT 2010 properties as described in Configuring the Appropriate MDT 2010 Properties. It includes several tools for getting started. The following section contains code samples that show how easily you can use these scripts to customize the deployment process. but the ability to customize deployment to fit your organization’s needs is the core of MDT 2010’s strength.ini files as described in Customizing MDT 2010 Configuration Files. 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. Copying content to the target computers for LTI and ZTI deployments as described in Copying Content to the Target Computer. Creating custom scripts that integrate with the LTI and ZTI deployment process as described in Creating Custom Scripts for MDT 2010. Saving and restoring the user state migration data using USMT as described in Saving and Restoring User State Information.ini and Bootstrap.

• • Identify the CustomSettings.ini File Syntax.ini file includes: • • • Sections Properties Settings Listing 1 shows a 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. Identifying the sections of the CustomSettings. Configuring the basic configuration settings for the CustomSettings. CustomSettings.327 Microsoft Deployment Toolkit 2010 Update 1 Customize the MDT 2010 configuration files by: • • • • Identifying the syntax of the CustomSettings.com/technet/SolutionAccelerators .ini file as described in Sections in the CustomSettings.ini File Customized for ZTI Deployment [Settings] Priority=Default. later in this guide.ini File for ZTI.ini file as described in Identify the CustomSettings.ini File Syntax The syntax of the CustomSettings. Listing 1.ini file as described in Properties in the CustomSettings.ini file is similar to many .ini File Syntax.ini file customized for ZTI.ini file for LTI deployments as described in Basic CustomSettings.ini file for ZTI deployments as described in Basic CustomSettings.ini file as described in Identify the BootStrap. A CustomSettings.ini File.ini File. see Basic CustomSettings. Identifying the syntax of the BootStrap. Configuring the properties in the CustomSettings. For more information about the CustomSettings.ini File for ZTI Deployments. Configuring the basic configuration settings for the CustomSettings.ini File for LTI Deployments.ini files.ini file in Listing 1.

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

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

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

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

ZTIGather.exe tool in the USMT.exe during state capture.com/technet/SolutionAccelerators . The properties listed here are in addition to the properties listed in ZTIGather. 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.ini [Settings] Priority=Default Purpose Indicates the start of the [Settings] section. Properties=MyCustomPropert y [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c Solution Accelerators microsoft. For LTI. Table 172 explains the properties and corresponding values used in Listing 3. This version of the file contains no values unique to a specific target computer. Explanation of CustomSettings.wsf parses ZTIGather.xml. In this example. the [Default] section is the only subsection that is parsed for variables. Table 172. These parameters are passed to Scanstate. Indicates that the computer is supposed to perform an operating system deployment.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.ini file in Listing 3 contains the property values for all the target computers to be migrated using this version of the file.ini Properties in Listing 3 Line in CustomSettings. Indicates the start of the [Default] section. Parameters passed to the Scanstate. Indicates any additional properties to locate.

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

ini file based on the responses provided. which includes target computer–specific settings. Listing 5. Listing 6 shows a modified version of the CustomSettings. This version of the file contains no values that are unique to a specific target computer. 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. Listing 6. Listing 5 shows the customized version of the CustomSettings. Modify this version of the CustomSettings. Customized CustomSettings. For ZTI. After modifying the file.ini template with no modifications to the file.ini file.ini file after completing the New Deployment Share Wizard.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.com/technet/SolutionAccelerators . Customized CustomSettings. MACAddress Solution Accelerators microsoft. update the distribution points for the Microsoft Deployment Files package so that the changes are available to the task sequences.ini file to include the target computer– specific configuration values. the Create Microsoft Deployment Task Sequence Wizard copies an unmodified version of the CustomSettings.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.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.ini File with Target Computer Settings [Settings] Priority=Default.

Indicates the start of the [Default] section. In this example. the [Default] section is parsed first. and then the section that corresponds to the MAC address of the target computer (MACAddress) is parsed. The properties listed here are in addition to the properties listed in ZTIGather. Properties=MyCustomProperty Indicates any additional properties to locate. Establishes the sequence in which the process parses subsections to locate values for the variables.xml. Explanation of CustomSettings.wsf parses ZTIGather.ini Properties in Listing 6 Line in CustomSettings. [Default] OSInstall=Y Solution Accelerators microsoft.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. MACAddress Purpose Indicates the start of the [Settings] section. Indicates whether the target computer is authorized to have the operating system installed.com/technet/SolutionAccelerators . The sections for the target computers ([00:0F:20:35:DE:AC] and [00:03:FF:FE:FF:FF]) contain computer-specific settings. ZTIGather.xml to obtain a list of the properties. Table 173.ini [Settings] Priority=Default.

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

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

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

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

A separate section.16.3=NYC 172.0.3=NYC 172. 172.3=DALLAS 172.16.112. includes the configuration settings specific to the NYC location. [NYC].2.16. a one-to-one mapping might be expected between the [DefaultGateway] section and a corresponding section.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 340 location.117.16.com/technet/SolutionAccelerators Solution Accelerators . Similar sections exist for the DALLAS and WASHINGTON locations.16. determine which properties and corresponding configuration settings to apply to each group.3=WASHINGTON 172.3=NYC 172.1.3) reside within the NYC location.3=DALLAS 172.3.16.3. Three subnets (172. This is a special case that allows multiple default gateways to point to the same section.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.16. Listing 8.2.111.1.16.16. and 172. Properties that can be grouped are those you can apply to multiple computers. Some examples of properties that are typically applied to groups of computers include: • BackupDir microsoft.16.0. Using [DefaultGateway] to Designate Location-Specific Configuration Settings [Settings] Priority=DefaultGateway [DefaultGateway] 172.116. In many environments.

In NYC. determine the method for identifying individual computers and the configuration settings to assign to each computer. 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.com/technet/SolutionAccelerators . The rules for target computers allow the override or augmentation of group-based processing rules based on the priority of the computer-based rules. The Administrator accounts that Administrator1 (WOODGROVEBANK\NYC Help Desk Staff and WOODGROVEBANK\DAL Help Desk Staff) reference are unique to each respective location. see Priority Reserved Property. location-specific packages are designated by Packages1 and Packages2. 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.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. and Administrator1 are specified for each location. Solution Accelerators microsoft. • Applying MDT 2010 Properties to Individual Computers After determining the groupings of target computers and configuration settings to be applied to each group. earlier in this guide. SLShare. UDShare.

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

Configure the MDT 2010 processing rules by completing the following tasks: • Configure the processing rules as described in Configure the Rules in the CustomSettings.ini file or in the MDT DB. [00:0F:20:35:DE:AC] ComputerName is the name of the computer after deployment—in this case. AAAAABBBBB-CCCCC-DDDDD-EEEEE. WasW2K. TTTTTVVVVV-WWWWW-XXXXX-YYYYY. 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.ini File. OverRideProductKey is the product key to be assigned to the computer—in this case. Table 176. BVMXP. Table 176 lists the computer-specific configuration settings applied to each computer. microsoft. OverRideProductKey is the product key to be assigned to the computer—in this case.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. [00:03:FF:FE:FF:FF] deployment—in this case. 1111122222-33333-44444-55555.com/technet/SolutionAccelerators Solution Accelerators . HPD530-1. OverRideProductKey is the product key to be assigned to the computer—in this case. 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.

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

Table 177. These task sequence templates include the task sequence steps listed in Table 177. You can configure these properties in CustomSettings.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.ini or in the MDT DB. For more information about the properties in Table 178.com/technet/SolutionAccelerators BDEDriveSize BDEInstall BDEInstallSuppress Solution Accelerators . available in ZTI task sequences only Configures BitLocker Drive Encryption on the target computer. 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. Configure the MDT 2010 properties used in saving and restoring user state information as described in Configure Disk Preparation Properties. Table 178. available for LTI and ZTI task sequences Format and Partition Creates partitions and formats disks on the target Disk computer. • Configure Disk Preparation Task Sequence Steps MDT 2010 includes task sequence templates for LTI and ZTI deployments. 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. Toolkit Reference. see the corresponding section for each property in the MDT 2010 document. available for LTI and ZTI task sequences Disable BitLocker Disables BitLocker Drive Encryption on the current operating system drive or on a specific drive. Disk Preparation Properties Property BDEDriveLetter Description The drive letter for the partition that is not encrypted with BitLocker Drive Encryption. 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. which are used to perform disk-preparation steps.

or %. the default is none.) OSDPartitionsxSize OSDPartitionsxSizeUnits The size of the partition The units of measure for specifying the size of the partition (Valid values are MB. The default value is MB. GB.) The type of file system for the partition (Valid values are NTFS or FAT32.) The partition that should be set to bootable (The default first partition is set to bootable.) 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.) BDERecoveryKey BDEWaitForEncryption DestinationDisk DestinationLogicalDrive DestinationPartition OSDPartitions OSDPartitionsxBootable OSDPartitionsxFileSystem OSDPartitionsxQuickFormat Indicates whether the partition should be quick formatted (The default is TRUE.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.com/technet/SolutionAccelerators .

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. during the State Restore Phase. • • Review User State Information Task Sequence Steps MDT 2010 includes task sequence templates for LTI and ZTI deployments.ini or the MDT DB for LTI deployments Captures the group membership of the local groups microsoft. The MDT 2010 deployment process uses USMT to save and restore user state information. data files. The MDT 2010 deployment process can automatically capture and restore user state information on the target computers. These task sequence templates include the task sequence steps listed in Table 179.com/technet/SolutionAccelerators Capture Groups Solution Accelerators . 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. and other user-specific data stored on the target computer. which are used to save and restore user state information. Configure the MDT 2010 properties used in saving and restoring user state information as described in Configure User State Information Properties. USMT restores this user state information. Later. During the State Capture Phase in the MDT 2010 deployment process. Table 179. USMT saves the user state information to a desired location. Internet Explorer favorites. Customizing the USMT XML control files as described in Customize User State Migration XML Control Files.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.

exe tool List of parameters passed to the Scanstate.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.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. Solution Accelerators microsoft. 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.ini file or in the MDT DB. For more information about the properties in Table 180.) A comma-delimited list of user profiles that the Scanstate. Toolkit Reference.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. User State Information Properties for LTI Deployments Property LoadStateArgs ScanStateArgs UserDataLocatio n UDDir Description List of parameters passed to the Loadstate.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. Table 180.com/technet/SolutionAccelerators . You can configure these properties in the CustomSettings. see the corresponding section for each property in the MDT 2010 document.

The XML files need to be copied into either the USMT folder or the Scripts folder in the distribution share.xml USMTMigFiles2=MigUser. 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.MigUser.xml The path to the XML control files is relative to the current folder. 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. insert one or more lines in the CustomSettings.xml.ini file that contains the OSDMigrateConfigFiles task sequence variable for the USMT migration XML control file that you want to specify. for details on configuration settings.com/technet/SolutionAccelerators Solution Accelerators .xml USMTMigFiles3=MigSys.xml USMTMigFiles4=MigCustom. Configure User State Migration XML Control Files for ZTI Deployments For ZTI deployments. insert a line in the CustomSettings. Use the following format for these lines: USMTMigFiles1=MigApp. 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. If you keep the XML control files in the USMT package. update this package each time you modify any of the XML control files. If you specify the OSDMigrateConfigFiles property.xml Note See the MDT 2010 document. Otherwise.xml USMTConfigFile=Config.ini file that contain the USMTMigFiles property for each of the USMT migration XML control files that you want to specify. insert another line that sets the OSDMigrateMode task sequence variable to Advanced. which will be the location of the USMT package. Toolkit Reference. Although you can complete this process manually. Configure User State Migration XML Control Files for LTI Deployments For LTI deployments.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. Use the following format for these lines: OSDMigrateMode=Advanced OSDMigrateConfigFiles=MigApp.

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. 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. Specifies the domain to which the target computer is to be joined. This text box is enabled only when you select Join a domain.ini as described in Join Domains by Modifying the CustomSettings. Table 181. see Complete the Windows Deployment Wizard.com/technet/SolutionAccelerators . Table 181 lists the configuration settings on this wizard page used in joining a domain. Solution Accelerators microsoft. User Name Password Domain Organizational Unit Specifies the OU in which the computer account will be created in the domain specified in Domain. Specifies the domain in which the account specified in User Name is located. This text box is enabled only when you select Join a domain.xml as described in Join Domains by Modifying the Unattended.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 350 • • • Modifying CustomSettings.ini File Modifying Unattended. 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. Specifies the password for the account specified in User Name. This text box is enabled only when you select Join a 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. For more information about completing the Join the computer to a domain or workgroup wizard page in the Windows Deploy Wizard.

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.351 Microsoft Deployment Toolkit 2010 Update 1 Join Domains by Modifying the 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. specify as Domain\UserName or UserName@Domain. Settings in Unattended.com/technet/SolutionAccelerators Solution Accelerators .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.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. Table 182.ini file used in the MDT 2010 deployment process. and underscores [_].) 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.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. Properties in CustomSettings. The JoinDomain property cannot be blank or contain spaces. hyphens [-]. Table 183.

This method allows the user running the Windows Deployment Wizard to retry the domain-join process. In the details pane. Manual Recover (Allow user to Join Domain). Select this method when you want the MDT 2010 process to automatically retry the domain-join process. Solution Accelerators microsoft. click Properties.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. 4. Select this method when you want MDT 2010 to stop running the task sequence if the computer has not successfully joined the domain.aspx.ini. This method automatically terminates the task sequence if the computer has not successfully joined the domain. This method automatically retries the domain-join process without intervention.com/technet/SolutionAccelerators .10). In the Actions pane. 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. • • To configure task sequence steps based on the Recover from Domain Join Failure task sequence step type 1.microsoft. Point to Microsoft Deployment Toolkit. 3. Select this method when you want the MDT 2010 process to allow the user to retry the domain-join process. 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). and then click Deployment Workbench. No Recover (Stop script execution). Click Start. 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).com/enus/library/cc748842(WS. and then point to All Programs. click task_sequence_name (where task_sequence_name is the name of the task sequence you want to configure). see Microsoft-WindowsUnattendedJoin at http://technet. 2. In the Deployment Workbench console tree.

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).com/technet/SolutionAccelerators . 5. 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. 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. On the Task Sequence tab.xml file. This process makes it possible to join computers to a domain in locations where there is no connectivity to a corporate network. go to task_sequence_step. configure the settings listed in Table 184 based on the requirements of your organization.xml file in Windows 7 and Windows Server 2008 R2 includes the Microsoft-WindowsUnattendJoin/Identification/Provisioning section. which includes the configuration settings for performing a domain join. Solution Accelerators microsoft. Table 184. No additional restart is required to complete the domain-join process. The Unattend. 6. and then click OK. in the task sequence hierarchy. The offline domain join is a variant on joining domains by modifying the Unattend. and then click the Properties tab. which can significantly reduce the overall time required for wide-scale VM deployments. On the Properties tab. Using offline domain join. target computers can be joined to the domain when they initially start after the installation of the target operating system.

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

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. 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. Some of the LTI task sequence templates provided in MDT 2010 include the Apply Patches task sequence step. For more information on creating selection profiles.wsf" Deploy Software Updates with Deployment Workbench for LTI Deployments In LTI deployments.com/technet/SolutionAccelerators .exe "%SCRIPTROOT%\ZTIWindowsUpdate. Deploy Software Updates with System Center Configuration Manager for ZTI Deployments In ZTI deployments. Table 185. including mandatory software updates Solution Accelerators microsoft.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. If you want to deploy software updates based on multiple selection profiles. create a task sequence step for each selection profile. 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 control the software updates deployed to the target computers by this method using selection profiles. which is based on the Install Updates Offline task sequence step type. 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. see Create a New Selection Profile in Deployment Workbench. and then specify the corresponding selection profile in the task sequence step. you can initiate software updates using a task sequence step based on the Install Software Updates task sequence step type.

Managing device drivers using the Deployment Workbench for LTI deployments as described in Control Device Driver Deployments for LTI. • Table 186 lists the advantages and disadvantages of these device driver management strategies. The proper device drivers must be available to Windows PE and to the target operating system for the deployment to be successful. Table 186. This is the default behavior for LTI and ZTI deployments.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 356 For more information about the Install Software Updates task sequence type.com/technet/SolutionAccelerators . only the device drivers specific to the target computer are deployed to the target computer. Include only the device drivers specifically required for the target computer. Managing Device Drivers Device driver management is a critical component in deploying operating systems to target computers. • Images require more frequent version Solution Accelerators microsoft.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. Then. Managing device drivers using System Center Configuration Manager for ZTI deployments as described in Control Device Driver Deployments for ZTI. Resolving device driver signing issues as described in Resolve Device Driver Signing Issues.aspx. all the drivers 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. Windows PE and the target operating system use Plug-andPlay IDs to identify the device drivers needed for the devices on the target computers. In this strategy. 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.microsoft. This requires that you configure the ZTI and LTI process to control which device drivers are deployed to the target computer. In this strategy.

because there are fewer drivers in the image. • Images require less frequent version updates. 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. • Can introduce unnecessary management overhead when there are fewer device drivers to manage.357 Microsoft Deployment Toolkit 2010 Update 1 Strategy Advantages drivers. In most instances. • Windows XP and Windows Server 2003 images should still include all mass storage drivers. • Ongoing management of device drivers in the image requires more effort. 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. • Works well when there are fewer device drivers to manage. • Requires more initial time and effort to identify the appropriate drivers. select a device driver management strategy that is a hybrid of these strategies and best fits your organization. The high-level approach to device driver management using the Deployment Workbench for LTI deployments is: Solution Accelerators microsoft.com/technet/SolutionAccelerators . • Works well when there is a large number of device drivers to manage. Disadvantages updates. • Does not work well if there are a large number of device drivers to manage. • Images are smaller. • All mass storage drivers for Windows XP and Windows Server 2003 are included. Either of these strategies can cause problems if taken to the extreme. Include only the device drivers specifically required for the target computer • Ongoing management of device drivers in the image requires less effort. 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. because there are more drivers in the image.

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. Processor architecture of the target computers. 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. 2. The folder structure groups or categorizes device drivers so that you can select specific groupings or categories of drivers using selection profiles. 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.com/technet/SolutionAccelerators Solution Accelerators . Select this method to deploy device drivers to the target computer based on the respective make and model of the target computer. Select any combination of the following methods for creating folder structures: • Target operating system. 3. the more complex the folder structure. Select this method to deploy only the device drivers to the target computers based on the respective processor architecture (32-bit or 64-bit). Select this method to deploy only the device drivers to the target computer based on the respective target operating system.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 358 1. and then place the device drivers in the corresponding folders: • • Windows 7 Windows Server 2003 microsoft. 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. For example. In this case. 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. The more precision you want. • • The complexity of the folder structure that you create is based on the level of precision you want for deploying the device drivers. 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. you may have or expect to have one of the following problems: • Device drivers are being selected for the wrong operating system. Manufacturer (make) and model of the target computers.

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. 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. and processor architecture: make\model\operating_system\architecture Figure 2 illustrates the folder structure Woodgrove Bank created. In this case. 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. operating system. 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.com/technet/SolutionAccelerators . 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 processor architecture. In this case.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 CustomSettings. If you create selection profiles on folders: • • Higher in the folder structure.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 360 Figure 2. Windows XP 64-bit Device Drivers.32-bit Device Drivers. Tip Use selection profile names that allow you to easily identify the device drivers included in them.Model A532.com/technet/SolutionAccelerators . 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 . and you have more granular control over the device drivers deployed. and in the MDT DB. Lower in the folder structure. The LTI deployment process uses selection profiles to determine the device drivers to deploy in the Inject Drivers task sequence step type.ini. By default. and you have less granular control over the device drivers deployed. such as Windows 7 32-bit and 64-bit Device Drivers. selection profiles deploy the device drivers in the selected folder and subfolders. Create selection profiles based on the level of control you want to have over the device drivers being deployed. fewer device drivers are included. Example: Woodgrove Bank Device Driver Selection Profiles for LTI Deployments Solution Accelerators microsoft. more device drivers are included.

ini file or the MDT DB to allow the selection profile to control the device drivers deployed to the target computer. 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.ini file.ini file. the CustomSettings. if you specify a selection profile that contains only 64-bit device drivers and leave the default device driver group. the CustomSettings. specify: • The Nothing device driver group in the CustomSettings. or the MDT DB. 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. which can cause unpredictable results.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. The LTI deployment process creates the list of device drivers to deploy based on the union of both selection profiles and device driver groups. So. To change this behavior. the result will include all device drivers.ini file or the MDT DB. • • The following are strategies for configuring task sequences to control the deployment of device drivers for LTI deployments: Solution Accelerators microsoft. or the MDT DB to allow the device driver group to control the device drivers deployed to the target computer. Selection profiles are exposed to the LTI deployment process as: • • Selection profiles that can be configured in the Deployment Workbench. Selection profiles and device driver groups are additive. The Nothing selection profile in the Inject Driver task sequence step. Device driver groups that can be configured in the CustomSettings. because the default selection profile and default device driver group include all device drivers.com/technet/SolutionAccelerators . For example.

and then used the DriverSelectionProfile task sequence variable in the CustomSettings. • 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. which is in most of the LTI task sequence templates. Because selection profiles and device driver groups are additive. • • • Configure a single Inject Driver task sequence step in the task sequence (which already exists in most of the LTI task sequence templates). they all will be overridden. The IT pros added the following line in their CustomSettings. However. add an Inject Driver task sequence step for each selection profile. For a limited number of selection profiles.ini file and the MDT DB to override the selection profile specified in the Inject Driver task sequence step as necessary.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. modify the Inject Driver task sequence step. Solution Accelerators microsoft. and then configure each task sequence step with the corresponding selection profile. because the task sequence will deploy only one operating system. this method is provided for backward compatibility with previous versions of BDD and MDT. If you want to use the DriverGroup task sequence variable for backward compatibility with previous versions of MDT. Its IT pros have created a device driver folder structure and selection profile strategy that allows detailed control of device drivers. Note The selection profile you specify in the DriverSelectionProfile task sequence variable overrides all Inject Driver task sequence steps in a task sequence.com/technet/SolutionAccelerators . the device drivers specified in the DriverGroup task sequence variable are deployed in addition to the device drivers in the selection profile. but specify additional device drivers to be added using the DriverGroup task sequence variable. to use the selection profile. 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. and then override the selection profile specified in the Inject Driver task sequence step using the DriverSelectionProfile task sequence variable in the CustomSettings.ini file or the MDT DB. Instead. Note You can also use the DriverPaths property to specify the UNC path to the folders containing the device drivers to deploy. If you have multiple all Inject Driver task sequence steps in your task sequence. Configure a single Inject Driver task sequence step in your task sequence.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 362 • For a single selection profile. use selection profiles or the DriverGroup task sequence variable. configure the Inject Driver task sequence step to use the Nothing selection profile.

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. 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.com/technet/SolutionAccelerators Solution Accelerators . device driver packages are distributed to distribution points so that they are accessible to the target computers. 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. Control the deployment of device drivers by performing the following steps: 1. You can control the device drivers deployed based on the device driver packages using the Apply Driver Package task sequence step. such as the make and model of target computer. Device driver categories allow you to specify a category for each device driver you import into the driver catalog. Create device driver categories based on the level of granularity you want in controlling the device drivers to be deployed. Like software packages. this step configures the task sequence to deploy all device drivers to the target computer. 4. if the device driver packages are based on the make and model of the target computer. Control the deployment of device drivers by performing the following steps: microsoft. Add multiple Auto Apply Drivers task sequence steps based on the number of combination categories you want to deploy. For example. Device driver categories. After you import device drivers into the driver catalog. you can organize them by: • Device driver packages. such as all network adapter drivers or by processor architecture. Categories allow you to group device drivers based common characteristics. 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. • Most of the ZTI task sequences created using the MDT 2010 task sequence templates include the Auto Apply Drivers task sequence step. You can create multiple device driver packages to group device drivers to be deployed to 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. By default. 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. 2. Configure the task sequence step conditions based on the contents of the device driver package. 3.

Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 364 1. 3. strServer with you System Center Configuration Manager site server. 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. 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. Configure the task sequence step conditions based on the contents of the device driver package.echo DriverGuid. Control the deployment of device drivers by performing the following steps: 1. 3. 4. For each device driver package. 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. • Configure a single Auto Apply Drivers task sequence step in your task sequence.CategoryInstance_UniqueID Solution Accelerators microsoft. Create device driver categories based on the level of granularity you want in controlling the device drivers to be deployed. Determine GUIDs for each device driver category you created by running the following script. as the category will be overridden by the OSDAutoApplyDriverCategoryList task sequence variable. Add a new or an existing Auto Apply Drivers task sequence step in your task sequence. Configure the Apply Driver Package task sequence step to use the corresponding device driver package. For example. 4. Note The device driver category you select is not important. substituting strSiteCode with your site code. 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. and then override the selection profile specified in the Auto Apply Drivers task sequence step using the OSDAutoApplyDriverCategoryList task sequence variable in the CustomSettings. if the device driver packages are based on the make and model of the target computer. 2.ExecQuery("select CategoryInstance_UniqueID from CMDB_categoryinstance where LocalizedCategoryInstanceName = '" & strDriverCatName & "'") For each DriverGuid in DriverGuids wscript. 2.com/technet/SolutionAccelerators .ini file or the MDT DB.

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

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. Configuring the Authorize DHCP task sequence step as described in Configure Authorize DHCP Task Sequence Step Settings for LTI and ZTI. microsoft. 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. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. and directory searches. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps. authentication. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. 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. Configuring the DNS Server server role task sequence step as described in Configure DNS Server Role Settings for LTI and ZTI. Configuring the DHCP Server server role task sequence step as described in Configure DHCP Server Role Task Sequence Step Settings for LTI and ZTI. Configure task sequence steps in MDT 2010 to deploy the server roles that are supported in MDT 2010. 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. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. 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. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps. 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.com/technet/SolutionAccelerators • • Solution Accelerators . including logon processes. An AD DS domain controller is a server that runs AD DS.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.

In the NetBIOS name box. click MDT. On the Properties tab. 3. and then click Configure ADDS. 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. . 4. 7.com might have the NetBIOS name WOODGROVE. You must include the extension of the domain—for example. 6.com. Deploy a Domain Controller in a New Forest Using this option. . To deploy a domain controller with a new forest 1. woodgrove. ZTI in the task sequence hierarchy. Description. click New Forest. Use this option when deploying a new forest environment. and then click Configure ADDS.com or any other type of extension. the forest domain name woodgrove. type the relevant information in the following boxes: • • Name.net. In the Create box. Type a description of the task—for example. . Click Add. deploy a domain controller that contains a new forest environment. 2. Type a name for the task. This name is usually the domain name without .com. click Roles. In the Recovery (safe mode) password box. In the New forest domain DNS name box. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. In the task sequence hierarchy. 5. click Add. Make note of this password in case AD DS must be recovered. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). For example. Configuring AD DS advanced properties for domain controllers as described in Configure AD DS Advanced Properties. type a name for the NetBIOS. You use this password to recover from a failed AD DS service. Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab.int.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. type a password to use for safe mode recovery.com/technet/SolutionAccelerators . Solution Accelerators microsoft. type a name for the new domain —for example.

microsoft. For more information about DCPROMO command-line options. 7. complete the task configuration as described in Configure AD DS Advanced Properties. type the name of an account that has permissions to add a domain controller to the existing network (typically.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 368 8. and then click Configure ADDS. Type a description of the task—for example. a domain Administrator account). To deploy a domain controller as a new domain controller replica 1. On the Properties tab. Type a name for the task. 3. ZTI in the task sequence hierarchy. click New domain controller replica. Click Add. In the Create box. type the relevant information in the following boxes: • • Name. deploy an existing domain controller as a new domain controller by replicating it into an existing environment. and then click OK.com/technet/SolutionAccelerators . In the Account box. Description. type the FQDN of an existing domain controller.mspx?mfr=true. click MDT. Use this option when deploying a new domain controller into an existing environment if replication will obtain the existing domain information from AD DS. 6. Solution Accelerators microsoft. type the name of a domain controller the new server will replicate within the existing environment. In the Replication source domain controller box. In the Existing domain DNS name box. 8. In the Recovery (safe mode) password box. click Add. 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. Deploy a New Domain Controller as a Replica in an Existing Domain Using this option. type a password to use for safe mode recovery. 2. Server_Name Site_Name (where Server_Name is the name of the server. In the task sequence hierarchy. In the Advanced Properties section. and then click Configure ADDS. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. and then click Set. go to http://technet2. Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab. The directory services database replicates this domain controller. and Site_Name is the name of the domain). 4. click Roles.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033.

type the name of an existing domain in the network.com (where child is the name of the child domain).mspx?mfr=true. click New domain in existing forest. click MDT. Description.com or any other type of extension—for example. and then click Configure ADDS.com might have the NetBIOS name WOODGROVE. In the Existing forest (parent) domain DNS name box. 3. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. deploy a domain controller that contains a new tree into an existing forest environment. child. In the task sequence hierarchy. On the Properties tab. In the Advanced Properties section. Deploy a New Domain Controller in a New Domain Tree in an Existing Forest Using this option. 5. and then click OK. For more information about DCPROMO command-line options. In the NetBIOS name box. Add a new task sequence step based on the Configure ADDS task sequence type for: • • LTI on the Task Sequence tab. 4. Click Add. 2.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. In the Create box. complete the task configuration as described in Configure AD DS Advanced Properties. 6.woodgrove. type the NetBIOS name of an existing domain in the network. go to http://technet2. type the relevant information in the following boxes: • • Name: Type a name for the task. Make note of this password in case AD DS must be recovered. and then click Configure ADDS. type a name for the child domain being created—for example.com/technet/SolutionAccelerators . Solution Accelerators microsoft. Type a description of the task—for example. usually the domain name without . click Roles.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. 7. click Add. ZTI in the task sequence hierarchy. the domain woodgrove. To deploy a domain controller with a new domain tree in an existing forest 1. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). Use this option when deploying a child domain into an existing forest environment. 9. 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.

11. type the name of the domain controller to which the new child domain will replicate. For more information about DCPROMO command-line options. Click Add. type the name of an account with permissions to add a domain controller to the existing network (typically. Use this option when deploying a new child domain into an existing forest environment. click New domain in existing forest. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. Type a name for the task. 9. In the Recovery (safe mode) password box. and then click OK. click Roles. ZTI 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. type a password to use for safe mode recovery. 4. To deploy a domain controller with a new domain in an existing forest 1. type the relevant information in the following boxes: • • Name. Make note of this password in case AD DS must be recovered. go to http://technet2. Solution Accelerators microsoft. a domain Administrator account). and then click Configure ADDS. In the task sequence hierarchy.com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. 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 a description of the task—for example. 3. Deploy a New Domain Controller in a New Domain in an Existing Forest Using this option.mspx?mfr=true. 10. complete the task configuration as described in Configure AD DS Advanced Properties. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). On the Properties tab. In the Create box. click MDT. You use this password to recover from a failed AD DS service.com/technet/SolutionAccelerators . click Add.microsoft. deploy a domain controller that contains a new domain into an existing forest environment. and then click Configure ADDS.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 370 8. Description. 2. In the Replication source domain controller box. and then click Set. In the Account box. In the Advanced Properties section.

child.mspx?mfr=true. Make note of this password in case AD DS must be recovered. type the name of an existing domain in the network. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. deploy a domain controller that contains a read-only replica of the existing domain into an existing forest environment. Use this option to deploy a domain controller that contains an un-editable replica of a domain structure into an existing forest environment. Add a new task sequence step based on the Configure ADDS task sequence type for: • LTI on the Task Sequence tab. 7. In the task sequence hierarchy. In the Advanced Properties section. Solution Accelerators microsoft.microsoft. In the Account box. 2. and then click Configure ADDS. type the name of the domain controller to which the new child domain will be replicated. go to http://technet2. usually the domain name without . 11. click Roles. 9. In the NetBIOS name box. type a name for the child domain being created—for example. 8. type the name of an account with permissions to add a domain controller to the existing network (typically. and then click Set. To deploy an RODC in an existing domain 1. the domain woodgrove. type the NetBIOS name of an existing domain in the network. In the Existing forest (parent) domain DNS name box. click Add.com might have the NetBIOS name WOODGROVE. and then click OK. complete the task configuration as described in Configure AD DS Advanced Properties. In the Recovery (safe mode) password box.371 Microsoft Deployment Toolkit 2010 Update 1 5. a domain Administrator account). In the Replication source domain controller box. Deploy an RODC in an Existing Domain Using this option.com/technet/SolutionAccelerators .com (where child is the name of the child domain). 10.woodgrove. You use this password to recover from a failed AD DS service. type a password to use for safe mode recovery.com or any other type of extension—for example. In the New domain (child) DNS name box. 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/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. For more information about DCPROMO command-line options. 6.

In the Create box. Description. a domain Administrator account). type the relevant information in the following boxes: • • Name. 6. You use this password to recover from a failed AD DS service.mspx?mfr=true. Click Add. click New read-only domain controller (RODC) replica. microsoft. Type a name for the task. type the name of an account with permissions to add a domain controller to the existing network (typically. 7. click MDT. Make note of this password in case AD DS must be recovered. perform the following steps: 1. and then click Configure ADDS. click MDT. ZTI in the task sequence hierarchy. In the task sequence hierarchy. and then click Set. The directory services database replicates this domain controller.com/technet/SolutionAccelerators • Solution Accelerators .com/windowsserver2008/en/library/d660e761-9ee74382-822a-06fc2365a1d21033. In the Existing domain DNS name box. for example. In the Recovery (safe mode) password box. • Configure AD DS Advanced Properties To configure AD DS advanced properties. On the Properties tab. 4. 8. and then click task_sequence_step (where task_sequence_step is the Configure ADDS task sequence step). In the Advanced Properties section. type a password to use for safe mode recovery. type the name of an existing DNS server. In the Account box. Modify the Configure ADDS task sequence step you created for: • LTI on the Task Sequence tab. For more information about DCPROMO command-line options. Click Add. type the name of the domain controller to be replicated within the existing environment. 9. 5. 2. 3. and then click OK. go to http://technet2.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 372 ZTI in the task sequence hierarchy. In the Replication source domain controller box. 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. complete the task configuration as described in Configure AD DS Advanced Properties. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. Server_Name Site_Name (where Server_Name is the name of the server and Site_Name is the name of the domain). click task_sequence_step (where task_sequence_step is the Configure ADDS task sequence step). Type a description of the task.

You can also configure this value using the LogPath property in the CustomSettings. Contains the fully qualified path on the target computer to the location for the log files. The default value is %SYSTEMROOT %NTDS. use the %DESTINATIONLOGICALDRIVE% task sequence variable instead of the %SYSTEMROOT% variable. select the following options as required for your environment and AD DS scenario: Options section: • • Install DNS if not already present. In the AD DS Advanced Properties dialog box. Make this domain controller a global catalog (GC) server. This is the default option and should be selected for new domains or forests and domains without a GC server. SYSVOL. however. Windows Server 2008 (2 = Windows Server 2003.ini file or the MDT DB. Log Files. and Folders sections. Select this option when creating a new forest or new domain. 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. in the Options. The default value is %SYSTEMROOT %SYSVOL. the variables are evaluated while running Windows PE. Contains the fully qualified path on the target computer to the location for the NTDS database. Forest Functional Level. The default name for a new forest or site is default_first_site. 4 = Windows Server 2008 R2) Database. For LTI deployments. 4 = Windows Server 2008 R2) Domain Functional Level. 3 = Windows Server 2008. type the name of the site in which to install the domain controller. 4. 5.373 Microsoft Deployment Toolkit 2010 Update 1 3.com/technet/SolutionAccelerators . The %SYSTEMROOT% variable for Windows PE typically is set to X:\WINDOWS. Wait for critical replication only.ini file or the MDT DB. Contains the fully qualified path on the target computer to the location for the Sysvol folder. On the Properties tab. not the target operating system.ini file or the MDT DB. 3 = Windows Server 2008.ini or the MDT DB. The default value is %SYSTEMROOT%NTDS. Windows Server 2003. In the Site name box. You can also configure this value using the DatabasePath property in the CustomSettings. click Advanced. Windows Server 2003. Windows Server 2008 (2 = Windows Server 2003. so the %SYSTEMROOT% variable will return the SystemRoot folder for Windows PE. • Functional levels section: • • Folders section: • • • Note If you configure values in the CustomSettings. Select this option to populate only the directory services database using replication. Functional Levels.

ZTI deployments. it is a new installation of DNS zones of all types. and multiple zones—all in an automated process. secondary. For Windows Server 2003 target operating systems.” in the Configuration Manager Documentation Library. rather. restart the target computer after installing the Windows Support Tools for Windows Server 2003. Run the following command (where unc_path is the fully qualified UNC path to the folder in which the suptools. 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. There is also an option to manage aging. To configure and deploy the DNS server role 1. 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. 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. Configure DNS Server Role Settings for LTI and ZTI Using this option. included with System Center Configuration Manager. For more information about deploying an application in: • • LTI deployments. types.msi file resides): msiexec /i unc_path\suptools. see the section. 2. and stub zones as well as AD DS-integrated primary and stub zones. 3. By assigning the DNS server role.com/technet/SolutionAccelerators . updates. see Create a New Application in Deployment Workbench. install the Windows Support Tools for Windows Server 2003 as an application. and then click OK in the Task Name Properties dialog box to complete configuration of the task. “Configuring Software Distribution. ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps. Add a new task sequence step based on the Configure DNS task sequence type for: Solution Accelerators microsoft. If you choose this option. This is not a migration process from an existing DNS server.msi /q addlocal=all Alternatively. click OK to complete the configuration of the AD DS Advanced Properties dialog box.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 374 Then. configure and deploy the DNS server role to a new computer or a DNS server operating on an existing computer. you can configure standard DNS primary. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console.

com/technet/SolutionAccelerators . click Server Properties. In Description. and then click OK. 9. and then click OK. woodgrove. in Server Options. 4. In the Zones section. In the DNS Zone Properties dialog box. in Dynamic updates. in Name. Select the Scavenge stale resource records check box to enable this feature. Solution Accelerators microsoft. and then click OK. 16. 5. select one of the following: • None • Nonsecure and Secure 12. In the Change Zone Type dialog box. 6. 17. In the task sequence hierarchy. type a name for the zone (for example. In the Server Properties dialog box. select the Store the zone in Active Directory check box if DNS will be installed on a domain controller. select the appropriate name-checking options to enforce. Close the Deployment Workbench. in DNS zone name. 13. 14. Configure DHCP Server Role Task Sequence Step Settings for LTI and ZTI Using this option. click Roles. ZTI in the task sequence hierarchy. click the yellow Add button. in Name checking. In Type. 7. In the Server Properties dialog box. In the Change Zone Type dialog box. type name (where name is the name by which the task is identified in the task sequence). select one of the following zone types: • • Primary zone Secondary zone • Stub zone 10. 11. type description (where description is the description of the task and its role in the task sequence). 15. In the task_sequence Properties dialog box (where task_sequence is the name of the task sequence being edited). click Add. click MDT. 8. 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. and then click Configure DNS. and then click Configure DNS. click OK. click Change. configure and deploy the DHCP server role using MDT 2010.375 Microsoft Deployment Toolkit 2010 Update 1 • • LTI on the Task Sequence tab.com). On the Properties tab of the Configure DNS step. select the appropriate server options to enable. In the DNS Zone Properties dialog box. On the Properties tab. Click Add.

and then click Configure DHCP. click Add. if you run the Configure DHCP Server task sequence step in the same task sequence as the Configure DNS task sequence step. scope names). A description of the task (for example. click MDT.com/technet/SolutionAccelerators Solution Accelerators . ensure that you run the Use Toolkit Package and Gather task sequence steps prior to running any of the server role task sequence steps. On the Properties tab. 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. ZTI in the task sequence hierarchy. 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. 2. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. The Configure DNS task sequence step requires that the support tools be installed. click Roles. Configuring the DHCP scopes for the DHCP server role as described in Configure DHCP Scopes for the DHCP Server Role. microsoft. Note For ZTI task sequences that are not created using the MDT 2010 task sequence templates. Note For Windows Server 2003 target operating systems. Configuring the DHCP server options for the DHCP server role as described in Configure the DHCP Server Options for the DHCP Server Role. click Add. 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. For more information. configure the Authorize DHCP task sequence in conjunction with the Configure DHCP Server task sequence. see Configure DNS Server Role Settings for LTI and ZTI.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 376 To implement the DHCP server role. In the task sequence hierarchy. Add a new task sequence step based on the Configure DHCP Server task sequence type for: • • LTI on the Task Sequence tab. DHCP scope information. Description. type the relevant information in the following boxes: • • Name. To configure and deploy the DHCP server role 1. 3. and then click Configure DHCP. ensure that the Configure DHCP Server task sequence step precedes the task sequence step to install the Windows Support Tools for Windows Server 2003. The name by which the task will be identified in the task sequence list. The server role task sequence steps are dependent on the Use Toolkit Package and Gather task sequence steps.

2.250). Start IP address. 192.microsoft.377 Microsoft Deployment Toolkit 2010 Update 1 • • Scope details.1). End IP address. Subnet mask. In the Scope Properties dialog box. Lease duration for DHCP clients. 255. Scope IP address.255.150). 192.0. configure the DHCP scopes that contain the rules and active scopes used on the DHCP server.0.255. Click task_sequence_step (where task_sequence_step is the name of the task sequence step). ZTI in the task sequence hierarchy. The name used to refer to the scope. microsoft. click the yellow Add scope button. Server options.168. The mask used for the IP address scope (for example. Click OK. 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. The options passed to DHCP clients (for example. Details about the IP address the DHCP scopes configured.168. On the Properties tab. ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. default gateway. configure the following options as required for the environment: • • • • • • Scope name.com/technet/SolutionAccelerators • Solution Accelerators . DNS server. click task_sequence_step (where task_sequence_step is the name of the task sequence step). Modify the task sequence step you created based on the Configure DHCP task sequence type for: • LTI on the Task Sequence tab.0).com/en-us/library/bb727003.aspx. 192. To configure and deploy DHCP scopes 1.168. 4. and WINS server addresses). For more information about DHCP scope configuration options and for guidance on using each configuration option. Configure DHCP Scopes for the DHCP Server Role Using this option. In the task sequence hierarchy. The beginning address of the scope (for example. see “Chapter 6 – Dynamic Host Configuration Protocol” of TCP/IP Fundamentals for Microsoft Windows at http://technet. The maximum time a client can keep the IP address that the DHCP server assigns.0. 4. The address of the scope itself (for example. The ending address of the scope (for example. 3.

Configure the DHCP Server Options for the DHCP Server Role Using this option. 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. The address used for PXE client Bootstrap code.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 378 • Description. including router or default gateway designation.251).168. ZTI in the task sequence hierarchy. To configure and deploy DHCP server options 1. and then configure the following options as required for your environment. On the Properties tab.168. configure the following options for the scope created on the General tab: • • • • • 003 Router. 3. 192. 7.168. The default gateway given to DHCP clients. configure the DHCP server options given to DHCP clients. DNS server IP information. End IP address. Click OK.0.0. click task_sequence_step (where task_sequence_step is the name of the task sequence step). ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. The WINS server IP address (for example.com). Solution Accelerators microsoft. On the Options tab.com/technet/SolutionAccelerators • . 2. The ending address for exclusion from a scope (for example. 6. woodgove. Click task_sequence_step (where task_sequence_step is the name of the task sequence step).2). 006 DNS Servers. type the following information to exclude addresses for the scope created on the General tab: • • Start IP address. 046 WINS/NBT Node Type. Modify the task sequence step you created based on the Configure DHCP task sequence type for: • LTI on the Task Sequence tab. 192. click Configure. • 060 PXE Client. 015 DNS Domain Name. in the Exclude IP Address Range section. 044 WINS/NBNS Servers. On the Advanced tab. The WINS node type. The DNS server address given to DHCP clients.255). in the Server Options section. and WINS server information. In the task sequence hierarchy.0. A description of the scope (for administrative reference). The DNS domain name given to clients (for example. 192. 5. The beginning address for exclusion from a scope (for example.

and then. Click 015 DNS Domain Name.379 Microsoft Deployment Toolkit 2010 Update 1 4. type the IP address and resolve the name.com/technet/SolutionAccelerators .microsoft. 9. Click 006 DNS Servers. type the PXE client string (typically. Note The ZTI task sequence templates that are provided with MDT 2010 do not include an Authorize DHCP task sequence step type. and then type one of the following codes: 44. type the IP address and resolve the name.com/windowsserver/en/library/e71fac630521-4217-899f-79802bfdb7481033.mspx?mfr=true. woodgrove. Click 044 WINS/NBNS Servers. 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 an IP address. Click Add to type an IP address. 6. Click Add to type an IP address. and then. 8. Click 060 PXE Client. 5. in the String Value box. in the String Value box. type the domain name (for example. 46. Click 003 Router. For more information about how to determine the correct option for the environment. Click an IP address. 7. see the section. To authorize the DHCP server role in AD DS 1.com). Solution Accelerators microsoft. You must manually add this step type if you want to automatically authorize the DHCP server as a part of the ZTI deployment. type the IP address and resolve the name. and then perform the following tasks: • • • In the Server Name box.” in WINS Tools and Settings at http://technet2. and then click Remove to remove the highlighted IP address. and then click Remove to remove the highlighted IP address. and then click Remove to remove the highlighted IP address. PXEClient). Click Add to type an IP address. and then perform the following tasks: • • • In the Server Name box. or 47. “DHCP Options for WINS. Click an IP address. Click 046 WINS/NBT Node Type. 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 perform the following steps: • • • In the Server Name box.

• Description. and then type the following information in the relevant boxes: • • Username. 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. 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. Click Add. Click Set.exe command or a similar command to copy the content to the target computer. In the Account box. 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. For more information about modifying task sequence steps. In the task sequence hierarchy. On the Properties tab. Add a new task sequence step based on the Authorize DHCP task sequence type for: • • LTI on the Task Sequence tab. 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. click Roles. click Add. click MDT.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 380 ZTI as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. in the format domain\user Password. The name by which the task appears in the task sequence list. type the relevant information in the following boxes: • Name. Copy content to the target computer using $OEM$ folders as described Copy Content to Target Computers Using $OEM$ Folders.com/technet/SolutionAccelerators . then click OK again. The account that can authorize DHCP. Retype the password 5. type the name of an account with permissions to authorize the DHCP service in AD DS. A description of the task. when deploying Windows Solution Accelerators microsoft. 3. However. The password for the account • Confirm Password. Click OK. and then click Authorize DHCP. and then click Authorize DHCP. 4. • ZTI in the task sequence hierarchy. Copying Content to the Target Computer To copy content to target computers. see Configure the Task Sequence Steps and Step Sequence. 2.

and files that this folder contains in the %SystemRoot% folder of each destination computer. microsoft. Platform (where Platform is either x86 or x64).cab file in the Support\Tools folder on the Windows installation media. subfolders. 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. both of which are in the Deploy. and files that this folder contains in the corresponding drive during the setup process.com/technet/SolutionAccelerators • • Solution Accelerators . E. • MDT 2010 looks in the following locations within the deployment share. Create $OEM$ folders in this location to create a custom folder for each platform. Create $OEM$ folders in this location to create a custom folder for each operating system. in the order specified. For more information about using: • Data WIM files or $OEM$ folders with Windows Vista or Windows Server 2008. Note In an instance where multiple $OEM$ folders have been defined. and files that this folder contains in the %SystemDrive% folder on each destination computer. and so on). An $OEM$ folder with Windows XP or Windows Server 2003. Windows Setup copies any files put in $OEM$\D to the root of drive D on each destination computer. the first driver that LTIApply. data WIM files are preferred over $OEM$ folders. It replicates all the folders. This is typically drive C on most computers. It replicates all the folders. Create $OEM$ folders in this location to create a custom folder for each build. Windows Setup copies the contents of this folder to the root of the corresponding drive on each destination computer.381 Microsoft Deployment Toolkit 2010 Update 1 Vista or later operating systems. The following list describes each folder that you can create within an $OEM$ folder to organize these files: • $$. for example.chm) and the Microsoft Windows Preinstallation Reference (Ref. 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). see the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy. D. $1. Drive is a drive letter (C. For example. Drive. put the file in $OEM$\$$\System32. Operating Systems\Name (where Name is the name of the operating system MDT 2010 is installing). For Windows Setup to copy a file to %SystemRoot%\System32 on each destination computer. $OEM$.chm). It replicates all the folders.wsf finds is deployed to the target computer. Windows Setup copies the contents of this folder to %SystemRoot% on each destination computer. • • • An $OEM$ folder contains supplemental files. subfolders. Windows Setup copies the contents of this folder to %SystemDrive% on each destination computer. see the Windows Automated Installation Kit User’s Guide in the Windows AIK. subfolders.

oem file. evaluate environment variables to determine the rules to be used when deploying the images to the target computers. open the installation path of the deployment share. and perform many other intricate deployment tasks. Solution Accelerators microsoft. For Windows XP and Windows Server 2003.vbs script includes the common routines for database access. Develop Custom Scripts You can develop new scripts for use in LTI and ZTI deployments.vbs script. The standard MDT 2010 script is a . query the configuration database.com/technet/SolutionAccelerators . Creating Custom Scripts for MDT 2010 Scripts provide automation of the image-build and overall deployment process. 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. there is no need to modify one of the delivered scripts. update it. it is best to review how the scripts included with MDT 2010 are constructed. 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.vbs]) and Windows Script file (. Create new scripts for use in LTI and ZTI deployments from a template as described in Create New Scripts from a Template. For examples of scripts that the Deployment Workbench uses.vbs script and the ZTIDataAccess. Typically. copy the script to a new file. Before describing how to create a script.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 382 Microsoft recommends that these folders not be used. mass-storage device drivers. MDT 2010 scripts leverage this functionality by referencing the ZTIUtility. The scripts create log files as the scripts automate the deployment process. and thoroughly test the effect of any change. They scan the configuration files. Note Microsoft does not support customized and custom scripts. In most installations.wsf) scripts.wsf file. which allows references to be made to functions that are contained in other scripts.wsf files. and then open the Scripts folder. instead of modifying one of the delivered scripts. These scripts should be in the form of . These files may include OEM HALs. and the Txtsetup.oem file describes how to load and install these files. • TEXTMODE.vbs or . Use $1 to represent %SystemDrive%. The folders rely on a very specific disk configuration on the destination computer. $OEM$\$1 and $OEM$\C write to the same location: the root of drive C. List these files in the [OemBootFiles] section of the answer file. If a modification is necessary. MDT 2010 uses both Microsoft Visual Basic® Scripting Edition (VBScript [. The ZTIDataAccess.vbs script is used to initialize the MDT 2010 environment and setup classes. The ZTIUtility. instead. The Txtsetup.

wsf when processing database rules from the CustomSettings.com/technet/SolutionAccelerators . Provide access to databases and is defined in ZTIDataAccess.ini files. Provides the logging functionality that all MDT 2010 scripts use. Can be used to access databases in scripts instead of configuring the CustomSettings. Utility. Logging. Can be used to access web services in scripts instead of configuring the CustomSettings.383 Microsoft Deployment Toolkit 2010 Update 1 including connecting to and querying databases.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.vbs as described in Environment Class.ini or BootStrap. query the architecture using the command: Solution Accelerators microsoft.ini files. Provides general utility functionality and is defined in ZTIUtility.vbs as described in Utility Class. WScript Shell object oEnv. File System Object oShell. The Database class: • • Is used by ZTIGather. and is defined in ZTIUtility.Item("ComputerName") = "Example" Or. Database.ini files. The WebService class: • • Is used by ZTIGather. Configures environment variables gathered through WMI and MDT 2010 rule processing.vbs as described in Database Class. and provides a web service interface.ini or BootStrap. change the computer name to Example using the command: oEnvironment. Process Environment object oNetwork. You can specify the parameters for accessing the web services in the scripts.wsf when processing web service rules from the CustomSettings.vbs as described in Logging Class. WScript Network object Environment. The following classes are defined that perform several standard tasks: • • • • WebService. For example.ini or BootStrap.ini or BootStrap. Environment Class Reference this class in scripts through the oEnvironment object. The scripts define several standard objects that need not be declared in the script: • • • • • oFSO. Provides access to web services and is defined in ZTIDataAccess. creating a single log file for each script and a consolidated log file of all scripts and is defined in ZTIUtility. allowing for direct reference from the script.ini files.

vbs"/> <script language="VBScript" src="ZTIDataAccess.FindFile("CustomSettings. AssetTag. sIniFile) Database Class Reference this class in scripts through the Database class. SerialNumber. use the command: iRetVal = oUtility.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 384 oEnvironment. MacAddress" oDatabase.com/technet/SolutionAccelerators .CreateEntry "An error occurred".Instance = "SQLExpress" oDatabase.CreateEntry "Informational message".ScriptName To find the location of a file.LogTypeError Utility Class Reference this class in scripts through the oUtility object.Port = "" oDatabase. You can create an instance of the object class and connect to a database using following script excerpt: <script language="VBScript" src="ZTIUtility.vbs"/> <script language="VBScript"> Dim oDatabase Dim oRecordset Set oDatabase = new Database oDatabase.Table = "ComputerSettings" oDatabase.ParameterCondition = "OR" oDatabase. use the command: oLogging. use the command: oLogging.Item("Architecture") Logging Class Reference this class in scripts through the oLogging object.SQLServer = "NYC-MDT-01" oDatabase.ini". When creating an informational log entry.SQLShare = "DeploymentShare$" Solution Accelerators microsoft. use the command: oUtility. LogTypeInfo When creating an error log entry. To determine the name of the current script.Parameters = "UUID.Netlib = "DBNMPNTW" oDatabase.Database = "MDTDB" oDatabase.

385 Microsoft Deployment Toolkit 2010 Update 1 oDatabase. Custom Script Template <job id="Z-Sample"> <script language="VBScript" src="ZTIUtility.Query WScript.Parameters = "USZip" Set oXML = oWebService.Connect Set oRecordset = oDatabase.Query WScript. Listing 10 shows a template for creating custom scripts.com/technet/SolutionAccelerators . Listing 10.vbs"/> <script language="VBScript"> ' //********************************************************* ****************** ' // ***** Script Header ***** Solution Accelerators microsoft.XML Create New Scripts from a Template You can also create scripts for use in the imaging process.net/uszip.Echo "Records retrieved: " & oRecordset.Item("USZip") = "98029" oEnvironment.vbs"/> <script language="VBScript" src="ZTIDataAccess.webservicex.Item("USZip") = "98029" Set oWebService = new WebService oWebService. You can create an instance of the object class and connect to a database using following script excerpt: <script language="VBScript" src="ZTIUtility.xml file.WebService = "http://www.asmx/GetInfoByZIP" oWebService.Echo "Web service response:" WScript.vbs"/> <script language="VBScript"> Dim oWebService Dim oXML oEnvironment. You call these scripts by adding them to the Task Sequence Editor and ultimately by adding them to the TS.Echo oXML.RecordCount WebService Class Reference this class in scripts through the WebService class.

0.wsf [/debug:true] ' // ' // Customer Build Version: 1.com/technet/SolutionAccelerators .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.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 386 ' // ' // Solution: Solution Accelerator for Microsoft Deployment ' // File: Z-Sample.wsf ' // ' // Purpose: Template ' // ' // Usage: cscript Z-Sample.0 ' // Customer Script Version: 1.

• Package source for the Microsoft Deployment Toolkit Files package.387 Microsoft Deployment Toolkit 2010 Update 1 iRetVal = ZTIProcess ProcessResults iRetVal On Error Goto 0 '//-------------------------------------------------------------------------'// '// Function: ZTIProcess() '// '// Input: None '// '// Return: Success .non-zero '// '// Purpose: Perform main ZTI processing '// '//-------------------------------------------------------------------------Function ZTIProcess() iRetVal = Success ZTIProcess = iRetval '!!!!!!!!!!! End Function </script> </job> At a high level. Create the script based on the template.com/technet/SolutionAccelerators INSERT YOUR CODE HERE !!!!!!!!!!!! . Configure the task sequence step created in the previous step to run your script. 3. 2. Follow these guidelines when creating a script: Solution Accelerators microsoft. Place the script in the Scripts folder of the: • Deployment share for LTI deployments. 4. Create a task sequence step based on the Run Command Line task sequence step type in your task sequence. complete the following steps to add a custom script: 1.0 '// Failure .

com/technet/SolutionAccelerators .vbs and ZTIDataAccess. ' // ' // Checks to see if you have any EFS Keys. or a beta version of Office 2007 ' // ' //********************************************************* ****************** Option Explicit '//--------------------------------------------------------------------------'// Main routine '//--------------------------------------------------------------------------Dim iRetVal On Error Resume Next Solution Accelerators microsoft..vbs"/> <script language="VBScript"> ' //********************************************************* ****************** ' // ' // Microsoft IT Verify ' // ' // Verify that the local machine is ready for installation. Only create objects where required.vbs do not already provide the functionality required before writing a function. Script to Check for EFS Keys or Beta Versions of the 2007 Office System <job id="LTIGetFolder"> <script language="VBScript" src="ZTIUtility. 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.. because MDT 2010 includes most objects that are needed. Listing 11. Verify that ZTIUtility..Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 388 • • • Always declare variables.vbs"/> <script language="VBScript" src="WizUtility.

Item("DeploymentType") = "UPGRADE" then ' -------------------------------------------------------' Check for EFS keys in the registry. sError ZTIProcess = Success If oEnvironment." & vbNewLine & "More info: http://go.com/fwlink/?LinkId=79038" Solution Accelerators microsoft.0 '// Failure .com/technet/SolutionAccelerators .microsoft. On Error Resume Next CheckForEFS = empty CheckForEFS = oShell.389 Microsoft Deployment Toolkit 2010 Update 1 iRetVal = ZTIProcess ProcessResults iRetVal On Error Goto 0 '//-------------------------------------------------------------------------'// '// Function: ZTIProcess() '// '// Input: None '// '// Return: Success .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.non-zero '// '// Purpose: Perform main ZTI processing '// '//-------------------------------------------------------------------------Function ZTIProcess() dim CheckForEFS.

" oLogging. 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.CreateEntry sError. LogTypeWarning if MsgBox(sError & vbNewLine & "Press OK to continue". if HasOldOffice then sError = "Warning: Please Manually remove all Beta Office 2007 Components.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 390 oLogging. oApplication DIM sQuery Solution Accelerators microsoft.CreateEntry sError. vbOKCancel) = vbCancel then ZTIProcess = Failure exit function end if end if end if ZTIProcess = Success End Function Function HasOldOffice DIM oApplications.com/technet/SolutionAccelerators . LogTypeWarning if MsgBox(sError & vbNewLine & "Press OK to continue".

Solution Accelerators microsoft. vbTextCompare ) = 0 then oLogging. The preflight checks are run on the Preflight Checks page in the Operating System Deployment (OSD) Setup Wizard. MDT 2010 includes some preflight checks for deploying the Windows 7 operating system using UDI.CreateEntry "Old version of: '" & oApplication.391 Microsoft Deployment Toolkit 2010 Update 1 ' Enumerate through all applications installed on the local machine. "MUI". oApplication.1014'" set oApplications = objWMI. "Proof". oApplication. However.Name.Name.Version .com/technet/SolutionAccelerators . you may need to create custom preflight checks.0. sQuery = "(Name LIKE 'Microsoft Office%2007' or Name LIKE 'Microsoft Expression Web') and Version <> '12. 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. depending on the configuration and system resources of the target computers. vbTextCompare ) = 0 and instr(1.Count > 0 for each oApplication in oApplications ' Filter out MUI and Proof Packages if instr(1.Name & "' = " & oApplication.4518. Looking for pre-RTM Office versions.ExecQuery("SELECT * FROM Win32_Product WHERE " & sQuery) HasOldOffice = oApplications.

Exit code display message. Allow for silent program operation. UDIWizard. For example.wsf displays all preflight check programs. • Include detection for the appropriate target operating system. For each condition that can occur. For each exit code. Exit code value. In some instances the preflight check might be applicable to specific target computers. a preflight check program may be appropriate for Windows 7 RTM but may not be appropriate for Windows 7 with a service pack. you can specify: • • • Exit code state.com/technet/SolutionAccelerators Solution Accelerators . • • • 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. so your program needs to support being started in this way. For example. The preflight check program should detect the target operating system and run only if the target operating system is appropriate. Any required parameters for the preflight check program must be passed on the command line. • By default. 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 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. Include detection for the appropriate target operating system architecture. 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. 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. ensure that the program returns a unique error code. a preflight check program may be appropriate for a 32-bit version of Windows 7 but not for 64bit versions of Windows 7.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. the preflight check program could return the following exit codes as a subset of other exit codes: microsoft. For example. Allow for parameters to be passed to the program. The wizard starts the preflight check program using a command-line interface. Return a unique exit code for each condition that can occur within the program. The preflight check program should not open any dialog boxes or other windows during normal operation.

Solution Accelerators microsoft.wsf script is modified to display preflight check programs that are applicable for the target computer and target operating system. the preflight check program may be appropriate only for portable computers. The preflight check program ran with a success status but is not applicable for the target computer.wsf script runs the custom preflight check program named CustomPreflight1 if the operating system is any operating system except Windows XP: If Left(oEnvironment.Item("Architecture")) = "X86" then If Instr(sFilename.Item("OSCurrentVersion").1) = "5" then If Instr(sFilename. Or. The following excerpt from a modified UDIWizard. For example. the UDIWizard. the preflight check program may be appropriate for only 64-bit operating systems. the UDIWizard.393 Microsoft Deployment Toolkit 2010 Update 1 • • 0. "CustomPreflight1") > 0 then bRemove = true End if End if The following excerpt from a modified UDIWizard. The preflight check program finished with a success status.com/technet/SolutionAccelerators . 1.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 should only display preflight check programs applicable to 64-bit operating systems when the target operating system is a 64-bit operating system. The preflight check program encountered an error while running. the UDIWizard. • • • Modify the UDIWizard. In this method. The preflight check program ran with a warning status. 3. such as desktop.wsf script to filter preflight check programs. or portable computer. because the program works for the target computer but is not applicable for the target computer. 2. For example. For example.wsf script runs the custom preflight check program named CustomPreflight2 if the target computer is 64 bit: If UCase(oEnvironment. see Creating Custom Scripts for MDT 2010. "CustomPreflight2") > 0 then bRemove = true End if End if For more information about modifying MDT 2010 scripts. server.

for ZTI deployments. Extending the schema of the MDT DB as described in Extending the Schema of the MDT DB. 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. on a SQL Server computer on which MDT 2010 is installed.ini as described in Managing Configuration Settings Stored in the MDT DB. create a deployment share in the Deployment Workbench. Configuring the MDT 2010 deployment process to retrieve configuration settings from the MDT DB by changing CustomSettings. you do not need to add any content to the deployment share. create a new MDT DB or connect to an existing MDT DB in the Deployment Workbench. Note To create and manage the MDT DB for LTI or ZTI deployments. . the MDT DB is a centralized version of the CustomSettings. Assigning appropriate permissions to the MDT DB as described in Assigning the Appropriate Permissions to the MDT DB. 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. • • Creating a New MDT DB or Connecting to an Existing MDT DB Before you can manage configuration settings in the MDT DB. tables. However. or on any other SQL Server computer in your organization. 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 have a centralized repository for managing deployment configuration settings. such as views. Conceptually. The MDT DB contains the database objects that the MDT 2010 deployment process uses.ini file. and stored procedures. The advantage to using the MDT DB is that for larger deployments. Configuring MDT 2010 to access the MDT DB as described in Configuring the MDT 2010 Deployment Process to Access the MDT DB.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. Upgrading the MDT DB from a previous version of BDD or MDT as described in Upgrading an Existing MDT DB. You can store the MDT DB on the same SQL Server computer that is used for System Center Configuration Manager. as ZTI deployments do not require it.

2. and then create the MDT DB database objects in the database. 2.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. In Instance. Information for Completing the New DB Wizard On this wizard page SQL Server Details Do this 1. Point to Microsoft Deployment Toolkit. Click Start. In the Deployment Workbench console tree. the db_owner database role must exist in the database that the DBA created. Table 187. A new database as described in Create the MDT DB in a New Database. click New Database. and then click Deployment Workbench. type instance_name (where microsoft. 4. create the MDT DB in the new database using the Deployment Workbench. 3. Complete the New DB Wizard using the information in Table 187. The New DB Wizard starts. To create the MDT DB in an existing database 1. Create a New MDT DB Create a new MDT DB. The DBA creates the database and grants you DBA permission on the it. Connect to an existing MDT DB as described in Connect to an Existing MDT DB. 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. and then grant you the appropriate permissions to create the MDT DB objects in the new database. 5. 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). the DBA must create the MDT DB. Note To create the MDT DB. type computer_name (where computer_name is the name of the computer running SQL Server). You can create the MDT DB in: • • An existing database as described in Create the MDT DB in an Existing Database. In SQL Server name. and then point to All Programs. In the Actions pane.com/technet/SolutionAccelerators Solution Accelerators . When the database has been created.

If you are using Microsoft SQL Server Express. 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). 2. the information in the existing MDT DB tables and views will be lost. Note If you select a database that has an existing MDT DB. In Network Library. If you are using SQL Server installed as the default instance. Click Next. 4. Select Create (or recreate) the tables and views in an existing database. Click Next. SQL Share 1. Windows PE connects to the network shared folder. and microsoft. you can leave SQL Share blank. type port_number (where port_number is the TCP port number for the SQL Server instances if different than the default value).com/technet/SolutionAccelerators Summary Solution Accelerators . In SQL Share. If you are using the default value. 5. In Port. In Database. 3.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). This text box is required for Window PE to connect to the database using the Windows Integrated Security with Named Pipes protocol. Database 1. Review the information in the Details box. you can leave Port blank. If Windows PE is not connecting to the database using this protocol. select database_name (where database_name is the name of the database in which you want to store the MDT DB). you can leave Instance blank. type SQLExpress for the instance name. 3. 2. establishing a network connection to the server so that Windows Integrated Security in SQL Server authenticates correctly. 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). Click Next.

Tip You can click Save Output to save the output of the wizard to a file. Note To create the MDT DB. In SQL Server name. Information for Completing the New DB Wizard On this wizard page SQL Server Details Do this 1. In the Deployment Workbench console tree. In the Actions pane. Create the MDT DB in a New Database In instances where you are the SQL Server DBA or have the necessary permissions. The database configuration information is listed in the details pane of the Deployment Workbench. To create the MDT DB in a new database 1. In Port. 2. The New DB Wizard starts.com/technet/SolutionAccelerators Solution Accelerators . type SQLExpress for the instance name. type port_number (where microsoft.397 Microsoft Deployment Toolkit 2010 Update 1 On this wizard page Confirmation Do this then click Next. In Instance. 3. 4. 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). Click Start. Complete the New DB Wizard using the information in Table 188. you need the sysadmin or dbcreator server roles. you can create the new MDT DB. Table 188. 3. type computer_name (where computer_name is the name of the computer running SQL Server). and then point to All Programs. The New DB Wizard finishes. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. and then click Deployment Workbench. type instance_name (where instance_name is the name of the SQL Server instance on the computer running SQL Server). you can leave Instance blank. and then create the MDT DB database objects in the new database using the Deployment Workbench. If you are using SQL Server Express. Click Finish. If you are using SQL Server installed as the default instance. Point to Microsoft Deployment Toolkit. click New Database. 2.

SQL Share Summary Confirmation Click Finish. 1. 5. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. In SQL Share. Tip You can click Save Output to save the output of the wizard to a file. and then click Next. This text box is required for Window PE to connect to the database using the Windows Integrated Security with Named Pipes protocol. Review the information in the Details box. If Windows PE is not connecting to the database using this protocol.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). 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. In Database. 3. Click Next. In Network Library. Select Create a new database. The New DB Wizard finishes.com/technet/SolutionAccelerators . type database_name (where database_name is the name of the database in which you want to store the MDT DB). you can leave SQL Share blank. Windows PE connects to the network shared folder. Database 1. 2. 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. 2. The database configuration information is shown in the details pane of the Deployment Workbench. 4. Solution Accelerators microsoft. Click Next.

If you are using SQL Server Express. To connect to an existing MDT DB 1. 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). the MDT DB to another SQL Server instance. you can leave Instance blank. Table 189. 3. 2. In the Actions pane. 4. you can leave Port blank. In Port. 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). The New DB Wizard starts. 1. 4. 3. Note To connect to an existing MDT DB. If you are using SQL Server installed as the default instance. Complete the New DB Wizard using the information in Table 189.ini to access the MDT DB. which allows you to copy. Point to Microsoft Deployment Toolkit. type SQL Express for the instance name.399 Microsoft Deployment Toolkit 2010 Update 1 Connect to an Existing MDT DB You can connect the Deployment Workbench to an existing MDT DB.com/technet/SolutionAccelerators Database Solution Accelerators . 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). 5. click New Database. In Instance. you must be a user in the MDT DB and be granted the db_datareader database role. and then click Deployment Workbench. Select Use an existing database that already microsoft. and then point to All Programs. If you are using the default value. and then configure CustomSettings. or replicate. Click Next. type port_number (where port_number is the TCP port number for the SQL Server if different than the default value). 2. Click Start. In SQL Server name. type instance_name (where instance_name is the name of SQL Server instance on the computer running SQL Server). In the Deployment Workbench console tree. In Network Library.

The database configuration information is shown in the details pane of the Deployment Workbench. establishing a network connection to the server so that Windows Integrated Security in SQL Server authenticates correctly. you can manually upgrade the MDT DB using the UpgradeMDTDatabaseSchema Windows PowerShell cmdlet. Tip You can click Save Output to save the output of the wizard to a file. In Database. In SQL Share. This text box is required for Window PE to connect to the database using the Windows Integrated Security with Named Pipes protocol. 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). Review the information in the Details box. and then click Next. The upgrade process preserves any schema modification in the existing MDT DB when you upgrade to the new MDT DB. 2. select database_name (where database_name is the name of the existing MDT DB). you can leave SQL Share blank. Solution Accelerators microsoft. Click Next. 3. If Windows PE is not connecting to the database using this protocol. If for some reason the existing MDT DB is not upgraded when you upgrade the deployment share. Click Next. 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. SQL Share 1. Windows PE connects to the network shared folder. The New DB Wizard finishes.com/technet/SolutionAccelerators . You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.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. Summary Confirmation Click Finish.

Table 190.microsoft. you may need different permissions on the MDT DB. The tables contain configuration settings that are accessible through the views.401 Microsoft Deployment Toolkit 2010 Update 1 Assigning the Appropriate Permissions to the MDT DB Depending on the tasks to be performed. Table 190 lists the types of tasks to be performed and the corresponding SQL Server server roles and database roles required to perform them.aspx.com/en-us/library/aa905184.com/technet/SolutionAccelerators . 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. Solution Accelerators microsoft. Managing Configuration Settings Stored in the MDT DB The MDT DB contains tables and views that the MDT 2010 deployment process can query. 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.

and Administrator-level accounts with a location. use standard SQL Server database tools as described in Manage Configuration Settings Stored in the MDT DB Using SQL Server Management Tools. and Administrator-level accounts with target computers that are of the same make and model. packages.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. and Administrator-level accounts with a role. applications. and Administrator-level accounts with a computer. packages. Locations. A group of computers using the DefaultGateway property of the target computers to identify a geographic location. Associate property settings. SerialNumber. 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. because items in the other nodes can be associated with roles. 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. You can use the nodes in Table 191 to make configuration settings that are stored in the MDT DB.com/technet/SolutionAccelerators . roles. roles. applications. UUID. A group of computers based on the tasks performed by the users of the target computers (using the Role property). packages. The Deployment Workbench manages the updates to the corresponding tables in the MDT DB. Table 191. If you want to make bulk additions or updates to the MDT DB. A group of computers using the Make and Model properties of the target computers. applications. Solution Accelerators microsoft. applications. roles. 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. and Make and Model). Associate property settings. Associate property settings. Table 191 lists the nodes beneath the Database node and describes when to make configuration settings in each node. Associate property settings. packages. Roles Locations Make and Model Note Create the items in the Roles node before creating items beneath the other nodes (Computers. or MACAddress properties.

click New. In the Deployment Workbench console tree. 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. 9. Manage location-based configuration settings as described in Manage Location-based Configuration Settings in Deployment Workbench. Solution Accelerators microsoft. 6. and then point to All Programs. 7. Click Start. In the Actions pane. Click the Packages tab. Manage Computer-based Configuration Settings in Deployment Workbench To manage computer-based configuration settings. 2. Manage Role-based Configuration Settings in Deployment Workbench To manage role-base configuration settings. Click Start. Point to Microsoft Deployment Toolkit. click the Identity tab. and then click Deployment Workbench. 4. In the Role name box. 5. In the Properties dialog box. and then point to All Programs.com/technet/SolutionAccelerators . configure the accounts to be made members of the local Administrators group on the target computers. Click the Details tab. Click the Administrators tab. Manage computer-based configuration settings as described in Manage Computer-based Configuration Settings in Deployment Workbench. Point to Microsoft Deployment Toolkit. perform the following steps: 1.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. and then configure the packages to install and the order of the package installation. type role_name (where role_name is the name of the role). Click the Applications tab. and then configure the relevant property values identified earlier in the process. and then click Deployment Workbench. 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). and then click OK. 8. and then configure the applications to install and the order of the application installation.

Toolkit Reference. 3. 6. Solution Accelerators microsoft. click New.) For more information about the values for asset tag. Table 192. and MACAddress properties in the MDT 2010 document. serial number. UUID. type the information listed in Table 192. Note You only need to provide one of the methods for identifying the new computer from the list of the AssetTag.com/technet/SolutionAccelerators . and then configure the appropriate property values identified earlier in the process. Click the Roles tab. SerialNumber. and MAC address. 9. and then configure the applications to install and the order of the application installation. Click the Packages tab. 4. you can specify any of the MAC addresses. and then click OK. MDT 2010 identifies the target computer by any MAC address. SerialNumber. 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. 5. configure the accounts to be made members of the local Administrators group on the target computers. 7. 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).Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 404 2. Click the Administrators tab. and then configure the roles to associate with the computer. UUID. and then configure the packages to install and the order of the package installation. Click the Details tab. Click the Applications tab. UUID. In the Deployment Workbench console tree. In the Properties dialog box. 8. on the Identity tab. In the Actions pane. and MACAddress properties. see the AssetTag.

Click Start. In the Properties dialog box. In the Deployment Workbench console tree. and then click Deployment Workbench. 2. Solution Accelerators microsoft. perform the following steps: 1. In the Actions pane. In the Properties dialog box. 3. in the Location box. 3.405 Microsoft Deployment Toolkit 2010 Update 1 Manage Location-based Configuration Settings in Deployment Workbench To manage location-base configuration settings. Click the Roles tab. Click the Packages tab. and then configure the appropriate property values identified earlier in the process. In the Deployment Workbench console tree. 4. Point to Microsoft Deployment Toolkit. click New. type the IP addresses for all default gateways that exist within the location. 6. on the Identity tab. Click the Administrators tab. 2. 8. 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 point to All Programs. and then configure the roles to associate with the computer. 10. 9. Click Start. Click the Applications tab. In the Properties dialog box. and then configure the applications to install and the order of the application installation. Manage Make and Model–based Configuration Settings in Deployment Workbench To manage make and model–based configuration settings. and then configure the packages to install and the order of the package installation. Click the Details tab. perform the following steps: 1. click the Identity tab. In the Actions pane. and then click Deployment Workbench. on the Identity tab. configure the accounts to be made members of the local Administrators group on the target computers. in the Default gateways box. Point to Microsoft Deployment Toolkit. click New. 4.com/technet/SolutionAccelerators . 7. type location_name (where location_name is the user-friendly name to associate with the location) 5. 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). and then click OK. and then point to All Programs.

The Transact-SQL language allows you to add. 9. 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. 6. Click the Packages tab. This bulk import/export tool allows you to import configuration settings to and export configuration settings from the tables in the MDT DB. 10. Toolkit Reference. or delete entries in tables in the MDT DB. bcp utility (Bcp. see the section. configure the accounts to be made members of the local Administrators group on the target computers. In the Model box. and then configure the packages to install and the order of the package installation. and then configure the appropriate property values identified earlier in the process.” in the MDT 2010 document. 11. However. Click the Applications tab. Click the Administrators tab.exe). • • You can review the tables. type make_name (where make_name is the exact make [manufacturer] name returned by the BIOS of the target computer using WMI). update. and then configure the applications to install and the order of the application installation. Solution Accelerators microsoft. views. use SQL Server database management tools. Click the Roles tab. 7. “Tables and Views in the Deployment Workbench Database. In the Make box. type model_name (where model_name is the exact model name returned by the BIOS of the target computer using WMI). 8. and then click OK. Transact-SQL language in SQL Server. For more information on the tables and views in the MDT DB. and then configure the roles to associate with the computer. 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.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 406 5. Perform bulk import and update of configuration settings in the MDT DB using: • Microsoft Office system applications. 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. and other database objects in the MDT DB to determine the tables that you want to update. Click the Details tab.com/technet/SolutionAccelerators .

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). use the Configure DB Wizard to modify the CustomSettings. the wizard recognizes any columns that you have added to the existing tables and views. The Configure DB Wizard starts.ini file. Effort required to modify the CustomSettings. or stored procedures.ini file. or stored procedures. In the Actions pane.ini.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.ini file to enable retrieval of configuration settings from the MDT DB. 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. click Configure Database Rules. 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. 3. 2.ini file if you have added database objects. You can modify CustomSettings. Point to Microsoft Deployment Toolkit.ini file as described in Configure Access to the MDT DB by Directly Modifying the CustomSettings. views. The advantages of using this wizard is that it helps reduce the: • • Possibility of configuration errors in the CustomSettings. Only make direct modifications to the CustomSettings. Run the Configure DB Wizard for each deployment share defined in the Deployment Workbench that will be updated. views. To configure CustomSettings. However. and then point to All Programs. such as tables. such as tables. In the Deployment Workbench console tree. In most instances. Click Start. Solution Accelerators microsoft.com/technet/SolutionAccelerators . and then click Deployment Workbench.ini for database queries using the Configure DB Wizard in the Deployment Workbench 1. Directly modify the CustomSettings.ini File.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.

and then click Next. Complete the Location Options wizard page using the information in Table 194. and then click Next. Query the roles associated with the computer on the Roles tab of the computer item’s Properties dialog box.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 408 4. 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. Complete the Computer Options wizard page using the information in Table 193. 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. 5. 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. 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. Table 194. 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 the settings configured on the Details tab of the location item’s Properties dialog box. Table 193. Query the roles associated with the location on the Roles tab of the location 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.

Query the roles associated with the make and model on the Roles tab of the make and model item’s Properties dialog box. 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. 7. 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 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. Solution Accelerators microsoft. and then click Finish.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. 6. Table 196. 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. Complete the Make/Model Options wizard page using the information in Table 195.com/technet/SolutionAccelerators . 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. 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.

Listing 12 provides an example of the CustomSettings. review the information. On the Summary wizard page. On the Confirmation wizard page.ini file is configured to perform the selected queries. MMAdmins. review the information in the Details box. and then click Finish. The CustomSettings. MMSettings. and then click Next. the CustomSettings. Listing 12. MMPackages. MMApps. LApps. LRoles. LPackages. AssetTag.ini file after the Configure DB Wizard has finished. RSettings. LAdmins. SerialNumber. When the Configure DB Wizard has finished. 9.com/technet/SolutionAccelerators .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. CApps. Locations. 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. RPackages. RAdmins. CAdmins. RApps.ini File After the Configure DB Wizard Has Finished [Settings] Priority=CSettings. CRoles. LSettings. MacAddress ParameterCondition=OR Solution Accelerators microsoft. MMRoles. CPackages.

com/technet/SolutionAccelerators . 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. AssetTag. AssetTag.411 Microsoft Deployment Toolkit 2010 Update 1 [CPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerPackages Parameters=UUID. MacAddress ParameterCondition=OR [CRoles] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=ComputerRoles Parameters=UUID. SerialNumber. MacAddress Solution Accelerators microsoft. 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 .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.

com/technet/SolutionAccelerators . Model Order=Sequence [MMApps] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW 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 [MMPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelPackages Parameters=Make.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 414 SQLShare=Client Table=MakeModelApplications Parameters=Make. Model Order=Sequence [MMAdmins] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelAdministrators 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. Model [MMRoles] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelRoles Parameters=Make.

Microsoft Deployment Toolkit Samples Guide. Solution Accelerators microsoft. Toolkit Reference. “Automating Deployment by Location” in the MDT 2010 document.” in the MDT 2010 document.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 Computer Make and Model” in the MDT 2010 document. “Tables and Views in the Deployment Workbench Database. Microsoft Deployment Toolkit Samples Guide. see: • For more information about customizing tables and views in the configuration database. “Automating Deployment by Role” in the MDT 2010 document. Microsoft Deployment Toolkit Samples Guide. The corresponding section for each property in the section. “Properties. see: • The section. Microsoft Deployment Toolkit Samples Guide. see: • • • • “Automating Deployment to a Specific Computer” in the MDT 2010 document.com/technet/SolutionAccelerators . Toolkit Reference. For more information about customizing each property.” in the MDT 2010 document.

microsoft. and minimizes the risk of configuration errors. if you need to create custom queries for information. too: You must specify one or the other. 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. Specifies the name of the MDT DB in the SQL Server instance specified in the Instance property. If you are using: • SQL Server installed as the default instances. If you specify the Table property. Toolkit Reference. Table 197 lists the MDT 2010 properties that are used to create the query. which is used when performing user authentication using Windows Integrated Authentication with Named Pipes protocol.ini File The Configure DB Wizard in the Deployment Workbench provides the method that requires the least effort.ini file that are used to build an SQL query. you cannot specify the StoredProcedure property. Specifies the table or view to be used in the query. you can leave Instance blank.com/technet/SolutionAccelerators Database Netlib SQLShare Table StoredProcedure Solution Accelerators . too: You must specify one or the other. However.ini file is modified. 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). Specifies a network shared folder on the computer specified in the SQLServer property. For more information on the properties in Table 197. see the corresponding section for each property in the section. you can modify CustomSettings. • SQL Server Express.” in the MDT 2010 document. Table 197. “Properties. The Configure DB Wizard creates entries in the CustomSettings. requires minimal knowledge about how the CustomSettings. Specifies the stored procedure to be used in the query. you cannot specify the Table property. type SQLExpress for the instance name.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 416 Configure Access to the MDT DB by Directly Modifying the CustomSettings.ini to return the proper query results. If you specify the StoredProcedure 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. Note The SQL query that these properties create returns all columns from the table or view specified in the Table property. you must specify ParameterCondition=OR.com/technet/SolutionAccelerators . which directs MDT 2010 to process the [CSettings] section later in the CustomSettings. MacAddress ParameterCondition=OR The Priority line in the CustomSettings. The properties in the [CSettings] section performs the Solution Accelerators microsoft. AssetTag. The CustomSettings. Most of these properties in Table 197 were configured when you created the MDT DB. ParameterCondition Specifies the Boolean operation to be performed when you specify more than one selection criterion in the Parameters property. Listing 13 provides an example of CustomSettings. Listing 13. Conceptually.ini file. SerialNumber. If you want to use a Boolean OR operation.ini File After the Configure DB Wizard Has Finished [Settings] Priority=CSettings. this property is the WHERE clause in an SQL SELECT statement.ini file contains the Computers value. Default [Default] OSInstall=YES [CSettings] SQLServer=NYC-SQL-01 Instance=SQLEXPRESS Database=MDTDB Netlib=DBNMPNTW SQLShare=SQL$ Table=ComputerSettings Parameters=UUID. this property is the ORDER BY clause in an SQL SELECT statement.417 Microsoft Deployment Toolkit 2010 Update 1 Property Parameters Description Specifies the selection criteria for returning rows from the query. Conceptually. Order Specifies the sort order of the rows returned from the query. You can select either Boolean AND (the default) or OR operations.

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. You can review the tables and views in the MDT DB to determine the columns you want to reference in the Parameters property.” in the MDT 2010 document. Create a task sequence step that references the new column as described in Reference the New Column in a Task Sequence Step. Views using the SQL Server Management Studio or the ALTER VIEW Transact-SQL statement.com/technet/SolutionAccelerators . see the section. “Tables and Views in the Deployment Workbench Database. For more information on the tables and views in the MDT DB. 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. roles. If so. there may be instances in which you need to extend the information associated with one or more of the entities in the MDT DB. 5.ini File. see the section. Create a backup of the existing MDT DB as described in Create a Backup of the MDT DB. such as the computer name or IP address of the target computer. You extend the schema for the: • • Tables using the Microsoft SQL Server Management Studio or the ALTER TABLE Transact-SQL statement. For more information on the tables and views in the MDT DB. To extend the schema of the MDT DB 1. Toolkit Reference. Solution Accelerators microsoft. Modify the tables using SQL Server Management Studio or the ALTER Transact-SQL statement as described in Modify the Table. 4. 3. 2. you must extend the schema for one or more of the tables and views in the MDT DB.” in the MDT 2010 document. review the tables and views in the MDT DB to determine which you need to modify. 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. you might also need to modify the views that depend on those tables. 6. locations. or the makes and models. Reference the new column in the CustomSettings. If you extend the schema for the tables.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. such as computers. “Tables and Views in the Deployment Workbench Database. To extend the schema of the MDT DB.ini file as described in Reference the New Column in the CustomSettings. Toolkit Reference.

Create a backup of the MDT DB using: • SQL Server Management Studio. For more information on how to add a column using SQL Server Management Studio. For more information on how to perform database backups using this method. To make the antivirus server information available. see “How to: Insert Columns into Tables (Visual Database Tools)” in SQL Server Books Online.” in the MDT 2010 document. create a backup of the MDT DB before modifying the tables and views in it. • Modify the Table You modify the table by adding new columns to it. included with SQL Server. Existing SQL Server backup solution in your organization. “Tables and Views in the Deployment Workbench Database. Toolkit Reference. Retrieve the information through the LocationSettings view. Note the views provided with MDT 2010 do not require modification. For more information on the tables and views in the MDT DB.com/technet/SolutionAccelerators Solution Accelerators . The table most commonly modified is Settings. look at the Transact-SQL statements used to create the view by right-clicking the view. Tip To determine which views are dependent on a table.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. and then clicking Edit. You add new columns to tables in the MDT DB using: • SQL Server Management Studio. To do this. microsoft. Create a Backup of the MDT DB As a best practice. they must: • • Modify the Settings table. 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. see the section. the bank’s IT pros need to add an antivirus server configuration setting for each location that they define in the MDT DB. For more information on how to perform database backups using this method. see “How to: Back Up a Database (SQL Server Management Studio)” in SQL Server Books Online. such as the ComputerSettings or LocationSettings. see the documentation for your backup solution. included with SQL Server. because they already return all columns. which is common to all views. or contact your DBA.

Modify the dependent views in the MDT DB using: • SQL Server Management Studio.com/technet/SolutionAccelerators . For more information on how to perform this task using other SQL Server management tools. see the section. The SQL data type for each column you will add to the table. Example: How Woodgrove Bank Modified Tables Woodgrove Bank will add a new column to the Settings table called AVServer. you can skip this step. The columns that you will add to the table. “Working Solution Accelerators microsoft. included with SQL Server. modify any views you want to display for the newly created column.” in SQL Server Books Online. Note the views provided with MDT 2010 do not require modifications. 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. see the section. The AVServer column will contain the computer name of the antivirus server for each location specified in the LocationIdentity table. you need to know: • • • • • For more information on how to determine what to use for each item in the previous list. Check constraints for the new column (optional). For more information on how to add a column using SQL Server Management Studio. If the new column allows Null values. For more information on how to add a column using the ALTER TABLE Transact-SQL statement. • To add a new column to a table. Woodgrove Bank has decided to create the AVServer column using the information in Table 198. because all these views already return all columns. If you have not created custom views. The default value for the new column (optional). you would add the new column to custom views that you have created. Typically. included with SQL Server. see “ALTER TABLE (Transact-SQL)” in SQL Server Books Online.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 420 • ALTER TABLE Transact-SQL statement. Other SQL Server management tools. Table 198. “Table Column Properties (SQL Server Management Studio). see the documentation for the corresponding tool.

This reference initiates the query defined in the query section that you will create in a later step. if required. • ALTER VIEW Transact-SQL statement.421 Microsoft Deployment Toolkit 2010 Update 1 with Views (Visual Database Tools). For more information on how to drop a view using the ALTER VIEW Transact-SQL statement. see the documentation for the corresponding tool. Even if the views do not require modification. However. Reference the New Column in the CustomSettings. or RoleSettings views. "sp_refreshview (TransactSQL).” in SQL Server Books Online. This allows all the views to return the computer name of the antivirus server. This step may not be necessary if CustomSettings.ini file to reference the new column.ini file. see the section.ini File After you have added the column to the table and modified the appropriate views. Example: How Woodgrove Bank Modified the Dependent Views Woodgrove Bank does not need to modify any views. LocationSettings. • To modify the dependent view. Add the new column name to the Properties line in the CustomSettings. see the section. To reference the new column in the CustomSettings. if required. perform the following steps: 1. 2. MakeModelSettings. included with SQL Server. ”Modifying Views. included with SQL Server. configure the CustomSettings. The columns that you will add to the view.ini file. refresh all views that reference modified tables by running the sp_refreshview stored procedure. included with SQL Server. Other SQL Server management tools.” in SQL Server Books Online. as the LocationSettings view already returns all columns from the Settings table.com/technet/SolutionAccelerators . “ALTER View (Transact-SQL). included with SQL Server.” 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. Solution Accelerators microsoft.” in SQL Server Books Online.ini already has an existing query for the view or table referenced in the query. The SQL SELECT statement used to create the view.ini file. For more information on how to perform this task using other SQL Server management tools. Woodgrove Bank ran the sp_refreshview stored procedure to refresh the ComputerSettings. you need to know: • • For more information on determining what to use of each of the items in the previous list. see the section. which reference the Settings table. Add a reference to the query section on the Priority line in the CustomSettings. For more information about the sp_refreshview stored procedure.

which queries the appropriate table or view. The LSettings query already exists in the CustomSettings.ini File to Retrieve Antivirus Server for Woodgrove Bank [Settings] Priority=LSettings. if you create a column named Zip_Code. As shown in Listing 14. the task sequence variable will be named Zip_Code.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. Create a query section that was referenced in step 1.ini file after running the Configure DB Wizard. Listing 14.ini File Woodgrove Bank queries the LocationSettings view to return the antivirus server for a particular location. 3. For example. The variable will have the same name as the column. 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.com/technet/SolutionAccelerators . You reference the new column as a task sequence variable in the task sequence step. you are ready to reference the new column in a task sequence step. CustomSettings. 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. Example: How Woodgrove Bank Referenced the New Column in the CustomSettings. Example: How Woodgrove Bank Referenced the New Column in a Task Sequence Step Solution Accelerators microsoft.ini file is modified to return the configuration settings from the new column.

exe -server %AVSERVER% Solution Accelerators microsoft.423 Microsoft Deployment Toolkit 2010 Update 1 Woodgrove Bank creates a custom task sequence step to run the antivirus setup program. the antivirus server name can be provided by using the –server parameter and referencing the new column name as a task sequence variable (%AVSERVER%).com/technet/SolutionAccelerators . As a part of the antivirus setup program. The command line used to run the antivirus setup program is: avsetup.

the remainder of the deployment process refers to these shared folders by these names.424 Microsoft Deployment Toolkit 2010 Update 1 Preparing the MDT 2010 Migration Resources During deployment to the target computers. However. Table 199. configure the appropriate shared folder permissions. This folder is optional for either deployment. Table 199 lists the shared folders that must be created and describes the purpose of each. Note The files in Table 199 are recommended shared folder names. To configure the shared folder permissions for the folders listed in Table 199 . Use any name for these shared folders. Prepare the MDT 2010 migration resources by: • • • Creating additional shared folders as described in Creating Additional Shared Folders. Ensure that unauthorized users are unable to access user state migration information and the deployment logs. Configuring Shared Folder Permissions After creating additional shared folders listed in Table 199. Configuring access to other resources as described in Configuring Access to Other Resources. deployment scripts connect to the deployment shares and shared folders. Only the target computer creating the user state migration information and the deployment logs should have access to these folders. Stores the deployment logs during the LTI or ZTI deployment process. create additional shared folders in which to store the user state migration data and the deployment logs. Create accounts for the scripts to use when accessing these resources. Configuring shared folder permissions as described in Configuring Shared Folder Permissions. Creating Additional Shared Folders Before starting the deployment. Shared Folders and Their Descriptions Shared folder Description MigData Logs Stores the user state migration data during the LTI deployment process.

In some instances. click Add. type Authenticated Users. ZTI deployments by substituting Authenticated Users in the steps above with the network access account in System Center Configuration Manager. click This folder only. In the Enter the object name to select box. In the Security dialog box.com/technet/SolutionAccelerators . Solution Accelerators microsoft. In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). On the Permissions tab. and then click OK. clear the Allow inheritable permissions from the parent to propagate to this object and all child objects check box. The resources include application or database servers (such as Microsoft SQL Server 2005 or Microsoft Exchange Server 2003). in the Apply onto list.425 Microsoft Deployment Toolkit 2010 Update 1 1. 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 Permissions list. the MDT 2010 scripts might require access to other resources. In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). Repeat steps 10–13 for each group that will receive Administrator privileges. and then click OK. This action allows domain computers and domain users to access the subfolders they create. you may want to further restrict the user accounts that can access the shared folder. On the Permissions tab. 3. click Add. 12. 6. in the Apply onto list. click Allow for the Full Control permission. 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. 2. 13. type CREATOR OWNER. and then click OK. 10. in the Permissions list. 5. Configuring Access to Other Resources In addition to the shared folders just created. In Windows Explorer. 11. click Remove. In the Enter the object name to select box. right-click shared_folder (where shared_folder is one of the shared folders listed in Table 156). and then click OK. 4. click Advanced. On the Permissions tab. click Subfolders and files only. In the Permission Entry for shared_folder dialog box (where shared_folder is one of the shared folders listed in Table 199). 8. 7. On the Security tab. 9. and then click Properties.

com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Preparing Migration Resources 426 Access is granted to the credentials specified in the: • • • UserID. Solution Accelerators microsoft. Configure access to the deployment share created in the Deployment Workbench.wsf script. Configure access to resources that are referenced using the ZTIConnect. Any resources accessed using the ZTIConnect.wsf script to establish these connections. Note Other connections to the same servers. such as Named Pipes and RPC. UserPassword. use the same credentials listed above. and UserDomain properties for LTI deployments. see the MDT 2010 document. Configure access to applications or databases that are accessed through the SQLServer. Microsoft Deployment Toolkit 2010 Samples Guide. Network access account used by the System Center Configuration Manager Client for ZTI deployments. Grant access to the following resources: • • • Any resources on application or database servers for LTI or ZTI deployments. SQLShare. MDT 2010 deployment share for LTI deployments. and Database properties. Windows Deployment Wizard for LTI deployments.wsf script for LTI or ZTI deployments. Note For further guidance on using the ZTIConnect.wsf script. Use the ZTIConnect.

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. 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.com/fwlink/?LinkId=81031. “Deploying and Managing the Windows Deployment Services Update on Windows Server 2003.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.microsoft. For these scenarios. Install images created in the Deployment Workbench on the target computers. You can create custom WIM images in the Deployment Workbench that you can deploy directly to target computers using Windows Deployment Services. Preparing Windows Deployment Services for use in UDI deployments as described in Preparing Windows Deployment Services for UDI Deployments. Preparing Windows Deployment Services for use in ZTI deployments as described in Preparing Windows Deployment Services for ZTI Deployments.10). see: • • • Windows Deployment Services at http://technet. Prepare Windows Deployment Services for LTI deployments by: . The Windows Deployment Services Help file. • For more information about setting up and configuring Windows Deployment Services. included in Windows Deployment Services.” at http://go. These boot images can be Windows PE images or custom images that can deploy operating systems directly to the target computers. you can automate starting Windows PE using Windows Deployment Services.microsoft. 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.aspx. The white paper.com/enus/library/cc772106WS.

Note This mode is supported only in Windows Server 2003. 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. To use Windows Deployment Services for LTI. 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. This configuration supports only: • Windows PE as the boot operating system. microsoft. • Administration using the normal RIS tools. not in Windows Server 2008 or later server operating systems. 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.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. • Images created by Risetup. Mixed Allows compatibility with RIS and Windows Deployment Services. Riprep. This configuration supports only: • OSChooser or Windows PE as the boot operating system. or WIM. Windows Deployment Services Operating Modes Mode Legacy Description Functionally equivalent to Remote Installation Service (RIS). Note This mode is supported only in Windows Server 2003. • Images created by Remote Installation Service Setup (Risetup) and Remote Installation Preparation (Riprep).com/technet/SolutionAccelerators Solution Accelerators . Native Provides only Windows Deployment Services–specific support. • • • 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. Table 200. • Administration using the normal RIS tools or Windows Deployment Services management tools. run Windows Deployment Services in Mixed or Native mode. not in Windows Server 2008 or later server operating systems. Table 200 compares the operational modes of Windows Deployment Services. This configuration supports only: • OSChooser as the boot operating system.

Depending on the Windows Deployment Services configuration. because it is the simplest method.10). 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. You can configure Windows Deployment Services to respond to computers that are known or unknown.microsoft. Target computers that are not pre-staged do not have computer accounts in AD DS domains (also called unknown computers). which is included in Windows Deployment Services.exe tool. Only Windows Deployment Services can use the pre-staged computer accounts. Note Responding to unknown computers is the preferred method for LTI deployments. • Administration using the Windows Deployment Services management tools. LTI will not use a pre-staged computer account when joining the domain. see: • • “Add an Image. the computer accounts exist in AD DS domains (also called known computers). How to Manage Images at http://technet.” in Windows Deployment Services Help. For more information about adding an LTI boot image to Windows Deployment Services. LTI is unable to use the pre-staged computer account. If you pre-stage the target computers. Solution Accelerators microsoft.429 Microsoft Deployment Toolkit 2010 Update 1 Mode Description • Images created by WIM. Instead. When target computers are pre-staged. pre-staging the target computers is not necessary. Note Add the LTI boot images only to Windows Deployment Services. LTI uses the computer name and credentials configured in the task sequence or through the rules process. Note If Windows Deployment Services is configured to respond to any computer (known or unknown). Doing so allows Windows Deployment Services to automatically initiate LTI deployment by starting LTI boot images. Doing so authorizes Windows Deployment Services to deploy operating system images to the target computer. You do not need to add operating system images from the Deployment Workbench.com/technet/SolutionAccelerators .com/enus/library/cc732961(WS. Note This mode is supported only in Windows Server 2003. You can add LTI boot images to Windows Deployment Services using the Windows Deployment Services management console or the WDSUTIL. you may need to pre-stage the target computers. not in Windows Server 2008 or later server operating systems.aspx. Pre-stage Target Computers for Windows Deployment Services for LTI Deployments You can pre-stage PXE client computers in AD DS domains.

mspx. review the information displayed.microsoft. and then click Next.com/WindowsServer/en/library/c2d81caf-dd93-4f4b-bc2d907c0413805c1033. The following remote installation server. 6. point to Administrative Tools. This option designates a specific server to service the computer. Images stored in Windows Deployment Services cannot be deployed using multicast transfer. In the Computer’s unique ID (GUID/UUID) box. select one of the following options. By default. In the Host server dialog box. For LTI deployments. the Deployment Workbench creates a multicast namespace for the deployment share.Using the Microsoft Deployment Toolkit: Preparing Windows Deployment Services 430 To pre-stage the target computers for Windows Deployment Services 1. 4. • 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. 7. type computer_name (where computer_name is the name of the target computer). In the New Object – Computer dialog box. 2. and then click Finish. in the Computer name box.” at http://technet2. In the Managed dialog box. right-click organizational_unit (where organizational_unit is the name of the OU that will contain the target computer). see the Microsoft TechNet document. and then click Computer. Close all open windows. select the This is a managed computer check box. multicasting support is disabled in MDT 2010. “Locate the GUID for client computers. Solution Accelerators microsoft. point to New. Note For more information on locating the GUID for target computers. The images are transferred to the target computers using multicast from the deployment share. In the New Object – Computer dialog box. not from a Windows Deployment Services share. 3. and then click Active Directory Users and Computers. type guid_uuid (where guid_uuid is the GUID/UUID of the computer). and then click Next. 5. Specify the FQDN of the server running Windows Deployment Services.com/technet/SolutionAccelerators . and then click Next: • Any available remote installation server. Click Start. In the console tree. Note MDT 2010 supports only the multicast transfer of images stored in the LTI$ distribution share. This option specifies that this computer can be serviced by any RIS/Windows Deployment Services server. which reduces the amount of network traffic required when multiple computers need to receive the same image.

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 other client computers request the same image. MDT 2010 supports multicast-based deployments when MDT 2010 and the deployment share are installed on: • The computer running Windows Deployment Services. Enable Multicast Deployments with MDT 2010 Installed on the Same Computer as Windows Deployment Services In this scenario. To enable multicast deployments with MDT 2010 installed on the same computer as Windows Deployment Services 1. Then.com/technet/SolutionAccelerators . Note You cannot use these scenarios to allow multicast for boot images. • Note The Multicasting feature in MDT 2010 is only supported in Windows Server 2008 or later server operating systems. they are joined to the transmission that has already started. as the multicast client is not loaded until after Windows PE is running. as soon as an applicable client computer requests an installation image. In this scenario. 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. 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. Note If the computer on which MDT 2010 is installed is running Windows Server 2003. Install Windows Server 2008 or a later server operating system on the computer that is to be the deployment server. you must install the Remote Server Administration Tools feature so that the WDSUTIL command-line utility is available. Solution Accelerators microsoft. LTI only uses multicast to transfer operating system WIM files. In this scenario. • A computer other than the computer Windows Deployment Services is running on. In this scenario. MDT 2010 is installed on a computer running Windows Server 2008 or a later server operating system with the Window Deployment Services server role. you must configure Windows Deployment Services manually. MDT 2010 can automatically configure Windows Deployment Services to support multicast deployments.431 Microsoft Deployment Toolkit 2010 Update 1 The multicast types available for use in LTI deployments include: • Auto-Cast. Scheduled-Cast. In this option. a multicast transmission of the selected image begins.

Enable Multicast Deployments with MDT 2010 Installed on a Different Computer from Windows Deployment Services In this scenario. Install Windows Server 2008 or a later server operating system on the computer hosting the deployment share.Using the Microsoft Deployment Toolkit: Preparing Windows Deployment Services 432 2. 5.0 on the computer that is to be the deployment server. To enable multicast deployments with MDT 2010 Installed on a different computer than Windows Deployment Services 1. Install MDT 2010 on the same computer as in step 3. 4. select the Enable multicast for this deployment share check box.com/technet/SolutionAccelerators . on the General tab. and then click Properties. In the Actions pane. 6. click Update Deployment Share. In the deployment_share Properties dialog box (where deployment_share is the name of an existing deployment share). remotely run the WDSUTIL command on the computer running Windows Deployment Services and Windows Server 2008 or the later server operating system. 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. the Deployment Workbench creates an Auto-Cast Windows Deployment Services multicast transmission from the deployment share. When completed. and then click OK. Install the Windows Deployment Services server role on the computer that is to be the deployment server. click Deployment Shares. In the Deployment Workbench console tree. Install MDT 2010 on the computer that is to be the deployment server. right-click deployment_share (where deployment_share is the name of an existing deployment share for which multicast deployments will be enabled). 5. On the computer hosting the deployment share. In this configuration. 4. 9. 2. 8. in a Command Prompt window. Install Windows AIK 2. Windows Deployment Services and Windows Server 2008 or a later server operating system are all installed on the computer acting as the deployment server. 7. but MDT 2010 is installed on another computer. 3. type the following command.0 on a computer other than the computer hosting the deployment share. Install the Windows Deployment Services server role on the computer hosting the deployment share. In the details pane. Start the Deployment Workbench. Install Windows AIK version 2. 3. Note The Network (UNC) path and Local Path text boxes on the General tab must contain valid paths for multicasting to function properly.

Doing so allows System Center Configuration Manager to directly service PXE boot requests received by Windows Deployment Services as a PXE service point. included with System Center Configuration Manager. “How to Configure the PXE Service Point. For more information. you can use traditional Windows Deployment Services methods for responding to PXE boot requests.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. in Configuration Manager Documentation Library.exe /new-namespace /friendlyname:"BDD Share Deploy$" /server:remote_server /namespace:"Deploy$" /contentprovider:WDS /configstring:"deploy_share_path" /namespacetype:AutoCast When completed. included with System Center Configuration Manager. which in turn allows target computers to boot images that System Center Configuration Manager manages using PXE. For more information about preparing Windows Deployment Services for ZTI deployments.com/technet/SolutionAccelerators . 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. Preparing Windows Deployment Services for ZTI Deployments For ZTI deployments. set a System Center Configuration Manager PXE service point on the computer on which Windows Deployment Services is installed. see the Windows Deployment Services Help file included with Windows Deployment Services. the WDSUTIL tool creates an Auto-Cast Windows Deployment Services multicast transmission from the deployment share. Solution Accelerators microsoft. • Note In addition to the methods described here. see: • “How to Deploy an Operating System Image Using PXE” in Configuration Manager Documentation Library.

aspx. perform the following steps: • • Identify the components in App-V as described in App-V Components.microsoft. The “Virtual Application Management with Microsoft Application Virtualization 4.com/enus/appvirtualization/cc843994. Identify the limitations of App-V as described in App-V Limitations.aspx.microsoft. which is available at http://technet.com/downloads. To determine how App-V can help you in deploying and managing applications.5 Infrastructure Planning and Design” white paper.com/enus/appvirtualization/cc843994.com/enus/appvirtualization/cc843994.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.5 Sequencing Guide” white paper. The “Microsoft Application Virtualization 4. which is available at http://technet.aspx. • • Microsoft Application Virtualization 4. Additional information is available from Microsoft Downloads at http://www. which is available at http://technet. including: • The “App-V 4. .microsoft.5.microsoft.5 App-V allows applications to run in a virtualized application environment on the target computers.5 and System Center Configuration Manager 2007 R2” white paper. This integration allows the automated deployment of virtualized applications as an integral part of the ZTI and LTI deployment processes.

Components on which App-V Management Servers rely include: • Management web service.435 Microsoft Deployment Toolkit 2010 Update 1 App-V Components App-V full infrastructure has several components. At least one instance of the Management web microsoft. However. It relies on components that can be installed on a single server in proof-of-concept installations. Figure 3. The App-V Management Server manages and streams virtual applications. App-V full infrastructure components The following list describes each component. in cases where components must be scaled or you cannot install dependencies such as IIS on the App-V Management Server. The Management web service controls access to the database. Figure 3 provides a high-level overview of these components in an App-V installation. beginning from the center of the diagram: • App-V Management Server. you can distribute components across other servers.com/technet/SolutionAccelerators Solution Accelerators .

App-V has a dedicated packaging utility known as the App-V Sequencer.NET version 2. The process of packaging an application for use with the App-V infrastructure is known as sequencing.com/kb/907265. All App-V management information regarding application publishing and usage tracking is stored in this database. 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.com/technet/SolutionAccelerators Solution Accelerators . “MMC 3. install the Management web service on multiple dedicated servers to provide fault-tolerant access to the management services. connect it by a fast network connection and performance test it to make sure that the database server will respond appropriately.microsoft. The App-V Management Server or App-V Streaming Server streams the sequenced application’s feature blocks to the microsoft. The App-V Management Console is based on Microsoft Management Console (MMC) version 3. IIS and file servers are more scalable than App-V Streaming Servers. 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. App-V Management Console. IIS servers can stream virtual applications to clients using Hypertext Transfer Protocol (HTTP)/HTTP over Secure Sockets Layer (HTTPS).Using the Microsoft Deployment Toolkit: Deploying Applications with App-V 436 service is required.” at http://support. The App-V Streaming Server is a slim version of a full App-V Management Server that only performs application delivery. Configure the database that hosts the App-V database with fault tolerance and run it on a separate server from other management components.When designing a production App-V environment. If the database will be hosted on a remote SQL Server machine. The App-V Sequencer prepares applications for use in virtual environments and separates each application into feature blocks. The console requires a connection to the Management web service to effect changes to the configuration information in the App-V data store. but they stream applications from the local App-V Streaming Server. while typical App-V Streaming Servers support approximately 1. Clients still communicate with an App-V Management Server located at a central location to obtain publishing information and for reporting. • Database. • App-V Sequencer.0 update is available for Windows Server 2003 and for Windows XP. IIS and Windows file servers can also be used as streaming servers. They can potentially support approximately 10.0 and requires installation of the downloads packaged with the Microsoft Help and Support article. • • App-V Streaming Server.0. The App-V Management Server stores configuration and reporting information in a SQL Server database.000 active application streams. This database can be local to the server or can be hosted on a remote database server.000 active streaming sessions. Windows file servers can stream virtual application to clients using the Server Message Block (SMB) protocol.

Applications that start as a service. • App-V Desktop Client. microsoft. Application virtualization does not remediate compatibility problems between Windows and legacy applications. It is possible to remove an application that is no longer used to free space in the cache. consider the following limitations: • Support for 64-bit architectures. Application size limit. SFT files are limited to 4 GB. 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). A typical example is Internet Explorer. Finally. App-V applications can be packaged and deployed through Terminal Services. Large applications that result in SFT files that exceed 4 GB in size after sequencing are not supported. which means that the total size of all files deployed to one client computer cannot exceed 1 TB. • App-V Limitations When using App-V in the scope of a larger desktop-deployment project.com/technet/SolutionAccelerators • • • • • Solution Accelerators . thus. 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. Sequencing applications is by far the most timeconsuming aspect of application virtualization. App-V can. however. The App-V Desktop Client manages applications on users’ client computers. It does. the App-V Desktop Client provides the virtual environment for the sequenced application. Applications that are part of the operating system cannot be sequenced. Application compatibility. Support for operating system–integrated applications.437 Microsoft Deployment Toolkit 2010 Update 1 App-V Desktop Client. The client can only start applications after a user has logged on to the client computer. It is possible to sequence a plug-in. The App-V Client for Terminal Services is optimized to run in a Terminal Services environment. A 64-bit version of the client is not yet available. The client limits the total space used for virtual applications to 1 TB in size. but these components are only supported in Windows 32-bit On Windows 64-bit (WOW64). You can install the App-V Management Console and Streaming Server on 64-bit server operating systems. which means that applications that run as a service when the computer starts cannot be sequenced into virtual applications. virtualize applications that install services as dependencies. An App-V Terminal Services Client license is required to run virtualized applications on a terminal server. such as Microsoft Silverlight™. the sequencer and client cannot are not supported on any 64-bit (x64) platforms. The current version of App-V is optimized for 32-bit (x86) platforms. Application cache limit. App-V Terminal Service Client. however.

MAPI resources—for example.5 Infrastructure Planning and Design” “Microsoft Application Virtualization 4. 3. COM+ or COM dynamic link library (DLL). Applications that use “click-once” technology for application updates should not be virtualized by using App-V. available at http://technet. 2. Messaging Application Programming Interface (MAPI) virtualization. In this step. The App-V Sequencer packages applications for deployment as virtualized applications. remediate compatibility problems between two applications. Determine where to store applications and prepare the network. Applications with licensing enforcement tied to machine computer. they would typically not run on the same client computer. • • • • Planning In this guide. Also. if two applications use a different Java Runtime Engine (JRE) version. consider whether to use System Center Configuration Manager and how to service branch offices during deployment. The high-level steps for planning application virtualization as part of a desktop-deployment project are listed below. the primary planning focus is on App-V client deployment and application sequencing. Plan the application App-V Sequencer environment.microsoft.aspx: • • • “App-V 4. App-V cannot virtualize device drivers.5 and System Center Configuration Manager 2007 R2” To plan application virtualization 1. If an application installs a device driver. Additional guidance is available in the following white papers. determine the requirements for sequencing applications. they now can run on the same client computer at the same time. • Device drivers. Click-once updates. Applications that use COM+ or COM DLL surrogate virtualization (DLLhost. Plan the application virtualization infrastructure. When sequenced. Choose an application deployment method. it may be possible to install the device driver locally and sequence the core application.Using the Microsoft Deployment Toolkit: Deploying Applications with App-V 438 however.exe) cannot be virtualized.com/technet/SolutionAccelerators . Applications that tie the license to the system’s MAC address should not be virtualized with App-V. profiles— are shared by all MAPI applications on a client computer rather than isolated. Solution Accelerators microsoft.5 Sequencing Guide” “Virtual Application Management with Microsoft Application Virtualization 4.com/en-us/appvirtualization/cc843994. Virtualized applications that use MAPI will use the MAPI interfaces in the underlying client operating system. this section briefly discusses infrastructure planning as it relates to the overall deployment project. Also. For example.

Components requiring planning include: • Application storage. However. such as site size. It includes integration with App-V to allow the deployment of virtualized applications.5 and System Center Configuration Manager 2007 R2. choose which applications will be sequenced and whether they are suitable for virtualization or particularly difficult to sequence. If the user tries to launch the virtual application while the client computer is offline. there are important aspects to consider when deciding whether to stream virtual applications and which network protocol (SMB.microsoft. and the package-retention policy regarding how many historical versions of virtual application packages will be maintained in the virtual application content repository.” at http://technet. The choice of applicationdeployment method is based on multiple factors.com/technet/SolutionAccelerators • • • . Note When using System Center Configuration Manager for streaming delivery. When using streaming delivery. Location types. “Virtual Application Management with Microsoft Application Virtualization 4. or RTSP) to us