Cannot get package from repository

[Sanjeev Velmurugan 0]

Dear Eset Team,

 

I have updated to ERA V6.2 today and also rolled out the new Agent Live installer.

This worked fine. Good improvements in this version.

 

Still there are bugs. I cannot get a package from the repository.

I can push an installation command from ERA6 to a client.

But it never gets installed. I got this from the detailed execution view

 

  

 

I have set the update server to "autoselect".

Im still in the process of getting in a lot of new clients with EEAv4 EEAv5 and i need to make sure they can update trough ERA to v6.

 

 

Can you help?

 

Thanks

[Marcos 5,458]

First of all, if you connect through a proxy server make sure it's set correctly in the Agent Live installer. You can also configure it later via an agent policy.

Unfortunately, the return error code is not visible in your screen shot, only "(error c..." is visible and the actual number is missing. Please get the agent trace log from the client and send it to me via a pm for analysis. Also a Wireshark pcap log from the time of agent installation might shed some light.

[Sanjeev Velmurugan 0]

 The error code is visible on the screenshot.

I have attached it again

we do not use a proxy, we want them to update from available era servers.

i know this can increase the bandwidth but this is not a problem for us.

we just want older clients to grab the newest installation file and install it.

that's what i am trying to push with task, which fails as described above

[Marcos 5,458]

Ok, I admit I overlooked the complete error in the tooltip. What I don't understand is the url av2.appway.com as the ESET's repository is located at hxxp://repository.eset.com/v2/.

[Sanjeev Velmurugan 0]

Hi Marcos,

 

I have checked again the configuration and saw that one policy was pointing wrong to the address above.

i cleared that and tried again to deploy components upgrades for security products without luck.

 

I had to generate a new certificate while upgrading to 6.2.

How can i push the new certificate to the existing clients?

 

I think this may be the problem why they cant update them self when i push the installation task from ERA6 webconsole.

Virus signature updates are working fine, i just cant get th clients to update to the newest security product.

[Sanjeev Velmurugan 0]

And 35 clients last connection date is the 4th September, the date when we did the upgrade to 6.2, so since then, not an single client is reporting back to the ERA 6 server.

 

How can i push the Certificate?

[Marcos 5,458]

Create a new Agent Live installer so that it contains current certificates and deploy it to the clients.

[Sanjeev Velmurugan 0]

Ok recreating the Live Installer worked that the client connects again to the era server again.

i can roll out policies, wake-up call, reboot etc.

 

The only thing not working is updating the antivirus itself. Signature database update works fine but every time i try to run a Software Install task, it points to av2.appway.com which is the DNS name of our ERA6 server.

but i have checked all policies. There is no policy or setting pointing to that address nor have i setup a HTTP proxy.

i just want them to update through the ESET repository.

 

Here are some screenshots from the settings:

 

[Marcos 5,458]

When creating a software install task, did you select "Install package from repository" and not "Install by direct package url" ? Make sure that you're not sending an older software install task that might have pointed to av2.appway.com.

[Sanjeev Velmurugan 0]

Deleted all Software install tasks, created a new one.

same result, still pointing to av2.appway.com

 

but ERA6 reports that the repository is set correctly

 

 

Edited September 10, 2015 by Sanjeev Velmurugan

[Marcos 5,458]

What about creating an agent policy that will have the repository set to the default value AUTOSELECT ? This should solve the problem with software install tasks.

 

 

As for the problem with updating Endpoint clients, please send me a complete error message that you're getting. If you have physical access to one of those computers, try running update manually and post here the recent records from the ESET event log.