Greetings,
I have inherited an MDT system that uses the DriverPathsxxx for driver management. The inject drivers step specifies to inject everything for all models.
We are working on deploying a new model and would like to do this in a more controlled manner. So I have some basic questions...
How do we know what drivers are required? I know that pnpenum.exe extracts the pnpids and then goes looking for a driver but does pnpenum create a logfile or is there any way we can capture what pnpenum detects? I want to use that to match up with inf files so I know what drivers are needed.
Some blogs recommend using a neat structure in out-of-box drivers and I like that approach. Firstly, Im a bit confused about out-of-box drivers as some blogs seem to suggest that drivers here can only be used in the boot wim and not the OS itself? Also, if I have the same driver used for different models, does it duplicate the disk space used within REMINST to store multiple copies? (We are very short of disk space sadly and its a big issue for us).
It appears that if a supplied driver does not use the standard inf approach but can only get installed with an exe, then we have to use an application.
My last task is a beauty. We are a huge organisation and we have no documentation on the various models that are out there and therefore no idea what drivers currently in MDT are no longer required. I have to write a script that contacts hundreds of WDS servers and extracts all the bdd.log files and summarises what makes and models have been installed and when. That will be fun!
Thanks
David Z