We create driver packages, but we do not do the WMI targeting anymore. We have a script reincarnated from the MDT days that would return a modelalias variable. When the model is found it sets the aforementioned variable to a driver category like below SetModelAlias = "DriverCategories:f6438f45-5aaf-4c35-99cf-07a4c6e51ada"
Then it sets the OSD variable in customsettings.ini UserExit=ModelAliasExit.vbs OSDAutoApplyDriverCategoryList=#SetModelAlias()# Then it uses the auto apply drivers limited to the set driver category. Using this we can use the packaged drivers cabs or packs downloaded from HP and Dell without having issues with an incorrect driver being installed or at least less often. Another reason for doing this was to decrease the amount of policies checked before and after a task sequence is selected. Since each driver package policy is downloaded it could take a while to even get the initial welcome screen. Even having a secondary at the site the policy request go to the primary management point. Writing a text file into each driver folder is interesting. From: [email protected] [mailto:[email protected]] On Behalf Of Roger Truss Sent: Saturday, August 27, 2016 8:25 AM To: [email protected] Subject: Re: [MDT-OSD] Driver in OSD We use driver packages and target using wmi. I create a text file for every release via power shell script and that file is created in every folder for a given model. This keeps the system from sharing drivers so I can retire older ones properly. Works pretty slick. On Thu, Aug 25, 2016, 11:55 AM Daniel Davila <[email protected]<mailto:[email protected]>> wrote: Greg, How are you applying drivers? Ideally I set them up as packages and have models apply them based on WMI query from that package. This is easy with vendors that release one pack per model, but more difficult with other vendors that support multiple models per pack. I know HP does multi-model packs and has a list of models that support each, at 100+ packs in your env it's tedious but you'd need to cross-reference and decide from there. It gets dicey if you're doing PNP discovery for unknown models (let SCCM choose best driver via PNP query from all available drivers). -- DD On Fri, Aug 12, 2016 at 11:25 AM, Augustine, Greg <[email protected]<mailto:[email protected]>> wrote: How does everyone handle retiring of drivers and driver packages? We currently support 100+ models and when we want to retire a driver package we have to make sure that the package is not the source of the driver if other packages are using it. Greg Augustine Office of Administration Information Technology Services Division – State Data Center (573)-751-4714<tel:%28573%29-751-4714>
