Sage 100

 View Only
  • 1.  Any idea why Sage went this way on 2017+? Isn't t

    Posted 06-06-2017 08:50
    Any idea why Sage went this way on 2017+? Isn't the concept of a workstation update installation bundle that you run it once to configure a workstation? Sage Exchange Desktop needs to be installed even if you only are placing cards into the Sage vault (no processing). Sage Exchange Desktop 2.0 no longer automatically installs. It must be manually installed on every workstation requiring access to SED.


  • 2.  RE: Any idea why Sage went this way on 2017+? Isn't t

    Posted 06-06-2017 09:09
    (1) SPS probably got sick of Sage installing out of date versions. (2) Why spend precious shareholder maintenance dollars on programming the installer correctly when you can pass along the costs to the partners and users?


  • 3.  RE: Any idea why Sage went this way on 2017+? Isn't t

    Posted 06-06-2017 10:59
    I suspect it's the prerequisite often needing a reboot / admin permissions.


  • 4.  RE: Any idea why Sage went this way on 2017+? Isn't t

    Posted 06-07-2017 09:25
    From version 2017 on the installer will no longer be a one click application since many customers had issues with remote desktop, terminals server/citrix. It is now a manual installation.


  • 5.  RE: Any idea why Sage went this way on 2017+? Isn't t

    Posted 06-07-2017 09:58
    Actually, once I realized it was not a combined install, I rather like it. Gives us a little more control over which bugs we want to install.... Now if they would only fix the damn module date prompt. Under classic, it works as always. Under the new ""standard"", the date pops when you click on the module, not when you click on the program. So I waste time waiting for the program to open. But no, I have to click on the program to open it....