A few weeks ago I installed ENS on a terminal server farm. I started small to monitor performance and worked my way up throughout a couple weeks. After getting through the majority of terminal servers on the farm, the entire environment went down with McAfee Scanner Service consuming over 60% cpu, maxing out resources and freezing the environment for all users...
We are an affiliate (not fully migrated) and our parent company has Tanium installed on all of our endpoints and servers for real time scanning of processes. Tanium has been excluded in our policies to avoid interference but I'm not sure if this has caused any conflict that would have impacted our TS farm the way it did. We have both Tanium and McAfee ENS running concurrently on over 800 systems with no issues.
We got the environment back to a stable state and are a bit hesitant to move forward with the ENS deployment. Policies were re-evaluated for servers and optimized as much as possible to favor performance while providing security.
Does anyone have any tips on reducing the cpu consumption of McAfee ENS services in a terminal server farm? Maybe there is something that was overlooked and would cause the cpu to spike so high.
We would recommend using profile based scanning for the ENS, this helps you to avoid scanning of known processes and the subsequent actions that it performs. To achieve this you will have to add the tanium related processes as low risk process and disable scan on read and write.
Additionally, we would recommend excluding the file/folder exclusions under the default and the high risk profile and disable scanning on them as well.
Additional information related to the profile based scanning is available under the article below:
Re: Installed ENS on Terminal Servers and they broke.
You don't install onto a full farm without policy tuning and exclusion tuning. Deploy it to one citrix server and then slowy adapt. You will need to monitor processes with systernals (Procmon etc.) tools and some low level knowledge to get this fully and performant running.
It's worth it since Terminal Server are still Extreme high risk in ransomware times. When one user get's infected and in some way the malware could infect all users in the TS bad luck.
We runs ENS since 10.5 to 10.7 with many customers on Clients, VDI, Server and Citrix Server.
It needed a lot of work and is not something you do on a weekend.
But it's worth it. No ransomware at any customer from us over 10 years.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.