Driver deployment during OSD has remained mostly unchanged since the days of ConfigMgr 2007, despite some of the awesome new features that have appeared since. For many, it can be a real bugbear to have to cater for an ever-expanding line of models to support.
Traditionally, the process of driver package processing during OSD involves creating a driver package and associating a WMI query to match the model and apply the driver package where a match is found. That is of course for those admins who stay away from the dreaded “use at your own risk” method that is Auto Apply Drivers.
In the example below you can see how the traditional WMI filtering method is applied for a Dell Latitude E5470:
WMI Query SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%Latitude E5470%”
Modern Driver Management
Back in March of 2017, Nickolaj Andersen and I posted a method which attempted to address this issue. We called the process “Modern Driver Management” or MDM for short, not to be confused with Mobile Device Management.
The process used a web service as a secure method to query various objects in ConfigMgr and leverage the returned data with a PowerShell script. The initial three-step method was based on the model name of the machine which is retrieved from WMI in PowerShell. An example of WMI query can be seen below: