Utilizing model variable to control what drivers are installed

As mentioned earlier, while using a default MDT task sequence, the Inject Drivers task sequence step will search your entire Out-of-Box drivers repository to find a matching driver. If you only have a few hardware models, and all models are from the same manufacturer, then this could very well suit your needs without problem; but let's consider the following scenario.

Let's say you have a Dell model that has a rebranded Broadcom Network Adapter. You also have an HP model that has a rebranded Broadcom Network Adapter of the same chipset. Now, Broadcom, Dell, and HP each have a driver. Based on what we discussed earlier about how PnP finds a matching driver, it would be possible for any of these three drivers to be a match, if both devices reported the same PnP ID, then Windows' driver ranking process would determine which driver is installed based on signed versus unsigned, version number, inbox versus Out-of-Box, and so on. So...