Deploy a Windows 1. MDT Windows 1. 0Applies to. This topic will show you how to take your reference image for Windows 1. Microsoft Deployment Toolkit MDT. You will prepare for this by creating a MDT deployment share that is used solely for image deployment. Separating the processes of creating reference images from the processes used to deploy them in production allows greater control of on both processes. You will then configure the deployment share, create a new task sequence, add applications, add drivers, add rules, and configure Active Directory permissions for deployment. For the purposes of this topic, we will use three machines DC0. MDT0. 1, and PC0. Create a Bootable USB Flash Drive for Hirens Boot CD diagnostic and recovery toolset ERD Commander replacement. Recover data, fix a damaged PC etc. Chris Isaak Wicked Game Flac Link. Windows 10 4in1 14393. Ms Dart 8 Iso Wim X64' title='Ms Dart 8 Iso Wim X64' />DC0. MDT0. Windows Server 2. R2 standard server, and PC0. Windows 1. 0. MDT0. PC0. 00. 5 are members of the domain contoso. Deploy Windows 10 in a test lab using System Center Configuration Manager. Ms Dart 8 Iso Wim X64' title='Ms Dart 8 Iso Wim X64' />Contoso Corporation. Note. For important details about the setup for the steps outlined in this article, please see Deploy Windows 1. Microsoft Deployment Toolkit. Figure 1. The machines used in this topic. Step 1 Configure Active Directory permissions. Ms Dart 8 Iso Wim X64' title='Ms Dart 8 Iso Wim X64' />This topic will show you how to take your reference image for Windows 10, and deploy that image to your environment using the Microsoft Deployment Toolkit MDT. Dart0.PNG' alt='Ms Dart 8 Iso Wim X64' title='Ms Dart 8 Iso Wim X64' />These steps will show you how to configure an Active Directory account with the permissions required to deploy a Windows 1. MDT. These steps assume you have downloaded the sample Set OUPermissions. C SetupScripts on DC0. The account is used for Windows Preinstallation Environment Windows PE to connect to MDT0. In order for MDT to join machines into the contoso. Active Directory. On DC0. 1, using Active Directory User and Computers, browse to contoso. Contoso Service Accounts. Select the Service Accounts organizational unit OU and create the MDTJD account using the following settings Name MDTJDUser logon name MDTJDPassword Pssw. User must change password at next logon Clear. User cannot change password Select. Password never expires Select. In an elevated Windows Power. Shell prompt run as Administrator, run the following commands and press Enter after each command. Set Execution. Policy Execution. Policy Remote. Signed Force. Set Location C SetupScripts. Set OUPermissions. Account MDTJD. Target. OU OUWorkstations,OUComputers,OUContosoThe Set OUPermissions. MDTJD user account permissions to manage computer accounts in the Contoso Computers OU. Below you find a list of the permissions being granted Scope This object and all descendant objects. Create Computer objects. Delete Computer objects. Scope Descendant Computer objects. Read All Properties. Write All Properties. Read Permissions. Modify Permissions. Change Password. Reset Password. Validated write to DNS host name. Validated write to service principal name. Step 2 Set up the MDT production deployment share. When you are ready to deploy Windows 1. MDT deployment share. You should not use the same deployment share that you used to create the reference image for a production deployment. For guidance on creating a custom Windows 1. Create a Windows 1. Create the MDT production deployment share. The steps for creating the deployment share for production are the same as when you created the deployment share for creating the custom reference image On MDT0. Administrator in the CONTOSO domain using a password of Pssw. Using the Deployment Workbench, right click Deployment Shares and select New Deployment Share. On the Path page, in the Deployment share path text box, type E MDTProduction and click Next. On the Share page, in the Share name text box, type MDTProduction and click Next. On the Descriptive Name page, in the Deployment share description text box, type MDT Production and click Next. On the Options page, accept the default settings and click Next twice, and then click Finish. Using File Explorer, verify that you can access the MDT0. MDTProduction share. Step 3 Add a custom image. The next step is to add a reference image into the deployment share with the setup files required to successfully deploy Windows 1. When adding a custom image, you still need to copy setup files an option in the wizard because Windows 1. SourcesSx. S folder which is outside the image and may be required when installing components. Add the Windows 1. Enterprise x. 64 RTM custom image. In these steps, we assume that you have completed the steps in the Create a Windows 1. Windows 1. 0 reference image in the E MDTBuild. LabCaptures folder on MDT0. Using the Deployment Workbench, expand the Deployment Shares node, and then expand MDT Production select the Operating Systems node, and create a folder named Windows 1. Right click the Windows 1. Import Operating System. On the OS Type page, select Custom image file and click Next. On the Image page, in the Source file text box, browse to E MDTBuild. LabCapturesREFW1. X6. 4 0. 01. wim and click Next. On the Setup page, select the Copy Windows 7, Windows Server 2. R2, or later setup files from the specified path option in the Setup source directory text box, browse to E MDTBuild. LabOperating SystemsW1. EX6. 4RTM and click Next. On the Destination page, in the Destination directory name text box, type W1. EX6. 4RTM, click Next twice, and then click Finish. After adding the operating system, double click the added operating system name in the Operating Systems Windows 1. Windows 1. 0 Enterprise x. RTM Custom Image. Note. The reason for adding the setup files has changed since earlier versions of MDT. MDT 2. 01. 0 used the setup files to install Windows. MDT uses DISM to apply the image however, you still need the setup files because some components in roles and features are stored outside the main image. Figure 2. The imported operating system after renaming it. Step 4 Add an application. When you configure your MDT Build Lab deployment share, you will also add any applications to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the MDT Production deployment share using Adobe Reader as an example. Create the install Adobe Reader XI x. In this example, we assume that you have downloaded the Adobe Reader XI installation file Adbe. Rdr. 11. 00. 0euES. E SetupAdobe Reader on MDT0. Using the Deployment Workbench, expand the MDT Production node and navigate to the Applications node. Right click the Applications node, and create a new folder named Adobe. In the Applications node, right click the Adobe folder and select New Application. On the Application Type page, select the Application with source files option and click Next. On the Details page, in the Application name text box, type Install Adobe Reader XI x. Next. On the Source page, in the Source Directory text box, browse to E SetupAdobe Reader XI and click Next. On the Destination page, in the Specify the name of the directory that should be created text box, type Install Adobe Reader XI x. Next. On the Command Details page, in the Command Line text box, type msiexec i Adbe. Rdr. 11. 00. 0euES. Next twice, and then click Finish. Figure 3. The Adobe Reader application added to the Deployment Workbench. Step 5 Prepare the drivers repository. In order to deploy Windows 1. MDT successfully, you need drivers for the boot images and for the actual operating system. This section will show you how to add drivers for the boot image and operating system, using the following hardware models as examples Lenovo Think. Pad T4. 20. Dell Latitude E6. HP Elite. Book 8. Microsoft Surface Pro. For boot images, you need to have storage and network drivers for the operating system, you need to have the full suite of drivers. The Computer Paper BC Edition by The Computer Paper. The Computer Paper BC Edition   Published on Nov 2.