TomasP

Hello Forum users, As most of you probably know, Google is shutting down Google+ later this year - and as one of the shutdown steps, the Google+ login will stop working too. Since Google+ is one of the login options on our Forum as well, we have prepared this post with information about the process. While the shutdown will happen on March 7, 2019, some login attempts may intermittently fail starting today (January 28, 2019), as Google is shutting the service down gradually. In case your login attempt via Google+ fails, please try again. We anticipate an update to the forum soon. This will replace the Google+ login option with a Google account login option, which will continue to work after the social network ceases its operation. The switch should be seamless and you should be able to continue using your accounts just as before. In case you have a dedicated Forum username and password, you can also use these to log in, regardless of the current status of the Google login plugin. Users logging in via different social channels or with Forum credentials are not affected by this change. Regards, Tomas

@Nick M, my last post in this thread was on January 9. The release happened on January 10. All the previous posts from earlier this month and from December were referencing the build released on January 10. The build does not predate any posts in the thread.

Hello, these errors are not detrimental to the product's functionality, but nevertheless, can you please let us know the product and version you have installed? Thanks

Hi @andrew.nicholas, We expect it to be released no later than in the upcoming few days. T.

Hello PeterO That's correct, there is no iOS app and no support for text notifications (regardless of the recent changes). The app can be controlled from an Android device. Tomas

Hello, Not at all - actually, your observations and comments helped us find and fix a bug in our product. We do value the efforts you put in this and our development team is sending their thanks. Also, sorry for such delayed response, Peter was out of office for the past two weeks and I did not get to this sooner. Regards, Tomas

Thank you all for your valuable testing and feedback, I will update our development team with your findings. @JetPants I will contact you via a personal message. @andrew.nicholas No date has been set yet, please watch https://support.eset.com/news/ for release announcements (you can also subscribe to receive email updates from the feed). UPDATE: The release is preliminarily scheduled for January 2019.

Hello, Thanks everyone for providing your feedback. We have a new build ready in which we changed detection of granted FDA to EES. I will be contacting you privately with the download link. Regards, Tomas

Hello, As for the silent installation - it is designed as a one-time feature. It allows to install the product without running the GUI. Then you can apply configuration that satisfies your criteria: disabling splash screen, tray icon, etc... After product upgrade, these settings would be preserved and applied to new version too. Regarding the TCC policy, the development team would like to ask you to test it for a different process, in order to compare the results: Open iPhoto and add any picture in the library (if you did not use iPhoto yet. This is required to create photo library on disk that is protected by TCC). If Terminal has NOT granted Photo access yet, try to create a file by Terminal in iPhoto library, e.g.: sudo touch ~/Pictures/Photos\ Library.photoslibrary/database/a.txt If Terminal has not granted Photos access, system will show panels where it asks you to decide whether to allow that access. It is important to do nothing, e.g. DO NOT grant Terminal access to Photos Create TCC profile for Terminal, grant it Full Disk Access Apply that TCC profile on iMac Repeat step 2. If the file was created, Terminal has granted access and the TCC profile is working. If the file WAS NOT created, the TCC policy process is not working and problem is outside of our product

Thank you for the feedback, I sent it to our development team. We will keep you posted.

Hello @mackay, @brandobot, @THahnke. I will contact you privately with the beta build. T.

Hello, We have made some changes to the way our code signing works and now it should satisfy the requirements mentioned in this thread. Are you interested in testing a beta build with this change implemented? Regards, T.

Hello, thanks for reaching out to us. We would like to take a look at this. Please open a ticket with our support team (see https://support.eset.com/kb3742/) and provide us with the following: header information from the message screenshot of details on this message from Mail server log (after doubleclicking on the entry) output from ESET Log Collector (see https://support.eset.com/kb3466/) Thank you, Tomas

Hello, For anyone interested in the latest builds of our Endpoint products - we have just released EES and EEA 7.1 BETA. You can find more details in the dedicated beta forum section at https://forum.eset.com/topic/17644-eset-endpoint-security-and-eset-endpoint-antivirus-71-beta/ Regards, Tomas

Hello, Despite releasing the new, 7th generation of our products just a while ago, we constantly work on improvements and new features and thus we already have a beta build of version 7.1 ready for you to try out. Here's a changelog of EES and EEA 7.1.2017.0: New features: Audit log: Tracks changes of protections state changes, settings changes etc. uPCU logic improved Changes: Rearrangements of Advanced configuration (Notifications, Application statuses) More reliable upgrades You can download the installers from http://ftp.nod.sk/~randziak/EP_7.1_BETA/ Please post any feedback in this "ESET Beta Products for Business Users" forum section. On behalf of ESET Beta team, Tomas

Hello, In this context, partner means a company that distributes the product to the resellers on the given market. There are a few countries where ESET's own office does that (USA, Canada, Slovakia, Czech Republic, Germany, and some more), while in the rest of the world, a local company does that for us. Thus, this is a list of partners/distributors for each country in the world where we sell our products. (Note the website's address starts with eset.com/int, where "int" means you are on an international version of the page, not a country-specific website. What you meant is probably a list of local resellers who sell directly to customers. This is up to each distributor to share the list on their local website (Slovak ESET website has the list published for example). Regards, Tomas

Hello forum users, ESET Security Forum is here for you for more than 5 years now and we are happy to see it grow. Back in 2013, we chose a look that was in line with our products, websites and overall brand at that time. However, in the recent years, ESET defined its brand design in more details and chose a unique color to represent and distinguish itself; a color that is present in most of our online and offline presentation materials nowadays, on our websites, etc. – the turquoise color. During the past year, we have designed a fresh new theme for the ESET Security Forum that fits perfectly with this new brand design. After implementing it and polishing the last few details that came as feedback from our ESET Forum staff (who have been using it for some time now), we are ready to unveil it for the world to see. When you are reading this post, the theme is already live, so you have a first-hand experience with it. We hope you like it – and in case you spot an issue, do let me know directly (via a private message). On behalf of the ESET Security Forum staff, Tomas

Hello, The goal of this message thread is to provide ESET with specific feedback on changes and new features you would like to see in future versions of ESET PROTECT Cloud. Please use the following format when providing feedback: Description: A very-specific one-line description of your feedback. Detail: A more detailed explanation of your feedback. Please feel free to make this any length, but be sure to use terms everyone can understand. If your suggestion is an extension or update to an existing discussion, please include a link to it in your message. You are welcome to discuss the merits of each and every suggestion, but keep your comments on topic, concise and thoughtful. There are other parts of the forum to discuss issues. NOTE: When making your requests do not offer general suggestions such as "better detection, HIPS, firewall, cleaning, and so forth." ESET's threat researchers constantly examine new threats and release updates to the virus signature database and to the modules in order to improve these functions. Requests must be actionable: If you have a specific feature or functionality you would like to see added (or improved) please post it here, but general requests to "make things better" or "improve detection" are not helpful because they do not give ESET detailed enough information. Thank you for your understanding.

Hello novice, I could not help but notice what is being said here. We don't embrace censorship and you are allowed to express your opinion, but assuming overall quality of a long-standing product based on just a few observations is quite bold, to say the least. Also, there are numerous statistics and performance results out there and you just chose those that suit your narrative. Anyway, anyone is free to choose what AV product they will use. If you don't like ours, nobody is forcing you to stick with it - and that's why I don't really understand your constant complaints and posts here on the forum. What is your endgame? What are you trying to achieve? Because what you have achieved so far is just that you created unrest among the community, submitted posts with content that many label as trolling, and didn't contribute to the discussion with anything of real added value. We are not going to ban you, but be prepared that you need to bear the resentment of the community that you sparked. Regards, T.

Hello, We have identified the cause of this issue and are working on a fix. Thank you for your patience.

Hello @BornData and @davidgagnon. I will send you instructions via PMs.

Hello @resscomputer and @glabrador. Check your inboxes soon, I will contact you with further instructions.

Hi @rdtitsupport, We never said we didn't want to give you access, Marcos just asked you to keep this thread just for the signup and describe the issue in a separate thread (of course don't have to do the latter, it's your choice). I am going to send you a message with instructions to access v7 BETA of our Endpoint solutions. Regards, T.

Hi @JakeHD Check your PM inbox for a message with instructions. Regards, T.

Hello Lemmi, We have reported this to our developers. In the meantime, we have learned that downgrading the ODBC driver to 8.0.11 or 5.3 restores the functionality. We will update this thread when more information is available. T.