Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

HELP!!! HP xw4300

Updated: 21 May 2010 | 3 comments
co2castro's picture
0 0 Votes
Login to vote

We just bought some HP xw4300 systems and I can't seem to get it to image. The boot disk works in so far as connecting the system to the network. However, when RDEPLOY is run, the destination drive isn't located.

I suspect this has something to do with the fact that these systems have RAID controllers in them.

How do I add the RAID controller drivers to the boot disk, and does anyone know where I can get the drivers? I see the setup files on the HP website, but they're not in any form I can use (they are self-extracting and self-installing EXE files).

My ultimate goal is to be able to create a boot disk and at boot, start the imaging process so that we can deploy our "gold image" to mass machines.

PXE will not be used.

discussion Filed Under:

Comments

pcalver's picture
08
Jan
2009
0 Votes 0
Login to vote

Adding new SATA drivers to a syspreped image

There are a couple ways we had handled this. One was to switch the BIOS to IDE mode. I don't remember the exact terminology.

The other was to load the image on an older system that worked, add the driver and reseal (re-sysprep) the system.

For the second solution what I did was copy the INF files to the local drive (C:\Drivers\Sata). Then I modified the [Unattended] OemPnpDriversPath in my sysprep.inf to include drivers\sata.

Then in the [SysprepMassStorage] section of the sysprep.inf I added the devices pointing to the correct inf. I have done this with a couple versions of AHCI and ICH drivers as follows. I know I need to some cleanup, I'll get to it im my "spare time". :-)

[SysprepMassStorage]
PCI\VEN_8086&DEV_2829&CC_0106 = c:\drivers\sata2\iaahci.inf
PCI\VEN_8086&DEV_2821&CC_0106 = c:\drivers\sata2\iaahci.inf
PCI\VEN_8086&DEV_2681&CC_0106 = c:\drivers\sata2\iaahci.inf
PCI\VEN_8086&DEV_27C1&CC_0106 = c:\drivers\sata\iaahci.inf
PCI\VEN_8086&DEV_27C5&CC_0106 = c:\drivers\sata\iaahci.inf
PCI\VEN_8086&DEV_2652&CC_0106 = c:\drivers\sata\iaahci.inf
PCI\VEN_8086&DEV_2653&CC_0106 = c:\drivers\sata\iaahci.inf
PCI\VEN_8086&DEV_27C3&CC_0104 = c:\drivers\sata\iastor.inf
PCI\VEN_8086&DEV_24DF&CC_0104 = c:\drivers\sata\iastor.inf
PCI\VEN_8086&DEV_25B0&CC_0104 = c:\drivers\sata\iastor.inf
PCI\VEN_8086&DEV_2652&CC_0104 = c:\drivers\sata\iastor.inf
PCI\VEN_8086&DEV_282A&CC_0104 = c:\drivers\sata2\iastor.inf
PCI\VEN_8086&DEV_2822&CC_0104 = c:\drivers\sata2\iastor.inf
PCI\VEN_8086&DEV_27C6&CC_0104 = c:\drivers\sata2\iastor.inf
PCI\VEN_8086&DEV_2682&CC_0104 = c:\drivers\sata2\iastor.inf
PCI\VEN_8086&DEV_2653&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_2681&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_27C1&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_27C5&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_2821&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_2829&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_2922&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_5029&CC_0106 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_2682&CC_0104 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_27C3&CC_0104 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_27C6&CC_0104 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_2822&CC_0104 = c:\drivers\sata3\iaahci.inf
PCI\VEN_8086&DEV_282A&CC_0104 = c:\drivers\sata3\iaahci.inf

Then I run sysprep and take a new image.

Hope this helps. This ma not be the best and easiest way, but it works.

Patrick
Sacramento Municipal Utility District

jebba's picture
08
Jan
2009
0 Votes 0
Login to vote

This helps, Thanks! What did

This helps, Thanks!
What did you use for your preboot? My WinPE can't fond the disk of the the 7900, and Linux preboot says no express mount found.
Any Thoughts?

pcalver's picture
08
Jan
2009
0 Votes 0
Login to vote

PXE

I use DOS through PXE. It's small quick and I can Multicast if I don't use the UNDI driver. Unfortunately on some of the XW systems the NIC is not using the IDE bus, and I have to use UNDI. Then in DS I use the Distribute disk image task. Then I use replaceTokens on the sysprep to replace %NAME% for the system name. Then I inject the custom sysprep.inf and all of the drivers for the model into the drivers folder. The sysprep.inf PNP path points to all of the driver INF files. Then I have the system reboot and it runs minisetup and already has all of the needed drivers and answers. I have it load aclient in the sysprep after it logs on 1 time as admin. Then I have it join the domain and start loading software. It's kind of an involved process to setup, but I do all the back-end work and our techs only need to drag and drop. I actually even take it a step further and have conditions on my jobs for the different model types so they only have to use 1 job and it figures the model and injects the correct drivers.

Patrick
Sacramento Municipal Utility District