Page 1 of 1

WAPT Update

Published: August 29, 2020 - 11:56 AM
by C80SGEEK
Hello,

WAPT version 1.0.0.0,
OS Windows Server 2008 R2.

We are using an older version of WAPT 1.0.0.0.
Is it possible to update this version to the latest one?

Thank you in advance.

Re: WAPT Update

Published: August 31, 2020 - 11:46 AM
by dcardon
Hello,

version 1.0 is over 5 years old... In the meantime, there have been quite a few changes (package signing, HTTP server, database, etc.). The best solution is to reinstall a server with WAPT 1.8.2, redeploy the agent on the workstations, and then re-import your software packages.
When reinstalling the agent, you should check that it doesn't need to be removed beforehand, as we've never tested an upgrade of the local SQLite database from version 1.0 to 1.8. Re-importing the machine packages will also be a bit tricky because the naming convention is different (FQDN or UUID instead of a short name).
If you need assistance, feel free to call Camille or Faustine at the TIS sales server.

Best regards,

Denis

PS: To be honest, I'm a little impressed by the longevity of your 1.0 server... :-)

Re: WAPT Update

Published: August 31, 2020 - 12:36
by C80SGEEK
Hello,

Thank you for your feedback.

I suspected there would be some inconsistencies between the versions.
I wanted to check with you to determine if there was a way to update by going through the various development versions, from 1.00 to 1.1, for example, and then, update by update, reaching the current version.

If I understand correctly, a complete reinstallation with removal of the 1.0 agent on all client machines is necessary.
Our packages will need to be recreated under version 1.8.

Is there a plan to be able to uninstall the WAPT agent via the WAPT server?


Thank you

Re: WAPT Update

Published: August 31, 2020 - 7:34 PM
by dcardon
If you reinstall the different versions on both the server and the client machines gradually, it should work. The server's communication protocol evolves, and we maintain a certain level of compatibility between versions N and N-1 to allow for agent upgrades. On the server side, the database has moved from MongoDB to PostgreSQL, the web server from Apache to Nginx, and so on.
You can test a direct upgrade on a client machine from 1.0 to 1.8.2, but I don't have any feedback on that.