Hi chris, Thanks for the link, however what I am trying to avoid is to add a Driver Package in the TS for each model we have. I would like to have 1 Driver Package sequence take would dynamically change depending on the model.
thanks From: [email protected] [mailto:[email protected]] Sent: April 26, 2016 5:07 PM To: Séguin, Mario (BAC/LAC) <[email protected]> Subject: RE: [mssms] Injecting Drivers like in MDT Yes, see below: http://deploymentresearch.com/Research/Post/273/The-Drivers-Saga-continues-How-to-Master-Drivers-in-ConfigMgr-2012 From: Séguin, Mario (BAC/LAC)<mailto:[email protected]> Sent: Tuesday, April 26, 2016 2:21 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Injecting Drivers like in MDT e Hello, In MDT I was able to only inject the drivers I needed based on model and os architecture. Basically I had one task in the TS that was running a script that was getting model name and was downloading the associated files. Can we do that in SCCM? I read that we can do it but have to setup a task for each model and do WMI filtering. I am trying to avoid creating 1 task for each models we have, I would like to only have 1 task that would dynamically call the correct package. thanks
