Agreed, for what Sage charges every year as "customer care", they should have an advanced notification system in place. Also, in addition to the notification and "admins-only" update restrictions, Sage should rethink the whole update and upgrade subsystems. They forget there are Quantum users out there with 40 workstations, so your every once in a while update means 40 updates at the time. Just some ideas here: Sage knows which installations are multi-user (license checks). Sage50 should be smart enough to know there is a "server" (tip: the installation where the data-path points to a local drive) and "clients". Only allow updates (unattended or on-demand) and upgrades on the server. For updates (Payroll, Tax tables, Service Packs) Once the "server" finds out there is an update available, we admins, should be able to schedule unattended updates. NOTE: Currently, if you check for updates, and you try to read the notes about the update BEFORE you install it, the links to Sage's website always return a 404 page. Then when the user logs in on a workstation, Sage50 Updates itself on the spot (just like Chrome / Firefox does), the update payload should be already on the server installation, so is just a matter of running the script. Done For upgrades (2015 to 2016) First off, Sage50 must check the activation servers are online (why? You dont want to waste 1 hr restoring a server state backup after upgrading sage50 and running into their " rare " chance of "Activation issues, try again later" occurrence. Now, as the users try to log on, Sage50 should upgrade itself, all files are already on the server, so the workstations need not to download the whole upgrade package all over again (think 40 user installations). Finally For an average of $1k x Sage50 installations per year that Sage charges (i'm pretty there are more than a 100), they most definitely can afford hiring a good programmer for a year to implement this changes. Thanks
↧