Hello everyone,
Context:
WAPT version: 2.1 Enterprise
Server OS: Debian 11
Administration console OS: Win10pro
Package development workstation OS: Win10pro
Some of our users' workstations remain off for a "relatively long" period.
Furthermore, some users rarely shut down their workstations (laptops + sleep mode).
We use WAPT to push certain patches (not yet fixed by Windows updates) resulting from CERT alerts, for example.
We would like to automatically install certain packages upon restarting the workstation.
Is there a way to automatically force the installation of certain packages at startup, rather than at shutdown? If so, how?
CR
[RESOLVED] Automatic installation of certain packages upon computer restart
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
-
olaplanche
- Messages: 178
- Registration: January 26, 2017 - 11:11
Hello,
it's possible to run the waptexit.exe binary at login by placing a shortcut in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp".
The drawback is that the user will see the update window upon logging in, and depending on the update installation time, this could be problematic.
it's possible to run the waptexit.exe binary at login by placing a shortcut in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp".
The drawback is that the user will see the update window upon logging in, and depending on the update installation time, this could be problematic.
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
One interesting method, if it's for a specific package, is to use the `forced_install_on` attribute
(https://www.wapt.fr/fr/doc/wapt-package ... ntrol-file).
This allows you to force the installation from a certain date.
(https://www.wapt.fr/fr/doc/wapt-package ... ntrol-file).
This allows you to force the installation from a certain date.
