IfI try to login to ESET HOME (either by clicking the "open ESET HOME"-button in the application, as well as when going via "
eset.com/be-nl/support/existing-customers/" and then clicking "In ESET HOME beheren"), a new empty window opens in my browser (url =
login.eset.com/Login/ResetPassword?returnUrl=%2Fconnect%2Fauthorize%2F......), and that's it.
Yesterday I tried to get help via "
eset.com/be-nl/" -->contacten, after a long search I found a Dutch phone-number for support. (I tried the "chat"-button first, but this also gave me an empty pop-up!) The person n the phone tried to help, took over the pc with Bomgar(?), but could not solve the problem because, he said, he couldn't get into my account because he operates in the Netherlands and I had to get help from a Belgian ESET-worker. That's problem nr. x: nowhere to find any support for Belgian customers.
I tried already to get help by using the 'get support'-button in the program (ESET internet security), but then I'm routed to a Dutch support-site, and they told me that they cannot help me and I should get help at Belgian support. On the Belgian website there is nowhere to find a link/button to specific Belgian support (links/buttons provided on this site lead me to international ESET support site, or Dutch support site). The Dutch support send me a direct link to get help ( -nl/support/contact), and I tried 2 times to get support this way, but I get no answer at all.
Hello.
I have a problem with the new upgrade of password manager. In particular, I can not figure out how to us this tool in my pc. Instructions provided in this link didn't help me. What is this "24-digit recovery key" being asked and where can I find it?
Same problem here. I cannot login into upgraded version of password manager using old credentials (which still work on the other device where I did not perform an upgrade). I tried to reset a password, but it asks a recovery key which i never received during initial registration.
Another issue arose from the importing database from the V2 to V3 (imported file is .xml). Upgraded version is not combining multiple logins, so if you have 2+ logins on website, you will have to input additional logins manually, then assign this website as unique. Which makes the whole process time consuming. This issue is not arising when you simply login into pass manager under your old credentials.
I am sort of new to Jamf Pro and I am having a bit of an issue getting the ESET client on our Mac's Using Jamf Pro the agent goes on without issue and it seems like the needed extensions are dealt with as well but it is not adding the client or showing up on my Eset Protect on premise server console (v8.1) I have been working with ESET for a couple of years but I am just a few months into Jamf Pro. Anyone else have any suggestions. I set things up using eset kb7324 which talks about eset and Jamf Pro. Also these are M1 macs so I have rosetta turned on and EEA in the script to add the antivirus. When this did not work I tried to push the client as a policy using the .dmg but that did not work and it seems like to even do that I really need a .pkg file. Any help would be greatly appreciated.
We used to have ESET. The Agent gets built and installed by a script from what I recall. The ESET server gives it to you. Then you need to have an action in ESET to look for devices with Agent on them and it will then push the Client to the Mac and set it up.
ESET really want you to use them as the MDM for Macs, and then it is an easy task to get ESET on the Macs.
Its been a year or so since I last used ESET so they might have changed their methods since then.
Installation failed. The installer reported: installer: Package name is ESET Endpoint Antivirus
installer: Installing at base path / installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. The package is attempting to install content to the system volume.)
To ultimately fix this I need to find out why the agent is going on fine but not talking to our eset protect console. Once agent shows the device on the console I can use eset to deploy the client. Thanks for the perspective and insight from your experience.
In Big Sur And Monterey, Could be earlier too, there HD is split into 2 partitions. Macintosh HD and Macintosh HD Data. Files that get dropped into the Data drive are ok, but anything in the system drive is not allowed. I had this with a package where there was an icon or similar that it was trying to put in the root of the drive. Or some older packages built on an older version of the OS will also fail with this same error. Have a good look about in Composer.
As to Eset, we had to set up a scheduled task to run and look for any Agents withoout the client. Its dumb, in as much as you have to set up limits time wise, It will look for this week but then stop next week. and you cant say look for the whole of this year. I cant remember the exact procedure to get it set up to schedule the task.
in the original installation script, the installer is parked at "/tmp" and the installation is running from there. This works fine. After the installation is done, the installer package will be deleted, as far, as I was able to check this.
Thanks for the tips. I repackaged it but still was not able to get it working so I went back and manually installed the client for the customers just to mitigate the risk of not having Antivirus active. For now I am going to back away from using Jamf to install the client. Oddly the ESET agent has always installed fine but these agent do not talk to my on premise ESET server running ESET protect 8.1 Just to keep things from getting to confusing I may restart this topic from the standpoint of why the agent does not talk to the eset server. If it would just talked to the server I am confident I can use that to deploy the client easily.
Hi, @Michael_Lynn if you use the original installation script (see above in my spoiler) , the installation of ESET EES will work like a charm. (provided, the right configuration profiles and ppps were configured, before)
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
If you have already removed Eset in another way, you can determine if Eset left remains on your Mac. Just switch to the Remaining Files section, and you will find them there. Select and remove unneeded junk files.
App Cleaner & Uninstaller is an easy Eset remover. However, you are not quite done yet. You can use this app even if you want just to reset Eset.
3a8082e126