Unfortunately, that's not really an option in ConfigMgr, especially because it runs counter to the content distribution model in place. But I have to ask what the benefit is in moving the logic for differentiating models from the more visible (Task Sequence) to the less visible (back end scripting). How many models are we looking at in this case?
-Phil From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Séguin, Mario (BAC/LAC) Sent: Wednesday, April 27, 2016 8:54 AM To: ms...@lists.myitforum.com Subject: RE: [mssms] Injecting Drivers like in MDT 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: christopher.catl...@us.sogeti.com<mailto:christopher.catl...@us.sogeti.com> [mailto:christopher.catl...@us.sogeti.com] Sent: April 26, 2016 5:07 PM To: Séguin, Mario (BAC/LAC) <mario.seg...@canada.ca<mailto:mario.seg...@canada.ca>> 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:mario.seg...@canada.ca> Sent: Tuesday, April 26, 2016 2:21 PM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> 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
