Skip to content

how to get rid of abortpxe.com

Featured Replies

Note: this works for me, your mileage may vary, it's worth a try, let me know if it helps.

if you've just started testing with SCCM you'll no doubt see this when imaging a client over and over, after you image the computer you cannot image it again until you right click on the computer in SCCM and choose 'clear last PXE advertisement'

clear_last_pxe.jpg

when you do that, you should be able to image the computer again, which is great when you are testing clients over and over to get your Task Sequence working...

however, after doing this a few times it no longer works, the clear last PXE advertisement no longer works

no_pxe_advertisement_listed.jpg

and when you PXE boot the client you still see the abortpxe message

Downloaded WDSNBP

Architecture: x64

The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved.

Pending Request ID: 45

Contacting Server: 192.168.3.1.
TFTP Download: smsboot\x64\abortpxe.com

PXE Boot aborted. Booting to next device...

Those lines above have added to my grey hair content many times as I would try all sort of things to resolve this including

1. deleting the advertisement and re-advertising it
2. restarting WDS and DHCP service
3. restarting SCCM server
4. all of the above and then some....

until finally I tried the following method which appears to work just fine,

Step 1.Add a rule

Add a direct membership rule on the collection you are deploying to by right clicking on it and choose properties.

properties.jpg

click on the Membership Rules tab

membership_rules_tab.jpg

click on the blue computer icon to create a direct membership rule

membership_rules.jpg

when the wizard appears click next

change the drop down menus so they are like this

Resource Class: System Resource
Attribute name: Name

*you can choose Netbios Name also*

resource_class.jpg

enter your computername that you want to remove the abortpxe.com feature from in lowercase or use wildcards eg: dell%

d.jpg

click next and leave the collection blank, click next again

blank.jpg

and here's the fun part !!!

look at the list, theres TWO of the computers with the same name... select them both *or only one if one appears* and click next

two_listed.jpg

click finish and then click ok at this screen

3_now.jpg

Step 2. Refresh the collection

Refresh the collection by selecting it and hitting F5

you should now see more than one of your original computers listed with the same name...

obsolete.jpg

Step 3. You are done !

That's it, your advertisement will begin working again now as now SCCM 'sees' the computer again. If you want you can delete the obsolete computers listed, it really doesn't matter if you leave them there or delete them.

delete.jpg

that's it smile.gif

abortpxe.com is kaboof !

 

related reading > http://blogs.msdn.com/b/steverac/archive/2013/10/03/delete-behavior-for-devices-in-configmgr-2012.aspx

  • 6 months later...
  • Replies 39
  • Views 284.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Thanks! Solved the problem with this before reinstalling the PXE servicepoint and WDS

  • I signed up for an account just to thank you! I had spent hours trying to clear one of my test imaging machines. This worked perfectly. I have used several of your postings to fix issues. Thanks a

  • Registered to say thank you!

Posted Images

I had the same problem. It lost at least one day "trialerroring"before i found your sollution.

Just wanted to thank you!

  • 2 months later...

Your solution saved me from more grey hair growing outta ma head!

  • 2 weeks later...

Hi Anyweb,

just wondering if this would be possible on a domain level.... like could i put a naming standard in instead of a hostname?

 

e.g. LXXXYYY* ?

 

going to test it today anyway ... let you know if i figure anything out...

Hi Anyweb,

just wondering if this would be possible on a domain level.... like could i put a naming standard in instead of a hostname?

 

e.g. LXXXYYY* ?

 

going to test it today anyway ... let you know if i figure anything out...

 

 

yup works perfectly using L% or D%

 

FYI i set my collection to update at 15minute intervals (lab) and picked up the changes.....

  • 2 months later...

it worked for me too !

BUT, my problem was slightly different.

 

After creating a computer association a particular PC was refusing to appear in the OS deployment collection. I added it over and over again, all in vain!

 

I did your procedure but put % as the value of the atribute - resource name. Then the wizard found the troublesome PC! I checked it's box and viola! it appeared in the OSD collection. The aportPXE went away too!

 

Thanks!

well, I just wanna report that this method does not work for all machines.

 

For one particular machine, no matter what I do.....abortpxe still happens.

I wonder what else can I do about it.

  • 3 weeks later...

Hi,

 

please help me to resolve the following issue on SCCM 2007 SP2.

 

after booting the client machine from SCCM boot image

 

Windows PE.bmp

 

the client system gets rebooted and getting the pxe boot aborted. booting to next device error.

 

Thanks

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.