Thanks, Sherry and Eswar! Very helpful ideas. Jeff From: [email protected] To: [email protected] Subject: RE: [mssms] Hardware Inventory Issues Date: Fri, 7 Nov 2014 10:39:05 +0800
use the SMS collection commander(Old Version) by roger to initiate full hardware inventory on set of clients at one go. This tool has been very helpful to perform the client actions.this still works with cm12 clients. http://smscollctr.sourceforge.net/ Collection for pulling computers not reporting hinv for X days: select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System where ResourceId in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) > 30)via http://eskonr.com/2009/08/sccm-collection-report-for-hardware-inventory-not-reported-for-x-days/ RegardsEswar Koneti www.eskonr.com From: [email protected] To: [email protected] Subject: Re: [mssms] Hardware Inventory Issues Date: Thu, 6 Nov 2014 23:17:12 +0000 here's one way.http://myitforum.com/cs2/blogs/rzander/archive/2008/08/11/sms-sccm-commandline.aspx grab the line for full hinv at next scheduled time. using whatever you want, a task sequence with one cmd line, or package/program, send that out to collections, probably collection(s) where lastworkstationstatus.lastscan is older than some date. you could then (if you want) follow that up with a custom client agent setting of hinv every 4 hours. if you have the collections do a update every 3 hours… as those boxes report successfully, they'll fall out of the collection, and no longer deserve either the advert nor the hinv every 4 hours. I see this cleaned up overnight if those boxes are online and your servers can handle the full hinv coming in. if you're concerned about that, split it up into diff collections til it cleans up most of the way. Sherry Kissinger From: John Aubrey Sent: Thursday, November 6, 2014 3:53 PM To: [email protected] 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]] On Behalf Of Jeff Poling Sent: Thursday, November 6, 2014 4:20 PM To: [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] To: [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]] On Behalf Of Jeff Poling Sent: Thursday, November 6, 2014 3:52 PM To: [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
