Full vs. Delta Inventory

Full vs. Delta Inventory (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager

Message

rjarrett -> Full vs. Delta Inventory (6/9/2008 10:34:02 AM)
We are still using SMS 2003. The advanced client submits its H\W inventory as a "delta" inventory from the previously submitted inventory. We have a script, shown below, to force a full inventory. Is there a way (e.g. MOF edit) to force full inventories everytime? Dim strComputer,strNameSpace,strClass Dim ObjWMIService strComputer = "." strNameSpace = "root\ccm\invagt" strClass = "C00000000_0000_0000_0000_000000000001" Set ObjWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ strComputer & "\" & strNameSpace) 'on Error Resume Next objWMIService.delete"C00000000_0000_0000_0000_000000000001" 'On Error Goto 0

jnelson993 -> RE: Full vs. Delta Inventory (6/9/2008 11:10:31 AM)
Eeew! Why? Instead of just dealing with normal delta inventory, it'd have to churn through, what...10MB worth of mostly redundant inventory data for every machine every time?

skissinger -> RE: Full vs. Delta Inventory (6/9/2008 12:32:51 PM)
What problem are you attempting to resolve with a full HW inventory?

rjarrett -> RE: Full vs. Delta Inventory (6/13/2008 8:55:19 AM)
We have a "Backup and Restore" utility that captures a Ghost image of the machine and stores it on the network. When the backup is restored, it does not send an inventory because from its perspective nothing has changed since its last inventory. We traditionally use this feature when we are doing software deployment testing. If you install anything onto the computer in the interim between its last inventory and the Ghost image, it is "orphaned" in the central database. For example, assume my machine inventories at 9:00 AM and I commence the backup at 9:30 AM. Later, I deploy my test application at 10:00 AM. Once the inventory for that new software goes forward, it is in the central database. Then "restore" the machine. At this point, it is sitting there thinking it has the exact same configuration as it did at the 9:00 AM inventory. So, when the next inventory rolls around, it computes no change. As a result, it does not update the inventory. As a result, the test application is still in the server inventory. Thus, the computer is set back in time to a point where it is happy with itself, despite the intervening test installation.

gjones -> RE: Full vs. Delta Inventory (6/13/2008 9:22:58 AM)
This will fix itself after 2-3 inventory cycles. The next time the inventory is sent up the SMS site server will see that the data is out of sequence and request a full inventory from the client again.

wbracken -> RE: Full vs. Delta Inventory (6/13/2008 10:08:40 PM)
Not sure how to enable it to always do Full (thinking that may produce undesirable effcts if you did anyway) however you could always trigger a full inventory via a script I would imagine. Maybe have it as a startup script? Just trying throw stuff out there. ;)

ldegroot -> RE: Full vs. Delta Inventory (10/12/2008 8:55:57 PM)
Sorry to hijack this thread, but can someone tell me if every file scanned in a delta SW inventory? Also, we are wanting to do a daily inventory just on what software has been added\removed. Is it possible to run a daily scan to just check for these changes, and say run a weekly for any other delta changes? Cheers

skissinger -> RE: Full vs. Delta Inventory (10/13/2008 10:12:50 AM)
If you look at the client's inventoryagent.log file during a software inventory action; you'll see that it scans through WMI, \\.\root\ccm\invagt, FileSystemFile. Then it'll attempt to send up a delta if applicable. Personally, because of the length of time a SW Inventory takes on the client side (several minutes) vs. a HW Inventory (seconds; the longest I saw on a really slow box was 96sec), and knowing that HW Inventory is what reports the contents of Add/Remove Programs (Software inventory reports on files, like .exe files); what I recommend is to forget about Software Inventory & using filenames to base your collection queries or reports against. Can you base your reports or collection queries on the contents of Add/Remove Programs? If so, do a daily HW Inventory, and SW Inventory less frequently; like every 4 days, or weekly. There were very, very few times that I had to rely on a filename vs. something I could get out of ARP or elsewhere in the registry or WMI. If I couldn't use ARP data, I was always able to find something in the registry or WMI and extended the mof instead. It was all about speed & reliability at the client. Alternatively, you are on Configuration Manager. Could you leverage DCM to check for whatever it is you need to look for?

ldegroot -> RE: Full vs. Delta Inventory (10/13/2008 5:17:04 PM)
Sherry Yet again your brilliance shines through!!! Thanks for the explanation, helps me heaps in my quest! We are looking at DCM and I think I will be able to get a lot of good use out of that too.... Cheers Lyle

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.234375