Marcos

Basically all you need to do is send a Remote administrator components upgrade task. Only to upgrade non-ESET components like Apache HTTP Proxy or Tomcat, it takes more steps to upgrade them.

Installing RDS in each of the subnets should do the trick.

That's because "[" is followed by an underscore "_" so it looks like "[_" then.

Do these machines update from a mirror or from ESET's servers? If from a mirror, how is it created? With Endpoint 6.6 or using the Mirror tool? If they update from ESET's servers, do you use a proxy server? Besides the error "module update failed" there should be also additional information about the cause of the failure displayed, e.g. Server not found:

This can happen in ultra power saving mode or when you have an aggressive power-saving application installed. When reporting issues on Android, please always include information about your phone (brand, type) as well as what version of Android you have installed.

Blocking rules are never created automatically. I assume you are using interactive firewall mode and when you were asked to allow or deny/block the communication, you chose deny and also checked the option to create a rule. If you delete such rule, it won't do any harm. Only if the application was installed and the same communication was attempted, you'd be asked to select the action again. You could simply not choose to create a rule when running an installer if you know that you won't run it again any time soon.

You can only hide the icon ("minimal" start mode) or gui completely ("silent" start mode).

That could be because notifications about certain application statuses are disabled under User interface -> Application statuses. These can be controlled separately for clients and ERA, ie. Endpoint may signalize that everything is ok despite some protection modules being disabled and ERA may report alerts. It all depends how this is configured in a policy or directly on clients. You can drop me a private message with an archive generated by ESET Log Collector on that machine or check the policies or Endpoint setup if protocol filtering, email or web protection or integration with email clients is disabled which is what could cause the blank alert in ERAS with current version of Endpoint 6.6.

What is the name of the file? Such large files are usually generated by video streaming when the stream is not recognized.

Please raise a ticket with your customer care since this is something that developers should look into.

The website in question has been blocked as scam for a while. We don't consider websites with guidelines to fixing various errors trustworthy as long as they start with advice to download dodgy or PUA application.

That doesn't mean that any inbound or outbound communication of the process wouldn't be blocked by the firewall. As long as the service is running, it will be in the listening state regardless of whether the firewall blocks the communication or not.

@pps I've moved your issue report to a new topic https://forum.eset.com/topic/15856-blank-problem-field-in-alerts/ where it will be tackled further. Description : More detailed problem alerts Detail: No problem description on problem alerts, (see screenshot below), it's the second or the third time that the same thing happens.

This was a bug in Endpoint when either protocol filtering or email plugin integration was disabled. Are you using the very latest version of Endpoint 6.6?

We don't plan a complete overhaul of gui, there can be basically only minor improvements. With new versions we will bring new features, not a new interface that users would need to get familiar with.

Problem bol vyrieseny vo verzii 4.0.88. Momentalne sa testuje verzia 4.0.90, ktora bude onedlho vydana.

Please refer to https://forum.eset.com/topic/12434-how-to-remove-mobile-not-manage/ and https://help.eset.com/era_admin/65/en-US/client_tasks_stop_managing_uninstall.html. You'll need to send a "Stop managing" task from ERA to remove the virtual agent from MDM. Just uninstalling Endpoint on Android is not enough.

It appears you have already found an answer to your question so I assume no further response is needed.

Please report it to ESET as per the instructions at https://support.eset.com/kb141.

Did you set a correct connection security and authentication type? Maybe Wireshark logs from the machine running the smtp server from time when email is sent successfully and when sending a test email fails could shed more light.

Deploying agent via GPO should prevent many potential issues with push installation. Or use psexec : For more information about methods of deploying agent, please refer to https://help.eset.com/era_smb/65/en-US/deployment_tool.html.

With EIS installed, enable AT: 2, Enter your username and password for my.eset.com portal or create a new account: 3, After a successful login, you will be asked to choose the name of the device: Subsequently you will see the new device in the Anti-Theft portal:

If you delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3DD675F0-E4EB-4CCD-A57E-2C47B8C86675} manually, install Agent from scratch and then uninstall it, does this key remain in the registry?

We indeed have ESET Insiders program where we offer users newer versions of consumer products for Windows before they are made available for the public. Then there may be closed groups for specific users who are provided with business products for internal testing. When beta versions of other products are available, they will offered for testing as well. The statement that ESET does not provide versions for public testing is not true. As far as I know, whoever wants to become a member of the Insider program can freely apply for membership.

That's how it works in ESMC (ERA v7) which is currently in the phase of beta testing and will be released soon.