Graphical Quickstart Guide to the Microsoft Deployment Toolkit 2010_73 | Booting | Microsoft Windows

Graphical Quickstart Guide to the Microsoft Deployment Toolkit 2010

Paul Jorgensen
1

Copyright 2010 Paul Jorgensen Part 1 Version 1.2 September 2010

Cover Photo: Baie du Havre-aux-Basque - Isle de la Madeleine, Quebec, Canada see map below

2

Graphical Quickstart Guide to the Microsoft Deployment Toolkit 2010
Table of Contents:
Graphical Quickstart Guide to the Microsoft Deployment Toolkit 2010 ............................................................. 3 Table of Contents: ...................................................................................................................................... 3 Introduction: .............................................................................................................................................. 6 Formatting of this Guide ............................................................................................................................ 7 Chapter 1: The Microsoft Deployment Toolkit................................................................................................... 8 Setup and use MDT ................................................................................................................................... 8 Import an Operating system to deploy ...................................................................................................... 13 Import a .wim or customized image ......................................................................................................... 16 Loading and using custom drivers ............................................................................................................ 22 Create a Task Sequence to deploy the reference image ............................................................................. 28 Modifying the Task Sequence Actions ..................................................................................................... 33 How to Change BootStrap.ini Settings in the MDT .................................................................................. 34 Update the Deployment Share .................................................................................................................. 37 Replicate the local Deployment Share to a network share ......................................................................... 37 Open and modify a network Deployment Share ....................................................................................... 41 Adding Application installs to the deployment ......................................................................................... 42 Running the USB boot Key with the completed MDT setup ..................................................................... 48 Method #1............................................................................................................................................ 48 Method #2............................................................................................................................................ 48 Method #3............................................................................................................................................ 48 Demonstration of a USB Key boot for a Network Share Deployment ...................................................... 50 Capture a Deployment Image with MDT .................................................................................................. 57 Method #1............................................................................................................................................ 57 Method #2............................................................................................................................................ 57 Method #3............................................................................................................................................ 57 Method #4............................................................................................................................................ 57 Introduction to WinPE tools ................................................................................................................. 58 Capturing a Windows 7 x86 reference install with imagex ................................................................... 59 How to deploy a Windows7 x86 image with imagex ............................................................................ 60 Notes on the bootable deployment Media ................................................................................................. 61 Use the Media Configuration to create Stand alone install deployments ................................................... 62 Creating a new Media Deployment Setup............................................................................................. 62 Chapter 2: Utilizing USB keys and Bootable CD's .......................................................................................... 70 Creating a Bootable USB Key .................................................................................................................. 70 Method #1 Bootable USB Key ........................................................................................................... 70 Method #2 Bootable USB Key ........................................................................................................... 70 Method #3 Bootable USB Key ........................................................................................................... 70 Method #4 Bootable USB Key ........................................................................................................... 70 Chapter 3: Deployment Customizations .......................................................................................................... 71 Dynamically mapping to Deployment Sharepoints ................................................................................... 71 Mapdrive description and basic instructions ............................................................................................. 72 Mapdrive and Mapdrive x64 ................................................................................................................ 72 Setting up Mapdrive to be run from the context menu in Windows 7........................................................ 81 Using Mapdrive or other utilities in MDT and WinPE deployments ......................................................... 82 3

........................................... 89 Microsoft: Fully Automated LTI Deployment for a New Computer Scenario ....................................... 86 Microsoft: How to skip Deployment Wizard Pages in in LTI – WinPE 3... 84 Microsoft: Understanding LocationServer........................... 83 Chapter 4: Direct References for Specific Tasks ............................................................................................................................................................................................................................ 95 4 ...............xml ........................................................................xml ..................................................................................................0..................... 84 Microsoft: LocationServer................................................................ 91 Chapter 5: Glossary ....... 94 Books and Documents ..................................................................................................................................................................................................................................................................................................................... 94 Index ............Customizing the LiteTouch or WinPE boot media ................................................................ 94 Links....................................................................................................................... 93 Chapter 6: List of resources .................................................................................. 85 Microsoft: Capturing a Disk Image for LTI .................................. 87 Microsoft: Skipping the Administrator Password Wizard Page .....................................................................................................

linkedin. corrections and pointers on this guide.com 5 . Johan Ardwidmark Dinesh Vinay Yannick Plavonil www.I would like to give special thanks to the reviewers for their detailed work.com/pub/dinesh-vinay/25/42b/613/ www.com http://in.deployvista.revuedugeek.

Volume activation.Migrating or saving user data .Details about deployment scenarios ( ie refresh ) or image types (ie thin ) . replication. ACT. It will not include any of the following ( refer to Resources Chapter for information on these items ) . DHCP. etc .Application compatibility. This guide is not intended to give you a complicated enterprise setup. you should use the platform you are targeting to follow the instructions. WSIM. This reference uses both x64 and x86 examples. and provide as much as possible a quick reference.Using the MDT database and associated functions .Windows System Center .Non-deployment issues. I have deliberately kept the focus of this document narrow for a number of reasons.WinPE. imagex. and second to keep it within the scope of a quickstart guide.Introduction: The Microsoft Deployment Toolkit is the latest generation of deployment tools for Microsoft operating systems. This is a quick reference guide and is targeted at a basic LiteTouch deployment only. you can pretty well generate a Microsoft deployment using the graphical tools available with the MDT 2010 and the WAIK – Windows Automated Installation Kit. the main one being limited time.Troubleshooting Litetouch deployments . To setup multiple servers. I would hope the information would be helpful to you in your deployment.Using MDT with Active Directory or Group Policy 6 . but a basic initial setup with which you can get started with.Writing or usage of scripts . My goal with this quickstart guide is to simplify and condense some of the information available for Windows 7 deployment into a concise easy to read guide. DISM. It has been updated significantly from previous tools and has a pretty friendly user interface. Windows Update. This means that instead of using command line tools and hand written setup files. etc . MAK keys. refer to the resource chapter. Windows Server. Key Management Service . MAP. databases. etc . etc. extensive details about the Windows 7 AIK.Windows Deployment Services .

Formatting of this Guide All commands that need to be typed in or added into a batch file or command file will be formatted in blue and in a smaller font size as follows copype.cmd x86 c:\win7_x86 Specific Note content important to the current content will be formatted in green as follows C:\Program Files\Windows AIK\Tools\PETools\ Notes will be preceded by the word “ Note” formatted in orange as follows Note Text formatted in brown is reference material 7 .

You can replicate this to a network share as documented in this guide.Chapter 1: The Microsoft Deployment Toolkit Setup and use MDT . 8 .Download and install MDT 2010 .Right click on “Deployment Shares” and click “Create New Deployment share” Type in the path to your deployment share.0 ) .Open the MDT Deployment Workbench from the Start Menu .Download and install Windows 7 Advanced Installation Kit on a Windows 7 system ( WinPE 3. I recommend using a path on your workstations local c: drive for the initial setup of your deployment.

Type in a descriptive name for the local deployment share.Accept the default share or type in a custom share name. 9 .

I recommend selecting the option to “Allow Image Capture” for now. 10 . you can always change it later. Select whether to allow the user to set the local Administrator password.

See the resources chapter for references to more information on licensing. Click through the next two screens to complete the deployment share setup. The summary is displayed.Click Next on the “Allow Product Key” option to accept the default setting. 11 .

You will then see the deployment share and tree structure below the “Deployment Shares” item 12 .

you should import the full set of source files from the desired Windows 7 DVD. See the section “Import a . 13 . You should do this for all platforms you will deploy – such as x64 and x86.wim or customized image for more information.Import an Operating system to deploy Right-click on the “Operating Systems” tree item and click on “Import Operating Systems” as shown below Select “Full set of source files”. Then when you import a custom image file you should also import the source files with it or you will get deployment errors. The higher versions such as Windows 7 Ultimate import all the lower versions as well. First you install the full set of source files and deploy the reference image. Important Note: In order for your deployment media to successfully install an image.

Select the source DVD drive that contains the Windows 7 installation DVD ( I usually mount an ISO to a virtual drive with ISO mounting applications. Type in the name of the destination directory for the source files 14 . UltraISO and Daemon Tools. Some examples of applications that do this would be CloneDrive.

and then click Finish on the Confirmation screen The appropriate versions of Windows 7 will appear in your Operating Systems node of the MDT. 15 .Click next on the Summary screen if the details are correct.

so you should be using folders in each of the MDT’s object folders so you can use selection profiles to create your deployment solution and specifically also to be able to create deployment media that just contains the specific deployment you are targeting. You can also create your subfolders first and then right-click on the subfolder to import your OS into the subfolder. Right-click on the Operating Systems folder and click on “Import Operating System” 16 . you will need to import the full set of source files for Windows 7 depending on how you are doing your deployment. Your deployment share will end up becoming quite large.wim or customized image Note: As noted in the previous section.Import a .wim files already you can use the function “Import Operating System” and “Custom Image file” to make it available to your deployments. If you have customized .

wim capture file to import 17 .wim file or custom .Select “ Custom Image file” to import a captured WIM file in the “Open” window browse to the .

Windows Server 2008.wim file deployment will fail with the message “unable to find SETUP files”. your custom .wim file is shown Note: If you are importing a .wim file only. or later setup files from the specified path”. you will still need to select “Copy Windows Vista. This will copy the setup files into the custom . 18 .wim files directory. but will not copy the install. If you don’t do this.The full path to the .wim file.

if correct click next. This should be something directly related and descriptive of the content for later referral The Summary is presented.Type in the name of the destination folder in the MDT. 19 .

The progress window will display. The Confirmation windows appears with a summary of the import. It may take some time to import a . 20 . It’s a good idea to make sure you are on a high-speed connection before you start the process if you are importing over the network.wim file since they are typically large.

The Custom image is shown in the Win7_x86 folder under Operating Systems. 21 . the OS’s are shown in the main window. Note: Until you create configuration folders for your selection profiles. You can also create the folders first and import directly into them by right-clicking on the appropriate folder and selecting “Import Operating System” as shown in the previous example.

Loading and using custom drivers MDT makes it fairly easy to setup driver installs for WinPE and for the target Windows OS.ini to set the correct driver selection profile based on the WMI Model name of the target system. This involves customizing your CustomSettings. Once you have imported the driver to the correct folder as shown in this section. It is important to create a folder structure that will allow you to setup driver selection profiles and/or driver filters. you can customize your task sequence using Selection Profiles to select a particular set of drivers. An example of this would be to setup a folder structure containing the target OS and the target system model number – ie \Windows7_x86\HP6930 in the Out-of-Box folder. Yannick Plavonil’s site ( French language ) contains detailed information on this. You can also setup driver filtering as documented in the resource document “Deploying Windows 7 with MDT 2010 – Basic Scenarios”. and there is information from various other sources for this – refer to the resources chapter. Right-click on the “Out-of-Box Drivers” and click on “New Folder” 22 . You can set it up how you like but keep in mind that if your deployment gets complicated you will need the folder to be arranged in a useable logical order.

Enter a descriptive name for the subfolder such as “Network” and continue through to completion Create a subfolder in the “Network” folder for your driver import 23 .

Right-click on the driver subfolder and click on “Import Drivers” Browse to the source directory that contains the extracted driver files 24 .

The source directory is shown After clicking next the import driver progress dialog will be displayed 25 .

The Confirmation Dialog window displays showing the completed import details The drivers imported are now listed in the driver subfolder 26 .

This selection profile was created for the Win7_x86 reference deployment.You should check your selection profiles once they are created to ensure the drivers are included. 27 . See details in “Use the Media Configuration to create Stand alone deployments and later sections.

Create a Task Sequence to deploy the reference image In the MDT. and try to use concise and descriptive “Task sequence name” and “Task sequence comments” because these last two items will be displayed in the task sequence window during the reference deployment. right click Task Sequence and click on the “New Task Sequence” menu item. Type in a descriptive Task Sequence ID. 28 .

you will need to modify the properties of the task to reflect the new location. For standard deployments this is the “Standard Client Task Sequence” Select the OS this task will install. Note that if you create folders and move the OS.Select the task sequence template. See “Creating a new Media Deployment for more information” 29 .

Again. Enter contact information for the task 30 .Do not specify a product key at this time. or enter a MAK key. see the Resources chapter for information on licensing.

The summary is displayed. click next if everything is setup properly. 31 .Select “Use the specified local Adminstrator password” and type in the password twice.

After the progress window. The new task sequence displayed in the main MDT window 32 . the wizard creates the task sequence and displays the Confirmation window.

33 . If you have problems with “Apply Network Settings” you can disable it. You can also click on “Continue on Error” for each sub task.Modifying the Task Sequence Actions Check you task sequence properties and enable or disable any steps as required in the Options tab.

you should set DeployRoot to nothing as follows "DeployRoot=" The below process documents making changes to the CustomSettings.How to Change BootStrap. For network deployments the DeployRoot variable should contain the UNC path to your network deployment share. ( This is only used for non-Media deployments such as network deployments ) Media deployments are detected as such by a media flag file on the boot media and do not use a network deployment variable. You can also change the settings on the network deployment share by right clicking the deployment share in the MDT and clicking on properties.ini files for a MDT Media deployment.ini file contains settings such as the DeployRoot variable which points to your deployment share.xml file if your network deployment uses multiple shares.xml. If you want to enable dynamic share points with mapdrive as documented in this guide.ini Settings in the MDT The bootstrap. According to Microsoft you should completely remove the DeployRoot variable when you use LocationServer. similar to the method used for MDT Media which is documented below. You can use the LocationServer. Right-click on the Media deployment and click on Properties 34 .

ini” you can edit the Bootstrap. and by clicking on “Edit Bootstrap.After clicking on properties. You can edit the CustomSettings.ini for this deployment and set the DeployRoot variable.ini directly in the window. or a Media Deployment ) You can also open the directory for the deployment share or media deployment directly and modify the CustomSettings.ini).ini or Bootstrap. ( ie the default deployment share. 35 .ini which are located in the “Control” directory. click on the “Rules” tab. Remember to run an update on the deployment that you changed( Not required for CustomSettings. an opened deployment share.

See the below explorer window and notepad window for reference regarding editing the configuration files directly 36 .

ini file for each deployment share. The image files are located in the Boot folder of the deployment share.iso. 37 . Replicate the local Deployment Share to a network share Once you have setup the initial deployment share on your local drive you may want to copy that deployment share to a final network share. You should also check your CustomSettings. OSInstall=Y is right even though it seems like it should be OSInstall=YES. The size of your deployment share and the speed of your network and systems will be an important factor in how long it takes to update. Large organizations normally use the Distributed File System to replicate deployment shares.. Johan Ardwidmark has verified that the code just looks at the first character. The Linked Deployment Share works best with a high speed low latency connection.Update the Deployment Share After making any changes to the deployment share you must update it so the changes are applied and the image files are updated (Litetouch_x86.. so “YES” is also acceptable. This can be done easily by creating a Linked Deployment Share in the MDT which allows you to easily update any changes. LiteTouch_x64. As shown below right-click the deployment share and choose “Update Deployment Share” from the context menu.iso and WIM files of the same name ).

and then expand advanced configuration. 38 . select “Merge” or “Replace” and complete the New Linked Deployment Share Wizard. Enter the UNC Path. expand the deployment share. comments and Selection profile ( should be “Everything” ). Right-click on “Linked Deployment Shares” and select “New Linked Deployment Share” as shown below.In the MDT. The Selection profile selected depends on your particular setup or requirements.

The Linked deployment share is shown below in the Deployment Workbench

Right-click on the Linked Deployment Share at any time and check or change the properties and options.

39

When you make changes to the main deployment share use “Replicate Content” to update the Linked deployment share – as shown below

You will then see the progress windows as the deployment gets replicated. This can take some time depending on how big your deployment share is, what selection profile you used, and how fast your connection is.

40

Open and modify a network Deployment Share
Once you have replicated your deployment share to a network share, you can open it and update it, or you can continue to use the “Linked Deployment Share object to update it.

If you open it you will then see it shown as a full deployment share in the MDT Deployment Workbench. Depending on your configuration your authentication server ( ie Windows Server 2008 ) needs to be available to allow MDT to open the network based deployment share.

41

Adding Application installs to the deployment Right-click on the “Applications” directory and click on “New Folder” Create a main folder for the class of applications you will be installing – ie Security Applications in this case 42 .

Right-click on the folder you created and click on “New Applications” Select the appropriate Application Type 43 .

Type in descriptive details for the application Browse to the source directory that contains your extracted setup files 44 .

for test images. etc. 45 . The install should be an automated install for final deployments. but its fine for use for demonstration purposes. In this case Microsoft Security Essentials does not allow automated install.Type in a descriptive name for the application directory to be created Type in the commandline to run the application install.

The application install is now shown in the Security Applications folder. You may need to modify your task sequence “Install Applications” step to have the application installed during deployment and it will need to be selected in your Selection Profile. 46 .The Summary is displayed. check it and continue if correct.

an application install that reboots the target system will cause problems with the MDT deployment. MDT 2010 handles the deployment reboots of the system being deployed during the deployment process.Note: It is very important for MDT deployments to ensure that the application install does not reboot the system it is being deployed on. 47 .

Once that is complete. boot your system with the USB key and choose the appropriate boot key ( such as F9 ) to choose the USB key as the boot device. Then navigate to the “Boot” directory in the windows explorer in the deployment share. You should probably have also created a linked network deployment share under Advanced Configuration in the MDT Workbench and replicated all the content there. create a Bootable USB key and copy the contents of the media directory “Content” in the Media directory you specified when creating the media to a bootable USB key.WIM file to a bootable WinPE bootable USB Key Method #3 After creating Media as specified in the next section “Use Media Configuration to create Standalone install deployments”.Running the USB boot Key with the completed MDT setup The first thing to do before you create your USB deployment key is to run the “Update Deployment” function. This can be done by using ISO mounting software such as Virtual Clone Drive. Method #2 Copy the . See below screen capture of the Content directory. then you will need to copy the required files to the USB key. Then copy the source files from the ISO to your bootable USB key. and right click on the appropriate ISO such as LiteTouchPE_x64. You will need to create a bootable USB key as detailed in Chapter 2 – Utilizing USB Keys and Bootable CD’s Method #1 Once you have created a bootable USB key.iso and mount the ISO to a virtual drive. ( You may also have to change settings in your bios ) 48 .

You may also want to check your task properties for problems before you update your deployment.For simplicity. 49 . you could also just burn the appropriate x86 or x64 ISO to a CD or DVD and boot that if you do not want to figure out the technicalities of creating a bootable USB key. Note: This is also useful if you use VmWare’s ESXi bare metal hypervisor since it does not support USB devices easily or without advanced technical tweaking.

select the appropriate task sequence 50 .Demonstration of a USB Key boot for a Network Share Deployment The initial Dialog Window when you bootup the MDT USB Key Once you select to run the Deployment wizard the task sequence selection dialog window appears.

You will not see this login screen for a Media deployment. Specify the computer name 51 .At the “User Credentials” screen specify the credentials for your deployment share.

Select whether to restore user data 52 .Join the computer to your domain or join to a workgroup. you can always add the computer to the domain later.

Specify the language Set the Time Zone 53 .

The summary window will appear. select “Begin” to continue the install Lite touch progress dialogs will appear Preparing the disk for install 54 .

Installing the image 55 .

56 .After reboot. post install steps will run and the install summary displays.

customize it some more. See Chapter 4 – “ Direct References for specific tasks” for more specifics.com/gimagex/ to capture or modify . You can then change this master image when you update your deployment images and recapture the final deployment image.Capture a Deployment Image with MDT For all captures of customized images its important to remember that there is basically a 3 update limit on running sysprep on a customized image. and import your customized .wim file. Import the capture as specified in Method #1 Method #3 Install Windows 7 on a workstation or laptop and customize it as much as possible. This means for the most part that you cannot sysprep your final deployment image. customize more. See below screen capture of the interface.exe from http://www. and then capture a master reference image. Method #1 To manually capture an image you already setup and customized via standard install of Windows 7 -see Method #3. 57 .ini for the deployment and set SkipCapture=NO Run the deployment and select the capture option. Then sysprep it and capture it using the below process – Capturing a Windows 7 reference install with imagex. edit CustomSettings. etc. sysprep it. and then recapture it again. KMS activation. Method #4 Use GImagex. To import an already captured file see the section “Import an Operating system to deploy” . See the resources chapter for more information on sysprep.autoitscript. recapture it. rearming. The recommended method for capturing images is to customize it as much as possible. you must start with the master reference image each time you wish to change the final deployment image. Method #2 If required.wim image files by launching it from Winpe/MDT boot media.

used to capture.exe to capture and deploy an image. help pages.exe WSIM. but I hope to give you a short introduction.WIM image files Windows System Image Manager – used to edit unattend. 58 .microsoft. or the WAIK included documentation. Then type the commands as specified. deploy and update images Deployment Image Servicing and Management .exe DISM. and of course Microsofts deployment forum at http://social. Imagex. It can take a bit of work to get into the details.technet.exe Windows Imaging tool . Reference the WAIK documentation that is installed with the WAIK for details.com/Forums/en-US/mdt/threads In the following examples of using imagex.0 boot disk and start a command prompt. but there are a lot of resources on the web such as videos. forums. you will need to boot with a WinPE 3. Its outside of the intended scope of this quickstart guide to describe the details.used to service offline . The WAIK includes the following files in addition to others.Introduction to WinPE tools You should have installed the Windows Automated Installation Kit when you installed MDT 2010.xml files You should reference the resource chapter for more information.

( copy the Windows 7 AIK tools to this directory on the WinPE bootable USB key first ) 9. Business. The /flags value is required if you are going to redeploy a custom Install. cd F:\Tools\Win7-AIK-Tools\x86 . Starter. drivers. The straight quotation marks are required. ServerDatacenter. Note: Imagex flag parameter . Ultimate.wim “Wim Title” /compress maximum /verify /flags “Ultimate” 10. ServerEnterprise. cd F: ( or whatever driver letter is for the base key ) 8. test the image on another system ( see the next section . run sysprep.wim file properly with the MDT you must use the Imagex flags option. HomePremium. etc 3. etc) 12. optionally./flags "EditionID" imagex /capture image_path image_file "name" {"description"} {/boot | /check | /compress [type] | /config | /flags "EditionID" | /norpfix | /scroll | /verify} Specifies the version of Windows you are about to capture. or preferably use the MDT deployment process – see section “Running the USB boot key with the completed MDT setup” and Demonstration of a boot with a boot key.How to deploy a standard WIM image using imagex . ServerStandard 59 .ie the Windows 7 AIK Windows PE bootable USB Key 7. Configure Windows 7 as required and install any required applications. boot with the Windows 7 Deployment USB key . run imagex. Valid EditionID values include: HomeBasic.exe /oobe /generalize /shutdown 6. copy the resulting image to a network location or import into the MDT 2010 11.exe /capture c: c:\win7-imagename. or an unattended install 2. cd c:\windows\system32\sysprep 4. This flag is not required if you deploy the image. Enterprise. find the subkey PersistAllDeviceInstalls under the main key “Sysprep” and set to 1 to preserve any device installs that have been completed 5. run regedt32. To deploy an imagex .wim with Windows Setup. by using ImageX.Capturing a Windows 7 x86 reference install with imagex 1 install Windows 7 using an install DVD.

13. Run diskpart and run the following commands ( on a single disk system ) a. If windows 7 does not boot properly. run imagex. dism. download or create a Windows 7 deployment USB boot key . create partition primary e. active i.net or softpedia.com ) 6. rescan k. format fs=ntfs quick g. or use the shutdown command from the tools directory 12.exe.exe from the Windows 7 WinPE USB key as follows a. Use the Mapdrive interface if installed to map a drive to the local share containing the enterprise . download the .ie WinPE 3. select partition 1 f. select disk 0 b. F: ( ie change to F: or whatever drive the actual USB key is ) b. clean c. and run diskpart again and 60 .wim image file ( Win7-image ) or map a drive manually from the cmd prompt ( Mapdrive can be downloaded from download. c: being the drive you created in 7) 10.0 and copy the WinPE files to it such as imagex.76 use the reboot button. Run diskpart again and ensure that partition 1 is active 9. imagex /apply R:\win7-image.wim image file for your enterprise deployment 2.How to deploy a Windows7 x86 image with imagex 1. Image a USB key with the Windows 7 USB boot image 4.exe. Reboot( if using Mapdrive 2. drive letter=c j. cd F:\Tools\Win7-AIK-Tools\x86 ( ie the WinPE tools you copied to the USB drive earlier ) c.wim 1 c: ( replace win7-image. run the 32 bit BCDEdit from the Win7 WinPE USB key from X:\windows\system32 with the following cmd Bcdedit c:\windows 11. boot the target machine with the USB key ( use F9 on an HP notebook to choose “USB Harddrive” to boot ) 5. boot up with the Windows 7 USB key. otherwise use the power button to reboot. select partition 1 h. list partition ( ensure there is an * next to Partition 1 ) j. select disk 0 d. etc 3. start a command line interface ( from the Mapdrive interface if installed ) 7. exit 8.wim with your image name ) ( R: being the drive you mapped. Windows 7 Enterprise should boot.

To activate you must change the product ID to a valid Windows 7 License #. This will fix the DNS activation error you will receive otherwise. but you have a 30 day period to activate.iso. These files are located in “Boot” folder of your deployment share. You can use the . Notes on the bootable deployment Media There are several ways to create your bootable deployment media as described in other sections. 14. You need to use x86 media for x86 deployments.WIM files to a bootable WinPE USB key. 61 . and rerun the bcdedit command.iso files to create bootable CD’s for deploying from a network deployment share.iso and LiteTouchPE_x64.check that the partition 1 is active.wim files are named the same with a . or you can copy the . The iso files are named LiteTouchPE_x86. and the . and x64 media for x64 deployments. For the enterprise version you have three days until Windows 7 activates automatically. x64 may also be called AMD64 in various places or literature.wim extension. You can use the Media folder deployment setup for media deployments.

which specifies what will be included in the media. You can create your own customized setup or you can use the Media folder in the MDT deployment Workbench to create specific bootable Media with specific contents. you may be able to have one large deployment setup. and completing the following graphically illustrated instructions. Creating a new Media Deployment Setup You will probably need to customize deployments to create selected deployments of a maximum size ( ie under 4 Gb ) If all of your technical people have large USB Keys. or USB disks. With MDT 2010 you can create bootable deployment setups that contain the full deployment utilizing USB Keys. DVD disks. etc. 62 . but its likely you will want to create customized deployments via the “Selection profiles” capability of the MDT 2010. a USB hard drive. This is done by creating a selection profile for the target media.Use the Media Configuration to create Stand alone install deployments In previous Windows deployments it was typical in my experience to use a network share for deployment. Right-click on the task sequences folder and choose new folder.

Create a descriptive task sequence folder that reflects the target/function of the deployment Now move the task x86 task sequence you created earlier in to the Win7-x86 task sequence folder you created so that it can be included in the x86 Media Selection profile. 63 .

it is important to create a “Selection profile” for use with generated deployments and specifically for generated Media deployments. In the “New Selection Profile Wizard” type in the selection profile name which should reflect the purpose of the profile – in this case for x86 Media. From the deployment Workbench screen highlight “Selection Profiles” under “Advanced configuration”. Select “New Selection Profile” from the Actions pane or use the right-click context menu on the “Selection Profiles folder. 64 . and type in any comments.Again. but it depends on your deployment setup as to how you will configure selection profiles.

applications. If your creating a 64 bit deployment use the same process but with 64 bit selections. You should create folders in all the areas needed such as Applications. the new selection profile is shown in the Selection Profiles window. The goal here is to create Media that will fit on a USB key or a DVD.In the folders screen select the appropriate folders to include in the Media selection profile. Task sequences. After completing the process. so we select only the Win7_x86 source files folder which contains the Windows 7 32 bit install. source files. 65 . etc to enable you to select only the tasks. etc that are needed for a specific deployment media.

Highlight the “Media” folder under “Advanced Configuration” for the selected deployment share. Create the target directory for your media and use the “Browse” button to select it in the New Media Wizard. 66 . Type in any comments and select the Selection profile you created earlier for the Media. or right-click the “Media” Folder and select “New Media” from the context menu. Then click on the “New Media” item in the Actions Menu.

Your Media will be created with a default title such as Media002.Click through the next screens to complete the New Media Wizard setup. 67 . If you are creating USB media you can deselect the “Create ISO option from the Media properties “General” page as shown below. you should rename it to a descriptive title as below by right-clicking on it and clicking on the rename option on the context menu.

You will also have to check your task sequence properties and reselect the OS if you moved it to a new folder such as Win7-x86 as shown below Check your task sequence settings by right-clicking on the task sequence and clicking on “Properties” 68 .

Make sure you run the “Update Media Content” function when you are done making changes to your Media deployment. 69 .

Some USB Keys just won’t work because they do not support boot. Method #1 Bootable USB Key On Windows 7 . select disk 1 clean create partition primary select partition 1 active format quick fs=fat32 assign exit Method #2 Bootable USB Key UltraISO provides the ability to create bootable USB keys to install Windows 7. Refer to the website for more information . You can then copy the WinPE / MDT files as needed to the key. select partition 1 h. 70 . or do not allow setting the removable media flag.Chapter 2: Utilizing USB keys and Bootable CD's Creating a Bootable USB Key It can be fairly difficult to get that bootable USB key to work. select disk 1 d.Run diskpart from a command prompt and do the following. select partition 1 f. clean c.http://www. Note: I use ghost32 to backup my USB Boot keys so I can easily image and re-image as needed with the required boot image needed for a particular operation. drive letter=c j. rescan k.Run diskpart and run the following commands ( on a single disk system ) a. active i. format fs=ntfs quick g. See the following sections for information on various ways to create bootable USB keys. select disk 1 b.ezbsystems. list partition ( ensure there is an * next to Partition 1 ) Copy the WinPE / MDT files as needed to the USB key. create partition primary e.com Method #3 Bootable USB Key On Windows 7 . Method #4 Bootable USB Key You can use tools such as the “HP USB Disk Storage Format Tool” and the “MBRWizard” to format and create a bootable USB key.

Chapter 3: Deployment Customizations Dynamically mapping to Deployment Sharepoints Dynamically mapping to Deployment Sharepoints can be a problem in deployments.xml file but this requires the file to be prepopulated. With the MDT you can use dynamic sharepoints in a number of ways. Here are some example DISM commands that will allow you to mount and unmount a . dism /Mount-Wim /WimFile:G:\Deploy\Boot\LiteTouchPE_x86. or as an “Extra Directory” in the Deployment share properties. and the folder containing the Mapdrive application needs to added to the boot media. You need to use Mapdrive for 32 bit deployments and Mapdrive x64 for 64 bit deployments. The most straightforward is to set the DeployRoot variable equal to nothing so that the deployment wizard gives you the option to manually enter the UNC pathname to the sharepoint. More details on using Mapdrive will be added to the next version of this Quickstart Guide.wim /index:1 /MountDir:C:\win7_x64\imgxmnt dism /unMount-Wim /MountDir:C:\win7_x64\imgx-mnt /commit 71 . Mapdrive can be used to dynamically map a drive to a copy of a Media deployment on a network share to run a deployment from a mapped drive. The unattend. You can also use the LocationServer.WIM file to modify it if required.xml needs to be modified on a copy of your LiteTouch or WinPE boot media so that it launches the mapdrive application and redirects to the mapped drive to run the Media deployment.

perform diagnostics or can be used on your Windows desktop to easily map to commonly needed network shares. by clicking on “Open User Settings File” Button created when no data file is present is xpdata. Refer to the rest of the this section for in depth instructions on Mapdrive. 72 . This file is also opened by default. Mapdrive x64 only runs on 64 bit versions of Windows and will run on WinPE x64 boot media – You can use it with WinPE or the Microsoft Deployment toolkit to dynamically map drives.Mapdrive description and basic instructions Mapdrive and Mapdrive x64 Mapdrivex64 is used to setup a network drive connection so you can image a system.Using Mapdrive or other utilities in MDT and WinPE deployments ).com Here is a screen capture of the Mapdrive x64 interface. Note: You can email me with specific questions about Mapdrive at pauljorgensen5@gmail. Using Mapdrive in deployments is documented at the end of the below general documentation on Mapdrive ( see section . You can open a pre-saved data file for mapping drives.dat.

dat files.The open file dialog is displayed. the default file Selecting a Servername from the server list retrieved from the data file 73 . The Mapdrive data files are .

Selecting a Sharename from the list retrieved from the data file Selecting a Username from the list retrieved from the data file 74 .

Select a drive to map from the drop down drive selection combobox Click on “Connect Network Drive to add the connection ( select drive letter first ) If the connection is sucessful you will receive the below dialog 75 .

click “Add ServerName Item” and then click “Save User Settings File” to save setup to a custom data file.Entering a new Servername example: to add the new servername to the list at item 8 – enter servername.dat ) You can get help for adding data to the fields by clicking on the ? Button beside the Main fields 76 . select item #. or select “Save aparameters to default file” to save settings to the default startup . ( 8 for example ).dat file ( xpdata.

and when typing the password now the characters are replaced by ### symbols or **** symbols 77 .When you unhide a password it becomes visible when typed When you click Hide Password the displayed password is erased.

Click on “Run Cmd Shell” to run a cmd prompt 78 .The R: drive now shows in the list after clicking “Update Current drive list”. Click “OK – Continue and Exit” to continue onto the Windows Deployment Wizard if you are running this from MDT boot media.

This requires that shutdown. but will run on WinPE32 or Windows 7 desktop. click on “Reboot Remote System”.To reboot remote system . Click on the Run Ghost button to run Ghost32. Ghost32 does not run on WinPE x64.exe ]. and click ok To reboot a the local system – click on “Reboot”. etc 79 .enter \\computername. You will be presented with the following Dialog box. Mapdrive will attempt to locate Ghost32 via the following drive path template – [ Drive:\ghost\ghost32.exe is located in the current directory or in the System path.

enter the desired name with a “.dat” or use the “Save Parameters to default file” button.You are prompted to manually enter the path if Mapdrive cannot find Ghost32.exe When you click on the “Save User Settings File” button you will get a “save as” box. 80 .dat” extension. If you wish this to be used by default. save the file as “xpdata.

thewindowsclub. or possibly from download.com.com 81 . This makes it very handy to run from the right click context menu for mapping frequently used drives on your Windows 7 workstation. Context Menu Editor is available from http://www.com called Context Menu Editor 1.1 which you can use to setup Mapdrive so it runs as desired from the right-click context menu on your installed Windows 7 workstation.there is a great utility you can download from download. See below for a screen capture of a typical setup for Mapdrive.Setting up Mapdrive to be run from the context menu in Windows 7 Although unrelated to deployment .

ini file in MDT from the “Properties Page” of your Deployment share. but it depends on how your deployment is setup and whether your using the MDT for your actual deployment.wim file. you will be prompted to enter the location of the deployment share when you run the deployment from bootable media. One option is to mount the .xml for your MDT/WinPE Boot media <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Description>Mapdrive Command to Map Drive prior to LiteTouch PE</Description> <Order>1</Order> <Path>X:\Tools\Mapdrivex64.WIM file with the /commit option. Note: You can also edit the bootstrap.ini and copy over the utilities such as Mapdrive x64( to \Tools\ ). change the bootstrap. Note: If you clear the deployment share setting in the bootstrap. Refer to Chapter 1 – How to Change the BootStrap.wsf</Path> </RunSynchronousCommand> </RunSynchronous> You have to modify the DeployRoot variable in your bootstrap.WIM file.exe X:\Deploy\Scripts\LiteTouch. then unmount the .ini file in your . The instructions for this will be detailed in the next version of this Quickstart Guide.xml for the boot media. here is a modified section of the unattend.wim file. For now.Using Mapdrive or other utilities in MDT and WinPE deployments In order to use Mapdrive to run a Media deployment from a network share you will need to add a RunSynchronousCommand section to the unattend.xml for your information. It’s probably a good idea to use the MDT to update your DeployRoot.ini File.ini in your . • Adding a RunSynchronousCommand Section to your unattended.exe</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Description>Lite Touch PE</Description> <Order>2</Order> <Path>wscript. 82 .

It will run on a standard desktop system . etc ). You can also type in the path to ghost32.ca for more information on Mapdrive and Mapdrive x64.e: etc or whatever the default system drive is with path listed above ).dat file to the WinPE boot media using an ISO editor. this likely would not be advisable for an MDT deployment but is a possibility for diagnostics or could be used for a custom setup ( because of changing drive letters.justcode.Direct References for Specific Tasks for further customizations 83 . Ghost32 must exist in a c:\ghost\ghost32. Refer to www. and you must copy the corresponding *.64 bit non-WinPE systems such as Windows 7 x64. MapDrive Notes: You must save the data file using “ Save User Settings File” in order to recover these entries when you run mapdrive again. DISM. ( WinPE creates a RAM disk for its own use – usually the X: drive ). It is possible to copy data files and applications to the root of a USB drive and access the files from WinPE by changing to the USB drive letter.exe type of path ( ie c:. or d:. etc if you wish to access these entries when booting with the WinPE Diagnostics CD.Ghost 32 notes: • • • To run ghost32. it currently does not run on the 64 Bit version of WinPE. - Customizing the LiteTouch or WinPE boot media Refer to Chapter 4 .exe manually as indicated previously in this document WinPE x64 note -Ghost32 only runs on the 32 bit version of of WinPE.

xml The simplest method for creating and using LocationServer. USA </friendlyname> <UNCPath>\\NYCDS01\Deployment$</UNCPath> </server> </servers> 84 . and then adding the following information: • A unique identifier • A location name.xml file configured for multiple locations. Listing 21.xml file and add entries for each deployment server in the environment (this can be either at the same location or at different locations).xml File to Support Multiple Locations <?xml version="1.Chapter 4: Direct References for Specific Tasks Microsoft references from MDT and WAIK documentation Microsoft: LocationServer. Seattle.0" encoding="utf-8" ?> <servers> <QueryDefault></QueryDefault> <server> <serverid>1</serverid> <friendlyname> Contoso HQ. USA </friendlyname> <UNCPath>\\STLDS01\Deployment$</UNCPath> </server> <server> <serverid>2</serverid> <friendlyname> Contoso NYC.xml file by creating a new section for each server.xml file is created using each of these properties using a sample LocationServer. Construct the LocationServer.xml is to create a LocationServer. used to present an easily identifiable name for that location • A UNC path to the MDT 2010 server for that location Listing 21 illustrates how the LocationServer. New York. Example LocationServer.

xml to display available deployment servers. Seattle. During LTI. 85 .xml First. Example LocationServer. If the BootStrap. MDT 2010 scripts read and process the BootStrap. USA </friendlyname> <UNCPath>\\STLDS02\Deployment$</UNCPath> </server> </servers> Microsoft: Understanding LocationServer.Using this format.xml file and. if it exists.0" encoding="utf-8" ?> <servers> <QueryDefault></QueryDefault> <server> <serverid>1</serverid> <friendlyname> Contoso HQ DS1. as shown in Listing 22.xml.ini file to gather initial information about the deployment. This happens before a connection has been made to the deployment server. the DeployRoot property is commonly used to specify in the BootStrap.ini file the deployment server to which it should make a connection. MDT 2010 scripts check for the existence of the LocationServer. Seattle. Listing 22.ini file does not contain a DeployRoot property. While initializing the HTML Application (HTA) wizard page. by specifying a different server entry for each server at that location. USA </friendlyname> <UNCPath>\\STLDS01\Deployment$</UNCPath> </server> <server> <serverid>2</serverid> <friendlyname> Contoso HQ DS2. Therefore. or for situations in which there are multiple servers within a single location. specify different server entries for each location (as shown in Listing 21). use LocationServer. MDT 2010 scripts load a wizard page to prompt the user for a path to the deployment server. you must understand How MDT 2010 uses LocationServer.xml File to Support Multiple Servers at Multiple Locations <?xml version="1.

Microsoft: Capturing a Disk Image for LTI Please refer to the section of the same name in the Microsoft book “Deploying Windows 7” 86 .

Windows Deployment Wizard Pages Skip this wizard page Administrator Password Welcome to the Windows Deployment Wizard Choose a migration type Configure the computer name Configure the target partition Join the computer to a domain or workgroup Using this property SkipAdminPassword SkipBDDWelcome SkipDeploymentType SkipComputerName SkipDestinationDisk SkipDomainMembership • DeploymentType • OSDComputerName • DestinationDisk • DestinationPartition • JoinWorkgroup or • JoinDomain • DomainAdmin • DomainAdminDomain • DomainAdminPassword Language and other preferences SkipLocaleSelection • KeyboardLocale • UserLocale • UILanguage Operating system deployment completed successfully Operating system deployment did not complete successfully Packages Ready to begin Select a task sequence to execute on this computer Select one or more applications to install SkipFinalSummary SkipFinalSummary SkipPackageDisplay SkipSummary SkipBuild. Note In instances where the Configure These Properties column is blank. and the properties that must be configured when skipping the wizard page. no properties need to be configured when skipping the corresponding wizard page. the property to skip the corresponding wizard page.If the SkipWizard property is used to skip all the Windows Deployment Wizard pages. provide all the properties in the Configure These Properties column. SkipTaskSequence SkipApplications • LanguagePacks • TaskSequenceID • BuildID • Applications 87 Configure these properties • AdminPassword . Table 3.0 Table 3 lists the individual Windows Deployment Wizard pages.Microsoft: How to skip Deployment Wizard Pages in in LTI – WinPE 3.

Skip this wizard page Set the Time Zone Using this property SkipAppsOnUpgrade SkipTimeZone Configure these properties • TimeZone or • TimeZoneName Specify credentials for connecting to network shares Skipped by providing properties in next column • UserID • UserDomain • UserPassword • BDEDriveLetter • BDEDriveSize • BDEInstall • BDEInstallSuppress • BDERecoveryKey • TPMOwnerPassword • OSDBitLockerStartupKeyDrive • OSDBitLockerWaitForEncryption Specify the BitLocker configuration SkipBitLocker Specify the product key needed to install this operating system SkipProductKey • ProductKey or • OverrideProductKey Specify where to save a complete computer backup SkipComputerBackup • BackupDir • BackupShare • ComputerBackupLocation Specify where to save your data and settings SkipUserData • UDDir • UDShare • UserDataLocation Specify whether to capture an image Specify whether to restore user data SkipCapture SkipUserData • ComputerBackupLocation • UDDir • UDShare • UserDataLocation 88 .

it is not updated by the replicate function. Typically you would create the default DeploymentShare on the c: drive and then use a linked deployment share on the network for the permanent deployment share ( under Advanced in the C:\DeploymentShare setup in MDT ) and replicate C: to it.ini Deployment Database Property applies to LTI ZTI for ConfigMgr Value YES NO Description Wizard page is not displayed. Edit the CustomSettings. but this is not the same as doing the replicate function in the MDT. The C: drive deployment share can be backed up/ moved / etc by simply copying the files to another computers C: drive.ini CustomSettings. and the information on that page is collected. and the information on that page is not collected. You will then still have to modify the CustomSettings.ini file and set – SkipAdminPassword = YES ( make sure yes is all uppercase ). When the LTI disk accesses the deployment share specified in its properties that were generated by the deployment workbench.ini on the linked network deployment share. Indicates whether the Administrator Password wizard page is skipped. see Providing Properties for Skipped Windows Deployment Wizard Pages. Property configured by BootStrap. Example [Settings] Priority=Default [Default] SkipWizard=NO SkipCapture=NO SkipAdminPassword=YES SkipApplications=NO 89 . This is the default value. For other properties that must be configured when this property is set to YES. Wizard page is displayed.Microsoft: Skipping the Administrator Password Wizard Page The configuration for this option is on the deployment share in the “control” folder. to a network share etc. it will read the configuration from the control folder.

Example SkipAppsOnUpgrade=NO SkipComputerBackup=NO SkipDomainMembership=NO SkipDeploymentType=NO SkipUserData=NO SkipPackageDisplay=NO SkipLocaleSelection=NO SkipProductKey=YES Caution This property value must be specified in uppercase letters so that the deployment scripts can properly read it. 90 .

wim SkipAdminPassword=YES SkipProductKey=YES SkipDeploymentType=YES SkipDomainMembership=YES JoinDomain=DomainName DomainAdmin=Administrator DomainAdminDomain=DomainName DomainAdminPassword=a_secure_password SkipUserData=Yes UserDataLocation=\\ServerName\Sharename\Directory\usmtdata SkipTaskSequence=YES TaskSequenceID=Enterprise SkipComputerName=YES OSDComputerName=%SerialNumber% SkipPackageDisplay=YES LanguagePacks001={3af4e3ce-8122-41a2-9cf9-892145521660} LanguagePacks002={84fc70d4-db4b-40dc-a660-d546a50bf226} 91 . In this sample. CustomSettings.ini File for a New Computer Scenario [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y ScanStateArgs=/v:5 /o /c LoadStateArgs=/v:5 /c /lac /lae SkipAppsOnUpgrade=YES SkipCapture=YES ComputerBackupLocation=\\ServerName\Backup$\ BackupFile=MyCustomImage. Note The properties that are used to skip wizard pages are in bold type in the listing. the properties to provide when skipping the wizard page are immediately beneath the property that skips the wizard page.ini file used for a New Computer scenario to skip all Windows Deployment Wizard pages.Microsoft: Fully Automated LTI Deployment for a New Computer Scenario Listing 14 illustrates a CustomSettings. Listing 14.

SkipLocaleSelection=YES UILanguage=en-US UserLocale=en-CA KeyboardLocale=0409:00000409 SkipTimeZone=YES TimeZoneName=China Standard Time SkipApplications=YES Applications001={a26c6358-8db9-4615-90ff-d4511dc2feff} Applications002={7e9d10a0-42ef-4a0a-9ee2-90eb2f4e4b98} SkipBitLocker=YES SkipSummary=YES Powerusers001=DomainName\Username CaptureGroups=YES SLShare=\\ServerName\Sharename\Logs Home_page=http://www.com/NewComputer 92 .microsoft.

Wim OS images Windows Imaging Specific tools and files for imaging computers’s with Microsoft’s imaging tools DiskPart Tool for servicing hard drives and partitions USMT User State Migration Tool Catalog file A binary file that contains the state of all of the settings and packages in a Windows image Configuration pass A sequence/phase of a Windows installation.MSU extension Task Sequence A configuration in the MDT 2010 that is selectable during and for the deployment which installs the target image onto the target system Unattend.wim A windows image file created with Imagex. service packs. the installation and configuration of software and/or hardware systems across an organisation Image-based Processes that install.xml An XML-based file that contains configuration settings to use during Windows Setup .0: Windows PE 3. update or maintain computer operating systems from a single image file Master Computer The computer from which the master image is created Master Image The image created from the master computer Master Installation The completed installation on the master computer Package Windows package files such as security updates. WAIK Windows Automated Installation Kit WSIM Windows System Image Manager 93 . etc.Chapter 5: Glossary DISM Deployment Image Servicing and Management tool included with the WAIK ImageX Utility for capturing. it is the bootable installation media you will create to run your deployments install.0 is part of the Windows 7 AIK. language packs.CAB or . Deployment. which end in a .exe or the MDT Windows PE 3. applying and updating .

Chapter 6: List of resources
Links
Deployment Guys blog http://blogs.technet.com/b/deploymentguys/ Deploying Windows 7 Guide http://www.mtit.com/reskit/chapter09.htm Johan Arwidmark Windows 7 deployment website http://www.deploymentcd.com/ A company that specializes in deployment , employed Johan Arwidmark http://en.truesec.com/ Michael Niehaus deployment website http://blogs.technet.com/b/mniehaus/default.aspx?PageIndex=3 Yannick Plavinol’s website www.revuedugeek.com Xtreme Deployment website http://deployment.xtremeconsulting.com/2010/03/10/keith-garner-on-mdt-2010/ Microsoft Volume Licensing Technical Guidence and Wall poster - VA 2.0 Vertical Wall Poster RTM.pdf http://www.microsoft.com/downloads/details.aspx?FamilyId=9893F83E-C8A5-4475-B02566C6B38B46E3&displaylang=en Microsoft Volume Activation Deployment Guide http://technet.microsoft.com/en-us/library/dd772269.aspx

Books and Documents
Deployment Fundamentals: Deploying Windows clients using MDT 2010 Lite Touch (Volume 1) - Johan Arwidmark , Mikael Nyström detailed guide on all aspects of setting up an enterprise deployment Deploying Windows 7 Guide Microsoft Essential guide on Windows 7 deployment Deploying Windows 7 with MDT 2010 – Basic Scenarios Gautier Confiant The Holy Grail of Deployment Rhonda Layfield 94

Index
“Control” directory .............................................. 35 Application commandline ................................................... 45 Applications ........................................................ 42 BCDEdit .............................................................. 60 boot key............................................................... 48 Bootable USB Key .............................................. 70 bootstrap.ini ......................................................... 34 Capture image with MDT ............................................. 57 Connect Network Drive ....................................... 75 Context Menu Editor ........................................... 81 CustomSettings.ini............................................... 34 diskpart................................................................ 60 DISM .................................................................. 71 domain ................................................................ 52 Dynamically mapping .......................................... 71 Ghost32 ............................................................... 79 GImagex.exe ....................................................... 57 Import .WIM Full set of source files ...................................... 13 unable to find SETUP files .............................. 18 Linked Deployment Share ................................... 37 Litetouch_x86.iso ................................................ 37 LiteTouchPE_x64.iso .......................................... 61 Mapdrive x64 ...................................................... 72 master reference image ........................................ 57 MDT Setup and use MDT ........................................... 8 New Media Wizard ............................................. 66 Replicate Content ................................................ 40 restore user data .................................................. 52 RunSynchronousCommand ................................. 82 Selection profile .................................................. 64 Selection Profiles window ................................... 65 sysprep ................................................................ 57 Task Sequence..................................................... 28 task sequence selection dia .................................. 50 unattend.xml........................................................ 71 Update Current drive list ..................................... 78 Update Deployment Share ................................... 37 Update Media Content ......................................... 69 USB deployment key........................................... 48 User Credentials .................................................. 51 virtual drive ......................................................... 14 VmWare’s ESXi.................................................. 49 Windows 7 Advanced Installation Kit ................... 8 WinPE x64 ......................................................... 83

95

About the Author

Paul Jorgensen works as an IT professional for the Government of Canada and lives in Atlantic Canada with his long time sweetheart Suzie. He maintains the website www.justcode.ca where you can find technical information about Windows, coding, electronics, Linux, etc.

96

Graphical Quickstart Guide to the Microsoft Deployment Toolkit 2010 97 .

Sign up to vote on this title
UsefulNot useful