Hello,

we've recently installed SP1 for SCCM 2012 R2 and now I had to create a new Driverpack for HP Z440 Workstation. So I downloaded all current drivers for this Model and Import them like always to SCCM.

First I noticed that it took ages to "Validate Driver Information". But I allready read about that so no big deal just wait. After this was finished I saw the new Import wizzard which now Lists the driver by .INF (see screenshot). I also noticed that there are many INFs for Realtek HD Audio

I continued importing the drivers and assigned them to a new driverpack. The import process also took ages. After it has finisehd I had a look at the Driverpack and couldn't belive how huge the Driverpack is, so I also had a closer look at the driversource.

The Driversource is about 550MB, so thats normal for one Computermodel
The Driverpack after import has about 20GB!!!!

SCCM creates for each .INF file a new Folder in the folder of the Driverpack and copys the whole content of the driver to it.

Example: The sourcefolder of the Realtek HD Audio driver is about 305MB and includes over 60 .INF files. After the Import this is about 19GB. For each .INF SCCM creates a new Folder in the Driverpackfolder and copys the complete source (305MB) to it. So I have 305MB more then 60 times in my Driverpack.

Anyone experience the same?

• Changed type Torsten [MVP]MVP, Moderator Wednesday, August 12, 2015 7:41 PM

Hi William

Thanks

I Think you are right and that the update is applicable on all systems with the admin console , but I find it strange that this is not mentioned in the KB article

it is also still not mentioned in the "Microsoft system center configuration manger team blog"

Regards

Johan

Just an update

We installed the update on the CAS and Primairy sites and also on computers with the configuration manager console installed.

We imported 300 MB on drivers (source), the driver package created was the same size , before the update the driver package was about 1,2 GB with the same drivers imported. 

Second  the step  'Validating file permissions and getting driver attributes" is indeed slow it was in our environment for the 300 MB about 7 minutes

Hope this will help someone

Regards

Johan

So after a powershell import it still took about 35-40 minutes to finish, so both methods took about the same amount of time. 

• Edited by Mike Snodgrass 12 hours 53 minutes ago

So after a powershell import it still took about 35-40 minutes to finish, so both methods took about the same amount of time. 

• Edited by Mike Snodgrass Monday, August 17, 2015 6:53 PM

Microsoft has released a Hotfix for this now

https://support.microsoft.com/en-us/kb/3084586

Microsoft has released a Hotfix for this now

https://support.microsoft.com/en-us/kb/3084586

and by me 5 days before that :)

anyhow glad it was addressed relatively quickly