hafka
asked on
Sccm OS deployment: Bootmgr is missing.
I'm trying to deploy Vista 64bit Enterprise with SCCM.
I've added the Operating System WIM-image to SCCM and distributed it to distribution points, I've made task sequence and advertised it to a collection where is a computer added by MAC association. I've also made a bootable USB stick to access SCCM infrastructure.
When I boot from usb stick everything goes fine, correct advertisement is found and installation starts. When system is booted during the installation I get this error: BOOTMGR IS MISSING.
I suspect that the problem is that there are no correct Diskpart commands. These are the commands I used when Vista was deployed without sccm:
diskpart
select disk 0
clean
create partition primary
select partition 1
active
format
exit
How can I add these commands to task sequence? Or is it possible that the problem is something else?
sccm-os-deployment.png
I've added the Operating System WIM-image to SCCM and distributed it to distribution points, I've made task sequence and advertised it to a collection where is a computer added by MAC association. I've also made a bootable USB stick to access SCCM infrastructure.
When I boot from usb stick everything goes fine, correct advertisement is found and installation starts. When system is booted during the installation I get this error: BOOTMGR IS MISSING.
I suspect that the problem is that there are no correct Diskpart commands. These are the commands I used when Vista was deployed without sccm:
diskpart
select disk 0
clean
create partition primary
select partition 1
active
format
exit
How can I add these commands to task sequence? Or is it possible that the problem is something else?
sccm-os-deployment.png
Is the system partition set active?
ASKER
noxcho: Is the system partition set active?
Probably not, where in the task sequence can I verify this?
Probably not, where in the task sequence can I verify this?
Normally the system you use as image source should have the active flag on system partition.
At this step:
"When I boot from usb stick everything goes fine, correct advertisement is found and installation starts. When system is booted during the installation I get this error: BOOTMGR IS MISSING."
-Boot the machine from Windows installation DVD and see via Diskpart if the system drive is set active.
At this step:
"When I boot from usb stick everything goes fine, correct advertisement is found and installation starts. When system is booted during the installation I get this error: BOOTMGR IS MISSING."
-Boot the machine from Windows installation DVD and see via Diskpart if the system drive is set active.
ASKER
Output says that the partition is active.
diskpart0.png
diskpart0.png
ASKER
Here is more diskpart output:
diskpart1.png
diskpart1.png
Do you remove USB stick when restarting?
Bootmgr is missing normally refers to missing active partition where Boot folder is residing.
Bootmgr is missing normally refers to missing active partition where Boot folder is residing.
ASKER
Same error message comes when usb stick is removed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I added a file in the scripts folder called Diskpart.cmd and put the code you had.
I added a task sequence right before the format and partition disk that calls it using
%deployroot%\scripts\diskp
It doesnt' seem to work, how were you able to get this in the task sequence??
I added a task sequence right before the format and partition disk that calls it using
%deployroot%\scripts\diskp
It doesnt' seem to work, how were you able to get this in the task sequence??
ASKER
If previous OS does not exist I have noticed that it is easiest to run those commands by pressing F8 and writing them in command prompt. Of course there might be a better solution but I just gave up.
If previous OS exists and there is bootable c-drive then those commands are not needed.
If previous OS exists and there is bootable c-drive then those commands are not needed.
I did some more testing and the reason mine didn't work was because of the product key, removing the product key resolved the issue
ASKER