Jump to content

All-in-one installer expiration


Recommended Posts

Good afternoon - I work for a MSP and came across an issue that was unexpected, wondering if other's have as well and if there is a workaround or a feature enhancement on the roadmap.

Today I learned that installers created in ESET expire every 6 months, wondering why that is and if it can be changed?

We're using Automate as our RMM tool and the deployment package created in the DEM becomes outdated and needs to be revised with the new URL created by the new installer package in ESET. Otherwise pushed deployments fail. This issues gets multiplied by x number of clients which makes monitoring and updating the packages a tedious process.

Perhaps there is something I am missing or others are doing things differently. Thanks in advance!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...