Migration ESET Remote Administrator to ESET CLoud Administrator

[axlgabo10 0]

Hi.
We are going to make the migration from eset remote administrator to eset cloud administrator. I have some doubts.
1. Can an all-in-one installer be generated from eca but be offline? that is, do not make an Internet request during the process? since there are 240 teams and they are going to consume a lot of bandwidth
2. Can I install 2 http proxies in 2 different branches for downloading updates?

I appreciate your help

[MichalJ 434]

Hello @axlgabo10

1. You can use the offline cache option that is described here. https://help.eset.com/epi/2/en-US/eca_win.html  By default the All In One installer package is downloading the Agent / Endpoint from ESET repository, but the offline cache should resolve this issue for you. 
2. Yes, but you will have to set those properly in your policies - different proxy setting for agent & endpoints, meaning 4 policies in total. But amount of apache proxies is not limited. 

Out of curiosity, what is your primary reason for migration from the on premise remote administrator? Also, were you running V5 or V6? 

[axlgabo10 0]

thanks MichalJ
The client does not have enough infrastructure to continue maintaining the local console, since it works under version 6 appliance in ova. One of the common problems was that every time he had power outages, the console and the database of the appliance were damaged, he even thought about changing the product

3 minutes ago, MichalJ said:

Hola @ axlgabo10

1. Puede utilizar la opción de caché sin conexión que se describe aquí. https://help.eset.com/epi/2/en-US/eca_win.html   De forma predeterminada, el paquete del instalador All In One está descargando el agente / punto final desde el repositorio de ESET, pero la memoria caché sin conexión debería resolver este problema por usted. 
2. Sí, pero tendrá que establecerlos correctamente en sus políticas: una configuración de proxy diferente para el agente y los puntos finales, lo que significa un total de 4 políticas. Pero la cantidad de proxies apache no está limitada. 

Por curiosidad, ¿cuál es el motivo principal de su migración desde el administrador remoto local? Además, estabas ejecutando V5 o V6? 

 

[axlgabo10 0]

2 hours ago, MichalJ said:

Hello @axlgabo10

1. You can use the offline cache option that is described here. https://help.eset.com/epi/2/en-US/eca_win.html  By default the All In One installer package is downloading the Agent / Endpoint from ESET repository, but the offline cache should resolve this issue for you. 
2. Yes, but you will have to set those properly in your policies - different proxy setting for agent & endpoints, meaning 4 policies in total. But amount of apache proxies is not limited. 

Out of curiosity, what is your primary reason for migration from the on premise remote administrator? Also, were you running V5 or V6? 

Hello MichalJ.
Can I bother you with another doubt?
Once I download the offline .dat package, can I do the deployment with the deployment tool just offline? that is, if I save the .dat next to the .exe package and execute the installation with the deploy, the request will be made to the internet or it will be locally with the .dat created

[MichalJ 434]

@axlgabo10 Hello, no problem. Although I am not an expert in this offline installer method, based on what´s written in the KB article, it should work exactly like that. Meaning, if you have the installer and the dat file in the same folder, it should download / distribute the installers from the offline cache, instead of contacting the ESET repository servers. This is listed in the documentation:  Keep in mind that the .dat file must be in the same folder as the installer .exe file in order to work. The next time the installer is executed it will use the .dat file instead of the online repository. This scenario is recommended for situations when the installer is executed on each new computer from a shared disk

 

[MartinK 378]

1 hour ago, axlgabo10 said:

Once I download the offline .dat package, can I do the deployment with the deployment tool just offline? that is, if I save the .dat next to the .exe package and execute the installation with the deploy, the request will be made to the internet or it will be locally with the .dat created

Even with .dat file prepared side-by-side to installer I think there will be still call to internet, but just to download metadata for installer, required to connecto to ECA. All product installers (MSI files) should be extracted from provided cache file, which is supposed to reduce overall download.

[axlgabo10 0]

5 minutes ago, MartinK said:

Incluso con el archivo .dat preparado lado a lado para el instalador, creo que todavía habrá llamadas a Internet, pero solo para descargar los metadatos del instalador, necesarios para conectarse a ECA. Todos los instaladores de productos (archivos MSI) deben extraerse del archivo de caché proporcionado, lo que se supone que reduce la descarga general.

I understand, but with the deploy tool if I can perform this process? or only locally on each computer

[MartinK 378]

18 hours ago, axlgabo10 said:

I understand, but with the deploy tool if I can perform this process? or only locally on each computer

Remote deployment tool is supported, it should detect .dat file and use it to deploy also on remote clients, but make sure you are using latest version of deployment tool.

[axlgabo10 0]

1 minute ago, MartinK said:

La herramienta de implementación remota es compatible, debería detectar el archivo .dat y usarlo para implementar también en clientes remotos, pero asegúrese de estar usando la última versión de la herramienta de implementación.

Great. In a few hours I will make the migration and I will tell you how it was. Thank you