Megachip 5 Posted March 28, 2014 Posted March 28, 2014 (edited) Try to update von 2225 to 2228. Not possible And what means: Support for Windows 8.1 Update 1 Did 2225 not working within 8.1U1? Edited March 28, 2014 by Megachip
WilliamT 21 Posted March 31, 2014 Posted March 31, 2014 Hello MegaChip, If you are having issues with the upgrade. Please uninstall the current version and install the latest. Below are some links to assist you. hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2289 hxxp://www.eset.com/us/download/business/
Megachip 5 Posted April 3, 2014 Author Posted April 3, 2014 Thx, but if I remote uninstall eset, am I able to reinstall (do not having root credentials)
Bart 4 Posted April 9, 2014 Posted April 9, 2014 add to installation package commands: IGNORE_CONFLICTS=1 and than try again
Arakasi 549 Posted April 9, 2014 Posted April 9, 2014 add to installation package commands: IGNORE_CONFLICTS=1 and than try again Hi Bart, That switch isn't really a public switch, and can cause further problems if not used properly. I'm not sure if it should be used here and would wait for staff to determine if it's ok or not in this scenario.
Megachip 5 Posted September 10, 2015 Author Posted September 10, 2015 So, since 2008 it is mostly impossible to do minor upgrades of ERA/ESS without loosing the configuration (remove ESET (or the registry key) and reinstall). Any official solution for that? Trying to upgrade 2242 to 2254 and running into the same issue. Why minor upgrades (of the same language, upgrading from german to english works fine) are blocked? Or is 2242 fine on Windows 10? THX a lot, Best, Meg
ESET Moderators TomasP 318 Posted September 10, 2015 ESET Moderators Posted September 10, 2015 I am not aware it would not be possible to perform incremental upgrades, millions of users perform them without any issues, so in your case it may be something specific. I'd advise to submit a request via the in-product support form and our support team will investigate the cause of the installation/upgrade issue on your computer.
Megachip 5 Posted January 11, 2016 Author Posted January 11, 2016 (edited) Sometimes, upgrades will not work and the ESET Remote Installer stops with this error message. What params will ERI check to determine if a package is already installed? Only the Packagename from Registry Key or some other params like version? If there is a minor version upgrade, I only replace the msi within the ERAS (not changing the package name). BTW, the safe mode uninstall tool seems not removing these entries :/ P.S. Topic allready exist, but search board search did not found it: https://forum.eset.com/topic/2161-a-package-with-the-same-name-has-already-been-installed-on-this-computer/ Could be merged, if possible. Edited January 11, 2016 by Megachip
Megachip 5 Posted January 11, 2016 Author Posted January 11, 2016 Prevention of repeat installationsImmediately after the remote installation process is complete, the remote client is marked with a flag prohibiting repeated installations of the same installation package. If the Type and Name of the package defined in the einstaller.exe agent match the data in the registry, the installation will not be performed. The flag is written to the following registry key: HKEY_LOCAL_MACHINE\Software\ESET\ESET Remote Installer So should I create for every minor update a new upgrade package? The last 6 Years I've simply replaced the msi files and only created new packages on major version upgrades. But problem only occurs sporadic and not on every client/upgrade ... :/
Megachip 5 Posted April 14, 2016 Author Posted April 14, 2016 Suggestions? Same for 2242.2 -> 2260.1. Except removing registry key before every update or creating new package in era every new update.
Administrators Marcos 5,408 Posted April 14, 2016 Administrators Posted April 14, 2016 Suggestions? Same for 2242.2 -> 2260.1. Except removing registry key before every update or creating new package in era every new update. Note that Endpoint 5.0.2260 cannot be installed using an Upgrade client task due to a new signature in the msi installer. It should be possible to deploy it via a push install, however. Could you post a screen shot of the message you're getting when attempting to push v5.0.2260 on clients?
Megachip 5 Posted April 18, 2016 Author Posted April 18, 2016 Note that Endpoint 5.0.2260 cannot be installed using an Upgrade client task due to a new signature in the msi installer. It should be possible to deploy it via a push install, however. Could you post a screen shot of the message you're getting when attempting to push v5.0.2260 on clients? PUSH installation is not possible. The upgrade procedure is providing the user the "remote installer" (300K) which is started by user manually. The installation mostly failed with this error line: "Status 2902, ID 103: A package with the same name has already been installed on this computer." This isn't a problem of ??? -> 5.0.2260. I think the problem is, that the eri only checks package name, not package version
Recommended Posts