SCCM 2012 SP1 – There are no task sequences available to this computer

Came across a weird issue yesterday where a machine had been imaged and the wrong task sequence was selected. Usually not a big deal, but in this case the TS that was selected didn't have drivers for that model to be imported. Because of the lack of network driver, the image did not join the domain and the TS after applying the WIM. 

Again, not a big deal, just reimage again, right? However, after the initial attempt, we couldn't. The client booted into PXE server fine, boot image started up, but right after preparing network connections the screen would go black and the machine would restart. Thankfully I had command-line support enabled on the boot image with CMTrace in there, and I was able to hit F8 to find out what happening. The log files revealed the message below. 

Sorry for the poor quality....

No task sequence associated? It imaged before. Not now? Turns out the computer record was wiped from the ConfigMgr database so the computer was no longer "known" or managed, but also not "unknown" as it must have recognized the SMBIOSGUID, or something. I'm still unsure of why it was out in "La-la land", but nonetheless it was. Did some research and found these three extremely helpful blog posts (thanks, guys!):

http://henkhoogendoorn.blogspot.com/2012/10/unknown-computer-bug-in-configmgr-2012.html

http://verbalprocessor.com/2012/04/06/unknown-computer-bug-in-configuration-manager-2012/

http://verbalprocessor.com/2012/04/17/unknown-computer-bugupdate/

However, after following them, I deleted all Unknown computers (not the default x86 and x64 ones - be aware) I still couldn't image the client and the log files still showed the same message. My SMBIOSGUID, UUID, or MAC address never matched. Searched all machines and couldn't find it. So, next logical thing to do was to import the computer data manually and add it to the ConfigMgr databse, since it apparently wasn't in there. I did so, no luck. Dang...forgot to approve it. Went back and approved it....BAM. Found its task sequences and imaged beautifully. 

I guess it's the fact it didn't join the domain after the image, before the Windows and ConfigMgr Setup task took place is the culprit. Hard to say if it bug or by design, though the above says it's by design. 

Also note that we had another instance, and before F-disking the hard drive and wiping it clean (bad move) we joined that machine to the domain and it could image again, without manually importing computer in ConfigMgr. Hope this made some sense and helps someone.