Using Apache HTTP PROXY

[Mr Problems 0]

Well, im trying to use the apache http proxy for the mirror stuff.

The problem is that when im trying to put it in a Policy it ask for a username and password, but when i installed era ans with that apche it never asked me to put a username and password.

What should i do?

Also is there another way of putting a mirror without using Apache http proxy in ERA 6.X.

 

Thanks!

 

[MichalJ 434]

Apache HTTP Prroxy does not support authentication by default. It should work without password.

If you have another proxy, you can use it as well for updating of ESET clients.

If you want to have another updating alternative for ESET clients, you can do it by:

1. creating a mirror out of a client / server product (EEA / EES / EFSW) and point other clients to this mirror (suitable for smaller networks)
2. creating a mirror out of a client / server product, and use some webserver to provide updates (IIS)
3. creating a mirror using the offline mirror tool, and use some webserver to provide updates (alternatively you can also use a network share).

Some useful articles: http://support.eset.com/kb5950/

Descriptions of differencies between mirror / proxy: http://help.eset.com/era_install/65/en-US/index.html?difference_connectivity.htm

[Mr Problems 0]

And if i want to create a mirror so EEA can update , i have to install EEA in the server o using EES its the same? Even if its not the same product.

[MichalJ 434]

EES is able to create mirror for EEA. If your server is installed on a Windows Server machine, then ESET File Security should a product of your choice.

[Mr Problems 0]

Yeah im installing file security in the server, but with that i should be able to mirror for EEA right?

[MichalJ 434]

Yes

[Marcos 5,074]

20 hours ago, Mr Problems said:

Yeah im installing file security in the server, but with that i should be able to mirror for EEA right?

To put it right, EFSW 6.5 does not create a mirror for Endpoint v6.6 which uses a new format of update files. However, Endpoint 6.6 as well as all future server products will create a mirror compatible with both older and newer versions which also means that the amount of downloaded files with each update will approximately double. This is also a reason why we recommend using an http proxy for caching update files instead of using a mirror.