Why is the Sage client version number not correct for updated installs?

I've pulled from reports of two different inventory/asset management trying to ensure my team didn't miss upgrading workstations this Sunday. Both tools use WMI to get the inventory, I used two different tools because I couldn't believe the version number didn't update with the re-install of the 18.4 client!

It's time consuming enough to track down every install of the Sage client without having NO way to tell when the client software has been updated. This seems quite an odd oversight - if it's there for compatibility checking, aren't there alternate ways of checking version without freezing a client to 2018?

The still-manual scripted install/updates are at least an improvement, despite they still require user input, but that process gets slowed down even further when the inventory doesn't show what version the client software is.

I'm looking at testing for the modified date/time of the local install log, that doesn't sit well with me to have that makework on a Sunday.

  • 0

    HI Brian, the InstallHistory.log may be of help.  It logs installs, uninstalls, and updates. You can find this file on the server and workstation machine in ProgramData\Sage. Please see KB 102299 for the details.

  • 0 in reply to Una

    I understand what you're saying but I used the datestamp value of the logfile written during the scripted install to discriminate between workstations that had or hadn't been updated. Not all my boxes have WOL so there was a certain amount of hoofing it around to boot all the machines up. It's hard for me to understand why versioning is handled so poorly, when it's a well understood part of the Windows development model. It's sloppy and user unfriendly.