System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Operating System Deployment
>
OSD - "BOOTMGR is Missing"
OSD - "BOOTMGR is Missing"
- Hi,
I've read the few amount of posts related to my issue but am unable to come to a resolution.
Environment:
Server 1 = Server 2008 - SCCM 2007 SP2 (All Roles) / SQL 2005 (local) / WDS (local)
Server 2 = Server 2003 - DHCP
OSD Components - MDS 2010 - WDS (Server 2008) - AIK 2.0
Goal:
Deploy Windows 7 via SCCM PXE Boot.
I am currently able to pxe boot a client and have the Windows 7 TS begin. It partitions the C: drive, formats it and proceeds. Upon rebooting for the first time, pxe advertisement has expired and the client attempts to boot locally but receives "BOOTMGR is missing"...
I have tried adding all network and storage drivers into a package and then including them in the TS as well as enabling compatibility in the BIOS. I have gone so far as to recreate the deployment but achieved the same results.
Can somebody please shed some light. Thanks!
All Replies
- try setting Option 67 on your DHCP server to \boot\x64\wdsnbp.com instead , does it work ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - I have manually set that as my boot image but that fails to even load PE. I am able to successfully load PE, have the TS start, go so far as applying drivers and then when it hits the "Setup Windows and Configmgr" the installation proceeds to install the video driver because the resolution gets smaller and then the computer restarts gracefully but i am hit with the BOOTMGR is missing every time
I was able to map a drive and copy my log files over and here is the interesting bits i was able to pull
<![LOG[==============================[ OSDSetupWindows.exe ]===========================]LOG]!><time="09:31:16.371+480" date="11-03-2009" component="OSDSetupWindows" context="" type="1" thread="1192" file="setupwindows.cpp:1689">
<![LOG[Command line: "OSDSetupWindows.exe"]LOG]!><time="09:31:16.371+480" date="11-03-2009" component="OSDSetupWindows" context="" type="1" thread="1192" file="setupwindows.cpp:1690">
<![LOG[Installing BOOTMGR bootsector ]LOG]!><time="09:31:16.386+480" date="11-03-2009" component="OSDSetupWindows" context="" type="1" thread="1192" file="bootsector.cpp:63">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="09:31:16.402+480" date="11-03-2009" component="OSDSetupWindows" context="" type="0" thread="1192" file="commandline.cpp:229">
<![LOG[Set command line: "bootsect.exe" /NT60 SYS /MBR ]LOG]!><time="09:31:16.402+480" date="11-03-2009" component="OSDSetupWindows" context="" type="0" thread="1192" file="commandline.cpp:707">
<![LOG[Executing command line: "bootsect.exe" /NT60 SYS /MBR ]LOG]!><time="09:31:16.402+480" date="11-03-2009" component="OSDSetupWindows" context="" type="1" thread="1192" file="commandline.cpp:805">
<![LOG[Process completed with exit code 0 ]LOG]!><time="09:31:16.620+480" date="11-03-2009" component="OSDSetupWindows" context="" type="1" thread="1192" file="commandline.cpp:1102">
Failed to run the action: Setup Windows and ConfigMgr . Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:31:36.885+480" date="11-03-2009" component="TSManager" context="" type="3" thread="1912" file="instruction.cxx:3101">
Windows setup failed, code 31 ]LOG]!><time="09:31:36.869+480" date="11-03-2009" component="OSDSetupWindows" context="" type="3" thread="1192" file="setupwindows.cpp:440">
I was able to open a command prompt (F8) and run diskpart and IT DID in fact have a partition and a formatted C: drive so its not storage drivers or network drivers....
- hmm, did you update your boot.wim images to the dps after installing SP2 ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - After installing SP2, i made sure that the PE image being used was in fact the updated PE in D:\SCCM\OSD\boot\x86\boot.wim. To make sure, i moved the images that were there prior to SP2 to a temporary folder and i made sure to note in the SP2 SCCMSetup.log that it detected AIK 2.0 and that it was exporting the boot images from WAIK into the above directory.
I updated all distribution points (I have 2, the SCCM DP and the PXE DP, both on the same server)
I have verified that the image is posted on the DP and that the install status is Installed. (No errors reported in the status message; Successfull Distirbution)
Here is the error i get in status messages for that particular machine:
The task sequence execution engine failed executing the action (Setup Windows and ConfigMgr) in the group (PostInstall) with the error code 2147500037 Action output: equence\unattend.xml Successfully initialized driver information Command line for extension .EXE is "%1" %* Set command line: "\\SCCM1.domain.COMPANY.COM\SMSPKGD$\U2000026\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Executing command line: "\\SCCM1.domain.COMPANY.COM\SMSPKGD$\U2000026\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Process completed with exit code 31 Windows Setup completed with exit code 31 Entering ReleaseSource() for \\SCCM1.domain.COMPANY.COM\SMSPKGD$\U2000026reference count 1 for the source \\SCCM1.domain.COMPANY.COM\SMSPKGD$\U2000026\ before releasing Released the resolved source \\SCCM1.domain.COMPANY.COM\SMSPKGD$\U2000026exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440) setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707) Exiting with code 0x80004005 Windows setup failed, code 31. The operating system reported error -2147467259: Unspecified error - Follow Up:
I recreated my TS using the basic TS creation wizard as opposed to the MDT TS and it seems to be working correctly. The issue lies somewhere in the MDT TS
Interesting to note that in the BBD.log, the entry states that i am using an x64 architecture but this laptop is x86....
Property CapableArchitecture is now = AMD64 X64
I have a feeling it is marking this as x64 and this is why its failing...any ideas?
BTW, Niall C. Brady , GREAT guides...! Very helpful with other areas - thanks about my guides !
most laptops nowadays are capable of both X64 and x86 architecture, check in the bios
you could also change your boot image by right clicking on your MDT task sequence, choose properties, advanced, and change the boot image from X64 to X86, does that make any difference ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - The boot image i am using is the Windows PE x86...The system pxe boots to the x86 version but I am still having issues with the MDT version of TS. If i make a non MDT TS everything works great. There is something in the MDT TS that is consistently causing the Windows Setup to fail thus causing BOOTMGR to be missing.
I noticed some weird errors in setuperr.log
2009-11-04 10:17:22, Error [0x0603ef] IBS CallBack_SelectImageOrShowUi: There are no matching OS images[gle=0x00000490]
2009-11-04 10:17:22, Error [0x06066d] IBS CallBack_SelectImageOrShowUi: Couldn't decide which Windows image to use and was asked to never show the UI in unattend mode. hr =0x80004005 [gle=0x00000490]
I have also noticed in the setupact.log file there are references to the windows setup halting due to drivers:
2009-11-04 10:01:42, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation. ]
2009-11-04 10:01:42, Info [SETUP.EXE] Called script [X:\WINDOWS\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
2009-11-04 10:01:42, Info [0x070042] DIAG CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
2009-11-04 10:01:42, Warning [0x070041] DIAG DiagnosticDataSendWorker: invalid arguments
2009-11-04 10:01:42, Warning DIAG CallBack_DiagnosticDataSend: DiagnosticDataSendWorker failed, hresult=0x80070057
2009-11-04 10:01:42, Info [0x090095] PANTHR WdsExitImmediate called! Execution will stop, and the queue won't be saved .
2009-11-04 10:01:42, Info PnPIBS: Exiting PnP callback to install drivers on WinPE . ..
2009-11-04 10:01:42, Info [0x09008c] PANTHR SeqExecute -- stopping , since WdsExitImmediate() was called
2009-11-04 10:01:42, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2009-11-04 10:01:42, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2009-11-04 10:01:42, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2009-11-04 10:01:42, Info PANTHR DeleteCriticalSection for pExecQueue->csLock;
2009-11-04 10:01:42, Info CryptoSetup module terminated
2009-11-04 10:01:42, Info [0x0605a6] IBS Requested UI to hide the language and locale selection pages.
2009-11-04 10:01:42, Info UI CallbackWin32UITerminate: Deleted WizardUI
2009-11-04 10:01:42, Info [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)
2009-11-04 10:01:42, Info [0x0601d7] IBS InstallWindows:Error Type = 3211266
2009-11-04 10:01:42, Info [0x090009] PANTHR CBlackboard::Close: x:\windows\panther\setupinfo.
I have uploaded my TS XML file to the following site. Anyway you can take a look. There is nothing that is NON DEFAULT in it...
My MDT TS XML File
Click on the link, then the Download Now (Blue Button) - I'm running into the same exact issue/errors with the basic deploy/capture MDT 2010 TS. I'm using (SCCM 2007 SP2)/(MDT 2010) to deploy Windows 7 (x86)
Have you been able to resolve this? - I could bypass the "BootMGR is Missing" issue by removing Windows product key from my MDT Deploy/Capture TS. (TS: Postinstall --> Apply Windows Settings).
I'm OK with not putting the product key in reference machine for now. I hope this issue wouldn't come up again in deploy TS which I would need to put the key in to deploy the captured image.
I'll keep you posted.
UPDATE:
Here is my Setuperr.log:
2009-11-10 21:29:44, Error [0x060551] IBS Callback_Productkey_Validate: EditionID for product key was NULL.
2009-11-10 21:29:44, Error [0x060554] IBS Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
2009-11-10 21:29:44, Error [0x06011a] IBS Callback_Productkey_Validate_Unattend:Product key did not successfully validate.[gle=0x00000490]
2009-11-10 21:29:44, Error [0x0603c7] IBS Callback_Productkey_Validate_Unattend:Did not pass validation; halting Setup.[gle=0x00000490]
2009-11-10 21:29:44, Error [0x060120] IBS Callback_Productkey_Validate_Unattend: An error occurred preventing setup from being able to validate the product key; hr = 0x80300006[gle=0x00000490]
And the issue is well explained here:
http://blogs.technet.com/askcore/archive/2009/10/05/invalid-product-key-error-specifying-mak-key-in-unattend-xml.aspx
