PENDING Software scan date not showing in sccm console.

[Rohit]

Hello Prajwal !


I have installed SCCM 1902. In which i am able to fetch installed software report. ( Its not Blank ! ) But when i see the console to check last software scan date, it shows blank.

Also i have increased MIF size from below.

HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size

But it didnt worked for me.

Below is the log file from client machine "inventoryagent.log"

Inventory: *********************** Start of message processing. *********************** InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Message type is InventoryAction InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Temp directory = C:\Windows\CCM\Inventory\Temp\ InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Clearing old collected files. InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Opening store for action {00000000-0000-0000-0000-000000000002} ... InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
InventoryVersionNumber for '{00000000-0000-0000-0000-000000000002}' not found. InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
CInvState::VerifyInventoryVersionNumber: Couldn't get version number for '{00000000-0000-0000-0000-000000000002}': 80070490 InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Delta report without a previous Full report; will do a Full report. InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Action=Software, ReportType=Full, MajorVersion=1, MinorVersion=0 InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Initialization completed in 0.125 seconds InventoryAgent 7/26/2019 4:02:03 PM 480 (0x01E0)
Inventory: Collection Task completed in 1.031 seconds InventoryAgent 7/26/2019 4:02:04 PM 480 (0x01E0)
Inventory: Temp report = C:\Windows\CCM\Inventory\Temp\06ca4b19-f42f-4ba9-a4b2-680324390df6.xml InventoryAgent 7/26/2019 4:02:04 PM 480 (0x01E0)
Collection: 0/0 inventory data items successfully inventoried. InventoryAgent 7/26/2019 4:02:04 PM 480 (0x01E0)
Inventory: Starting reporting task. InventoryAgent 7/26/2019 4:02:04 PM 480 (0x01E0)
Reporting: 0 report entries created. InventoryAgent 7/26/2019 4:02:05 PM 480 (0x01E0)
Inventory: Reporting Task completed in 0.125 seconds InventoryAgent 7/26/2019 4:02:05 PM 480 (0x01E0)
Inventory: No data items to collect and report is empty. No report will be sent. InventoryAgent 7/26/2019 4:02:05 PM 480 (0x01E0)
Inventory: Cycle completed in 1.344 seconds InventoryAgent 7/26/2019 4:02:05 PM 480 (0x01E0)
Inventory: Action completed. InventoryAgent 7/26/2019 4:02:05 PM 480 (0x01E0)
Inventory: ************************ End of message processing. ************************ InventoryAgent 7/26/2019 4:02:05 PM 480 (0x01E0)




Please Help !

 

[Sam Banford]

0/0 inventory data items successfully inventoried.

Have you configured the software inventory? Add *.exe to the "Inventory these file types".

 

[Rohit]

Hello Sam !

I have configured and now i am getting latest software scan date in console. Thanks !

 

[Sam Banford]

Nice, glad to have helped.

 

[Garth]

you should read these blogs as to why SW inventory is bad. https://www.enhansoft.com/?s=software+inventory

 

[Sam Banford]

To blanket state that SI is bad is misleading. SI like any other tool has uses and misuses. He was asking for help in getting it up and running and that's what I gave him. He'll see the results and hopefully tune it to provide more meaningful results at a reasonable interval during non-work hours.

 

[Garth]

You are welcome to promote this SW inv. But all of my statements are based on facts, hence why I posted links to various blogs the explain in detail as to why it is bad.



Here is a summary:

• SW Inventory is slow to the point it can take days to complete one SW inv cycle.
• When SW inventory is running, it blocks all other inventory processes.
• SW Inv. will not scan all files on a computer.
• SW Inv., once it hit the 4-hour run-time limit, abandons the SW scan and does NOT send the results to SCCM.
• Because of the above you can't trust the results of SW inv.
• The next SW scan will NOT continue on where the last SW scan finished.
• SW Inv should NOT be called SW Inv, instead, it should be call File Inventory.
• SCCM CIs are faster (and more reliable) than SW Inv for things like detecting PSSexec.
• SW Inv can be IO intensive

Here is one example of how to use a CI to detect files on a computer.

https://www.enhansoft.com/the-four-files-you-need-to-remove-from-configuration-managers-environment/



It is NOT recommended to set a defined schedule for any of the inventory tasks as this can put a lot of strain on the SCCM server, SANs, and alike. A defined schedule is ignored when the computer is turned off and will run first thing in the morning when computers are turned on. A simple schedule is what is recommended, although this will also mean that it will be run first thing in the morning too for those computers that are off. But a simple schedule does lend to more random scheduling for those computer that are online.

 

[Rohit]

You are welcome to promote this SW inv. But all of my statements are based on facts, hence why I posted links to various blogs the explain in detail as to why it is bad.



Here is a summary:

• SW Inventory is slow to the point it can take days to complete one SW inv cycle.
• When SW inventory is running, it blocks all other inventory processes.
• SW Inv. will not scan all files on a computer.
• SW Inv., once it hit the 4-hour run-time limit, abandons the SW scan and does NOT send the results to SCCM.
• Because of the above you can't trust the results of SW inv.
• The next SW scan will NOT continue on where the last SW scan finished.
• SW Inv should NOT be called SW Inv, instead, it should be call File Inventory.
• SCCM CIs are faster (and more reliable) than SW Inv for things like detecting PSSexec.
• SW Inv can be IO intensive

Here is one example of how to use a CI to detect files on a computer.

https://www.enhansoft.com/the-four-files-you-need-to-remove-from-configuration-managers-environment/



It is NOT recommended to set a defined schedule for any of the inventory tasks as this can put a lot of strain on the SCCM server, SANs, and alike. A defined schedule is ignored when the computer is turned off and will run first thing in the morning when computers are turned on. A simple schedule is what is recommended, although this will also mean that it will be run first thing in the morning too for those computers that are off. But a simple schedule does lend to more random scheduling for those computer that are online.

Nice info. Garth. Issue has been resolved now the only issue was with the date only which was not showing in the console. Please close this thread as it's resolved now.