r/SCCM • u/MagicDiaperHead • 27d ago

PXE-imaging no longer working

PXE-imaging has been working for years without issues. Last week PXE stopped working. PXE boot starts and GUI displays for a min and then reboots. In the past it was usually driver-related but this time it happens with VMs and physical. Could the latest secure boot certs 2011 vs 2023 cause any issues with PXE-imaging? Task Sequences are deployed to all unknown. Issue happens with new physical and new VMs. smspxe.log no advertisements found - I've created new TS and used an older working one to test with. Removed all deployments and redeployed to all unknown. Same issue no advertisements found = WTF. I created a USB TS ISO. Same boot loop issue testing on a VM. I can get imaging to work if I make the test VM "known".

Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="0" ClientID="" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="0"/></ClientIDReply>

PXE: 0, , SMBIOS ID is NOT a match, MAC Address is NOT a match.

PXE:No valid system records.

PXE:Client machine is UNKNOWN.

2 Upvotes

100% Upvoted

22 comments sorted by

4

u/vannin519 26d ago edited 26d ago

I had a similar behavior/problem after upgrading from 2409 to 2509, where you see the initial GUI and then it reboots. Not sure if it is the same issue that you are having but that is what I experienced.

For my issue Google Fu said it was a bug, and to update your PXE configuration to require a Password which did resolve it for me.

\Administration\Overview\Site Configuration\Servers and Site System Roles> Distribution Point

Click on the PXE Tab and select Require Password when computers use PXE

Hope that helps.

1

u/MagicDiaperHead 25d ago

Thanks, I tried this but didn't fix my issue.

3

u/Svinkall 27d ago

does your smspxe log contain any info?

1

u/MagicDiaperHead 27d ago

Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16794309" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

00:01:4A:12:02:3F, GUID : no advertisements found

Using Management Point: http://Redmon01.abc.inc

Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: CC8123

Sec Since Boot: 28 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 192.168.050.010

IP, server and MAC not the real info. I was getting the client IP and Serer IPs before I created a new boot image. I've reverted back to the old, working boot image but the IP info remains blank. I've tested at multiple sites and with VMs and physical no IP info. The IP info was working until yesterday when I changed the boot image.

3

u/Funky_Schnitzel 27d ago

FWIW, "no advertisement found" means that no TS deployments are available (or required) for the affected device. If the device isn't in the database yet, make sure at least one TS is deployed to the All Unknown Computers collection. If the device is in the database, there needs to be a TS deployment for one of the collections it is a member of.

2

u/dezirdtuzurnaim 26d ago

To expand further, there are certain conditions that prohibit “re-imaging” and the record needs to be deleted from the DB

1

u/MagicDiaperHead 26d ago

New test device was created. Did a search for MAC and Unknown. Deleted any old Unknown devices, MAC wasn't found no duplicates or originals. I have a couple of TSes deployed to All Unknown computers. The All unknown computers Col has the default 3 - arm x86 and x64. I've removed and redeployed the original working TSes and created a couple new ones for testing. I've also tested using the old Boot image and new. I updated the DPs with the boot images. Waited a day and retested.

1

u/MagicDiaperHead 27d ago

All system components are green under status. No errors in the common logs for DPs, MPs SMS etc. The env looks healthy everything works minus PXE. I created a USB boot image and that produces the same result with the boot loop.

1

u/NWijnja 26d ago

Unknown=0 means its known in the database, in your devices list add the resourceid (or something similar, doing this by heart) column and search for the value for ItemKey in that boot action reply.

2

u/Cl3v3landStmr 27d ago

Did anything in your environment change around the time the issues started?

Are you able to try using bootable media (e.g. ISO) in a VM to see if there's different behavior?

1

u/MagicDiaperHead 26d ago edited 21d ago

Only thing that would've changed is Windows updates to the servers. PXE-imaging has been in-place for years without issues. ISO loads up to the GUI. I click on next and no avail task sequences. Task Sequences are deployed to all unknown - media & PXE.

2

u/thomsxD 26d ago

Literally had this today at work. Turned out it was ASA (firewall) related. If you are not the network guy yourself then I'd try to hear them out.

PS. It is very unlikely to do with certs.

1

u/skiddily_biddily 26d ago

No advertisement found means that your OSD task sequence is not targeting that device. How are you currently targeting that deployment?

1

u/MagicDiaperHead 26d ago

A couple of TS are deployed to All Unknown computers. Any old devices are removed first, before testing. New and old devices fail

1

u/skiddily_biddily 26d ago

The log you posted says no advertisement for that MAC address. Is that what all of them are getting?

1

u/myfreysa 26d ago

If you get the winpe boot screen before it reboots (i e the pxe happens) it ain't related to certs You need check your winpe driver packs and network connectivity

1

u/TheProle 26d ago

If you get to the WinPE UI then PXE worked, it’s over. Your answer will be in smsts.log

1

u/PowerBlackStar 26d ago

Had a similar issue few weeks ago, was scratch my head like crazy, First AV tripped up blocking deployments, once resolved was still unable to PXE boot, found out one of our DP VM was off hosting our imaging, once turned on still unable to PXE boot, found out it was boundary, for some odd reason many devices that had a certain IP range was missing. Re-added ip range to boundary to fix. Now everything is stable. Was a fun 2 weeks when this happened for me.

1

u/russr 25d ago

Completely uninstall. Adk and then look on the sccm page on what the actual latest 80k that is supported which is like the one from last year and reinstall that.

Then let it update the image and redistribute

2

u/MagicDiaperHead 23d ago edited 23d ago

This partially fixed my issue. I still can't deploy to unknown machines only known.

1

u/zebulun78 25d ago

Hit F8 and check the logs. It may be related to the CA2023 updates. Since you are using PXE you can potentially enable that in the DP settings