Hi,

Not a massive issue, but has anyone else noticed weird behaviour when importing the Realtek HD Audio driver into SCCM? It creates 18 seperate driver items in SCCM.

Looking at the driver source, it does seem like there are a load of .inf files, so I'm presuming this is why. Anyone else encountered this, and if so, was there anything you have done to work around it?

Thanks,

Iain

Not sure what you are expecting here. If you don't want a driver, delete it.

Also note that the drivers node and the drivers listed there are in no way representative of the number of files or size of a driver package. They are simply entries detailing the devices supported by a specific set of files which could have a lot of overlap as many inf files actually contain information for many different devices and the other driver files (like dlls)  often overlap also.

Ultimately, why is this causing you any concern? ConfigMgr is doing what it's supposed to do.

Also, when you are importing drivers, don't just select everything (ie all the .inf files).

Do you need x64 for example if you are deploying x86 only?

another alternative may be to run the audio driver setup.exe with a silent switch. I have done that before with audio driver packages and not imported them at all. I just ran that in front of any software install steps in my TS. If you do that you would have to figure out the silent switch though.

Hi,

I guess that you import the drivers from a uncompressed .exe file? As Gerry said, you don't need to import all the drivers. You could install the driver on a reference computer, then backup this driver by a software. After that, you should get the files you need to import.

Best Regards,

Joyce Li

Install one of your models and check this tool:

http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d

You can export only the needed drivers with that tool.

• Edited by narcoticoo 8 hours 6 minutes ago

Install one of your models and check this tool:

http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d

You can export only the needed drivers with that tool.

• Edited by narcoticoo Thursday, January 30, 2014 4:13 AM
• Marked as answer by iainrobins 22 hours 25 minutes ago

Thanks for the responses.

My concern? Ultimately nothing major, I understand ConfigMgr is behaving as it should and is importing all the inf files it finds.

In this case it seems to be a crazy amount of drivers to import for one piece of hardware, made worse by the fact that pretty much every device in our estate has a realtek HD audio chip....

I was wondering if anyone else had encountered this frustration as it makes viewing the drivers in the database a bit confusing.

• Edited by iainrobins 22 hours 16 minutes ago

Thanks Greg... I was just doing x64, just even for x64 only there are still a hell of a lot of different inf files.

Interesting idea.

But might that lead to overcomplicated the task sequence, accounting for different hardware models and then running the appropriate exe?

Thanks Joyce, I will give that a try.

Interesting tool, will check it out.

Thanks!

*EDIT* PERFECT! That does exactly what I need it to. Thanks again!

• Edited by iainrobins 22 hours 15 minutes ago

I was wondering if anyone else had encountered this frustration as it makes viewing the drivers in the database a bit confusing

So delete the ones you don't need then. Or create a sub-folder and move them all to that sub-folder. You can even rename them in the console.