When I deploy an OS via PXE boot the certain laptop gets all the drivers it needs. My problem is when I created TS media and boot from this, I am missing some dirvers (nic, video...). Am I missing something here? All I did was right clicked the TS and said "create media". I used my main DP when creating it which had 4 or 4 packages associated with this TS. Any help is appreciated.Thanks, Mark-

Hello Mark, Can you please specify what kind of media you created? I am assuming you create a standalone media. With standalone media there is an assemption that there is not connection to server at TS run time. The autoApply driver action will be skipped for standalone media. Only Apply Driver Package TS action will be executed. If you are using Boot media then you should have the same experience you had with PXE. Thanks, Mahmoud

Hi Mahmoud, Yes I created stand alone media. I am trying to create a base ISO/CD for my technicians to use that will install our "gold image". I guess this is not the case when installing by media? This is my only laptop that I am having problems with, with this media. Thanks, Mark-

As mentioned, the Auto Apply task does not work with Stand-alone media. This is because it is dynamic in nature and requires communication with the MP to determine what drivers are available in the driver catalog and stand-alone media assumes no connectivity. Is there a reason you are using stand-alone media as opposed to normal boot media? Normal boot media is the typical option used; stand-alone media is usually only used for systems that actually have no connectivity to the ConfigMgr site.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

You said: "This is my only laptop I am having problems with, with this media". Does that mean the media worked elsewhere? As I mentioned on my first reply for standalone media the Auto Apply action is skipped. Unless you have a good reason for using Standalone media I advise you to use Boot media. Since your scenario worked fine with PXE it will work using Boot media. If you insist to use Standalone media the solution is to create a Driver package with the proper drivers and add an "Apply Driver Package" action to your task sequence. Thanks,

Is there a reason you are using stand-alone media as opposed to normal boot media? Normal boot media is the typical option used; stand-alone media is usually only used for systems that actually have no connectivity to the ConfigMgr site. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys Jason, I am using the stand-alone media for that exact reason. These machine have no network connectivity in the labs. I guess I can add a driver package to it and go from there. Thanks, Mark-

I would add driver packages and use wmi querys to select which package to install for specific hardware.

I would add driver packages and use wmi querys to select which package to install for specific hardware.

Yep, that's your only option. Make sure you understand the differences between the two task types. Also, to limit the number of drivers actually copied, use Gakis's suggestion.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Yep, that's your only option. Make sure you understand the differences between the two task types. Also, to limit the number of drivers actually copied, use Gakis's suggestion.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Hi Mark, Use apply driver package task sequence step with this option for different computer models in Options tab: select * from Win32_ComputerSystem where Model Like "%Your Laptop Model%" Upon picture is from Richard Wu's blog post: Managing Device Driver by System Center Configuration Manager(SCCM) Hope this will help. Thanks

Hi Mark, Use apply driver package task sequence step with this option for different computer models in Options tab: select * from Win32_ComputerSystem where Model Like "%Your Laptop Model%" Upon picture is from Richard Wu's blog post: Managing Device Driver by System Center Configuration Manager(SCCM) Hope this will help. Thanks