We have ConfigMgr 07 setup deploying images to All Unknown computers and a reimg collection via PXE. Everything worked great for a year, up until yesterday. Now whenever we try and image anything (bare metal or replacement) the computer gets into WinPE, applies windows settings, gets to the apply network settings phase and then stops and reboots. Checking the SMSTS.log right after the network settings phase the following error appears: There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; Source: Windows). I have verified that there are advertisements to the All Unknown Computers collection as well as our reimaging collection, which the computers to be reimaged are members of. I have gone through all the duplicate GUID steps verifying that there are not duplicate items in configmgr and adding the GUIDs to the BannedGuids registry key just in case. I have also verified that the site certs are all still active (they expire tomorrow which I will take care of today). Neither of which have had any impact further than that I (and Google search results) have run out of ideas. Thanks,

make note of the MAC address, then open the SMSPXE.log file in trace32.exe, while looking in that tool pxe boot the computer, do you see any reference to your mac address in the log and if so, what does it tell you about it ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Could you please confirm whether the Task Sequence Advertisement is not expired.

In the SMSPXE.log I see that it lookups the device, succeeds, and then "Device not found in the database" which is correct as this is a bare metal image. The Task sequence ads are set to never expire.

Hi Does this affect ALL machines? Best regards, Kenny

Do some modification in the Task Sequence Advertisement like Change the Schedule or adding Description. It will trigger a Policy update on the MP. Check whether it helps.

Yes this was affecting all machines we tried to image (or re-image). I discovered today that all our SCCM certificates expired yesterday. So after resolving that, imaging works again. Nothing else changed except the certificates, which I repeat were not yet expired when the imaging problem began, so I can't be sure what fixed this issue for us.

Tom, do you recall which certificate caused the failure? I'm experiencing a similar issue, however my SCCM PXE certificate looks good.