Don't forget about the right-click tools to they can force full inventory on a whole collection.
From: [email protected] [mailto:[email protected]] On Behalf Of John Aubrey Sent: Thursday, November 6, 2014 1:53 PM To: '[email protected]' Subject: RE: [mssms] Hardware Inventory Issues I haven't found a way to mass blow out a full inventory scan. Not sure of how that would affect the server, probably won't make it happy to say the least. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Thursday, November 6, 2014 4:20 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Hardware Inventory Issues I tried a full hardware inventory on a few machines and that seems to have worked. Thanks for the idea! I've been at this site for a few days and performed the upgrades to SP1 and R2, so maybe I am just not being patient enough to allow this to resolve on its own. . . :) Thanks, Jeff ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Hardware Inventory Issues Date: Thu, 6 Nov 2014 20:56:39 +0000 Did you try to do a full hardware inventory on a few machines? I have had some issues with bad mifs and running a full scan fixes it. I always let this kind of issue sit a couple days and it works itself out. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Thursday, November 6, 2014 3:52 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Hardware Inventory Issues I am having an issue with hardware inventory in ConfigMgr 2012 at a customer. Numerous machines are not getting good HW inventory and have MIF files that get placed in the BADMIFS directories. The site was recently upgraded to SP1 and from there to R2 CU3. The ivnentory issue existed prior to the SP1 to R2 upgrade. I see numerous dataldr warnings and errors: Inventory Data Loader failed to process the delta MIF file "XHLI3TFB3.MIF" and has moved it to "D:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\Outdated\dru1e5aq.MIF." Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax. Inventory Data Loader failed to process the file D:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\Process\HRHNGT8D.MIF because it is larger than the defined maximum allowable size of 5000000. I know I can increase the maximum allowed size of the MIFs, but I do not understand why they are so large. THe customer did have the AI class for InstalledExecutable enabled, but we turned that off since no one knew why it was enabled. Also, as a possible side effect of this, the data in the SMS_G_System_SYSTEM class does not seem to be correct. Is there a good way to determine the root cause of the various HW inventory failures? Thanks, Jeff
