Additional investigation has shown that one of our custom probes is causing the most memory usage in WMI. I think the overall issue still affects ntevl, but the issue is much worse for the custom probe. We have found some documentation online about memory leaks in WMI on Windows 2008 R2, but there are few solutions. We also discovered a promising hotfix, but that did not change the behavior on our test server.
Does anyone else have experience with WMI memory leaks on Windows 2008 R2?
Thanks,
Keith