In general use I haven't seen much of an impact. It looks bad during agent install when lots of processes kick off, but they all unload only to be called when needed.
Network traffic is low to non-existent as it is local monitoring and alerts when thresholds are breached (which you need to set).
In most cases I've seen people want to use this with the Console Inspector option for stopping/restarting processes and services like you describe. Not heard many bad things from the people I've worked with on this.
As with all things, if you want to be certain, try it out on a smaple group of systems first to make certain there is nothing about your configuration that might clash.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based
Update - New v2.3 Now with Automated Subnet Rep Selection and Optional Maintenance of LANDESK Reps
The One-Stop Shop for LANDesk Enhancements
Thank you for the reply, Mark. After doing some testing and benchmarking on a few test machines, I do not see any significant impact from using the real-time inventory features, and it does in fact only seem to spike the resource usage when you request info from the machine. The rest of the time the processes idle. Looks like we will be implementing this feature. Thanks again for the information!