are there any news on this problem yet?
Unfortunately I found the described error also with us.
ES 10.6.1 AMCore 3614
Citrix XenApp 7.15
Certificates Options for Citix have been set
Ticket opened and MER file uploaded.
For now the only solution is set the exclusions (read and write) on Citrix processes.
This solution is not usable, for my company, and we are waiting an answer from the support.
My last activity was to send new logs: Amtrace, Mer and ProcessMonitor for the two situations one working with 10.5.4 and one not working with 10.6.1.
To make a comparison, i think.
For the moment I stay with viruscan 8.8 on the VDA Citrix.
Anybody an Update if the thematic is STILL Valid for Server 2016 Terminal Server and ENS 10.6.1 MAY 2019 UPDATE? We have two customer on which we are still unsure after a lot of testing if McAfee could be the source. Both have HIGH configured Exclusion and almost anything in LOW/HIGH Risk and active.
Customer has some Lag sometimes and we are unable to reproduce. It's not Certificate Revocation and anything else which we are aware off.
Found a good blog entry which describes the API Hooks Citrix does.
Greetings from Switzerland
Mcafee SR Support team ask me to try this (1 month Ago 😞
"As I already mentioned, it is necessary to check whether the problem persists after updating the AM core content after version 3682.0 or later."
I asked for a greater explanation, and if the problem was solved forever and this was the answer:
"AMCore Content has solved this problem by reducing the scanning of files written by Citrix. This will never be reversed. The only risk is when Citrix starts signing its software with a new certificate and the customer updates the Citrix software before McAfee sees the new certificate. To be sure, that McAfee is always ready for this, the customer can run GetClean on the Citrix binaries before updating Citrix."
For now with ENS 10.6.1 + November Update and Amcore update i dont have problem on Citrix Xenapp 7.15 CU2.