Didn't get it to work reliably with 17.1, way more miss than hit (upgrading from 16.1). I'm looking forward to a client FINALLY intended to be used in large deployments. Are you going to 18.1 already?

I was considering upgrading, but it's such a headache going to every machine.  Sure was hoping this would work, but honestly didn't expect it to.  Not sure when I'll upgrade, we usually stay current with the updates.   Thanks so much for your response. 

What are you doing for remote management? I pull a software inventory from all domain workstations, filter for Sage and sort by version number, then check against that for any that got missed. From that list it's just an RDP or remote session into a machine to kick off the upgrade. 90+ machines, took one day of Memorial Day weekend - first day was server migration and 3d party product integration, Monday was for internal testing.

It's misusing a tool that is perfect for push installs, but I'll have to wait and try again with 18.1 next year. Automation is not really possible yet with the Sage client, but remote management is still the way to go.

I don't typically remote into individual computers, but that may be my best option. What do you use to do the software inventory?  

Goverlan is my primary tool for endpoint management, software inventory being an example of a remote task executed on each workstation. The Goverlan remote control tool is good for help desk staff for over the shoulder support, but for off-hours activity RDP with an account with local admin privileges is still the fastest method. How many workstations do you have to update? Last I looked, we have 95 with the Sage client installed, not counting RDS and MA server installs. Physically touching that many machines would be time/cost prohibitive, especially with the glacially slow install speed of the 17.1 client.

I only have 25 with Sage installs.  I do use RDP but I don't have accounts set up on all workstations.  That is probably my best way to go. I may look into Goverlan but it may not be cost effective for us. Thanks for your input.

If you're on a domain, you can use Restricted Groups in a Group Policy to add a domain group to the local Administrators group. If you're not on a domain, you can use a script on a thumb drive to create a uniform local administrator user - one stop and you're done.

Goverlan is cheap at scale, but I totally get 25 machines isn't a lot to spread the cost across.

We are on a domain.  Thanks so much for your help.  I'm kind of a self-taught IT tech - I was the controller for several years but always was very involved in the IT part.  Now I'm just a "jack of all trades" so I appreciate all help.  

Knowing the money side of IT is super important, so you're miles ahead of most of us. Think about setting up a Security Group for desktop administrators, avoid using a Domain Admin account for anything that doesn't REQUIRE that level of permissions. Use a Group Policy to add that security group to the workstation's local Administrators group. Then you can add and remove individual accounts to that security group, and the accounts will inherit local administrator privileges. My daily driver account has zero domain level privileges, for example, and as a rule anyone with any kind of admin access has a separate account for those tasks. Accountability goes with user privileges that way. Don't mean to overload the info, but having a Domain is a HUGE advantage for network management, users and computers and everything else.