Tranquil IT Forum

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

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.

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

Hello,

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

Regards,

Bernard.

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