See this article in the KB. ID:83952Last Modified Date:6-18-2019

As a note, do not use FQDN for the installation your scripting

thank you.

JStone1, have you had any success scripting it without the need to touch the workstation re: these steps suggest physically running the script at the workstation.  Take the example where you have users logging in without admin privileges.  Even if you set the script to run through GPO or login script I am guessing it would fail.   

On a similar note if a company has the money the really easy way around this is to centralize the install on a terminal server(s) and you are left with updating just the amount of clients that equate how many servers in your farm.  Sage 300 cannot be run (well) via a VPN so any company that has remote users must go with this process. 

The installer is chained and a bunch of sub-installers kick off as part of that, with dependency checking included. It's better than it was, but far from great. MSI's aren't even on the horizon, from what we've been told.

Up until 17, there wasn't even scripting, and it didn't work well for Sage 17.1 It works BETTER with 18.1, but it sometimes takes multiple runs of the script to make it work. Random errors popup as well, so it's far from fully automated.

I setup two scripts, one for initial installs and one for version updating. You don't need a path to the response file for upgrading.

Updating switches: INSTALL_MODE=Reinstall MAINTENANCE_MODE=RemoveAcctClient ACCOUNTING_UPGRADE=true 

I got better results with the 18.1 -> 18.4 update the end of last year with a forced reboot upon script exit

:: Added shutdown 12/15/19

SHUTDOWN -r -t 0 -f

Edit to add: Make sure your desktop support folks know the difference between the two scripts! A lot of time can be wasted otherwise.

That's as automated as I've been able to make it, with 100+ endpoints running Sage Desktop I've spent plenty of time looking for workarounds.

As for running everyone on a Remote Desktop server, while we do have one, it's only for users at jobsites or remote offices. It's not really worth it just for updates to put everyone on an RDS, especially when they have so many other specialized programs on their local machines.

Hey Jeff -

I have not successfully run this script, but I know I saw Sage advertising this with the most recent update. We actually moved users to Citrix, as you suggested, to address this coupled with increasing security.

Thanks for your reply.  I am a big believer in centralizing (and virtualization which is a different topic) apps like Sage which do not require specialized graphic cards in the Citrix servers.  Not only is upgrading and maintenance easier you also limit potential application clashes and have a much smaller potential security issue footprint as you alluded to.