Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

quijibow

10 Posts

104270

February 1st, 2011 08:00

Problem with Dell Client Cab Driver Import Wizard

When I import Dell driver cabs into SCCM, it doesn't put the drivers in the drivers folder. In the package, the drivers folder is empty even though the import completed successfully. This worked in the past, I don't know what has changed to cause it to stop working. The Data Source path looks like the following: \\MyServer\SMS_COS\OSD\Lib\DriverPackages\Dell\Client\T5500-Win7-A00-R253041\T5500\win7\x86\Audio
When it did work correctly, it named the folders differently: \\MyServer\SMS_COS\OSD\Lib\DriverPackages\Dell\Client\960-Win7-A00-R246445\960\win7\x861B0C2993-4365-4ADB-BD89-C78E3564475D
Any ideas why it's not working? thanks!

matt7184

3 Posts

March 4th, 2011 02:00

"Sorry to bump an old thread but I'm having the exact same problem with all the XP cab files 760/780/E5400/5410/E5500/E5510 ..

It puts the mass storage drivers into drivers but not the specific model ones.. if i browse to the folder it inported to they are infact all there just not available within configmgr..

Im guessing I could manually export and import the cabs but I'd like to use the CAB import wizard."
I tried v1.1 and v1.2 of the DCDP both do not put the drivers in.

matt7184

3 Posts

March 4th, 2011 03:00

Scratch that.. installed v1.2 and they work now.. just had to delete again and reimport.

vivek_agarwal2

14 Posts

April 1st, 2011 13:00

Thanks a lot for your feedback.

jcaswell

4 Posts

July 15th, 2011 09:00

Having the same problem with the E6320 driver package. It imports fine, but the driver package doesn't have any drivers listed. Verified running v1.2 of DCDP

Cody8411

2 Posts

July 21st, 2011 17:00

I had the same problem with the Latitude E5410 and Optiplex 380 CABs as well. I also downloaded a bunch of other models but just reverted to importing them manually.

Maybe if you can let us know what the manifest issue is we can take care of it when we need to

bduaneENA

1 Message

September 7th, 2011 11:00

Same problem here, ~7 months later. I have confirmed i have 1.2 version, and downloaded the latest WinPE drivers cab and the latest E6420 drivers cab, both have the same problem, it goes through the motions of importing all of the drivers, however, none of them show up in the "Drivers" folder of SCCM Manager Console for the package.

jamesloker

8 Posts

October 24th, 2012 05:00

I am having a weird issue.

The Registry key is actually HKLM\Software\WOW6432Node\Dell

Also, when I click continue it just wont let me get past or install the driver.

jamesloker

8 Posts

October 24th, 2012 05:00

as an additional, if I click USE default, no registry error occurs but the same secondary problem occurs where it just sits there.

DELL-Warren B

1.1K Posts

October 24th, 2012 06:00

are you using elevated privileges?

jamesloker

8 Posts

October 24th, 2012 06:00

Yes, It installs fine. The user is a member of the Local Administrators group. Also tried with a domain admin. Same thing. Tried installing on my local machine with the SCCM2012 console installed. Same errors.

jamesloker

8 Posts

October 24th, 2012 07:00

OK, Running SCCM Console as Administrator seems to have cured the problem mentioned. But it still fails to create the driver in the default path or in a shared unc folder

Driver Package: 390-Windows7-x64-A00
 Driver Package successfully created.
 Drivers for Driver Package: 390-Windows7-x64-A00
     Failed to import driver: 390\win7\x64\video\R299314\IntcDAud.inf
     Failed to import driver: 390\win7\x64\video\R299314\Impcd.inf
     Failed to import driver: 390\win7\x64\video\R299314\2312-64.inf
     Failed to import driver: 390\win7\x64\chipset\R292027\nusb3hub.inf
     Failed to import driver: 390\win7\x64\chipset\R292027\nusb3xhc.inf
     Failed to import driver: 390\win7\x64\communication\R296702\snxpci.inf
     Failed to import driver: 390\win7\x64\communication\R296702\snxpcip.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\cougahci.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\cougcore.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\cougide.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\cougsmb.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\cougusb.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ibexahci.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ibexcore.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ibexid2.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ibexide.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ibexsmb.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ibexusb.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ich78id2.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ich78ide.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ich78usb.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\ich7core.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\IntelCP2.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\IntelIOH.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\JasperFo.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\NehalMEX.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\SNB2009.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\Tcreek.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\Tcrkahci.inf
     Failed to import driver: 390\win7\x64\chipset\R293337\tcrkusb.inf
     Failed to import driver: 390\win7\x64\audio\R299945\H61Carwa.inf
     Failed to import driver: 390\win7\x64\video\R289243\AtihdW76.inf
     Failed to import driver: 390\win7\x64\video\R289243\C7108749.inf
     Failed to import driver: 390\win7\x64\video\R289243\CH108749.inf
     Failed to import driver: 390\win7\x64\video\R289635\AtihdW76.inf
     Failed to import driver: 390\win7\x64\video\R289635\C7108749.inf
     Failed to import driver: 390\win7\x64\video\R289635\CH108749.inf
     Failed to import driver: 390\win7\x64\chipset\R300750\HECI.inf
     Failed to import driver: 390\win7\x64\network\R301239\rt64win7.inf
     Failed to import driver: 390\win7\x64\network\R295625\bcmvwl.inf
     Failed to import driver: 390\win7\x64\network\R295625\bcmwl6.inf
     Failed to import driver: 390\win7\x64\communication\R294048\DellUSBw.INF
     Failed to import driver: 390\win7\x64\network\R296762\b57nd60a.inf
     Failed to import driver: 390\win7\x64\network\R296762\k57nd60a.inf

Distributed Package Content to below Distribution Points:390-Windows7-x64-A00
 (1)\\TCSCCM.TCL.office

jamesloker

8 Posts

October 24th, 2012 07:00

Fixed....

1. The source has to be local (ie :\ )

2. Console has to be Run As Administrator

Cheers for all your help

DELL-Warren B

1.1K Posts

October 24th, 2012 07:00

You have a space in your UNC path between "OptiPlex" and "390"  Could that be causing the issue?

jamesloker

8 Posts

October 24th, 2012 09:00

spoke too soon. It appears the OptiPlex 390 cab has 'issues'. Re downloaded the cab but the same problems. OptiPlex 380 worked fine.

Was this post helpful?

View All

No Events found!

Top