Your network contains a System Center 2012 Configuration Manager environment. You deploy the Configuration Manager client to all client computers. You enable Hardware Inventory and Software Inventory

Question

Options

• ADataldr.log
• BInventoryagent.log
• CMp_hinv.log
• DContenttransfermanager.log

• A
  93% (14)
• C
  7% (1)

Explanation

Technical Reference for Log Files in Configuration Manager Site Server log file Records information about the processing of Management Information Format (MIF) files and hardware inventory in the Configuration Manager database. Further information 1: Site system server log file Records details about the conversion of XML hardware inventory records from clients and the copy of those files to the site server. InventoryAgent.log Records activities of hardware inventory, software inventory, and heartbeat discovery actions on Contenttransfermanager.log Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access packages. Further information 2: Troubleshooting Configuration Manager Performance Slow Hardware Inventory Processing - Solution If you suspect that hardware inventory report processing is slow for a Configuration Manager 2007 site, the following actions should be taken: Inspect the client inventoryagent.log log file to determine whether the client is sending delta hardware inventory reports or full reports. After initial client deployment, a very high percentage of hardware inventory reports should be deltas, which contain much less data than full inventory reports. If you are seeing a significant number of full inventory reports, this could be caused by inconsistent inventory report processing by the site server. For example, a delta hardware inventory report could be processed before a full inventory report for the same system has been processed. In this situation, a hardware inventory resynchronization request will be sent to the client and an additional full inventory report will be generated. To determine whether this is happening, review the dataldr.log log file on the site Inspect the size of the hardware inventory files in the site server's inbox directory to determine whether the software inventory files have grown significantly from previous inventory reports. If hardware inventory report file sizes have grown beyond an initial hardware inventory report file size baseline, you should determine the cause and whether the larger inventory report files are expected to be larger. One possibility is that the site’s SMS_def.mof file has been modified to collect more inventory information from clients. Determine whether there is a consistent SMS_def.mof hardware inventory reporting file in use throughout the hierarchy. If not, the hardware inventory processor might be running very slowly because of changes in the database schema caused by the different SMS_def.mof files throughout the hierarchy. The dataloader.log log file will record instances of database schema changes and should be reviewed when investigating this issue. This article was originally written for SMS, but the same principles should apply to SCCM 2012: Chapter 20 - Hardware and Software Inventory Flowcharts If a backlog of MIF files accumulates at the site server (that is, if MIF files are not being Examine the Inventory Data Loader status messages or the Dataldr.log file to determine whether the Inventory Data Loader has been able to connect to the SMS site database server. Inventory Data Loader might be unable to write a discovered client's MIF to the database. If the MIF files are not being processed on the site server: Verify that Inventory Data Loader successfully parsed the MIF file by checking Inventory Data Loader status messages or the Dataldr.log file. If the MIF file cannot be processed, it will be transferred to the \Badmifs directory. If inventory from clients is not being reported to a new parent site: Examine the Dataldr.log file to verify that Inventory Data Loader has read the *.sha file, stopped all new MIF file processing, and is creating MIF files for each client's data in the site database to forward to the parent site.

No community discussion yet for this question.