Microsoft Deployment Toolkit 2010 Update 1

®

Using the Microsoft Deployment Toolkit

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

3

Contents

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

4

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

5

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

6

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

7

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

8

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

9

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

10

Estimating Storage Requirements for Computers Running MDT 2010

8

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

11

Estimating Storage Requirements for MDT 2010 Deployment Shares

8

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

12

Estimating Storage Requirements for System Center Configuration Manager Distribution Points 10

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

13

Estimating Storage Requirements for User State Migration Data

10

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

14

Estimating Storage Requirements for Target Computer Backup 11

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

15

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Contents

16

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 .

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

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

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

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.

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

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

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

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

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 .Using the Microsoft Deployment Toolkit: Contents 69 Upgrade an Existing Deployment Share in Deployment Workbench 67 Solution Accelerators microsoft.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 .

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.

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

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

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

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.

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

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

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 .Using the Microsoft Deployment Toolkit: Contents 107 Enable or Disable Device Drivers in Deployment Workbench 127 Solution Accelerators microsoft.

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

....Using the Microsoft Deployment Toolkit: Contents 109 Configuring Task Sequences in Deployment Workbench....127 Solution Accelerators microsoft...........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 .

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.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.......Using the Microsoft Deployment Toolkit: Contents 140 Preparing the ZTI Deployment Environment....216 Solution Accelerators microsoft...........................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 .

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

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

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

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

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

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

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

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

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

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

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.

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

............Using the Microsoft Deployment Toolkit: Contents 155 Managing ZTI Deployments in Configuration Manager Console.....com/technet/SolutionAccelerators .........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..

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.....com/technet/SolutionAccelerators ...........Using the Microsoft Deployment Toolkit: Contents 185 Preparing for UDI Deployment to the Reference Computer...............

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

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

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

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

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

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

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 .Using the Microsoft Deployment Toolkit: Contents 194 Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates..276 Solution Accelerators microsoft....

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

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

com/technet/SolutionAccelerators .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 .Using the Microsoft Deployment Toolkit: Contents 200 Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File 290 Solution Accelerators microsoft.

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

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

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

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

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

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

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 .

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.

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 .

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

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

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

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

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

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

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

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

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.Using the Microsoft Deployment Toolkit: Contents 222 Basic CustomSettings.com/technet/SolutionAccelerators .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.......................Using the Microsoft Deployment Toolkit: Contents 269 Creating a New MDT DB or Connecting to an Existing MDT DB.com/technet/SolutionAccelerators ....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 .

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

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

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

com/technet/SolutionAccelerators .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 .Using the Microsoft Deployment Toolkit: Contents 276 Manage Configuration Settings Stored in the MDT DB Using SQL Server Management Tools 420 Solution Accelerators microsoft.

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

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.

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

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

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 .

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

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

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

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

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

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

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

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

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

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

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 .

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

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

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

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

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

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

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

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

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

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

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

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 .

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

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

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

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

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 ..............483 Solution Accelerators microsoft.....................................Using the Microsoft Deployment Toolkit: Contents 317 Stabilizing..........

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Requires more initial IT administration configuration time Can require interaction by the user or deployment technician Increases the risk of introducing configuration errors Requires users or deployment technicians to have credentials with elevated permissions Requires that users or deployment technicians know some configuration settings prior to initiating the MDT 2010 deployment process Can require less initial information technology (IT) administration configuration time Can require interaction by the user or deployment technician Increases the risk of introducing configuration errors Requires users or deployment technicians to have credentials with elevated permissions Requires that users or deployment technicians know some configuration settings prior to initiating the MDT 2010 deployment process Solution Accelerators microsoft. DVD.com/technet/SolutionAccelerators . 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.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.

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

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

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

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

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

25

Microsoft Deployment Toolkit 2010 Update 1

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

• • •

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

26

• • • •

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

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

• •

Solution Accelerators

27

Microsoft Deployment Toolkit 2010 Update 1

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

28

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

29

Microsoft Deployment Toolkit 2010 Update 1

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

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

1: 2: 3: 4: 5:

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

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

30

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

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

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

Solution Accelerators

31

Microsoft Deployment Toolkit 2010 Update 1

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

• •

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Planning MDT 2010 Deployments

32

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

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

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

33

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

34

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

35

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

Ready to Install Completing the Microsoft Deployment Toolkit Setup Wizard

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

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

Solution Accelerators

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

36

• •

MDT 2008 Update 1 BDD 2007 Update 2

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

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

Summary Confirmation

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

37

Microsoft Deployment Toolkit 2010 Update 1

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

38

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

39

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

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

Solution Accelerators

Using the Microsoft Deployment Toolkit: Performing LTI Deployments

40

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

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

Deployment Shares

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

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

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

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

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

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

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

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

Configure the Deployment Share Properties Windows PE x86 Components Tab. 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. Solution Accelerators microsoft. 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. For more information about the MDT 2010 deployment scenarios. Table 13.com/technet/SolutionAccelerators . To prepare for the New Computer deployment scenario 1. a new installation of a Windows operating system is deployed to a new computer. Prepare for the New Computer Deployment Scenario to Target Computers Using LTI In the New Computer deployment scenario. any combination of the deployments scenarios might be necessary. Optionally. Configure the Deployment Share Properties Windows PE x64 Settings Tab. 2. Customize the MDT 2010 configuration files to the needs of your organization as described in Configuring MDT 2010 Deployments. 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. Verify the Windows PE options for each deployment share as described in: • • • Configure the Deployment Share Properties Windows PE x86 Settings 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). 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. 4. 3. see Identifying Deployment Scenarios.47 Microsoft Deployment Toolkit 2010 Update 1 Depending on the target computers in your organization.

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

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

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

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

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

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

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

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

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

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

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

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

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

The deployment share is added to the details pane in the Deployment Workbench. the Open Deployment Share Wizard will not upgrade the deployment share. Select the Upgrade the content of the deployment share (if required) check box. • Cleared. Upgrade an Existing Deployment Share in Deployment Workbench MDT 2010 can upgrade an existing BDD 2007 deployment share.com/technet/SolutionAccelerators . 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. Tip You can click Save Output to save the output of the wizard to a file. Start the wizard by Solution Accelerators microsoft. and then click Next. the existing deployment share is upgraded (if required). the Open Deployment Share Wizard upgrades the deployment share. After the wizard finishes. Upgrading an existing deployment share that is listed in the Deployment Workbench as described in Upgrade Deployment Shares Already Listed in Deployment Workbench. You can also click View Script to view the Windows PowerShell scripts used to perform the wizard tasks. Note You can alternatively click Browse to find the local or network shared folder. 3.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. Click Next. Click Finish. If the check box is: • Selected. an MDT 2008 deployment share. 2. and the Upgrade the content of the deployment share (if required) check box is selected. • Upgrade Deployment Shares Not Already Listed in Deployment Workbench Upgrade deployment shares not listed in the Deployment Workbench using the Open Deployment Share Wizard. or a pre-release version of MDT 2010 deployment share to MDT 2010.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

and then click Deployment Workbench. new_image_name is the new image name. Import the operating system using the Import Operating System Wizard in the Deployment Workbench. go to Deployment Workbench/Deployment Shares/deployment_share/Operating Systems Solution Accelerators microsoft. wim_file is the name of the WIM file. To resolve this issue. Click Start. 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. Destination In Destination directory name. the wizard fails with an error similar to the following: Setup failed applying image F:\Deploy\Operating Systems\W2K8R2RTM\W2K8R2RTM. and then click Next.com/technet/SolutionAccelerators . 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. rc = 31. 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. To import an operating system from an existing image in Windows Deployment Services 1.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. In the Deployment Workbench console tree. Summary Confirmation Click Finish. If you attempt to import a custom image that does not have an Edition ID. Click Next. 2. type destination_folder (where destination_folder is the name of the folder in the deployment share that will contain the operating system source files). and then point to All Programs. Tip Click Save Output to save the output of the wizard to a file. The Import Operating System Wizard finishes.wim. Point to Microsoft Deployment Toolkit. rc = 31 ZTI ERROR – Non-zero return code by LTIApply.

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). and then click Next. The Import Operating System Wizard starts. type server_name (where server_name is the name of the Windows Deployment Services server that contains the existing WIM images). Table 37. Information for Completing the Import Operating System Wizard On this wizard page OS Type WDS Server Do this Click Custom image file. No other settings can be modified. The Deployment Workbench leaves the operating system image on the Windows Deployment Services server. click Import Operating System. 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. Table 36. The Import Operating System Wizard finishes. In the Actions pane. and only the Operating system name can be modified. 4. Click Next. Tip Click Save Output to save the output of the wizard to a file. In Server name. The operating system is added to the list of operating systems in the details pane but is not is copied to the deployment share. 3.com/technet/SolutionAccelerators Solution Accelerators . 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. Windows 7 ENTERPRISE in microsoft. Summary Confirmation Click Finish. and then click Next. Note The configuration settings on the General tab are populated when you import the operating system. Complete the Import Operating System Wizard using the information in Table 36. but the image is now available to LTI. Table 37 lists the configuration settings on the General tab of the operating system Properties dialog box and provides a description of each setting. or click View Script to view the Windows PowerShell scripts used to perform the wizard tasks.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

105

Microsoft Deployment Toolkit 2010 Update 1

Setting

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

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

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

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

106

Setting Description Install multiple applications

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

Success codes

Install a single application Application to install

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

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

To create a new task sequence step for installing applications

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

107

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

108

• •

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

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

Summary Confirmation

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

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

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

109

Microsoft Deployment Toolkit 2010 Update 1

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

Comments Display name

Type

Processor architecture

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

110

Setting Language

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

Keyword

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

Public key token

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

Version

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

Product name

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

Product version

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

Package path

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

Hide this package in the Deployment Wizard

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

Enable (approve) this package

Solution Accelerators

111

Microsoft Deployment Toolkit 2010 Update 1

Setting

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

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

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

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

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

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

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

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

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

112

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

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

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

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

113

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

114

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

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

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

115

Microsoft Deployment Toolkit 2010 Update 1

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

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

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

116

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

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

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

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

Click Finish.

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

117

Microsoft Deployment Toolkit 2010 Update 1

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

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

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

Comments
Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

118

Setting Platforms: x86

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

Platforms: x64

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

Enable this driver

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

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

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

Solution Accelerators

microsoft.com/technet/SolutionAccelerators

119

Microsoft Deployment Toolkit 2010 Update 1

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

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

Solution Accelerators

Using the Microsoft Deployment Toolkit: Managing LTI Deployments

120

Setting

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

the step runs. To modify existing task sequence properties on the OS Info tab 1. Solution Accelerators microsoft. and Edit buttons to modify the conditions under which the group of tasks runs. see Configure a Conditional Task Sequence Step. Note Any conditions configured for a group affect all the tasks within a group. 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). If no criteria are specified. Condition list box For more information about conditions in task sequence steps. If the check box is: • Selected. Contains any conditional criteria for running this step. Add criteria for determining when the group of tasks should (or should not) run. • Cleared. Point to Microsoft Deployment Toolkit. the task sequence continues if the group or step encounters an error. and then click Deployment Workbench. Remove. • A task sequence variable. the task sequence will not continue if the group or step encounters an error. 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. In the Deployment Workbench console tree. • The version of the target operating system. Use the Add. The criteria can be based on: • An IF statement. 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. Click Start. 2.com/technet/SolutionAccelerators . • A Windows Management Instrumentation (WMI) Query Language (WQL) query within a WMI namespace.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Configure the settings on the Windows PE x64 Settings tab as described in Configure the Media Properties Windows PE x64 Settings Tab. The folders and content you specified in the selection profile are copied to the Deploy folder when the Update Media Content Wizard runs. • • Configure the Media Properties General Tab The media properties on the General tab are configured when you run the New Media Wizard. Point to Microsoft Deployment Toolkit. go to Deployment Workbench/Deployment Shares/deployment_share/Advanced Solution Accelerators microsoft. 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. and then point to All Programs. In the Deployment Workbench console tree. The New Media Wizard finishes. However. Click Start. Configure properties on the Rules tab as described in Configure the Media Properties Rules Tab. Modify Existing Media in Deployment Workbench Modify existing media in the Media node in the Deployment Workbench using the Properties actions as described in View Item Properties in Deployment Workbench. and some base folders are created. To modify existing media properties on the General tab 1. Configure the settings on the Windows PE x64 Components tab as described in Configure the Media Properties Windows PE x64 Components Tab. 2. Configure the settings on the Windows PE x86 Settings tab as described in Configure the Media Properties Windows PE x86 Settings Tab. The media_path\Content\Deploy folder is created (where media_path is the name of the media path you specified in the wizard).com/technet/SolutionAccelerators . you can update the linked deployment share properties on the General tab of the media Properties dialog box (where media is the name of the media in the Deployment Workbench). and then click Deployment Workbench. Configure the settings on the Windows PE x86 Components tab as described in Configure the Media Properties Windows PE x86 Components Tab. 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. Click Finish.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

a new installation of Windows is deployed to a new computer. 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 target computer. the user state data is restored to the new computer. 2. 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. 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. customize the MDT 2010 configuration files or the MDT DB to the needs of your organization as described in: • Configuring MDT 2010 Deployments. When performing this step in a production environment. • Performing Deployments Using the MDT DB. 6. Then. one computer replaces another computer. Note Most production networks have multiple distribution points. Note Most production networks have multiple distribution points. Finally. Use the: Solution Accelerators microsoft. Optionally. When performing this step in a production environment. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. 3. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console.215 Microsoft Deployment Toolkit 2010 Update 1 Table 120. 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. Create a computer association record that associates the existing target computer and the new target computer.com/technet/SolutionAccelerators . select the appropriate distribution points for the network. 5. Prepare for the Replace Computer Deployment Scenario to Target Computers Using ZTI In the Replace Computer deployment scenario. select the appropriate distribution points for the network. There are no existing file systems to preserve. The existing user state migration data is saved from the existing target computer. and specify the fully qualified UNC path to the WIM image captured from the reference computer. 4.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

” in Configuration Manager Documentation Library. which is installed with System Center Configuration Manager. Deploying specific device drivers to target computers for ZTI deployments as described in Deploy Specific Device Drivers to Target Computers in ZTI. For more information about managing operating systems in the Configuration Manager Console. The Create Microsoft Deployment Task Sequence Wizard closes when the task sequence is created. For information about this wizard. Solution Accelerators microsoft.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. see the section. which is installed with System Center Configuration Manager. use the Import New Driver Wizard.com/technet/SolutionAccelerators . 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. For information about creating a new driver package. “Import New Driver Wizard. 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. the actions that you can run. “Operating System Deployment: Operating System Images Node. see the section. 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. 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. • Import Drivers into System Center Configuration Manager To import drivers into System Center Configuration Manager. Create a New Driver Package A driver package contains the content associated with one or more device drivers. Creating a new driver package that contains the device drivers as described in Create a New Driver Package.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

including operating system deployment packages. Note Most production networks have multiple distribution points. Optionally. Note Most production networks have multiple distribution points. 8. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. When performing this step in a production environment. 7.Using the Microsoft Deployment Toolkit: Performing ZTI Deployments 260 2. 9. select the appropriate distribution points for the network. Ensure that all packages. 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. including operating system deployment 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. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. When performing this step in a production environment. select the appropriate distribution points for the network. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. Solution Accelerators microsoft. 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). 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. that the new UDI task sequence uses are properly distributed to the assigned distribution points as described in Managing Distribution Points in Configuration Manager Console. When performing this step in a production environment. • 4. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. which is the same process for UDI and ZTI deployments. 3. 5. Ensure that all packages. Note Most production networks have multiple distribution points. that the new UDI task sequence uses are properly distributed to the assigned distribution points as described in Managing Distribution Points in Configuration Manager Console. Configure System Center Configuration Manager to contain the appropriate software for deployment to the reference computer.com/technet/SolutionAccelerators . which is the same process for UDI and ZTI deployments. 6.

which is the same process for UDI and ZTI deployments. and specify the fully qualified path to the WIM image captured from the reference computer. Configure System Center Configuration Manager to contain the appropriate software for deployment to the target computer. 2. Optionally. To prepare for the Refresh Computer deployment scenario to target computers 1. 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 • . • Performing Deployments Using the MDT DB.261 Microsoft Deployment Toolkit 2010 Update 1 Prepare for the Refresh Computer Deployment Scenario to Target Computers Using UDI In the Refresh Computer deployment scenario. including: • Configuring applications and operating system packages as described in Managing Software Packages in Configuration Manager Console. 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. Customize the task sequence to the needs of your organization as described in Configuring ZTI Task Sequence Steps in Configuration Manager Console. which is the same process for UDI and ZTI deployments. Table 131. Configuring device drivers as described in Managing Device Drivers in Configuration Manager Console. There is user migration information to save and restore but no existing file systems to preserve. Tip Create the task sequence for deploying to the reference computer based on the UserDriven task sequence template included in MDT 2010. Solution Accelerators microsoft. which is the same process for UDI and ZTI deployments. Create a new task sequence that will deploy the target operating system to the reference computer using the Create Microsoft Deployment Task Sequence Wizard in the Configuration Manager console as described in Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates. 4. a computer is refreshed. 3. including computers that must be re-imaged for image standardization or to address a problem.

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

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

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

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. 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. Managing software packages for UDI in the Configuration Manager Console as described in Managing Software Packages in Configuration Manager Console. 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. Managing operating systems for UDI deployments in the Configuration Manager Console as described in Managing Operating Systems in Configuration Manager Console. which is the same process for UDI and ZTI deployments. You can use the UDI Wizard Designer to configure the behavior of the Operating System Deployment (OSD) Setup Wizard. Managing advertisements for UDI as described in Managing Advertisements in Configuration Manager Console. • • • • • • • • • . Managing computer collections for UDI as described in Managing Computer Collections in Configuration Manager Console. Manage UDI deployments by: • Creating a new task sequence for UDI deployments using the Create Microsoft Deployment Task Sequence Wizard as described in Creating a UDI Task Sequence Using MDT 2010 Task Sequence Templates. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments. Manually adding computers to the site database for UDI as described in Manually Adding Computers to the Site Database in Configuration Manager Console. You use the Deployment Workbench in UDI deployments only to configure the MDT DB.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. Creating boot images for use with UDI using the Create Image Using Microsoft Deployment Wizard as described in Creating ZTI Boot Images. which is the same process for UDI and ZTI deployments. which is the same process for UDI and ZTI deployments.

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

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

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

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

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

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

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

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

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

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

In Version. type version_number (where version_number is the version number to be assigned to the package). In Path to USMT executables and related files.com/technet/SolutionAccelerators . 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 path (where path is the fully qualified path for the location of the folder in which the USMT source files reside). 2. 4. In Name. 3. Click Next. If you select this option. In Package source to be created. In Manufacturer. Tip You can also click Browse to locate the path. type language (where language is the language of the package). perform the following steps: a. 1. In Comments. 3. type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package). 6. b. type package_name (where package_name is the name to be given to the package). 5. Tip You can also click Browse to locate the UNC path. 2. Solution Accelerators microsoft. Click Create a new settings 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). The other option is Specify an existing settings package. and then click OK. type comment_text (where comment_text is descriptive information about the package). In Language. Summary Click Next.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). 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. 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. Note Create a separate version of the UDIWizard_Config. 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. the step also references the UDIWizard_Config.com/technet/SolutionAccelerators • • • • • • • Solution Accelerators . Configure the UDI Wizard task sequence step to use a file other than the UDIWizard_Config.xml file using the UDI Wizard Designer. 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.xml file for each set of configuration settings for the Operating System Deployment (OSD) Setup Wizard.xml file.xml file as described in Override the Configuration File Used by 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. 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. microsoft. 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. The Create Microsoft Deployment Task Sequence Wizard closes when the UDI task sequence is created. When a task sequence step runs the Operating System Deployment (OSD) Setup Wizard. 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. 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. You can customize 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.

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. 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.xml file. 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. To create a new Operating System Deployment (OSD) Setup Wizard configuration file using the UDI Wizard Designer Solution Accelerators microsoft. Configure the behavior of the Application Discovery preflight check as described in Configure Application Discovery Preflight Check Behavior.com/technet/SolutionAccelerators . Tip Create a new MDT 2010 files package and corresponding package source for each unique configuration of the UDIWizard_Config. • • • • • • • 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. • 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 for the Language page in the UDI Wizard Designer as described in Configure the Behavior for the Language Page Using the UDI Wizard Designer.xml file in the Scripts folder of the MDT 2010 files package specified in the task sequence. 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.279 Microsoft Deployment Toolkit 2010 Update 1 • Configure the behavior for the User Configuration page in the UDI Wizard Designer as described in Configure the Behavior for the User Configuration Page in Using UDI Wizard Designer. Preview the behavior of the wizard pages in the Operating System Deployment (OSD) Setup Wizard using the Preview OSDSetupWizard menu item in the UDI Wizard Designer as described in Preview the Operating System Deployment (OSD) Setup Wizard Behavior Using the UDI Wizard Designer.

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

A list of available files appears in the list box. In the UDI Wizard Designer console. and then click Save. Also. The UDI Wizard Designer starts. and then click OK. in File name. In the Open Remote Configuration dialog box. create a new task sequence or modify an existing task sequence steps to use the appropriate MDT 2010 files package (if necessary).com/technet/SolutionAccelerators . 4. click file_name (where file_name is the file name for the configuration file). click File. and then click Connect. 2. type udi_web_service (where udi_web_service is the Uniform Resource Identifier (URI) to the UDI web service where you want to open the configuration file). Click Start. In the Save As dialog box. go to folder_path (where folder_path is the fully qualified path to the Scripts folder in the MDT 2010 files package source). Also. Point to Microsoft Deployment Toolkit. the configuration file can be updated without having to update Configuration Manager packages. and then click UDI Wizard Designer. 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. 3. To open an Operating System Deployment (OSD) Setup Wizard configuration file from a UDI web service using the UDI Wizard Designer 1. After modifying the existing Operating System Deployment (OSD) Setup Wizard configuration file.281 Microsoft Deployment Toolkit 2010 Update 1 6. and then point to All Programs. type file_name (where file_name is the file name for the configuration file). in the list box. and then click Open Remote Configuration. in Specify root service URI. Publishing to the UDI web service allows centralized management and access to the configuration file. Publishing to the UDI web service allows centralized management and access to the configuration file. 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. Solution Accelerators microsoft. In the Open Remote Configuration dialog box. the configuration file can be updated without having to update Configuration Manager packages. 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 Configuration Manager Console. You can override the default configuration file that the wizard uses by modifying the UDI Wizard task sequence step to use the /definition parameter. type udi_web_service (where udi_web_service is the URI to the UDI web service where you want to save the configuration file). and then click Publish Configuration. in Specify root service URI. 3. go to Computer Management/Task Sequence. In the Save Remote Configuration dialog box. 3.Using the Microsoft Deployment Toolkit: Managing UDI Deployments 282 If you publish the configuration file to the UDI web service. 4. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. Open a configuration file as described in one of the following sections: • • • Create a New Operating System Deployment (OSD) Setup Wizard Configuration File. Click Start. Right-click task_sequence (where task_sequence is the name of the task sequence you want to edit). and then point to All Programs.xml file in the Scripts folder in the MDT 2010 Files package for configuration. and then click Edit. type tag (where tag is a method of identifying the configuration file. and then click OK. Beneath the State Capture phase. 2. 2. in Tag. In the UDI Wizard Designer console. 5.com/technet/SolutionAccelerators . 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. click File. The UDI Wizard Designer starts. Solution Accelerators microsoft. 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 the UDI Wizard task sequence step. Make the appropriate changes to the configuration file in the UDI Wizard Designer console. and then click UDI Wizard Designer. 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. such as OSDSetup-Win7-NYC). Point to Microsoft Deployment Toolkit. To publish an Operating System Deployment (OSD) Setup Wizard configuration file to a UDI web service using the UDI Wizard Designer 1.

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

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

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. Configure the Preflight page behavior using the UDI Wizard Designer. configure the settings listed in Table 138 based on the requirements of your organization. Configuration Settings for the Preflight Page in the Tasks Pane Solution Accelerators microsoft.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. In the UDI Wizard Designer console. In the Workspace pane. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. In the Tasks pane. You can add one or more items to the list.com/technet/SolutionAccelerators . To configure the Preflight page behavior using the UDI Wizard Designer 1. 3. and then click UDI Wizard Designer. in the navigation pane. 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. Point to Microsoft Deployment Toolkit. The preflight checks are performed in the order they appear. 4. and then point to All Programs. 2. 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. Table 138. 5. Table 137. from the top of the list to the bottom of the list. 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. click Wizard. Theses checks help ensure that the system resources and configuration of the target computer are adequate to perform the deployment. Click Start. and then click Preflight Page.

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

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

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

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

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

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

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

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

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

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

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

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

Point to Microsoft Deployment Toolkit. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. and then click UDI Wizard Designer. In the UDI Wizard Designer console. 2. Configuration Settings for the Volume Page in the Workspace Pane Setting Description Format: Clean all This check box determines if the Operating data on the target System Deployment (OSD) Setup Wizard will volume during install default to formatting the target volume on the target computer. Configure the Volume Page Behavior Using the UDI Wizard Designer The Volume page in the Operating System Deployment (OSD) Setup Wizard contains the configuration settings for the disk volume configuration of the target computer and the image to be deployed to the target computer. To configure the Volume page behavior using the UDI Wizard Designer 1. configure the settings listed in Table 147 based on the requirements of your organization. If this check box is: • Selected. In the Workspace pane. 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. and then point to All Programs. and then click Volume Page. the Operating System Deployment (OSD) Setup Wizard defaults to formatting the target volume during installation on the target computer. Click Start. see Available Language Packs. Solution Accelerators microsoft.com/technet/SolutionAccelerators . Table 147. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. 3. click Wizard.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. Configure the Volume page behavior using the UDI Wizard Designer.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution Accelerators microsoft.315 Microsoft Deployment Toolkit 2010 Update 1 2.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. In the UDI Wizard Designer console.com/technet/SolutionAccelerators . 4. Navigate through the wizard pages to verify that the configuration settings made in the UDI Wizard Designer are correct. click Preview OSDSetupWizard. Open an Operating System Deployment (OSD) Setup Wizard Configuration File from a UDI Web Service. Open configuration_file (where configuration_file is the fully qualified path and file name the UDIWizard_Config. Open an Existing Operating System Deployment (OSD) Setup Wizard Configuration File. 3. The Operating System Deployment (OSD) Setup Wizard opens in preview mode.

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

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

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

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

The Page Behavior for the User Configuration page is configured to Silent. 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. The value entered in this box must match the value in the Password box.com/technet/SolutionAccelerators Confirm password User name Back Solution Accelerators . 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. Each account is separated by a semicolon. but there are problems with required information on the wizard page. 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. Goes to the previous wizard page. The value entered in this box must match the value in the Confirm password box. 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. 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.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. Contains the password for the Administrators local built-in account on the target computer. Table 166. Contains the user names of one or more accounts that will be members of the Administrators built-in local group. microsoft.

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

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

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 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. 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 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.com/technet/SolutionAccelerators . 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 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.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 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. Volume Windows Directory Format: Clean all This check box determines whether the target data on the target volume on the target computer is formatted prior volume during install to deploying the target operating system. This field can be enabled or disabled using the Enabled or Disabled task in the Disk Volume field on the Volume page in the UDI Wizard Designer as described in Configure the Behavior for the Volume Page Using the UDI Wizard Designer. The list of local disk volumes that are available in the list box is configured in the Display volumes with a minimum size of (gigabytes) text box on the Volume page in the UDI Wizard Designer.

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

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

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. 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. Saving and restoring the user state migration data using USMT as described in Saving and Restoring User State Information.326 Microsoft Deployment Toolkit 2010 Update 1 Configuring MDT 2010 Deployments Configure MDT 2010 deployments by: • • • • • • • • • • • Customizing the CustomSettings. Preparing disks on the target computers as described in Preparing Disks on Target Computers. Managing device drivers in LTI and ZTI deployments as described in Managing Device Drivers. Copying content to the target computers for LTI and ZTI deployments as described in Copying Content to the Target Computer. .ini and Bootstrap. Creating custom scripts that integrate with the LTI and ZTI deployment process as described in Creating Custom Scripts for MDT 2010. Applying the MDT 2010 properties to groups of computers as described in Applying MDT 2010 Properties to Groups of Computers. Deploying software updates to the target computers as described in Deploying Software Updates to Target Computers. Customizing the MDT 2010 properties as described in Configuring the Appropriate MDT 2010 Properties. • • • Customizing MDT 2010 Configuration Files MDT 2010 is flexible and highly customizable. Configuring the MDT 2010 processing rules as described in Configuring MDT 2010 Processing Rules.ini files as described in Customizing MDT 2010 Configuration Files. Joining target computers to AD DS domains as described in Joining Target Computers to AD DS Domains. 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. Applying the MDT 2010 properties to individual computers as described in Applying MDT 2010 Properties to Individual Computers. It includes several tools for getting started.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.com/technet/SolutionAccelerators . The servers that UDShare and SLSShare (NYC-AM-FIL-01 and DAL-AMFIL-01) reference are within each respective location. see Priority Reserved Property. For more information about determining the priority of processing rules. In NYC. determine the method for identifying individual computers and the configuration settings to assign to each computer. SLShare.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. Solution Accelerators microsoft. and Administrator1 are specified for each location. 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. • 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. location-specific packages are designated by Packages1 and Packages2. UDShare.

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

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

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

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

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

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

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

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

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

Settings in Unattended.) 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.xml File You can automate the domain-join process for LTI or ZTI deployments by modifying the settings listed in Table 183 in the Unattended. specify as Domain\UserName or UserName@Domain.ini file used in the MDT 2010 deployment process. Table 182. and underscores [_].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.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. Table 183. Properties in CustomSettings.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.com/technet/SolutionAccelerators Solution Accelerators . hyphens [-]. The JoinDomain property cannot be blank or contain spaces.351 Microsoft Deployment Toolkit 2010 Update 1 Join Domains by Modifying the CustomSettings.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.xml file used in the MDT 2010 deployment process. The JoinDomain property can contain alphanumeric characters.

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

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

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

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

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

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

and then place the device drivers in the corresponding folders: • • Windows 7 Windows Server 2003 microsoft. 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 operating systems. 3. Select this method to deploy only the device drivers to the target computer based on the respective target operating system. Processor architecture of the target computers. 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.com/technet/SolutionAccelerators Solution Accelerators . The folder structure groups or categorizes device drivers so that you can select specific groupings or categories of drivers using selection profiles. you may have or expect to have one of the following problems: • Device drivers are being selected for the wrong operating system. 2.Using the Microsoft Deployment Toolkit: Configuring MDT 2010 Deployments 358 1. In this case. • • The complexity of the folder structure that you create is based on the level of precision you want for deploying the device drivers. 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. Create selection profiles used to select the device drivers for deployment based on the folder structure you created in the previous step as described in Create Selection Profiles to Select the Device Drivers for LTI Deployments. Select this method to deploy only the device drivers to the target computers based on the respective processor architecture (32-bit or 64-bit). you can select the appropriate folder structure based on task sequence variables later in the process. Tip If the name of the folder matches the value that the BIOS returned for make and model. 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. Select any combination of the following methods for creating folder structures: • Target operating system. Select this method to deploy device drivers to the target computer based on the respective make and model of the target computer. 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 more complex the folder structure.

Solution Accelerators microsoft. So. you could organize your device drivers by creating the following folder structure in the Out-of-Box Drivers node in the Deployment Workbench based on the make and model of the target computer. its IP pros create a folder structure in the Out-of-Box Drivers node in the Deployment Workbench that organizes the device drivers by make and model. 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. operating system. and processor architecture: make\model\operating_system\architecture Figure 2 illustrates the folder structure Woodgrove Bank created. In this case. 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. In this case.com/technet/SolutionAccelerators .359 Microsoft Deployment Toolkit 2010 Update 1 • • • • Windows Server 2008 Windows Vista Windows XP Device drivers are being selected for the wrong processor architecture. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

0.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 History: ' // ' // ***** End Header ***** ' //********************************************************* ****************** '//--------------------------------------------------------------------------'// '// Global constant and variable declarations '// '//--------------------------------------------------------------------------Option Explicit Dim iRetVal '//--------------------------------------------------------------------------'// End declarations '//--------------------------------------------------------------------------'//--------------------------------------------------------------------------'// Main routine '//--------------------------------------------------------------------------On Error Resume Next Solution Accelerators microsoft.0 ' // Customer Script Version: 1.0.wsf [/debug:true] ' // ' // Customer Build Version: 1.com/technet/SolutionAccelerators .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

and then click Next. Query the roles associated with the computer on the Roles 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. Query the settings configured on the Details tab of the location item’s Properties dialog box. Complete the Location Options wizard page using the information in Table 194. 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 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. and then click Next. Information to Complete the Computer Options Wizard Page Select this check box Query for computerspecific settings Query for roles assigned to this computer To do this Query the settings configured on the Details tab of the computer item’s Properties dialog box. Complete the Computer Options wizard page using the information in Table 193. 5. Table 194. Table 193. Query the roles associated with the location on the Roles tab of the location item’s Properties dialog box. Information to Complete the Location Options Wizard Page Select this check box Query for location names based on default gateways To do this Query for location names based on the IP addresses of the default gateways configured on the Identity tab of the location item’s Properties dialog box.com/technet/SolutionAccelerators .Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 408 4. 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.

Complete the Role Options wizard page using the information in Table 196. and then click Next.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. 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. 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. 6. 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. and then click Finish. Query for administrators to be assigned to machines with this make and model Query the accounts that are to be made members of the local Administrators group on the target computer with the make and model as configured on the Administrators tab of the make and model item’s Properties dialog box. Table 195. 7. Table 196. Complete the Make/Model Options wizard page using the information in Table 195.com/technet/SolutionAccelerators . Query the roles associated with the make and model on the Roles tab of the make and model item’s Properties dialog box. Solution Accelerators microsoft. 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.

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

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

Model [MMPackages] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelPackages Parameters=Make.com/technet/SolutionAccelerators .413 Microsoft Deployment Toolkit 2010 Update 1 SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationAdministrators Parameters=DefaultGateway [LRoles] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=LocationRoles Parameters=DefaultGateway [MMSettings] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW SQLShare=Client Table=MakeModelSettings Parameters=Make. Model Order=Sequence [MMApps] SQLServer=R33-dep-01 Instance=R33instance Database=AdminDB Netlib=DBNMPNTW Solution Accelerators microsoft.

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

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

if you need to create custom queries for information. The Configure DB Wizard creates entries in the CustomSettings. • SQL Server Express. you cannot specify the StoredProcedure property. you can leave Instance blank. you can modify CustomSettings. and minimizes the risk of configuration errors. see the corresponding section for each property in the section. Specifies the name of the MDT DB in the SQL Server instance specified in the Instance property. Table 197. However. Specifies the stored procedure to be used in the query. For more information on the properties in Table 197. Specifies the table or view to be used in the query.ini File The Configure DB Wizard in the Deployment Workbench provides the method that requires the least effort.ini to return the proper query results. too: You must specify one or the other. Toolkit Reference. you cannot specify the Table property.ini file is modified. 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. too: You must specify one or the other. If you specify the StoredProcedure property. Specifies a network shared folder on the computer specified in the SQLServer property. If you are using: • SQL Server installed as the default instances.Using the Microsoft Deployment Toolkit: Performing Deployments Using the MDT DB 416 Configure Access to the MDT DB by Directly Modifying the CustomSettings. 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. If you specify the Table property.ini file that are used to build an SQL query.com/technet/SolutionAccelerators Database Netlib SQLShare Table StoredProcedure Solution Accelerators . 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). “Properties. requires minimal knowledge about how the CustomSettings. microsoft. type SQLExpress for the instance name.” in the MDT 2010 document.

ParameterCondition Specifies the Boolean operation to be performed when you specify more than one selection criterion in the Parameters property. The CustomSettings. Most of these properties in Table 197 were configured when you created the MDT DB. SerialNumber. MacAddress ParameterCondition=OR The Priority line in the CustomSettings. this property is the ORDER BY clause in an SQL SELECT statement.com/technet/SolutionAccelerators . The properties in the [CSettings] section performs the Solution Accelerators microsoft.ini file contains the Computers value. If you want to use a Boolean OR operation. Listing 13. which directs MDT 2010 to process the [CSettings] section later in the CustomSettings. 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 WHERE clause in an SQL SELECT statement.ini File After the Configure DB Wizard Has Finished [Settings] Priority=CSettings. You can select either Boolean AND (the default) or OR operations. Note The SQL query that these properties create returns all columns from the table or view specified in the Table property.ini file.417 Microsoft Deployment Toolkit 2010 Update 1 Property Parameters Description Specifies the selection criteria for returning rows from the query. Order Specifies the sort order of the rows returned from the query. you must specify ParameterCondition=OR. Conceptually. AssetTag. Listing 13 provides an example of CustomSettings. Conceptually.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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

microsoft. In this step. The storage requirements for App-V vary based on deployment method. existing infrastructures. In this step. because a distribution Solution Accelerators microsoft. A variety of methods is available for deploying applications. number of applications. This task can occur first or concurrently with the other tasks in this checklist. Plan how to deploy the App-V Desktop Client.com/en-us/appvirtualization/cc843994. there are important aspects to consider when deciding whether to stream virtual applications and which network protocol (SMB. For example. a virtual application is not streamed until the user launc