Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED ccmexec component is in disabled state

Dineshyadav

Well-Known Member
Messages
46
Reaction score
0
Points
8
I have been noticing that clients are not getting any policies from the MP. I could see only 2 policies under action tab. computer and user related policy. but on components, I noticed that ccmexec component is in disabled state. this is noticed on machines from a trusted domain and also on a different forest which is not trusted by the domain on which configuration manager is installed. looking for help. is this a known issue with cm2012 r2.
 
If you are finding just 2 policies under the action tab then the client agents are not able to communicate to the MP. Check if boundary and boundary groups are configured correctly.

Check locationservices.log if it has got correct MP locations.

If the MP is working fine check policyagent.log file on the client computer. (Log location: C:\Windows\System32\CCM\Logs)

On the client computer check the following log files (%windir%\ccm\logs):

- Inventory log: should have information about heartbeat DDR, hw/sw inventory)

- PolicyEvaluator.log should give you information when a new policy has been applied or not
 
Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process:

  1. Client location services identify the site code and the MP it is supposed to connect to.
  2. The client connects to the Management Point and downloads the policies.
  3. Once the policies are downloaded it sends the heartbeat record to the server.
  4. Once the server receives this heartbeat record these are converted in to DDR and processed. This will set the client flag to 1 which will make the client status display as Yes in the console.
  5. On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to No.
 
Strange, after I restarted the SCCM server its working fine. After the restart I had to wait for half and hour.
 

Forum statistics

Threads
7,028
Messages
27,500
Members
17,680
Latest member
Symetria
Back
Top