?
Solved

How to inject drivers into a custom WIM using the MDT 2010 Task Sequence

Posted on 2011-10-24
6
Medium Priority
?
1,124 Views
Last Modified: 2012-08-13
Hi.  I've created a MDT 2010 Update 1 Task Sequence that installs Windows 7 and several application.  The sequence then captures the build to a WIM file.   I created another Task Sequence that deploys this Task Sequence to a computer.  Everything works great when deploying to a VMware virtual system, and when deploying to an HP 8100.  But when I deploy the image to a Dell Latitude E6320,  many drivers are not installed and the build fails.  It gets as far as installing the OS and then doing a restart, but cannot find the device drivers to connect back to the network and complete the build sequence.

I have downloaded the driver bundle from Dell and have imported the drivers to MDT.  I have added the Inject Drivers task and specified to install the E6320 drivers if the model is like "Latitude E6320%"    I can see the task run as the drivers are injected, but after the reboot, the ethernet controller is not available as well as several other devices.

Thanks in advance.
0
Comment
Question by:netrxinc
  • 5
6 Comments
 
LVL 13

Expert Comment

by:notacomputergeek
ID: 37025209
If you downloaded the exe from the Dell website, you'll actually have to run that file to extract it, then import that into the MDT. It won't work if you're just inporting the exe that you download.
0
 

Author Comment

by:netrxinc
ID: 37034403
I had imported the extracted driver files.
0
 

Author Comment

by:netrxinc
ID: 37127471
I've requested that this question be deleted for the following reason:

No responses.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Accepted Solution

by:
netrxinc earned 0 total points
ID: 37127467
The issue was due to a C:\Drivers folder that was embedded in the WIM.  This caused the injected drivers to be inserted into C:\Windows.old.  I used gimagex.exe to mount the WIM and delete the C:\Drivers folder.  The next time the WIM was applied, the drivers were properly injected.
0
 

Author Comment

by:netrxinc
ID: 37127472
I found the answer and have posted it.
0
 

Author Closing Comment

by:netrxinc
ID: 37158219
It works and no one else provided a valid response,
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

IF you are either unfamiliar with rootkits, or want to know more about them, read on ....
A new hacking trick has emerged leveraging your own helpdesk or support ticketing tools as an easy way to distribute malware.
This Micro Tutorial will teach you how to change your appearance and customize your Windows 7 interface to your unique preference. This will be demonstrated using Windows 7 operating system.
This Micro Tutorial will give you a introduction in two parts how to utilize Windows Live Movie Maker to its maximum capability. This will be demonstrated using Windows Live Movie Maker on Windows 7 operating system.
Suggested Courses
Course of the Month14 days, 17 hours left to enroll

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question