How to create a Driver Package

[emmathews83]

Hello Everyone,

 

I am trying to create one image for multiple laptops, but now I'm getting stuck on the part that applies the driver package and was wondering if someone could give me a hand on how they did it. Here is what I did:

 

-First I copied the driver folders over from one of the Dell's that I am testing, it's an E6510: Now I copied over the folders that start with an R but the rest were created when I created the Driver package.:

 

,

 

-Next I imported the drivers into SCCM and created a package called Dell E6510 Drivers XP.

 

-After I did this I created a Task Sequence to install the Base Image with the drivers. I added the WMI Query to the step, but I was also trying to use the check box to select a Mass Storage driver but it will not find anything.

 

 

Please help

 

 

[emmathews83]

I went in and edited the install file for the driver now it doesn't give me the copy error it give me the message saying this isn't a trusted driver do you want to continute the install or stop the install. So I click continute the install and it works fine. I still get the popups after I can login to windows, but I will give it a try with checking the 'Do unattended installation of unsigned drivers on Versions of Windows where this is allowed'

 

By the way thanks for all your help so far.

[Greg Ramsey (MVP)]

What model system did you use to capture the .wim file? If that original capture contained any of the same drivers that are on the target hardware, you need to have an entry in sysprep.

 

 

UpdateInstalledDrivers=Yes

 

This goes into the Unattend section of sysprep.inf. See here for more information. http://support.microsoft.com/kb/302577

 

You can dynamically apply this during your task sequence, in the "Apply Operating System" step.

[emmathews83]

I created the image on a E6510, but what I did was only install the ethernet driver. Then I updated everything I wanted for the image. When that was complete, I removed the ethernet driver and deleted the Dell Driver folder that it created when I installed the ethernet driver. This way it was just the windows image with the programs I want, but no drivers. When I did the capture I just saved the .wim file to the C: drive of that machine, then I copied it to the server.

[Greg Ramsey (MVP)]

Is this your first attempt using OSD, or are you deploying others successfuly? For the record, Deploying XP is harder than vista and win7 .

 

Looking at your first image in this post, I see you have GUIDS, as well as R numbers. That driver package source directory should not look like that.

 

If you're in a test environment, I recommend you (from the admin console, delete all drivers, and all driver packages, and start over, then walk through the steps I referenced from delltechcenter - if we can get back to that basic, we should be able to help you better. Use the .CAB download for XP on the 6410 on delltechcenter, and follow that process to import them - don't add anything to the driver package source.

 

oh yea, side note - I would still include this entry in sysprep.inf: UpdateInstalledDrivers=Yes . . . . for me, better safe than sorry.

[emmathews83]

This is my first time using SMS/SCCM 2007 in my life.

 

The driver package has been changed, it looks like this now.

 

 

That is what is created when I created the driver package. The drivers are from that website, but I downloaded the E6510 package instead of the E6410 package.

 

This is what the TS looks like now also.

 

 

Now I run the RunDLL32.exe command because if I don't it will not apply the drivers. But this is also where I get the saying "this isn't a trusted driver do you want to continute the install or stop the install" but I click continue and it installs fine. Then once you login to windows is where I get the popups and I did find out as long as I uncheck the box that says "Always ask before running this file" and click run they don't show up after the restart anymore.

 

[Greg Ramsey (MVP)]

You do not need to run that rundll32 command - there must be some other problem. Did you add the information I mentioned for sysprep.inf?

[emmathews83]

If i don't run the task RunDll32.exe it won't auto install the drivers. I will update the sysprep file and give that a try.

 

Below is a copy of it, is there anything else you think i should add to it?

 

sysprep2.txt

[anyweb]

give it a try, Greg's advice is great

[emmathews83]

Ok since i changed the sysprep file in my image and took out the RunDll32.exe command it does not ask me to click anything anymore for the video driver for the E6510, I added the E6410 and E6500 and that's fine also. The only problem yet is after you login to Windows for the first time I still get these pop ups.

 

 

(One side note I did add the E6410 and E6500 Driver package to my TS last Friday and it never gave me an issue with the video drive like the E6510)

 

I changed the Driver Singing Options to Ignore and Make that the default action and it still has them popup.

 

I found that from this website:

 

Driver Signing

 

 

In the above website I found this:

 

To disable the warning start the Group Policy Editor (Start > Run, type

-gpedit.msc- and press OK) and go to:

 

-User Configuration > Administrative Templates > Windows Components >

Attachment Manager- then set -Inclusion list for low file types- to

Enabled and enter the file types you don't want to be warned about in

the box (for example: -.htm;.exe-).

 

I'm just not sure that's a good ideal or is it? I mean if a virus gets in with a .exe won't it just run it. It works, but I would rather have the user's click the extra step.

[Greg Ramsey (MVP)]

This is all you should have in that sysprep.inf file, and apply it using the "apply operating system" phase - let ConfigMgr handle the rest of the config in that .inf.

 

[unattended]

UpdateInstalledDrivers=Yes