Yeah. I didn’t realize choakem had resurrected a 7 month old thread. Thanks for updating the WIKI though!

[quote=“Nate Baker, post: 24539, member: 23116”]I know this thread is old, but wondering if anyone else has had success with this?

Doug, your method sounds like it would work great, but I’m wondering if that would work with critical drivers such as storage and network? Or do you need to have the storage and network drivers in the image already, and install the rest of the drivers using that method? It seems like since that oobeSystem pass is the last pass, it would need the storage and network drivers by that point.

Thanks,
Nate[/quote]

Sorry for the late reply. You are correct, Nate. I inject mass storage and LAN drivers into my base image for all the models of computers we deal with here before sysprep.

as i said before. i am using 2 xml files “audit.xml and unattend.xml” and both are in “C:\windows \system32\sysprep” and i am using 2 patch files audit.bat where i have this command “C:\Windows\System32\sysprep\sysprep.exe /audit /quit /unattend:C:\Windows\System32\sysprep\audit.xml” after running the audit.bat the sysprep will import all the drivers into the system and then boot windows, at that point it will show you the GUI of sysprep just close it. i run the other phase of sysprep oobe.bat “C:\Windows\System32\sysprep\sysprep.exe /generalize /quit /unattend:C:\Windows\System32\sysprep\unattend.xml”
and here everything is getting done for deployment. why would you put your drivers into WinPE ??? you should put them into the Audit phase “look at my audit.xml” in the previous post. anyway it depends on your deployment method. this process is working for me and may be there are other ways out there but i couldnt find any better than this. i attached a copy of my audit.xml just try it and see if it works for you. as i said before just change the path to the drivers and the architecture.

[url=“/_imported_xf_attachments/0/30_audit.zip?:”]audit.zip[/url]