Another way deployment agent and endpoint together

[mahiralkhoir 4]

Because remote installation always failed for unknown reason. So I've decide deployment using *.bat ( Agent Live Installer ). Unfortunately, it's deploy agent only. I know, if agent installed successfully, you can push install endpoint from ERA and its easy. But, when push installation failed, error information its very simple.

 

 

Look at that picture ? How can i see error log or any information ?

Maybe some one can helping me, for get more information if push installation endpoint failed ?

 

ESET describe many ways for installation, but our client doesn't have active directory for deployment via GPO or SCCM. So, i am decide make some script for manual deployment, i think its much easier than using
AgentLiveInstaller.bat generated from ERA Server. This script contains 2 file agentcfg.ini and executable file.

[Config]
EndpointURL_32bit="hxxp://192.168.186.1/ENDPOINT/v6/eea_nt32_enu.msi"
EndpointURL_64bit="hxxp://192.168.186.1/ENDPOINT/v6/eea_nt64_enu.msi"
AgentURL_32bit="hxxp://192.168.186.1/ERA/Standalone/Agent/Windows/Agent-6.1.444.0_x86.msi"
AgentURL_64bit="hxxp://192.168.186.1/ERA/Standalone/Agent/Windows/Agent-6.1.444.0_x64.msi"
HostnameServer="192.168.186.1"
ERAPort="2222"
AgentCert="Your BaseCode64 Agent Certificate"
CACert="Your BaseCode64 Authority Certificate"

Edit and change according to your server configuration.

 

 

Maybe this trick can helping sysadmin for deployment ESET more easier.

 

Notes : you must compile using autoit for get executable file

sourcecode.zip

Edited June 10, 2015 by mahiralkhoir

[ElJuan 2]

Thanks for share,

I had to find another way to deploy instead of ERAS console too.

I just create an exe file with winrar and put inside an small script with the following instructions:

start /wait " " msiexec /i \\fileserver\sharename\agent.msi /qn TRANSFORMS=\\fileserver\sharename\agent.mst /li c:\agent.log

start /wait " " msiexec /i \\fileserver\sharename\endpoint.msi /qn /li c:\endpoint.log

Now you can deploy the exe (or the batch file) with pstools.

I have made successfully deployments with tools like: pstools, Active Directory-GPolicy and Lansweeper.

Note. In the ERAS guide you can find how to create the transform file.

Hope this can help.

Edited June 17, 2015 by ElJuan

[mahiralkhoir 4]

I know you can create MST transform and deploy through GPO or SCCM.

But if you dont have network with AD it can some trouble,

Anyway deployment with pstools its a good idea, thanks !

But, i missed offline package installation from ERA 5

 

 

 

This script contains 2 file agentcfg.ini and executable file.

[Config]
EndpointURL_32bit="hxxp://192.168.186.1/ENDPOINT/v6/eea_nt32_enu.msi"
EndpointURL_64bit="hxxp://192.168.186.1/ENDPOINT/v6/eea_nt64_enu.msi"
AgentURL_32bit="hxxp://192.168.186.1/ERA/Standalone/Agent/Windows/Agent-6.1.444.0_x86.msi"
AgentURL_64bit="hxxp://192.168.186.1/ERA/Standalone/Agent/Windows/Agent-6.1.444.0_x64.msi"
HostnameServer="192.168.186.1"
ERAPort="2222"
AgentCert="Your BaseCode64 Agent Certificate"
CACert="Your BaseCode64 Authority Certificate"

Edit and change according to your server configuration.

 

v6-einstaller.png

 

Maybe this trick can helping sysadmin for deployment ESET more easier.

 

Notes : you must compile using autoit for get executable file

 

Edited June 19, 2015 by mahiralkhoir

[macros 1]

that's great. this is what we need t deploy endpoint since using deployment from era never work!

[ElJuan 2]

 

I know you can create MST transform and deploy through GPO or SCCM.

But if you dont have network with AD it can some trouble,

Anyway deployment with pstools its a good idea, thanks !

But, i missed offline package installation from ERA 5

 

 

 

This script contains 2 file agentcfg.ini and executable file.

[Config]
EndpointURL_32bit="hxxp://192.168.186.1/ENDPOINT/v6/eea_nt32_enu.msi"
EndpointURL_64bit="hxxp://192.168.186.1/ENDPOINT/v6/eea_nt64_enu.msi"
AgentURL_32bit="hxxp://192.168.186.1/ERA/Standalone/Agent/Windows/Agent-6.1.444.0_x86.msi"
AgentURL_64bit="hxxp://192.168.186.1/ERA/Standalone/Agent/Windows/Agent-6.1.444.0_x64.msi"
HostnameServer="192.168.186.1"
ERAPort="2222"
AgentCert="Your BaseCode64 Agent Certificate"
CACert="Your BaseCode64 Authority Certificate"

Edit and change according to your server configuration.

 

v6-einstaller.png

 

Maybe this trick can helping sysadmin for deployment ESET more easier.

 

Notes : you must compile using autoit for get executable file

 

hello

it is not necessary AD for use Transform file and deploy.

 

and thanks for sharing your scripts