default group

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
seb b
Messages: 23
Registration: Oct 26, 2017 - 3:12 p.m.

March 26, 2018 - 4:27 PM

Hello,

I'm still on version 1.3 for a while longer, but I'd like to know if it's possible to define a default group for workstations after the agent is installed.

Let me explain: during workstation setup, the WAPT client is installed via a post-installation script.
I also have a software suite that needs to be installed on all workstations without exception (antivirus, browser, and others).

The problem is that while it's easy to keep the WAPT agent up to date, it's much harder for the other software, making it very tedious to manage post-installation. Therefore, I'd like to have a default group where all machines are placed when they appear on the server, so I only have to keep my WAPT packages up to date and the software suite installs automatically.

Thank you for your replies.

Seb
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :

March 26, 2018 - 4:32 PM

Good morning,

This default package group assignment behavior is only available in version 1.5 Enterprise with Organizational Unit packages: https://youtu.be/UAO0dykMH5w?t=1509

Another solution is to add a script to the system startup via GPO that installs the packages from the command line:

Code: Select all

wapt-get install grp-socle antivirus
seb b
Messages: 23
Registration: Oct 26, 2017 - 3:12 p.m.

March 26, 2018 - 5:01 PM

Thanks,

since I'm stuck on version 1.3 for the moment, the script solution remains.
I had considered it, but it won't work for non-domain machines.

Thanks again.
User avatar
vcardon
WAPT Expert
Messages: 278
Registration: Oct 06, 2017 - 10:55 p.m.
Location: Nantes, France

March 26, 2018 - 9:49 PM

Hello,

For those who would like assistance upgrading from 1.3 to 1.5 while remaining in the Community Edition, we have a service that allows you to do just that. It costs €600 excluding VAT, so it's very affordable, and the session takes place over a morning or afternoon.

Beyond a fully functional, turnkey upgrade to the latest version, you'll be contributing to the funding and sustainability of the software and enjoying a mutually enriching experience with WAPT's main developers.

Please note that version 1.3 will quickly become obsolete as all package repositories will begin migrating to 1.5, so you'll soon find yourself quite alone in 1.3.

Sincerely,

Vincent
Vincent CARDON
Tranquil IT
Locked