Jump to content


MSolouma

SCCM 2012 _ PXE error (no advertisement found)

Recommended Posts

1st I am trying to install on a new object

and i also try to import computer info in to Device collection

 

The error happens on the 2 cases

 

In the 1st instance is the task sequence deployed to the All Unknown Computers collection

 

In the 2nd instance is the task sequence deployed to the collection the device is imported into?

Share this post


Link to post
Share on other sites

Is this happening on all PXE deployments to every system you are trying to OSD via PXE? OR just this system?

If it is just this system you could Push the task sequence out as required to this system (isolate the computer object and add it to a custom collection) with only media and PXE option selected on TS deployment and see what happens.

 

Also, which architecture of boot file are you using in your TS?

Share this post


Link to post
Share on other sites

Is this happening on all PXE deployments to every system you are trying to OSD via PXE? OR just this system?

If it is just this system you could Push the task sequence out as required to this system (isolate the computer object and add it to a custom collection) with only media and PXE option selected on TS deployment and see what happens.

 

Also, which architecture of boot file are you using in your TS?

yes i can not deploy any OS via PXE

:(

Share this post


Link to post
Share on other sites

How about adding the FQDN of the boot server hostname and also using the x86 path for the boot file, so the path will be SMSBoot\x86\wdsnbp.com and the host name will be name of server.fqdn as opposed to the IP address of it.

Share this post


Link to post
Share on other sites

How about adding the FQDN of the boot server hostname and also using the x86 path for the boot file, so the path will be SMSBoot\x86\wdsnbp.com and the host name will be name of server.fqdn as opposed to the IP address of it.

thank you Rocket Man

i changed my DHCP config to your recommendation with no action :(

Share this post


Link to post
Share on other sites

And you have specified in the options of both boot wim files to deploy from PXE server?

 

The PXE boot aborted usually means that the system has had a previous PXE deployment sent out to it, so in your case you say you never have been able to image any machine using PXE method, just double check that there is no PXE flag set on the system(s) that you are trying to OSD via PXE, if there is clear the flag and try again..

Share this post


Link to post
Share on other sites

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...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.