I have been looking for the link that lead us this way but cannot seem to find
it, I know I seen something somewhere. Since we had MDT integrated into SCCM
using the scripts and customsettings.ini file, we added the model alias section
back into the custom settings file, like MDT.
UserExit=ModelAliasExit.vbs
OSDAutoApplyDriverCategoryList=#SetModelAlias()#
We edited the model alias script to just set the OSDAutoApplyDriverCategoryList
variable.
elseif Instr(sModel, "OptiPlex 7010") then
SetModelAlias =
"DriverCategories:99717c22-238c-442a-b49f-abbac96229d1"
elseif Instr(sModel, "OptiPlex 7020") then
SetModelAlias =
"DriverCategories:f079bb92-547b-461a-9566-f6205d308dd1"
There probably are some disadvantages to it, but in our case we were using OSD
in locations that had low bandwidth. T1 or less with 128-256k throttle to
primary during working hours, shared between AV servers and SCCM. Each
package in a task sequence seemed to pol the primary even if a secondary was at
the location for policy and we were seeing a 30-45 minute wait once a task
sequence was selected before it would start imaging. Once thru that it would
image at a normal rate.
Greg Augustine
Office of Administration
Information Technology Services Division - State Data Center
(573)-751-4714
From: [email protected] [mailto:[email protected]] On
Behalf Of Séguin, Mario (BAC/LAC)
Sent: Monday, May 02, 2016 2:01 PM
To: [email protected]
Subject: RE: [mssms] Injecting Drivers like in MDT
I was thinking of using this a well but wondering what are the disadvantages.
https://blogs.technet.microsoft.com/deploymentguys/2008/04/18/configuration-manager-dynamic-driver-categories/
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Augustine, Greg
Sent: May 2, 2016 2:41 PM
To: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: RE: [mssms] Injecting Drivers like in MDT
We currently have 96 models. We use the auto apply driver and use the model
alias script to set driver categories.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Mawdsley R.
Sent: Wednesday, April 27, 2016 9:56 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Injecting Drivers like in MDT
Agree with Daniel, I for one am touching the limits of the XML size, so have
to be careful with what currently gets added in.
However, I 100% believe individual driver steps with individual driver packages
using wmi queries is the best way to currently do it.
Rich Mawdsley
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Daniel Ratliff
Sent: 27 April 2016 14:56
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Injecting Drivers like in MDT
One use case is task sequence XML size. I know the limits were increased in
2012 R2, but I know some have complained they still hit the .XML size. This is
compounded by some ACPs out there that may require additional steps for driver
package caching. Just as an example, we have ~35 models and have over 50 driver
cache and install steps.
I also know Aaron and team are already looking at a solution similar to the
dynamic task sequence variables step, but its probably lower on the priority
list.
Daniel Ratliff
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Schwan, Phil
Sent: Wednesday, April 27, 2016 9:23 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Injecting Drivers like in MDT
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: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Séguin, Mario (BAC/LAC)
Sent: Wednesday, April 27, 2016 8:54 AM
To: [email protected]<mailto:[email protected]>
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:
[email protected]<mailto:[email protected]>
[mailto:[email protected]]
Sent: April 26, 2016 5:07 PM
To: Séguin, Mario (BAC/LAC)
<[email protected]<mailto:[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
The information transmitted is intended only for the person or entity to which
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information
in error,
please contact the sender and delete or destroy the material/information.
