Vista driver injection (manual HII)
Updated: 21 May 2010 | 3 comments
Hi there.
I have XP routines for copying machine-specific drivers to a newly imaged machine. I use the OEMDriverPath to point to driver location, so it finds the drivers in PnP phase on first boot.
Can I do the same when imaging Vista?
Is there a similar function to OEMDriverPath that will find and install the drivers during Plug and Play?
Thanks a lot for any feedback!
discussion Filed Under:
Comments
I'm not sure but!
I'm not sure if it helps, but why not try something like given in this article:
https://www-secure.symantec.com/community/article/...
I hope it helps you.
Regards
Erik
www.DinamiQs.com
Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)
*************************************************************
If your issue has been solved, Please mark it as solved
***********
Injecting/installing Vista drivers?
Thanks for your answer!
I was hoping to achieve this manually, without installing the HII Tools. The article refers to a number of exe's that I presume comes with the HII Tools.
Aren't there anyone out there who are deploying Vista images?
How do you inject/install drivers?
Do you install them in automation OS or at first boot?
pkgmgr or auditmode
You have 2 options to accomplish manual driver injection for Vista.
1st. You can use your unattend.xml to trigger audit mode which will allow the installation of drivers from a specific location (local or remote). There are a couple of disadvantages to this method: 1. An extra reboot is required. 2. You need to supply the admin user/password in the unattend.xml file for the login during audit mode process.
A good thing about Vista audit mode is that you are able to supply a single folder path and Vista will search for INFs 2 levels below that folder. This greatly reduces the effort of setting up the old oempnpdriverspath statement. The next good thing is that you can supply a UNC path with user/password in the unattend.xml which avoids the need to use firm to copy drivers. There are some examples of using a generic DS job to do this in KB 37972.
2nd Option - Use pkgmgr.exe to inject drivers into the system in WinPE prior to initial boot. There are some examples of this in the kb document 38612.
DS 6.9SP1 is the best choice for all of these methods. If you are using DS 6.8 you will need to make some changes to the WinPE bootfiles to achive this.
Good Luck.
Pete
Would you like to reply?
Login or Register to post your comment.