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

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

hmmm.. no luck... same problem.. i've tried a few things now.. same result.. anything else you guys suggest? Chris

Its a clean OS install. I will remove the drivers today and re-add them just incase missed something. Will report back. Thanks! 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

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

I've solved the problem. The issue was that WinPE required the Vista NIC drivers.

Hey everyone, I found this forum after doing a google search for a computer related problem. Looks like there's a lot of useful info here!

Hi, I'm currently having some problems with deploying an OS using BDD2007 and WinPE. I'm fairly new to this and I understand that BDD2007 is old, but unfortunately its an existing system and it is what I have to work with. The PC model is a HP DC7900, the LTI was working for older DC7900s but it looks like HP have changed the motherboard in this model PC. So the LTI installation works for all the previous models except this one. They use two different deployment methods here, a standalone DVD deployment and a network deployment after booting from disk. I've added drivers within the Out of the Box Drivers section, updated the deployments, burnt the disks and tested. The standalone deployment method works and the build completes successfully. The network deployment will fail after asking me to authenticate to the network with an error "A connection to the deployment share could not be made. The deployment will not proceed" The NIC is an Intel 82567LM-3, Within the NIC driver download I found a folder RIS_INF, I added the driver found in there too but build will still fail at the same point. Any help appreciated. Thanks!