CCGStewart
asked on
Client Machines will not PXE boot in SCCM 2012
We have set up a new System Center Configuration Manager 2012 Server recently and are trying to PXE boot machines so that they execute a task sequence to deploy an Operating System. On the PXE Boot Screen, the following message comes up:
Message from Administrator: Please wait. SMS is looking for policy
Contacting server: Server IP Address
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device...
PXE-M0F: Exiting Intel Boot Agent.
In the SMSPXE log file, I see the following lines:
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 1/31/2013 3:19:40 PM 2364 (0x093C)
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
I can post full versions of the log files upon request. Any assistance would be greatly appreciated!
Message from Administrator: Please wait. SMS is looking for policy
Contacting server: Server IP Address
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device...
PXE-M0F: Exiting Intel Boot Agent.
In the SMSPXE log file, I see the following lines:
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 1/31/2013 3:19:40 PM 2364 (0x093C)
00:1B:D3:8A:17:B1, BC08771E-4E1B-AC54-9004-78
I can post full versions of the log files upon request. Any assistance would be greatly appreciated!
ASKER
The PXE flag is/has been cleared. Task sequence is deployed to the collection in question. Under the MAC address, I see that it's listing 2 of them. One is the address for the LAN connection, and the other is for the Local Area Connection 2, which is the Bluetooth Personal Area Network. This was not put in manually, but discovered on the network. Would the fact that there are 2 MAC addresses listed in there cause an issue?
I'm not seeing any duplicate objects with the same MAC address, and yes, WDS/PXE server was configured correctly. As for the boot images, I have updated them on the DP, and watched the distmgr log. From that standpoint, it appears they copied up correctly. Under the monitoring tab in the config manager console (Under Distribution Status), both boot images have a 0 in the "Targeted" field. Wim files in this same window show a status of Success under the details screen on the bottom, but neither the x86 or x64 boot images show any status on the same details screen.
I'm not seeing any duplicate objects with the same MAC address, and yes, WDS/PXE server was configured correctly. As for the boot images, I have updated them on the DP, and watched the distmgr log. From that standpoint, it appears they copied up correctly. Under the monitoring tab in the config manager console (Under Distribution Status), both boot images have a 0 in the "Targeted" field. Wim files in this same window show a status of Success under the details screen on the bottom, but neither the x86 or x64 boot images show any status on the same details screen.
ASKER
Interestingly enough, another machine that's in this same collection (with only 1 MAC address) is doing the same thing when I try to PXE boot it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Resolved the issue myself
Care to share your solution?
Should share the solution.
I was able to get the issue resolved myself.
but they don't share the solution.
Isn't that the worst? lol.
- Cleared PXE Advertisment Flag on the Client machine
- Task Sequence Deployed to the Collection where the Client is member of
. MAC Address typed n correctly
- No duplicate Objects with the same MAC Address?
- WDS / PXE Server configured correctly?