Kim Oppalfens
My feedback
-
12 votesKim Oppalfens
supported this idea
·
-
834 votes
-
1 voteKim Oppalfens
shared this idea
·
This blogpost should get you pretty close to what you want to achieve.
http://www.oscc.be/sccm/osd/The-holy-grail-of-ConfigMgr-diver-management,-or-whatever-you-want-to-call-it/
The apply device drivers step doesn't give you the same level of control, and misses the ability to apply drivers for hardware that is not detected. Which is problematic on some devices where a certain piece of hardware only pops up after a "parent" component is detected.
Other methods require one to modify your tasksequence each time it has to support a new hardware model. This request (or the alternative implementation in the blogpost) allows for a hands-off approach, needing no TS edits to support new models.