Hello,
I'd like to understand something about package maturity.
I've set the maturity level of a group of computers to DEV to test packages before deployment across the entire network.
I believe that as soon as I set a package to DEV, it should be automatically retrieved by all computers with DEV maturity. However, I've noticed that it must be applied to the OU (Organizational Unit).
In this case, the machines in the OU that don't have DEV maturity can see the package (their status changes to TO UPGRADE), but they can't install the software, which is expected.
Could you please tell me the correct procedure?
[RESOLVED] Packet Maturity
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
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Tchoko,
maturity is a way of selecting packages from among several available packages. If you have a package on an OU, it means that all packages must have that package, and therefore you must have the same package in both PROD and DEV environments; otherwise, there will be missing packages—this is by design.
Could you please indicate in the documentation which page is unclear regarding this issue?
Regards,
Denis
maturity is a way of selecting packages from among several available packages. If you have a package on an OU, it means that all packages must have that package, and therefore you must have the same package in both PROD and DEV environments; otherwise, there will be missing packages—this is by design.
Could you please indicate in the documentation which page is unclear regarding this issue?
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
Actually, the documentation explains how to change the maturity of packages. However, it doesn't specify that the maturity should be changed when applying test packages.
I was able to find the solution to my question using common sense.
When applying to the OU, you need to click on "view more attributes" and choose the maturity on which to apply the updates. See the link below.
Thank
you. I'm marking this as resolved.
Actually, the documentation explains how to change the maturity of packages. However, it doesn't specify that the maturity should be changed when applying test packages.
I was able to find the solution to my question using common sense.
When applying to the OU, you need to click on "view more attributes" and choose the maturity on which to apply the updates. See the link below.
Thank
you. I'm marking this as resolved.
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Tchoko,
thanks for the feedback.
As with the other post, I've removed the image linking to remote content. Images should be included directly in posts (see forum rules). It's more practical; you can see the image directly. It's also better for security, because you never know what you're clicking on when you go to a Google Drive. And it's better for long-term preservation, since files on Google Drives are constantly being moved.
Regards,
Denis
thanks for the feedback.
As with the other post, I've removed the image linking to remote content. Images should be included directly in posts (see forum rules). It's more practical; you can see the image directly. It's also better for security, because you never know what you're clicking on when you go to a Google Drive. And it's better for long-term preservation, since files on Google Drives are constantly being moved.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
