tmuster2k 22 Posted August 29, 2018 Posted August 29, 2018 (edited) We have good amount of customers who buy ESET ENDPOINT SECURITY but some may not want to use the firewall so they can still take advantage of Bot Net, IDS, Web Control. So the firewall is disabled in ESMC company base policy. Confirmed that policy was created before EES was even pushed out to client and these are all fresh installs of latest EES 7. confirmed policy was applied correctly in global fashion. Confirmed that locally on endpoint as well. On EES 7 deployments now the windows defender action center is reporting "Actions needed in ESET Firewall- Open ESET Firewall" Opening just goes to GUI which reports "you are protected". Windows 7 machines with this same policy implementation do not report anything wrong with firewall. Confirmed that windows firewall is enabled on the Windows 10 1803 systems. I was also able to reproduce this on VM as well. Edited August 29, 2018 by tmuster2k
itman 1,799 Posted August 29, 2018 Posted August 29, 2018 As far as I am concerned, Windows is "dyslectic" when it comes to Win 10 1803. If you take the below WDSC screen shot at face value, you would assume both Eset and Win firewall are active. However if you use Control Panel, it clearly shows Eset firewall Is on and Windows Defender firewall is off in addition to noting that Eset is managing Win firewall settings:
Recommended Posts