Just wondering since we see this problem often in our environment. The Nimsoft IM tool tends to get very sluggish after running for either a few days or after a weeks time. Usually there are not clear indicators as to what is causing the tool to behaving this way, (CPU usage on all machines is normal, memory is normal) but the IM tool just doesn't respond and our NOC reports the same behavior as well. I tend to cycle the Nimbus Robot Watcher Service once this behavior presents itself. Curious, is this a common practice that other do on a weekly schedule or should the root of the problem be found out?
Just curious.. Thanks,