Test on CPU spikes and LANDesk agent correlation

LANDesk posted an updated ticket this evening, regarding the CPU spikes on the View agent machines.

Unfortunately, so far, in their lab environment, they have pushed the agent to one of the machines, and there are no CPU spikes. This is, of course a preliminary finding. However, if this continues on this course, and they aren’t able to reproduce the problem, we may have to do some additional troubleshooting on our end to see if any of our software is causing this issue with the LANDesk agent.

Dave Couch was working on deploying a new template in the View environment that is bare-bones, to see how that would affect the LANDesk agent performance.

Here’s the update inserted into the LANDesk ticket by the engineer:

We set up the VMware View infrastructure, a connection server and another machine with the View agent. The view agent was connected to the connection server successfully.
Just for fun I pushed a LANDesk agent to the connection server and it seems to be working correctly. I see no tmc service CPU spikes after watching for a few minutes.
I am having trouble getting an agent to the view agent machine, so will ask Kevin to look at this in the morning.

Will keep you updated as soon as I hear more regarding this issue.

On a related note, I should be receiving the Antivirus patch from LANDesk sometime tomorrow morning. As soon as I apply it, I will be pushing out new agents to all our workstations.