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.
The client does not apply the changes
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
You can remove tis-waptserver
(apt-get remove tis-waptserver).
Switch the repo back to 1.7
and reinstall tis-waptserver.
(apt-get remove tis-waptserver).
Switch the repo back to 1.7
and reinstall tis-waptserver.
