cancel
Showing results for 
Search instead for 
Did you mean: 

Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

tnguyendoit
Occasional Contributor

Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

Pulse Connect Secure 8.3R3, 8.3R6, etc.

 

Many of our users run the McAfee consumer endpoint protection product on their called "McAfee Total Protection" version 16.x various releases (R13, R15, etc.)

 

We were using ESAP 3.2.8 SDK v4.  Many of our users complained that Host Checker could not detect their McAfee Total Protection 16.x product (with the latest updates dated 10/11/2018) and Host Checker kept throwing error about their Windows 10 Windows Defender real-time protection isn't enabled. Error message is "Windows Defender 4.13.xxxxx.x" does not comply with policy. Compliance requires real time protection enable." (naturally it's disabled because McAfee is installed).  As a result, they're unable to establish  VPN connection.

 

Pulse Secure stated in the Release Notes for ESAP 3.3.1 that 3.3.1 supports McAfee Total Protection 16.x:

 

https://www.pulsesecure.net/download/techpubs/current/1404/pulse-connect-secure/esap/3.3.x/ps-esap-3...

 

---> Even after we uploaded and activated ESAP 3.3.1 and the Host Checker on the users' home machines were upgraded, Host Checker with ESAP 3.3.1 OPSWAT SDK v4 still couldn't detect McAfee Total Protection 16.x at all.

 

Anyone else encountering the issue?  This is most frustrating, as it resembled similar issue with Norton Security Suite 22.12.0.104 back in mid-March 2018.

7 REPLIES 7
mustangs550
Pulser

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

Hello @tnguyendoit

 

If you have set Host Checker for any supported AV, if McAfee is not being detected, it will detect other AV's to run HC. But in your scenario, Windows Defender has been disabled that is why you are getting the error message is "Windows Defender 4.13.xxxxx.x" does not comply with policy. Compliance requires real time protection enable.

 

I recommend to open a support ticket to determine McAfee Total Protection 16.x is not being detected. 

 

wecc04
New Member

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

I'm running McAfee Total Protection 16.0 R17 and Host Checker is still failing and asking for Microsoft Defender real time protection when McAfee is active.  Is there a fix as yet.  Have not been able to post on Technical forums.

ARMARSHALL_RIDOT_PULSE
New Contributor

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

This is still happening to me.  McAfee takes over for Windows Defender when it is the virus protection.  In effect, Windows Defender is disabled.  I have had this issue over and over with Pulse.   Cannot even connect to my major client's network, and I refuse to disable my AV to use PULSE.

The client cannot update the Pulse apparently.

 

 

McAfee Total Protection 16.0 R29 

Windows 10, patched to latest

Windows Defender (disabled by McAfee) 4.18.2011.6

 

What is going on here?

ARMARSHALL_RIDOT_PULSE
New Contributor

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

Me too, me too, me too.

ARMARSHALL_RIDOT_PULSE
New Contributor

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

Support ticket is not an option.  I am the state'sVPN client, not an IT support person.  This is chronic and has continued for years.  Please.

ARMARSHALL_RIDOT_PULSE
New Contributor

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

Yes, exactly this issue.

zanyterp
Moderator

Re: Even latest ESAP 3.3.1 cannot detect McAfee Total Protection 16.x

thank you for letting us know it is an issue (again).
do you know if McAfee is an allowed application by the State?