ConfigMgr OSD/MDT Clear PXE Cache
I have been able to successfully boot a test machine via PXE and install an OS (using the Task Sequencer) but after building the same machine a dozen or so times SCCM stops supplying the machine with the boot WIM.
This is my test machine that i am using to to build my WIM’s with and play with other settings (thus why i am constantly rebuilding it).
The PXE service point produces a status message stating "The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned."
But this statement is not correct.
I’ve tried the following:
-
The device exists in a collection which has a TS advertisement assigned
-
The advertisement is configured to "make this TS available to WINPE and PXE"
-
I have attempted to re-run advertisement
-
I’ve removed the machine altogether and tried to use the Unknown PC function.
The same advertisement works perfectly when run from "run advertised programs" if run from within the OS.
After searching the internet i found this:
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/55cbc072-4dd4-4c0f-a7eb-d3d505cb26d1
I tried both of these solutions and found that number 2 worked best.
1. The PXE flag is set on the computer resource to indicate that the computer was booted mandatory via PXE and prevents any further PXE boots until it is cleared (right click on the computer in the collection and select "Clear Last PXE Advertisement") [should only happen if the Task Sequence is advertised mandatory]
2. A caching issue: Occurs when the ResourceID of a computer changes but the MAC address stays the same. Happens if you delete and import a computer with the same MAC address after it was booted via PXE, then SCCM/PXE tries to lookup the advertisements for the old ResourceID. You can restart the Service WDSSERVER to clear the cache of the SCCM/PXE provider and see if the problem persists.
Hope this saves someone else time.
God knows I’ve wasted enough time on this issue.