jimwillsher
-
Posts
593 -
Joined
-
Days Won
5
Posts posted by jimwillsher
-
-
No issues here, sending a test email and relaying off my O365 tenant. It took 2-3 seconds before displaying the "sent successfully" message.
-
or consider installing ERA on a completely different network. I manage 6 separate companies, on different subnets (completely different parts of the country in fact), and they all connect to my central ERA on a different network entirely.
-
Thanks Marcos, I suspected that was probably the case. i just mentioned it because some people may find it disconcerting, worried that they are choosing the wrong package etc. e.g. no mention of 2012R2 or 2016, but mention of 2003.
-
-
-
Have you configured Endpoint to add the "scanned by" tags to messages?
-
Sounds perfect for me. I manage four customers, but ERA6 is installed on a single server....in my house! Purely since the customers had no hosting capability. This will allow me to ditch the server here and move to a hosted platform.
Hopefully we can help beta-test it later this year?
Jim
-
Thanks Martin, yes I got that error with everything I tried
-
Thank you very much Marcos, that was the missing piece in my jigsaw :-) That's working perfectly.
Excellent!
Jim
-
Thanks Marcos, I've configured that but it doesn't seem to want to work for me. Hopefully the screenshots show how I have defined the policy, and I have confirmed that the policy has been applied.
-
Thanks Marcos, but I can't find that anywhere in the EEA or ERA tree (ERA 6.5, EEA 6.6 beta)
-
Sorry to harp on about this, but please can someone advise on how I make a *permanent* exclusion for something that ESET classes as a PUA but which I feel is unfounded. Every day my file gets scanned and shows an alert; every day I say "no action". Rinse and repeat.
I've now resorted to deleting the utility and will simply re-download it when I need it, but that is NOT the solution. There must be a way in EEA or ERA to exclude this alert type or marking the file as safe. i don't really want to use path names as I have several copies/versions of this file.
Many thanks
Jim
-
Hi folks
I'm looking to add a filter to report, listing only software where the application name begins with "Microsoft Office" and ends with "2010" ?
Many thanks
Jim
-
Can someone advise me how I exclude Win32/Auslogics.F from being detected as a PuA? Every single day i'm getting alerted to the AusLogics Disk Defrag utility, which IMHO is not a PuA. So each day I choose "No action" (as opposed to Clean or Delete) and the warning goes away, until the next day. I don't reaelly want to disable PuA checks globally, but equally, I don't want to delete this utility which I do use frequently.
Happy to disable via EEA 6.6 Beta or ERA 6.5. I just need to know how.
Many thanks
Jim
-
Can you pm me your email address, then I can forward the email in its entirety. Probably easier than be trying to send the email and attachments to you on the forum.
-
Not sure if I'm the only one to receive this, but I've received an unsolicited email from a company trying to persuade us to move from ESET to McAfee. They have sent a supposedly authoritative summary report, showing different AV products and their "security effectiveness". I won't post the actual report here, but out of 13 AV products, only two are rated below ESET. Clearly it's difficult to judge their exact basis for the testing, but I am curious to know if anyone else has received a similar report? Needless to say, the report shows McAfee to be on top :-)
Jim
-
Sure, but I'm still confused why it's a PUA. TO me, PUAs are stuff like the ASK Toolbar, things that install themselves in the background without permission, trackers, etc. Whereas Auslogic's disk defragger does exactly what it claims to do and it does it very well. And I use the Portable version from their website, which doesn't even install anything.
I've unblocked it and allowed it, I'm just very surprised.
-
Hi
Curious why AusLogics Disk Defragmenter (portable) is flagged with win32.auslogics. I've used their software for years with no issue.
Jim
-
rkok, there's a beta of 6.6 that I've installed successfully on build 1703 machines that wouldn't otherwise install 6.5. Just in case that's of use to you?
-
Many thanks Marcos.
Just to be clear, this was a new install, not an upgrade. Interestingly, I recently upgraded 80+ Windows 10 computers, and on a few of them, ESET seems to vapourise/get removed. Maybe related? Maybe not.
6.6 is continuing to work perfectly for us.
Jim
-
Thanks Peter; can you upload the EEA versions please?
You may have seen a forum posting of mine yesterday. I had two brand new Win10 laptops where EEA 6.5 wouldn't work at all, but 6.6 did work. I'll be curious to try this later version.
Jim
-
Me again....
The 6.6 beta, when locally installed, seems to work okay, in that it's talking to ERA and picking up tasks etc. GUI also looks okay.
Jim
-
OK so I've given up for now. To summarise (TL;DR) :
- Windows 10 Pro x64, build 1703, clean install. Workgroup, not domain. ERA is hosted external - access across internet, in standalone domain. ERA works fine for my other 160+ computers, some of which are workgroup machines.
- Pushing EEA 6.5.x from 6.5.x ERA. EEA appears to be installed, and ERA reports that the definitions are current and shows the icon and the security product, but there is virtually no trace of EEA on the client - no GUI, no start menu, no entry in appwiz.cpl. App uninstalls correctly via the ESET uninstaller command-line tool in safe mode. Event og shows the error as per my forum post title.
- Installing EEA 6.5.x directly on the laptop by running the .EXE is slightly better, in that the GUI and appwiz.cpl etc look okay. EEA also correctly "checks in" to ERA every few minutes. Status.html file also shows green. However EEA refuses to pick up any ERA policies or run any assigned tasks (such as product activation). Uninstalls correctly via control panel.
It's very rare that I have to work with workgroup laptops, they are almost all domain-joined. But I don't think that's the problem, I think it relates to Windows 10 Creators.
I have two laptops, both unboxed today, both identical, and both exhibiting identical behaviour. Both were brand new Dell laptops with Windows 10 x64 1607 installed, and I've used the Windows Upgrade Assistant to upgrade to build 1703. One laptop had the agent installed before the 1703 upgrade, the other laptop had it installed after the 1703 upgrade.
These laptops aren't needed urgently so I am happy to help troubleshooting, and I can provide remote access if that helps (TeamViewer). Getting it to work via ERA would be my preferred route.
Many thanks
Jim
-
Hi Marcos
Clean install laptops, purchased this week.They had build 1603 of Win10 which I've upgraded to 1703, and then installed (or tried to) EEA.
The manual installation hasn't moved me forward. It installed okay, the GUI is there etc, and it's successfully communicating with ERA. However it's not puling any tasks from ERA - and my first task is the Activation task.
So I'm not really any further forward.
Jim
Support Win 10 1709
in ESET Endpoint Products
Posted
No issues here with 1709 on 6 PCs