I signed up for the trial of GoToManage and installed the crawler on Saturday morning.

By Saturday night one of my virtual servers was showing network errors and server access was slowed to a point where it was unusable.

I stopped the crawler service and after a while the server went back to normal. Without more tests I can’t prove the the crawler caused the problem, but it was the only new thing on the network. There have been no more errors since I stopped the crawler.

The server with the problem was a virtual Win2008 Core server running under Hyper-v. Another virtual server on the same hardware showed no problems, so I don’t believe it could have been hardware failure.

I’m puzzled as to why this one server showed problems while no others did. Is it possible that the crawler was trying to read data from the Hyper-v host and the virtual servers at the same time and so bogged down the NIC?

Is there a way to throttle that? Or was it just initial scanning that wouldn’t be so intensive going forward?

I like the idea of GoToManage, but I can’t use it if it’s going to kill a server.

Thanks for any thoughts.

—Matt

I had the same issue with multiple virtual servers on VMWare using Server 2003 and 2008. I found the wmiprsve.exe process was eating up 40-70% processor consistently over a few days. As soon as I stopped the crawler everything leveled out.

I contacted GoToManage support and the thought was that the schedule I was using on the crawler was too much for the servers to process. They suggested increasing time between plugin runs and to watch out for WMI_Full and Registry plugins as those poll the most info from WMI. Seems to have helped a bit for now but I’m keeping an eye on it. Hope this helps!

-Michael

Mine got better when I turned off the log file monitoring. Support told me that large Windows log files were taking too much time to read.