Hello and thank you for your reply, Floflobel.

I'm not sure I fully understand your solution.
I created a WAPT group and added my machine to it to avoid the known bug.
Once in the group, I tried to add it to the AD groups.
Is there something I...

Hello,

I'm following up on this topic.
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`,
verified its membership in the correct AD group (global security group),
created a...

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'm still open to suggestions...

Hello,

thank you for the confirmation about the "-" ;) all my AD groups have them, so I couldn't test without them.

I confirm that my test PC is indeed in the AD group; in fact, I'm running my test using the original group in which the computer is located.

I tried with another...

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 the issue?

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 spread across different groups...