DumitruSino

@Marcos, if you've read the TOPIC, and if you've read what people mentioned. This issue popped up AFTER THE UPDATE! So please dig in your update, and find the issue. You don't need our logs for that.

Same problem here! After the update! @ESET, please fix this. I think you've could easily prevent this, if you would've TEST THE UPDATE BEFORE RELEASE! Poor testing! Please blame it on your PRODUCTION and TESTING TEAM, not on us clients! UNPROFESSIONAL!

A very good feature I saw on LOCAL ESET PROTECT SERVER, where YOU HAVE A CHOISE to select WHAT WILL HAPPEN to Computer that were FOUND in AD, even if they were removed before from ESET LOCAL SERVER. Why it was useful ? +Easy to find a missing computer +It would add computer to ITS CORRECT AD GROUP folder + AUTOMATION, you could chose what to do with it. ESET CLOUD PROTECT DOESNT HAVE THIS OPTION: Disadvantages: - ADScanner will miss removed computers, and you don't have any options, they will never be added back. - Computers once removed, cannot be added back to where they BELONG, ITS IMPOSSIBLE TO AUTOMATE. - You have to INSTALL agent on an OLD REMOVED COMPUTER so it WILL RE-APPEAR AGAIN in ESET PROTECT CLOUD. - Even if you install AGENT on OLD Removed Computer, it will appear NOT UNDER ITS GROUP IN AD, but under: a standard Dynamic Group (Windows Computers) -> (No manageable security product). - Next, you have to go in your AD, find that computer where it belongs to, and MANUALLY MOVE IT TO CORRECT GROUP. Please do something about this, as its annoying and hurts our business, as we have many old, and many new computers and changes. We don't have time to manually do this. Thank you!

Tried using: C:\it-tools\eset\Agent_x64.msi /q /L*V "C:\it-tools\eset\logs.log" and SUCCESS! Apparently the CERTIFICATE was the problem! Weird that I chatted with couple ESET Support guys, and nobody had this idea to remove the certificate.

Tried using: C:\it-tools\eset\Agent_x64.msi /q /L*V "C:\it-tools\eset\logs.log" and SUCCESS! Apparently the CERTIFICATE was the problem! Weird that I chatted with couple ESET Support guys, and nobody had this idea to remove the certificate. Last authentication 2021-May-10 19:43:35 Enrollment OK Last replication 2021-May-10 19:43:43 OK Last successful replication 2021-May-10 19:43:43 OK Successful replications: 3 All replication attempts: 3 Connection: xxxxxxxxxx.a.ecaserver.eset.com:443 Scenario: REGULAR Peer certificate 2021-May-10 19:41:03 OK Agent peer certificate with subject 'xxxxxxxxxxxxxxxxxxxxxministrator External CA' with serial number 'xxxxxxx4' is and will be valid in 30 days Policies 2021-May-10 19:41:03 Applied policies: Hidden: Agent defaults VNC Allow Disable Windows Updates Notifications Enable Secure Browser Product 2021-May-10 19:41:01 Product install configuration: Product type: Agent Product version: 8.0.1238.0 Product locale: en_US Thank you!

Installed using: C:\it-tools\eset\Agent_x64.msi /q P_CERT_PATH=C:\it-tools\eset\certificate.txt P_CERT_AUTH_PATH=C:\it-tools\eset\ca.txt P_LOAD_CERTS_FROM_FILE_AS_BASE64=YES /L*V "C:\it-tools\eset\logs.log" Here is what I got: Last authentication 2021-May-10 19:32:28 Enrollment failed with error: Request: Era.Common.Services.Authentication.RPCEnrollmentRequest on connection: host: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message: Connect Failed, and error details: Last replication 2021-May-10 19:32:28 ERROR: InitializeConnection: Initiating replication connection to 'host: "xxxxxxxxxxxxxxxxxxxxxxxxx.a.ecaserver.eset.com" port: 443' failed with: GetAuthenticationSessionToken: Failed to fetch device session token in time Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: 2alxfromorhuzkixxiws7uwxzq.a.ecaserver.eset.com:443, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 00000000-0000-0000-0000-000000000000, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] All replication attempts: 2 See trace log attached. trace.log

With LOCAL ESET SERVER I was installing Agents with following command and files: C:\it-tools\eset\Agent_x64.msi /q P_HOSTNAME=199.164.42.68 P_ENABLE_TELEMETRY=1 P_CERT_PATH=C:\it-tools\eset\certificate.txt P_CERT_AUTH_PATH=C:\it-tools\eset\ca.txt P_LOAD_CERTS_FROM_FILE_AS_BASE64=YES /L*V "C:\it-tools\eset\logs.log agent_x64.msi ca.txt certificate.txt install_config.ini All worked really nice for all our 60 workstations. NOW I MIGRATED TO CLOUD and I use following: C:\it-tools\eset\Agent_x64.msi /q P_ENABLE_TELEMETRY=1 P_HOSTNAME={server name from install_config.ini from protect.eset.com} P_PORT=443 P_CERT_PATH=C:\it-tools\eset\certificate.txt P_CERT_AUTH_PATH=C:\it-tools\eset\ca.txt P_LOAD_CERTS_FROM_FILE_AS_BASE64=YES /L*V "C:\it-tools\eset\logs.log" agent_x64.msi - new file downloaded from Configuration GPO/SCCM scrip from hxxp://protect.eset.com/ ca.txt - same old file certificate.txt - same old file install_config.ini - new file downloaded from Configuration GPO/SCCM scrip from hxxp://protect.eset.com/ I installed it multiple times, on different workstations. Here are the logs: Status log Scope Time Text Configuration 2021-May-08 23:01:00 Product configuration: Use of HTTP proxy for ESET services is disabled Use of HTTP proxy for replication is disabled Repository hostname is: AUTOSELECT Update server is set to: AUTOSELECT with "regular" update type Dynamic groups 2021-May-10 14:47:32 Device is not member of any dynamic group Last authentication 2021-May-10 17:04:58 Enrollment failed with error: Request: Era.Common.Services.Authentication.RPCEnrollmentRequest on connection: host: "*****************.a.ecaserver.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message: Connect Failed, and error details: Last replication 2021-May-10 17:04:52 ERROR: InitializeConnection: Initiating replication connection to 'host: "****************.eset.com" port: 443' failed with: GetAuthenticationSessionToken: Failed to fetch device session token in time Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: ****************.a.ecaserver.eset.com:443, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 00000000-0000-0000-0000-000000000000, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] All replication attempts: 848 Peer certificate 2021-May-10 00:37:44 OK Agent peer certificate with subject 'C******************************************************************* Policies 2021-May-08 23:01:00 Device has no policies assigned Product 2021-May-08 23:00:58 Product install configuration: Product type: Agent Product version: 8.0.1238.0 Product locale: en_US Replication security 2021-May-10 17:04:58 OK Remote host: **************************.a.ecaserver.eset.com Remote product: Server Remote certificate: Subject='**************** ', NotBefore=2019-Sep-04 00:00:00, NotAfter:2021-Oct-03 12:00:00, ************************ Performance Indicator Value Up time 42:04:00 Memory private usage 25 MB Available physical memory 8792 MB Generated at 2021-May-10 17:04:58 (2021-May-10 12:04:58 local time) ANY HELP WOULD BE APPRECIATED! THANK YOU!

WORKSTATIONS

With LOCAL ESET SERVER I was installing Agents with following command and files: C:\it-tools\eset\Agent_x64.msi /q P_HOSTNAME=199.164.42.68 P_ENABLE_TELEMETRY=1 P_CERT_PATH=C:\it-tools\eset\certificate.txt P_CERT_AUTH_PATH=C:\it-tools\eset\ca.txt P_LOAD_CERTS_FROM_FILE_AS_BASE64=YES /L*V "C:\it-tools\eset\logs.log agent_x64.msi ca.txt certificate.txt install_config.ini All worked really nice for all our 60 workstations. NOW I MIGRATED TO CLOUD and I use following: C:\it-tools\eset\Agent_x64.msi /q P_ENABLE_TELEMETRY=1 P_HOSTNAME={server name from install_config.ini from protect.eset.com} P_PORT=443 P_CERT_PATH=C:\it-tools\eset\certificate.txt P_CERT_AUTH_PATH=C:\it-tools\eset\ca.txt P_LOAD_CERTS_FROM_FILE_AS_BASE64=YES /L*V "C:\it-tools\eset\logs.log" agent_x64.msi - new file downloaded from Configuration GPO/SCCM scrip from hxxp://protect.eset.com/ ca.txt - same old file certificate.txt - same old file install_config.ini - new file downloaded from Configuration GPO/SCCM scrip from hxxp://protect.eset.com/ I installed it multiple times, on different workstations. Here are the logs: Status log Scope Time Text Configuration 2021-May-08 23:01:00 Product configuration: Use of HTTP proxy for ESET services is disabled Use of HTTP proxy for replication is disabled Repository hostname is: AUTOSELECT Update server is set to: AUTOSELECT with "regular" update type Dynamic groups 2021-May-10 14:47:32 Device is not member of any dynamic group Last authentication 2021-May-10 17:04:58 Enrollment failed with error: Request: Era.Common.Services.Authentication.RPCEnrollmentRequest on connection: host: "*****************.a.ecaserver.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message: Connect Failed, and error details: Last replication 2021-May-10 17:04:52 ERROR: InitializeConnection: Initiating replication connection to 'host: "****************.eset.com" port: 443' failed with: GetAuthenticationSessionToken: Failed to fetch device session token in time Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: ****************.a.ecaserver.eset.com:443, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 00000000-0000-0000-0000-000000000000, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] All replication attempts: 848 Peer certificate 2021-May-10 00:37:44 OK Agent peer certificate with subject 'C******************************************************************* Policies 2021-May-08 23:01:00 Device has no policies assigned Product 2021-May-08 23:00:58 Product install configuration: Product type: Agent Product version: 8.0.1238.0 Product locale: en_US Replication security 2021-May-10 17:04:58 OK Remote host: **************************.a.ecaserver.eset.com Remote product: Server Remote certificate: Subject='**************** ', NotBefore=2019-Sep-04 00:00:00, NotAfter:2021-Oct-03 12:00:00, ************************ Performance Indicator Value Up time 42:04:00 Memory private usage 25 MB Available physical memory 8792 MB Generated at 2021-May-10 17:04:58 (2021-May-10 12:04:58 local time) ANY HELP WOULD BE APPRECIATED! THANK YOU!

TASK to MERGE DUPLICATES Hello, dealing with DUPLICATES is ANNOYING, support could not help me to automate removal of duplicates. Could we please get a TASK to MERGE Dupliates? Thank you!