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.
Import the Drivers in MDT 2013. Identify your Laptop/Workstation Model and import the drivers in MDT 2013. Find all the details in the following article. How to add drivers in Windows ISO with MDT 2013 Create New Task Sequence. After import the Windows OS and add drivers we must create the Task Sequence for the Deployment.
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.
- In MDT 2013 (Lite Touch), there are two types of drivers to worry about when deploying Windows. There are drivers for Windows PE 5.0 (the boot image) and there are drivers for the Windows Operating System that you deploy.
- The INF files are what Microsoft Deployment Toolkit (MDT) needs for driver injection. Many drivers are distributed as packages, which come in the form of an executable different from the Cabinet Files (CAB). Since the drivers are available in executable (.exe), this cannot be uploaded directly into MDT.
- Get drivers and downloads for your Dell OptiPlex 3040. Download and install the latest drivers, firmware and software.
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.
Mdt Drivers Total Control
- 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
Came across this great post by Keith Garner (http://ow.ly/JeHHD) on Microsoft Social forum
Its the most thorough debugging guide I’ve seen on drivers in MDT
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the full OS
- Step 1 – Try network connection again
It’s possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
- Step 2 – Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment Server, manually connect to the Deployment Share. IF you can’t connect to the Deployment Share, neither can MDT.
- Step 3 – Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever. Install the driver package by:
○ Open the Device Manager (devmgmt.msc).
○ Find the network device in the list (ensure this is the wired device, not the wireless device)
○ Right click on “Properties” and click on the “Details” tab.
○ From the “Details” tab, select the property “Hardware Ids” select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
○ From the “Driver” tab, click on “Update Driver…”, click on “Browse my computer for driver software” locate the driver package on the local machine or USB Drive, and install the package.
○ You should get a confirmation that the driver package was installed.
○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See: http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
- Step 4 – Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
- Step 5 – Run the full MDT installation
During installation MDT will perform the following:
○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the “HardwareIDs” property above must be present in this list. Otherwise we won’t have a match.
○ Search through the %DeployRoot%controldrivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
○ MDT will copy each matching driver to the local c:drivers directory using the xcopy.exe command. You can search (grep) for the string “xcopy” in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:windowsinfSetupAPI.*.log files will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in WinPE
- Step 6 – Try the network connection again
- Step 7 – Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
○ Try connecting to the Deployment Share:
c:> net use * MDTDeploymentShare$ /u:UserDomainUserName *
○ Try pinging the Deployment Server:
c:> Ping.exe MDT.Corp.contoso.com
○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address – Driver OK – WinPE can’t reach the DHCP server. If you have “Media Disconnected” – Driver OK – Physical adapter not plugged to network. If no devices are listed – Driver bad – Driver not installed.
○ Check the x:windowssystem32WpeInit.log – This log will show the network driver (if found) being installed.
- Step 8 – Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via “Selection Profile” or other method. Cross check your WinPE Driver Settings.
○ From within the MDT console, right click on the root of your Deployment Share and select properties.
○ Click on the “Windows PE” tab, and the “Drivers and Patches” sub tab for both x86 and x64.
○ Your Network Drivers package must be in the “Selection Profile” if enabled.Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals http://live.sysinternals.com/Dbgview.exe tool.
○ Open up the MDT console.
○ Download and run the DbgView.exe tool.
○ Update the deployment share in question.
○ The DbgView tool should show what drivers were copied to each WinPE Image.
- Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select “Completely regenerate the boot images.” to ensure the drivers is imported. Additionally, you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
- Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the “RIS” class of drivers from Broadcom in your MDT environment.
- Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
- This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic. http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Drivers Mdt Software
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Drivers Mdt Driver
- Include a short description of the problem. Including the Make/Mode if necessary.
- Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
- Copy your known good driver package (step 3 above) to OneDrive.
- Copy the following log files to a public site like OneDrive and include the link:
○ PnpEnum.xml (from Client)
○ Bdd.log (From Client) – or at least the ZTIDrivers.log file.
○ c:windowsinfSetupAPI.*.log (from client)
○ %DeployRoot%controlsettings.xml (if problems in WinPE)
○ x:windowsSystem32WpeInit.log (if problems in WinPE)
○ If the MDT server is not including your driver package in WinPE include the DBGView log.