Petr Mrazek 4 Posted September 13, 2023 Posted September 13, 2023 Hi, we've got a problem with upgrading / installing the new version of ESET Management Agent 10.1.1292.0. When we try to update it from the ESET Protect console, the task finishes successfully, but the Management Agent is not upgraded. When we try it manually - installtor end with error - 1603. Log is attached. ra-agent-install.log
Administrators Marcos 5,468 Posted September 14, 2023 Administrators Posted September 14, 2023 It appears that agent is password protected and an invalid password was used: ERROR: (CheckAgentSetupPasswordWin) CConfigEngineModuleWrapper::VerifyPassword failed with error: Password does not match
Most Valued Members ewong 8 Posted September 15, 2023 Most Valued Members Posted September 15, 2023 Unless you've found the password, my solution is to run ESETUninstaller to get rid of the old agent.
Solution Petr Mrazek 4 Posted September 15, 2023 Author Solution Posted September 15, 2023 It wasn't problem with password. The problem was cache on ESET Bridge server. Deleted, restarted and now everything works. 👍 Andreas H., Peter Randziak and Cramaboule 3
Andreas H. 1 Posted September 19, 2023 Posted September 19, 2023 Thanks for the Solution! https://help.eset.com/ebe/2/en-US/troubleshooting.html Cramaboule 1
labynko 5 Posted September 21, 2023 Posted September 21, 2023 Starting from version 10.1.1288.0, agent updates are only possible after password protection is disabled. Is this a new policy? If, when upgrading to version 10.1.1288.0, this can still be explained, but the upgrade from version 10.1.1288.0 to 10.1.1292.0 is not performed without disabling password protection! The update occurs via the command line: msiexec /i hxxp://192.168.0.1:3128/ema/ema_10.1.1292.0_x64.msi /q P_HOSTNAME=192.168.0.1 P_ENABLE_TELEMETRY=0 P_CERT_CONTENT=... P_CERT_AUTH_CONTENT=...
ESET Staff MartinK 384 Posted September 21, 2023 ESET Staff Posted September 21, 2023 I would recommend to contact support in this case. In your case, you are performing upgrade with modification of configuration and thus I would expect password to be required so that crucial configuration is actually protected. But regardless of that, seems that this change is not properly documented, as there is possibility to enter password as part of the command line (or as part of install_config.ini property file used by installer), which would resolve this issue.
Recommended Posts