LCS
-
Posts
7 -
Joined
-
Last visited
Posts posted by LCS
-
-
10 hours ago, katycomputersystems said:
Marcos: Thanks. It's a mix of W7 & W10 causing the update issue. The notification is valuable, we want it to continue, but need a bit more information to help us resolve the alert.
I changed the non-ESET application setting - looking forward to getting this information, it affects less than 10% of our clients, but the information will be helpful.
I changed this setting & waited until the workstation checking in a couple of times, I still don't see the Security Product listed on this page:
Is it on another page, the client's configuration is showing the new setting:
Client has McAfee:
Personally, I think this would allow us to sell a lot more ESET. Going a bit further, I wonder if it is possible to get the expiration date of the installed product? Then a month or two before the competing product is due for renewal, we as MSP's can go in and quote for the renewal.
Andy
-
1 hour ago, ewong said:
Description: Able to determine the "reason" why the task failed in the Task Execution History.
Detail:
Right now, suppose a task failed for a particular system. In ERA, you go to that system, go to "TASK EXECUTIONS", select the task entry, and then right click and select "History", it would show something like:
2018 Mar 22 16:06:58 Security product Failed Task failed Task failed in the security product
There's no way to find out "why it failed" until I go directly to that system and do a manual check.
Having some sort of reason why it failed helps the sysadmin to figure out how to get it updated, if it is at all possible.
I agree with this.
Typical example yesterday, in which I was attempting to install ESET EAV on a machine. The report said "try installing the product locally." Did this and then realised that I was trying to install EAV when I should have been installing ESET File Security for Microsoft Windows Server.
In this case, I would like to see the report come back and say something along the lines of "Detected O/S: Windows Server 2016. Compatible products are ESET File Security for Microsoft Windows Server." Like wise, if it were a linux system, then "Detected O/S: Ubuntu Server 16.04.4. Compatible products are ESET File Security for Linux / FreeBSD." etc.
The agent has all the info about the O/S, so why not use that information and parse back some meaningful information?
Andy
-
Restrict the login of the Administrator account to specific IP addresses, but allow other accounts with 2FA enabled to login from anywhere.
As we cannot delete, disable or rename the Administrator account, the only other option is to only allow the Administrator to login from specified IP addresses only.
Andy
-
Disable the display of the Administrator login account:
-
1 hour ago, Marcos said:
2FA is already supported in the current version of ERA.
I've missed that. Can you educate me as to how to enable it?
Andy
Scrub that. I found it. Doh!!!
-
2FA - I've heard rumours that in the next version of ERA, we will also be controlling Endpoint Encryption as well. I feel that it is imperative that some form of 2FA is used to confirm our login details to ERA. The days of a simple userid (which everyone knows, because it displays automatically), with a simple password are long gone.
Andy
Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
in ESET PROTECT On-prem (Remote Management)
Posted
Agreed. I even thought about the programming logistics of that when I posted it, but as the forum is about suggestions, I thought what the heck, let's put it in, as it is a nice idea (IMO)
Andy