andy17d
-
Posts
7 -
Joined
-
Last visited
Posts posted by andy17d
-
-
That's right. I'm using Apache HTTP Proxy.The computer on which the error is outside the corporate network.I've set a policy, which enable the option to download updates from the main server ESET if the proxy server is unavailable.
-
I'm trying to update the agent from version 6.2 to 6.3 through the remote installation from the console ERA. Unfortunately, the installation job fails.
I get the message: GetFile: Failed to process the HTTP request (error code 20008, url: 'hxxp://repository.eset.com/v1//info.meta') -
I know this is that I blocked out the computer to the Internet and let only movement within the internal network. Then download the updates stopped.
I would like to Endpoint while downloading updates did not contact with external servers eset but benefited from my server update.
-
I wanted to configure ESET Endpoint to get updates from my proxy.
I installed and configured the Apache proxy by advice hxxp://support.eset.com/kb3637/?viewlocale=en_US
Unfortunately I can not force the endpoint to update from it.
I set options Update / server http proxy. I typed my proxy address and port.
However, the updates are downloaded from the Internet constantly instead of a local proxy
When I used the ERA in version 5 there could force clients to set the update server. However, in version 6 is no longer think such an option and it should be done just by proxy.
-
I was able to finally do it. The problem was that a Windows XP group created as a subgroup of Windows computers.
When I moved a Windows XP group on the same level as the group Windows computer everything started working.
-
I'm trying to create a template for a dynamic group, which will all computers running windows xp.
I created a template with the expression:OS edition.Os name contains Windows XPUnfortunately it does not work. The group did not show up any computer.What am I doing wrong?
Agent remote installation error
in ESET PROTECT On-prem (Remote Management)
Posted
It is working now. It turned out that apart from setting a proxy for the EEA, it was necessary to additionally set up a proxy for the agent (and more specifically, to Agnet not use a proxy, if it is outside the corporate network).