(except for the console client).I'm now going to tackle adding the repositories.
Thanks everyone for your help!
WAPT 1.3 to 1.5 Migration Error
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 :
CTRL F5?tech62 wrote: ↑Dec 22, 2017 - 5:29 PM I reread the documentation and created the missing group to update the database, but on the client side, I still don't see the list of available packages (it's empty).
From my console (version 1.5.11), when I generate the agent, everything goes smoothly. So I go to the portal to download the agent, and that's where the problem starts: it shows version 1.3.11.
tech62 wrote: ↑Dec 22, 2017 - 5:29 PM A simple clarification, but one that will surely help some:
I noticed that wapt doesn't install/download on demand, let me explain.
Basically, you have to create a group containing the software via the console, assign this group to the machine(s) which, after the package update, will download all the components of this group.
Then, the user, by going to localhost:8088 via the web browser, will only be able to trigger the installation if they have been added to the SYSTEM group "waptselfservice", which must first be created on the client.
When the user requests the installation, they simply need to enter their usual login credentials to authorize it.
Yes, that's normal behavior; there's also waptexit or forcing installations from the console.
To see the fundamental principles:
https://www.wapt.fr/wapt-1.5/Theorique/ ... ndamentaux
