locked
SCCM 2012 PXE Unknown Computer RRS feed

  • Question

  • Hi All,

    I have an SCCM 2012 SP1 server setup and having an issue with PXE boot. I can PXE boot successfully if my task sequence is deployed to the "All Systems" collection. However I have noticed when the OSD is complete the computer name is identical to a machine already in our domain. I have set the task sequence to add to the domain placing into the Computers OU.

    So I remove any trace of the computer from AD and from SCCM (in the case of rebuild) and then have set a OSDComputername variable on the "Unknown Computers" collection.

    However when PXE booting the same machine now it does not like it. Refuses to work. Again if I re-deploy same task sequence to "All Systems" collection is boots into PXE and again when finished picks up a computername that is already in use within AD.

    Totally confused......

    If anyone has any ideas I'd be most grateful?

    Friday, May 10, 2013 3:52 PM

Answers

  • Hi Gerry,

    We have eventually found the answer. Duplicate GUID's! Thank you for all your help. I found KB2591483 and followed it. I can now boot into Windows PE from an advertisement. However another problem looms but I'll create a new post.

    Thanks 

    Friday, May 17, 2013 1:18 PM

All replies

  • What is the error?

    SCCM could have a record of the MAC address. Are there any devices shown as Unknown? You can delete them (not Unknown Computers - be careful) Run the SCCM report "Computers with a specific MAC address" to see if the MAC address exists in the SCCM database. This would make it "Known" and deployments to "Unknown Computers" would not be available.



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson




    • Edited by Gerry HampsonMVP Tuesday, June 25, 2013 11:07 PM Edited blog address
    Friday, May 10, 2013 3:56 PM
  • Hi Gerry,

    Thanks for your reply.

    The error is generic something along the lines of PXE Boot aborted.  Booting to next device.

    I have searched for the MAC within SCCM and nothing is found. Also cannot find any "unknown" computers. I am at a complete loss as to why it would only work when advertised to "All Systems" and then give it the name of another active computername randomly from AD.

    Friday, May 10, 2013 4:03 PM
  • PXE Boot aborted means that there is no deployment available for this computer. This means that, for some reason, SCCM does not see it as unknown. That's why it works when you use "All Systems".

    Strange. You would normally find this using the report. "Update the membership" of All Systems. Does the rogue appear? 



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    • Edited by Gerry HampsonMVP Tuesday, June 25, 2013 11:07 PM Edited blog address
    Friday, May 10, 2013 4:07 PM
  • I have done that also.

    before using OSD the computer was domained and in use daily. I want to re-image and name it differently.

    Here is what I have done

    Removed the Computer account from AD

    Deleted the Resource in SCCM

    Advertised the OSD task sequence to "Unknown Computers" - Doesn't work PXE Boot Aborted..........

    Advertised OSD task to "All Systems" PXE works after pressing F12, computer images but the computer name is identical to another in AD, I do the process again and a different computer name is used again one that's already in use within AD.

    Friday, May 10, 2013 4:13 PM
  • Where are the computer names coming from? Have you configured this in your task sequence? Normally, when you have not configured a method for naming SCCM automatically names in the format MININT-xxxx.

    Are these physical or virtual machines?



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    • Edited by Gerry HampsonMVP Tuesday, June 25, 2013 11:07 PM Edited blog address
    Friday, May 10, 2013 4:18 PM
  • They are names of computers already in use within AD!

    I am expecting it to prompt for a computer name as set in the Unknown Computers collection but its not. The machine is physical and upto an hour ago was in use in its old location.

    Friday, May 10, 2013 4:21 PM
  • Get rid of the deployment to "All Systems". Right click "All Unknown Computers" in Device collections and select Clear PXE Deployments. Then try to network boot again.

    Also, Clear PXE Deployments on "All Systems" collection.



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson



    • Edited by Gerry HampsonMVP Tuesday, June 25, 2013 11:07 PM Edited blog address
    Friday, May 10, 2013 4:34 PM
  • I have done that, still happens.

    Bizarre! I have just tried again. The PC was named BUISNESS01 before, PXE booted and imaged, now then PC is called LIBRARY12.

    no idea why, LIBRARY12 is in a different OU and still in use, and no doubt will now need to be looked into......

    Friday, May 10, 2013 4:54 PM
  • You should examine the SMSTS.log file to try and figure out where the ComputerName is coming from.


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    • Edited by Gerry HampsonMVP Tuesday, June 25, 2013 11:07 PM Edited blog address
    Friday, May 10, 2013 4:56 PM
  • Hi Gerry,

    We have eventually found the answer. Duplicate GUID's! Thank you for all your help. I found KB2591483 and followed it. I can now boot into Windows PE from an advertisement. However another problem looms but I'll create a new post.

    Thanks 

    Friday, May 17, 2013 1:18 PM
  • Also be aware that even if you delete a resource record from the site it'll still be recorded as historical information (new to CM12), this is so that identity reuse can take place.

    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Saturday, May 18, 2013 10:27 AM