Problem with Lite Touch install and LAN driver recognition

[chris]

Hi everyone,

I'm wondering if someone can help me here.

Details below:

OS: Windows XP

Deployment method: BDD2007 Lite Touch Installation

Hardware: HP Mini 5102

The issue here is encountered during bootup into the OS for the first time during the Lite Touch installation.

Upon booting into the OS, the Network (and wireless, and HD protect) drivers haven't been detected and installed by the OS; and hence the build cannot complete.

I added the relevant drivers to Out-Of-Box-Drivers through the BDD console.

There are no network connectivity issues with the WINPE portion of the build, its just that Windows itself doesn't recognise the driver. Device manager comes up with a question mark for the LAN, Wireless and HD protect devices.

The drivers are definately the correct ones as if I update the driver manually, the OS installs it without any problems.

I've tried multiple drivers, including those from the Marvell Yukon site, which is a later version than the one from the HP site.

In the past with Altiris Scripted OS builds I have encountered similar problems where the hardware didn't detect the driver; there was a work around which involved making the new driver folder alphabetically at the top of the list (say making the folder name begin with a '1'). I tried this and it doesn't seem to make a difference here.

Any help greatly appreciated.

Thanks!

Chris

Edited May 31, 2010 by chris

[arwidmark]

The reason it works with the boot image is that is based on Windows Vista (or Windows 7 if you are using the latest MDT version).

You need to make sure to add Windows XP drivers to BDD 2007 for your HP mini PC. A problem you may run into is that XP is trying to inject the Windows Vista Drivers you use for the boot image... In MDT 2010 Microsoft added numerous new features to deal with drivers, so my recommendation would be to upgrade from BDD 2007 to MDT 2010.

[chris]

Hi,

Thanks for your reply.

The driver pack I downloaded from the HP website is actually the same one whether I select Vista or XP.

And as I mentioned, after booting into the OS, if I manually specify the drivers that are in the OOBD folder, it does actually install correctly. It seems like something is preventing the OS from recognising the correct driver during the build process.

Upgrading to MDT is definately happening, however the company has elected to do this later in the year. So at least for the moment, I have to work with BDD.

Would there be anything else I should be looking at? I will re-add the network drivers and retest just to be sure.

Thanks.

Chris

[cluberti]

Is this a flat-file install of a clean OS, or is this a sysprep image? I've had issues with creating sysprep images from (specifically) HP laptops due to odd PNP detection issues afterwards, but work fine from a clean OS deployment.

[chris]

Is this a flat-file install of a clean OS, or is this a sysprep image? I've had issues with creating sysprep images from (specifically) HP laptops due to odd PNP detection issues afterwards, but work fine from a clean OS deployment.

Its a clean OS install.

I will remove the drivers today and re-add them just incase missed something. Will report back.

Thanks!

Chris

[cluberti]

Good luck .

[chris]

Good luck .

hmmm.. no luck...

same problem.. i've tried a few things now.. same result..

anything else you guys suggest?

Chris

[cluberti]

Unfortunately, no. The problem is likely the PnP identification phase failing (either due to Windows or BDD, but my money's on BDD here given the drivers install fine in Windows). Do the wireless or protect drivers require functional chipset drivers to be installed before they'll work? I can't imagine anything else other than BDD is screwing up the detection, or there's something specific about the driver order.

[chris]

Unfortunately, no. The problem is likely the PnP identification phase failing (either due to Windows or BDD, but my money's on BDD here given the drivers install fine in Windows). Do the wireless or protect drivers require functional chipset drivers to be installed before they'll work? I can't imagine anything else other than BDD is screwing up the detection, or there's something specific about the driver order.

I posted this on the MS forums too, but thought I'd post it here again to keep you updated

Unfortunately, this is still an issue.

I tried implementing driver groups and presenting the build with only the Marvell Yukon drivers and it failed at the same point.

I then went through BDD and performed a clean up, manually removing doubled up network drivers that had been installed previously (those folders that had the (1) after it in the OOB Drivers folder). Now the build will fail to connect during the WinPE stage after I attempt authentication.

Does this indicate that the drivers I downloaded from the HP site are incorrect? It suggests that the drivers I downloaded do not work, and it was using some other driver (that I have now cleaned up) to connect to the deployment share during the WinPE phase?

As I stated earlier, whether I select Vista or XP on the HP site, it directs me to the same download for the NIC. I have included these NIC drivers into the OOB Drivers folder. I require Vista drivers for WinPE and XP drivers for the OS.

The behaviour displayed seems to be inconsistent with the changes made?

Chris

Edited June 17, 2010 by chris

[chris]

Update: Issue resolved!

Thanks everyone for the help.

I finally got the driver to install by copying the drivers into the OS source folder: \I386\$OEM$\$1

Then edited the path manually in the Unattend.txt file. So it seems like old methods still work.

NIC will now install and the build completes.

Chris