Hiberboot application problem

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
Mikael
Messages: 3
Registration: March 28, 2023 - 3:49 PM

May 2, 2023 - 7:04 PM

Hello,

I'm currently using WAPT 2.3 Enterprise. I'm having trouble disabling hiberboot (perhaps I misread the documentation)
. During manual agent installation, I can disable hiberboot (and it's disabled by default).
For deployment across the network, I'm using waptdeploy (not via GPO, but through another tool). The deployment goes smoothly.
However, hiberboot isn't being applied: it's not present in the watp-get.ini file and hasn't been modified in the Windows options. Consequently, packages only install/uninstall after a reboot, but not when the system is shut down.
I haven't yet tried modifying the wapt-get file locally, but I initially thought that waptsetup loaded the configuration for the waptagent onto the server and would therefore be used during deployment?

Alternatively, in the Enterprise version, there is the "Edit initial configuration" section: do I need to go through this to deploy the configuration in another package?
Locked