Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all articles
Browse latest Browse all 11297

MDT 2010 injects drivers successfully but Windows 7 x64 SP1 doesn't install them

$
0
0

Hi gurus, hopefully someone can shed some light on this issue we're having:

Essentially, MDT is able to recognise the machine being deployed and injects the drivers into C:\Drivers, but Windows does not appear to do anything with them.

We use a combination of Altiris and MDT 2010 (don't ask) to deploy our hardware independent SOE. Currently the XP image works fine and I'm trying to get a Win7 x64 SP1 build off the ground.

I've used an unattend.xml to deploy Win7 from the DVD, then jumped into audit mode to make some user interface changes and finally sysprepped it with the /generalize and /oobe switches. No special drivers are set up at this stage as we're using it as a generic image.

Following that, I've taken a WIM of the drive and inserted it into our deployment process (boot using Altiris PXE into WinPE, deploy the WIM using imagex then call a task in MDT which does an inject drivers task using a limited selection profile that only contains Windows 7 drivers). Because we're not using MDT to deploy the image end to end, I've had to set a task sequence variable 'ImageBuild' to 6 specifically so that ZTIDrivers.wsf follows its Windows Vista/7 tree rather than defaulting to XP mode.

The image deploys, unpacks and installs normally on our test machines, but never seems to install the drivers that MDT drops into C:\Drivers, only the stock ones. If I go into Device Manager, select the unknown devices and tell it to scan C:\Drivers, it then installs correctly, but that's a very manual process we'd like to avoid on every single machine. I've gone through a number of posts talking about modifying the unattend.xml to set the DriverPaths variable in Microsoft-Windows-PnpCustomizationsNonWinPE to C:\Drivers (even put in C:\Drivers\ just in case), checking there's no existing C:\Drivers in the WIM, but it just seems to not realise that it has the drivers it needs.I've taken a brief look through the setupact.log files but it's a lot of junk to me and mainly seems to be that it can't find the drivers it wants.

Has anyone come across this before or more importantly does anyone know how to fix this?


Viewing all articles
Browse latest Browse all 11297

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>