Click on Pictures to View

To view a larger version of an image within a post, just click on the picture you want to view :)

Wednesday, June 8, 2016

Fix: SCCM 2012 Client Check Shows No Results

This post was copied and slightly modified from Dale's Tech Blog post on the issue.  See bottom for source link.



Computer SCCM client lists "No Results" for "Client Check Result" in the System Center 2012 Console














Problem: SCCM client computer listed as "no results" for "client check result" in the system center 2012 console client monitor. You'll notice on the problem computer that it's missing the ccmeval.log and you'll see errors in the ccmevaltask.log file.

The ccmeval.exe is run from a scheduled task that is created upon installation of the agent. This task is run daily to allow the computer to check-in with the sccm server. More than likely this error condition occurs when a client agent was upgraded, but for some reason the scheduled task wasn’t recreated. On the problem computer you'll see listed under the task results "not registered" or other failure codes.

Solution 1:  On the computer with the problem client, in Task Scheduler under Configuration Manager folder in the Microsoft folder, right click and Run the task Configuration Manager Health Evaluation.  Refresh page, and verify task updates to show “Last Run Time” as the current time (when the task was Run).

If this doesn't fix the issue, try solution 2 below (from Dale's Tech Blog).

Try Solution 2: On the computer with the problem client open the Task Scheduler in Control Panel. Open Microsoft folder in the Task Scheduler Library, then Configuration Manager and delete all listed entries. Initiate the “install client” with the “always install” option checked from within the SCCM 2012 console. The scheduled tasks should be recreated when the agent installs and the computer will start checking in appropriately to the SCCM server. Check the local computers ccmeval.log file for more details.

After implementing one of the above solutions, prompt the client to check in with the SCCM server by running that client’s Data Discovery Collection Cycle either by opening from Control Panel > Configuration Manager, go to Actions Tab, and selecting and running the task, or using Right Click Tools, if installed, in the SCCM console.

Tip:  Open up the Task Scheduler by either typing "task" into the Start Menu search bar, or by opening All Programs > Accessories > System Tools OR go to Control Panel > Administrative Tools


Source:

8 comments:

  1. Step 1 worked for me, thanks

    ReplyDelete
  2. Step 1 worked for me as well, thank you.

    ReplyDelete
  3. Option 1 worked for me as well. Thank you!

    ReplyDelete
  4. Hi Jenni
    Solution 1 works for me, but I have to do it for every new client I install
    do you have any idea why this is happening?
    I did not expand the ad schema, could it be the cause?
    Thanks

    ReplyDelete
    Replies
    1. Hey Simone--z, sorry for the massive delay! Are the clients being installed manually or pushed via SCCM Admin Console, or during an "image" task sequence, etc? I would double check where something could be misconfigured in the admin console or going wrong during the install process. Some logs you might find helpful checking include the ccmsetup.log, ccmexec.log, scheduler.log, and for task sequence deployed clients also smsts.log.

      Delete
  5. Solution 1 worked perfectly

    ReplyDelete
  6. Hi Solution 1 works for me

    ReplyDelete

Give my post a +1 or let me know if you found any of my blog content helpful!