ShaneDT
-
Posts
236 -
Joined
-
Last visited
-
Days Won
3
Posts posted by ShaneDT
-
-
No I created the agent installer and deployed the agent with this, then once the computers reported back I was able to deploy EES from SMC 7 successfully. This doesn't download any software, just creates the EraAgentInstaller.bat file. This then downloads the agent software when run on the clients. I did however notice this download seemed very slow also.
With ERA 6.5.522 same with the agent, but only way to get EES or EFS installed (EFS on the ERA server, was a new build) was to manually download and install from the public website links, then once installed and updated, deploy the activation task from ERA.
-
I originally contacted AU support a week ago, they confirmed they were also having the same problem on their servers (not sure if test or production).
This problem also occurs on ERA 6.5.522, so not specifically a version 7 issue. On ERA 6.5.522 I was also getting errors deploying EFS and EES from ERA. Only option was to download manually from the download.eset.com websites, then push out the Activation task from ERA. On SMC 7 I am able to push out the installation.
-
Can confirm this is still failing, has been a problem for over a week now!
I've provided wireshark logs to MichalJ. Any idea when this will be fixed?
-
Tip for anyone finding this topic.
After importing, before assigning, check for and update any certificates or server specific settings from the old server
-
-
Nope, installing ESMC from scratch, currently no clients to worry about, just don't want to spend an hour going through my default policy again lol.
-
Is it possible to export policies from ERA6.5.522 and import to ESMC7?
-
Question though and this applies to the v7 products, why are the email notification settings in Policy lacking the same settings available in Server Settings?
There is no option to specify the port or authentication type, and only TLS is available, not STARTTLS. So this doesn't work with Office 365 accounts.
-
Thanks Michal, but apparently v7 isn't yet supported for MSP's, so that doesn't help me yet.
-
Is it possible to configure email threat alerts based on static groups in ERA 6.5.522?
I've tried creating a permission set and native user restricted to the static group, then logging on as this user and configuring under Admin/Notifications, as per;
https://forum.eset.com/topic/14089-notifications-per-groups/
However detections in other static groups still generate emails based on this Notification rule, only with the text;
"Event list is not available, because the user has no read access to the affected computers."
I'm using an Office 365 account for notifications. This is configured in Server Settings using port 587, STARTTLS and 'Automatic' authentication.
There is an option in EES policy to configure Email Notifications, but there is no option to specify the port or authentication type, and only TLS is available, so this doesn't work with Office 365. Strange that policy would not have at least the same capabilities as Server Settings?
Is there any other way to configure email threat alerts assigned to selected static groups?
-
Confirmed that worked.
Cheers.
-
MDM, or 'ESET Mobile Device Connector' to be accurate, is installed on the ERA server.
-
3 minutes ago, LegacyConnectorSupport said:
However configuring server connection via policy would work as well.
So;
Create a new policy for 'ESET Mobile Device Connector' in Admin/Policies in ERA Server, just adding the server as 'localhost:newportnumber' in Edit for the setting 'Servers to connect to', then assign this policy to the ERA server itself.
Is this correct? Leaving all other settings in the policy unselected.
-
This is on ERA 6.5.522.
I selected Mobile Device Connector when installing ERA Server. TBH I haven't even looked at how this works yet.
Everything was fine until I changed the port number. Now my ERA server in ERA console is reporting connection problems for MDC and the status log is reporting unable to connect on port 2222. I tried a 'Repair' install same as I ran for the ERA Agent to reset the port but there was no option for the Host or port number.
If I simply do an uninstall of 'Eset Remote Administrator Mobile Device Connector' from Programs and Features, restart server, then reinstall again using the MDC installer MDMCore_x64.exe, will this screw anything up with ERA Server, and will this give me the option to specify the Host and Port Number during reinstall?
-
Yes I've changed the port there, and I've changed the port for the ERA Agent on both the ERA server and clients, and I've changed the port for any relevant firewalls.
The ERA Agents are reporting back successfully, no issues there.
The problem is Eset Remote Administrator Mobile Device Connector isn't connecting back to the ERA server (installed on the ERA server).
If I go to status.html in C:\ProgramData\ESET\RemoteAdministrator\MDMCore\Logs\Proxy\ it's still trying to connect on port 2222.
-
Thanks, but what about on the ERA server itself?
-
Is it possible to change the replication port for MDM on the ERA (6.5.522) server?
When installing ERA it wasn’t possible to change this port.
I’ve changed it post install for ERA Server and Agents, then run Change/Repair on the Agent in Programs and Features to change it for the ERA Agent, but if I run Change/Repair for MDM there is no option for the Host or Port Number.
Is there some other way to change this from the default 2222?
Thanks.
-
Yes https://edf.eset.com/edf resolves to some xml text.
As per my post, several clients updated and reactivated fine. These three didn't.
So are we not supposed to update the endpoint software?
What does the policy 'Program Component Update' do?Myself and my customers are getting very tired of having to constantly manually update this software. My customers don't understand why I'm having to continually charge them to update their antivirus. Every other antivirus program I know of has automatic program updates as standard, has had for years. Then again every other antivirus company has hosted management platforms, and have had for years! Only Eset requires having to still run the management software on an internal server, that also needs to be manually updated!
-
Hoping someone can help. The amount of time I waste trying to resolve issues with ERA, updates and activation is very frustrating!
First question, why does EES never self update? I have the following option enabled via ERA policy on all my customers servers, but EES and EFS never ever self update, I always have to manually deploy program updates from ERA, which always generates intermittent problems with clients failing to update, failing to reactivate, and now reverting to an old licence!
Policy:
Program Component Update (set to): Always update program components.
With this enabled program components never update! Why? I can't find any other policy that relates to program updates?
So updating computers via ERA on one of my customers this weekend. Create Software Install task for several PC's that are all online. Several of these complete successfully, restart and all OK. One updates but reverts to the previous licence expiry date (ie last year). Two refuse to update and continualy fail. So I manually download and run the software which completes successfully but again both revert to the previous licence expiry date!
All attempts to deploy Product Activation from ERA or enter the Licence Key manually on the client fail with error: Activation was not successful: Could not reach activation server.
Yet these computers are resolving all URL's listed on the following website under 'Activation' however not all respond to ping.
https://support.eset.com/kb332/#services
The following two url's do not resolve and their IP addresses do not respond to ping either, so I assume these are no longer used?
edf-pcs.cloudapp.net
edf-pcs2.cloudapp.net
All computers on the network use the same server for DNS, the local Domain Controller, there is no Internet Proxy server on the network and there are no outgoing port restrictions.
What should have been a simple process has again cost me numerous hours over this weekend and I've only completed this on a quarter of this customers computers! I have customers with Trend Micro (mostly customers that don't have a server) and I never have issues with their computers. They auto update everything including their licences!
Can someone please shed some light on where to look to troubleshoot this issue. Yes I have spent hours searching already and haven't found any answers that help.
ERA Server version is 6.3.136.0.
(yes I know this should be updated, but again with multiple customers finding time out of hours ie on weekends to update all these customer manually along with all the other required after hours maintenance is challenging! Why does Eset make everything so complicated and difficult!).
ERA Agent version on all computers is 6.3.136.
EES version was 6.5.2107.1 and 6.3.2016.0 (no I don't have documented which was which before the upgrade).
EES upgraded version is 6.6.2072.4.
Operating System on all the PC's that have reverted their licence is Windows 7 Professional with all latest updates installed.
-
It's very disappointing that Eset Engineers(?) are not even able to replicate the problem. I can't believe that so many people are having this problem but it works perfectly every time at Eset. Does not give me a good feeling selling these products to my customers knowing the inability of the Eset developers to write code that works.
-
Hello guys,
we released a new version of ESET Online Scanner recently.
In case you encounter a crash please capture the crash dump and send me and TomasP a private message with a download link so we can check it.
Regards, P.R.
When did Eset release a new version? Will give it a go when I have a chance. Let's hope it's been fixed.
-
Shane, you're absolutely right. V2 has crashed on EVERY Windows 10 machine I've tried it on (I fix PC's, I see a lot of them). I found V1 here (it appears to be safe and "uncorrupted": http :// eset-online-scanner.en.uptodown . com / windows / download (fix the spacing to make that work as a link). Good luck.
Thanks Laurie(?), I already have the v1 scanner file. Didn't want to mention here in case it suddenly stopped working lol...
-
Wow that was quick
Try running it on a PC that is more representative of real world computers that this might be run on. Lots of programs installed, 100Gb plus of files, something that will take more than an hour to complete the scan. Also (from memory) when this has crashed the scan had already detected threats, and when I've then repeated it and it didn't detect anything it's completed. So maybe download and install some malware so it detects something during the scan. PUPs like Ask or Google toolbars should do the trick.
But you're also missing the other major point of my post. When it does crash, there is no record of the files that it has detected as threats and therefore what files it has deleted. So there is no way to review the scan for any false positives, nor is it possible to restore these false positives. With the old version there was a log and there was a quarantine. And you could run the scan again at any point in the future and still restore previously quarantined files, if you hadn't chosen to delete them of course.
Your scanner should not delete files, it should quarantine them and present the option to delete, as the old version did. Eset is very aggressive with malware and pups, and often what is detected as a pup is actually a legitimate program. Having these automatically deleted is another reason I won't be using this new version with my customers.
-
Hi Peter,
It crashes almost every time I use it, W7, W10, no matter the operating system or computer. It looks like there are plenty of others also having this problem on here.
Sorry I just don't have time to troubleshoot this for you by creating dumps etc, I'm sure if you run it a couple of times on your own systems it won't take you long to replicate.
Personally I've given up on it. Don't have time to waste with products that don't work. Sorry.
Request for feedback on a plan to change handling of Potentially Unwanted & Unsafe Applications
in ESET PROTECT On-prem (Remote Management)
Posted
I would really like to see a separate setting available for how to handle PUA's.
By default I setup policy with everything set to max security settings, enabling Strict Cleaning on all policies.
But it would be useful to be able to set this setting separately for PUA's, as this often picks up and deletes programs/processes in use by the client. And I don't want to reduce the response for viruses and malicious processes by changing this setting to Normal Cleaning, so as a result have started to disable PUA detection, which again I really don't want to do.
I'd like to be able to setup PUA detection separately so I can set these to alert only, prompt, or Strict Cleaning depending on the customer.