Should ENS Removal Tool be able to remove Threat Prevention?

[nashcoop]

Is this tool supposed to be able to remove Threat Prevention?  I have an issue where I tried removing Threat Prevention from a system using an EPO removal task, and the task somehow managed to get corrupted and never removed Threat Prevention, but now the properties for it are not being displayed in EPO either.  I have tried removal and redeployment tasks to fix the problem, but TP will not remove from the system or display TP properties in EPO.  So, I decided to try deploying the ENS Removal Tool to the system so I can remove Threat Prevention.  The deployment task is configured to "Install" with "McAfeeEndpointProductRemoval.exe --accepteula --ENS" in the command line (minus the parentheses).  I receive the error below that says it can't open the registry key Software\McAfeeEUA.  I'm not sure if that's supposed to be in the HKEY Current User or HKey Local Machine location, but I don't see a McAfeeEUA in either.  Any help with this would be appreciated.  

[jess_arman · Accepted solution]

@nashcoop  Your command line options should only be --accepteula --ENS 

You should not include mcafeeendpointproductremoval.exe as an argument. You can also see this in the log:

You can find the EPR user guide in REGISTERED - PD27734

Was my reply helpful?

If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?

[nashcoop]

Thanks, I figured that out shortly after adding my post.  I based my original command line content for the deployment task on what I read at the bottom of page 7 in the Endpoint Product Removal User Guide v19.3 which includes McAfeeEndpointProductRemoval.exe in the command line field.  Somebody ought to modify the guide and remove that .exe from the example since it's misleading and incorrect.

[jess_arman]

@nashcoop I'll take an action to provide feedback to the appropriate team to get that modified to be more clear at the next release. The reason that it is written as such is to give an example of what the inputs would be if you were executing it from local Windows Command Line, thus the column header. However, I understand where it can be extremely misleading when attempting to interpret that for use in ePO's command arguments section.

The differentiator is that ePO deployment automatically takes care of the .exe portion and you only need to implement the arguments without the need to call out the .exe.

Was my reply helpful?

If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?