High memory utilization on agent after DI scan
Is it typical for an agent to have the memory pegged after a DI scan has been completed? I have a Windows 2008 R2 Fileserver that has the memory consistently high at 96% (9.6GB of 10GB utilized) during and after a DI scan. Before the scan, there was 6.6GB of 10GB memory available. It would seem that the memory doesn't free up and a reboot of the agent is the fix. DI server/agent -3.0.1.2511(30RU1)Solved1.5KViews0likes2Comments