waptagent/waptdeploy /StartPackages does nothing

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
dsp
Messages: 9
Registration: February 27, 2018 - 09:15

January 22, 2020 - 12:03

Hello,
I'm not sure if I'm doing this correctly, but nothing happens when I use `/StartPackages=package_name` with Waptagent or `--setupargs=/StartPackages=package_name` with Waptdeploy.
However, modifying `set_start_packages` in Waptagent.iss before generating the Waptagent package works.

group of packages directly during installation, depending on the machine being installed.

specific
WAPT version: 1.8.2
Server OS: Debian 10
Administration/package creation machine OS: Windows 10 1909
LMU-wapt
Messages: 8
Registration: Oct 02, 2020 - 11:04

May 12, 2021 - 5:58 PM

Hello,

I have the same problem in version 2.0 with the wapt agent and the /StartPackages=XXX parameter.

Is this parameter still functional?

Where can I find logs to try and find the source of the problem?

Thank you.
- Installed WAPT version (2.0)
- Server OS: Linux and Debian 10 version
- Administration/package creation machine OS: Windows 10
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

May 18, 2021 - 3:27 PM

That should work. I'm opening an internal ticket to track this issue. Otherwise, you can create an OU package so the machine retrieves its updates after joining the domain.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
bsok
Messages: 2
Registration: June 15, 2022 - 4:01 PM

June 16, 2022 - 09:25

Hello,

the problem persists.
So it won't be fixed in community version 1.8.2?

Regards,

Bernard.
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 16, 2022 - 09:32

Hello bsok,
bsok wrote: June 16, 2022 - 9:25 AM The malfunction persists.
So it won't be fixed in community version 1.8.2?
Tranquil IT has stopped contributing to WAPT Community 1.8.2 support. But that doesn't prevent another user, or yourself, from fixing it and publishing their fix (the WAPT 1.8.2 Community code is under GPLv3).

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked