Andre Della Monica's blog

Andre Della Monica's Manageability ConfigMgr blog

ConfigMgr 2012 - Hardware Inventory sizing challenge

ConfigMgr 2012 - Hardware Inventory sizing challenge

  • Comments 1
  • Likes

My customer asked me about having a more accurate size for specific Hardware Inventory information (Full and Delta) which are sent from the clients to the Site Server, they wanted to know how can they size their database that is going to work with ConfigMgr 2012, so I decided to talk about this here.


The hardware inventory files don't go directly to the Site Server, before that, we have other components (actually a bunch of them) working behind of scenes until the client creates his .XML HINV report/file (which is also hidden on the client side by default) and sent to the Management Point that will convert it onto a .MIF file that will be processed by Data Loader component on Site Server. (Really high-level process, I can post further information about this process on another post)
We know that each client requires approximately 3 MB of space in the database but that will depends of the number of HINV customizations you have in your environment. There is an known trick for SMS 2003/SCCM 2007 which it is still applicable to ConfigMgr 2012 to gather the Full/Delta HINV file size that it can be used on the client side:

1. To save off inventory reports on a client that is not a Management Point, create the following folder:

      %systemroot%\windows\ccm\inventory\temp\archive_reports.sms

2. To save off inventory reports on a client that is not an Management Point, create the following folder:

     <x>:\sms_ccm\inventory\temp\archive_reports.sms

The .XML file will be saved in the inventory\temp folder and this means that it will be only archived on the client side and it will keep sending the HINV information to the Management Point. After that, you just need to see the file size (I'd recommend doing this for a few clients) then you will have the HINV file size baseline by calculating the file size X number of clients of you environment. Also you can open the .XML file in order to see the information gathered from WMI by viewing with notepad or other .xml viewer.


This is really usefull when we need to troubleshoot HINV and to know if the client is sending not only HINV but also the following:

      1. Software Inventory
      2. Discovery Data (Heartbeat)
      3. Software Metering usage reports

You can delete the folder: "archive_reports.sms" after you gathered the sizing information or even after your troubleshooting, the client will stop archiving the HINV, SINV, Discovery Data or Software Metering usage reports on \inventory\temp folder.

I hope that helps!

Cheers,

Andre Della Monica (SMS/SCCM PFE)

Comments
  • Great Post. Thanks...

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment