[SOLVED] AD OU display bug in the console

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Answer
esberard
Messages: 44
Registration: Oct 09, 2023 - 11:35

July 2, 2026 - 8:15 AM

Hello,

We encountered a bug yesterday regarding the display of OU information for workstations in Active Directory on the WAPT console. Unfortunately, I didn't have time to take a screenshot, as my colleague fixed the problem too quickly.

We had workstations that were in an OU whose name was historically written in all capital letters. One day, it was decided that this wasn't aesthetically pleasing, and the OU was renamed with only the first letter capitalized and the rest in lowercase.

This caused the new OU to appear in WAPT (so far, nothing unusual). However, the old OU was still present, and the machines appeared in both OUs simultaneously (old and new).

We had to delete all the machines from the OU in question for both OUs to disappear and for the machines to reconnect with only the new OU.

If this information can help you identify the bug and fix it, ;)

have a good day

. Sincerely, Rémy Esberard
High
User avatar
dcardon
WAPT Expert
Messages: 1970
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

July 2, 2026 - 12:15

Hi Rémi,

thanks for the update. Indeed, Active Directory DNs are case-insensitive, so we should sort without considering the case in the hierarchy. Note: the hierarchy is generated from the data retrieved from the workstations, not from Active Directory data (this has the advantage of accurately reflecting the workstation's state :-) ), so it might select one case or the other depending on the first workstation accessed in the console, but at least there won't be two.

Instead of deleting the entries, you could normally have just forced an inventory check so the machine retrieves the DN with the correct case. To save bandwidth and CPU, workstations send a diff of their inventory by default, and the DN update with the new case shouldn't have been forced automatically since, technically, it was still the same...

I'm submitting an internal ticket about this. I'm marking the topic as Resolved for tracking purposes.

Best regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
High
esberard
Messages: 44
Registration: Oct 09, 2023 - 11:35

July 6, 2026 - 07:26

Following our conversation, Denis, I'm pasting the details I mentioned to you here.

The forced inventory system didn't fix the problem. We could clearly see that the workstation had adopted the new part number with the new nomenclature, no problem there. It appeared correctly in the new OU in online mode, but the main bug was that it also appeared online in the old OU with the new part number in the workstation's inventory.

Basically, all the machines were showing up identically in both the old and new OUs despite having forced the inventories.

Thanks for looking into it,

Rémy.
High
Answer

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT