OSD Issue with drivers installation
Hi, taking lot of time to install Drivers, image installation is going intime, taking 2 hours for drivers installation, can anyone please help. Regards, KM
May 17th, 2012 5:26am

Hi, How are you installing thre drivers? how large is the driver package? Need a little more information to be able to help you.. regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2012 5:32am

Defintiely a lot more info needed. In addition to what Jorgen asked: - What kind of driver task and methodology are you using? - How are you delivering the task seqeunce? - Have you reviewed smsts.log?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 17th, 2012 8:36am

Defintiely a lot more info needed. In addition to what Jorgen asked: - What kind of driver task and methodology are you using? - How are you delivering the task seqeunce? - Have you reviewed smsts.log?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2012 8:50am

in task sequence i have seleted auto apply drivers and selected install only the best matched compatible drivers. for other site it is working without any issue. drivers package size is around 7 Gb.
May 17th, 2012 9:46am

A 7GB driver package is your problem. You should include ONLY the specific drivers you need for your hardware models. Do not import every driver for all Windows versions. You'll end up with way to may drivers making in unmanageable, not to mention a huge 7Gb file. I would start by creating a brand new driver package with only the specific drivers you need for your OS version and hardware models.
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2012 6:14pm

A 7GB driver package is your problem. You should include ONLY the specific drivers you need for your hardware models. Do not import every driver for all Windows versions. You'll end up with way to may drivers making in unmanageable, not to mention a huge 7Gb file. I would start by creating a brand new driver package with only the specific drivers you need for your OS version and hardware models. Why? That's the whole point of using auto apply. It picks out which drivers are applicable based upon a PNP Scan and does not download the entire package. Without additional info about the infrastructure in use and the smsts.log, not much more can be said.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
June 21st, 2012 6:43pm

I agree auto apply will pick the best driver, but as a personal preference I try to keep my driver packages as simple as possible with just the LAN and storage drivers. Then install the remaining drivers as applications in the task sequence. Even when using BITS throttling, do you really want to refresh the DP's with a 7gb file everytime you add/update a driver? Considering that the problem is occuring at only one of the sites, it's possible there was an issue during package replicaiton.
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2012 7:16pm

When files are added to or updated in a package, including a driver package, only the new or changed files are copied to the DP. Also, DPs do not use BITS for content copy -- only BDPs do. Installing drivers using the manufacturers installation packages is acceptable, but can add considerable bulk to the deployed system, time to the deployment, and unwanted utilities. All of the top tier vendors provide methods to download drivers packs that are importable into ConfigMgr for use with built in driver installation tasks. The only time it is necessary or recommended to use the installation packages is when you can't find or extract the drivers in their raw form or Windows simply refuses to install them in any other way. What many folks actually do is use these apcks provided by the vendors and Apply Driver Package tasks -- one for each model. Then each of these tasks is conditionally executed based on a WMI query that matches the hardware model. This is done because PNP matching is a "black" art and better resuls are achieved by simply forcing every driver for a model to the system based soley on model id. (@Chad -- Sorry, not trying to be argumentative or mean or anything or Mr. know-it-all -- all though I have been accused of that -- just trying to be be technically correct.)Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
June 21st, 2012 8:01pm

I have over 30gb of drivers set to auto apply, the packages are broken down for each model though - roughly 1gb for each package. Wont OSD TS download the whole driver package not just the individual drivers when it finds the suitable driver in a package? Maybe you need to repackage your drivers based on model but still use the auto apply drivers so it doesnt end up downloading the whole 7gb file you have with every driver in it. Mine runs pretty quick over the lan from the dp, 3 mins max to apply all drivers in my osd ts. That is whith over 40 models including dell, lenovo and hp drivers. The only time I have used WMI query in the ts is for model specific drivers (bad drivers) like bluetooth, tpm and mass storage drivers. As jason also said "When files are added to or updated in a package, including a driver package,only the new or changed files are copied to the DP. Also, DPs do not use BITS for content copy -- only BDPs do." I have ran into problems with only new or changed files set on these packages - sometimes its better to strip it all out and start again.
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2012 10:01am

this was resloved , this is issue with DP server and MP
July 19th, 2012 9:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics