Sccm Software Inventory Not Reporting
In client configuration manager console there are just two actions listed and clients can not send inventory information to the SCCM server ( hardware and software ), also dbo.vSoftwareFile view in sql is empty. All settings are configured correctly but still SCCM can not collect data from clients. If you are using the Software Updates feature (not ITMU) in ConfigMgr. Then data is not collected with hardware inventory. You should look at the wuahandler.log on the client to see if a scanning has been successfully performed. Our SCCM Software Inventory reports shows installed software on your devices using SCCM Asset Intelligence data. SCCM Software Inventory reports is broken down into 2 distinct reports: Installed Software – Overview: This reports shows a count of a specific software installed on devices. You can enter the desired software or scope it using a.
- Free Software Inventory Tool
- Sccm Software Inventory Not Reporting Software
- Sccm Installed Software Inventory
Applies to: System Center Configuration Manager (Current Branch)
Use software inventory to collect information about files on client devices. Software inventory can also collect files from client devices and store them on the site server. Software inventory is collected when you select the Enable software inventory on clients setting in client settings. You can also schedule the operation in client settings.
After you enable software inventory and the clients run a software inventory cycle, the client sends the information to a management point in the client's site. The management point then forwards the inventory information to the Configuration Manager site server, which stores the information in the site database.
There are a few ways to view software inventory data:
Create queries that return devices with specified files.
Create query-based collections that include devices with specified files.
Run reports that provide details about files on devices.
Use Resource Explorer to examine detailed information about the files that were inventoried and collected from client devices.
When software inventory runs on a client device, the first report is a full inventory. Subsequent reports contain only delta inventory information. The site server processes delta information in the order received. If delta information for a client is missing, the site server rejects further delta information and directs the client to run a full inventory.
Configuration Manager can discover dual-boot computers but only returns inventory information from the operating system that's active at the time of inventory.
Mobile devices: See Software inventory for mobile devices enrolled with Microsoft Intune for information about collecting inventory for apps installed on mobile devices.
The requirement of the software inventory to function is similar to that of the hardware inventory. The process is also almost similar.
Client Side
The scheduler will send a message to the inventory agent to start the software inventory process.
Scheduler.log:
Sending message for schedule 'Machine/{00000000-0000-0000-0000-000000000002}' (Target: 'direct:InventoryAgent', Name: ')Scheduler4/10/2005 9:39:06 AM3904 (0x0F40)
The agent will determine the type of inventory it has to process (Full, Delta, Resync).The Scan Properties are stored in WMI at the RootCCMPolicyMachine namespace.
If you don’t see this, the issue can be the client unable to download the policies or the server has not been configured for Software Inventory.
Once the Software Inventory Client Agent has determined its Scan type, it must now determine precisely what it needs to inventory. This is accomplished by again pulling configuration data from WMI. Software Inventory Rule information (what an administrator has configured SCCM to inventory) is stored within the same namespace of WMI (RootCCMPolicyMachine) Each rule is stored in an instance of this class.
The inventory agent will scan the machine according to the software inventory rules and will send an XML file to the software inventory endpoint.
Once the properties of the scan have been determined, and the Advanced Client knows what type of scan (Full, Delta or Resync) to perform, as well as what it is scanning for (as defined in the Software Inventory Rules), it is time for it to perform the actual scan.
Inventoryagent.log
Inventory: *********************** Start of message processing. ***********************InventoryAgent4/22/2010 12:07:36 AM2924 (0x0B6C)
Inventory: Message type is InventoryActionInventoryAgent4/22/2010 12:07:36 AM2924 (0x0B6C)
Inventory: Temp directory = C:WINDOWSsystem32CCMInventoryTempInventoryAgent4/22/2010 12:07:36 AM2924 (0x0B6C)
Inventory: Clearing old collected files.InventoryAgent4/22/2010 12:07:36 AM2924 (0x0B6C)
Inventory: Opening store for action {00000000-0000-0000-0000-000000000002} ..InventoryAgent4/22/2010 12:07:37 AM2924 (0x0B6C)
Inventory: Action=Software ReportType=DeltaInventoryAgent4/22/2010 12:07:56 AM2924 (0x0B6C)
Inventory: Initialization completed in 19.849 secondsInventoryAgent4/22/2010 12:07:56 AM2924 (0x0B6C)
Collection: Input context, scan rate in milliseconds = 2InventoryAgent4/22/2010 12:09:57 AM3972 (0x0F84)
Collection: Input context, skip file name = skpswi.datInventoryAgent4/22/2010 12:09:57 AM3972 (0x0F84)
Collection: Namespace = .rootccminvagt; Query = SELECT Name, Path, LastWriteDate, Size, CompanyName, ProductName, ProductVersion, ProductLanguage, FileVersion, FileDescription FROM FileSystemFile WHERE Name = '*.exe' AND Path = '**' AND IsCompressed = FALSE AND IsEncrypted = FALSE; Timeout = 14400 secs.InventoryAgent4/22/2010 12:09:57 AM3972 (0x0F84)
……………………………
……………………………
………………………….
Inventory: Starting reporting task.InventoryAgent4/22/2010 12:16:19 AM2384 (0x0950)
Reporting: 0 report entries created.InventoryAgent4/22/2010 12:16:20 AM2384 (0x0950)
Inventory: Reporting Task completed in 0.931 secondsInventoryAgent4/22/2010 12:16:20 AM2384 (0x0950)
Inventory: Successfully sent report. Destination:mp:MP_SinvEndpoint, ID: {EBC09961-66DD-4C98-9656-FA370C3259BC}, Timeout: 80640 minutes MsgMode: Signed, Not EncryptedInventoryAgent4/22/2010 12:16:20 AM2384 (0x0950)
Inventory: Cycle completed in 541.088 secondsInventoryAgent4/22/2010 12:16:37 AM2384 (0x0950)
Inventory: Action completed.InventoryAgent4/22/2010 12:16:37 AM2384 (0x0950)
Inventory: ************************ End of message processing. ************************InventoryAgent4/22/2010 12:16:37 AM2384 (0x0950)
If there are some failures there then you can check to make sure that the consistency of the WMI and client of the system. Also we have information on
FileSystemFile.log
************* Start of File System Query. *************FileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Query = SELECT __class, __path, __relpath, name, path, lastwritedate, size, companyname, productname, productversion, productlanguage, fileversion, filedescriptionFROM FileSystemFile WHERE name = '*.exe' and path = '**' and iscompressed = false and isencrypted = false; Timeout = 14400 secs; ScanInterval = 2 msecs; SkipFile = skpswi.datFileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Query parsed successfully.. ready to scan for files.FileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Folders to skip: c:system volume information.FileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Scanning all local drives using input path *FileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Skipping A:;GetDriveType indicates it is not a fixed drive pathFileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Free Software Inventory Tool
Scanning C: ..FileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
Skipping directory c:system volume informationFileSystemFile4/22/2010 12:11:49 AM2384 (0x0950)
Skipping directory c:system volume informationFileSystemFile4/22/2010 12:11:49 AM2384 (0x0950)
Excluding C:WINDOWS$NtUninstallKB923845$ (compressed)FileSystemFile4/22/2010 12:11:59 AM2384 (0x0950)
Excluding C:WINDOWS$NtUninstallKB923845$ (compressed)FileSystemFile4/22/2010 12:11:59 AM2384 (0x0950)
Once the scan based on software inventory rules is completed, the results are stored within WMI on the Advanced Client
Server Side
The Management Point receives the message from the Advanced Client via a CCM_POST request. This allows the client to upload the message to the C:SMS_CCMServiceDataMessagingEndpointQueuesMP_SinvEndpoint directory on the Management Point.
Once there, CCMExec on the Management Point processes the message to recreate the XML file. This file is then stored in the <SEREVERDIR>[1]MPOutboxesSinv.box folder. Once the Management Point has properly received the message and converted it into an XML file for processing, the XML file is then parsed and used to create a .SIC or .SID file. If the inventory data in the XML file is a Delta, the XML file is used to generate a .SID file. On the other hand, if the XML file is complete inventory information, a .SIC file is created.
Mp_sinv.log:
Mp Message Handler: copying attachment to C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxSinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010 9:49:55 AM3548 (0x0DDC)
Free radio automation programs. Inv-Sinv Task: processing xml file 'C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxSinvAttachment8920FQG5.xml'MP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
Sinv Sax: loading C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxSinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
Full report from client SQL, action description = SoftwareMP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
Sinv Task: Translate report attachment to file 'C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.box9GY0JSG8.SIC' returned 0MP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
Mp Message Handler: copying attachment to C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxSinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010 7:37:16 PM5980 (0x175C)
Inv-Sinv Task: processing xml file 'C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxSinvAttachment4L7OW9WF.xml'MP_SinvEndpoint2/19/2010 7:37:16 PM272 (0x0110)
Sinv Sax: loading C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxSinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010 7:37:16 PM272 (0x0110)
Sinv Task: Translate report attachment to file 'C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxAN46DUDY.SIC' returned 0MP_SinvEndpoint1/31/2010 9:36:45 AM4812 (0x12CC)
The management point file dispatch manager copies the file to the site server. There the software inventory processor inserts the data into the database.
Sccm Software Inventory Not Reporting Software
Sinvproc.log:
Process Inventory Files..SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:13 AM5208 (0x1458)
Processing file: C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxW06N50OM.SICSMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:13 AM4668 (0x123C)
Processing Inventory for Machine: SCCMResId: 3 [OpCode=17 Sinv=1 FC=0 Resync=1] Generated: 01/31/2010 09:27:02SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668 (0x123C)
Transactions: Exist=0, Add=1196, Upd=0, Del=0, Total=1196SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668 (0x123C)
Report for Machine SCCM took 27 secs. for 2290 recs, FP=109, P=985, F=1196, FC=0SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
Successfully Processed file C:Program FilesMicrosoft Configuration Managerinboxesauthsinv.boxW06N50OM.SIC !!!SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
Sccm Installed Software Inventory
If the files are not getting processed then we need to make sure that the component SMS_SOFTWARE_INVENTORY_PROCESSOR. In certain circumstances a site reset can also help.
Links
http://technet.microsoft.com/en-us/library/bb693889.aspx : Overview of Inventory
http://technet.microsoft.com/en-us/library/bb632359.aspx:Troubleshooting Inventory
[1] <SERVERDIR> :Program FilesMicrosoft Configuration Manageror <Drive>SMS