Tranquil IT Forum

Hello,

I would like to know if it's possible with WAPT to automatically apply a package group based on the domain a machine belongs to, or even better, the OU (Organizational Unit) it belongs to?

I know I could use the machines' FQDNs and define a dependency package group, but with a large number of machines, this would quickly become cumbersome.

Thank you in advance for your suggestions

Yes we can!! (in version 1.2.2)
If you launch the WAPT console from a domain-joined machine with a domain account, and right-click on one or more machine packages, a new entry will appear in the menu: Add AD groups as dependent packages. This action will search Active Directory for groups with the same name as the WAPT group packages. If matching groups are found, WAPT will add the machines that are members of the AD group to the WAPT group. (How many machines do you have to manage with WAPT?)

Regards

Thank you for your reply.

I'm currently using version 1.1.1, so I'm eagerly awaiting the final release of 1.2.2 .

For now, I don't have many workstations to manage, as I'm working (as an intern) on OS and software deployment, and only new machines have WAPT installed. But eventually, the entire network, approximately 1500 workstations, is slated to be managed by WAPT.

Hello,

I just updated my WAPT server from version 1.1.1 to 1.2.3.

I then tried to set up dependencies related to Active Directory groups.

I created a "test" group on my Active Directory server, and then a "test" dependency group on WAPT.

Next, using the WAPT console, I right-clicked and selected "Add AD groups as package dependencies," but I get the following error:
exceptions.KeyError: 'depends'.

Do you know what this error means?
Could you explain how to create dependency groups linked to Active Directory, as there's no documentation on this in the wiki (or at least, I haven't found any)?

Thank you in advance, best regards.

We encountered the same problem on our installation.

The problem arises for machines that don't yet have an associated configuration (no "machine package").
This is a bug that needs fixing.
To work around it, assign a package group (even an empty one) to the machines beforehand (using the "Add a package or package group" option).

Hubert

Yes, it's working now. Thank you very much, Hubert.

And does the AD group need to be specific (local/global/universal domain, security/distribution), or will any type of AD group work?

I imagine it shouldn't have too much of an impact.
I tested it with a Global Scope / Security Type group.