Page 1 of 1

The client does not apply the changes

Published: January 28, 2020 - 08:41
by jsdmc
Hello,
Our WAPT server was running version 1.5.6 with a few test clients.
We wanted to migrate everything to version 1.8.

The server migration went smoothly, without any changes to the private key or prefix.
The console is working correctly.

We created a waptupgrade package and assigned it to a workstation.
However, in the console, the waptupgrade package appears in the list of required packages on the machine, but not in the "General" tab.
Checking for updates and running the installations has no impact on the client or the target workstation; the WAPT client remains on version 1.5.

Any ideas?

Thank you.

Re: The client is not applying the changes

Published: January 28, 2020 - 8:39 PM
by sfonteneau
You're coming from a slightly older version of WAPT.

In your case, you can go directly to version 1.6, but not directly from 1.5 to 1.8.

I advise you to first upgrade ALL the workstations in your network from 1.5 to 1.7.

Once that's done, you can then upgrade to version 1.8. (All of this is to make the WaptUpgrade package compatible.)

The other solution is to opt for deployment via WaptDeploy using Group Policy.

Simon

Re: The client is not applying the changes

Published: January 29, 2020 - 08:26
by jsdmc
Hello,

thank you for your reply.

Our server is already on version 1.8, how do we migrate the clients to 1.7?

Re: The client is not applying the changes

Published: January 29, 2020 - 11:29 AM
by sfonteneau
You can remove tis-waptserver

(apt-get remove tis-waptserver).

Switch the repo back to 1.7

and reinstall tis-waptserver.