Client Management Suite

Hi guys,

I noticed under the "inventory" folder on the client machine that some of the files in the "nsi" folder are months old eventhough i have weekly "full inventory policy" running on all machines.

I know i used to have a problem like this with inventory in ns6 and the solution was to use a clean before run switch to delete all the files in the inventory folder....

Is there something like this in ns 7.... if not has anyone found a work around.... added some screenshots.

Best practice is delta weekly, full monthly.  In large environments, you'll want a staggered schedule.  Are you running deltas or just fulls?  .baks are only created when a delta is run, to compare the delta vs. last full.  If you're only running fulls, the deltas don't need to create the .bak's and you're not going to see them with updated dates.

You can tune inventory performance by ...

* Running delta inventory:

Delta inventory reports only the data that has changed since the last full inventory scan.
Running delta inventory reduces the network load and increases the performance.
However, the data in the Configuration Management Database can get outdated and then a delta is not adequate anymore. For example, if the full inventory gets purged and deltas continue to come in, only the deltas remain in the database. That is why it is also recommended to run the full inventory on a recurring basis. 

* Using unique policies and schedules for different kinds of inventory.

For example, you can run different types of inventory on the following schedule:
-Full hardware inventory every four months, every first Monday
-Delta hardware inventory every two months, every second Monday
-Full software inventory every month, every first Tuesday
-Delta software inventory every week, every Wednesday
-File scan every six months, every second Friday

To learn more about inventory performance tuning, please follow the link: http://www.symantec.com/docs/HOWTO50114

I am looking at my inventory task schedules right now and I have some questions. Our inventories (deltas and fulls) are set to run over night using the monthly schedule for fulls and the weekly schedule for deltas. We have a mixed environment of desktops that are more than likely online when the schedule hit and laptops which are more than likely are not on line at the time the schedules hit. I am thinking that we are missing the laptops. Do the schedules pick up the next time that that the machine is on line or could we be missing them entirely if the machine is not online when the schedule hits? 

BTW Good point about staggering the schedules!  

They typically run when it comes online, unless you've checked 'at the exact scheduled time.'  But it depends on how you've got your schedule set up.