6.6 and Mirror Tool

[sdnian 6]

Quote

It is not possible to update Endpoint 6.6 using Mirror tool from ESET Remote Administrator 6.5 and earlier or create an update mirror for Endpoint 6.6 using any product earlier than 6.6 (6.5 and older)  

Does ESET will update new Mirror Tool version to support 6.6 in the future?

[Peter Randziak 1,183]

Hello Sdnian,

as far as I know the mirror tool does not have any special application logic to support the Endpoint 6.6

It just copies the files required from the update servers.

Regards, P.R.

[Marcos 5,462]

On 8/25/2017 at 6:45 AM, sdnian said:

Does ESET will update new Mirror Tool version to support 6.6 in the future?

Yes, we plan to have a new version of the mirror tool but it will take some time. Isn't an http proxy an option for you? With http proxy much less data should be downloaded with each update compared to using a mirror.

[sdnian 6]

11 hours ago, Marcos said:

Yes, we plan to have a new version of the mirror tool but it will take some time. Isn't an http proxy an option for you? With http proxy much less data should be downloaded with each update compared to using a mirror.

I've try to use http proxy since 6.2/6.3.. I am familiar the http proxy advantages. But in my experience, It is relatively slow, and more unstable. Some of my clients always complain it. So I prefer to use mirror tool.

When you release new version of mirror tool, please support Windows Server 2003. Several months ago, I've ask this issue, but still no fix until now. 

 

By the way, could you ask your engineer to check why the 6.6 update files can't be cached in local disk by apache http proxy? Every time it download from ESET server, apache http proxy just forward the requests. I tried to analyze the problem, It should be missing 'Cache-Control' in the header of HTTP response.

For example, this file hxxp://update.eset.com/era6-sta/mod_000_loader_1112/em000_64_l0.nup, it have 'Cache-Control' and could be saved the cache file in "C:\ProgramData\Apache Http Proxy\Cache"

< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 29 Aug 2017 00:00:35 GMT
< Content-Type: application/octet-stream
< Content-Length: 70124
< Last-Modified: Tue, 22 Nov 2016 00:00:00 GMT
< Connection: keep-alive
< ETag: "58338a80-111ec"
< Expires: Tue, 05 Sep 2017 00:00:35 GMT
< Cache-Control: max-age=604800
< Cache-Control: s-maxage=0, must-revalidate
< Accept-Ranges: bytes
 

But this file hxxp://update.eset.com/ep6.6-rel-sta/mod_041_w10upgrade_1000/em041_32_l0.nup, it can't be saved by Apache HTTP Proxy. No matter how many times I download, it is always downloaded directly from the ESET server.

< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 29 Aug 2017 00:00:37 GMT
< Content-Type: application/octet-stream
< Content-Length: 118835
< Last-Modified: Thu, 23 Jul 2015 00:00:00 GMT
< Connection: keep-alive
< ETag: "55b02e80-1d033"
< Accept-Ranges: bytes
 

Edited August 29, 2017 by sdnian

[Marcos 5,462]

We are currently in the process of checking nginx configuration which is most likely causing EPv6.6 update files not to be cached. We'll keep you posted.

[Peter Randziak 1,183]

Hello guys,

the required changes has been deployed to production.

Can you please try it and let us know?

Thanks, P.R.

[sdnian 6]

The update files of v6.6 could been cached by Apache HTTP Proxy now.

[Peter Randziak 1,183]

Thank you for the confirmation sdnian.