If you haven’t read part 1 of this article series yet I recommend you do.
Once you’ve properly extended the SCCM hardware inventory you should now focus your attention on the clients. In order for the clients to pick up their new marching orders they will need to retrieve a new machine policy. You can either wait for this to happen naturally or force refresh a few immediately. I recommend refreshing a couple just to make sure the 2 new inventory classes you’ve created were configured correctly.
Once you refresh the machine policy on a few clients go ahead and request a hardware inventory cycle as well. If you know off hand a couple of clients you know were imaged via SCCM/MDT, use those as the initial tests as well as a couple you know were done via other methods. This way you can confirm if the imaged clients are reporting and the non-imaged clients are not.
Check your logs
After the policy refresh and hardware inventory cycle, check the clients’ inventoryagent.log file. In this file you should see a couple references like these:
If you do, that’s good! That means the client knows about your new inventory classes! The next log you need to look at is dataldr.log. This log file is located in C:\Program Files\Microsoft Configuration Manager\Logs or related directory on your site server.
Look for lines like this:
If you see that, you’re golden! This means the client successfully ran a hardware inventory cycle and the site server inserted the results into the database.
At this point all of your clients either have or will be getting their updated machine policy and will eventually run a hardware inventory cycle depending on your schedule. Personally, I’d wait a couple days for all your clients to report in. When I originally set this report up I was all excited about and wanted to see results right away! It’s not a good idea because if you know SCCM well enough you know everything takes a long time to run. Making a client change like this is no different.