Ended up manually creating our own driver folder with the files windows was requesting taken out of the original install directory. Most unusual but its now working fine.
Main Topics
Browse All TopicsWe have just received new hardware into our environment which must have the drivers loaded onto our software deployment tool (Not SMS!)
The drivers have been added to the 'cache' and the PC builds as per usual but the VGA adapter isnt being recognised.
Our deployment tool has an 8 DOT 3 limit. So you can only have 12345678.DLL.
Unfortunately some drivers recently released by intel contain too many characters so the files were having their names changed and subsequently the driver install was failing.
I've amended the INF to reflect the new file names but during the automated win PXE boot and subsequent windows setup & configuration the file is still not being installed.
Now here lies the giveaway! ... If I manually update the drivers using the Have Disk method and point the machine to the exact INF file within the local copy of the driver cache it works fine (and recognises ive changed the file name!)
If I use the other method of specify a location to search within a folder for drivers, it finds 3 sets of drivers and subsequently fails.
Now my question is, What type of file could be causing this? Ive amended the only INF file in the folder but there must be something else windows is seeing which makes it things that there are more drivers available within that folder.
We cant simply use the exe install as a workaround, This image must be hardware independant so resolving this is critical.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: Netman66Posted on 2009-05-23 at 07:44:56ID: 24457989
It may be the CAT file that's causing it. Modding the INF would invalidate the driver signing (CAT) file. Therefore, if you have Driver Signing set to Warn, then an Automated install would fail.
If it's set to Silently Succeed, I imagine it would work.
Other than that, you could use the DevicePath registry entry to point to that specific driver to get around the autodetect method.