MDT - Injecting Drivers

Morning,
I've managed to figure out how to inject drivers using the %make and %model% variables. After booting into the image the drivers are not installing automatically; I have to manually install them myself by going into device manager and updating.
Is there a way to automate this at all?
Many Thanks

All i've done so far is installed windows 7 from the disk and capture an image without syprepping it using MDT. I was then hoping what I could do is to use this image to install a basic copy of Windows 7 and inject the necessary drivers. I'm guessing doing
it this way does not go through the Windows 7 setup stage until I sysprep it?
Hope that makes sense
Regards

Similar Messages

MDT 2010 - USB 3.0 issue after OS Install and Inject Drivers steps

Hello,
I'm using MDT 2010 and I'm booting and image PCs from a USB drive. On some newer systems (eg: Latitude El530) I have issues when I use the USB 3 ports (if media is connected to USB 2 port, everuthing is fine). The systes recognizes the USB stick and I can
start the Task Sequence just fine. I pass the Install OS step and Inject Drivers step, but after the first reboot, I get the prompt to insert the media to continue the deployment. This happens only if the stick is connected to the USB 3.0 ports. If I
check Device Manager, I see the USB device withouth driver. The drivers are already on the USB stick...I puled them from FileRepository from an updated system with all the drivers. Is anyone else having similar issues? I see other people have USB 3 issues,
but mostlly to start the deployment from it, or at partitioning...I don't have that issue. My issue starts after the OS is installed.
Any sugestion is appreciated...Thank you...
aburica

You should be able to do this. nVidia Optimus video drivers have the same issue. How we solved this
We create selection profiles for each make and model
We inject every single driver in profile for each make and model
The Optimus driver then gets installed because it is local to the machine already.
Why it didn't work before is the child device never gets detected during the PNP enum that happens when you have 'Install only matching drivers from the selection profile' so never ends up in the local driver store.
P.S. We ONLY have the drivers that install imported into each make model folder.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
How to ask a question that is fixable.

Inject Drivers Task Sequence Step vs Using DriverSelectionProfile in Database

I'm using a Database and 'Make and Model' in MDT 2012. I wonder if I specify a DriverSelectionProfile in the Database, what happens when the Task Sequence reaches the Preinstall > Inject Drivers step? Does it process the selection there and ignore the
Database settings? Or should I disable this step in the Task Sequence?
Orange County District Attorney

If you are having driver folders that are named after the computer models a single line is enough. MDT will replace the variable with the real model name. If you only deploy Windows 7 SP1 x64 you can set in the CustomSettings.ini file.
[Default]
DriverGroup001=Windows 7 x64\%Model%
If you deploy multiple operating systems (Windows Server 2012 R2, Windows 8.1 and Windows 7) it's easier to set it in the task sequence instead.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Windows 7 Sysprepped Image - Injecting Drivers issue

Hi
I have created a Windows 7 Image, sysprepped it and capture an image using MDT. I am using the "Total Control" driver management method and during the imaging phase I can see that it injects the drivers into the image but for some strange reason,
and I can't see to figure out why, it's not installing the drivers during the windows setup phase.
Please can someone help!
Thanks

How do you know for sure the drivers are not getting installed, and how do you know for sure you have the correct drivers? Please illusrate. You should be able to boot into the new OS, open DevMgmt.msc, and update each missing device with drivers MDT copyied
to the c:\Drivers folder, if these drivers don't install, then you might now have the correct drivers.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT Copying drivers but not applying

Hello all,
We use the 'total control' method for drivers, defining Drivergroup001 as "Windows 7 x64\%Model%" and placing the appropriate drivers into the folder structure.
During build, MDT correctly identifies the model, assigns the Drivergroup001 variable and copies all drivers from that folder into the c:\Drivers folder on the machine. Operating system is then applied however none of the drivers are then installed, causing
the deployment to halt as the network card is unable to reconnect due to having no driver.
If I go into device manager and select to install drivers by browsing the c:\ drive it finds the correct drivers and installs them so I know the driver files were copied correctly.. just not installed.
Any thoughts? Thank you in advance!
MCITP Windows 7 Enterprise Administrator

To anyone else that come across this:
I eventually found the problem as being with the unattend.xml. In the offlineServicing pass you need to include both components:
x86_Microsoft-Windows-PnpCustomizationsNonWinPE
AND
amd64_Microsoft-Windows-PnpCustomizationsNonWinPE
specifying the driver path as \Drivers to ensure the OS is looking in the c:\Drivers folder for the driver files copied in previously.
MCITP Windows 7 Enterprise Administrator

MDT inject driver for usb3.0 port on pc

I import usb 3.0 drivers to share and replaced the boot wim after I updated the share.But the usb 3.0 drivers still cannot be installed well on PC.Beyond that,everything works fine.How can I deal with it?

AS a follow up, I checked the logs offline...
It appears that MDT did find the drivers and attempted to copy down locally:
Found Device PCI\VEN_8086&DEV_8C31&REV_04 with 3rd party drivers! Count = 0 = {380f248f-1b26-450f-9697-1fa8e749210b}
Found a driver for PCI\VEN_8086&DEV_8C31&REV_04: {380f248f-1b26-450f-9697-1fa8e749210b} from \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69\oem143.inf
Validating connection to \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69
Mapping server share: \\MDT\DeploymentShare$
Already connected to server MDT as that is where this script is running from.
Copying drivers from "\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" to "V:\Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69"
About to run command: cmd.exe /c xcopy /seihycd "\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" "V:\Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" 1> NUL 2>NUL
Command has been started (process ID 500)
Return code from command = 0
Found Device PCI\VEN_8086&DEV_8C31 with 3rd party drivers! Count = 0 = {853ada7d-36f6-40e5-8719-734d3606bac1}
Found a driver for PCI\VEN_8086&DEV_8C31: {853ada7d-36f6-40e5-8719-734d3606bac1} from \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9\LxPtUSB3.inf
Validating connection to \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9
Mapping server share: \\MDT\DeploymentShare$
Already connected to server MDT as that is where this script is running from.
Copying drivers from "\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" to "V:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9"
About to run command: cmd.exe /c xcopy /seihycd "\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" "V:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" 1> NUL 2>NUL
Command has been started (process ID 832)
So the question remains, if we copied down the drivers, why didn’t MDT pick up these drivers?
IT is possible that the OS does not like these driver packages, so it did not install.
As a test, find the device in the device manager, and “update Driver Software”
Then force MDT to use the paths:
\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69
\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9
The system should use these drivers, if not, then you do not have the correct drivers, or there is some other problem, check the SetupAPI.*.log files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Can't inject drivers into boot images as they don't appear

Hello,
I have a problem trying to inject some drivers into the boot image using SCCM 2012.
I right click on the specific driver, I choose Edit > Boot image and there no boot images show up! The list is empty.
We do have 2 boot images (x32 and x64) and they are working just fine!
Does anybody have a clue what is going wrong here?
Thanks.

What version of ConfigMgr (RTM, SP1, or R2) are you using and what version are the boot images?
Each version of ConfigMgr can only directly manage (including driver injection) specific boot image versions.
RTM -> WinPE 3.1
SP1 -> WinPE 4.0
R2 -> WinPE 5.0
Thus, you are most likely trying to edit downlevel (or maybe uplevel) boot images.
Jason | http://blog.configmgrftw.com

Can I inject drivers into a .wim file on usb boot media?

Hi,
I have been working for days trying to install win7 64 bit on a HP Z620 machine and I keep getting the error “Windows failed to load because of a critical system driver is missing, or corrupt.” 0xc0000359
iastore.sys. I am fairly new to SCCM and I don't want to mess with the productive boot image so I was wondering can I inject the iastore.sys drivers into the boot wim file on a thumb drive? All I have found is examples only using config manager and modifying
the productive boot wim. Is this possible? Thank you

The Boot .wim file has nothing to do with loading Windows and the drivers needed there. That error is typically because Windows did not have the driver needed to load the Storage controller.
Are you using Auto Apply Drivers or Apply Driver Package to install the drivers into Windows for the Z620 in your task sequence?
Review below for information about loading drivers into SCCM:
http://hayesjupe.wordpress.com/sccm-osd-driver-best-practices/
http://gerryhampsoncm.blogspot.com/2013/02/sccm-2012-sp1-step-by-step-guide-part-9.html
http://www.deploymentresearch.com/Research/tabid/62/EntryId/69/The-Drivers-Saga-continues-How-to-Master-Drivers-in-ConfigMgr-2012.aspx
Daniel Ratliff | http://www.PotentEngineer.com

Back Screen when Injecting Drivers into Discovery Image

I am using windows server 2012 with ADK 8.1
The discovery wim was created from a windows 7 enterprise boot wim
The drivers I am using are windows 7 drivers for Optiplex 7010 downloaded from here
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx#WinPE
I created two driver folders one dell x32 and one dell x64.
I have tried injecting only the network drivers into 32 and 64 bit discovery images making sure only x64 drivers were used with 64 bit images and the same for 32 image only using 32 bit drivers.
I retried the above steps however I injected all available drivers available in addition to the network drivers and had the same result.
After the windows 8.1 splash screen appears and then goes away the screen remains black. What may be the cause of this?

Hi,
I wonder which driver did you injected. Boot.wim contain a widows PE image, and windows 7 code based windows PE version is winPE3.0.
So I suppose we need a winPE3.0 driver but not the one for windows 7.

Inject Drivers step fails, DISM application error

We've been imaging Surface 3 tablets for a while with SCCM 2012 R2 CU4 since CU4 came out. Recently the task sequence is failing while applying drivers. On the screen is a DISM.exe application error.
"The instruction at 0xa7356ccc referenced memory at 0x258d1a58. The Memory could not be read"
The SCCM task Sequence Error is 0xC0000005
I cannot find a DISM log, probably because it's an application crash. The SMSTS Log isn't much help either.
I've changed from apply driver package to auto-apply, refreshed Distribution Points for the driver packages and the boot images.
Our Windows 7 Task Sequences are unaffected. Seems to only be the Windows 8.1.

If you have UEFI enabled, have a look there:
http://deploymentresearch.com/Research/Post/333/Deploying-Surface-2-Pro-with-ConfigMgr-2012-SP1-CU3

SCCM 2012 Injecting Drivers in to WIM File fails

Hi All,
I am currently having issues updating the boot wim file x86 I keep getting the following
Error: Boot image to update:
• Microsoft Windows PE (x86)
Error: Actions to perform:
• Add ConfigMgr binaries
• Add custom background
• Set scratch space
• Enable Windows PE command line support
• Add drivers
Error: Failed to import the following drivers:
• Intel(R) 82945G Express Chipset Family (Microsoft Corporation - WDDM 1.0)
• Intel(R) 82579LM Gigabit Network Connection
• ASIX AX88772B USB2.0 to Fast Ethernet Adapter
• Intel(R) 82567LM Gigabit Network Connection
Optional components:
• Scripting (WinPE-Scripting)
• Startup (WinPE-SecureStartup)
• Network (WinPE-WDS-Tools)
• Scripting (WinPE-WMI)
Error: The wizard detected the following problems when updating the boot image.
• Failed to install required components into the boot image
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4630;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"NZP00041\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
I have searched Google and read up other people's issues, and there seems to be many different options to resolve this.
Tried most out there so far, going to try downloading the network driver again and test that, incase its the INF files issue.
Just wanted to see if anyone else has resolved this and what was there method.
Cheers in advance.

Hi Gerry,
I tried this and it updated the WIM file, but I still couldn't get it to capture the OS once I filled in all the details.
The look file TSMBAutorun.log says this -
<![LOG[TSMBAutoRun started]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1">
<![LOG[Unknown system architecture 0]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1">
The smsts.log says
<![LOG[Activating Welcome Page.]LOG]!><time="12:13:02.255-720" date="04-22-2014" component="OSDCaptureCD" context="" type="0" thread="5372" file="infopage.cpp:68">
<![LOG[InfoPage::OnWizardNext()]LOG]!><time="12:13:05.609-720" date="04-22-2014" component="OSDCaptureCD" context="" type="0" thread="5372" file="infopage.cpp:113">
<![LOG[Activating Finish Page.]LOG]!><time="12:13:05.609-720" date="04-22-2014" component="OSDCaptureCD" context="" type="0" thread="5372" file="finishpage.cpp:59">
<![LOG[Saving capture information in the environment.]LOG]!><time="12:13:06.264-720" date="04-22-2014" component="OSDCaptureCD" context="" type="1" thread="5372" file="wizardcontrol.cpp:499">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="12:13:06.295-720" date="04-22-2014" component="OSDCaptureCD" context="" type="1" thread="5372" file="osdcapturecd.cpp:157">
<![LOG[Process completed with exit code 0]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="commandline.cpp:1123">
<![LOG[Succeeded loading resource DLL 'E:\SMS\bin\i386\00000409\TSRES.DLL']LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="util.cpp:963">
<![LOG[AllocateCDRoms=1]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="tsmediawizardcontrol.cpp:2265">
<![LOG[AllocateCDRoms is set; will not start TSManager]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="3" thread="5132" file="tsmediawizardcontrol.cpp:2269">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="0" thread="5132" file="commandline.cpp:228">
<![LOG[Set command line: "E:\SMS\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="0" thread="5132"
file="commandline.cpp:731">
<![LOG[Executing command line: "E:\SMS\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132"
file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 4284 ]==========]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:330">
<![LOG[Command line: "E:\SMS\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="0" thread="4276" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="utils.cpp:2320">
<![LOG[ExecuteSelectedTaskSequence(fpCallbackProc,pv,hCancelEvent), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1527)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap"
context="" type="0" thread="5132" file="tsmediawizardcontrol.cpp:1527">
<![LOG[ResolveAndExecuteSelectedTaskSequence( 0, 0, 0 ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2421)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap"
context="" type="0" thread="5132" file="tsmediawizardcontrol.cpp:2421">
<![LOG[Unattended(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2762)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context=""
type="0" thread="5132" file="tsmediawizardcontrol.cpp:2762">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, false ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,910)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap"
context="" type="0" thread="5132" file="tsmbootstrap.cpp:910">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183)]LOG]!><time="12:13:06.405-720" date="04-22-2014"
component="TSMBootstrap" context="" type="0" thread="5132" file="tsmbootstrap.cpp:1183">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="tsmbootstrap.cpp:1195">
<![LOG[Finalizing logging from process 5128]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="tslogging.cpp:1741">
<![LOG[Successfully finalized logs to SMS client log directory from C:\Users\NCR\AppData\Local\Temp]LOG]!><time="12:13:06.498-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132"
file="tslogging.cpp:1542">

MDT 2010: How to change WinPE drivers?

We have boot images that currently work for all of our systems and is used for PXE booting with a WDS server, but I think we have lots of extra drivers in the PE image because the boot image size is quite large and it seems to spend a long time injecting
drivers during the PE portion before the OS is installed.
Which drivers other than than NIC drivers are needed in the boot image?
How can we change the boot image so that it has only the minimum necessary drivers for each computer model?

Network and storage controller drivers are the essential ones and that is included by default in the boot image. However there are certain types of these drivers you do not want/need in the boot image and that is drivers for wireless network cards and for
instance all kinds of memory card reader drivers.
One of way of gaining full control over the drivers in the boot image is to create a WinPE structure in the driver part of Deployment Workbench and then use Selection profiles (see the settings on the deployment share) to make sure that only the drivers
from the selection profile is added to the WinPE/Boot image.
Blogging about Windows for IT pros at
www.theexperienceblog.com

MDT Config UEFI Specific disk and partition?

Installing Win8.1 with MDT2013 on UEFI enabled machines everything seems to be ok.. Until... Injecting drivers. The deployment cannot proceed because of destination disk. Sounds obvious because Uefi makes multiple partitions unlike non-uefi that can be installed
on the first partition.
I've created an extra step to the "Format and partition disk" and named it "Format and Partition Disk - UEFI". In this step I've set an option "Task sequence variable IsUEFI equals True". So when it is "True" the step
will format the drive in GPT (as is required for UEFI boot). This seems to work good. I see in the installation the step "Format and Partition Disk - UEFI" when it's a uefi machine, and the original step if it is a non uefi machine. Obviously the
original step will have also an option "Task sequence variable IsUEFI equals False".
The problem comes when we get to the step "Install Operating System". Here I made the same change like I did above. (added extra step with extra option:
The original step "Install Operating System" will have install location: "Specific disk and partition"
Disk 0 Partition 1.
The added step will have install location "Specific disk and partition"
Disk 0 Partition 3. (Because UEFI has multiple partitions)
For some reason the deployment will accept the step "Format and Partition Disk - UEFI" but in the install step it will take the "Install Operating System - Legacy" (so it will try to install to disk 0 partition 1 as I see in BCD log).
Is there any reason that the same condition works at the format step and not at the install step?
We choose the option install to "Specific disk and partition" because of problem when have the location set at "logical drive letter stored in a variable" (problem described:
link)

Solution in my case was going for the "logical drive letter stored in a variable" instead of "Specific disk and partition".
Note when applying this: must keep using "OSDisk" variable or it will throw errors (problem described in
this link)
So I deleted the "UEFI" steps, and renamed the "Install Operating System - Legacy" to before. Removed the query for the IsUEFI variable. MDT will automatic install to MBR or GPT based on device.

Using MDT to re-join computers to a domain after a re-image

Since 2010 we have been using WDS to build, capture and deploy our image across our organisation (A High School) which has worked well enough. While WDS can do all this the build and capture is a little clunky and relies on you to manually installing all
programmes and then mounting the WIM file and inject the drivers so I have moved us onto MDT for the build and capture before importing the finished WIM file into WDS for deployment.
This has worked much better as MDT makes it much quicker to get an image up and going (programme silent installs, testing is much quicker etc) and drive management is as simple as telling MDT to put ALL the drivers you want into the image but I have been
reading that you should link MDT and WDS together.
I followed the instruction and imported the LiteTouchPE wim file into WDS and we are able to PXE boot right into MDT and either make a new image or capture the one we are working on but I am trying to automate the deployment so it is more like what we have
when just using WDS for deployment. Because I want to retain the ability to use MDT to make a new image I cannot customise the customesettings.ini file too much and instead I am relying on MDT task sequences for must of the customisations.
Currently all our systems are pre-staged into WDS (I think it is actually Active Directory at the end of the day but you use wdsutil to pre-stage them) so when we boot into PXE WDS deploys and configures the machines using WDSClientUnattend and ImageUnattend
XML file so that once the deployment is finished it is sitting at the logon screen waiting for the user to login already joined to the domain and our wireless network.
I am having trouble trying to achieve this same result using our WDS + MDT combo with the main sticking point being trying to re-join the computer back to the domain (we re-image machines constantly so re-join back to the domain is a must). I wrote/found
a PowerShell script that does the domain join but because an account already exists (all our machines are pre-staged under their service tag and GUID) it throws an error about their already being an account with that name (the computer still appear to join
the domain and I can logon using my domain account). Because of this error MDT borks the deployment and doesn't finish up and complains about deployment being in progress etc.
Is using WDS to boot the LiteTouchPE and then deploying through MDT the best way or are we better off going back to using MDT to do the build and capture and then using WDS and it's pre-staging to do the deploy? I really like that with MDT I can have a little
more control over driver deployment (recently had a problem where we got a new laptop and injecting the new drivers into the WIM broke the entire image for all our machines except the new one) and software at the time of the re-image (I cannot install the
Lenovo hotkey software in a virtual machine because it does a hardware check and fails to install so either the entire image needs to be made on a Lenovo or the software doesn't get installed).
I am currently making a Windows 8.1.1 x64 Enterprise SOE/MOE/whatever you would like to call it using MDT 2013 with WDS running on Windows Server 2012 R2 x64.

Hello,
It is better to use so-called "thin" images. These contain only the operating system (in a facility and captures vm). Subsequently pilots and soft will be deployed by the bais of MTD.
For drivers I recommend you to use selection profiles. Moreover it is necessary to put a condition in step "Inject Drivers". Condition Type: Variable called MODEL, variable value Latitude E6430 (change the value to the desired model). It is necessary
to add more step Inject Drivers that type of position.
Application level, you import the different applications in MDT allowing you to select only the desired wizard when applications. If you want to automate this step you will need to indicate statically in the task sequence to install applications, this will
require the creation of several task sequence.
Best Regards
Well I am well aware the Microsoft recommends a thin image it is simply not practical in a School environment where Students change in and our of subjects and where the combination of subject specific software is nearly infinite the overhead is too great
(maybe if we used something like SCCM where we could deploy applications based on OU or group membership).
All your other points aside my problem/issue/question which appears to have been lost is, how do I rejoin a computer to the domain using MDT? We re-image laptops constantly and using WDS they rejoin with no problems but using MDT an error is thrown because
the account already exists. In WDS we have all our machines pre-staged so is there an MDT equivalent that will let me re-image a laptop and have it re-join the domain under the same account without throwing and error.

MDT - iaStorA.sys error when starting up, Status: 0xc0000098, multiple errors updating deployment share

I recently had rearranged our imaging by creating selection profiles for each computer model and then creating a task sequence for each model so that it looks for a model and only injects the drivers for that model. Everything had been working great
and then we got a new batch of Dell Latitude E6440's in. I checked over the machine and just wanted to make sure nothing changed so i grabbed a couple drivers off of it and uploaded them into mdt under that model. I went to update the deployment
share and started to get a whole host of Error: 2, no driver packages were found on the specified path. Verify the driver .INF file are in the specific location and try the command again. It points to the dism log and exit code is =2 then it says DISM
/Add-Driver failed, rc = 2 and lists all the drivers that had failed. It was a whole bunch for both the x86 and x64. Although i didnt add all these drivers. I only messed with the wifi and nic driver and it was only two files. I ran
through imaging and there were no issues it rebooted windows is about to start and it goes to the black screen with the iaStorA.sys message. I checked everything, i looked over all the chipset drivers i knew i imported and those were still there. I
downloaded the WINPE stuff from dell and found the driver and made sure to import everything in that folder and it skipped it as it said it was still there. I wanted to make sure it wasnt the whole mdt server so i imaged a different computer model all
together and that worked. So i deleted every driver out for this model made sure to delete it if it was in other places. I am now in the process of only including very specific drivers ie just the nic and display and audio and see if it will get
passed first bootup. But what would make it go from working every time for about 3 weeks now to all of a sudden not injecting drivers through updating the deployment share and causing a problem for just this image. I am including the dism log and
it is lengthy. The drivers are all sitting all sorted out in their respected folders on the desktop of the share. This has never been an issue before. here is the log
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\iaAHCI_8.9.8.1005_157DE4AE7437DC1A46C7E0E4B3294E513CB47D80\iaAHCI.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc iaAHCI.inf 8.9.8.1005 (2)
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (14)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\ibexahci_7.0.0.1013_CDE6EABDFCC22A23476F9CB4EA115D63FF4A6DBE\ibexahci.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (15)
Injected driver Intel hdc ibexid2.inf 9.1.1.1013 (6)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
There were about 2,000 plus more lines of the same stuff.
For future purposes where should the driver be when import them into mdt and do i need to then keep them? I am still learning all this stuff after taking over the roll in October of 2014. Any help would be greatly appreciated.

Hi KheenanHalvorson,
According to the log ,it seems that there is something missing in the driver package .
According to your description ,I assumed that you have configured the whole process correctly.
To deploy the drivers in this way the driver package should include two files an INF and SYS file .We may need to replace the driver package with another one including the INF file .
Here is a link for reference:
How to manage Out-of-Box Drivers with the use of Model Specific Driver Groups in Microsoft Deployment Toolkit 2012 Update 1
http://blogs.technet.com/b/askcore/archive/2013/05/09/how-to-manage-out-of-box-drivers-with-the-use-of-model-specific-driver-groups-in-microsoft-deployment-toolkit-2012-update-1.aspx
"One thing to note about Driver injections is that the driver must have an INF and SYS file in order for us to install the driver this way. If a driver installs via an EXE and there is no way to extract that driver to reveal the actual INF
and SYS file, then you would be forced to add that driver EXE package as an application and install it as an application. "
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

MDT - Injecting Drivers

Similar Messages

Maybe you are looking for