Today I will be sharing that. You have successfully implemented your System center configuration environment. It was working fine as expected. After couple of day your manager ask to provide details inventory of the Hardware. While validate in console found that none of the client sending inventory.

In this Article I have divided in two:

Phase 1: Client Side Inventory Troubleshooting How validate on client side

Phase 2: Client send Inventory How to Validate on Server side.

Phase 3: In my case what was issue and what bring to solutions.

Issue reported: Client is sending Hardware Inventory but none of the Client is getting update.

To bring in to solution below is root and findings let have details Looks.  

Phase. 1^st Phase how to validate on client side

Troubleshooting hardware inventory in SCCM is to look at the client log files, specifically the InventoryAgent.log. The full path for the log file is C:\Windows\CCM\Logs. Another thing you have to note, is that SCCM will never actually show that the “hardware inventory” is taking place. Instead it uses its Global Unique Identifier (GUID) to specify which inventory cycle is taking place.

Below is table shown for easier reference.

Go to the Client Log location C:\Windows\CCM\Logs à AgentInventory.log with the help of CMTrace log view in AgenInventory.log: Opening store for action {00000000-0000-0000-0000-000000000001}.

You will see below thing on Logs.

If you scroll down you will see in inventory agent logs.

Next we have to validate that process MP_HinvEndpoint is moved to next steps open log CcmMessaging.log.

You will see that Message Payload transfer completed.

Now we got to know that client is sending to Management Points.

Let’s have phase 2 How to validate on Serverside. 

Happy Learning!!!

Thanks & Regards,
Haresh Hirani
Email: [email protected]
Follow me: Twitter @hirravi1
linkedin: https://www.linkedin.com/in/hiraniconfigmgr