KeithDib Posted January 21, 2014 Report post Posted January 21, 2014 Hi i am using SCCM 2007R3 on a 2008R2 Server All was working fine until yesterday I enabled Unicast for testing, this worked fine but slow, so I unticked the box again. This broke the WDS service some how. I could not get it to restart. I went through the procedure of removing WDS and PXE point etc, then rebooted and added these functions back, this took a few attempts as when reinstalled the WDS service would not restart. This needed to be reinstalled three times and rebooted about 6 times before this service was running again. Although the WDS service is running, I cannot get either WDS or PXE Point to respond to any requests. I have created new BOOT WIMs etc just in case but I keep getting "PXE-E53" errors, but the PXE is not passing the requests to the PXE[sccm] server To me [looking at the smspxe.log] the WDS is receiving the requests but the PXE is not getting them passed to it. This is due to the log saying "Warning: Matching Processor Architetcure Boot Image (0) not found" but this message is coming from WDS not PXE Everything looks to be configured as per before this problem but clearly something is not right please help I have attached the smspxe.log Keith Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 21, 2014 Report post Posted January 21, 2014 "Warning: Matching Processor Architetcure Boot Image (0) not found" Have you updated your TS to use the new boot files?? Quote Share this post Link to post Share on other sites More sharing options...
KeithDib Posted January 21, 2014 Report post Posted January 21, 2014 Have you updated your TS to use the new boot files?? Hi yes I have created new WIM boot disks, but its WDS reporting this NOT SCCM, OSD is not taking over the PXE service from WDS Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 21, 2014 Report post Posted January 21, 2014 Have you edited your TS and added the newly created boot.wims to suit? You say you created new files... so your task sequence has to be up dated to use them. Have you done this? Quote Share this post Link to post Share on other sites More sharing options...
KeithDib Posted January 21, 2014 Report post Posted January 21, 2014 yes, all done as above Quote Share this post Link to post Share on other sites More sharing options...
KeithDib Posted January 22, 2014 Report post Posted January 22, 2014 NOW RESOLVED I removed all the WDS and PXE Point for about the 6th time, then put it all back on exactly the same way as I have done many times and this time it worked... Time for an upgrade to SCCM 2012 I think Thanks for the help anyway guys Quote Share this post Link to post Share on other sites More sharing options...
