AD linking > packet groups

[zeyf]

Hello,

I'm a new WAPT user, and I find your solution full of potential!
However, since I'm posting here, it's because I'm encountering a small problem.

I'm using WAPT 1.2.3.2 on a Windows machine.
Eventually, the solution will be deployed on approximately 800 workstations distributed across different Active Directory groups.
Therefore, I'm trying to match my package groups with my groups in Active Directory.

To do this:
I log into the console as a domain administrator.
I select a test machine and add it as a client in the console.
I create a package group with the same name as the Active Directory group of my test machine.
I assign a default group to my machine to avoid the error: exceptions.KeyError: 'depends'.
In the inventory section, I right-click on the test machine and then select: "Add AD groups as package dependencies".

From this point on, I don't get an error message, but the console returns: "0 machines modified." And indeed, my test machine isn't accepting the "AD" group.
Could you tell me if I've missed something in my steps or misunderstood a particular one, please?
I read in a forum post that the "Add AD groups as dependent packages" function should be located in the package groups, but I can only find it on my machines.

I haven't found any information on your wiki, but I think I followed the steps suggested in a thread on your forum.

Thank you in advance if you can help me move forward because, I confess, I'm stuck ^_^'

Sincerely,
Zeyf

[sfonteneau]

Hello,

I just tested it and it works for me.

I created a group in my Active Directory ("Global", "Security") with the same name as my software group in WAPT (administrative).

In AD, I added my PC (company account) "pc-compta" to my newly created "Administrative" AD group.

I logged into an AD session, then I logged into the WAPT console.

I used CTRL-A to select all the PCs in the console.

Then I clicked "Edit" and then "Add AD groups as package dependencies."

And it works!

Simon

[zeyf]

Hi Simon, and thanks for your reply.

Unfortunately, I can't create a test group on my Active Directory.
So, I'm creating my package group from an existing AD group, but I don't think that's a problem.
However, my group names contain hyphens ("-"). Could that be related?

The only other difference I notice is that I'm not on my domain administrator Windows account, but I'm launching the console "as" a domain administrator.
To clarify, I'm connecting to the console locally.

In any case, if I find the reason, I'll post the solution/reason here.

Zeyf

[sfonteneau]

Hello

, I think it's the Windows APIs that are used to contact Active Directory, so if you log in with an account that doesn't have access to the AD group list, it will generate an error, in my opinion.

Regarding the minus sign, I just tested a group with it and it works for me.

What's certain is that your test PC must be a member of your group in Active Directory. (Can you confirm this for me?)

Simon

[zeyf]

Hello,

Thank you for confirming about the "-"; all my AD groups have it, so I couldn't test without it.

I confirm that my test PC is indeed in the AD group: I'm running my test using the original group in which the workstation is located.

I tried with another machine in the same group, but the problem remains.

Now, I'm considering two possibilities:
- Is there a specific parameter to set in the group? The section, for example, even though the console doesn't save my change tests?
- The creation of my client installer?
I went through Tools/Create a WAPT Agent, then I retrieve the installer on my target machine and run it. Nothing particularly unusual, but isn't there something to configure on the client side?

Even though it doesn't seem like a problem, for the moment my WAPT console is running on my machine. I might install it on a dedicated machine permanently in the coming days to eliminate any doubt on this point.

Thanks again for your help!

Zeyf

[sfonteneau]

I can confirm that there are no specific parameters to set in the wapt software group.

I can also confirm that it doesn't need to do anything special in the client installer.

In fact, the wapt console simply reads the AD groups (not to be confused with OUs) and their members (the PCs).

If there's a match, it modifies the wapt package on the PC to add the group to the `depends` field of the wapt machine package.

[zeyf]

Hello,

I'm still stuck and busy with other tasks at the same time; but I haven't given up!
My machines belong to several security groups simultaneously (domain computer and its machine group).
Do you think this could be causing the problem?

I'd appreciate it if anyone has encountered the same issue or if you have any suggestions.

Thank you in advance for your feedback.

Best regards,
Zeyf

[zeyf]

Hello,

I'm following up on this issue.
I reinstalled my server on a new machine (the configuration remains the same as in my first post),
checked the group membership of my test machine using `gpresult /r`,
and verified its membership in the correct AD group (global security group).
I created a group with the same name as my AD group in the console.
Just to be sure, I also created groups named after the group's SID and GUID.

I'm still stuck with the exact same result.
There's no error message and "0 machines modified,"
yet I'm installing everything exactly as described in the documentation.

If anyone has any suggestions to help me move forward, I'd be very grateful.

PS: To get around this problem, do you think it's possible to predefine a group directly in the client installer? That way, I could still create one installer per group and deploy the installer based on the machine.

Best regards,
Zeyf

[ryoken95]

Hello,

I'm also looking for a solution; I have exactly the same problem.

Regards

[Floflobel]

Hello,

you just need to assign it to another group.
In my case, World, which represents all the computers in Active Directory.
No need to add this group to Active Directory. This trick works for me; let me know how it goes!