Microsoft Deployment Toolkit 2013 is a very useful tool for IT, System Administrators with lot of abilities. With Microsoft Deployment Toolkit (MDT 2013) you can reduce deployment time , standarizing desktop and servers images and improve security and ongoing configuration management.
Download page listing driver packs for HP computer systems for use in operating system deployment (64-bit).
- MDT Push Button Smart 55 from ETS 5.7.x.01: 09/20: V1.0a-prod: prod-MDT DCA App for device update Push Button Smart 55: 01/21: 3.4-etsapp: pdf: MDT Push Button Lite 63.01: 10/20: V1.3-prod: prod-MDT DCA App for device update Push Button Lite 63: 01/21: 4.0-etsapp: pdf: MDT Push Button Smart 63 from ETS 5.7.x.01: 09/20: V1.0a-prod.
- I only injected some of those drivers in MDT from the.cab file from Dell. The rest of the drivers I downloaded the.exe packages and extracted them. Then created a batch file that calls for those setup.exe and install.exe and tested via CMD line. The batch file is in the root folder that was created from the extraction.
In the past i wrote multiple articles for different features that you can use with MDT.
The result is to create the Category MDT that you can find also in Menu and you can read lot of articles related to Microsoft Deployment Toolkit 2013.
Today i write the article because previous week i receive the following email
<<I have found your guides very helpful but I am still have difficulties. I have inherited an MDT 2013 setup in my office for image deployment. I have very little experience with this product. It has worked well since it was introduced into or environment a year ago. We recently received a new model desktop HP EliteDesk 800 G2 and the image will not deploy to the new system. I have downloaded the drivers and created a folder in MDT deployment workbench deployment share for this specific model following the folder structure already in place. I am not sure how to apply/inject the drivers and update the image? I do not want to make changes to the production environment for fear of breaking it. I have copied the contents of the deployment server to an external drive and have been making my changes there. My hopes are to successfully apply the drivers on to the usb drive copy and create a USB bootable deployment. Can you provide some guidance? >>
I have already answer in the user but i thought that and other users maybe has this question. So let's start to explain step by step how can do it.
Import Setup Files of Windows
MDT 2013 support adding full source of Windows DVD ISO or custom images that you have created. For the article will be use a Windows 8.1 Pro x64 ISO file to Import in MDT 2013. If you have an iso file of Windows open the folder which include the iso files, right click and select Mount. Then you will see a new DVD Drive in My Comuter with the files of Windows iso to import in MDT 2013. If you don't have an iso file but you have Windows files in a folder you don't need to do this.
- Expand the Deployment Shares and the MDT Deployment Share.
- Right Click in Operating Systems and select Import Operaring System.
- Select Full set of source files.
- Browse and find the DVD Drive which mount with Windows ISO file in previous step and click Next.
- Change the name of destination directory or use the default and click Next.
- Verify in the Summary that all the options are ok and click Next.
- Wait to finish the import and then click Finish.
Base on your hardware and status of your Windows it will take some time. For your reference a normal time is 15-25 minutes.
- In the right side you can see the Operating System which import.
Import Drivers in MDT
Now it's time to import the drivers for specific version of Laptop/PC that need to Deploy.
- Expand Deployment Share - - -> MDT Build Lab - - -> Out of Box Drivers
- Right Click in Out of Box Drivers and select New Folder.
- Type the folder name and click Next. I recommend to keep a clear structure in the folders of your MDT because you must identify and understand quicly what you have in MDT.
- Just click Next
- Wait to finish and click Finish.
- In my enviroment for every PC Model i create and subfolders for x64 or x32. So in this article i create a subfolder for the specific model as x64.
- Now right click in the folder which create and select Import Drivers.
- Select the source directory which include the drivers and click Next.
- This is onlya Summary. Click Next.
- Wait to finish and click Finish.
- Now if you go in your folder which Import the drivers you will see all the driver in the right side.
Create the Task Sequence
- Expand the Deployment Shares and the MDT Deployment Share.
- Right Click in Task Sequence, select New Task Sequence.
- Fill the Task SequenceID and TaskSequenceName (names that you can identify in the future) , clck Next.
- Select Standard Client Task Sequence.
- Select the OS which created before
- You can specify a product key now or leave it as it to activate the Windows after the installation
- Fill the Organization with a name.
- Specify the local Admin Password if you want or select Don't specify an Administrator password at this Time
- Here is a Summary only , click Next
- Clik Finish
Create the Selection Profile
Now it's time to create the Profile that will be use for the Media in the next step.
- Expand the Deployment Shares , MDT Deployment Share and Adnamced Configuration
- Right Click in Selection Profiles, select New Selection Profile
- Type the name of Selection Profile and click Next.
- Expand and tick the the folder of Operating System, Out of Box Drivers and Task Sequence which Import in previous steps. Click Next.
- Just a Summary of your Configuration. Click Next
- Wait to finish and click Finish
Create and Update the Media for Offline Use
Here we will create the Media which include the ISO file that will use for the Boot.
- Expand the Deployment Shares , MDT Deployment Share and Adnamced Configuration.
- Right Click in Media, select New Media
- Click Browse and select the folder which be create the Media.
- When finish with the structure and have select the Media Path go in Selection Profile and select the Profile which create in previous step (Windows 8.1 x64(Full Update) for the article). Click Next
If you will use Offline Media for the Deployment it's better to create a folder like Offline Media and for every Media that will be create to create a new subfolder with the name of Windows OS.
For example my struture forOffline Media is
- This is only a Summary. Click Next
- Wait to finish and click Finish.
- Now you can see the new Media in the right Pane.
- Right click in Media and select Update Media Content. It will take some timme until finish.
- When finish go in the path that select for the Media in the first step and you will se a LiteTouchMedia.iso.
- Use a software like Rufus or Windows USB/DVD Download Tool to create your bootable USB.
- Plugin the USB in the Laptop/PC and boot to start the installation
This procedure you can use it for every Windows OS combine it with your PC/Laptop modesl in your enviroment and take advantage.
It will be my pleasure if you have your own recommendations or questions to be share in our commented system. You can help others or help yourself if share it.
Have a nice weekend !!
Free Tools for everyone
Please refer to the tutorial below for Windows 10 Deployment with MDT
Components used in this lab
- Windows 2019 Server Core as AD Domain Controller
- AVENTIS-AD01 – 192.168.1.230
- Windows 2019 Server as MDT Deployment Server
- AVENTIS-MGMT – 192.168.1.232
Software Required for MDT Installation
- Download Windows ADK for Windows 10, version 1903 and Windows PE Add on for ADK and save it locally
Windows PE is available separately form the Assessment and Deployment Kit (ADK) starting from Windows 10 version 1809
- Download Microsoft MDT 8456 – MicrosoftDeploymentToolkit_x64.msi
- Download ISO Installation file for Windows 10 1909 from [Microsoft Volume License Service Center] (https://www.microsoft.com/Licensing/servicecenter/default.aspx)
- Installation Files for Applications, like 7Zip, Foxit Reader and etc
Installation of Windows Deployment Service (WDS)
Install WDS Role with the PowerShell
Open Windows Deployment Service and right click on Server-SERVER_NAME-Configure Server
Select Integrated with Active Directory
Select the Remote Installation Folder
Select Response to all client computers (known and unknown)
Uncheck Add image to the server now
We will prepare the Boot & Capture Image in later stage
Preparation of DHCP Server for PXE Boot
Add the following DHCP Options to existing DHCP Server running on AVENTIS-AD01
DHCP Option 066 & 067 are configured
Do not configure Option 60 if DHCP Server is NOT installed on MDT Server, or VM will failed to boot from PXE with error PXE-E55 ProxyDHCP did not reply to request on port 4011
Installation of Windows ADK & MDT
Install ADK v1903 by double click on C:Usersadministrator.LABDownloadsWindows Kits10ADKadksetup.exe
Select the following features when prompted
- Deployment Tools
- Imaging And Configuration Designer (ICD)
- Configuration Designer
- User State Migration Tool (USMT)
Install WinPE by double click on C:Usersadministrator.LABDownloadsWindows Kits10ADKWinPEAddonsadkwinpesetup.exe
Installation of MDT v8456
Launch MDT by opening Deployment Workbench
Create Deployment Share with PowerShell
Import PowerShell Module for MDT
Create a New Deployment Share called MDT$ in M:MDT on AVENTIS-MGMT
Prepare Boot Image in WDS
A boot image is a WindowsPE which is a stripped down OS that only includes the necessary tools to install, deploy, and repair Windows.
Mount Windows 10 1909 ISO File
Right click on Boot Image-Add Boot Image
MDT Driver Download
Enter Image Name, like WIN10-BOOT
Import VMware Drivers to Boot Image
Please follow the steps below to import VMware Drivers to Boot image if you are preparing the Windows 10 reference image in VMware ESXi Host
Download VMware Tools (windows.iso) from ESXi host with SCP
Mount the ISO file and extract the contents to M:MDT-AppsVMware with 'setup64.exe /a /p'
VMware Drivers are extracted to M:MDT-AppsVMwareVMwareVMware ToolsVMwareDrivers
Open Windows Deployment Services and right click on Drivers – Add Driver Package to import drivers
Create a Driver Group called VMware where prompted
Accept all default values when prompted, and VMware Drivers are imported successfully
Right click on WIN10-BOOT and select Add Drivers Package to Image
Click Search for Packages
VMware Drivers are imported to boot.wim image successfully
Prepare Capture Image
A capture Image is used to capture a Windows 10 Reference Images and import it to MDT for deployment
Right Click on WIN10-BOOT and select Create Capture Image
Enter Name & Location for Capture Image
Check Add Image to the Windows Deployment Server Now
Enter the Location & Image Name when prompted
WIN10-BOOT & WIN10-CAPTURE are created in WDS successfully
Prepare Windows 10 Reference Image
Mdt Driver Download Tool
Refer to Prepare Windows 10 Image for MDT Deployment
Capture Windows 10 Reference Image
Refer to Capture Windows 10 Image for MDT Deployment
Import Windows 10 Reference Image
Import the captured WIN10-2004.wim file to MDT
- -SetupPath – Location of the Windows 10 ISO File
- -DestinationFolder – Create a new Folder for WIN10-2004.wim image
Rename the imported image
WIN10PRO-2004.wim is imported to Deployment Share – Operating Systems successfully
Out of Box Drivers
Medrx usb devices driver download windows 7. Drivers for Windows 10 can be organized in folder and injected to Windows 10 during MDT deployment
Download and extract SCCM Driver Pack, like HP Driver Pack and import to MDT Server using PowerShell below
New folder called VMware is created in Out-of-Box-Drivers with all VMware Drivers imported
Selection Profile can be used to control what drivers and packages are injected into the Boot Image.
Create a new Selection Profile called VMware with all drivers in Out-of-Box DriversVMware
Task sequences are basic XML files which call on a series of scripts to run parameters chosen by the user, when the task was created.
Create a new Task Sequence based on the template Client.xml to deploy WIN10PRO-2004.wim to new computer
Customize the Task Sequence
- Disable Format and Partition Disk (BIOS)
- Remove the Recovery Partition and increase the Windows (Primary) partition to use 100% of the remaining spaces
- Inject Drivers – Select the Drive Profile to be installed during OS Deployment
- Install Operating System – Select the WIM file that will be deployed and Select Next Available Formatted Partition
- Inject Drivers – Select Continue on Error
- Add a PowerShell Script in State Restore – Custom Tasks – Run PowerShell Script
Create a PowerShell Script called PostInstallation.ps1 in M:DeploymentShareScriptsCustom
- Enter the location of PowerShell Script – %SCRIPTROOT%CustomPostInstallation.ps1
- Disable Apply Local GPO Package
We had create a task sequence to deploy Windows 10 PRO successfully
Convert the Task Sequence to Template
Copy the the Task Sequence we prepared above from M:DeploymentShareControl010ts.xml to M:DeploymentShareTemplatesTS-WIN10PRO-UEFI-VM.xml
Open the XML file with Notepad and change the Display Name this Template
Mdt Dim2 Led Driver Download
Select the Template – TS-WIN10PRO-WUFI-VM when you want to create a similar Task Sequence in the future.
Update Deployment Share
Update Deployment Share with the latest file from the Windows ADK to updates or regenerates the required Windows PE boot images in both WIM and ISO file formats.
- Right click on MDT Deployment Share – General and uncheck x86 as we are going to use x64 files only
- Modify the CustomSettings.ini (Rules) and Bootstrap.ini in M:DeploymentShareControl
- Uncheck Generate a Lite Touch Bootable ISO Image as we are not going to use the WinPE ISO file to boot up VM
- Update Deployment Share
MDT Monitoring let you to monitor the progress of deployment tasks and check for error message from MDT console
Check Enable Monitoring for this Deployment Share
Ensure that Microsoft Deployment Toolkit Monitor Service is running
Allow inbound TCP 9800 & 9801 if Windows Firewall is enabled – Optional Steps
Verify that EventService=http://PROD-MDT.lab.aventislab.com:9800 is added in CustomSettings.ini
Access to http://192.168.1.232:9801/MDTMonitorData/ to confirm that the page below is displayed
Dell Mdt Driver Download
You can monitor the deployment progress in MDT Console now