Hello All - I've been using SCCM OSD TS for deployments for a while now and enjoy the challenge. Recently, though, I've found an error that I can't yet resolve. Recently, my company purchased some new models of laptops - Lenovo T410 & Lenovo T420. Both of these models have an Intel HD Graphics Family (8086&DEV_0126) display adapter. Before running any of my TSs on them, I went to Lenovo's site, downloaded all drivers for both models, extracted them, then imported them into SCCM. However - after running an OSD TS, I get an error message on the display adapter and can't get a higher resolution. In Device Manager, there is an exclamation mark on the adapter and has the error Code 12 - This device cannot find enough free resources to use. No matter what i try - uninstall/reinstall drivers, clearing & changing BIOS, everything - nothing resolves it. The only catch is that this morning I wiped the partitions and reinstalled Windows 7 from an OEM disc. I downloaded the same video driver from lenovo, extracted it, installed it via "update driver" device manager (so that no extra software would be installed as SCCM would do) ,and rebooted. It worked great! No Problems! I have deleted the specific driver from SCCM, reimported it, then updated dist points but still get the same error. Note: During OSD TS, the driver does install. When getting the error, it displays the "Intel(R) HD Graphics Family" name, not Standard VGA Adapter. Any suggestions? Thanks! Ben K.

What if you install that driver as a Software Package?My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

Hi Ben, I’ve created and tested driver packages for a Lenovo T410 without any problems. But I don’t use the method that you describe in your post. I never import the drivers into ConfigMgr. I just create a folder with the required drivers in my ConfigMgr source, and create a driver package that points to that folder. Then I use the “Apply Driver Package” step (with WMI filtering) in the Task Sequence. In a perfect world your method should work just fine, but my experience is that this method has a higher success rate, and I think it’s a lot easier to predict the result when you keep the drivers for each model 100% separated. Ronni Pedersen | Configuration Manager MVP | Blog: http://www.ronnipedersen.com/ | Twitter @ronnipedersen

Yes Ronni, I agree with you. Using "Apply Driver Package" task sequence step can have sccm to install only device drivers from sepcific category. But using "Auto Apply Drives" will will search in the Configuration Manager 2007 existing driver categories for the most appropriate device driver to install with the operating system deployment. Configuration Manager 2007 will look in all available categories for the device driver. And your install the driver in a clear Windows 7 will success, I think your failure maybe based on SCCM did not find the appropriate driver for the video device. So try the "Apply Driver Package" way. Thanks

Hi Ben, This device cannot find enough free resources that it can use. (Code 12) This issue can be caused by the conflict between different hardware trying to access same resources. The hardware could be different and not necessarily two graphic cards. However, you can build the machine manually using an OEM disc and then install the same driver works fine. So, this rules out the possibility of a hardware specific problem. Please build a machine manually, install the Intel HD Graphics driver and capture that machine. Then use that image for deployment without the Apply driver package or Auto apply driver step to check if it works. If it works properly, you may then in the second attempt try to use only the Auto Apply driver step to test. Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Its interesting that three Microsoft experts all recommend against using the "official" method of using the drivers module in SCCM 2007 - However, I have to say i totally agree with you. It feels to me like component was thrown together with much thought for how it would be used. I also have the Code 12 problem from Intel HD gfx devices, so this thread has been very useful thanks. But, if you are recommending having seperate packages for each hardware platform (which is a sensible approach and defiinately the easiest to manage), then the EXTREMELY annoying restruiction in SCCM of only being able to add a driver to 1 driver package completely lets down this logic. So creating seperate driver packages for each hardware platform as you have suggested Ronni, is fine except how do you separate the actual driver files required by the OS and SCCM, from all the crap that is not required (for this Toshiba R700 = 1.29 GB), why is the overall reason for my post. I use an extremely useful tiny utility called Double Driver (crap name incidentally). It will scan the local system, distiguish (reasonably well) the build in OS drivers from the third party non standard ones, and allow you to backup all the required drivers to a folder structure. That folder structure can then be used for driver packages, which are both minimal in size and specific to each hardware platform (and CPU architecture if required). We find this a great solution to the SCCM driver shortcoming. http://www.boozet.org/dd.htm PS One additional benefit of using this tool is that each driver backup seems to be unique, so you can add the same drivers for the same bit of hardware more than once, this gets around the annoying problem above.

Double Driver is a very useful utility, thanks for the suggestion. My Intel graphics card has been causing me all sorts of problems.

I know i'm late to the party here, but i had the exact same same issue as you. Turns out i had recently imported AMD Graphics drivers too and they were conflicting with the intel ones. So you need apply them manually using a WMI query logic Hardware ID for the AMD one's. Since intel don't conflict with AMD devices but the AMD drives seem to conflict with the intel HD graphics. Hope this helps anyone else who comes across this issue. Regards

Daryl, I am in the same boat. I have an AMD driver for my Lenovo X100 series devices and now my intel driver is blowing up on my Lenovo R400, L412, T410 etc. I have seperate driver packages for the different models but my intel drivers are still broken. How did you resolve it? We are using a WMI query for the machine type such as thinkpad L412. I thought the seperate driver packages kept the drivers "seperate". Please let me know. I am stuck!