CraigB

Thanks MartinK The setting for the certificate in use by the server was exactly what was wrong. I updated the server certificate to the one I just created. Restarted the Remote Administrator Server service on the VM and logged in again. I can now create installers with the agent certificate required. Janoo - I wanted to create my own certs because the default certs are too open, I want to limit my certificates to the static IP and hostname of my server.

I am in the process of setting up a new remote administrator server. I currently have a linux server hosting version 6.4 of the Remote Administrator, but have had endless issues trying to upgrade it to 6.5 so I am setting up an Azure VM to host the windows version of Remote Administrator. I am aware that I cannot copy the database over directly, so I am attempting to replicate most of my setup manually. I have setup a certification authority. It is present, and the only one available. I have setup an agent and server ceriticate linked to the authority. At first I tried setting these up with the IP and FQDN of the server (I have done this on our current RA and it works). The certs all create and show as valid, but when I try and create an agent installer with the agent certificate I have created, I get an error message: Failed to get installers: Specified certification authority certificate was not found . I then created new certificates with the host *. These also do not allow me to create installers. I have seen a note on the ESET docs that some firewalls might block addresses in Slovakia, so I gave setup the US repository, and also tested a connection with the URL provided and I was able to connect to both the US and Slovakia repositories just fine. I've attached screenshots of my certification authorities and peer certificates. Can anyone suggest what might be missing?

Thanks Michael I was following the instructions here: hxxp://support.eset.com/kb3670/?intcmp="KBCJ_3668_Linuxupgrade" which states to stop the tomcat7 service. The first time I tried the upgrade, it is possible I did not wait long enough (perhaps put a warning in the instructions that a long wait is required for the database upgrade - when I could not access the system after the normal 10 minutes or so it takes from a restart, I assumed it had failed). I tried a second time after stopping all the services. I see now this is also incorrect. I am unclear on how I can add the server agent to the webconsole so I can target the server itself. Are there some instructions for this (for linux)?

Thanks I'd stopped both the ERAagent and ERAserver services, and the tomcat webserver before starting the upgrade, so I don't think so. Possibly did not wait long enough for those services to stop before running the upgrade though.

@wind-e Can you let me know if your upgrade is successful? I had the same error and had to roll our server back to a snapshot taken before the upgrade to get it back online. I left my upgrade running for over 2 hours, and it appeared to have hung, but maybe it was still running... Only have about 300 client computers connecting, but they are scattered across many networks. Haven't had a chance to re-run the update since.

This is unfortunate as my clients that are affected by this issue are using Office 365. I don't have control of the mail server, so cannot install ESET on it. I have temporarily disabled the email scanner, and for four days now, not a single conflict message has been created, whereas prior to that I was getting 1-2 conflict messages per email received, so ESET is definitely the cause. Is there any way to limit the email scanner to only scan specific folders? I could potentially configure each computer to only scan the email folders that are unique to it, so that multiple computers are not scanning the same folder.

Did you ever resolve this? I am having an issue where these tags are causing conflicts and multiple versions of each email. I am looking for a way to prevent these tags being applied to all messages, but have found nothing yet.

We have multiple users that using Outlook to access the same office 365 mailbox and are getting sync conflict issues and multiple copies of the each message. The ESET scanner is appending an X-esetid tag tothe header of every message as it scans, but we are getting conflict messages where multiple computers are receiving and scanning the same email and adding a different ID tag to the email header. When the message with the changed header is seen by the server, it is causing a conflict message because the emails are no longer identical between all of the computers. The exchange server is generating error logs like this 16:22:25 Compare property: 0x007D001F 16:22:25 Ignore property: 0x3FFA001F 16:22:25 Compare named property: EsetMessageFlag 16:22:25 Getting remote properties 16:22:25 Checking remote modifications 16:22:25 Compare (conflict) property: 0x007D001F 16:22:25 Not equal (conflict) property: 0x007D001F 16:22:25 Local modification: {00:21:51.0644 06/01/2017 [DD/MM/YYYY]} 16:22:25 Remote modification: {00:22:21.0081 06/01/2017 [DD/MM/YYYY]} 16:22:25 Conflict generated, remote item is winner And after one of the messages "wins" the other message gets moved to the Conflicts folder. The message in the inbox gets a warning notice that the user has modified another copy of the message and there is an option to view the other versions. I have done a text comparison between the conflicting message and headers and the ONLY difference between them is a tag in the header like this: X-EsetId: 37303A298C781C696C7C64 where each version of the message has a different tag number I have set the email policy 'alerts and notifications' option 'append tag messages to received and read email' and sent mail both to Never, but this has not changed the X-EsetId header tag behaviour. I need a way to stop ESET from appending this tag to the email header. I am running ESET Endpoint Antivirus 6.4.2014.0 and Remote Administrator 6.4.304.0