ShaneDT
-
Posts
236 -
Joined
-
Last visited
-
Days Won
3
Posts posted by ShaneDT
-
-
54 minutes ago, Peter Randziak said:
Hello guys,
few moments ago we released a module update to pre-release update channel so far, which will adjust the EoL messages behavior and those will be reported in the management console only in the managed environments.
Thank you for the feedback and use cases provided.We apologize for the inconvenience caused by this.
Peter
Great news, good to see ESET listening to their partners/customers and taking action.
This leaves the first part of my post still to be answered. Why do automatic program updates still not work?
The reason in my case for a lot of these alerts is because the only way program updates get installed on 95% of my client computers is when I schedule it and push the updates out from ESET Protect. Again strangely around 5% of my customers computers do auto update, I have around 4 out of 100 computers that have auto updated to 10.0.2034. All computers have the same policies assigned. All computers are similar in operating system and configuration.
It would be good to have automatic program updates work consistently.
An option to enable automatic update to the latest version and latest version minus 1 would also be useful to allow enabling a test set for each new version released.
-
The other strange and annoying part of this is there is no consistency on which clients are getting these alerts.
For example some computers with 9.0.2032.6 installed are getting this alert, while others aren't, all in the same group on ESET Protect with the exact same policy applied?
Is this some kind of bug in the software?
I can appreciate maybe generating warning if still running 8 or below, but generating warnings on the client computers for a version that doesn't go end of life for another 12mths just creates headaches for all involved.
-
^^^ 100% this. This is just silly. Why suddenly are we alerting users that their product will be end of life in 12 months!?
-
-
So this morning I'm receiving lots of emails from my customers all asking about a new prompt in ESET reporting that their security product is out of date.
"Your current security product is going to reach end of life on 2023-11-30"
Most of these computers are all on 9.0.nnnn.
So first question, what happened to ESET supposed to be able to finally do automatic application updates from v9?
Secondly, how can I disable this prompt so I don't inadvertently have customer clicking on this and making a right royal mess of it!?
-
58 minutes ago, MichalJ said:
Most of the competition handles is in the way, that "custom report builder" is not even available, and they just offer you "out of the box" set of reports.
Yes but that's why we don't sell or support the competition
Following is a list of what I'd like to be able to export to csv to then import in Excel. Or if there was a way to export the Details \ Basic and Details \ Hardware pages for each computer as this has all these details. There must be a way to bring this together since it's brought together in the gui?
Serial number
Computer name
Computer workgroup
OS Version
OS Name
OS Service Pack
OS Platform
Manufacturer
Model
Serial number
Trusted Platform Module (TPM) version
Firmware version
CPU Description
RAM Total
Storage / Description
Capacity
Chassis -
This is on ESET Protect Server v8.0.1238.0, but has been an issue since at least early v7.
Running on Windows Server 2012 R2 Standard.
-
Why is it when you select an item to add a column when creating a report, suddenly this then limits what additional items you can add to the report?
For example, I want to create a report for hardware inventory.
So I add Computer Name. So far so good.
I then add Manufacturer.
I then want to add Model, but already I've been reduced to a very small subset of items, and Model is no longer available.
So I can't add model, processor, memory, hard drive, firmware details, driver details, etc...
I basically want to create a report that exports everything on the Computer Details / Basic and Hardware TABs but ESET Protect doesn't let me do this.
Same applies for other reports I want to run. I have weekly reports for all my customers with different information but I have to separate these reports into half a dozen different reports as I can't select everything I want in one or two reports.
This has been a problem for a long time. Can it be fixed please?
-
OK I'm confused.
I would have thought enabling "Disable checking upon inbox content change" would disable scanning of emails in the Inbox?
That's one thing about ESET, it's a great security product, but by god you guys make it complicated...
-
Marcos do we have any idea on when this will actually be fixed without disabling scanning of the Inbox?
Having incoming email being scanned in Outlook is one of the big selling points of ESET. Even with Office 365 scanning I regularly see emails being picked up by ESET on customers computers with krypto attachements. So disabling scanning of emails in the Inbox IS NOT a viable option.
Is this something that the developers are actually working on or does it continue to be ignored?
As has been said many times, this problem with sync conflicts due to attribute changes has been a problem for many years. Surely it can't be that hard to just disable the attribute changes?!
-
Everyone will be having these Sync Conflicts issues, just 99% of people don't realise because the default view in Outlook is the Mail virtual view, and you don't see the Sync Issues folders in this view.
-
16 minutes ago, Marcos said:
Not really. The bug with "Disable checking upon inbox content change" was discovered and confirmed by developers on July 23, 2021.
We have already rolled out a uPCU to the latest v8.0.2039 for users with older Endpoint v8.0. As for uPCU to v8.1, a new service build is going to be released within a few days. After 30-60 days it will be released as uPCU.
You could avoid sync issues by reading email only on one device. Accessing it from more devices with ESET installed and Outlook email protection enabled at a time increases the chances of sync issues.
I'm pretty sure this problem with Outlook has been reported well before July 23 this year...
So the automatic updates are only for minor updates? I thought this was for minor and major updates post 8.0? So computers currently on 8.0 would receive 8.1 automatically? This doesn't seem to be happening. (Yes I did notice a minor update on some 8.0 computers that I hadn't yet manually deployed the 8.1 update to).
Edit: Also having ESET and Outlook on multiple devices (which is very very common) doesn't increase the chances of duplicates in the Conflicts folder, it GUARANTEES it! Every single email gets duplicated. As has already been reported by me and several others.
-
9 hours ago, Marcos said:
The fix won't be included in the upcoming Endpoint 8.1 service release yet, however, we will be able to provide you with a fixed dll. Also we should be able to provide you with newer installers that you could install via a software install task to upgrade existing clients. However, this version will not undergo QA tests and we'll be able to test it just briefly before giving it out to particular users. A drawback of using an unofficial version is that it cannot be upgraded via the so-called uPCU in the future and you will need to use a software install task. The fix will be included in Endpoint v9 available later this year as well as in possible futrther service release of Endpoint v8.1 that may be released after v9 too.
That is disappointing. This problem has been known for so such a long time, and a fix has been promised (and not working) also for a long time. I'm not interested in deploying an 'only briefly tested' version to hundreds of customers computers. Will the dll fix be able to be deployed by ESET Protect? Will this affect future 'uPCU' updates?
Whatever happened to automatic program updates by the way? This feature has been in policy for a long time and also has never worked. Wasn't this supposed to be fixed in version 8.0?
-
Can we please have an option in "Web and Email / Web Control" to create rules to block websites based on keyword.
For example, for an unproductive student, we don't want to block youtube completely as this is sometimes required for their school work, but we do want to block youtube videos on for example Minecraft.
Now admittedly we are assuming every youtube page with a Minecraft video will have the word 'minecraft' on that page, but most probable will, so at least this rule would block most of these videos.
This is just one example of many that we could come up with to block content that is not currently covered under the set categories, and where blocking based on url is not practical.
-
Seems strange this would not be available for websites but is available for emails?
-
Looking at the current policy options in "Web and Email / Web Control" there doesn't seem to be any way to block websites based on keywords?
ie I want to block all websites with the work 'Minecraft'.
Is there any way to do this? If not is this a feature that might be available in a future release?
for ESET EndPoint Security managed via ESET Protect server.
Thanks.
-
On 9/12/2021 at 1:08 AM, Marcos said:
A new service release of Endpoint v8.1 is going to be released with the next few days. I'll need to check with devs if the "Disable checking upon inbox content change" setting is already fixed there.
Marcos did you check with the 'devs' whether this setting was being fixed in the business version and what date this release was please?
-
1 hour ago, CraigC said:
TBH, I don't think this issue is an easy problem to fix, if it was we wouldn't still be chatting here about the issue that has been around for a long time. The issue is just hidden for majority of users, and is only noticed when looking at mailbox size. The issue is not just about mailbox size, but performance / overhead of the AV software on the device, again this is hidden with fast devices with SSD drives, but the issue is still there.
Obviously not understanding technically how it works, I don't understand why not tagging the metadata of an email that is scanned would be so difficult? OK so ESET no longer knows which emails have been scanned and which haven't. Is that really a problem. All this really needs to do is scan emails as they are received in the Inbox. Maybe add an option to do a full mailbox scan on a schedule, but even then it shouldn't need to tag the emails.
Yes tagging the email would be ideal yada yada but if it causes such a major issue (I've been running Powershell on my customers tenants all day, most are around 10-30% capacity in Conflicts, some are up to 80%!) that has been a problem for so long, why persist with it?!
Just simplify it down to just scan new emails as they are received in the mailbox, no tagging, and optionally add an option to schedule a full scan. Leave the option to manually scan folders but again without tagging.
Re your point 3 above, that used to be a major problem when first installing ESET on a customers computer. First thing it would do is scan the entire mailbox already downloaded in Outlook, which would trigger Outlook to resync the whole mailbox (EDIT: Actually from memory it was only the Inbox)! From memory disabling some of the settings in the security policy did fix this at the time. That's where I remember I had these settings set to Never.
-
No Marcos that would not be an acceptable solution.
If that computer is being used and the other isn't then emails aren't being scanned as they are received.
-
PS: Probably better to use Get-Mailbox -ResultSize unlimited as this will then include Shared Mailboxes.
-
Thanks Craig, was going to go looking for a PowerShell command today so I can compare the size of these folders with the total size of a users mailbox. Help to identify those with the biggest problem.
I've found in testing yesterday, if you have Outlook on two computers with ESET installed with Outlook open at the same time, every single email received gets duplicated to Conflicts, some times twice. Makes sense as ESET is scanning and tagging these emails twice. This was the case for my customer in the thread I started. She has an office PC that she normally leaves on with Outlook open at the office... But even with Outlook only open on one computer I'm still seeing maybe 10-20% of all emails getting duplicated.
Re ESET, they have known about this problem for years, there are settings in policy that are supposed to remove this tagging that have been there for years, they just don't work!
This will be a problem for EVERY user that has Outlook and the ESET Outlook plug-in. Most just don't know it as they never see these Sync Issues folders as they're hidden in the default Mail view in Outlook. It's only if you switch to Folder List view that you see them.
ESET just needs to fix it.
How did you go with the xml file Marcos provided? Did this work for you in the end?
I assume this is imported in EES on the actual client? For a managed client (policy assigned by ESET Protect Server) I'm just worried it may screw up settings pushed down by the server.
If this xml policy works I don't understand why they can't just add it to security polices that are applied from the server!?
-
14 minutes ago, ShaneDT said:
I'm able to trigger these conflicts on demand by emailing myself news links from my iPhone. Sometimes this creates two duplicate emails in the Conflicts folder!
Actually looks like this was due to having Outlook open on both my office PC and notebook. With Outlook open on both devices EVERY email is getting duplicated to Conflicts! Makes sense I guess...
-
Marcos do you have instructions on where and how to import this xml file you linked earlier please?
I'm assuming from reading through the other thread that this is imported in the client itself which creates a new policy directly on the client? Is this how it works? If yes why can't ESET release a policy update for the ESET Protect Server so we can push this out as a policy update for all our client computers?
Also I've been trying disabling different settings tonight, none of these make any difference.
Force Enable ‘Disable checking upon inbox content change’.
Force Disable ‘Allow advanced antispam scan’.
Force Disable ‘Start email client antispam protection automatically’I'm able to trigger these conflicts on demand by emailing myself news links from my iPhone. Sometimes this creates two duplicate emails in the Conflicts folder!
-
I'm right now looking at the realization that I have hundreds of GB's of emails duplicated to the Conflicts folder on hundreds of customers computers that will need to be cleaned up. Even if we assume that all of these duplicated emails are due to ESET, and therefore it's safe to just empty the Conflicts folder without backup or review, this is hours of work that my customers aren't going to be happy to pay me to do! If we assume that not all of these emails are due to ESET, and we can't just empty these folders without backup or review, this now becomes hundreds of hours of work!!
EES and duplicated emails in Outlook Conflicts folder - finally resolved?
in ESET Endpoint Products
Posted
Referencing the following discussions - threads now closed.
It does appear this probably is finally resolved with version 9.1.2060.0. I haven't checked with my customer computers yet, but my own computers were updated to 9.1.2060.0 around the end of October. I only have one email in my Conflicts folder since then
Thank you ESET developers for finally resolving this long running issue. Let's hope it stays resolved.