Client Deployment Improvements

Two improvements:

1.) Enable Silent Install for Cloud Installations

2.) Currently, the Client looks at a deployment location for updates and each client will download from that location when version changes occur. In a single-site on-prem installation, this is fine. For companies with users across the WAN (site-to-site or in the Cloud), this creates a lot of unnecessary network traffic. For an upgrade, every client pulls down the client over the WAN and then all over again for the Pilot instance. Being able to “cache” the client install by site would reduce network traffic for Epicor Customers and save Epicor money on their edge caching services.

  1. It is already on the books.
    2A. You can change the deploymentserver of the sysconfigs for the remote users to full the client from a local server to them instead of a single server.
    2B. Our Cloud team has requested the ability to have a tiered deploymentserver option so that a local machine can be used as the source of the update if it is available, if not, pull from the deploymentserver.
2 Likes

I knew that but wanted to see if the interest was broader than just us.

Including SaaS users?

I like the way the Cloud Team thinks. :wink:

Thanks Nathan!

Technically possible, in practice not practical for SaaS users.

With the move to Azure, maybe something like this would help?

#All-In-the-Cloud