Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter > System Center Configuration Manager Forums > Configuration Manager 2007 Operating System Deployment > WDS Works But SCCM PXE Does Not.

Answered WDS Works But SCCM PXE Does Not.

    •  
      Thursday, November 06, 2008 8:50 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Hello,

      I know there is numerous post related to PXE booting and SCCM and one similar to my issue http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2160398&SiteID=17  but this resolution does not work.

       

      Installed WDS on 2003 R2 Enterprise server

      Add a boot image to test PXE and I can boot no problem

      PXE boot fails after adding the ccm PXE service point and distributing my boot images to the PXE DP.

       

      This is what i get when i try to PXE boot after i add the CCM PXE Service Point:

      "Downloaded WDSNBP"

      "Arch x64"

      "The details below show the information relating to the PXE Boot Request.  Please provide these details to yoru Windows Deployment Services administrator so this request can be approved"

      Pending Request ID 6

      Contacting Server 192.168.1.2

      TFTP Download smsboot\x64\abortpxe.exe

       

      The WDS service is configured to accept all requests.

      The DHCP server is not on the WDS server.

      I can PXE Boot no problem when there isn't a CCM PXE Service Point

       

      Do i need to manually add the Boot images from \\SiteServer\SMSPXEIMAGES$ so they show up in WDS boot images or is this automatic when i enable CCM PXE Service Point?

       

      Any help would be great as this is the last piece of the puzze for OSD...

       

    Answers

    • Wednesday, November 12, 2008 3:11 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      All of the times that I've had issues with the PXE component not working properly for me, it was becasue I messed with the WDS before I installed the PXE role.  I know some people say that the proper way to get this to work is to install WDS, then configure the WDS server, then install the PXE role, but that has always ended in frustration for me.  I even went to a week-long SCCM class and the instructor swore up and down that this was the way to do it.

       

      However, I have seen other posts that dispute this, and I whenever I run into this problem, I do the following:

       

      Stop the WDS service, stop the PXE component.

      Deinstall the PXE role.

      Uninstall the WDS role.

      REBOOT

      Install WDS (NOTE: Do NOT configure it, or even start it up, just check that the service is started)

      Install the PXE role.

      Any configurations that you do should happen from Inside the the SCCM console.

       

      See if that works for you.

       

    All Replies

    • Friday, November 07, 2008 2:57 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      The SMSPXE.log will give you a detailed reason as to why the client is being rejected. The most common reason is that there is no advertisement for the client machine, or that the advertisement has run for it and it is mandatory (in which case, you need to clear the 'last pxe advertisement' flag.
       
    • Friday, November 07, 2008 2:58 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Also, if the client is 'unknown' (that is, there is no record of it in the site database), then you need to 'import' the machine information (MAC address and/or SMBIOS).
       
    • Friday, November 07, 2008 8:49 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I have same problems.

      Check following:

      1. PC located in Collection with OS deployment advertisement
      2. PC have correct MAC adress (it is very important in in Virtual LAB env)
      3. DHCP configured to answer on BOTH DHCP and boottp packets, and NO 60 or 65 options (just DNS server, default GW and suffix)

      For more information see pxe logs on SCCM machine with PXE Role, you may see somthing like "this machine is skiped because PXE advertisement already advertise"  -> Clera last PXE advertisement on this machine in collection or "no advertisement for this machine" -> then check (1) (2)

      And one more suggestions, if use Virtual LAB use not default Virtual ethernet adapter but intel E1000:

       

      1. add this line to *.vmx file of your virtual machine

      Code Snippet
      ethernet0.virtualDev = "e1000"

       

       

      1. download drivers for intel e1000 and supplay them with boot image
       
    • Tuesday, November 11, 2008 4:19 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hello,

      What happens now  is it get's farther in the process but it hangs at

      Contacting Server: 172.31.128.5....................................................................................

       

      this is what the smspxe.log is outputting.

      Code Snippet

      <![LOG[[172.031.128.005:67] Recv From:[000.000.000.000:68] Len:548 77c304]LOG]!><time="11:24:55.497+300" date="11-11-2008" component="smspxe" context="" type="0" thread="8136" file="smspxe.cpp:663">
      <![LOG[Ignoring req from [000.000.000.000:68] Dest Server:[144.212.066.247]]LOG]!><time="11:24:55.497+300" date="11-11-2008" component="smspxe" context="" type="0" thread="8136" file="pxeutil.cpp:114">
      <![LOG[[172.031.128.005:4011] Recv From:[172.031.128.154:68] Len:548 24876e4]LOG]!><time="11:24:55.607+300" date="11-11-2008" component="smspxe" context="" type="0" thread="700" file="smspxe.cpp:663">
      <![LOG[[172.031.128.005:4011] Recv From:[172.031.128.154:68] Len:299 248879c]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="700" file="smspxe.cpp:663">
      <![LOG[Executing GetBootAction(715, TRAININGDC-AH)]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:512">
      <![LOG[vLastPXEAdvertisementID is NULL]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:581">
      <![LOG[vLastPXEAdvertisementTime is NULL]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:591">
      <![LOG[GetBootAction: MAC:00:03:0D:22:D7:AA SMBIOS: SMSID:GUID:4B0B9BEA-DAE1-45CC-AABE-8AE31CD7B38E LastAdv:]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:602">
      <![LOG[Advertisement results: OfferId:TD1200D6 OfferTime:11/11/2008 11:09:00 PackageID:TD10006B BootImageID:TD10004A PackageVer: PackagePath:http://SCCMServer/SMS_DP_SMSPKGE$/TD10004A/ Mandatory:1]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:675">
      <![LOG[Advertisement results: OfferId:TD1200D6 OfferTime:11/11/2008 11:09:00 PackageID:TD10006B BootImageID:TD10004A PackageVer: PackagePath:\\SCCMServer\SMSPKGE$\TD10004A\ Mandatory:1]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:675">
      <![LOG[Advertisement results: OfferId:TD1200D6 OfferTime:11/11/2008 11:09:00 PackageID:TD10006B BootImageID:TD10004A PackageVer: PackagePath:\\SCCMServer\SMSPXEIMAGES$\SMSPKG\TD10004A\ Mandatory:1]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:675">
      <![LOG[ProcessDatabaseReply: Using Advertisement found in DB: TD1200D6]LOG]!><time="11:24:55.794+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="pxehandler.cpp:504">
      <![LOG[[172.031.128.005:4011] Recv From:[172.031.128.154:68] Len:299 2489854]LOG]!><time="11:25:15.544+300" date="11-11-2008" component="smspxe" context="" type="0" thread="700" file="smspxe.cpp:663">
      <![LOG[MAC=00:03:0D:22:D7:AA SMBIOS GUID=F1049A34-3C7A-419F-11DB-9BED9ADC58CC > Device has been accepted.]LOG]!><time="11:25:15.544+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="pxehandler.cpp:1840">
      <![LOG[[172.031.128.005:4011] Recv From:[172.031.128.154:68] Len:299 248a90c]LOG]!><time="11:25:35.310+300" date="11-11-2008" component="smspxe" context="" type="0" thread="700" file="smspxe.cpp:663">
      <![LOG[MAC=00:03:0D:22:D7:AA SMBIOS GUID=F1049A34-3C7A-419F-11DB-9BED9ADC58CC > Device has been accepted.]LOG]!><time="11:25:35.310+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="pxehandler.cpp:1840">
      <![LOG[[172.031.128.005:4011] Recv From:[172.031.128.154:68] Len:299 248b9c4]LOG]!><time="11:25:55.075+300" date="11-11-2008" component="smspxe" context="" type="0" thread="700" file="smspxe.cpp:663">
      <![LOG[MAC=00:03:0D:22:D7:AA SMBIOS GUID=F1049A34-3C7A-419F-11DB-9BED9ADC58CC > Device has been accepted.]LOG]!><time="11:25:55.075+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="pxehandler.cpp:1840">
      <![LOG[[127.000.000.001:4011] Recv From:[127.000.000.001:9000] Len:274 253e944]LOG]!><time="11:25:55.200+300" date="11-11-2008" component="smspxe" context="" type="0" thread="700" file="smspxe.cpp:663">
      <![LOG[Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF)]LOG]!><time="11:25:55.200+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:395">
      <![LOG[CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0]LOG]!><time="11:25:55.200+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="database.cpp:445">
      <![LOG[MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database.]LOG]!><time="11:25:55.200+300" date="11-11-2008" component="smspxe" context="" type="0" thread="932" file="pxehandler.cpp:335">

       

       

       
    • Wednesday, November 12, 2008 3:11 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      All of the times that I've had issues with the PXE component not working properly for me, it was becasue I messed with the WDS before I installed the PXE role.  I know some people say that the proper way to get this to work is to install WDS, then configure the WDS server, then install the PXE role, but that has always ended in frustration for me.  I even went to a week-long SCCM class and the instructor swore up and down that this was the way to do it.

       

      However, I have seen other posts that dispute this, and I whenever I run into this problem, I do the following:

       

      Stop the WDS service, stop the PXE component.

      Deinstall the PXE role.

      Uninstall the WDS role.

      REBOOT

      Install WDS (NOTE: Do NOT configure it, or even start it up, just check that the service is started)

      Install the PXE role.

      Any configurations that you do should happen from Inside the the SCCM console.

       

      See if that works for you.

       
    • Wednesday, November 12, 2008 3:33 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Just the same for me. Eventually WDS service does not start (or is not runing properly) and once you (re) start it everything goes well. According to the course 6451A you need to install and configure WDS first, then add PXE role to SMS. I will do so once upgrading to SCCM R2. As the workaround I would just restart WDS service before booting into PXE. Hopefully MS has fixed this in R2.

       

       

       
    • Wednesday, November 12, 2008 4:58 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Course 6451A material is incorrect. You don't have to configure WDS, before adding PXE Service Point role. I've done this many times without configuring WDS first. I would recommend that you DON'T configure WDS if you just want to use it as a PXE Service Point.

       

      Two most common problems I see with PXE + ConfigMgr:

      - you haven't added BOTH x86 and x64 boot images to PXE Service Point.

      - the target computer is unknown to ConfigMgr and you are not using ConfigMgr R2's unknown computer support

      (you have in the SMSts.log: "the device is not found in the datebase")

       

      Panu

       
    • Wednesday, November 12, 2008 6:28 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      This PXE-WDS-Sequence thing is a mistery. I've played around a bit more with it and it just works once every five retries. Maybe you just have to wait (as in many things with SCCM) before attempting to boot into PXE after advertising a sequence. Did anyone here managed to make it working reliably?
       
    • Wednesday, November 12, 2008 9:07 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hello,

      It finally worked when i followed CD Shriver's steps by uninstalling everything, rebooting, then reinstalling without ever configuring WDS. 

       

      Thanks everyone for the replies as this is the last piece of the puzzle...let's hope that it is consistent.

       

      .