Unsolved

This post is more than 5 years old

8 Posts

11464

April 27th, 2011 10:00

Incorrect CAB. release.dat files missing or specifying incorrect model

I extracted the driver CAB files and imported them in exactly the same way as I have for the other models but I encountered the 'Cannot import this driver as it already exists in this site' issue.

The CAB file seems to be missing a lot of the release.dat files that have been added to other driver packages to circumvent the duplicate driver detection process of ConfigMgr. The release.dat files that are included in some of the folders refer to the 760 model.

8 Posts

April 28th, 2011 05:00

I've managed to fix this cab release by deleting all the release.dat files and then running a script I have written to re-reate them (following the same format as Dell). Place it alongside the root folder (in this case 990) and run it.

@ECHO OFF
setlocal enabledelayedexpansion

for /f "tokens=*" %%c in ('dir *.inf /a-d /b /s') do (

set abspath=%%~dpc
call set "relpath=%%abspath:%cd%\=%%"
call set "str=%%relpath:\= %%"

for /f "tokens=1 delims=." %%d in ('echo %time%') do echo !date! %%d > "!relpath!release.dat"
echo !str! >> "!relpath!release.dat"
)

1.1K Posts

May 2nd, 2011 21:00

There is a patch for ConfigMgr that addresses the root cause of the import failures on duplicate drivers (the reason for the release.dat files). You should look at using the patch unless you leverage categories heavily as the patch doesn't handle categories correctly.

Dell recommends that you do not import entire cab files into the ConfigMgr driver store and it adds to the complexity of driver management along with the importing issues.

Create driver packages directly from the extracted cab files and you will see that updating those driver packages becomes a very simple exercise without any importing issues.

I have a video that describes this process here http://www.delltechcenter.com/page/Client+Deployment

8 Posts

May 3rd, 2011 02:00

I did install KB2213600 when the cab files didn't import correctly, however, that just generated a different error. I don't remember what it was exactly as I have since uninstalled the patch, but it was something along the lines of 'general error' when importing the graphics drivers.

1.1K Posts

May 6th, 2011 10:00

I didn't realize that the patch created more issues. I guess that's just more reason to look at creating your driver packages without importing. :)
No Events found!

Top