locked
Trouble PXE booting RRS feed

  • Question

  • I have inherited an SCCM environment that was very under utilized. I recently fixed my DP and have created a reference image. 

    In SCCM I have set up an Operating System Image, Installer, a Boot Image, and created a basic Task Sequence. 

    I have deployed this TS to a test collection.

    I added an Oracle Virtual Box to SCCM, gave it the name "w7_test" and added it's IP address during "import computer information".

    When I try and PXE boot I see three options that are not mine - I traced this back (via the IP shown) to an imaging server with WDS that the previous crew setup to deploy everything through using MDT.

    Some questions...
    Can I have two WDS servers working together? I will eventually take the other one down once I know I have a suitable environment...
    Would two WDS servers be the reason I cannot see my wim during PXE boot?

    I have verified that all of the content is distributed to to my sites.

    Tuesday, July 5, 2016 9:11 PM

Answers

  • So - I did not have my x86 deployed to this DP... I deployed it to the DP and now PXE boot advanced past the TFTP error.

    I thought I had x86 deployed but through my testing I had been redeploying and changing settings, so yeah, wasn't distributed to my DP. 

    I was able to PXE boot just now. 

    It allowed me to choose the correct Task Sequence I had created for testing. 

    Now I need to complete a final image and load some drivers into my TS!!

    EDIT* - Here are the things I did that enabled me to image this computer: Added IP of my DP to IPhelpers, turned off the previously used imaging server's WDS role, distributed x86 boot.wim to my DP.

    • Marked as answer by noobert87 Monday, July 11, 2016 1:02 PM
    • Edited by noobert87 Monday, July 11, 2016 2:18 PM
    Monday, July 11, 2016 1:02 PM

All replies

  • No, you cannot have two different WDS/PXE servers in the same subnet at the same time.  The DHCP scope associated with that VLAN will have options 66 and 67 set to point to the old WDS server.  To use the new one set option 66 to the IP of the new PXE enabled DP and option 67 to SMSBoot\x86\wdsnbp.com. (Its possible these options will be set by your network team using IPHelpers).  If you want to use both WDS/PXE servers at the same time you'll need to add a new VLAN for the new environment.
    Tuesday, July 5, 2016 9:33 PM
  • Not exactly. It is possible but usually problematic to have multiple PXE servers in the same scope.

    The exact behavior and path to having multiple though depends upon whether you are using iphelpers or DHCP scope options though as they cause slightly different behaviors in the PXE client. Thus, which are you using? You may have to investigate DHCP and/or communicate with the networking folks to determine this.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, July 5, 2016 10:13 PM
  • Yes you can have more than one WDS server.
    Wednesday, July 6, 2016 9:58 AM
  • I shutdown WDS on the original imaging server.

    I now get "PXE-E32: TFTP open timeout". 

    I confirmed TFTP service is running on my DP. I assume option 66/67 are setup for the original imaging server. I put in a request to change option 66 to the IP of my DP and set 67 to "SMSBoot\x86\wdsnbp.com". There are other posts here with this similar issue and it seems each person found a different solution. 

    Going to try 66/67 first... Then will try other things. 

    *I checked SMSPXE.log and it stopped logging 7.1.16 with PXE PROVIDER SHUTDOWN. I restarted the DP and tried to PXE boot a machine and the log didn't update.

    Wednesday, July 6, 2016 4:51 PM
  • IF PXE and DCP are not co located option 66/67 should not be configured, other wise they will point to the configured PXE server.
    Thursday, July 7, 2016 9:12 AM
  • Options 66/67 have nothing to do with DHCP and PXE being co-located. They tell clients where the PXE server is located. Anyway ... using 66/67 is officially not supported. Use IPhelpers instead.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, July 7, 2016 9:34 AM
  • I had the network guys add this command to the router's interface: ip helper-address 'address of my distribution point/WDS'

    I am still receiving PXE-E32: TFTP open timeout

    We have outsourced some of our server scope... so since the previous team had their own imaging server with WDS, I think it is possible they configured option 66 to point to that server. I submitted a ticket for this but I won't know for 1-3 days. 

    Torsten - if option 66 was configured with the other imaging server's IP, even with IP helpers, would I still be getting PXE-E32?


    • Edited by noobert87 Friday, July 8, 2016 4:46 PM
    Friday, July 8, 2016 2:16 PM
  • Is your smspxe.log saying PXE PROVIDER SHUTDOWN still?

    "I recently fixed my DP" - what was wrong with it?

    What happens if you try PXE boot a machine in the same subnet as the DP?



    Nick | https://brotechcm2012.wordpress.com/

    Sunday, July 10, 2016 3:45 AM
  • Nick,

    smspxe.log - No, this no longer says "PXE PROVIDER SHUTDOWN". I'll post a bit of the logs from 7.8.16 at the bottom of this post.

    "I recently fixed my DP" - Well, after a bit of troubleshooting I realized that when my Primary Site was looking at my DP for a drive to host content, WMI was returning "no drive", so it failed to distribute. I ran WMI diagnostics and there were a lot of errors. I ran diagnostics on the DP and found there were a large amount of WMI errors. I posted here, and was told I should probably start from scratch. Following some guides online I was able to repair WMI and now all of my content distributes correctly - I can push software successfully. 

    "What happens if you try PXE boot a machine in the same subnet as the DP?" - I received the same error "TFTP open timeout". - I am not 100% sure about this. Had some miscommunication with our network guy. He says we tried this but will double check when he gets in.

    CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003 SMSPXE 7/8/2016 12:32:28 PM 1404 (0x057C)
    CContentDefinition::Expand failed; 0x80070003 SMSPXE 7/8/2016 12:32:28 PM 1404 (0x057C)
    Adding PRI00005.6 SMSPXE 7/8/2016 12:32:28 PM 1404 (0x057C)
    Adding PRI00011.4 SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003 SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    CContentDefinition::Expand failed; 0x80070003 SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    Found new image PRI00005 SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    ADK installation root registry value not found. SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    Loaded C:\Windows\system32\wimgapi.dll SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    Opening image file D:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    Found Image file: D:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim
     PackageID: PRI00005
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version:  
     Creator: 
     SystemDir: WINDOWS
    SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    Closing image file D:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim SMSPXE 7/8/2016 12:32:29 PM 1404 (0x057C)
    Begin validation of Certificate [Thumbprint C83A0B00D803D6FCE08187ACBB2B994557CA235E] issued to 'd4b59326-a61a-43c6-b1c2-c341f0bd8e59' SMSPXE 7/8/2016 12:32:30 PM 1404 (0x057C)
    Completed validation of Certificate [Thumbprint C83A0B00D803D6FCE08187ACBB2B994557CA235E] issued to 'd4b59326-a61a-43c6-b1c2-c341f0bd8e59' SMSPXE 7/8/2016 12:32:30 PM 1404 (0x057C)
    PXE Provider finished loading. SMSPXE 7/8/2016 12:32:30 PM 1404 (0x057C)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16787447" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    SMSPXE 7/8/2016 12:33:01 PM 2508 (0x09CC)
    34:E6:D7:33:15:96, 4C4C4544-0054-4D10-804E-B6C04F4E3332: device is in the database. SMSPXE 7/8/2016 12:33:01 PM 2508 (0x09CC)
    Warning: Matching Processor Architecture Boot Image (0) not found SMSPXE 7/8/2016 12:33:01 PM 2508 (0x09CC)

    Edit*

    I just tried to PXE boo again and smspxe.log shows: 

    Warning: Matching Processor Architecture Boot Image (0) not found SMSPXE 7/11/2016 7:48:19 AM 2508 (0x09CC)
    • Edited by noobert87 Monday, July 11, 2016 12:50 PM Added details
    Monday, July 11, 2016 12:47 PM
  • So - I did not have my x86 deployed to this DP... I deployed it to the DP and now PXE boot advanced past the TFTP error.

    I thought I had x86 deployed but through my testing I had been redeploying and changing settings, so yeah, wasn't distributed to my DP. 

    I was able to PXE boot just now. 

    It allowed me to choose the correct Task Sequence I had created for testing. 

    Now I need to complete a final image and load some drivers into my TS!!

    EDIT* - Here are the things I did that enabled me to image this computer: Added IP of my DP to IPhelpers, turned off the previously used imaging server's WDS role, distributed x86 boot.wim to my DP.

    • Marked as answer by noobert87 Monday, July 11, 2016 1:02 PM
    • Edited by noobert87 Monday, July 11, 2016 2:18 PM
    Monday, July 11, 2016 1:02 PM