Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Driver Deployment - What am I missing?

Created: 15 Nov 2013 • Updated: 21 Nov 2013 | 2 comments
This issue has been solved. See solution.

I am sure I am missing something, probably something obvious.

I am using Altiris Deployment Server 6.9 and Altrinsic HIIS to deploy Windows 7 Enterprise 64 bit. Image deployment goes fine and HIIS correctly copies the drivers to the target machine. The process also updates my unattend.xml to point to the correct driver location, that section is shown below. The problem is those drivers do not seem to be applied. A point of evidence is the display driver stays at the Standard VGA instead of the ATI Radeon which is in the machine. Is there something I need to change in my xml file? Does Windows 7 Sysprep "prefer" the drivers which are embedded in the OS to those added on which match specific hardware?

I am tried a second, different model, PC with the same lack of drivers being applied.

Here is the unattend.xml section, the rest of the file performs as I need it to.

<settings pass="auditSystem">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>C:\Drv\</Path>
</PathAndCredentials>
</DriverPaths>
</component>
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>C:\Drv\</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
<settings pass="windowsPE">
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>C:\Drv\</Path>
</PathAndCredentials>
</DriverPaths>
</component>
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>C:\Drv\</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>

Thanks in advance!

Operating Systems:

Comments 2 CommentsJump to latest comment

BBC's picture

If it is all about the display drivers, have you checked / confirmed that there are no dependencies missing for the drivers to be installed? I know for a fact that several display drivers require either VRC++ or .NET to be installed.

-BBC

pshore's picture

I also opened a ticket with Altrinsic which is where I got my answer.

HIIS expects WIndows 7 to be in audit mode, not generalize/oobe, which is why injection did not work.  The support folks at Altrinisic, who were great as always, were able to provide me with a VBScript that uses dpinst.exe (from the Windows Driver Framework) to install the drivers during sysprep.  Additionally, they provided the XML I needed for the unattend.xml to call the vbscript.

SOLUTION