Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2858

May 30th, 2017 13:00

SCCM 1702 and Dell System Driver Library Import

I'm running SCCM 1702, and although there is no verified compatibility with it, the issue I'm running into I feel like is a configuration problem on my end, not a bug with the import. 

I was wondering if anyone else can let me know if they have the driver imports working correctly or are experiencing the same issues as I am:

The import works fine as far as allowing me to select and filter the correct package, and it downloads without an issue, but the problem I am running into is that after the files are downloaded into a directory (i.e. 9360-WIN10-A03-VGC9M) they are then processed into a folder named (9360-WIN10-A03-VGC9M_Drivers), which contains randomized folders with the drivers in them. It then deletes the original folder with the organized folder structure (i.e. subfolders like "Chipset", "Audio", etc...)

The problem then is that the SCCM software library is referencing that original folder structure, so when I try to use any of these files it doesn't know where to look because the 9360-WIN10-A03-VGC9M folder was deleted after the files were processed into the 9360-WIN10-A03-VGC9M_Drivers.

The only workaround I've found so far is to temporarily copy the 9360-WIN10-A03-VGC9M folder to another location while the system is moving those files to the new directory, then copy that original folder back once it is complete.  Then I am able to import those drivers into my boot images.

Does this seem like normal behavior?  I had the same issue with the '16 version of SCCM too.

11 Posts

June 9th, 2017 12:00

Disregard this post, I read on a Dell engineering post that this SCCM plugin is definitely not compatible with newer versions of SCCM (i.e. later than 2012R2) so I've gone back to manually downloading the cab files and extracting them myself.

Hopefully at some point Dell will release a compatible version.

No Events found!

Top