Hello,
I have a question about the WAPT console that appears when an agent workstation is shut down.
Is it possible to modify it? For example, to disable clicking the red cross and remove it.
[RESOLVED] WAPT Console
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 :
Good morning,sfonteneau wrote: ↑Apr 29, 2022 - 6:04 PM Hello:
https://www.wapt.fr/fr/doc-1.8/wapt-usa ... f-upgrades
Thank you for your response.
Do I need to manually edit the wapt-get.ini file on each machine, or is it possible to do it via the console?
Installed WAPT version = 2.2.1
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Hello Jitero,
In my opinion, the simplest solution would be to create a small package that modifies the wapt-get.ini file. There's an example package in the WAPT store.
For subsequent agent updates, it's preferable not to use the automatically generated waptupgrade package, but rather to create your own agent update package incorporating all the changes to the INI file.
For our purposes, I created a package for the agent that determines whether it's installed on a server, laptop, or desktop, and therefore applies different settings to the agent (for example, remotely shutting down or restarting a PC is fine, but this shouldn't be an option that appears in the console for servers).
Best regards,
Tom
In my opinion, the simplest solution would be to create a small package that modifies the wapt-get.ini file. There's an example package in the WAPT store.
For subsequent agent updates, it's preferable not to use the automatically generated waptupgrade package, but rather to create your own agent update package incorporating all the changes to the INI file.
For our purposes, I created a package for the agent that determines whether it's installed on a server, laptop, or desktop, and therefore applies different settings to the agent (for example, remotely shutting down or restarting a PC is fine, but this shouldn't be an option that appears in the console for servers).
Best regards,
Tom
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Hello Tomt.heroult wrote: ↑May 2, 2022 - 10:47 AM Hello Jitero,
In my opinion, the simplest solution would be to create a small package that modifies the wapt-get.ini file. There's an example package in the WAPT store.
For subsequent agent updates, it's preferable not to use the automatically generated waptupgrade package, but rather to create your own agent update package with all the changes to the INI file.
For our purposes, I created a package for the agent that determines whether it's installed on a server, a laptop, or a desktop, and therefore applies different settings to the agent (for example, remotely shutting down or restarting a PC is fine, but it's not an option that should appear in the console for servers).
Best regards,
Tom
Yes, that's what I've done so far. I've created a small script that deletes the file and replaces it with a properly configured wapt-get.ini file that is stored on one of my servers.
Installed WAPT version = 2.2.1
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
