NOVELLUS

Hello there, we are using ESET Endpoint Security 6.11.202.0 on our Macs. The ESET VPN (Web and Email Protection) seems to block the macOS Updates. When the ESET VPN (localhost) connection is running, the update server will not be found. There is coming up a message "be sure, you have an internet connection to update your mac" When we stop the VPN connection and deselect the checkbox "start automatically" , the Apple update server will be found and the update can be installed. Is there any settings to configure to avoid this behavior?

Here are some further informations : In some rare cases, the "VPN connection ESET" is not running after the installation of ESET EES was finished. The needed system extensions are configured and active. With a uninstallation , reboot of the client, new installation (via Jamf) and reboot, we can solve this issue. We uninstall ESET with the ESET uninstall setup that is included in the ESET-ees_osx_en.dmg.

Hello Marcos, thank you for your reply. My fault, thank you for opening my eyes Meanwhile, I got a response from one of our affected users. Because of this feedback, I think, I can say, that ESET is not the cause for this behavior. The cause seems to be the update from MacOS 11 to MacOS 12. Something seems to went wrong while the update was running. Our employee told me, that he had to log in with his Apple-ID after every new boot of his Mac. While the login process, he was able to see, that the keychain was changed. It seems, that he got a new keychain at every logon with his Apple-ID. He did a reset of his Mac and a fresh installation with MacOS 12 and after that, he installed ESET EES (Version 6.11.1.0) via our software deployment Jamf. Since that time, his keychain stayed unchanged. In summary, you can say, the case is solved.

Hi there, we use ees 6.11.1.0 for mac, deployed with jamf pro®. All necessary configuration profiles are deployed to the clients, before ees is deployed. At this time, I get some messages from our employees, the their keychain was cleared, after the rebooted their clients. I found an article, that ees version 10.x did have this issue and it should be fixed in later versions. Does anyone know this problem, too ?

We have cisco anyconnect VPN installed on all clients. The issue is faced on some, but not on all clients. No matter, If the cisco VPN client is running or not. We removed ees from the affected systems and re installed ees, again. the issue still is present

Hi, we face the same issue. But not on all clients. ESET ees is deployed with Jamf Pro ® , too. The necessary configuration profiles are on the client, too. At this time, I cannot find out, where the root cause is. I would be glad to get some hints.