Let’s see how to create custom image using MDT. In this post, you shall learn how to capture Windows 10 image creation using MDT. I hope this post helps SCCM admins to create MDT custom image.
Introduction -Image Creation Using MDT
In my lab infrastructure I’m using 2 VM’s for capturing the image. One VM I have installed the 2012 R2 server OS with MDT and installed the latest Windows ADK according to the Win 10 image. The second VM I’ll use to build and capture the image.
NOTE: If I want to capture Win10 1903 image, then MDT server has to be updated with Windows 1903 ADK.
In first step, downloads the latest Windows 10 ISO from MS VLSC (Volume Licensing Service Center) site. Open the deployment workbench console from the MDT server. To open MDT console go to search option and type deployment workbench.
Create New Deployment Share
Right click on the deployment share then click on New Deployment share.
Then choose the deployment share path and click on next.
Then provide the path name of the deployment share, click next button and define the description according to the choice and click next.
In option tab choose the correct option according to the requirement and click next.
Verify the settings according to the custom settings on the summary page and click next.
Once deployment share created successfully then click on finish. Now new deployment share will be created as below.
Import Operating System
Expand the deployment share, go to the Operating System step and right click select Import Operating System option.
Select Full set of source files if you are capturing the image from the CD, DVD drive. Then click next.
Browse the CD/DVD drive in the source directory and click next.
Note: To map CD/DVD drive in the MDT share, open Hyper-V Manager go to the MDT installed VM and right click on the settings.
Go to SCSI Controller DVD Drive and browse the ISO downloaded from the MS site.
Once mounted ISO soure selected, then provide the destination directory name and click next. According to the customization verify the summary and click next.
Post next Operating system will be imported to the deployment share folder. Once process completed click on finish.
Select Windows 10 Version – Enterprise
Now all edition of the Win10 image .WIM will be available on the deployment share, keep the required ones and delete others.
In my case I need the Win10 Enterprise Edition, so I’m keeping the same.
Select the wim file has to be deleted from the deployment share and right click delete. Post validate the wim files and check the option “Completely delete these items, even if there are copies in the other folder”
Click next and finish.
Create New MDT Task Sequence
Once OS import step is completed, move to “Task Sequence” step to create “New Task Sequence” and right click to capture the image.
Provide the “Task Sequence ID” and “Task Sequence Name” and click next.
Task Sequence Template
Select the “Standard Client Task Sequence” template and click next. Then select the operating system which was imported earlier step and click next.
In this step I’m not defining any product key as this will automatically activated from the KMS server. But this depends upon the requirement and click next.
Provide the details in the “Full Name” and “Organization” field and click next.
In this step do not specify any “Admin Password”, because password & other customization settings can be provided in the Bootstrp.ini file in deployment share properties and click next.
Verify the settings on “Summary” filed and click next and finish the step.
Now the task sequence will be created in the deployment share. Right click on the task sequence go to “Task Sequence” tab to see the steps has been created.
As next step right clicks on the deployment share and go to properties and uncheck the Platforms Supported “x86” in “General” tab. Then go to “Rules” tab modify the rule according to the requirement and click “Apply” & “Ok”. Also modify the “Bootstrap settings” in deployment share Control folder.
Modify the Bootstrap as below:
Update Deployment Share
Once all the customization settings are completed then go to deployment share right click and “Update Deployment share”.
Regenerate Windows 10 Boot Image
Select completely regenerate the boot images and click next, next and finish.
Once the deployment shares successfully updated with the boot image, then copy the LiteTouchPE_x64.iso from the deployment share “Boot” folder to other location. We can use the same boot image in VM 2 to capture the image.
Boot VM from ISO
Next step goes to Hyper V Manager. Then select the VM 2 right click and click on setting, go to DVD drive and browse the LiteTouchPE_x64.iso. Once this is completed then go to “Firmware” step to select the boot file, “Move up” the DVD drive to start build and click OK.
Turn on the VM and press any key to start boot from CD option.
Once booting started below screen will appear then click on “Run the Deployment Wizard to install a new Operating System”
- Then provide the deployment share path where it has been created.
- To connect deployment share provide appropriate credential to connect to the share.
- As next step, once it’s connected to the share image build and capture will start. Just wait while image capture in progress.
- Once the capture completed the new WIM file will stored in “Capture” location.
- Once WIM image captured, same file can be used in SCCM console to create “Operating System” package.
- How To Deploy Windows 10 Image Using Microsoft Deployment Toolkit (MDT) – https://www.anoopcnair.com/deploy-windows-image-using-mdt-sccm/
- Overview of Features in MDT
- Deploy a Windows 10 image using MDT