Bootmgr missing - windows 2008 server
Hi Guys,
I set up a windows 2008 server image deplyment in Kbox2000. I uploaded the ISO through K200 meda manager to Kbox. THen this is what i did.
I created a wizard attended file.
and than added the following Pre installations tasks
Create a single partition
Format C: as NTFS
Install Vista/2008/7 MBR.
I tried in 3 machines and it goes to the process of building and then after a bootup i get:
BOOTMAGR is missing
CTRL+ ALT+ DEL
Please let me know what i'm missing
Answers (4)
You should be able to boot using a 64 bit KBE. The real question is on the machines that you are deploying to do they have a raid card, are they destops or virtual machines? The reason I ask is that you may be missing drivers for the raid controller for Server 2008 and you may need to add them using the driver feed or the driver feed builder for non Dell systems.
Comments:
-
what is the rule? is it also as long as it is pe2.0 or above for 2008/vista pe2.1 for 2008r2/win 7 - SMal.tmcc 11 years ago
-
I believe you want to be using pe 3 or 3.1. They may need to download and install the latest version of WAIK for Win7 but it should work. It is also correct that the number of partitions they captured from could be different from what they are applying.
I would check the number of partitions,
the drivers for the raid controller (if one is in use),
try using bcdedit to correct the boot information - Timi 11 years ago-
Agree, I use 3.1 just for the drivers and updates, I think the default boots that come with the k2000 are 3.0 - SMal.tmcc 11 years ago
-
Correct, KBE uses WinPE3 out of the box but Dell KACE Support puts of a supplemental driver pack that expands the compatibility of WinPE3 quite a bit: http://www.kace.com/support/resources/kb/article/kbe-driver-pack-boot-environments - mpace 11 years ago
I didn't capture a server image. DO i need to do that. I thought i could just upload the ISO to the KBox 2000 and use the sam create single partion used for Windows 7.
Comments:
-
I saw image deployment and missed it is scripted. boot with the same boot you are using for the script and from the main screen choose recovery, command window. Then step thru the disk process manually to see if the works or you get some error.
first step is open diskpart and enter the following commands
select disk 0
clean
create partition primary
select partition 1
active
assign
exit
then
format /q /y /fs:ntfs c
then
bootsect.exe /NT60 c:
see if you get any errors - SMal.tmcc 11 years ago -
I am thinking you may have to create a 2008 boot env for the commands to be compatible - SMal.tmcc 11 years ago
Agreed that this sounds like a missing driver for the storage controller. Find out what storage controller is on that system, add the driver files (the INF and associated files) to \\k2000\drivers\kbe_windows_x64\, recache the drivers, build a new 64-bit boot environment and try the 2008 deployment using the new KBE.
You can also boot into your current 64-bit KBE and choose Recovery > Command Prompt. From the prompt you can run a command called drvload and target the driver INF to load it temporarily. This is useful for testing as you can avoid the KBE rebuild process until you can zero in on the correct driver that needs to be added permanently via building a new KBE.
K1000 KKE's: https://support.software.dell.com/k1000-systems-management-appliance/kb?k=KKE
Comments:
-
I was looking at the point he ran into problems. He is getting thru install okay but dies on reboot. So wouldn't the missing driver be in the deployment not the pxe env? - SMal.tmcc 11 years ago
-
http://technet.microsoft.com/en-us/library/cc766485%28v=ws.10%29.aspx - SMal.tmcc 11 years ago
-
I've seen it unable to mount the hdd in PXE and I've seen it behave as the problem described. Also there might be a hdd emulation in the BIOS that is preventing the MBR from getting read correctly. - mpace 11 years ago
-
thanks for the info. - SMal.tmcc 11 years ago
I forgot to mention guys . im testing the image on a old laptop( precision M6400) . i have installed Windows 7 image on that laptop without a problem. And Boot environment was update by the person that was hndling KBOx before he left the company , about 3 months ago.
Thanks