Problem importing DELL Driverpacks with SCCM

Question

Using the DELL Extensions for SCCM i try to import some dell driverpacks. The packs for (Optiplex) 360, 380, 760, 780, 960, 980, E5500 (Latitude), E6400 (latitude), E6500 (Latitude) work fine. But the Exx10-Releases do not. Eg the E6410 (Latitude) fails on distribution with this error: ~Copying C:\Program Files (x86)\Microsoft Configuration Manager\OSD\Lib\DriverPackages\Dell\Client\E6410-win7-A02-R269407\E6410\win7\x64\controlpoint\R257552\Security Device Driver Pack\O2Micro Smartcard Reader\program files\O2Micro OZ776 SCR Driver\Vista64\oz776x64.cat to C:\SMSPKGC$\BOS00059\controlpoint\R257552\Security Device Driver Pack\O2Micro Smartcard Reader\program files\O2Micro OZ776 SCR Driver\Vista64\oz776x64.cat, Failed, Win32 Error = 3 ~Cannot copy package BOS00059 from C:\Program Files (x86)\Microsoft Configuration Manager\OSD\Lib\DriverPackages\Dell\Client\E6410-win7-A02-R269407\E6410\win7\x64\ to C:\SMSPKGC$\BOS00059\, Win32 Error = 3 ~Failed to copy package BOS00059 from C:\Program Files (x86)\Microsoft Configuration Manager\OSD\Lib\DriverPackages\Dell\Client\E6410-win7-A02-R269407\E6410\win7\x64\ to MSWNET:['SMS_SITE=BOS']\VIRSRV02\SMSPKGC$\BOS00059\ STATMSG: ID=2328 SEV=E LEV=M SOURCE='SMS Server' COMP='SMS_DISTRIBUTION_MANAGER' SYS=VIRSRV02 SITE=BOS PID=2604 TID=5476 GMTDATE=Fr Jul 30 12:19:21.313 2010 ISTR0='BOS00059' ISTR1='C:\Program Files (x86)\Microsoft Configuration Manager\OSD\Lib\DriverPackages\Dell\Client\E6410-win7-A02-R269407\E6410\win7\x64\' How can this be fixed ? This complies to all Exx10 Version of all latitude driverpacks (at least E6510, E6410, E5510 E5410)

bosbremen · Answer

When i delete the O2Micro OZ776 SCR Driver from the package it deploys successfully. It seems that something is wrong with that driver. Please check this dell

mathias.h · Answer

Hello Dell?
I have the same problem. I can't import the Driver pack for E6410 with that device driver:

"Error: Failed to import the following drivers: \\xxxsccm01\Drivers_Source\Latitude E6410\E6410-win7-A04-R292083\E6410\win7\x64\Control Point\R269916\Security Device Driver Pack\Dell PBA Device Driver\pbadrv.inf - The selected file is not a valid Windows device driver."

mathias.h · Answer

This one is also broken from the same package: "E6410-win7-A04-R292083":

Error: Failed to import the following drivers:
\\xxxsccm01\Drivers_Source\Latitude E6410\E6410-win7-A04-R292083\E6410\win7\x64\application\R257449\Filter Driver\stdfltn.inf - The selected file is not a valid Windows device driver.

DELL-Warren B · Answer

Thanks for the post. I'll send your feedback to the dev team. Workaround: You can get the CABs to successfully import by skipping those drivers since ConfigMgr isn't seeing them as valid.

mathias.h · Answer

Absolutely, that's how I did it. Originally I thought the broken drivers were the reason for why the driver-pack couldn't be imported correctly.

vivek_agarwal2 · Answer

Issue fixed with the new release [E6410-win7-A05-R296780.CAB] on dell support site.

vivek_agarwal2 · Answer

A new release posted on dell support site fixes this problem [E6410-win7-A05-R296780.CAB ]. Let us know if the issue still persists.

bhethcote · Answer

FYI: We just ran into this same issue with the Desktop and Notebook Win7 Combo CABS. We tried to import the newer files from the 6410 CAB into SCCM and they failed as well.

Error: Failed to import the following drivers:
\\\
- The selected file is not a valid Windows device driver.
\\\
- The selected file is not a valid Windows device driver.

bhethcote · Answer

REVISION: The path schould actually start like: \\Notebook...

DELL-Warren B · Answer

The best practice for the Combo Cabs is to not import them. Importing them will only make it more difficult to update the driver package when the Combo cabs are updated. I have a video that walks through the process of creating a driver package without importing it. http://www.delltechcenter.com/page/Client+Deployment

The pros to this approach are that you make your driver package updates extremely simple (~5 minutes) which will be very helpful as Dell increases the frequency of Driver CAB updates. The only con would be that you do have to import boot critical drivers for use with WinPE, but the WinPE driver CAB takes care of that.

If you choose to import, then you will need to remove the 2 .inf files listed as they are not applicable to Windows, but ConfigMgr tries to process them anyways and fails the import.

Thanks,

Warren

bhethcote · Answer

Cool! Thanks Warren! We're not far into deciding our driver approach, so the info is very useful.

Enterprise Client

Was this post helpful?