When it is just the wireless MAC, PXE fails if lists just the Ethernet MAC or both MACs, it will PXE. On laptops it seems it can be either the Ethernet MAC, the wireless MAC or sometimes both. On desktops, this will be the Ethernet MAC. Right clicking the device and going to Properties on the General tab there is a MAC Address listed. Have not messed with Unknown Computers, dont have the confidence to deal with that yet. I have OSD task deployed to a custom collection and computers are added to the collection when they are ready to be imaged. Sorry, there are lots of variables involved. Sometimes those help when machines get stuck. You can also right click on the device in SCCM an clear PXE requests or even see if the Approve option is available. If you have it advertised to another collection, make sure that the device appears in that collection. What collection(s) have you deployed your PXE enabled TS to? If it’s only Unknown computers, that’s why you can’t boot with a device that has an SCCM record. When the device boot into PXE you should be able to monitor the smspxe log on the DP that is responding to the PXE request and it will show the MAC that the laptop is attempting to connect with. The AD Discovery agent will report what it knows about. The Heartbeat agent will report limited info from the active adapter. The SCCM client will report your hardware inventory. The data in SCCM is from the various inventory and discovery options that you have set up. When you PXE, you should see the LAN MAC. Unless you’ve done something special in PXE, you can’t natively PXE using WiFi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |