I made a driver pack for a specific model of machine we have \\MYdp\drivers\Optiplex760 as the source, driver pack uploaded to DP as well do I also need to import them into the ConfigMgr DB? From what I see the ts ended successfully everything has an exit code of 0, yet none of the drivers in the driver pack installed?, it has all generic drivers that come with Windows 7. if it makes any difference, I am not using auto apply drivers step in my TS but I am using apply driver pack i made in my ts. Any advice would be appreciated.

Hi, If you are using SCCM 2007 which I assume as this is the SCCM 2007 forum then you don't have to import the driver into the Databaase for it to work. Are there any errors in the SMSTS-log file? Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

the smsts.log file will reveal whether or not this Step/group was run, have you checked that, perhaps you have a typo or error in your WMI check on the step/group assuming you are doing that cheers niall Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

I did not do a wim check because I know that all the machines in the collection are that specific model. I see now errors in the smts.log, for the driver package in the log I see. Parsing "Name of driver pack" step exit code 0 Take a look https://skydrive.live.com/?cid=b8dfad0155f75e0b#cid=B8DFAD0155F75E0B&id=B8DFAD0155F75E0B%212274 Thanks for any help.

parsing the step only tells us that it was looking at the step previously and not executing it, what we need is the actual smsts.log file which includes the Apply Driver Package step itself and the one you provided does not, you can press F8 during the time the step is taking place and immediatly afterwards capture the logs and upload them. the log file should say 'Start executing an instruciton. Instruction name: ' the typo is included in the LOGs... (not from me). can you try again please ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

here is the smsts.log https://skydrive.live.com/?cid=B8DFAD0155F75E0B&id=B8DFAD0155F75E0B%212274#cid=B8DFAD0155F75E0B&id=B8DFAD0155F75E0B%212274

It looks like your driver step was never run. Please review your task sequence and see if that step has any condition associated with it and see if that condition is true for your clients.

Hi Kerwin, Niall There is no condition on the step in the ts, just curious is there something in my log file that I posted that indicates the driver packages didn't run?. I can tell you I did not import the drivers in ConfigMgr DB, therefore under task sequences-->Drivers it is empty is this correct?. Under Task sequences-->driver packages I made a package called 2F26-2F24, and it's source is \\MyDP\OSImages\Lab Master Windows 7 x64 bit Drivers\Optiplex760. The package is on the dp. With the folder Optiplex760 I have folders for Video Nic sound etc The drivers are in these folders. Does it sound like I missed something or did something wrong?

I don't see any log lines that indicate that the driver client was run. I believe it is because your logs has rolled over. You don't have the older log lines. Can you please re-run your task sequence, but this time, copy the log files before the reboot to the new OS.

I don't see any log lines that indicate that the driver client was run. I believe it is because your logs has rolled over. You don't have the older log lines. Can you please re-run your task sequence, but this time, copy the log files before the reboot to the new OS.

yup as Kerwin says you are missing the important part of the logs, the easiest way to guarantee that you capture the logs from the moment you are interested in is to pause the task sequence in the step immediately after this one, you can pause it using a simple msgbox script to pop up a window which needs to be clicked, thereby the task sequence will wait for your click until it continues and you can grab the smsts.log file which should include the previous steps (apply driver package)... Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

yup as Kerwin says you are missing the important part of the logs, the easiest way to guarantee that you capture the logs from the moment you are interested in is to pause the task sequence in the step immediately after this one, you can pause it using a simple msgbox script to pop up a window which needs to be clicked, thereby the task sequence will wait for your click until it continues and you can grab the smsts.log file which should include the previous steps (apply driver package)... Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Maybe this would cause the same behavior, but do you have "Do unattended installation of unsugned drivers on version of Windows where this is allowed" checked?

Maybe this would cause the same behavior, but do you have "Do unattended installation of unsugned drivers on version of Windows where this is allowed" checked?