Installation order of End User Computing Agents for User Environment Manager (UEM) and App Volumes (. Note we had this done already but started clean none the less Remove VMware agents, Remove Mcaffee Agent and Virus scan. That being said we think we found a work around for now which has helped alleviate the problem. Long term I'd love to move away from McAfee all together as I have not been a fan. This is the eventual way we are moving but waiting on an upgrade of the E-policy server before we start testing. The other is similar to Deep Security as a host based solution. One uses an offloaded scanning server to do all the work but introduces horrible latency when users attempt to open files. MCafee agent is 5.x Virusscan is 8.8 Patch 9įor reference I have one parent template with Mcafee Agent and Antivirus installed and a second without any mcafee products on its clear some Mcafee policy appears to be the cause. We found removing vmware tools for a clean install to be a problem as it drops into a blue screen crash cycle requiring us to revert to snap shot. We have tried rebuilding our VMs from scratch after our security team asked us to run some additional debuging and found vmtools was doing alot WMI chatter. Then we log out of the VM and cpu jumps right back up to the 2.2+Ghz consumed range. If I lock the workstation and continue to monitor the cpu utilization doesn't change. As soon as I use console to log into one of these systems the cpu drops to standard usage about 300-500Mhz and remains this way while logged in. Recently we've been seeing high idle vm cpu usage and after a bit of troubleshooting we ran pslist -s against idle vms and found mcShield taking 33%+ cpu on the systems consistently, vcenter shows the vm consuming at minimum 2.2Ghz cpu while idle. So I have 2 data centers One Primary and a secondary which has a few users on it.
0 kommentar(er)
