Jump to content

CraigC

Members
  • Posts

    17
  • Joined

  • Last visited

About CraigC

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.
  1. @Marcos maybe some confusion here. There has been an ongoing issue with ESET and Outlook Sync issues for many years. There may have been some fixes, that rely on importing config files, as the options are not visible on GUI, but the issue has not been addressed as a proper solution. It seems this fix is broken, and has been reported as a specific BUG in a specific version of ESET that I reported to ESET UK in July. If we look at the Windows Server ESET product, it automatically detects the environment its being installed on and will apply exclusions etc. I wonder if the same should be applied to the ESET client on Windows, if it detects Outlook and Exchange, any 'fixes' or configs should be automatically applied as default? I know this issue and specific bug are maybe not seen as high priority, as its only affecting performance, excessive IO/CPU cycles, disk space. On modern PCs this is masked with fast CPU, SSD drives, and massive Office 365 mailboxes, and most people are unaware of issue, so is not widely reported. I also don't understand the logic of prioritising a fix in a Home version before the Business version? In my experience Home users do not tend to use Outlook and Exchange. You can not avoid Sync issues even using one device with ESET/Outlook/Exchange, you will still get sync issues. ESET must be seeing this is QA/Testing?
  2. Hello @Marcos, I originally started this thread specifically regarding v8.1, the business product that is more commonly used with Outlook and Exchange. You refer to v15, the home version? Will this ongoing sync issue also be fixed in the business version? When will this be release? I did open a case with ESET as you originally suggested, but I have not heard anything back from ESET with regard to this fix or release date? The ticket case ref in the ESET system is #CASE_00129486. Regards, Craig
  3. It doesn't work. I was advised to open a case locally here in UK with version 8.1, I supplied some debug info, and ESET HQ confirmed its broken, with no timescale to fix. I would suggest you do same, and refer to this thread and the many others. 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. I do hope ESET are having discussions with Microsoft on how to resolve. @Marcos There are a few use cases ESET need to consider when testing with Office365 mailboxes: 1) Multiple devices sharing same mailbox. This often happens in companies, users have their own mailbox and a shared mailbox, eg 'customerserivice@', 'finance@' etc. Also Manager / PA / Secretary type 2) Multiple devices with same mailbox, eg laptop and PC 3) Brand new devices with ESET installed, that will sync a whole mailbox.
  4. If you are running Office365, you can run a powershell command to show how BIG the issue is for all the mailboxes on a single tenant: Get-Mailbox -RecipientTypeDetails UserMailbox | Get-MailboxFolderStatistics -FolderScope SyncIssues | Select Identity, Name,FolderSize Use the guide here to setup exchange online powershell if you haven't already: https://docs.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps I think the issue is compounded with shared mailboxes and/or multiple devices accessing a mailbox that are all running ESET Endpoint. It would be good if ESET can build these use cases into their QA tests for Outlook Plugin, rather than just a single mailbox with a single ESET endpoint device.
  5. I have runs scripts on some of our Office365 tenants, and have notice all ESET users running various versions are getting issue, its not just 8.1. Also, and I think this is important, the issue is compounded if there are multiple devices accessing the same mailbox. Take the example of a manager who has a PC, laptop & mobile all connected to his Office365 Exchange mailbox, he also has his PA/secretary accessing his/her mailbox from their PC. So, 2 PCs and 1 laptop all running ESET, all with ESET Outlook plugin enabled accessing same mailbox, this is where the issue gets compounded. We are seeing 25%, 25GB of sync issues in a 100GB mailbox.
  6. Hello @Marcos, I did as you suggested, the diagnostics have been been reviewed and the issue has been classified as a BUG. The instructions on the ESET website that I posted above, and are supposed to work with v8 do not correct the issue with ESET writing named property: EsetMessageFlag into the messages. The ticket case ref in the ESET system is #CASE_00129486. I am surprised other ESET and Office365 users are not complaining about this, we have seen some mailboxes that are 25GB of sync issues, due to the EsetMessageFlag property issue.
  7. Hello @Marcos I am getting sync issues on all new messages. I set the following 3 days ago. <NODE NAME="DisableInboxChangesChecking" TYPE="number" VALUE="1"/>
  8. Hello @Marcos, I was wondering if there is any update on this? I am still seeing these sync issues, even after applying the settings you recommend: 13:16:50 Checking local modifications 13:16:50 Ignore property: 0x3FFA001F 13:16:50 Compare named property: EsetMessageFlag 13:16:50 Getting remote properties 13:16:50 Checking remote modifications 13:16:50 Compare (conflict) named property: EsetMessageFlag 13:16:50 Local: {I4:0} 13:16:50 Remote: {Error (0x8004010F)} 13:16:50 Not equal (conflict) named property: EsetMessageFlag 13:16:50 Local modification: {12:16:40.0993 13/07/2021 [DD/MM/YYYY]} 13:16:50 Remote modification: {12:16:41.0490 13/07/2021 [DD/MM/YYYY]} 13:16:50 Conflict generated, remote item is winner And here is my config: <ITEM NAME="01000800"> <ITEM NAME="settings"> <NODE NAME="OutlookIntegrationEnabled" TYPE="number" VALUE="1"/> <NODE NAME="OEIntegrationEnabled" TYPE="number" VALUE="1"/> <NODE NAME="WLMIntegrationEnabled" TYPE="number" VALUE="1"/> <NODE NAME="DisableInboxChangesChecking" TYPE="number" VALUE="1"/> <NODE NAME="OutlookIntegrationChangeCounter" TYPE="number" VALUE="0"/> <NODE NAME="OutlookSyncIssuesFix" TYPE="number" VALUE="33"/> <NODE NAME="OutlookCOMAddinForced" TYPE="number" VALUE="0"/> <NODE NAME="DeliveryByEESessionEventsEnabled" TYPE="number" VALUE="0"/> <NODE NAME="ExportToMsg" TYPE="number" VALUE="0"/> <NODE NAME="OEAlwaysUseEplgHooks" TYPE="number" VALUE="0"/> <NODE NAME="ExportToEmlEnabled" TYPE="number" VALUE="0"/> </ITEM>
  9. Still does not make sense to me @Marcos. Here is what is I have done: 1) I have changed settings as per my post above. 2) I have restarted my PC and Outlook 3) A new message arrives, but I still get the Sync error Are you saying If I make the change from 0 to 1, even if a new message arrives the property is still written to new messages?
  10. Mailbox is 7GB. I don't fully understand what the DisableInboxChangesChecking is doing, as documentation just says "If you are experiencing system slowdown when retrieving emails, enable this option" But, if the 'disable' is enabled, ie '1', then I don't know why it would have to update new messages that arrive in inbox after the setting is enabled, and PC rebooted. I am using Office365 as server, there are no PST's, just OST for cache.
  11. Hello @Marcos, yes I tested this setting, it makes no difference to Sync issues. I am now in contact with UK support, and I have given them a link to this forum post. 16:10:07 Remote: {Error (0x8004010F)} 16:10:07 Not equal (conflict) named property: EsetMessageFlag 16:10:07 Local modification: {15:10:02.0327 09/07/2021 [DD/MM/YYYY]} 16:10:07 Remote modification: {15:10:00.0459 09/07/2021 [DD/MM/YYYY]} 16:10:07 Conflict generated, local item is winner <ITEM NAME="01000800"> <ITEM NAME="settings"> <NODE NAME="OutlookIntegrationEnabled" TYPE="number" VALUE="1" /> <NODE NAME="OEIntegrationEnabled" TYPE="number" VALUE="1" /> <NODE NAME="WLMIntegrationEnabled" TYPE="number" VALUE="1" /> <NODE NAME="DisableInboxChangesChecking" TYPE="number" VALUE="1" /> <NODE NAME="OutlookIntegrationChangeCounter" TYPE="number" VALUE="0" /> <NODE NAME="OutlookSyncIssuesFix" TYPE="number" VALUE="33" /> <NODE NAME="OutlookCOMAddinForced" TYPE="number" VALUE="0" /> <NODE NAME="DeliveryByEESessionEventsEnabled" TYPE="number" VALUE="0" /> <NODE NAME="ExportToMsg" TYPE="number" VALUE="0" /> <NODE NAME="OEAlwaysUseEplgHooks" TYPE="number" VALUE="0" /> <NODE NAME="ExportToEmlEnabled" TYPE="number" VALUE="0" />
  12. This option is currently disabled, I can enable the option to disable the checking, but would like to understand what the impact of this is? There must be a good reason for ESET to have this option enabled by default?
  13. Hi @Marcos, you say above it was not supposed to be in 8.1, but you did say "it will be included in 7.0" three years ago, I am curious what the delay is?
  14. The fix does not seem to work with 8.1, still seeing this in Outlook: 10:02:04 Remote: {Error (0x8004010F)} 10:02:04 Not equal (conflict) named property: EsetMessageFlag 10:02:04 Local modification: {09:01:59.0310 08/07/2021 [DD/MM/YYYY]} 10:02:04 Remote modification: {09:02:01.0438 08/07/2021 [DD/MM/YYYY]} 10:02:05 Conflict generated, remote item is winner Here is export of settings: <ITEM NAME="01000800"> <ITEM NAME="settings"> <NODE NAME="OutlookIntegrationEnabled" TYPE="number" VALUE="1" /> <NODE NAME="OEIntegrationEnabled" TYPE="number" VALUE="1" /> <NODE NAME="WLMIntegrationEnabled" TYPE="number" VALUE="1" /> <NODE NAME="DisableInboxChangesChecking" TYPE="number" VALUE="0" /> <NODE NAME="OutlookIntegrationChangeCounter" TYPE="number" VALUE="0" /> <NODE NAME="OutlookSyncIssuesFix" TYPE="number" VALUE="33" /> <NODE NAME="OutlookCOMAddinForced" TYPE="number" VALUE="0" /> <NODE NAME="DeliveryByEESessionEventsEnabled" TYPE="number" VALUE="0" /> <NODE NAME="ExportToMsg" TYPE="number" VALUE="0" /> <NODE NAME="OEAlwaysUseEplgHooks" TYPE="number" VALUE="0" /> <NODE NAME="ExportToEmlEnabled" TYPE="number" VALUE="0" /> </ITEM>
  15. OK, thanks, but I'm sure this was supposed to be fixed in 7.x. Is this the correct workaround? FWIW - Chrome browser blocks the download, says the download is dangerous. https://support.google.com/chrome/answer/6261569?visit_id=637611007709209594-884251380&p=ib_download_blocked&hl=en-GB&rd=1#zippy=%2Cmore-info-for-software-developers-and-website-owners
×
×
  • Create New...