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]> 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]> 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 >> >> >> >> >> > >
