locked
SCCM OSD Deployment - Bootmgr is missing" RRS feed

  • Question

  • Hi everyone,

    We are currently doing an OSD of Vista using SCCM. To give you an idea on our environment.
    We are using hyper-V and we have 3 machines in it, these are:
    VM1- System Center Configuration Manager 2007 with SP1 R2 and Database server running on SQL 2008
    VM2- WSUS
    VM3- Distribution Point



    We tried to deploy windows Vista on one of the test machines. The task sequence was advertised successfully and run continuously on the test machine but when the test machine reboots, an error appear stating that " BOOTMGR IS MISSING" "PRESS CRTL+ALT+DLT". This error appear continously everytime we reboot the machine. We end up installing vista using its DVD installer.

    We do have some other questions:
    1. Where should we install the PXE role site? Should it be on the SCCM server or on the DHCP server?
    2. Where should we install the WDS role? Should it be on the SCCM server or on the DHCP server? 

    Can anyone help us with this problem? Any response would be much appreciated.
    Thanks.


    Regards,

    Kathleen Sarmiento, MCTS

    Tuesday, May 5, 2009 7:42 AM

Answers

  • Hi Kathleen

    It sounds like you are missing some storage drivers in your  image..  Add the storage driver to a driver package in SCCM, and use that package during deployment, so that the storage drivers are added to the image during deployment.  ( you could set the Storage controller to run in compatibility mode from within the BIOS for testing purposes)

    Question 1: - PXE role must be added to all your WDS servers, as it will add files to the Reminst share.  (Add PXE role to SCCM server)

    Question 2:  - if you add WDS to your SCCM server, it makes adding the PXE role easy, as you will then add it to your primary site, and not have to create extra child sites. Further more you will not have to configure option 60 and 67 on your WDS server as you would have had to if you added the WDS to the DHCP. (Add WDS to SCCM server)

    Michael Petersen


    http://kongkuba1.spaces.live.com
    Tuesday, May 5, 2009 9:26 AM

All replies

  • Hi Kathleen

    It sounds like you are missing some storage drivers in your  image..  Add the storage driver to a driver package in SCCM, and use that package during deployment, so that the storage drivers are added to the image during deployment.  ( you could set the Storage controller to run in compatibility mode from within the BIOS for testing purposes)

    Question 1: - PXE role must be added to all your WDS servers, as it will add files to the Reminst share.  (Add PXE role to SCCM server)

    Question 2:  - if you add WDS to your SCCM server, it makes adding the PXE role easy, as you will then add it to your primary site, and not have to create extra child sites. Further more you will not have to configure option 60 and 67 on your WDS server as you would have had to if you added the WDS to the DHCP. (Add WDS to SCCM server)

    Michael Petersen


    http://kongkuba1.spaces.live.com
    Tuesday, May 5, 2009 9:26 AM
  • Hi Kathleen ,

    After you have verified the steps from Michael , please llok at this.

    1. Check that you have the correct boot storage drivers added thru you task sequence
    2. Personnaly , if all above steps are correct , I think you are missing the Setup windows & Config mgr step into your Task sequence

    Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
    Tuesday, May 5, 2009 9:33 AM

  • Hi,

    Thank you Michael, We will do these steps that you provided us. Thanks again.


    Kathleen Sarmiento

    Wednesday, May 6, 2009 2:17 AM
  • Hi Michael,

    Thanks again for the help.We did all the steps that you've provided, we add the drivers needed but still we weren't able to deploy Vista. During the Task Sequence- Apply Operating system part, an error pop up "Error ID: 0x80070002" after a while the machine reboots and we see the "BOOTMGR is MISSING, PRESS CTRL + ALT + DLT" error again.

    By the way,your answers for our 2 question were a big help to us. We were able to add the PXE role to SCCM server.

    Hope you could help us with this.Thank you.


    Kathleen Sarmiento
    Wednesday, May 6, 2009 9:46 AM
  • Hi Kathleen ,

    1. Did you replicate all your content to your DP ?
    2. Did you add the step apply drivers into your Task sequence ?
    3. Did you add the step "Setup Windows & configmgr " ?
    4. Did you fill in your license data into the "apply windows step " ?

    regards ,

    Kenny
    Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
    Wednesday, May 6, 2009 10:10 AM
  • Hi Kathleen

     

    First try and enable command prompt F8 support in your boot image. Once you boot to WinPE and you see a dialog box, press F8 to open a command prompt. Once you get the error go to X:\windows\temp\smslogs\smsts.log.
    Some where in the log you will see the 0x80070002 (which means “The system cannot find the file specified”) indicating that one of the packages used by the TS is inaccessible. Now look in the line just above the error line, and you should find a reference to a packageID. Once located, you can go to SCCM and point to the TS, and you will see which packages the TS depends on. When you have located the package distribute it to the DP.

     

    Regarding storage drivers. You must put them in a Driver package and add a “add Device Driver Package” Step to make SCCM inject the Storage driver into your Vista build.

     

    If it still does not work, post your SMSTS.LOG

     

    Michael Petersen


    http://kongkuba1.spaces.live.com
    Wednesday, May 6, 2009 4:27 PM
  • Hi Michael and Kenny,

    We try to do another Vista deployment today and we haven't received the error "BOOTMGR is MISSING" but We received another error, stating this:

    Windows PE cannot start because the actual SYSTEMROOT directory (X:\Windows) is different from the configured one (X:\$Windows. ~BT(Windows).

    Press the OK button or close this message to reboot.

    Where should we configured this?..Thank you for helping us in our issues with OSD of SCCM.Looking forward to your next response.

    -Kathleen Sarmiento

     

     

     

    Thursday, May 7, 2009 9:36 AM
  • Hi anne ,

    The problem is the boot.wim that you use.
    It should be created from a standard WinPE boot file found in WAIK , and not the one from Vista.

    Michael Petersen has written a good post on how to create a custom one using his guide on http://kongkuba1.spaces.live.com/blog/cns!EEFF1607E296E5AB!332.entry.

    Regards ,

    Kenny
    Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
    Thursday, May 7, 2009 9:46 AM
  • Hi Kenny,

    Thank you for this information, we'll try this one. thanks for your big help.

    Regards,

    Kathleen Sarmiento

    Thursday, May 7, 2009 10:52 AM
  • Hi Kenny,

    We decided to just used the Microsoft Deployment Toolkit (MDT) rather than WAIK., I just wanted to verify since our SCCM is running on VM1 and Distribution Point is running on VM3, Where should we install MDT?.

    I just also wanted to ask if it is much better to use MDT rather than WAIK?. Thank you.

    Regards,

    Kathleen Sarmiento
    Thursday, May 7, 2009 11:21 AM
  • Hi Kathleen

    WAIK is just a collection of tools.. Neither MDT nor SCCM can function without WAIK (primarily because of ImageX).

     

    If you use MDT only you can install it anywhere, as it is the location of the MDT deployment point that is important, but I would install it on VM3 as it has properly more disk space, being DP and all.  

     

    If you use MDT in conjunction with SCCM you should install it on the SCCM server and then integrate it into SCCM.

     

    Weather you choose MDT as standalone or SCCM integration you will always need WAIK,. So if you use SCCM anyway I would always suggest using that with the MDT integration as it makes the ZTI solution much easier.

     

    Once you have integrated MDT you can actually use the MDT WinPE creation wizard from within SCCM, by right clicking Task Sequences and choosing the “Create media using Microsoft deployment toolkit” option.

     

    Michael Petersen

     


    http://kongkuba1.spaces.live.com
    Friday, May 8, 2009 8:11 AM
  • Hi Michael,

    Thanks for your reply.I was able to integrate MDT and SCCM and I was able to create a boot image through "Create boot image using Microsoft deployment toolkit" - the result are WinPE.wim and WinPE.00100043.wim. 

    I'm just confuse,Which of the two should I use?, I have read in the other forums that the created .wim file should also be used in the Operating System Image and not the one from the CD.

    Regards,

    Kathleen Sarmiento

    Friday, May 8, 2009 10:41 AM
  • Anne Kathleen ,

    You should use this one : WinPE.00100043.wim

    Kenny

    Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
    Friday, May 8, 2009 11:20 AM
  • Hi Guys,

    We were able to run the task sequence. It run smoothly but when it reach the " Apply Operating System" part it suddenly stop and prompt with the error message, "Task Sequence Failed: 0x80070002". We already used the WINPE00100043.wim in the boot image and Operating System Images and we have already added all the drivers needed.

    Hope you could help us with this. I will post the SMSTS.log


    Regards,

    Kathleen Sarmiento
    Monday, May 11, 2009 9:46 AM
  • <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:06:41.771+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="instruction.cxx:3010">
    <![LOG[Failed to run the action: Apply Operating System.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="08:06:41.771+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="instruction.cxx:3101">
    <![LOG[Sending status message . . .]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:292">
    <![LOG[Send a task execution status message SMS_TSExecution_ActionFailError]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:314">
    <![LOG[MP server PRODSCVM01.LBCONE.COM and port 80. SSL=false. CRL=false.]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:458">
    <![LOG[Site code: 001]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:489">
    <![LOG[Client machine name: SCCM-PC]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:494">
    <![LOG[Client Identity: GUID:4ECC0D0C-BBA3-4F28-9799-D82A45D96D0B]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:496">
    <![LOG[Advertisement ID: 00120044]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:505">
    <![LOG[Package ID: 0010004C]LOG]!><time="08:06:41.787+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:507">
    <![LOG[Sending StatusMessage]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:3806">
    <![LOG[Formatted header:]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:1500">
    <![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:4ECC0D0C-BBA3-4F28-9799-D82A45D96D0B</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-05-12T00:06:41Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4222"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
    ]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:1501">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: PRODSCVM01.LBCONE.COM:80  CCM_POST /ccm_system/request]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:7446">
    <![LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:7665">
    <![LOG[unknown host (gethostbyname failed)]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:624">
    <![LOG[hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="libsmsmessaging.cpp:7714">
    <![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:7714">
    <![LOG[End of retries]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="2" thread="1676" file="libsmsmessaging.cpp:1925">
    <![LOG[Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="libsmsmessaging.cpp:2052">
    <![LOG[failed to send the request]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:2052">
    <![LOG[DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835)]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="libsmsmessaging.cpp:3835">
    <![LOG[Failed to send status message (80072ee7)]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:3840">
    <![LOG[smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\utility.cxx,529)]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="utility.cxx:529">
    <![LOG[Non fatal error 0x80072ee7 in sending task sequence execution status message to MP]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="2" thread="1676" file="utility.cxx:542">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147024894]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="08:06:41.927+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Install Operating System) decides whether to continue execution]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="instruction.cxx:3210">
    <![LOG[The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Apply Operating System. Execution of task sequence failed.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:292">
    <![LOG[Send a task execution status message SMS_TSExecution_TaskSequenceFailError]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:314">
    <![LOG[MP server PRODSCVM01.LBCONE.COM and port 80. SSL=false. CRL=false.]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:458">
    <![LOG[Site code: 001]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:489">
    <![LOG[Client machine name: SCCM-PC]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:494">
    <![LOG[Client Identity: GUID:4ECC0D0C-BBA3-4F28-9799-D82A45D96D0B]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:496">
    <![LOG[Advertisement ID: 00120044]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:505">
    <![LOG[Package ID: 0010004C]LOG]!><time="08:06:41.974+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="utility.cxx:507">
    <![LOG[Sending StatusMessage]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:3806">
    <![LOG[Formatted header:]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:1500">
    <![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:4ECC0D0C-BBA3-4F28-9799-D82A45D96D0B</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-05-12T00:06:41Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2090"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
    ]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:1501">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: PRODSCVM01.LBCONE.COM:80  CCM_POST /ccm_system/request]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:7446">
    <![LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="1" thread="1676" file="libsmsmessaging.cpp:7665">
    <![LOG[unknown host (gethostbyname failed)]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:624">
    <![LOG[hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="libsmsmessaging.cpp:7714">
    <![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:7714">
    <![LOG[End of retries]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="2" thread="1676" file="libsmsmessaging.cpp:1925">
    <![LOG[Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="libsmsmessaging.cpp:2052">
    <![LOG[failed to send the request]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:2052">
    <![LOG[DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835)]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="libsmsmessaging.cpp:3835">
    <![LOG[Failed to send status message (80072ee7)]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="3" thread="1676" file="libsmsmessaging.cpp:3840">
    <![LOG[smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\utility.cxx,529)]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="0" thread="1676" file="utility.cxx:529">
    <![LOG[Non fatal error 0x80072ee7 in sending task sequence execution status message to MP]LOG]!><time="08:06:41.989+000" date="05-12-2009" component="TSManager" context="" type="2" thread="1676" file="utility.cxx:542">
    <![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="08:06:59.430+000" date="05-12-2009" component="TSBootShell" context="" type="1" thread="876" file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="08:06:59.430+000" date="05-12-2009" component="TSBootShell" context="" type="1" thread="876" file="bootshell.cpp:850">
    <![LOG[Successfully launched command shell.]LOG]!><time="08:06:59.430+000" date="05-12-2009" component="TSBootShell" context="" type="1" thread="876" file="bootshell.cpp:430">
    Monday, May 11, 2009 9:47 AM
  • Have you set option 003, 006 and 015 in DHCP ??

    Michael


    http://kongkuba1.spaces.live.com
    Monday, May 11, 2009 10:01 AM
  • hi michael,

    yes we have set option 003,006,015 and 060 in DHCP.
    I noticed that When I try PXE boot, I got an error message " PXE-E55: Proxy DHCP service did not reply to request on port 4011".

    Could it be one of the reason why our OSD of Vista failed?

    Thank for the help.

    Regards,

    Kathleen
    Tuesday, May 12, 2009 1:25 AM
  • Michael,

    I am getting the bootmgr is missing as well. I'm lost when it comes to finding the correct storage driver or any for that matter. I'm working with OSD to HP. Can you tell me what I might need to use for a storage driver? I'm just not sure what I am looking for for...
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3253418&prodTypeId=12454&prodSeriesId=3252512&swLang=13&taskId=135&swEnvOID=1093#7828

    Thanks!
    Friday, February 19, 2010 7:05 PM
  • Michael,

    I am getting the bootmgr is missing as well. I'm lost when it comes to finding the correct storage driver or any for that matter. I'm working with OSD to HP. Can you tell me what I might need to use for a storage driver? I'm just not sure what I am looking for for...
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3253418&prodTypeId=12454&prodSeriesId=3252512&swLang=13&taskId=135&swEnvOID=1093#7828

    Thanks!


    I could be wrong as I do not know what controller you have but these two jump out at me:

    ATI IDE Bus Master Controller Driver

    ATI RAID Driver for Microsoft Windows XP

    • Proposed as answer by jjstok Saturday, February 20, 2010 6:13 PM
    Friday, February 19, 2010 8:19 PM
  • Looks like it didn't amtter. After reviewing the logs I was trying to implement a 64bit sequence to a 64bit pc using a x86 image... Oops.

    Thanks
    • Proposed as answer by jjstok Saturday, February 20, 2010 6:14 PM
    Saturday, February 20, 2010 6:14 PM
  • Here are all the steps to resolve the Bootmgr missing error message. I know you’ve tried some of them, but do run them all

    again:

    Boot from the Windows DVD or a repair CD (you may have to change the first boot device to CD/DVD in the BIOS), answer a few

    questions, select the Repair option in the bottom left corner and choose:

    1. Startup Repair (you may have to run it several times).
     
    2. If the above doesn't cure the problem, go back to the Repair Option and this time choose Command Prompt, then type these 4

    commands (in all instances the capitals are for clarity only):
    BOOTREC /FIXMBR and press Enter
    BOOTREC /FIXBOOT and press Enter.
    BOOTREC /SCANOS and press Enter.
    BOOTREC /REBUILDBCD and press Enter.
     
    3. If it’s not successful or you receive ‘No operating system found’ or ‘Element not found’ messages, go back to the Command

    Prompt and make the partition active by typing these commands:
    DISKPART and press Enter.
    LIST DISK and press Enter.
    SELECT DISK N and press Enter (N represents the disk you want).
    LIST PARTITION and press Enter.
    SELECT PARTITION N and press Enter (N represents the partition you want).
    ACTIVE and press Enter.
    EXIT and press Enter.

    For more info on bootmgr is missing

    Wednesday, November 9, 2011 1:40 PM
  • hi Michael,

    need to know storage driver will fall in which category.


    Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

    Sunday, July 14, 2013 5:49 AM