Home
%3CLINGO-SUB%20id%3D%22lingo-sub-321789%22%20slang%3D%22en-US%22%3EBDD%202007%20-%20driver%20injection.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321789%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Apr%2027%2C%202007%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EEver%20wondered%20how%20BDD%202007%20driver%20injection%20actually%20works%3F%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EThere%20are%20actually%26nbsp%3Bthree%26nbsp%3Bpossibilities%20-%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Vista%20Lite%20Touch%20%3CBR%20%2F%3E%20-ZTIDrivers%20calls%20Pnpenum%20to%20enumerate%20the%20hardware%20on%20the%20imaging%20system.%26nbsp%3B%20This%20data%20is%20stored%20in%26nbsp%3B%20Pnpenum.xml.%20%3CBR%20%2F%3E%20-ZTIDrivers%20script%20compares%20list%20of%20hardware%20in%20Pnpenum.xml%20against%20available%20drives%20stored%20in%20Drivers.XML%20%3CBR%20%2F%3E%20-ZTIDrivers%26nbsp%3Bcopies%20matching%20drivers%20to%20c%3A%5CDrivers.%20%3CBR%20%2F%3E%20-Vista%20SETUP%20injects%20drivers%20into%20the%20Vista%20driver%20store%20(as%20a%20result%20of%20the%20offline%20servicing%20entry%20for%20c%3A%5Cdrivers%20in%20the%20unattend.xml)%20%3CBR%20%2F%3E%20-Vista%20PnP%20injects%20the%20drivers%20from%20the%20Vista%20driver%20store%3B%20c%3A%5Cdrivers%20is%20no%20longer%20used%20and%20can%20be%20deleted.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EVista%20Zero%20Touch%3A%20%3CBR%20%2F%3E%20-ZTIDrivers%20calls%20Pnpenum%20to%20enumerate%20the%20hardware%20on%20the%20imaging%20system.%26nbsp%3B%20This%20data%20is%20stored%20in%26nbsp%3B%20Pnpenum.xml.%20%3CBR%20%2F%3E%20-ZTIDrivers%20script%20compares%20list%20of%20hardware%20in%20Pnpenum.xml%20against%20available%20drives%20stored%20in%20Drivers.XML%20-ZTIDrivers%20copies%20matching%20drivers%20to%20c%3A%5CDrivers%20(bare%20metal)%20ro%20x%3A%5CDrivers%20(refresh).%20%3CBR%20%2F%3E%20-ZTIPatches%20script%20calls%20PKGMGR%20to%20inject%20the%20drivers%20into%20the%20Vista%20driver%20store%20(as%20a%20result%20of%20offline%20servicing%20entries%20for%20c%3A%5CDrives%20and%20x%3A%5CDrivers%20in%20the%20unattend.xml)%20%3CBR%20%2F%3E%20-Vista%20PnP%20injects%20drivers%20from%20the%20Vista%20drivers%20store%3B%20c%3A%5Cdrivers%20is%20no%20longer%20used%20and%20can%20be%20deleted.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20XP%20Lite%20Touch%20and%20Zero%20Touch%20%3CBR%20%2F%3E%20-ZTIDrivers%20calls%20Pnpenum%20to%20enumerate%20the%20hardware%20on%20the%20imaging%20system.%26nbsp%3B%20This%20data%20is%20stored%20in%26nbsp%3B%20Pnpenum.xml.%20%3CBR%20%2F%3E%20-ZTIDrivers%20script%20compares%20list%20of%20hardware%20in%20Pnpenum.xml%20against%20available%20drives%20stored%20in%20Drivers.XML%20%3CBR%20%2F%3E%20-ZTIDrivers%20copies%20matching%20drivers%20to%20c%3A%5CDrivers%20(bare%20metal)%20ro%20x%3A%5CDrivers%20(refresh).%20%3CBR%20%2F%3E%20-ZTIDrivers%20updates%20unattend.txt%20(unattended%20install%20only)%2C%20sysprep.inf%20(all%20scenarios)%2C%20and%20the%20applied%20OSDevicePath%20registry%20entry%20(sysprepped%20image%20deployment)%20to%20add%20each%20new%20driver%20directory%20copied.%20%3CBR%20%2F%3E%20-XP%20Pnp%20injects%20drivers%20from%20the%20c%3A%5Cdrivers%20directory%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-321789%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Apr%2027%2C%202007%20Ever%20wondered%20how%20BDD%202007%20driver%20injection%20actually%20works%3F%26nbsp%3B%26nbsp%3BThere%20are%20actually%26nbsp%3Bthree%26nbsp%3Bpossibilities%20-%26nbsp%3BVista%20Lite%20Touch-ZTIDrivers%20calls%20Pnpenum%20to%20enumerate%20the%20hardware%20on%20the%20imaging%20system.%3C%2FLINGO-TEASER%3E
Microsoft
First published on MSDN on Apr 27, 2007

Ever wondered how BDD 2007 driver injection actually works?


There are actually three possibilities -

Vista Lite Touch
-ZTIDrivers calls Pnpenum to enumerate the hardware on the imaging system.  This data is stored in  Pnpenum.xml.
-ZTIDrivers script compares list of hardware in Pnpenum.xml against available drives stored in Drivers.XML
-ZTIDrivers copies matching drivers to c:\Drivers.
-Vista SETUP injects drivers into the Vista driver store (as a result of the offline servicing entry for c:\drivers in the unattend.xml)
-Vista PnP injects the drivers from the Vista driver store; c:\drivers is no longer used and can be deleted.


Vista Zero Touch:
-ZTIDrivers calls Pnpenum to enumerate the hardware on the imaging system.  This data is stored in  Pnpenum.xml.
-ZTIDrivers script compares list of hardware in Pnpenum.xml against available drives stored in Drivers.XML
-ZTIDrivers copies matching drivers to c:\Drivers (bare metal) ro x:\Drivers (refresh).
-ZTIPatches script calls PKGMGR to inject the drivers into the Vista driver store (as a result of offline servicing entries for c:\Drives and x:\Drivers in the unattend.xml)
-Vista PnP injects drivers from the Vista drivers store; c:\drivers is no longer used and can be deleted.

XP Lite Touch and Zero Touch
-ZTIDrivers calls Pnpenum to enumerate the hardware on the imaging system.  This data is stored in  Pnpenum.xml.
-ZTIDrivers script compares list of hardware in Pnpenum.xml against available drives stored in Drivers.XML
-ZTIDrivers copies matching drivers to c:\Drivers (bare metal) ro x:\Drivers (refresh).
-ZTIDrivers updates unattend.txt (unattended install only), sysprep.inf (all scenarios), and the applied OSDevicePath registry entry (sysprepped image deployment) to add each new driver directory copied.
-XP Pnp injects drivers from the c:\drivers directory