Inventory Workflow

Question

Hello,

I have several Clients which are doing their inventory:

InventoryAgent.log

Inventory: Successfully sent report. Destination:mp:MP_HinvEndpoint, ID: {06AF8B60-3ABE-4777-A7C4-057692D1E58D}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted

CcmMessaging.log

MESSAGE PAYLOAD TRANSFER COMPLETE: Status: SUCCESS Direction: Upload Msg ID: {06AF8B60-3ABE-4777-A7C4-057692D1E58D} BITS Job ID: {4BB3333D-FDBA-4021-AEFC-F11384FFC0F2} Start time: 02/22/2023 14:59 (GMT) Completion time: 02/22/2023 15:00 (GMT) Elapsed time: 35 seconds

What is the next log to check on the Management Point? MP_Ddr.log? it does not seem to have a trace of these clients?

Thanks,

Dom

Answer 1

First off, BITENTSQL1 has NOT returned a full HW inventory. You can see that from resource Exploerer by the face that version is 37.36, it need to be 38.0.

Secondly, AV def come from SU and not HW inv., On top of that the console can take 24 hours to update. You should never relay on the console to be update. Always use reports.

Answer 2

Hello,

I found an entry in

MP_HInv.log

Hinv Retry: ******************* Start of Task ********************* 2/22/2023 3:23:44 AM 1028 (0x0404)

Hinv Sax: loading E:\SCCM\inboxes\auth\dataldr.box\HinvAttachmentDXNTI8ZW.xml 2/22/2023 3:23:44 AM 1028 (0x0404)

Delta report from client VITMEDINT01, action description = Hardware 2/22/2023 3:23:44 AM 1028 (0x0404)

Hinv Task: Translate report attachment to file "E:\SCCM\inboxes\auth\dataldr.box\H5B4PYW8.MIF" returned 0 2/22/2023 3:23:44 AM 1028 (0x0404)

Hinv Retry: ******************* End of Task ********************* 2/22/2023 3:23:44 AM 1028 (0x0404)

Thanks,
Dom

Answer 3

Use this article to follow the Inventory from your device to the database.

https://www.recastsoftware.com/resources/updated-troubleshoot-configmgr-hardware-inventory-issues/

Answer 4

Hello,

dataldr.log

Thread: 16460 will use GUID GUID:334FB7D0-D264-4DCE-806C-D7A924F38AB4 2/22/2023 7:01:08 AM 16460 (0x404C)

Processing Inventory for Machine: BITENTSQL1 Version 37.36 Generated: 02/22/2023 06:59:31 2/22/2023 7:01:08 AM 16460 (0x404C)

Begin transaction: Machine=BITENTSQL1(GUID:334FB7D0-D264-4DCE-806C-D7A924F38AB4) 2/22/2023 7:01:08 AM 16460 (0x404C)

Commit transaction: Machine=BITENTSQL1(GUID:334FB7D0-D264-4DCE-806C-D7A924F38AB4) 2/22/2023 7:01:08 AM 16460 (0x404C)

Cannot find MIF with next version 2/22/2023 7:01:08 AM 16460 (0x404C)

Done: Machine=BITENTSQL1(GUID:334FB7D0-D264-4DCE-806C-D7A924F38AB4) code=0 (183 stored procs in XHSJ6J3I8.MIF) 2/22/2023 7:01:08 AM 16460 (0x404C)

==============================================================================

Is the message "Cannot find MIF with next version" the issue?

Thanks,

Dom

Answer 5

Yes that is fine. EXACLTY what problem are you trying to solve?