KACE Scripted Install "BOOTMGR is missing"

We have a Windows 7 64bit scripted install that works on a handful of machines perfectly fine.  When we try to deploy the scripted install to a Dell Latitude D830 it seems to install Windows fine but it just sits at the complete installation step of the windows installer wizard for a very long time then the windows install closes and it goes back to the KACE screen that asks what scripted install to use.  If we try to do anything we get errors that act like the machine is no longer connected to the KACE system (red x's indicating images aren't loading and scripting errors).  We reboot the machine and get a BOOTMGR is missing error.

As stated before this scripted install works on plenty of other machines D630's, E5500's, etc.   It's this one hardware type that we have this happen. 

0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: cserrins 9 years ago
Red Belt

Don't think POs have anything to do with this, and I doubt any midlevel taks, just because you are saying files are missing, so I don't think the install completed.

It sounds like the machine is disconnecting from the network.  Can you go to Recovery | command prompt and try pinging something? Do you have the driverpack from out website installed for your kbe?  If not, I would try that.

Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

  • I went ahead and installed the supplementary driver pack, re-cached and it seems to be working now. - hawt 9 years ago
Posted by: dugullett 9 years ago
Red Belt

I would take all of your post install tasks out and see if that changes the outcome. What mid level tasks do you have?

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ