Hello,
it seems that the "Add computer to groups" feature of djoin has a very annoying bug (to say the least):
When adding a computer to an Active Directory group with 1501 or more members, the target group is completely emptied of its existing members, retaining only the computer added via this feature.
I'm not on the latest version, but I haven't seen a fix in the WAPT changelog.
Can anyone else confirm this problem?
Version used: 2.6.0.17392
WADS and adding a computer to a group
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
you've just found the (big) bug (we hadn't seen it before).
It's actually related to how Active Directory works.
https://learn.microsoft.com/en-us/previ ... -retrieval
When a group has more than 1500 members, AD doesn't return the `member` attribute but `member` with a range of 0-500.
And in our code logic, that doesn't work. It makes it look like the group is empty.
We'll fix this as soon as possible. In the meantime, it's best not to use it.
you've just found the (big) bug (we hadn't seen it before).
It's actually related to how Active Directory works.
https://learn.microsoft.com/en-us/previ ... -retrieval
When a group has more than 1500 members, AD doesn't return the `member` attribute but `member` with a range of 0-500.
And in our code logic, that doesn't work. It makes it look like the group is empty.
We'll fix this as soon as possible. In the meantime, it's best not to use it.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
We've just fixed the problem.
Sorry and thank you for the feedback.
Sorry and thank you for the feedback.
