That is the thing, we had at the time, 70+ models defined in the TS, and all 
the package and application installations was handled thru either the CS or 
Collection Variables and boundaries were configured correctly.  It was the 
checking for every driver package that was slowing it down.  Now it seem to run 
fine at the slower locations, about 1 hr for an actual thin image (no 
applications in image, unless you count IE 11) and it installs what is needed 
for that group (version of office, AV any line of business apps).

From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On 
Behalf Of Troy Martin
Sent: Monday, May 02, 2016 7:00 PM
To: ms...@lists.myitforum.com
Subject: RE: [mssms] Injecting Drivers like in MDT

...the 30-45 min delay described, sounds like there are quite a few reference 
packages in the TS.  As policy is downloaded for EACH reference package, 
ExecMgr validates it ensuring the content (package/application) has been 
distributed to DP(s) i.e. content location request (CLR).  Like machine policy 
refresh (MPR), CLRs also query the MP but do it in order to obtain content 
location on DPs.

With that said - the point about clients not doing MPR against the proxy MP on 
the Secondary -, have you confirmed that the clients are within the boundaries 
of the secondary site and the MP is truly the client's assigned MP?  Factor in 
boundary(ies) lookups associated with the process (when the DPs are preferred 
e.g. IP subnet, IP ranges or AD subnets...there will be impact on MP 
performance.

Read this for more info' - 
https://technet.microsoft.com/en-us/library/bb681077.aspx

To increase performance and speed of your deployments - by dramatically 
reducing the 30-45 min delay -, think about using "data-driven" deployments 
where content (packages/applications) are defined in the MDT database or CS.ini 
and content locations are derived dynamically (during TS execution/run-time).

Also, read the attached email from Michael Niehaus about the number of policies 
created by reference packages in a task sequence.


Troy L. Martin | Technical Architect
1E | Software Lifecycle Automation for the Digital Business
US Mobile: +1 (678) 898-6147 | UK Phone : +44 208 326 9141
troy.mar...@1e.com<mailto:troy.mar...@1e.com> | 
www.1e.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.1e.com_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=lfm9K0cSqM44FHIoBa6p0wzT4MWYkn_0HYGNmWgkATs&e=>

Facebook<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_1eglobal&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=RRWJDZaMGcmivktB58TkvRLoQr1bC6jIDj-MN1oDLlE&e=>
 | 
Twitter<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_1e-5Fglobal_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=6SY99zYqJ1R5pAavjFi-JmFdxUD0lt-n0XwOK-omJcI&e=>
 | 
YouTube<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_1enews&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=XWjlpxF0vI8J3n42uqWMrEXgHphlWI2PD9XZHOHhX8U&e=>
 | 
Blogs<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.1e.com_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=tKrxeysyE64idSmjz1G3NP2ojp9RhRdpv1OljUgTbyg&e=>
 | 
RSS<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.1e.com_index.php_feed_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=qGt8-ZGt5rG-J3ClWoppG9TfmFKmktUZprrf0vtNjII&e=>

[1E @ 
MMS]<http://mms2016.sched.org/event/6bgE/more-real-world-windows-10-deployments-with-dell-1e?iframe=yes&w=i:100;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no>

From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Augustine, Greg
Sent: Monday, May 2, 2016 3:51 PM
To: 'ms...@lists.myitforum.com' 
<ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>>
Subject: RE: [mssms] Injecting Drivers like in MDT

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: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Séguin, Mario (BAC/LAC)
Sent: Monday, May 02, 2016 2:01 PM
To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>
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: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Augustine, Greg
Sent: May 2, 2016 2:41 PM
To: 'ms...@lists.myitforum.com' 
<ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>>
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: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Mawdsley R.
Sent: Wednesday, April 27, 2016 9:56 AM
To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>
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: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Daniel Ratliff
Sent: 27 April 2016 14:56
To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>
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: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Schwan, Phil
Sent: Wednesday, April 27, 2016 9:23 AM
To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>
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: listsadmin@lists.myitforum.com<mailto: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<mailto: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




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.






________________________________


Legal Notice: This email is intended only for the person(s) to whom it is 
addressed. If you are not an intended recipient and have received this message 
in error, please notify the sender immediately by replying to this email or 
calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any 
attachments may be privileged and/or confidential. The unauthorized use, 
disclosure, copying or printing of any information it contains is strictly 
prohibited. The opinions expressed in this email are those of the author and do 
not necessarily represent the views of 1E Ltd. Nothing in this email will 
operate to bind 1E to any order or other contract.




Reply via email to