Deployment Solution

I've scripted an install of XP with SP3 on a VM, sysprepped it and deployed the image on new HP hardware (6000 Pro & 6555b) and older (dx2000). None will boot properly, a Stop 7B can be seen on the 6550b. The image will deploy back to the VM OK.

The VM is on VMware workstation 6.5, the scsi0.present = "FALSE" line is in the .VMX file and the .VMDK header has the ide line in it. The disk is set to IDE in the setting for the VM.

The HP machines are set to IDE (not SATA) in the BIOS.

The sysprep.inf file used to do the -reseal and image deploy has a full Mass Storage section, the Mass Storage section is the same whether "sysprep -bmsd" is run on the VM or one of the HP machines.

If I manually Update the driver for the IDE controller in Device Manager on the VM and change it from Intel to "Standard Dual Channel PCI IDE Controller" before I "sysprep -reseal" the image will work on the HPs. But I don't know how to do this using a command line, I really want to leave the user with an easily repeateable image build not requiring any manual steps. I tried Devcon but both the Intel and Standard driver use the same inf file, mshdc.inf, and have the same hardware ID (HWID), PNP0600.

I thought "sysprep -reseal" would unload all the drviers including the Intel IDE one, shoudn't it?

Does anyone know how I can either get this to work without changing the IDE driver to "Standard..." or how I can force the "Standard..." IDE driver through a command line?

Hi,

Have you tried DeployAnywhere option while deploying image on new HP Hardware?

Thanks

hardware vendor.

And I'm not sure how that would help, I'm copying down the correct mass storage drivers but the Sysprep mini wizard isn't gettting that far.

I used the Software Virtualisation Admin tool to make a snapshot of the changes that were done when I manually changed the IDE driver from Intel... to Standard...

It makes a change to HKLM\System\CurrentControlSet\Control\Class\{4d36e96A...}\0000 to replace the Intel... driver with the Standard... IDE driver, fills out HKLM\System\CurrentControlSet\Services\PCIIde with details of the PCIIde.sys driver and extracts the PCIIde.sys driver file to %systemroot\system32\drivers, it wasn't there before. It also takes some entries out of the Critical Drivers Database for some reason. 

I tried the reg changes first and only realised that PCIIde.sys wasn't in the drivers directory at the end, adding it was what finally fixed things but I haven't tested it without the reg changes too.