Driver Management (Part 1) - Configuration Manager

re: Driver Management (Part 1) - Configuration Manager

Björn Axéll — Fri, 15 Feb 2008 14:16:16 GMT

Hi Ben

Thanks for an exilent post, looking forward to the WD part.

Thanks!

Björn

Ben Hunter on Driver Management

Joseph Hinkle at MyITForum.com — Fri, 15 Feb 2008 20:45:16 GMT

Ben put together a really nice artice on driver management in MDT and ConfigMgr. File this one away!

re: Driver Management (Part 1) - Configuration Manager

Or Tsemah — Sun, 17 Feb 2008 15:50:01 GMT

Do you recommend using the "Apply Driver Package" in conjunction with "Auto Apply Drivers" ?

I've tried to use it after the "Auto Apply Drivers" Step to install the more "Problematic" Drivers which the previous step didn't recognized (Like Nvidia's 6100 Driver instead of MS's Nvidia 6100 WDDM Driver) but with no luck, The MS Driver allways took over ispite the fact that nvidia's driver were Newer\Better

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Mon, 18 Feb 2008 09:54:52 GMT

In this case I would recommend installing the Nividia driver using an application.

If the installer is an installshield installer, create a custom install file that suppresses the reboot.

Record an answer file first by extracting the source package to a folder (mine is extracted to C:\NVIDIA\WinVista\169.25)

Then run setup and record an .iss file with all the options required.:

C:\NVIDIA\WinVista\169.25setup.exe -r -f1C:\NVIDIA\WinVista\169.25\nvidiasilentsetup.iss

You can silently install every time thereafter with:

C:\NVIDIA\WinVista\169.25setup.exe -s -f1C:\NVIDIA\WinVista\169.25\nvidiasilentsetup.iss

An .iss file example follows, at the end you should note the BootOption (0 means no reboot):

[InstallShield Silent]

Version=v7.00

File=Response File

[File Transfer]

OverwrittenReadOnly=NoToAll

[{EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-DlgOrder]

Dlg0={EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-SdWelcome-0

Count=2

Dlg1={EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-SdFinishReboot-0

[{EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-SdWelcome-0]

Result=1

[{EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-SdFinishReboot-0]

Result=6

BootOption=0

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

CCA — Mon, 18 Feb 2008 22:31:08 GMT

Ben, when you say 'injected' as for the apply driver package, do you mean unused drivers are actually statically in the driver store? Or is this only for the pnp scan and once the OS is installed these are not found on the Host?

Thanks

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Mon, 18 Feb 2008 22:45:39 GMT

Hi CCA,

By injected I mean that the drivers are in the driver store. This means they are available when a device is plugged in later.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Bzwart — Tue, 19 Feb 2008 00:12:42 GMT

Ben we have been using almost the same concept however we created a Vista X86 driver package and Vista X64 Driver package. The reason for this is we are maintaining drivers for about 8 different Dell models that share a lot of the same drivers. For example if I add the Dell Optiplex 755 Drivers this will also use the same chipset drivers as several other Dell workstation models. The problem here is SCCM lets you add the drivers to the repository once and if you accidently add them again it errors out. The only reason why we would add them again is it is much easier to create a packge and point it to a folder with all the appropriate drivers for a certain model rather then hunt and peck looking for the drivers from the repository.

This also has it down-falls. Since everything is associated to 2 groups X86 and X64 it may cuase issues by Vista selecting a wrong driver however this has not happend yet. You are also injecting a lot of drivers not needed for that model. So here is an example of what I am referring to, when adding drivers for a computer that may allready have them in the repository you get the errors indicating it allready exists. Well this is a real pain in the ass if I have to go and manually add every single chipset driver that may be needed for a certain model. Maybe chipset makes sense to create a seperate category or even use application packages for these?

I would like to follow your method however I was curious how you deal with drivers that are the same driver across muliple models?

Thanks

Error: Some driver(s) can not be imported successfully. Please see following details.

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Tue, 19 Feb 2008 00:32:20 GMT

Hi Bzwart,

You are correct. If the driver has already been imported then you will need to manually add it to the driver package. This can be a hassle, but at least you only have to do it once for each model type.

Thanks

Ben

re: Driver Management (Part 1) - Configuration Manager

Rich — Fri, 29 Feb 2008 20:56:52 GMT

Hi Ben,

Looking forward to your post on this process with MDT/BDD!

Thanks!

Rich

re: Driver Management (Part 1) - Configuration Manager

Rich — Fri, 29 Feb 2008 23:18:28 GMT

Ben,

What is the suggestion for installing Common Windows XP update modules (ex. Q889816, Q909667) or the Universal Audio Arch drivers?

This is an element of my task sequence that I need to cleanup a bit before I roll MDT out. I appreciate your feedback.

Thanks man!

Rich

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Sun, 02 Mar 2008 05:00:14 GMT

Hi Rich,

I like to include these patches in the base im age.

I just create another application to install them.

That way I don't have to worry about installing them for every client that requires them.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Rich — Sun, 02 Mar 2008 19:11:06 GMT

Hi Ben,

Sounds like I should be bringing down my captured WinXPSP2 Image and adding these updates such as the UAA High Def Audio class driver to my gold image, then recapture, and redistribute to MDT?

I was sort of confused with what you were trying to get at when you say you create another application to install them.

Thanks brotha!

Rich

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Mon, 03 Mar 2008 06:03:53 GMT

Hi Rich,

I like to create an application for each task that I perform when creatig an image.

So what I would do here is create an application with source files. The source files would be the patches. I would then write a vbscript that installs these patches. The command line for ths application would then run the vbscript.

I then add the application to the task sequence.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Old_Chicago — Mon, 03 Mar 2008 18:14:35 GMT

Ben,

I understand now what you meant earlier in relation to writing a script to execute the install of the patches. I bring my XP gold image down every 3 months to update the capture with security updates. At that time, I see if there is anything else that I could add to the image, such as hotfixes, and the items mentioned above.

Is there anything wrong with doing it this way, opposed to adding them in via task sequence?

Rich

re: Driver Management (Part 1) - Configuration Manager

Old_Chicago — Mon, 03 Mar 2008 21:30:04 GMT

Ben,

I've had an issue with installing a video driver for an HP 8510W w/ MDT. For some reason the driver does not want to inject. The driver is an Nvidia v156.31 (sp36726.exe) from HP's website. If I had install the driver it loads just fine.

I'd rather not have to add this driver and install as I do the rest of my "bad" drivers. Is there any other way around this using MDT?

Thanks,

Rich

re: Driver Management (Part 1) - Configuration Manager

Rich — Tue, 04 Mar 2008 22:18:33 GMT

Hey Ben,

Thanks for your response. I wanted to follow-up with you regarding driver management in BDD/MDT. You have a fan of the deployment guys blog that is eager to see the post. Let us know when we can expect any information regarding the post. :)

Thanks,

Rich

re: Driver Management (Part 1) - Configuration Manager

Greg — Wed, 05 Mar 2008 03:50:32 GMT

Hi,

Thanks for the article.. very well written. I am trying to install a network card driver and am still experiencing issues. From what I can see, it is downloading the drivers from the driver package fine but it doesn't actually install it. When the image comes online, the network card appears as an unknown device. When I go through the process of installing the driver through the wizard, it actually finds the driver in the downloaded location (c:\drivers\2). Am I doing something wrong here?

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Thu, 06 Mar 2008 00:46:15 GMT

Hi Rich,

I have seen all sorts of weird issues with drivers. Try adding the following to your sysprep.inf file whe you create your master image:

[Unattended]

UpdateInstalledDrivers=yes

Here is some more info on what it does:

http://technet2.microsoft.com/windowsserver/en/library/4dba14f3-76e1-4a9e-b67a-3a93230f63071033.mspx?mfr=true

Also your method of updating patches is fine.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Thu, 06 Mar 2008 00:47:39 GMT

Hi Greg,

I would suggest that you try the method in my previous reply to Rich and see if that works.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Old_Chicago — Thu, 06 Mar 2008 21:39:46 GMT

Something very strage just happened. I added the entry to my sysprep.inf and now during Mini-Setup I receive an error "Setup cannot copy the file nvsvc32.exe. Ensure that the location specified is correct, or change it an insert the Nvidia Windows 2000/XP driver library Installation Disk 1 in the drive you specify."

It then references to Copy the files from: C:\drivers\display\nvb 6.14.11.5631.

Any idea on where I can go from here? Thanks man!

Rich

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Sat, 08 Mar 2008 11:27:22 GMT

Hi Rich,

Does that file exist in the driver folder?

You should also look to see if this driver is in the driver package itself?

This sounds like a driver that may have to be installed as an application.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Rich — Tue, 11 Mar 2008 00:02:39 GMT

Ben,

I'd love to see an article on installing BAD drivers in MDT. In particularly determining silent switches for BAD drivers that you have to add as applications in MDT.

I'm building out my Task Sequence in MDT for an HP8510W. I'm finding by the time that I go through and find all the additional drivers that need to be installed (3D Drive Guard, BlueTooth, FingerPrint, DVD, Quick Launch Buttons, etc. - It's very time consuming. Then I have to find the silet installs, test them and add them to Task Sequence.

Is there an easier way? I'm using a captured WinXPSP2 image for my deployments.

Just a suggestion, I'm sure others out there have this problem.

Thanks,

Rich

re: Driver Management (Part 1) - Configuration Manager

Nico — Tue, 11 Mar 2008 18:26:27 GMT

Ben,

When are you gonna post Part 2 of the Driver Management?

I'm very interested!! Thanks

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Wed, 12 Mar 2008 04:35:15 GMT

Hi Rich,

I will cover this in my next post :).

I just have to find the time to finish writing it.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Jared Wetmore — Wed, 19 Mar 2008 20:44:15 GMT

MD. BDD part 2 blog entry would be great. Ben, do you expect to have it done any time soon ? thanks in advance.

re: Driver Management (Part 1) - Configuration Manager

mwest — Fri, 11 Apr 2008 22:37:46 GMT

Hey guys,

Great blog, been really informative so far. When can we expect to see Part2 for the MDT 2008? I've been trying to deploy a captured WIM of XP and add my Out-of-Box Drivers but can't for the life of me get them to work.

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Sun, 13 Apr 2008 12:36:03 GMT

I am working on it now :). So it shouldn't be too long.

So much to do so little time :(.

Ben

re: Driver Management (Part 1) - Configuration Manager

mwest — Wed, 16 Apr 2008 22:47:41 GMT

Looking forward to it. In the mean time, here is the issue I'm having:

I'm trying to deploy a Windows XP WIM image to a Dell Latitude D610 using the MDT 2008. The image was captured from the laptop with no drivers added, not sysprepped. I'm trying to deploy it back and have it install all of the drivers for the laptop. I've added the drivers to the Out-of-Box Drivers in the Distribution Share and created a group for the drivers, they also happen to be the only drivers I've added at this point. After deploying the image and going back into Windows, none of the drivers have installed. I've also copied them to the $OEM$ share with no luck. I've been searching for a solution for this for about a week now but it seems no one has had an issue with this and can only find the standard answers of adding the drivers to the Out-of-Box drivers and $OEM$ share. I have not made any modifications to my Task Sequence. I attempted adding the LTIapply.wsf script after the Install Operating System task in hopes that it would copy the drivers before rebooting, but alas no luck. I apologize if I've just confused you, I'm still pretty green to the Deployment Desktop work after having worked with Image X for the past year and a half.

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Thu, 17 Apr 2008 03:17:37 GMT

Hi Mwest,

I would suggest that you should sysprep the machine before you add it into MDT. This could be causing some of your issues.

The out-of-box process should work for most drivers witout you needing to do anything special.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Andrea — Thu, 17 Apr 2008 18:37:32 GMT

Ben- First can you send a link,or post the link for the setup logs blog you have? I can't find it. I've used your blog for mass storage drivers and am having an issue with the machine just re-booting after deploying a captured image.I can boot from the cd and look at the logs and the setup api log has a couple failures on 3 diff devices. All these devices are in the out of box drives and should be in the c:\drivers folder in the captured image, which sysprep has the path for. What else can I do to troubleshoot this problem? Also, MDT 2008 has a task in the client std task sequence to resolve the uber bug problem. I'm not sure a lot of people know that. It's disabled by default. This link tells how to fix a problem in the script, but I found that with MDT 2008 the script was modified and looks ok.

http://blogs.technet.com/msdeployment/archive/2007/11/22/workarounds-for-two-bugs-in-microsoft-deployment.aspx

Driver Management (Part 2) - MDT 2008

Rod Trent at myITforum.com — Thu, 17 Apr 2008 22:50:51 GMT

I am often asked what the best way is to manage drivers with both BDD/MDT and ConfigMgr. With this in

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Sat, 19 Apr 2008 02:27:42 GMT

Hi Andrea,

Here is the link you are looking for:

http://blogs.technet.com/benhunter/archive/2007/06/16/bdd-2007-understanding-bdd-logs.aspx

Your issues sounds like it is the uberbug issue but it could also be related to the HAL or Mass storage drivers.

Are you using MDT or ConfigMgr for deployment?

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

jarod.han — Tue, 29 Apr 2008 03:47:38 GMT

When I used MDT 2008 Deployment Operating System sometime new NIC can't loading , because some driver in PE2.0 is older

HOW can add new driver or replace old driver

re: Driver Management (Part 1) - Configuration Manager

Daniel Oxley — Wed, 30 Apr 2008 00:54:19 GMT

Jarod,

You can add new drivers to be included in the WinPE image via the drivers section in the MDT console. Then, in the properties of the deployment point you can configure the creation of the WinPE ISO file to include extra network drivers, video drivers and system drivers.

HTH,

Daniel

re: Driver Management (Part 1) - Configuration Manager

Andrea — Wed, 30 Apr 2008 14:33:10 GMT

Hi Ben- problem resolved. Something messed up in the task sequence or typo in the unattend. Re-created all from scratch and no sata drive problem- no driver issues (except the HD audio thing which I can handle) life is good. You guys are a fantastic resource for all of us who don't have a lot of hours and need answers. Tanks a million.

;)

andrea

re: Driver Management (Part 1) - Configuration Manager

Rob — Tue, 13 May 2008 12:44:35 GMT

Great blog post!

Is it a good idea to manage all non hardware dependent drivers (scanners, imaging, cameras etc) in a single package (to be included in the driver store for all Vista workstations) and what's the best way to manage driver updates after deployment?

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Fri, 16 May 2008 12:36:03 GMT

Hi Rob,

The best method of doing this would be to advertise a taks sequence that applies a driver package containing these drivers. Then advertise this task sequence to the clients.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Jared Wetmore — Thu, 29 May 2008 21:14:43 GMT

Ben,

Any chance you ahve done this type of blog for litetouch driver injection? I dont cm, and trying to use the driverpath001= in cs.ini to point to specific make/model/architechure wmi calls. any idea how I can get this same process or work for a wmi call of the OS diffecence of Xp pro, vs Vista so i could use the same process ? something like...

driverpaths001=\\servername\share\%OS type %\%architechure%\%model% ?

what would the %os type % wmi call be ? i can seem to figure that out.

thanks

JAred

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Thu, 29 May 2008 23:01:42 GMT

Hi Jared,

The seconnd part of this post that covers Lite Touch is here:

http://blogs.technet.com/deploymentguys/archive/2008/04/17/driver-management-part-2-mdt-2008.aspx

Determining the OS type at driver injection time cannot be done via WMI as the OS is not loaded yet. You could use the IMAGEBUILD value gathered by MDT to determine the OS type. You would probaly need to include some kind of script in your Task Sequence to translate the values returned into something easier to use.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Patricio — Thu, 12 Jun 2008 15:36:35 GMT

Hi Ben,

is there any actual limits or best practices for how many "Apply driver Packages" that can be put into a Task Sequence?

Let's say you need to support 30 (or more) different computer types, then there will be a lot of "Apply driver Packages" for both nice and and bad drivers ?

Thanks in advanced!

/Patricio

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Sun, 15 Jun 2008 12:30:14 GMT

Hi Patricio,

There is no easy answer to this question. It really is completely dependent on your environemtn.

I do not no of any physical limits for this process. I would just apply logical limits based on management of the task sequences.

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Andrea — Tue, 14 Oct 2008 16:27:20 GMT

Well, I sent soemething out yesterday,but thought I'd clarify. I'm trying to boot win pe on a DELL E6400. When I specify the all driver group (which includes all the network drivers including WiFi, win pe comes back and says it can't connect and ipconfig shows only the wireless and gives me a DHCP error. If I disable the wireless than Winpe comes back and says the device has no driver installed- and gives the correct dev id for the nic-I've verified that the driver is there in all driver group. I have the additions to the startnet command file and have through my whole desktop imaging. I've had no problems with any other machine with nic drivers and win pe. I've tried adding a separate group and just telling Win PE to use that group. I've deleted the wireless driver from all the groups in case there's a problem. No other driver has those device ID's from that driver in it.

Not sure where to go from here.

Any suggestions?

Andrea

re: Driver Management (Part 1) - Configuration Manager

Andrea — Fri, 17 Oct 2008 14:40:14 GMT

My fault- used the XP driver that shipped with the machine- Forgot that I needed the vista driver for Win PE- All happy again. :)

Andrea

Session 6: Questions and Answers

News and Updates from the MCS Talks Team — Fri, 24 Oct 2008 01:54:49 GMT

The following post recaps on the questions we covered off during last weeks webcast on desktop deployment,

re: Driver Management (Part 1) - Configuration Manager

Rudi — Thu, 11 Dec 2008 01:48:23 GMT

Hi Ben,

Concerning the installation of the "Bad Drivers": is it possible to download and execute these packages, instead of running from the SCCM Distribution point?

Very good article! helped us a lot,

Rudi

re: Driver Management (Part 1) - Configuration Manager

Dustin Mobley — Tue, 23 Dec 2008 02:46:34 GMT

Listen. I'm trying to apply an image to a Compaq 6730s and not having much luck. It seems to start working and then the next time I check on it, i got a BSOD error ending in 7B it goes by so fast, but looks like 0x0000007B.

I'm thinking its a driver issue, however I'm pretty sure that I have downloaded all the drivers from the HP site. What am i missing?

re: Driver Management (Part 1) - Configuration Manager

BenHunter — Fri, 23 Jan 2009 09:36:39 GMT

Hi Dustin,

A 7B error suggests that you have a mass storage driver issue.

Have you tried add mass storage drivers to your image as detailed in the following blog:

http://blogs.technet.com/benhunter/archive/2007/07/12/bdd-2007-integrating-mass-storage-drivers-into-your-xp-image.aspx

Thanks,

Ben

re: Driver Management (Part 1) - Configuration Manager

Brian Hall — Thu, 16 Jul 2009 19:11:28 GMT

Thanks for this post. Do you have a similar walkthrough for MDT 2010 Beta 2? I'm trying to do hardware-specific driver injection for a Windows 7 deployment. Thanks!

re: Driver Management (Part 1) - Configuration Manager

Louis Dawso — Wed, 02 Dec 2009 12:46:00 GMT

I have stuggling with running the ATI and Nvidia driver setup during a XP deploy task sequence. The driver installs OK when I run it interactivly via a advertised program. I get the following error when it runs in the task sequence:

~~~~~~~~~~~~~~~~~~~~~~~~~~

The task sequence execution engine failed executing the action (Install ATI Radeon X550 Graphics Driver) in the group (Hardware Based Applications) with the error code 50

Action output: . The operating system reported error 50: The request is not supported.

~~~~~~~~~~~~~~~~~~~~~~~~~~

The command line i'm using is the following:

Setup.exe -s -SMS -f1"setup.iss" -f2"c:\Windows\temp\RADEON.log"

I found the solution. The command line looks something like this:

setup.exe -s -f2c:\drivers\nvidia.log

For some reason you need to drop the -f1setup.iss and -SMS switches. I also worked out how to install different drivers depending on what model of graphics card is installed. This is an issue for us since the same computer Model could have different graphics cards. Just work out what PNPiD your graphics cards are. eg PCI\VEN_10DE&DEV_0402&SUBSYS_043910DE&REV_A1\4&196AFE53&0&0008

Trim off the sub-revision ids a like this VEN_10DE&DEV_0402

Creat a Package and install it in your task Sequence after the apply Drivers section.

Now in your task sequence step set the WMI condition to query the PNPdeviceID like this:

SELECT * From Win32_PnPEntity WHERE PNPDeviceID LIKE "%VEN_10DE&DEV_002C%" OR PNPDeviceID LIKE "%VEN_10DE&DEV_0171%" OR PNPDeviceID LIKE "%VEN_10DE&DEV_01D1%"

This way you can install the right BAD driver devending on what PNPid the hardware has, which is much better than just the Model.

Louis