We get about 1000 deltamismatch BADMIFs generated each day.

Here is the case of sccm client Inventoryagent.log says successfully sent but the ccmessaging.log shows the upload failed.
Why can’t the client inventory agent act on the status back from ccmmessaginglog and if the upload of the inventory fails, don’t increment the delta number.
This would greatly reduce the number of deltamismatch files generated each day and improvement keeping the inventory up to date without having to force a full inventory sync for this case.

Here are the details:

Dataldr.log for computer: CHOSIJ1-L2

Thread: 6108 will use GUID GUID:c28fa179-d722-4692-be69-a71f5a81e75c SMSINVENTORYDATALOADER 6/23/2020 4:06:34 PM 6108 (0x17DC)
Processing Inventory for Machine: CHOSIJ1-L2 Version 2.7 Generated: 06/23/2020 14:04:44 SMSINVENTORYDATALOADER 6/23/2020 4:06:34 PM 6108 (0x17DC)
Begin transaction: Machine=CHOSIJ1-L2(GUID:c28fa179-d722-4692-be69-a71f5a81e75c) SMSINVENTORYDATALOADER 6/23/2020 4:06:34 PM 6108 (0x17DC)
WARNING - Attempting to resync due to missed delta reports (sp return code = 7) SMSINVENTORYDATALOADER 6/23/2020 4:06:34 PM 6108 (0x17DC)
Rollback transaction: Machine=CHOSIJ1-L2(GUID:c28fa179-d722-4692-be69-a71f5a81e75c) SMSINVENTORYDATALOADER 6/23/2020 4:06:34 PM 6108 (0x17DC)
SQL MESSAGE: dbo.spAddInventoryLog - Inventory Log for machine:CHOSIJ1-L2,Server:2.5,Client:2.7,Message:Missing Delta. Resync,Detail: SMSINVENTORYDATALOADER 6/23/2020 4:06:34 PM 6108 (0x17DC)

Shows processing 2.7 but database is 2.5 – force a re-sync

Client tried to send delta 2.6 at 6/22/ 10:55am – but the network was not working client probably dropped vpn or connected vpn

Client Inventory Agent.log at 6/22 @ 7:41am starts processing delta 2.6
Inventory: Action=Hardware, ReportType=Delta, MajorVersion=2, MinorVersion=6
Reports successfully sent at 10:55am
Inventory: Successfully sent report. Destination:mp:MP_HinvEndpoint, ID: {1090DA21-86C6-44C8-9C38-260F7824060E}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted

CCMMessaging.log @ 10:55AM shows it failed:
[CCMHTTP] ERROR: URL=https://MSPM1BADP20.ent.core.medtronic.com/ccmsystem/request, Port=443, Options=448, Code=12007, Text=ERRORWINHTTPNAMENOT_RESOLVED

In summary if the InventoryAgent.log could detect that the Inventory was not successfully sent then don’t increment delta to 2.6 leave at 2.5

Thanks

Hello, When we try to configure the PullDP to use CDP as Source, the pullDP only uses the proxy configured on Winhttp service, neither the proxy configured in site system property or the Configmgr control panel applet are used. Seems at moment the admin has to configure Winhttp proxy manually to allow the pullDP to get the content from CDP, whereas this should be handled by sccm, whenever the Pulldp is being enabled in the console, the proxy configured on the Site system props has to be applied in the winhttp service on the system context as well.

Got to know that this piece is missing as proxy configured on site system applicable only for Site system (server config) and pullDP is not a server component as it uses CCM_framework of the client, also on the other-hand the proxy on the configmgr client applet also not get applied as PullDP runs independent of the client though it shares the same framework.

Thanks in advance.

Just upgraded from 1910 to 2002 and the upgrade failed and had to open a support case. Bottom line our SQL DBA made unauthorized changes to SCCM database and enabled PAGE compression on 370 tables in the SCCM database.

Please add to the pre-req check the running of this SQL query if any tables are set to PAGE data compression fail the pre-req.

SQL to Check: SELECT t.name AS tablename,

   i.name AS indexname,

   p.data_compression_desc

FROM sys.tables AS t
INNER JOIN sys.indexes AS i

 ON t.object_id = i.object_id

INNER JOIN sys.partitions AS p

 ON i.object_id = p.object_id

    AND i.index_id = p.index_id

Where p.datacompressiondesc = 'PAGE'

Report recommendation to turn off PAGE compression using this SQL:
EXEC spMSforeachtable 'SET QUOTEDIDENTIFIER on;alter TABLE ? REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE)'

That will save you from failed ConfigMgr Upgrade nightmare.

Hi Team,

Based on the below article, there seems to be no control on distribution point rate limit in SCCM Client or Server DP.

https://www.systemcenterdudes.com/dp-network-bandwith-limitation/

For an instance, If the company wants to throttle the package transfer from SCCM primary site to remote ditrbution point at 10% available bandwidth between the specified duration. If the WAN bandwidth for the location is 10 Mbps then SCCM rate limit feature use the % you specify as to when it can use 100% of the available bandwith. In my example, I’m telling SCCM to use 100% of the available bandwith 10% of the time (0 to 0). It doesn’t mean to use 1 Mbps.

Unlike other products like Altiris or Symantec ITMS has such control over the package transfer with throttling limit. Hoping to see the same funtionality implemented in Microsoft SCCM CB.