K2000 - deploying to different hardware
ok, I'm starting to pull my hair out now....
I've got an image setup for a specific HP model PC. I used driver feed builder to create the relevant driver share for this model on the k2000. The image runs perfectly on PCs of this model, the image deploys, minisetup runs and arrives at the login page, sweet.
So I tried to deploy on a different HP model PC, first I ran driverfeed builder on it to create the driver share, then I deployed the image. I can see the correct drivers being installed but when I reboot instead of minisetup running I get to the safe mode screen and the pc gets caught in a loop, booting in safe mode shows it getting stuck on mup.sys.
I have the image set to run driver_feed_mid_task.bat as a mid level task and install drivers.exe to run as a post installation task.
Been putting off updating to 3.5 but maybe I should?
Answers (2)
Using the HAL tasks mentioned in the Link above should work. For some more information on which HAL you may need to use, check out the first half of this article. It may just come down to choosing a new HAL when creating your system image to maximize support.
http://www.vernalex.com/guides/sysprep/hal.shtml
Is this a WinXP image? If so, XP images are hardware dependant per the chipset unless you utilize HAL injection.
Comments:
-
http://www.kace.com/uk/support/resources/kb/article/hal-injection-in-30 - mpace 10 years ago
-
yes they are win xp images, I thought the chipset drivers took care of the hal. At least that's how acronis works. This could be a dealbreaker as far as deploying winxp with kace goes.
So 'd need t get all 6 versions of the hal.dll plus all the mass storage and plug and play drivers for each machine I want to deploy to? Plus they'd need to be extracted to the image for sysprep to use? - babaton 10 years ago
