locked
Client check failed on XP/Server 2003 systems only--ccmeval is not being scheduled RRS feed

  • Question

  • Hi, I have SCCM 2012 RTM installed in our environment that has mostly Windows XP machines and some Windows 7 machines, and about an even mix of server 2003/2008 R2

    The Windows 7 and 2008 machines that are regularly used are showing as Active and with Client Check Result Passed.

    Windows XP and 2003 machines that are regularly used are initally showing Active and Client Check Result Passed. However, after 7 days they are still showing Active but with Cleint Check Result Failed. When I look at Client Check Detail, it says "Verify CcmEval task has run in recent cycles" and the evaluation time shows as a few days after the client was installed on that computer.

    If I manually run ccmeval on the Windows XP machines, then they do show as passed.

    From this link http://blogs.technet.com/b/configmgrteam/archive/2011/05/03/client-health-in-configuration-manager-2012-beta-2.aspx I understand that a scheduled task for ccmeval.exe should have been set up to run daily. On Windows 7 machines, this has been done, however, Windows XP machines do not have that task scheduled?

    How can I fix this? How can I make sure that it gets scheduled on other XP/2003 machines?

    Thanks

    Monday, May 7, 2012 3:59 PM

Answers

  • the solution is to check the following group policy:

    Computer Configuration:

    Policies
      Administrative Templates
        Windows Components / Task Scheduler
    "Prohibit New Task Creation" 

    this should be set to disabled or not configured. when it is enabled, the scheduler cannot be used by interactive users. SCCM for some retarded reason, uses a user session to create the task, rather than doing via the command line, which this policy does not disable.

    Also, check the obvious, the service itself, and make sure your policy allows it to run, and isnt altering the default permissions. 

    Monday, September 24, 2012 6:57 PM

All replies

  • Does ccmeval.log show any activities on the XP machines?

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 7, 2012 5:16 PM
  • So when you go under Scheduled Tasks in the XP Control Panel, it doesn;t show the task (pictured below)? Also, what does ccmevaltask.log have to say?


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Monday, May 7, 2012 6:14 PM
  • Torsten, the ccmeval.log does not exist on the systems that I have not manually run ccmeval.

    Jason, you are correct, the Configuration Manager Health Evaluation task does not show up under Scheduled Tasks in the XP control panel.

    The ccmevaltask.log has the following:

    <![LOG[Client evaluation task is missing.]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="2" thread="2936" file="ccmevalsched.cpp:123">
    <![LOG[Attempting to recreate the scheduled task.]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="1" thread="2936" file="ccmevalsched.cpp:135">
    <![LOG[Failed to create the client evaluation task]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="2" thread="2936" file="ccmevalsched.cpp:139">
    <![LOG[Current time is 2012/05/05 09:52:08 (UTC), last evaluation time is 2012/04/19 16:30:33 (UTC), not run threshold is 4320 minutes]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="2" thread="2936" file="ccmevalcheck.cpp:217">
    <![LOG[CcmEval failed to run in recent 4 cycles and reaches the maximum cycles, build and send a report on that]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="2" thread="2936" file="ccmevalcheck.cpp:91">
    <![LOG[Send previous report if needed.]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="1" thread="2936" file="messagesender.cpp:281">
    <![LOG[Previous report was successfully sent, no need to resend.]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="1" thread="2936" file="messagesender.cpp:288">
    <![LOG[Previous site code DOR, current site code DOR]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="1" thread="2936" file="messagesender.cpp:371">
    <![LOG[Report is built but not necessary to send]LOG]!><time="05:52:08.016+240" date="05-05-2012" component="CcmEvalTask" context="" type="1" thread="2936" file="messagesender.cpp:471">

    Unfortunately I don't see why it is failing. What user is used to create the scheduled task?

    Thank you

    Monday, May 7, 2012 7:10 PM
  • Given that the ConfigMgr client is running as local system, it should be using local system.

    Do you have a group policy in place or some other type of security software in place?

    You can try to correlate the time shown for the above failed creation to events in your Windows, System, or Security event logs to see if that provides any clues.


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Monday, May 7, 2012 8:06 PM
  • There were no events corresponding to the hourly attempts to schedule that task.

    After reviewing RSOP for one of the affected machines, I do see that we have a Conficker Block GPO http://support.microsoft.com/kb/962007 which prevents local system from creating a scheduled task. I've turned that GPO off and I will see if the task gets scheduled. It seems that GPO isn't really meant to be turned on all of the time anyway.

    Thanks so much for your suggestion. I will report back with my results.


    • Edited by taymac Monday, May 7, 2012 9:21 PM
    Monday, May 7, 2012 9:04 PM
  • It was definitely the conficker blocker GPO that was preventing this from happening.
    Friday, May 11, 2012 7:36 PM
  • It was definitely the conficker blocker GPO that was preventing this from happening.

     Hello,

    I have the same problem with clients XP, I have applied Conficker, How do you determine that the cause was the conficker? what other functions disables the conficker in SCCM 2012?

    Thanks 



    • Edited by Mathius_93 Thursday, August 9, 2012 1:14 AM
    Thursday, August 9, 2012 1:08 AM
  • the solution is to check the following group policy:

    Computer Configuration:

    Policies
      Administrative Templates
        Windows Components / Task Scheduler
    "Prohibit New Task Creation" 

    this should be set to disabled or not configured. when it is enabled, the scheduler cannot be used by interactive users. SCCM for some retarded reason, uses a user session to create the task, rather than doing via the command line, which this policy does not disable.

    Also, check the obvious, the service itself, and make sure your policy allows it to run, and isnt altering the default permissions. 

    Monday, September 24, 2012 6:57 PM
  • Thursday, January 10, 2013 4:22 PM
  • Great find and really value you coming back and showing us your fix. Awesome work.

    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Friday, January 25, 2013 12:46 PM