ShaneDT
-
Posts
236 -
Joined
-
Last visited
-
Days Won
3
Posts posted by ShaneDT
-
-
Hi Marcos, what ID are you referring to? I've included examples of the Modification Resolution email in Sync Issues above.
-
Marcos, all of my customers are Office 365. No one has there own Exchange server anymore. Therefore it's not possible to install ESET on the Exchange server.
I understand this is by design. But it's also a feature of the security policy that you can disable this 'tagging'. The problem is this doesn't work. And as per my other forum post, disabling the Outlook plugin is not an option. It's on of the key reasons I recommend, sell and support ESET. Even with Office 365, my customers regularly receive malicious emails that the ESET Outlook plug in detects. But having anywhere between 10 & 50% of your mailbox duplicated to conflicts as a result is unworkable.
This has been a known problem for SOOOO long. Why is it still not fixed?
-
OK just found this thread after more searching after starting my own post.
This is a massive problem that has been around for so long, WHY hasn't ESET fixed this years ago. There are settings in the client that should fix it but they don't work...
And to answer why most people don't notice this, because Outlook defaults to the Mail view which doesn't display the Sync Issues folders. Only if you switch to Folder view do you see these. So this can go on unnoticed until someone realizes their mailbox has grown to stupid levels and actually goes looking for it.
-
Also disabling the ESET Outlook add-in is not an option, this is one of the key reasons I use ESET.
Even with all my customers on Office 365, ESET regularly removes malicious emails.
-
Just found this post. I'm using EES 8.1, and it's still not fixed?
https://forum.eset.com/topic/26323-sync-issues-in-outlook-for-microsoft-365/
-
I'm aware this has been a problem for a while, and many years ago I configured the 'Web and email / Email client protection / Alerts and notifications / Append tag messages' options all to Never on my ESET Protect management servers for my own and all my customers.
However this has come to my attention again as I had a customer contact me yesterday with Outlook issues, and upon investigating I found their Exchange Online mailbox had grown to 90GB, with 38GB in the Sync Issues \ Conflicts folder.
The 'Append tag messages' for this customer is set to Never.
Yet it appears all of the conflicts are being caused by ESET. All of the Modification Resolution messages contain either of two common causes.
I also checked my own Conflicts folder and it has grown to 2.5GB (24GB mailbox).
So either this 'Append tag messages' set to Never is not working, or something else is causing this?
My ESET Protect servers are on v8.0.1238 and EES installed is the latest version 8.1.2031. Windows 10 is up to date as is Outlook the latest version via Office 365 subscription.
Examples of the two sync issue error wording below.
10:40:25 Compare named property: EsetMessageFlag
10:40:25 Compare named property: Emon Scanner Build
10:40:25 Compare named property: EsetAntispamMsgHeader
10:40:25 Getting remote properties
10:40:25 Checking remote modifications
10:40:25 Compare (conflict) property: 0x007D001F
10:40:25
10:40:25
10:40:25 Not equal (conflict) property: 0x007D001F
10:40:25 Local modification: {00:40:15.0411 10/08/2021 [DD/MM/YYYY]}
10:40:25 Remote modification: {00:40:15.0453 10/08/2021 [DD/MM/YYYY]}
10:40:26 Conflict generated, remote item is winner14:44:01 Overwrite named property: InTransitMessageCorrelator
14:44:01 Compare named property: Emon Scanner Build
14:44:01 Getting remote properties
14:44:01 Checking remote modifications
14:44:01 Compare (conflict) named property: Emon Scanner Build
14:44:01 Local: {I4:50051}
14:44:01 Remote: {Error (0x8004010F)}
14:44:01 Not equal (conflict) named property: Emon Scanner Build
14:44:01 Local modification: {04:44:00.0516 07/07/2021 [DD/MM/YYYY]}
14:44:01 Remote modification: {04:44:02.0246 07/07/2021 [DD/MM/YYYY]}
14:44:02 Conflict generated, remote item is winner -
Thanks Marcos.
Final question that hasn't yet been answered, and is potentially pretty critical.
If I upgrade the server to the latest version, will I have any issues if any of the client computers are still running an older version of the agent (all 7.0 or above, most are already 7.2)? Will they still connect OK?
-
Marcos, you're not reading my posts. I'm talking about upgrading the server!
Forget it, I'll email partner support...
-
Hi Marcos,
So you recommend go straight to the latest version using Client Task / SMC Components Upgrade? Just run it, let it finish and I guess restart the server? Nothing else to do?
Will I have any issues if any of the client computers are running an older version of the agent (all 7.0 or above, most are already 7.2)?
Do I also need to upgrade Apache or is this upgraded along with Components Upgrade?
If not is there documented process to upgrade Apache?
Are there any other components that need to be separately upgraded on the server?
-
1 hour ago, GregA said:
I have the latest ESET SMC server version and I see the same issue suddenly happening over the weekend. On the main computers screen it says "ESET Management Agent is outdated" on some computers but if I drill down to one of those computers from the dashboard and view it's installed applications, the ESET agent version (7.2.1266.0) says it is "Up-to-date version". So it seems to be a bug since one part of ESET says the agent it is up to date and another says it is out of date. I am going to call support later today to have them sort it out.
GregA so you have the latest version ESMC server and the latest version of the agent installed on your client computers and you're still getting the warning message?
Very strange. Marcos does ESET have any idea what is suddenly triggering this warning? Clearly it's not the server or agent version that is the problem. On my own server I have this warning appearing on maybe a third of my customer computers, regardless of what version agent is installed. And nothing changed on my server or customer computers that I'm aware of that could have triggered it. It appears to be affecting a random sample of client computers.
Anyway I do need to update the server so await your answers to my questions
-
Hi Marcos, no I'm asking about upgrading the server. Server is currently 7.0.553.
So you recommend go straight to the latest version using Client Task / SMC Components Upgrade? Just run it, let it finish and I guess restart the server? Nothing else to do?
Will I have any issues if any of the client computers are running an older version of the agent (all 7.0 or above, most are already 7.2)?
Do I also need to upgrade Apache or is this upgraded along with Components Upgrade?
If not is there documented process to upgrade Apache?
Are there any other components that need to be separately upgraded on the server?
Thanks.
-
Hi ESET support. Hope everyone is well.
I've started getting "ESET Management Agent is outdated" alerts on some computers this week even though the Agent on these computers is already v7.2 and most have been updated to the latest 7.2.1266. So I guess it's time to stop putting off upgrading the server.
Some questions. I'll create certificate and database backups first.
Are there any known issues with upgrading from 7.0.553.0 to 7.2.11.1?
Should I use the Help / Update Product method or Client Task / SMC Components Upgrade or manually download the latest ESMC and do a manual upgrade?
Which is the simplest and less likely option to cause issues?
Should I upgrade to 7.0.557.0 first (the latest 7.0 build)?Do I need to update the agent on all the client computers first?
Most are already 7.2 but some are 7.1 and possibly 7.0. These are customer computers so could take weeks to organise with the customers to get these all updated (don't ask...).The server is Windows Server 2012 R2 with all the latest updates installed.
Thanks.
-
7 minutes ago, MichalJ said:
Hi @ShaneDT Indeed, you are right, and I can assure you, that enabling automatic product updates, for both the endpoint clients, and the management environment (both cloud / on premise) is our uppermost priority.
👍
-
5 minutes ago, Marcos said:
We haven't released automatic program updates for Endpoint yet; ESMC 7.2 will be a prerequisite.
Yep, but the option is and has been there in the policy settings since I've been selling ESET (circa v6). If the option doesn't work it shouldn't be there, but it really is an option that we need. Every other vendor has had automatic program updates for aeons.
-
Campbell IT I don't know that you're understanding what your problem is. If your computers are upgraded to 7.3, they are not shutting down due to upgrading, they are shutting down due to a bug in this version that triggers a shut down after a scheduled scan. You need to go into your policy settings and turn off the scheduled scans.
And as far as I'm aware the 'Program Update' policy does not and has never worked? I've never been able to get any of my endpoints to automatically update the EES software. Always have to deploy it manually from the server.
-
Same issue with some but not all computers upgraded to 7.3.2032 with scheduled scans configured via policy in ESMC.
Have had a mad scramble the last few days to get all computers on 7.3 due to the W10 2004 blue screen issues...
-
Should I enter it with the quotations? So;
"/"
Cheers.
-
What do you enter for Mac computers in the 'Scan Targets / Edit Rule' option when configuring scheduled scans in ESMC policies for Mac's?
ESMC policy requires you to enter values. And it won't allow you to complete the scheduled task without entering a value.
I want to configure daily In Depth scheduled scans to scan the entire computer.
The equivalent Windows policy simply has a check box 'Scan all Targets'.
Thanks.
-
Sorry Peter but it's 12:30am here and I don't wish to spend hours of my time providing logs for what is a known problem!
The amount of time I've wasted troubleshooting vendor problems this week is ridiculous!!
I've manually installed the agent using the server assist option and installed EES using the direct download link. PITA but at least I can call it a night.
-
This has been a known issue for months. Please someone at ESET just fix it. Several hours wasted again.
-
Yes set to autoselect no issues with firewall. Can access repository just fine.
Quite simply the servers are just tooooooooo slow!
-
Seems we are having repository issues in Australia again re the following thread. I've been trying to deploy ERA Agent to new computers on a customers network for most of the night. Continually fails to start and times out in ERA Server Task. So created installer .bat file. Running this worked on one computer but times out on others. Can confirm access to the repository website from both server and clients. Can even trigger downloaded of the msi file from the repository, gets to about 6% downloaded and then just hangs!
Can ESET please fix this! It's really annoying trying to sell and support your product when we're regularly having these issues!
-
So after leaving it for about an hour I did a restart of the mac and the install kicked off straight away after the computer restarted.
So no idea why it needed the restart to kick it off. I was connected to the MacBook via TeamViewer to monitor the install, but I can't imagine that was blocking it.
I reconnected via TeamViewer after the restart, luckily as the install prompted to allow access to System Preferences and the hard drive for scanning. Is there any way to script this into the Client Task install so these are set automatically? Makes remote deployment a lot more complicated than with Windows.
-
I can't seem to find any info on this and it doesn't seem to want to work.
ERA server is version 6.5.522.
Mac notebook is version macOS Mojave 10.14.1.
The ERA Agent has been installed and is reporting back to the ERA server as expected.
I've created a Client Task to install EES v6.7.500.0 but it's not doing anything. It's not running, hasn't failed. Just doesn't appear to have started. Trigger is set to As soon as possible.
Help please
EES and duplicated emails in Outlook Conflicts folder
in ESET Endpoint Products
Posted
Marcos, am I going to have to do that on every single one of my customers computers? That's hundreds of computers Marcos! And from Craig's post, that xml file doesn't work anyway!?