Quick background: We’ve always captured our images by running sysprep in audit mode without generalization. Then, we decided it would be easier to create image files on VMs instead of physical boxes, which lead us down a rabbit hole where we discovered that in order to capture from a VM we needed to sysprep for OOBE WITH generalization.
Now, it’s my understanding that when you lay down an image captured like that, it’s going to come up and process the “Specialize” and “oobesystem” passes of an unattend file but not the auditsystem or audituser passes of an unattend file. Unfortunately, previously, we were creating some local accounts and setting some passwords during the auditsystem pass, which is no longer taking place.
So I set out to create a new unattend file that would be more compatible with our new sysprepping approach. Then I remember that as part of the HII process, we tell Windows to look at C:\Windows\LDDriverstore for drivers during the AuditSystem pass of the unattend file….and you cannot use the driverpaths component during the Specialize or OOBESystem passes.
So to get to the point: is it still necessary to tell windows a driverpath in the unattend file? If so…does that mean that in order for HII to fully function we can only capture images that have been sysprepped for audit mode WITHOUT generalization?
For reference here's the section in our old unattend file where we always told windows to go look for any drivers it may need (which is where HII downloads drivers to while still in WinPE):
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="XXXXXX" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<PathAndCredentials wcm:action="add" wcm:keyValue="1">