The First Problem - Windows PE fails to identify the Intel 82567 when using the Dell provided driver.
The Windows PE boot image did not detect the network card and therefore did not receive an IP Address. I've experienced this sort of problem in the past when loading the DELL OEM device drivers. Sometimes they don't support Windows PE all that well. So, after going to Intel's site (http://downloadcenter.intel.com/download.aspx?url=/12197/eng/PROVISTA32_v13_3.exe&DwnldId=12197&ProductID=3003&lang=engeng) to get a driver that works properly for the Intel 82567 nic in these notebooks I was able to get an IP address in PE.
The Second Problem - Mass Storage drivers and Blue Screen of Death
As many of you probably know, XP will bluescreen at minisetup if it cannot access the hard drives and lacks drivers to do so. The root cause of this problem is that the mass storage drivers are not on the image you are applying. Fortunately Configuration Manager makes this easy to fix for us lucky chaps that have it. Unfortunately you still have a 19 in 20 chance of picking the wrong driver. Thank your lucky stars for this blog, as I will tell you which driver you need to use exactly and the steps involved.
- Create a new driver package that only contains Mass Storage Drivers and nothing else. If you really wanted to you could create driver packages for each unique hardware model where you need specific Mass Storage Drivers applied, or you can do what I usually do and just put all mass storage drivers in one. I named mine 'XP Mass Storage Drivers'.
- Download the storage drivers from Dell's site and load them up into the Mass Storage Drivers package.
- Add a new step to your task sequence to Apply Driver Package. I named mine Apply Mass Storage Drivers for Dell E6400, but this will probably apply to other models as well as its Intel based. Under Driver Select the Intel ESB2 SATA RAID Controller. Then for Model select the Intel ICH8M-E/ICH9M-E SATA RAID Controller. Click Ok to save your task sequence.
- Now re-run the task sequence on your E6400 and your bluescreen problem should be resolved.
Don't you just love Configuration Manager!
The Third Problem - Ricoh Drivers
You may notice a base system device that is missing a driver. This is the Ricoh device for your SD/MMC included device. Dell has a driver, but SCCM won't automatically apply it. I ended up using a Lenovo driver to get this to work. I'm pretty sure this is the link I used... but there are several (http://www.downloadpipe.com/drivers/review-Ricoh-MMC-Host-Controller-1110691.html).
The Fourth Problem - Errors with the IDT audio codec driver
You may not run into this one. It really depends on how you build your reference image. I recommend putting your network drivers, and mass storage drivers into their own categories. This way you can build your reference image without loading audio/video drivers at all. If you do load up audio drivers and try to apply the reference image to other systems you may get errors that you cannot resolve. You will also need to apply MS KB835221. This KB is needed on XP whether you are deploying with SP2 or SP3.
So that is a how-to on the Dell E6400 and Dell E4200 for XP. Vista should be easier and I haven't attempted it yet.
Cheers!
8 comments:
Great Post. I wish I would have found this earlier. Would have saved alot of time :)
Agreed, that network issue was killing me.
I did run in to one other issue - the Broadcom USH deal. I can't find a driver that works for this without installing an application (ControlPoint) and installing that application during the task sequence doesn't seem to install the driver. If I run the install again manually, post build...works fine. Has anyone else seen this?
I have the same problem Android, i've found that i can install the application silently by using the command line switch "setup.exe -s" however it fails during SCCM OSD with the error......
"Installation failed with error (0x80042000)"
Which then follows on to say.....
"Failed to run the action: Install Control Point Security.
Unknown error (Error: 80042000; Source: Unknown)"
However once i'm in Windows and i run the application with the install parameter setup.exe -s it will install without an issue
.......i thought i'd sign up for a Google account instead of posting anonymously ;-)
I think i've cracked this Broadcom USH Control point device problem.
Here's how, i let SCCM install my windows image, once i logged on i was prompted about new hardware.
The new hardware is the two Dell / Broadcom USH devices (Control point security).
I manually installed the application from the dell driver website (Dell_ControlPoint-Security-M_A11_R210495.exe)
Once installed it created two folders in "Program Files" they were as follows....
"C:\program files\Dell\Security Device Driver Pack\Microsoft CCID Smarcard Reader"
and
"C:\program files\broadcom corporation\broadcom ush host components"
I copied the driver files from both locations and added them two my E4200 driver package, now when the driver package is applied during OSD the Control Point devices are installed.
And that's it working :-)
Any questions let me know, or get me on msn "chirpsh@hotmail.com"
This blog was a lifesaver! I couldn't figure out why XP 64-bit was BSOD'ing after half a second, but #2 was what I needed.
However, I did follow the steps and still had 2 hours of troubleshooting until it dawned on me to look at the BIOS. Sure enough, the E6400 I was working on was set to AHCI instead of SATA, so I was still getting BSOD's. Once I changed it to SATA in the BIOS and tried to deploy our image again, it worked!
Thanks again :)
Steve awesome thanks for the assistance. I have the same issue with the E5500. I downloaded the Vista drivers and applied the same principle.
But it continues to fail at the "finding valid network adapter part" Is there a generic I should add to my boot image?
If yes can you send me a url
hey,
I noticed in this blog that youve selected the raid driver as opposed to the AHCI driver - is this because it is running in RAID mode, or are you avoiding some kind of intel mismatch of driver?
having similiar isues with a lenovo t61 at the moment.
Ltd Resources, Thank you!
That worked perfectly.
(Thanks Steve for the blog :-))
Post a Comment