Altering HP OEM image before firstboot

[i686]

I have a case where the task is to alter 250+ HP laptops with OEM factory image before firstboot. The purpose of this is to be able to use the preinstalled image of Win 7 Pro x64 on the laptops instead of using a generic VLA installation image (don't ask why).

Is there any way to modify the SetupComplete.Cmd or any other pertinent scripts/reg keys that the Windows OEM Preinstallation Kit or sysprep is using or any custom HP firstboot scripts so the bloatware and custom HP settings (except drivers) are not being installed or applied?

 

[Bill2]

Newer HP machines have a recovery option called Minimised Image Recovery. Running this from the HP recovery solution leaves behind only the OS, drivers, and some minimal HP software but gets rid of most bloat. Depends on whether your machines came preloaded with this option.

http://h30434.www3.hp.com/t5/Deskto...-Install-Windows-7-Recovery-Discs/td-p/394461

Other than that, you could adopt the standard deployment route- make a template image on one machine by stripping all bloat, then sysprep, capture the image and apply. This thread has a problem similar to yours.

Sysprep'ing an OEM Windows 7 image for WDS - Spiceworks Community

Note the requirement of a VL.

 

[theog]

+1 Bill.
Nice find for HP/Compaq users.

 

[i686]

Thanks for the feedback so far. A follow up question is this: What tools/scripts are HP using at firstboot to install all of their crapware? Cant find much in SetupComplete.Cmd or registry files. Runonce entries? Any other sysprep scripts that can invoke post-sysprep commands/exe/bat/etc.? The point is to try to disable the HP scripts in the firstboot/sysprep/waik process. Stil bloatware in the minimal install though.