Dear Marcos
I want to ask one thing, our users want to migrate from Eset Security Management Console to the latest Eset protect console, and also migrate eset endpoint antivirus products to eset endpoint security, for the Eset Protect Console setup has been completed as info our users have 30 thousand endpoints that have eset endpoint antivirus installed, we have problems when migrating endpoint antivirus products to endpoint security products there is a failure with code 1603, is there a way to migrate endpoint antivirus products to endpoint security without having to uninstall existing endpoint products first?
I think maybe if I use the install from the eset web I'm sure it will work, but our users are planning to migrate from Eset ESMC to Eset protect, so I think we should use an all in one install, so that if the install is successful, endpoint security or eset management agent is connected directly to the new eset portect.
Dear marcos
I think the error 1603 is due to the computer I tested already installed eset management agent version 7.2 and endpoint antivirus version 9.1 so if the computer I tested uninstalled the existing eset, of course using all in one installation works but as I said before we have 30 thousand existing endpoints so if the method must uninstall the existing eset first it is time consuming is there a more relevant solution?
It appears to me that you have some tasks set up in ESET PROTECT that continually push installation of ESET Endpoint Antivirus. Please check it out. Also make sure to install Endpoint v10.1 or at least v10.0 instead of v9.1.
Dear marcos
Let me explain again, I want to migrate ESMC to Eset Protect and also migrate Eset Endpoint antivirus products to Eset Endpoint Security, I have finished setting up Eset Protect, to migrate eset endpoint antivirus to eset endpoint security we use third party tools, namely kaseya dekstop management, we use a virtual computer as a test with the following steps:
first we run the all in one Eset endpoint antivirus installation (endpoint version 9.1 agent 7.2) on the virtual machine computer using the kaseya dekstop management procedure after the eset endpoint antivirus has finished installing and updating then we run the procedure to install all in one endpoint security (endpoint security version 10.1 and Agent version 10.1) all procedures that are run through kaseya are successful, but after we check on the virtual machine computer it is still installed eset endpoint antivirus, but in windows security it reads eset endpoint security.
Please note that you are using an all-in-one installer labeled "ESET Package Installer". What I asked is if you can install ESET Endpoint Security using the installer from the web which looks differently as follows:
As for upgrading ESMC to ESET PROTECT, let's not mix it with the issue about upgrading ESET Endpoint Antivirus to ESET Endpoint Security but rather discuss it in a new topic. Anyways. for instructions how to do the upgrade please refer to _install/10.1/en-US/upgrade_procedures.html.
i had the same problem, but this problem hit to me on esmc version 7.x and i upgraded to version 8.1, this problem can be solved, i don't know this problem can happen again on new version, i will think twice about upgrading eset my current protection
i have got same issue, eset block another website and get issue ssl revoke, i try exclude this website include the certificate, clear cache browser, this method not effect on me, this website stay block with ssl revoke issue.
is there currently a problem with one of the link ip epns.eset.com ?
is this the cause to appear status epns cannot reached
at the same time I will also try to contact my internet service provider, to get any clue for this issue
i get this issue after upgrade v9 endpoint security
Thank you.
I tried it without proxy and via proxy without user authentication, this status keep stay on my endpoint
oh sorry im not tell information os
for client i use Windows 10, and another version windows like 7 sp1 dan windows 8
and EP for server i use Linux Centos 7 (VA), i think for proxy no issue
because the VA eset has been configured properly for EPNS connection and another ESET connection
and have been using it so far no problems, i check on log.
but i found on my ping and telnet to port 8883 443 epns eset has dificult to connect (cannot stable connection) on my pc client and server.
my question
is this the cause a notification show up, because epns cannot stable to connect on location my network ?
or problem on new endpoint v9 ?
i got this issue after v9, and never happened in the previous version
and Send Wake-Up call on my management stil use properly
I'm confused why the notification can appear on endpoint if the EPNS link can be connected and another related feature is running properly.
If you do not use the proxy try to switch to pre-release updates, confirm that LiveGrid communication module bas been upgraded to version 1123.1 and let us know if it resolved your issue, even if you have License Interval Check set to limited.
c80f0f1006