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