Ok, I think everyone can relate: Driver management is a pain in the behind. Having to make sure you have the latest, duplicated drivers that work for two models in different packages, etc. If you work with Lenovo hardware, you're feeling my pain.
But it just doesn't seem to work well with our PC vendor of choice (as I said: Lenovo is a headache).
So, I'm wondering if there are other thoughts on how to get drivers installed during the task sequence. My initial thought was to get the LAN drivers installed, then do a DISM command step that would just recurse a directory (this method would eliminate having to add the drivers each time to SCCM and create a driver package).
But then I was thinking about maybe using the Unattend.xml file for it. Specify the path of the drivers and have it imported into the wim during the TS. Maybe this will eliminate the need for the actual dism command (instead just running "Setup /unattend:C:\unattend.xml"). Maybe???
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Ok, I think everyone can relate: Driver management is a pain in the behind. Having to make sure you have the latest, duplicated drivers that work for two models in different packages, etc. If you work with Lenovo hardware, you're feeling my pain.
So I'm a huge fan of Johann and his Total Control Method.
But it just doesn't seem to work well with our PC vendor of choice (as I said: Lenovo is a headache).
So, I'm wondering if there are other thoughts on how to get drivers installed during the task sequence.
My initial thought was to get the LAN drivers installed, then do a DISM command step that would just recurse a directory (this method would eliminate having to add the drivers each time to SCCM and create a driver package).
But then I was thinking about maybe using the Unattend.xml file for it. Specify the path of the drivers and have it imported into the wim during the TS. Maybe this will eliminate the need for the actual dism command (instead just running "Setup /unattend:C:\unattend.xml"). Maybe???
Anyone have any thoughts on this?
Share this post
Link to post
Share on other sites