Hi,

I have a problem installing a client on a server 2008 machine. The client is installed, it is registered, it showing in SCCM Console but it is not retrieving any policies.

When I go to control panel and look at the CM->Actions tab, I only see two actions, there should be something like 8. So this tells me that client is not initialized properly.

1. ClientLocation - shows the correct site.

2. LocationServices - Shows the correct management point.

3. ClientIDManagerStartup - Shows client as registered.

4. CCMExec - Shows error <![LOG[System task 'PolicyEvaluator_Unlock' returned error code 0x8000ffff.]LOG]!><time="11:06:34.932+00" date="12-13-2013" component="CcmExec" context="" type="3" thread="23236" file="systemtask.cpp:199">.

5. PolicyEvaluator and PolicyAgent - Show no errors.

Please help. I have tried installing and reinstalling the client to no avail. The same installation method works on other clients in the same site.

Thanks

Something could be wrong with the wmi repository..  so may need to troubleshoot it.

Also, might try uninstall it again, then deleting ccmsetup and ccm afterwards.   Then push it down again.   Strangely I've noticed that the client seems to install better when no one is logged in.  Not sure if that's true but when you push a new client, make sure no one is logged into the machine for 20 minutes.

• Edited by CSMatMan Friday, December 13, 2013 1:30 PM

Hi,

I have tried deleting both folders and reinstalling the client manually, still get the same problem. Yes I am kind of leaning towards a WMI problem on the Domain Controller.

Do you know any checks on WMI that can be performed to check the repository? I don't want to just blindly rebuild the repository if possible.

Thank You

This is the guide I see handed out most when troubleshooting wmi.   Please let us know how it goes. 

http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx

• Proposed as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, December 18, 2013 8:25 AM

While almost always a possibility, WMI errors are usually  little more clear cut than this and it's rarely the place to start troubleshooting.

Is this client "approved"?

Hi,

How are things going? Please let us know if there is any progress.

Regards.

Hello all,

Apologies to hijack this thread, but we are experiencing exactly the same issue.

We are using SCCM to create our golden images for a vdi deployment.
All our vdi machines are provisioned from the same master.

We have lots of machines which are working perfectly so the backend settings such as IIS authentication, boundaries, client installation properties etc are fine.

We do have a small margin of machines which are unable to receive user policies.
When using Policy Spy, I get an error 08x80040154.
I confirmed we do not experience what is explained in following link : http://myitforum.com/myitforumwp/2013/01/11/sccm-2012-clients-not-downloading-user-policy/

Negotiate was already correctly set in the authentication providers.

I then went on to thinking what else could be causing this.
Next I set the Authentication on the CCM_System_WindowsAuth to anonymous to see if it was an authentication issue. This doesn't improve/change the behavior of the client so I set the authentication mechanism back as it was.

In the ccmexec.log I then discovered the error message which the TS was also experiencing: System task 'PolicyEvaluator_Unlock' returned error code 0x8000ffff

However, not much is to be found when looking for any posts, topics on this subject.

The client is generated from the same template which does have successful instances, but specific ones don't work.

The client shows as installed and approved.
Status messages are being successfully sent to the MP and processed and added to the record in the database.

Policy evaluation  is the only feature which isn't working. The Actions tab on the configuration manager client pane  in the control panel is only showing the  Machine Policy Evaluation & User Policy Evaluation actions.

No other actions are available.

Another strange thing which I've noticed is, is that if I restart the ccmexec service that the client will then be able to receive and process policy.

Can anybody help me on the right path to the root cause for this issue?

What is  wrong that gets fixed by an agent restart that won't allow the client to release the policyrefreshlock?

Thanks!

Filip

• Edited by Filip Theyssens 22 hours 48 minutes ago

"The client is generated from the same template which does have successful instances, but specific ones don't work."

Did you properly prepare the client agent?

Have you compared the GUIDs reported on the client agent to those showing for the resources in the console?

Do these systems have PKI issued certs for the computer?

Random error codes from log files don't help much. When posting info from logs, you need to post entire, unedited and relevant snippets. Logs are about context and flow, not out of context error codes. Sometimes, an error is actually expected and normal.

Logs to examine in detail (and not just look for error codes) include clientidmanagerstartup.log, policagent.log, and ccmmessaging.log.