there are none needed - EEPC6 presents itself in a different way than EEPC5, so there's no exclusions to be set.
Customer running SAV, no on access exclusions required for EEPC 6.1.3?
nope. none at all.
Hmmm, interesting. Here's the information I received from support, when I had an issue with unable to decrypt a drive. SR# 3-2006587215
Below is the exclusion in AV as promissed.
To avoid problems after installing Endpoint Encryption for PC (EEPC) 6.x on a client, McAfee recommends you create the following exceptions for every EEPC 6.0 client:
What to Exclude Comments
Endpoint Encryption File System Sometimes an anti-virus scanner might lock the Endpoint Encryption file system. This can cause data corruption because Endpoint Encryption tries to write data to the file system.
Endpoint Encryption for PC v6 Endpoint Encryption for PC 6.0 Product system files
Endpoint Encryption Agent Endpoint Encryption 6.0 Agent system files
PreBoot File System Mark these files as unmovable when using third-party defrag tools.
BootCode Mark these files as unmovable when using third-party defrag tools. See KB72568.
Recommended VirusScan Enterprise 8.x On-Access exclusions for supported EEPC 6.x clients Example of an ePO VirusScan Enterprise (VSE) exclusions policy:
What not to scan Exclude Subfolder Read/Write
c:\Program Files\McAfee\Endpoint Encryption for PC v6\ Yes read / write
c:\Program Files\McAfee\Endpoint Encryption Agent\ Yes read / write
\Device\SafeBootFSVolumes\Disk0\ Yes read / write
c:\SafeBoot.FS No read / write
c:\SafeBoot.RSV No read / write
So is it none or do I follow the above recommendations?
I think this is a depreciated article specific to EEPC6.0, though I guess it's fair practice to not scan the executables or root folder files.
It can't do any harm, and I don't see how exclusions could make it easier/harder to decrpt a drive, but it's best to follow support info where possible.
Just stumbled across this article as I was about to ask the same for 6.2. I think if no exclusions are required McAfee should look to note this in either a KB article or in the product documentation - would this be possible? For new projects where EEPC is being rolled out, change control procedures tend to like information like this, and also something they can cross reference :-)