MSolouma Posted June 3, 2014 Report post Posted June 3, 2014 Hi i have an error, always happen with PXE deployment on SCCM 2012 SP1_CU4 i tray to uninstall DP ,WDS and delete Reminstall, recreate Boot images nothing no advertisements found save me Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 3, 2014 Report post Posted June 3, 2014 Are you deploying the task sequence to the collection in which the computer object exists? Quote Share this post Link to post Share on other sites More sharing options...
MSolouma Posted June 4, 2014 Report post Posted June 4, 2014 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 Quote Share this post Link to post Share on other sites More sharing options...
SCCMentor Posted June 4, 2014 Report post Posted June 4, 2014 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? Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted June 4, 2014 Report post Posted June 4, 2014 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? Quote Share this post Link to post Share on other sites More sharing options...
MSolouma Posted June 9, 2014 Report post Posted June 9, 2014 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? yes i did Quote Share this post Link to post Share on other sites More sharing options...
MSolouma Posted June 9, 2014 Report post Posted June 9, 2014 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 Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted June 9, 2014 Report post Posted June 9, 2014 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. Quote Share this post Link to post Share on other sites More sharing options...
MSolouma Posted June 10, 2014 Report post Posted June 10, 2014 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 Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted June 10, 2014 Report post Posted June 10, 2014 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.. Quote Share this post Link to post Share on other sites More sharing options...