By the way, the actual default value is 4c4b40 (hex) or 5000 bytes which is just under 5 MB. Change the HEX value to 3200000 which is 50 MB.Find Max MIF Size and double-click on it.Drill down to HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER.On the MEMCM site server, open regedit.exe.You simply edit one registry key and restart the smsexec service. Change the Maximum File Size of a MIFĬhanging the file size of a MIF is quick and easy to do.
If you use AI at all, you should see my post on How to Setup, Configure and Use SCCM’s Asset Intelligence for more details on how to avoid this issue and get the most out of MEMCM AI.
Only Citrix servers might be larger than 50 MB, but only if the SMS_SoftwareShortCut AI class is enabled. Increasing the MIF file size to 50 MB, however, stops the endless loop for what I estimate is 99% of all computers. Even if you set the value to be greater than 50 MB, the file will get rejected as being too large by your site server. There is only one major reason for this – MEMCM won’t process MIF files over 50 MB! So, that’s the absolute maximum size of a MIF file. Until, of course, the file size is increased. The endless loop continues to use the client, network and site server resources endlessly and needlessly. This triggers a re-sync message creating an endless loop.
Next, the MP then sends the MIF file to the site server.But, the MEMCM client doesn’t know that, so it sends the MIF file to the MP.
This full HW inv, of course, is bigger than the registry key value (in other words 5 MB).The computer sees that the re-sync message is set for the computer and the computer performs a full hardware inventory (HW inv).Then a hardware inventory re-sync message is sent to the computer.When a computer submits a MIF file that is too large, it gets sent to the \inboxes\auth\dataldr.box\BADMIFS\ExceedSizeLimit folder.The “2719 Loop” is a term that I use to describe what happens when a computer triggers the 2719 error message. It’s little things like this that we do to make sure that you get the most out of MEMCM. We never want to leave them guessing why their hardware inventory is not showing up. We do this because we want our clients to have a great experience.
The problem is so wide-spread that Enhansoft’s Enhansoft Reporting and Warranty Information Reporting software checks the file size setting prior to the installation of either solution. The hardware inventory MIF is now bigger than 5 MB, so the MIF size needs to be increased to the maximum 50 MB. When I see this error, I know exactly what happened. Then they wonder why they don’t see the new inventory class. Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size (the default is 5 MB), and wait for Inventory Data Loader to retry the operation.Īs I explained earlier, this MIF error is so common that most companies and MEMCM admins don’t even know they have a problem until a custom inventory class is added. Inventory Data Loader failed to process the file D:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\Process\HDD6EP0U.MIF because it is larger than the defined maximum allowable size of 5000000. In case you also need tips about troubleshooting inventory problems, please check out my other blog post, Troubleshoot ConfigMgr Hardware Inventory Issues. I needed to increase the MIF’s file size, so this blog post will show you how to change the maximum file size of a MIF.īy the way, the maximum file size is only 50 MB, but more on that later. At once, I knew what the problem was and how to fix it. I’m going to keep this blog post relatively short, so I’ll skip to the part where I finally located an error within the SMS Inventory Data Loader. While adding yet another custom hardware inventory class to MEMCM, I wondered why my inventory was not being updated in the MEMCM console. It also pops-up when you are reviewing hardware inventory details and see outdated results. This usually occurs when a custom hardware inventory class is added and you are left wondering why you don’t see this new inventory on some computers. Eventually, the problems associated with the maximum file size of a MIF come to light. Does your company rely on inventory data from Microsoft Endpoint Manager Configuration Manager (MEMCM)? There may be a problem with the hardware inventory and, unfortunately, many MEMCM admins aren’t aware of it.