Jump to content

Update Agent 6.3 - 6.4 Automatically - Locally


jdashn
 Share

Recommended Posts

Good Morning/Afternoon/Evening;

 

We currently have about 2k computers connecting up to Eset RA, they are a mix of win7,8 32&64bit, desktops, laptops and tablets. We would like for our clients to download the Agent files from the local network, instead of from ESETs servers. I have followed the instructions provided:

 

hxxp://help.eset.com/era_admin/64/en-US/index.html?agent_live_installer.htm

 

These instructions are wrong and the screenshots to not seem to reflect the same bat file that is generated in v 6.4-- Spesifically this line from the instructions:

 

echo.

eho.dim params: params = "/qr /i " ^& packageLocation ^& " /l*v %temp%\ra-agent-install.log" ^&_

 

appears like this in my unmodified batch file:

 

echo.
echo.Dim params: params = "/qr /i """ ^& packageLocation ^& """ /l*v ""%temp%\ra-agent-install.log""" ^&_

 

 

Please note the extra "s. If you follow the instructions given in the link above the resulting vbs file that is genereated by the batch file has an error at this line. 

 

The only way i was able to fix this (I think, as i've not been able to verify that it's working properly) is to leave the above line as it is, and to change:

 

echo.packageLocation = DownloadUsingHTTPProxy^("!url!", "!http_proxy_hostname!", "!http_proxy_port!", "!http_proxy_username!", "!http_proxy_password!"^)

 

to:

 

echo.packageLocation = "!url!"

 

(Of course after changing the URL path to the network location of the files)

 

--------------------------------

 

 

Is there an easier way? Have i done this correctly? Why does ESET not automatically deploy the new agent to clients locally when it's determined the update is needed? Is there an option for this that i've missed?

 

Thanks

 

Jdashn

 

Link to comment
Share on other sites

  • ESET Staff

Thanks for letting us know. We have made some late changes in windows live installer and documentation was not adapted to this as it requires some time due to localizations.

 

Your steps seems to be correct - I would do this:

 

  1. Change url to local/network share path to your installer(s):
    set url=hxxp://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.4.283.0/Agent_x64.msi
    set checksum=67e2c3c29633548daad2a8f6c59045d11d538b42
    if defined IsArch_x86 (
      set url=hxxp://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.4.283.0/Agent_x86.msi
      set checksum=0f80b4e9dc22ae4192601c335b6b6a76a79f5255
    )
    

    to something like this:

    set url=C:\Installers\Agent_x64.msi
    set checksum=67e2c3c29633548daad2a8f6c59045d11d538b42
    if defined IsArch_x86 (
      set url=C:\Installers\Agent_x86.msi
      set checksum=0f80b4e9dc22ae4192601c335b6b6a76a79f5255
    )
    

    Make sure checksum is SHA1 hash of installer file. This may change for different installer versions.

  2. Disable HTTP download as it will fail for local/network share files. This can be done by replacing:
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.    If packageLocation = "" Then
echo.        Wscript.Quit 30
echo.    End If
echo.End If
echo.On Error GoTo 0

with:

echo.packageLocation = "!url!"

Regarding your question I am not sure I understood you: you are trying to upgrade AGENTs to newest version but your clients have no direct visibility to ESET repository (hxxp://repository.eset.com) and therefore you are not using "Components upgrade task" to perform automatic update? If this is the case, we recommend to use HTTP Proxy so that AGENTs can download installer files even when they do not have direct access to internet.

Link to comment
Share on other sites

All of my clients have direct visibility to the repository, but share their access on one metered line -- so we'd prefer not to have 2k downloads of the Agent file hence the reasoning for the adjustment to the batch file. 

 

What i'm doing right now is using powershell to: 

adjust this batch file based on the site the computer is at (pointing to the agent files on the domain controller at each site) 

deploy the batch file to the computers that are online, and do not have the latest version of agent installed (determined by quering the eset db, and a ping)

Running the batch file locally on each machine.

 

What i'm asking is really is there an easier way to update the agent from within RA without having to have each machine reach out to the eset repository? Even if i can't base the DL location on Site, but could just tell all the clients to update from the same local share that would be great, is that possible using 'Components upgrade task'?

Edited by jdashn
Link to comment
Share on other sites

Do you know where install and usage instructions are for the ESET HTTP Proxy are? I think the original administrator who setup our v6 server install attempted to set it up, but it does not appear to be functional. I believe with some instructions or documentation i should be able to set it up properly? This is like the 'mirror' option correct? 

Link to comment
Share on other sites

  • ESET Staff

Do you know where install and usage instructions are for the ESET HTTP Proxy are? I think the original administrator who setup our v6 server install attempted to set it up, but it does not appear to be functional. I believe with some instructions or documentation i should be able to set it up properly? This is like the 'mirror' option correct? 

 

Manual installation steps are described in ERA documentation: hxxp://help.eset.com/era_install/64/en-US/http_proxy_installation_windows.htm

You could also use all-in-one installer to install of upgrade Apache HTTP Proxy and it should work out-of-the box.

Edited by MartinK
Link to comment
Share on other sites

Thanks MartinK!

 

Was just wondering if you'd had a chance to ask anyone else regarding if it's possible/advisable to set the target of the Apache Proxy cache to a dfs location as the traffic over our WAN for installs can be a limiting factor in getting updates pushed out to our clients in a timely manner?

 

It looks like over night i was able to get the apache proxy setup, but I believe there may be some issues, when i set the following setting:

hxxp://help.eset.com/era_install/64/en-US/index.html?efficient_usage_of_apache_http_proxy.htm

 
 
Enable usage of Apache HTTP Proxy under Admin > Server Settings > Advanced settings, enable Use proxy server, fill in the required fields, leaveUse direct connection if HTTP proxy is not available enabled and then click Save.

 

 

 

After setting the above setting, the server states it's no longer able to access the ESET repository. I'm going to guess that this setting is for the ESET proxy? or for usage if you've got a web proxy setup for internet access in general? From the instructions it seems that this is part of what you do to get the apache http proxy setup?

 

Is there a way with the apache http proxy to limit the items you get from it to just application updates and i can use the mirror tool for DB updates (I know the mirror tool can handle it's target file location being a dfs share, at least thats what it looks was being done for our 5x install. 

 

Thanks again!!

 

Jdashn

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...