Beta Feedback

Agent msi vs exe packaging

Previous versions of the agent adhered to Microsoft Windows standards and utilized the App.Wiz for uninstalling (in addition to the bat file, which simply called the msiexec standard with the usual /x uninstall parameter). This is standard .msi packaging. Enterprise deployment of a non-standard, at least for Sharp, is, well, unsettling. What is the reason for this deviation to industry norm? Are there any plans or roadmaps to get it back into compliance with Microsoft standard?
  • Gravatar Charles Nicholson
  • Sep 11 2015
  • Already exists
  • Chad Hanson commented
    April 27, 2016 13:00

    I would also like to see agent updates pushed from the server console.   

  • Admin
    Raviv Chalamish commented
    April 27, 2016 15:01

    Chad, we are planning to this feature actually. It is used already internally (we push Agents from the console in Aternity own deployment) but we need to improve security and administration before we make it available to customers. Feel free to open a separate idea for it for tracking purposes.

    As for MSI vs. Exe, we moved back to Msi in newer Agents.

  • Chad Hanson commented
    April 27, 2016 16:24

    Sounds great, I have posted another idea to the portal for tracking purposes.  Thanks!