karlisi
-
Posts
149 -
Joined
-
Days Won
3
Posts posted by karlisi
-
-
You mean, March 14 ?
-
Please sign up me too, thanks!
-
Yes, there is no ERAC v6. ERA6 management interface is made using web.
-
The same here. I tried both, ova and vhd, no success.
-
Also, I don't understand why you couldn't have just used the hostname. Yes, it can change; so what? The worst that would happen is you have the client connect to ERAS with the new hostname and the old one just sits in the console waiting for cleanup or manual deletion.
This will be OK in homogenous network. My network consists of about 30 very small distributed networks, about 850 workstations, with duplicate hostnames, dynamic addresses on Internet side and other mess. For me identification by MAC is the best solution, I was very happy when ESET introduced this in ERAS v.5.
-
From my experience if user shuts down computer when scheduled scan is running, this error is generated. All our clients are password protected, so users can't stop scheduled scans, though these errors happens quite frequently..
-
Wow, that are great news! Perhaps after July we will begin planning ERA upgrade to v.6.
-
I'm left with option to walk around 60 clients and do manual upgrade. Can you confirm that future upgrades will work via upgrade client task?
ERA: 5.3.33.0
EEA: 5.0.2254.0
EES: 5.0.2254.0
You are lucky one with only 60 clients. We have 840 clients and only 50 of them are on-site and in AD. Others are in remote locations, most of them not accessible remotely. And this is the reason I am not happy about this (and not the first) surprise from Eset.
-
The same here, business products, definition 13102
-
Thanks for fast reply. We have one last question in our external IP survey: How would you use this external IP if available? Only visual confirmation in Webconsole? or you would also expect dynamic groups and client task (task executed on remote machine) to work based on this IP address? switching configuration based on IP address client is using?
For me this feature is essential. I am using these external IP in dynamic groups. We have about 30 remote sites and so we can easily identify client-to-site relation.
-
From my experience, yes, legacy credentials still works after I generated the licence key.
-
2, We are about to release a newer version of ERA (5.3) soon as well. It will contain some minor improvements and fixes in updater that will be backported from Endpoint v6.
Very god news, thanks ESET!
-
Yes, ESET Endpoint Antivirus 5, connected to ERAS 5.
-
I don't know if it's of any interest to you chaps, but this is what I've done.
What I've done is installed ERA6 on a virtual server *at my house* (HyperV) and I manage all the clients from the one place
Only one ERA server for all clients? Or separate for each client?
Agents on client workstations installed manually, only configuration and monitoring with ERA?
I am very interested in experience with ERAS 6 and clients in many separate networks. Currently we have about 850 workstations in more than 60 remote locations, no VPNs, no servers on remote sites, one ERAS 5 for all this.
-
A competitor offering ESET as well as other AVs? No way
Have ESET at least visited this site before banning? I found no illegal downloads or links on page. At least for ESET and Kaspersky download links are leading to trial downloads on official pages. There is also some text about 'free download not always means free to use'.
-
Setting password for clients to connect to ERAS: In ERA Console -> Tools -> Server Options -> Security tab -> Password for clients
also uncheck 'Enable unauthenticated access for clients'
But first you should set this password on clients, manually
advanced setup -> Tools-> remote administration
or using ERAS policies.
You should create new static group and add allowed clients to it.
Then create new empty child policy below your main policy.and set RA access parameters there
Then add new policy rule, edit filter 'ERA groups in (your new group)' and move this rule to top.
-
Yes, ERAS can be installed on member server. In fact, this is the best place to install it. You should not use DC for other roles except AD related.
-
From my experience ERA can't rename client automatically. If you will change computer name, ERA will see it as new client. My suggestion - don't connect the new-cloned workstations to network, rename them first, it will make things easier.
-
Almost all of them are modified installers with some PUP included. Smart defrag 3 ,i.e., includes some 3rd party toolbar installer. By default ESET antiviruses blocks PUPs.
-
I suppose You installed Endpoint Security on server. Probably it blocks network access to Firebird ports. Try to uninstall Endpoint from server to check if it is the reason for problem.
Endpoint Security and Antivirus are products for workstations, for Windows servers use ESET File Security for Microsoft Windows Server.
-
I have many computers with same computernames. Settings are default
Duplicate names are showing as 'computername 00001'.
-
Check your DNS server for duplicate name records.
-
Do you have a MS Active Directory or local DNS server?
-
For syslog server settings there is a branch Syslog (ERA Server->Settings->Syslog)
Additional column needed in Client tasks view
in ESET PROTECT On-prem (Remote Management)
Posted
It would be great to have column 'Expiration date' in ERA Console 'Client tasks' view. As for now I must open each 'As soon as possible' trigger to check if it is not already expired.