AD Groups / WAPT Groups

[elk]

Hello everyone,
I'm currently testing and evaluating WAPT (latest version), and now that all the agents are installed and appearing in the console, we'd like to deploy a group of common applications across all workstations.
I read on the forum (viewtopic.php?f=13&t=770&p=2364&hilit=A ... tory#p2364) that it's possible to create an Active Directory group (containing all the desired computers) and then create a group with the same name in the WAPT console. From what I've also read, you then need to select all the computers in the console and choose the "Add AD groups as dependency packages" action.
That's what I did, but unfortunately, when I perform this action, a popup titled "waptconsole" appears with the following message: "0 machines modified, 1 machine ignored (error), 0 machines unchanged."

I'm not sure which logs to look at to try and solve the problem. Furthermore, I would like confirmation that this behavior is still implemented in the latest version of Wapt (so as not to try to get something working that no longer functions).

Thank you in advance for your answers.

Sincerely,

[elk]

I just realized that this behavior is also described in the official documentation (https://www.wapt.fr/fr/doc/Utilisation/ ... de-paquets "If you name a group with the same name as a machine group in your Active Directory (Microsoft or SaMBa4), then the machines in the AD group will be assigned to the WAPT group.").
So I have part of my answer: it should work.
But as mentioned, it doesn't work (message "0 machines modified, 1 machine ignored (error), 0 machines unchanged" when selecting the "Add AD groups as dependent packages" action).

Sincerely,

[elk]

Hello,

I recently reported that the expected functionality (AD groups/WAPT groups mapping) is not working in a freshly installed version of WAPT (1.5.1.23).

I understand that patience is required, however, we are pressed for time and need a clear and precise answer regarding this functionality described in the official WAPT documentation.

Should we conclude that the AD/WAPT groups mapping feature described in the documentation does not work in the WAPT community version?

Thank you in advance to the WAPT developers/admins for your response.

Sincerely,

[vcardon]

Should we conclude that the AD/WAPT group mapping functionality described in the documentation does not work in the WAPT community version?
Regards,

This is a feature that works great in the Enterprise version; perhaps we should be more specific in the documentation?

I recently watched Simon demonstrate this Enterprise feature the other day at a regional branch of the CPAM and it worked just too well, the guys were positively surprised and just won over.

With the Community edition, TIS delivers on its promise to provide system and network administrators with a tool to deploy, update, and remove software and configurations. For large networks or organizations seeking better Active Directory integration or improved auditability/traceability of actions, the Enterprise edition is the right choice.

Sincerely.

Vincent

[sfonteneau]

Hello,

the function mentioned by wapiti (Add AD groups as a dependent package) no longer works in version 1.5.

We need to fix this. We haven't had time to do it yet.

Simon

[sfonteneau]

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *
from active_directory import *

uninstallkey = []

def get_computer_groups():
    """Try to finc the computer in the Active Directory
        and return the list of groups
    """
    groups = []
    computer = find_computer()
    if computer:
        computer_groups = computer.memberOf
        if computer_groups:
            if not isinstance(computer_groups,(tuple,list)):
                computer_groups = [computer_groups]
            for group in computer_groups:
                # extract first component of group's DN
                cn = group.split(',')[0].split('=')[1]
                groups.append(cn.lower())
    return groups

def install():

    for group in get_computer_groups():
         if WAPT.is_available(group) :
            WAPT.install(group)
            

Here is a quick workaround.

This wapt package allows listing the groups to which the machine belongs; if a group has the same cn as a wapt group, then the installation will be launched.

Simon

[elk]

Should we conclude that the AD/WAPT group mapping functionality described in the documentation does not work in the WAPT community version?
Regards,

This is a feature that works great in the Enterprise version; perhaps we should be more specific in the documentation?

Hello Mr. Cardon, thank you for your reply. From what I've read, this feature existed until recently in the Community version. Therefore, it's not so much the documentation that needs clarification, but rather the evolution of your choices and strategies (which are yours and perfectly valid).
Indeed, if you no longer wish to maintain this feature in the Community version, this should be clearly stated (it's a waste of time trying to keep something working that no longer functions), at least in the changelog and documentation

I recently watched Simon demonstrate this Enterprise feature the other day at a regional branch of the CPAM and it worked just too well, the guys were positively surprised and just won over.

I don't doubt it in the slightest

With the Community version, TIS delivers on its promise to provide system and network administrators with a tool to deploy, update, and remove software and configurations. For large networks or organizations seeking better AD integration or improved auditability/traceability of actions, the Enterprise version is the right choice.

Regards,

Vincent

Mr. Cardon, we are well aware that the Enterprise version of WAPT is a natural evolution from the Community version for companies seeking true Active Directory integration (in our case, that's all we're interested in; the other features offered by the Enterprise version aren't yet essential for our use: two people in the IT department). It would be a real advantage. In any case, and quite naturally, we want to get to grips with this very powerful tool, familiarize ourselves with the Python language, and give ourselves at least a year to evaluate it. In the long run, it's very likely that we'll subscribe to additional services and features.

In conclusion, clarity and communication about your strategic/functional choices are important and I repeat, these choices belong to you and I respect them.

Thank you again for your response and this exchange.

Sincerely,

[elk]

Hello,

The function mentioned by wapiti (Add AD groups as a dependent package) no longer works in 1.5.

We need to fix this. We haven't had time to do it yet.

Simon

Hello Mr. Fonteneau, thank you for your clear and concise answer, as it was exactly what I needed to know (works or no longer works)
I imagine you have very busy days and I understand that the correction may take some time.

Thank you again.

Sincerely,

[elk]

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *
from active_directory import *

uninstallkey = []

def get_computer_groups():
    """Try to finc the computer in the Active Directory
        and return the list of groups
    """
    groups = []
    computer = find_computer()
    if computer:
        computer_groups = computer.memberOf
        if computer_groups:
            if not isinstance(computer_groups,(tuple,list)):
                computer_groups = [computer_groups]
            for group in computer_groups:
                # extract first component of group's DN
                cn = group.split(',')[0].split('=')[1]
                groups.append(cn.lower())
    return groups

def install():

    for group in get_computer_groups():
         if WAPT.is_available(group) :
            WAPT.install(group)
            

Here is a quick workaround.

This wapt package allows listing the groups to which the machine belongs; if a group has the same cn as a wapt group, then the installation will be launched.

Simon

Great!!!!! Thank you so much!!!!!! We'll use this method until the feature returns in version 1.5

Have a great day!.

Sincerely,

[sfonteneau]

The solution we would potentially to propose is to integrate this code into the agent.

This would avoid assigning this package to each machine.