Bootmgr is missing
Hello,
I'm very new to the Kace imaging process. I had 6 training videos I had to watch but unfortunately, they only dealt with setting up the Kbox and nothing to do with imaging.
I've been scouring over the various posts here and trying to pick some brains in my office but I'm lost and unfortunately, not sure where to start to even answer my question.
In a nutshell:
We have an existing machine that was previously built for a learning environment with special software. We had no base image on the Kbox (or our previous Ghost setup), so I sysprepped and captured this as a WIM image (Harvested from C:) and it appears to have gone up fine.
When I try to deploy it back down to another machine of the same make, I consistently get the "Bootmgr is missing - Press Cntrl + Alt + Del to restart" message.
In my various searches of ITNinja on this issue, I seem to keep coming back to a tutorial on imaging 100MB System Partition. This system has:
An unformatted, unlabeled 47MB partition (Active, OEM partition) 100% free of 47MB
C:\ (NTFS Boot, Page File, Crash Dump, Primary Partition) 85% free of 232.84GB
My current preinstallation tasks are:
Create Single Partition
Format C: as NTFS
Install Vista/2008/7/8/2012 MBR
In one instance, we tried a mid level mbr rectify but no matter what I do, I still get the "Bootmgr is missing" error and I'm completely lost and a bit frustrated at this point.
If I can provide more information to try to root this issue out, I will do my best to do so.
If someone would also recommend, basically, a primer on where to start with learning Kace imaging, that would be incredibly helpful.
Please be gentle.
Thanks.
I'm very new to the Kace imaging process. I had 6 training videos I had to watch but unfortunately, they only dealt with setting up the Kbox and nothing to do with imaging.
I've been scouring over the various posts here and trying to pick some brains in my office but I'm lost and unfortunately, not sure where to start to even answer my question.
In a nutshell:
We have an existing machine that was previously built for a learning environment with special software. We had no base image on the Kbox (or our previous Ghost setup), so I sysprepped and captured this as a WIM image (Harvested from C:) and it appears to have gone up fine.
When I try to deploy it back down to another machine of the same make, I consistently get the "Bootmgr is missing - Press Cntrl + Alt + Del to restart" message.
In my various searches of ITNinja on this issue, I seem to keep coming back to a tutorial on imaging 100MB System Partition. This system has:
An unformatted, unlabeled 47MB partition (Active, OEM partition) 100% free of 47MB
C:\ (NTFS Boot, Page File, Crash Dump, Primary Partition) 85% free of 232.84GB
My current preinstallation tasks are:
Create Single Partition
Format C: as NTFS
Install Vista/2008/7/8/2012 MBR
In one instance, we tried a mid level mbr rectify but no matter what I do, I still get the "Bootmgr is missing" error and I'm completely lost and a bit frustrated at this point.
If I can provide more information to try to root this issue out, I will do my best to do so.
If someone would also recommend, basically, a primer on where to start with learning Kace imaging, that would be incredibly helpful.
Please be gentle.
Thanks.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
EdT
10 years ago
Windows 7 has two partitions, and both must be present for Windows to boot. The first partition is around 100Mb in size and is HIDDEN. The remainder of the drive is what you see as the C: drive.
If you image without including the 100Mb partition, it will not boot as bootmgr cannot be found.
Posted by:
genfoch01
10 years ago
If your boot manager is missing because you did not capture the service partition, you can fix that with a mid level task
assuming your OS is on the C drive
create a bat file with the following "bcdboot c:\windows /s c: " and save as rebuildboot.bat or something like that.
go to the k2000 and create a postinstallation task "add new application " from the drop down
set the title to rebuild mbr on c or whatever you want
set the runtime environment "k2000 boot environment (windows) "
then upload the bat file you created in the "file" section
and add the full bat file name in the command line and save the task.
then add this task to your deployment and see if that clears it up.
note: there are other things that can cause the issue you are seeing but this (above) is a solution for for a high percentage of these kinds of errors.
its also worth checking the BIOS settings for "disk operations" on the machine you captured the image from and the machine you are deploying to. if they are not the same you can also get the same error.
for example if disk operations on the capture machine is "AHCI" while the deploy machine is set to "sata" you will get this message.
assuming your OS is on the C drive
create a bat file with the following "bcdboot c:\windows /s c: " and save as rebuildboot.bat or something like that.
go to the k2000 and create a postinstallation task "add new application " from the drop down
set the title to rebuild mbr on c or whatever you want
set the runtime environment "k2000 boot environment (windows) "
then upload the bat file you created in the "file" section
and add the full bat file name in the command line and save the task.
then add this task to your deployment and see if that clears it up.
note: there are other things that can cause the issue you are seeing but this (above) is a solution for for a high percentage of these kinds of errors.
its also worth checking the BIOS settings for "disk operations" on the machine you captured the image from and the machine you are deploying to. if they are not the same you can also get the same error.
for example if disk operations on the capture machine is "AHCI" while the deploy machine is set to "sata" you will get this message.
