SCCM Client Action tab

[Aendni]

Any more suggestions for me?

 

Andi

[neilb]

Hi Aendni, I know exactly what you mean as recently had some client issues with over 200 xp machines .

 

It might be of help but I have fixed a few by doing this

 

1) Stop the ccmexec service (SMS Agent Host) on the machine you have an issue with

2) browse/locate and delete the following file "SMSCFG.INI" (should be located in c:\windows\)

3) Start the ccmexec (SMS Agent Host) service again on the machine and check that the new logs populate c:\windows\system32\ccm\logs (if thats your path)

4) Check SCCM Console for the machine and check if its registered and approved or you can use the "trace" to check the machines log files

5) Check your config mgr client to see if its populated the rest of the services other than the two you mentioned

 

I have other suggestions if you want to share information

 

Neilb

[DOnDiv76]

Hi Neilb,

I have tried your suggestion to no avail. I have all the exact same errors in my log files:

 

LocationServices: Failed to reset certificate request times. (0x80041002)

CcmExec: Endpoint'PolicyAgent_PolicyEvaluator' return 0x80070057 from event notification

PolicyEvaluator: Failed to trigger Machine settings update (80070057)

SrcUpdateMgr: Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI

 

I was thinking that this was a boundary issue. But not sure where to check. Only two actions are availble in ConfigMGR.

[DOnDiv76]

Actually, I found out what my issue was by just combing thru the CCMEXEC.log. I had this entry:

 

[CCMHTTP] HTTP ERROR: URL=http://<SERVERNAME>/ccm_system/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED

 

I doublechecked the host name of the server and it was incorrect. Populated the correct host name in in the secondary site settings and restarted the SMS Agent host on the client and VIOLA! everything started to work correctly!

 

Thanks guys for "indirectly" pointing me to the logs files!

[arovbukay]

Hi, I have the same issue. Machines that are built and have the client installed via SCCM Task Sequence dont seem to be getting the other policies, under the actions tab I have machine policy and user policy only. initiating action for either of these does not do anything. Neilb's suggestion above, deleting the SMSCFG.ini file seems to have started activity in the log files under c:\windows\system32\ccm\logs but there is nothing obvious that is erroring. this seems to have started some time last week, machines built in the same way prior to a day last week are fine, all newly built machines have client issues. Any ideas?

[arovbukay]

to confuse matters even more, just found that it's not ALL machines but most, just rebuilt one where the client is fine. Action components are there.

[Peter van der Woude]

You really should be looking at the client logs (like Locationservices.log, Clientlocation.log and ClientIDmanager.log)

[arovbukay]

seems like all machines are having this problem afterall. checked ClientIDmanagerStartup.log and found that the client is not registering, it keeps cycling but never actually registers. The only way I can get this working is to delete the machine entry from SCCM and reinstall the client. Not sure why this has started happening all of a sudden.