/build/static/layout/Breadcrumb_cap_w.png

Can't Deploy OS with K2000 [Client Machine show error “BOOTMGR is Missing Press CTRL+ALT+DEL to Restartâ€]

Dear All,

After I tested Deploy OS with K2000 I got error on Client Machine it show “BOOTMGR is Missing Press CTRL+ALT+DEL to Restart” Please advise me what should I do for solved this issue thanks.

This is step when I tested it.

1.     Manual install Windows 7 (x64) and install all driver

2.     Download Driver Harvesting Utility from K2000 and upload all the drivers to K2000

3.     Update Recache Driver on K2000

4.     Create new KBE from K2000 Media Manager

5.     Create new scripted installation

Thanks.


0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Summary solution for solved this issue for me is 1.I remove image file .ISO of Windows 7 (x64) 2.reupload image file by use DVD Media (not file .ISO)
Posted by: dugullett 12 years ago
Red Belt
0

What are your preinstall tasks? Is this Windows 7?


Comments:
  • Dear dugullett,

    Yes, I use Windows 7 for test and this is preinstallation tasks when I test

    1.Create Single Partition
    2.Format C: as NTFS
    3.Install Vista/2008/7 MBR

    Please advise me what should I do? thanks - manpang 12 years ago
Posted by: jegolf 12 years ago
Red Belt
0

^ Yes, I would check your Preinstallation Tasks. The first 3 I always use are Create Single Partition, Format, and Install MBR...that may solve your issue.

Posted by: manpang 12 years ago
Fourth Degree Green Belt
0

Dear all,

For your information, I think I know my problem already because I use Vostro V131 for test Deploy OS so that mean the problem happen from Driver I guess then if I correct what should I do? Have anyone use this model for test? or use another brand for test with K2000? thanks


Comments:
  • The driver harvesting utility will only get the drivers needed for the KBE. I would add this model to the driver feed or import them manually into \\k2\drivers_postinstall. - dugullett 12 years ago
  • dugullett, the driver harvesting utility can be used to gather all drivers, not just for kbe. However, it puts them all in drivers under the os of the machine it was run from. We recommend moving these into drivers_postinstall under the correctly model name.
    Corey
    Lead L3 Enterprise Solutions Engineer, K2000
    If my response was helpful, please rate it! - cserrins 12 years ago
  • Dear cserrins,

    Thanks you for your comment but I already use "driver feed" to upload driver file .exe to K2 and I already copy to folder \\K2\drivers\kbe_windows_x64 and \\K2\drivers\windows_7_x64 but it still show same error. so please advise me how to do? thanks - manpang 12 years ago
  • Finally, it's the Drivers x3, can't wait for them to appear in the Driver Feed. - Aaron Cool 12 years ago
 
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