cwb124

But this is only happening on hosts that have gotten the task sequence but the task sequence failed for whatever reason. I am still working out my task sequences since we just migrated to 2012.

Making you mad??? I've been at this most of the week lol The client in the console is Client Type: NONE. Client: NO. Site Code WC1 (correct site code) You can't really delete from SCCM 2012 anymore. Not the way you could in SCCM 2007, which is one of my gripes. I think it's an issue with just this one object though. I think it's corrupt or somehow effed up. I just don't know how to fix it.

The drivers are added to WinPE for sure. This server built initially the first time it was manually added to SCCM as a computer object in a collection with a required advertisement. It's the rerunning of the task sequence that I can't get to work on at least this one host, and perhaps a couple others.

I didn't have the deployment set to Make Available to Configuration Manager Clients, media, and PXE. I only had Media and PXE. I removed the deployment and re-deployed with that set properly. Half an hour later, my tests are failing with the same exact error that there are no available task sequences. I really thought that was it. Guess not.

Did you ever resolve this problem? I am running into the same issue. We have 6 build collections, each with a different task sequence deployed to them. They are set to required and Always Rerun Program. The problem I am having is a new bare metal box will build once. If it fails at some point beyond laying down the OS and it boots to the OS and checks into SCCM, I can never get it to run that task sequence again. If I clear PXE advertisement it says there are none to clear. I verify that the task sequence is deployed to that collection and that the computer object is still in that collection. In the properties of the computer object, on the deployments tab, it shows that the task sequence is available to it. However when I PXE boot it goes into WinPE and establishes network connectivity and then reboots immediately. If I hit F8 and check out the smsts.log, I see the following: There are no task sequences available to this computer. In SCCM 2007, I could delete the object from SCCM and then re-create it. No problem. However in SCCM 2012, it handles "deletion" completely differently. Here's an article: http://myitforum.com/myitforumwp/2012/08/08/sccm-2012-when-you-delete-a-system-from-the-console-its-removed-from-v_r_system-but-still-exists-in-table-system_disc/ So I can't figure out how to redeploy a task sequence to an existing SCCM object or one that failed at some point but still checked into SCCM.