Hello,
I have a question about installation errors on the WAPT console.
WAPT 2.6.1.17472.
I'm putting my server packages at the Organizational Unit level to avoid forgetting any.
Out of hundreds of servers... there are a few old Windows 2012 machines, unfortunately still in production.
To prevent some packages from being used by the 2012 machines because they're incompatible, I set a minimum OS:
min_os_version: 10.
Is it normal that I still see the Windows 2012 servers with this kind of error?
EWaptUnavailablePackage: Missing dependencies: tis-sysmon.
Normally, even if they have the package, it shouldn't do anything, right?
Enterprise license
: approximately 1200 PCs,
approximately 100 servers
Error: Missing dependencies and min_os_version
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: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Jonathan,
package dependency calculations are generally based on the package name without filtering on capabilities. This is the expected behavior because the WAPT agent doesn't know if it's a deliberate choice by the administrator or not.
For OU packages or AD Profile packages, these are "implicit" packages linked to the machine's state and not explicit dependencies. So you can impose restrictions on capabilities and it won't cause the problem you're experiencing.
Alternatively, you can create an empty group package with the appropriate capability for the 2012 machines, and that way they'll be happy.
Regards,
Denis
package dependency calculations are generally based on the package name without filtering on capabilities. This is the expected behavior because the WAPT agent doesn't know if it's a deliberate choice by the administrator or not.
For OU packages or AD Profile packages, these are "implicit" packages linked to the machine's state and not explicit dependencies. So you can impose restrictions on capabilities and it won't cause the problem you're experiencing.
Alternatively, you can create an empty group package with the appropriate capability for the 2012 machines, and that way they'll be happy.
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
