McAfee VSE 8.7i exceptions required for Citrix XenApp 6
Hello.
We are currenlty testing our new Citrix XenApp 6 farm.
On the applicaton farm servers we have McAfee VSE 8.7i P4 installed.
Managaed by Epolicy Orchestrator 4.5.
We are finding that the On Access Scanner component within VSE is scanning all processes on the lauch of logins and applications on the Citrix servers.
This is slowing down the logon and application lauch process for the user.
McAfee have no recommendations for exclusions of Citrix XenApp 6 and visa versa. No xeclsuions can be found on neither vendors knowledgebases.
Has anyone made any exclusions for XenApp 6? Do you recommend using another vendor for virus scanning.
Attached is the OAS log, within this log file you can see what OAS is scanning on the app server when applications are launched.
thanks. loggingOAS.txt
We are currenlty testing our new Citrix XenApp 6 farm.
On the applicaton farm servers we have McAfee VSE 8.7i P4 installed.
Managaed by Epolicy Orchestrator 4.5.
We are finding that the On Access Scanner component within VSE is scanning all processes on the lauch of logins and applications on the Citrix servers.
This is slowing down the logon and application lauch process for the user.
McAfee have no recommendations for exclusions of Citrix XenApp 6 and visa versa. No xeclsuions can be found on neither vendors knowledgebases.
Has anyone made any exclusions for XenApp 6? Do you recommend using another vendor for virus scanning.
Attached is the OAS log, within this log file you can see what OAS is scanning on the app server when applications are launched.
thanks. loggingOAS.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Fine... the Citix post has been removed?!
Yes, Citrix, McAfee and Symantec have all removed their posts "for further discussion".
Look at this MS doc
http://support.microsoft.com/kb/822158
Look at this MS doc
http://support.microsoft.com/kb/822158
ASKER
Might as well turn it off hey... :)
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
ASKER
Exclude all write's... ouch!