I keep searching the discussion threads, and helpful links here on the LANDesk portal, but I don't seem to find anything related to my question/issues I'm seeing in my LANDesk environement. Go ahead...try it. Go to the search option. Type in "multiple vulscan.exe processes running" You'll find little to no explaination. Why is that? I know I'm not the only person who has seen this.
Why are there 2 or sometimes 3 or more VULSCAN.EXE processes that run?
But, more importantly, I've seen (and this is very random machine behavior) some machines that when the LANDesk vulscan kicks off, their machines come to a crawl and are sometimes unusable for up to an hour. Their CPU isn't 100%, and it's running about 10-30% (pretty normal CPU behavior), but their HD LED light is SOLID green and makes the machine utterly useless.
Now I've done some research here on the discussion forums, and I see all these "try this" and "try that" suggestions, but I don't think any of those suggestions are valid, and seem to be more guesswork/trial and error.
I don't have that kind of time to spend on this, unfortunately.
I've resorted to creating a different agent, scanning less frequently (once per week), rather than once per day. And setting some of the settings to Zero, etc (again from suggestions in the forums) to possibly create an agent, that appears to be less intrusive for a real business environment.
I'm not expecting that this will be answered by anyone, as it would require alot of troubleshooting or checking error logs, or patching the LANDesk core to some buggy new version that I'm leary of doing in our invironement.
But, I wish that someone really knew why these machines exhibit this problem. Initially, when the agents were deployed with the once per day, random up to an hour and mini-scan thrown in there agent, there didn't seem to be ANY machines with this problem. Now that a year has passed, I'm seeing more and more complainers of their machines being "hogged" by some LANDesk process.
What's changed? Nothing.
We windows technical support people know that over time and usage, and Microshaft patches later, that machines will degradate just by everyday users machine habbits/usage. But, this LANDesk product isn't helping my life much; creating more work for myself.
Has anyone out there noticed in your own environments where when you first deployed LANDesk, there weren't that many issues (aside from rollout issues) in the beggining and now that time has passed, agents/clients/machines seem to be showing signs of problems? And for no apparent reason at all.....
I'm hoping that by creating this new agent, testing it, and deploying out to the masses, that this will help my support work life, rather than complicate things.
Don't get me wrong, I like the product and the tool alot....but, someone needs to really address the product flaws.
Thoughts on this?