Era Client remote installation

[amityservice 0]

Dear all

 

I just want to know that if we perform agent deploy task on client system then it require internet on client system or not

[MartinK 384]

Dear all

 

I just want to know that if we perform agent deploy task on client system then it require internet on client system or not

 

Yes, both deployment using "Remote deployment task" and using "Live installer" will attempt to download installation packages from ESET repositories through HTTP proxy (if configured so).

[amityservice 0]

ok thanks for information

 

But if there is any other way to install client without internet connection. or Live installer will attempt to download installation packages from local server.

[MartinK 384]

ok thanks for information

 

But if there is any other way to install client without internet connection. or Live installer will attempt to download installation packages from local server.

 

Live installer (for Windows) is technically a bat/vbscript script which downloads and runs installer with "bundled" parameters -> you may freely modify it to fit your needs (basic parameters as package URL or ERA connection parameters should be easily modifiable). Also there were multiple topics on this forum discussing specific scenarios.

[amityservice 0]

thanks for information

 

but i am ask about agent deploy task. i attach screen for this. for this task installer will attempt to download installation packages from local server?

 

Edited February 22, 2016 by amityservice

[jimwillsher 65]

Agent Installer is a batch file, You need to *somehow* get that batch file onto the client machine. If you want the agent insatller to download from a file share then you need to edit the file. For example:

 

change:

 

set url=hxxp://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.3.136.0/Agent_x64.msi
if defined IsArch_x86 (
  set url=hxxp://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.3.136.0/Agent_x86.msi
)

 

to

 

set url="C:\Temp\Agent_x64.msi"
if defined IsArch_x86 (
  set url="C:\Temp\Agent_x86.msi"
)

 

 

and change

 

echo.On Error Resume Next
echo.packageLocation = DownloadUsingHTTPProxy^("!url!", "!http_proxy_hostname!", "!http_proxy_port!", "!http_proxy_username!", "!http_proxy_password!"^)
echo.If packageLocation = "" Then
echo.    packageLocation = DownloadUsingHTTPProxy^("!url!", "", "", "", ""^)
echo.End If
echo.On Error GoTo 0
 

 

to

 

echo.On Error Resume Next
echo.packageLocation = !url!
echo.On Error GoTo 0

 

 

(there's probably other ways to achieve the same result).

 

 

Jim

[amityservice 0]

thanks for information jim

 

but i am asking about agent deploy task. i attach screen for this. for this task installer will attempt to download installation packages from local server?

 

Edited February 22, 2016 by amityservice

[jimwillsher 65]

No. it will download from ESET. UNLESS you change the batch file as I indicated. And yes, this is for deploying the agent but NOT the "agent deploy task" since that's active directory based.

[MartinK 384]

thanks for information jim

 

but i am asking about agent deploy task. i attach screen for this. for this task installer will attempt to download installation packages from local server?

 

task.png

 

Unfortunately remote deployment task will be downloading installer from ESET repositories and there is currently no way how to change it, especially in case Windows->Windows deployment is performed. Only options is using HTTP proxy - remote installed will use proxy parameters set in SERVER's configuration during task execution.

[amityservice 0]

thank eset staff

 

then it use internet by HTTP proxy in every agent deploy task or just one time?(once it download in first task on server HDD then use it )

[MartinK 384]

thank eset staff

 

then it use internet by HTTP proxy in every agent deploy task or just one time?(once it download in first task on server HDD then use it )

 

It will be downloaded on each client separately (= it is so called "pull" remote installation). In case HTTP proxy is properly configured and visible/accessible by client computers, installer file should be cached during first download and re-used for all others.

[MichalJ 434]

Maybe to ask another question, is there any specific use-case, where this scenario (caching of agent installers on Apache HTTP Proxy (or any proxy with enabled caching) is not optimal for your organization?

[rekun 43]

Maybe you can use this:hxxp://support.eset.com/kb3677/?locale=en_US&viewlocale=en_US

To store and install the agent from a local share