I am running SCCM 2010 with MDT integrated. We have recently created a new Windows 7 images and setup the drivers for all the required models. These all work fine using both methods of driver deployment (Auto Apply Drives via SCCM driver database and Apply Driver Package). Our preferred method for deploying drivers is the "Apply Driver Package" as this is the easiest to upgrade drivers.
I have recently been tasked to add a new model (Toshiba Portege R830) to SCCM. As we use a USB flash drive to boot I was able to work out the three drivers (NIC, HDC, USB - yes this model has USB3 and would disconnect the USB flash drive before loading the drivers if the USB driver was not included)needed for this model without breaking SCCM.
- I then imported only the NIC and HDC driver into SCCM driver database so that I could add them to the boot WinPE.wim, all good so far.
- Next I got all of the required drivers, extracted them in a folder and sub folders and then created a driver package in SCCM and deployed it to my DP's (this is how some of the other working models have been done.
- Then I added the "Apply Driver Package" task to my task sequence and targeted the correct model using a WMI quire (verified that it works).
Now the big test.
- Laptop boots off USB and loads NIC etc. I am able to select task sequence and the WinPE.wim downloads.
- Laptop reboots into the download WinPE.wim and starts the task sequence. The HDD is cleaned and partitioned. WIN 7 image is downloaded and applied. The apply driver package is selected and the drivers are downloaded. some other bits are done and the laptop reboots into the applied Win 7 image.
- Win 7 applies the drivers and this is where it all goes pear shaped. The driver package that downloaded is not on the drive anywhere. After a reboot the TS tries to continue. At this point I can press F8 to launch the command prompt and run explorer.exe and go into device manager. I can see that none of the drivers in the driver pack have been applied. If I try to update the drive for one of the devices and point it at anywhere on c:\ ( including the root) no drivers are found. If I do the same but point it at the USB stick that has a copy of the folder used for the driver package all devices find there appropriate driver fine.
Sorry about the rant. Can any one tell me where SCCM puts the drivers during the download phase and why it goes through the process but then can not find them later?
The above process works for the Toshiba Teca M10 so should work for the Portege... The Portege has a SSD hard disk and USB 3 but these drivers are there and the SSD drive appears to be work otherwise it wouldn't boot from C:\ into windows in the first place, would it?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi All,
I am running SCCM 2010 with MDT integrated. We have recently created a new Windows 7 images and setup the drivers for all the required models. These all work fine using both methods of driver deployment (Auto Apply Drives via SCCM driver database and Apply Driver Package). Our preferred method for deploying drivers is the "Apply Driver Package" as this is the easiest to upgrade drivers.
I have recently been tasked to add a new model (Toshiba Portege R830) to SCCM. As we use a USB flash drive to boot I was able to work out the three drivers (NIC, HDC, USB - yes this model has USB3 and would disconnect the USB flash drive before loading the drivers if the USB driver was not included)needed for this model without breaking SCCM.
- I then imported only the NIC and HDC driver into SCCM driver database so that I could add them to the boot WinPE.wim, all good so far.
- Next I got all of the required drivers, extracted them in a folder and sub folders and then created a driver package in SCCM and deployed it to my DP's (this is how some of the other working models have been done.
- Then I added the "Apply Driver Package" task to my task sequence and targeted the correct model using a WMI quire (verified that it works).
Now the big test.
- Laptop boots off USB and loads NIC etc. I am able to select task sequence and the WinPE.wim downloads.
- Laptop reboots into the download WinPE.wim and starts the task sequence. The HDD is cleaned and partitioned. WIN 7 image is downloaded and applied. The apply driver package is selected and the drivers are downloaded. some other bits are done and the laptop reboots into the applied Win 7 image.
- Win 7 applies the drivers and this is where it all goes pear shaped. The driver package that downloaded is not on the drive anywhere. After a reboot the TS tries to continue. At this point I can press F8 to launch the command prompt and run explorer.exe and go into device manager. I can see that none of the drivers in the driver pack have been applied. If I try to update the drive for one of the devices and point it at anywhere on c:\ ( including the root) no drivers are found. If I do the same but point it at the USB stick that has a copy of the folder used for the driver package all devices find there appropriate driver fine.
Sorry about the rant. Can any one tell me where SCCM puts the drivers during the download phase and why it goes through the process but then can not find them later?
The above process works for the Toshiba Teca M10 so should work for the Portege... The Portege has a SSD hard disk and USB 3 but these drivers are there and the SSD drive appears to be work otherwise it wouldn't boot from C:\ into windows in the first place, would it?
Help please???
Share this post
Link to post
Share on other sites