Has anyone seen after an image deployment all the boxes showing this error:

Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
Please check the windows documentation about hardware disk configuration and your hardware reference manual for additional information.

I tried doing an image upload and download. The upload went fine I assume, but every box I deploy down to gives that error message. The only way to fix it reasonably quickly is to break out my ghost image dvds and do them by hand. This 2000 has cost me 3 times as much time as it has saved me.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I wish I could help, but I have little experience with the K2000 (and my company doesn't own one).

If this is a critical issue costing you time and money, I'd suggest calling KACE support. They should be able to help you out much quicker than users on the forums.
Answered 07/01/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
What operating system are you deploying?

What was the partition table like on the source machine for the image?

Is it different on the target machines?

If you recover an image from a machine with hidden partitions, like a Dell Diagnostic partiion, you may find that your boot configuration isn't correct in the image. If you're partitioning the target machine with a single partition, you'll need to modify the image. For Windows XP, you'd need to edit the image and change the boot.ini to reflect the single partition.

Here's how to create a pre-install task that will handle the case where you want to keep the hidden partitions.

http://www.kace.com/support/kb/index.php?action=artikel&cat=57&id=1021&artlang=en
Answered 07/01/2010 by: jkatkace
Purple Belt

Please log in to comment
0
Have you uploaded drivers using the driver harvesting utility or added drivers to the driver cache?

If so delete them. Also try recreating your kbe boot environment.
Answered 07/25/2010 by: CordlezToaster
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share