This was added to the incompatible product rules for V6.2 because there is a conflict between the Wave driver and the EEPC driver, which would cause sporadic BSODs even when the Wave product was not actually activated.
I hope this explains the reason behind this rule being introduced in 6.2.
In general, McAfee recommends that no third party encryption products are installed onto the endpoint when EEPC is installed as these conflictss are common due to the nature of the product requiring low-level access to devices on the endpoint. The incompatible product rules are specifically designed to prevent EEPC activating when there is the risk of system instability being introduced following activation due to the presence of other encryption products.
Do you know when EEGO will be updated to map to that? I have my helpdesk team rely on that to look for issues and now I need to re-train them to look through the eePE log files to see this error instead.
Also there needs to be more options around this, while i agree you need to protect the system from users where possible there is no fool proof way to check some software is activated like truecrypt which we use to encrypt harddrives that we send externally which causes issues with having to remove and add software.
1 of 1 people found this helpful
We are looking to update the compatible product rules in the V7 release of EEPC. However, I will also alert the product manager to this issue.
Thanks for this valuable feedback.