Hello,
I'm currently thinking about creating my machine groups. Naturally, when I learned about Unit-type packages and what they offer, I immediately started searching everywhere for information on how they worked.
But I can't find anything... neither in the documentation nor on the internet... nothing at all.
My question is therefore quite simple: do Unit packages exist in the Community Edition? If so, how can I create them?
Louis
Unit-type packaging: myth or reality?
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 :
That's right!
However, since this is primarily a feature of the Enterprise Edition,
absolutely nothing is done to make creating a Unit package easier in the Community Edition...
In the Enterprise Edition, however, creating Unit packages is seamless through the
Simon
However, since this is primarily a feature of the Enterprise Edition,
absolutely nothing is done to make creating a Unit package easier in the Community Edition...
In the Enterprise Edition, however, creating Unit packages is seamless through the
Simon
-
louisinger
- Messages: 27
- Registration: June 26, 2018 - 09:40
Is it therefore possible to create Unit packages in the community version?
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Yes.
EDIT:
Yes, in the sense that the code to manage unit packages is in the WAPT agent code.
However, this remains a feature of the enterprise version and is not planned for use in the community version.
EDIT:
Yes, in the sense that the code to manage unit packages is in the WAPT agent code.
However, this remains a feature of the enterprise version and is not planned for use in the community version.
-
louisinger
- Messages: 27
- Registration: June 26, 2018 - 09:40
Could you give me an overview of this? Or do you have any additional documentation on the subject?
Thank you in advance.
Thank you in advance.
-
louisinger
- Messages: 27
- Registration: June 26, 2018 - 09:40
I don't understand the point of including a feature in the community version if they're going to do nothing to make it easier to use. They might as well put it in the enterprise version right away. WAPT is a superb tool, but this mentality benefits no one...
I'll manage with Unit packages, thanks!
I'll manage with Unit packages, thanks!
The concept of a package associated with an organizational unit is not integrated into the community version.
We chose to have the core of the WAPT agent (and especially the security functions) as common as possible between the two versions because it's less expensive to develop and test (the so-called "community" version requires people's time that needs to be paid... just as you may have been paid for your work).
If you create a unit package manually and it works for you, that's great; that's the spirit of open source.
But creating documentation for that takes time.
In terms of "mindset," I think we're quite respectful of our "community," as evidenced by the answers we provide regarding the operation of the "community" version and the relatively detailed documentation.
We chose to have the core of the WAPT agent (and especially the security functions) as common as possible between the two versions because it's less expensive to develop and test (the so-called "community" version requires people's time that needs to be paid... just as you may have been paid for your work).
If you create a unit package manually and it works for you, that's great; that's the spirit of open source.
But creating documentation for that takes time.
In terms of "mindset," I think we're quite respectful of our "community," as evidenced by the answers we provide regarding the operation of the "community" version and the relatively detailed documentation.
Tranquil IT
Hello,
Following Hubert's response, I am closing this thread. If you require any support with your request, please do not hesitate to contact us directly by phone at 02.40.97.57.55.
Have a good day.
Following Hubert's response, I am closing this thread. If you require any support with your request, please do not hesitate to contact us directly by phone at 02.40.97.57.55.
Have a good day.
Camille FARGUES,
Account Manager
Account Manager
