![]() Since many models have the same base hardware, the drivers are duplicated in each model subfolder. The one downside to our method is driver duplication. We've never had a single issue with USB3 drivers, which seem to plague everyone else. We currently support 24 different models, both Dell and HP, laptops and desktops, and only two require any OEMSetup customization (both older models, both bluetooth drivers). Add custom unattended installation command lines for drivers that didn't install automatically (rare).Perform initial deployment on the first new computer and verify that all drivers installed correctly.Copy in a blank OEMSetup.cmd to this folder.Download the driver pack cab from Dell or HP and extract the 64bit contents to this folder (we only support 64bit Windows 7).Determine the full productname (model) for the new computer and create a folder named this in our driver repository.So our process for adding a new computer model is: We also add one batch file to the driver folder for each model (OEMSetup.cmd) which is usually blank but in the few instances we find drivers that don't auto-install properly during mini-setup we put the manual unattended installation command lines in there and fire it off as a task in the deploy job after booting to production. Mini-setup then installs all the drivers during the boot to production. The devicepath is in our custom answer file. A batch script copies them into place after querying the productname via wmic. We have a driver repository on each site server with a folder for each model containing a set of drivers extracted from the Dell or HP driver pack. We put the drivers into place in winpe after image deployment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |