Jump to content

Using external URL package source in Update Task


pronto
 Share

Recommended Posts

Servus Community,

I created a new client task today to update the ESET product and it ran correctly on 12 test machines, but not on two. The task terminated there with the error:

Repository package checksum verification failed

While searching for the cause I came across several post that specified a different update source in the task. I tried that as well and the task terminated successfully on the other two machines as well.

In the process I noticed that a latest version is specified in the URL[1]. My question would be, is this URL permanent? So I wouldn't have to create a new task for every version I want to upgrade to, but could simply configure a task with Upgrade to latest and run it over and over again. If that then makes sense in the long run in the history of updates as well.

Another question follows, is there somewhere a list of all these URLs? When I only modify the URL to enter an above located folder, I get an 404 error.

[1] https://download.eset.com/com/eset/apps/business/eea/windows/latest/eea_nt64.msi

Thx & Bye Tom

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...