locked
Boot an ESX 5.1 VM to my SCCM 2012 (WDS) server? RRS feed

  • Question

  • Hi folks,

    I just got my SCCM 2012 server installed, configured a distribution point, published new boot.wim to distribution point.

    I am trying to test booting up a 'bare metal' ESXi 5.1 VM to my SCCM 2012 (WDS) server, but fails with attached error.

    Configuration Manager is looking for policy.

    Anyone have a suggestion?

    Thanks, romatlo

    Tuesday, December 17, 2013 10:32 PM

Answers

  • The error message in your screenshot is quite clear.

    Honestly, at this point, you really should read about the entire process and hwo it works on TechNet, in a book, or a good web based walk-through (like those at windows-noob.com). OSD has many, many moving parts that come together to deploy Windows; all of these must be in place and working. You seem to be doing one step at a time and (not be insulting at all) fumbling your way through. without knowing the implications or reasons for what you're doing. Knowing the building blocks and the whys of the building blocks will pay infinite dividends in the future.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by romatlo32 Wednesday, December 18, 2013 2:32 PM
    Wednesday, December 18, 2013 2:24 PM

All replies

  • Do you have a task sequence deployed to this system or unknown computer support enabled with a task sequence deployed to the unknown computer collection (or objects).

    If not, then a client will not PXE boot in ConfigMgr. You can easily see this in the smspxe.log on the DP (which is within the SMS_DP$\SMS\logs folder).


    Jason | http://blog.configmgrftw.com

    Wednesday, December 18, 2013 12:47 AM
  • Thank you so much for responding!  I must admit that this is my first install.  :)

    I could not find that option, so I deleted/recreated my task sequence, then found it as part of Deploy option.

    I deployed the task sequence to unknown computers but I still get that message and will not boot up correctly.

    I've pasted last part of my SMSPXE.log in case you see something definitive.

    I did not have my WDS server role installed when enabling PXE on my DP, maybe that messed me up.

    Thanks again, I may snapshot my VM here and start over on install if there is not a clue.

    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6346">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: device is in the database.]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: No boot action. Aborted.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: Not serviced.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">

    Wednesday, December 18, 2013 4:55 AM
  • hi,

    If you don't have WDS on your DP after enabling the PXE then that's a problem.

    When a server is added in SCCM for DP with pxe enabled, SCCM installs & configures the WDS by itself.

    When WDS is installed on the server a folder named Remote install is created in the installation drive, which has folders naming SMSBoot, SMSImages which contains the boot images from SCCM.

    What you can do is uncheck the PXE enabled option, Install the WDS role manually & Configure WDS but don't add anything. After Configuring WDS check if Remote install folder is created in installation drive. Once this is done go & check "Enable PXE support in DP" again & check if following folders are created or not :-

    SMSBoot, SMSImages, SMSTemp, SMSTempBootFiles

    Then check under SMSImages you have the boot images with folder name as Package ID.

    But your log file says :-

    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!>

    Thanks,

    Pranay.


    Wednesday, December 18, 2013 5:06 AM
  • Thank you for responding!

    I did notice that when I enabled PXE on DP, that it installed WDS role (at the time did not look for SMS folders).

    I ended up unchecking/checking PXE option and I see all of the SMS folders in my RemoteInstall directory.
    Retested VM boot, same problem.

    However! I set one of my thin clients to PXE first (prompted to press F12 again). sccm2.jpg attached.
    It actually booted to a \SMSImages\02900008\boot.02900008.wim file.
    It stopped at an error Failed to Run Task Sequence.  TS.jpg attached.

    Then I tried PXE booting an old desktop and it has same policy message but just keep trying to contact smsboot\x86\pxeboot.com.

    Maybe I should back out my configuration and recreate DP, task sequence, etc.

    Thanks! romatlo

    sccm2.jpg

    TS.jpg

    Wednesday, December 18, 2013 1:01 PM
  • The error message in your screenshot is quite clear.

    Honestly, at this point, you really should read about the entire process and hwo it works on TechNet, in a book, or a good web based walk-through (like those at windows-noob.com). OSD has many, many moving parts that come together to deploy Windows; all of these must be in place and working. You seem to be doing one step at a time and (not be insulting at all) fumbling your way through. without knowing the implications or reasons for what you're doing. Knowing the building blocks and the whys of the building blocks will pay infinite dividends in the future.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by romatlo32 Wednesday, December 18, 2013 2:32 PM
    Wednesday, December 18, 2013 2:24 PM
  • You're right Jason.  I am fumbling through here...not experienced.

    I will close this thread and reset.

    Thanks again!!

    Wednesday, December 18, 2013 2:31 PM
  • Check out Windows-noob.com, Niall has done a great job of providing very good walk-throughs.

    Jason | http://blog.configmgrftw.com

    Wednesday, December 18, 2013 2:45 PM
  • Just wanted to update my thread.

    I finally resolved booting Unknown Computers to a boot image after reinstall and making sure that boot images were distributed.

    Resolved the task sequence error (referencing SCCM client), by creating an IP Subnet boundary.

    I only had an AD boundary created.  I initiated the creation of IP boundary by selecting automatic on Forest Discovery.

    Sunday, January 5, 2014 12:35 PM
  • Side note: forest discovery does not create IP Subnet boundaries, it creates IP Range boundaries and yes there is a big difference between the two.

    Jason | http://blog.configmgrftw.com

    Sunday, January 5, 2014 7:40 PM