Tuesday, October 2, 2012

Unknown computer bug in ConfigMgr 2012

When re-deploying an already deployed system with ConfigMgr 2012, an error message is sometimes displayed: "Failed to Run task sequence, There are no task sequences available for this computer". This because the system is already available in the ConfigMgr console as a "unknown" system. Because of that the "All Unknown Computers" deployment isn't used and a deployment on a known computers collection isn't used also. This because in system properties: "Unknown Computer = 1" is detected. No way to install this system again!?


As a workaround it's possible to delete the created object in ConfigMgr collections to re-deploy a system again. After deleting the system(s) the error message: "Failed to Run task sequence, There are no task sequences available for this computer" will be gone. Unfortunately after re-deployment the same thing happens again, so it's no real solution to this problem. Another solution to resolve this is mentioned HERE. It says: Add a query rule to the Collection that grabs new computers where the System Resource “Unknown Computer” property = “1”.


I tried that solution myself also, but it don't seems to work either. A "Unknown Computer Bug Update" can be found HERE. It mentions: 
"The final response back from Microsoft via Connect was that this would be submitted to the Product Group as a Design Change Request". Hope it will be solved soon! Strange enough I don't have this issue at all ConfigMgr 2012 implementations? Anyone?

Update: For it seems this is only a problem when working with workgroup systems. When working with domain members there isn't any error message. That explaines why I haven't see this problem before.

Update 16-6: Unchecking "Unknown Computer Support" on the DP/PXE in question restarting the executive on the Primary and then reselecting "Unknown Computer Support" on the DP/PXE in question and restarting the executive resolves this issue. The problem you're running into is an corrupt policy on the MP. By Unchecking the option mentioned this will create a new policy and your unknown systems should pick up the TS when in WinPE.

15 comments:

  1. hi there
    I am experiencing this exact problem. I have deployed af TS to the same Tablet about 5-7 times. Suddenly it stops working with the error Ts failed 0x80004005 . I have removed all unkown objects as explained in your article but still i cant deploy to them. Have you seen this problem?

    ReplyDelete
    Replies
    1. Hi there, what's the exact error message in the SMSTS.log file? Otherwise it's hard to troubleshoot. Hope it helps!

      Delete
  2. Same problem here' I don't know what to do with that bug before. Glad that I saw your post. I've got an idea.

    ReplyDelete
  3. Unchecking "Unknown Computer Support" on the DP/PXE in question restarting the executive on the Primary and then reselecting "Unknown Computer Support" on the DP/PXE in question and restarting the executive resolves this issue. The problem you're running into is an corrupt policy on the MP. By Unchecking the option mentioned this will create a new policy and your unknown systems should pick up the TS when in WinPE.

    ReplyDelete
    Replies
    1. Thanks for mentioning! Will update the blogpost.

      Delete
  4. How do you restart executive?

    ReplyDelete
    Replies
    1. It's a service called SMS Executive. Hope it helps!

      Delete
  5. Thanks for the "Update 16-6" tip.
    This solution worked with SCCM 2012 1605.

    ReplyDelete
  6. Same thing is occurring on SCCM 2016 (which has the same code-base as 2012 R2 1606, I understand). Except - unknown computer support is turned off in our case. 1st Deployment was successful but failed domain-join due to an account permission error (so resultant machine was a workgroup member - but "unknown computer" flag is not set for it), now additional attempts result in "Failed to Run task sequence, There are no task sequences available for this computer". I have tried the opposite of your suggestion by Enabling Unknown Computer Support, restarting the Executive, re-disabling Unknown Computer Support. This has not worked unfortunately..... (I'll continue and post if resolved) - Keith

    ReplyDelete
  7. Adding to my note on SCCM 2016: The computer had never previously been built, so it had not yet been approved. Once I approved it in the console, the build task sequence applied again. - Keith

    ReplyDelete
    Replies
    1. That's right indeed. When using default Site settings, workgroup systems are not approved automatically. Manually approve the system will be the solution then.

      Delete
  8. Any luck with this Keith?
    I've just done a 2012_r2_sp1 to 1606 upgrade in a test environment and cannot get a PC to image because of "no task sequences available".

    Can see PCs have the task sequence deployed to them in the SCCM console

    ReplyDelete
  9. Hi there!

    Just to add that I had a similar problem on my environment and only solved the problem with this procedure:
    https://www.windows-noob.com/forums/topic/15543-sccm-1703-osd-not-working%E2%80%93-no-task-sequences-available/

    hope it helps someone.

    cheers

    ReplyDelete