Ask a questionAsk a question
 

AnswerWierd PXE situation

  • Thursday, October 29, 2009 5:59 AMRybal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I could not get a computer to PXE for the life of me (was trying to image a former server). I ran a report on mac address and the server had no record of it. I could not get it to see any advertisements via unknown computer support or by importing the computer information and making a new record for the machine or any of the usual methods.

    In frustration I finally optionally advertised a task sequence to all systems and it took off. After the OSD the computer was joined to the domain with a name from a system totally on the opposite side of the network(workstation). This machine had a completely different MAC address.

    How the heck did it think that the old server box was the workstation across campus?

    Any ideas on what happened to cause this?

Answers

  • Thursday, October 29, 2009 7:37 PMNiall C. Brady Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    i would never advertise a task sequence to the All Systems collection to prevent this type of behaviour even though you say it was optional,

    I would recommend using specific Deploy collections that are populated with machines that you intend to deploy an os to

    eg:

    Deploy
    >>Deploy XP
    >>Deploy Vista
    >>Deploy Server 2008
    >>Deploy 7

    and so forth,

    as regards your actual problems reading your logs may reveal what actually happened and why

    cheers
    niall
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

All Replies

  • Thursday, October 29, 2009 7:37 PMNiall C. Brady Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    i would never advertise a task sequence to the All Systems collection to prevent this type of behaviour even though you say it was optional,

    I would recommend using specific Deploy collections that are populated with machines that you intend to deploy an os to

    eg:

    Deploy
    >>Deploy XP
    >>Deploy Vista
    >>Deploy Server 2008
    >>Deploy 7

    and so forth,

    as regards your actual problems reading your logs may reveal what actually happened and why

    cheers
    niall
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
  • Friday, November 06, 2009 9:29 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks!