locked
HP Proliant Gen9 Servers unable to PXE boot with ADK 1709 Boot Image. Older ADK version work. Other server models work. RRS feed

  • Question

  • ProLiant BL460c Gen9

    UEFI Optimized

    FLB Adapter 1: HP FlexFabric 10Gb 2-port 536FLB Adapter

    We have been imaging these servers using the ADK 1703 Boot Image without issue. After upgrading to ADK 1709 and creating new boot images, we are unable to boot to into PE with these model servers.  We have verified that the correct drivers are in the image, and have also tested with the default boot image that is generated in SCCM when ADK is installed/upgraded.  We aren't seeing this issue with any other server models and we can boot fine off of any of our older boot images that use older ADK versions (1703, etc).  Additionally, we were running SCCM 1706 when we did the ADK 1709 upgrade and began seeing the issue.  We then upgraded to SCCM 1710 and rebuild the boot image and had the same issue.  We plan to open a Premier Support case next week, but wanted to see if anyone else is experiencing this.

    You can PXE boot then, as the boot image is about to begin downloading to the server, the HP Logo screen is displayed and it doesn't go any further.


    • Edited by AdamGrossTX Saturday, January 27, 2018 8:20 PM Edited the picture
    Saturday, January 6, 2018 5:41 PM

Answers

  • Hi, I got the same issue too.
    Update to CB1710 from 1702. Updated to ADK 1709..
    Tasksequence for Gen8 and VM working fine, but Gen9 only loads boot.wim and got stuck after download completed. I created new boot Images, verified all drivers and tried again and again.. but nothing is working..

    btw. there was a reboot pending after updating to CB1710 on my DP/PXE server(but rebooting didn't resolve the issue)

    How to fix:
    1 . Please download following cumulative update for Windows Server 2016:
          http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4056892

    2. locate your boot.wim and follow:
    https://support.microsoft.com/en-us/help/4055537/config-initialization-failed-error-when-installing-windows-Server

    In short, you need to apply this update to your boot.wim:
    start "Deployment and Imaging Tools Environment"

    dism /mount-image /imagefile:<path_to_image_file>\sources\boot.wim /index:1 /mountdir:<target_mount_directory>\offline

    dism /image:<target_mount_directory>\offline /add-package /packagepath:"<path to the update>\Windows10.0-KB4056892-x64.cab"

    dism /unmount-image /mountdir:<target_mount_directory>\offline /commit

    3. update your DP with the modified boot.wim

    And don't be afraid of the size of the update ;) After injecting the update, my boot.wim had a size of 350MB including all neccessary drivers. 

    Please let me know if this helped you


    • Edited by Michael_Jakob Thursday, January 25, 2018 12:27 PM
    • Marked as answer by AdamGrossTX Friday, January 26, 2018 7:48 PM
    Thursday, January 25, 2018 12:24 PM

All replies

  • Hi,

    Was the server restarted after ADK upgrade?

    I have seen a similar case that after a reboot, it works properly with ADK 1709.

    In addition, you may also refer to MDT forum to see whether people have experienced the same issue:

    https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Edited by Amy Wang_ Monday, January 8, 2018 7:35 AM
    • Proposed as answer by Amy Wang_ Monday, January 15, 2018 8:06 AM
    • Unproposed as answer by AdamGrossTX Saturday, January 27, 2018 8:27 PM
    Monday, January 8, 2018 7:25 AM
  • Hi,

    What do you means for " server restartd" ?

    Do you means SCCM server or HP ProLiant server ?

    Because I have the similar problem since ADK 1709 with the similar drivers from 1703.

    Thanks in advance

    Monday, January 22, 2018 8:05 AM
  • Hi, I got the same issue too.
    Update to CB1710 from 1702. Updated to ADK 1709..
    Tasksequence for Gen8 and VM working fine, but Gen9 only loads boot.wim and got stuck after download completed. I created new boot Images, verified all drivers and tried again and again.. but nothing is working..

    btw. there was a reboot pending after updating to CB1710 on my DP/PXE server(but rebooting didn't resolve the issue)

    How to fix:
    1 . Please download following cumulative update for Windows Server 2016:
          http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4056892

    2. locate your boot.wim and follow:
    https://support.microsoft.com/en-us/help/4055537/config-initialization-failed-error-when-installing-windows-Server

    In short, you need to apply this update to your boot.wim:
    start "Deployment and Imaging Tools Environment"

    dism /mount-image /imagefile:<path_to_image_file>\sources\boot.wim /index:1 /mountdir:<target_mount_directory>\offline

    dism /image:<target_mount_directory>\offline /add-package /packagepath:"<path to the update>\Windows10.0-KB4056892-x64.cab"

    dism /unmount-image /mountdir:<target_mount_directory>\offline /commit

    3. update your DP with the modified boot.wim

    And don't be afraid of the size of the update ;) After injecting the update, my boot.wim had a size of 350MB including all neccessary drivers. 

    Please let me know if this helped you


    • Edited by Michael_Jakob Thursday, January 25, 2018 12:27 PM
    • Marked as answer by AdamGrossTX Friday, January 26, 2018 7:48 PM
    Thursday, January 25, 2018 12:24 PM
  • THANK YOU!!! This worked perfectly.

    We had info from HP about a KB that MS was going to issue, but it never showed up. After you posted, I checked and found this post. https://social.technet.microsoft.com/Forums/ie/en-US/4e6e7937-7efa-45d7-aede-d64119cb75e4/winpe-boot-issue-proliant-gen9-server-with-winpe-1709-where-is-the-fix-kb4055537?forum=ConfigMgrCBOSD

    Which led me to this: https://support.microsoft.com/en-us/help/4055537/config-initialization-failed-error-when-installing-windows-server

    Which is the KB from HP from here: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00037880en_us

    Thank you for the info!

    Friday, January 26, 2018 7:48 PM
  • Michael, thanks again for the info. I credited you in a post about it here. http://www.asquaredozen.com/2018/01/27/winpe-image-fails-load-hp-proliant-gen9-servers-using-adk-1709/
    Sunday, January 28, 2018 3:05 PM
  • I had a similar problem booting WinPE 1709 on VMware. No luck on fixing it with KB4056892. This was later caused by the template used to create wmx-09 machines. It's stuck just a bit before the HP Gen9 issue.

    Adam, Little addition on your blog:

    You point to 2018-01 Delta Update for Windows Server 2016 (1709) for x64-based Systems (KB4056892). When you download and extract this specific update you will end up with the file Windows10.0-KB4056892-x64_Delta.cab. Using this in the DISM Add-Package wil give Error "The specified package is not applicable to this image."

    You should use, and refer to http://www.catalog.update.microsoft.com/Search.aspx?q=cumulative*KB4056892*2016*1709* in your blog.

    Just my 2 cents.


    • Edited by Ariendg Wednesday, January 31, 2018 5:26 PM
    Wednesday, January 31, 2018 5:26 PM
  • Good catch on the update name. I have updated the post. Thanks!
    Thursday, February 8, 2018 5:51 AM