Tranquil IT Forum

Hello everyone,

Context:
WAPT version: 2.2 Enterprise
Server OS: Debian 11
Administration console OS: Win10pro
Package development workstation OS: Win10pro

We have migrated workstations with the WAPT agent to a new Active Directory domain.

In the WAPT console, the domain controller field updates correctly and points to the domain controller of the new domain.
However, despite restarting the WAPT agent on the client, the "DN in AD" field still points to the DN of the old domain controller: consequently, the PC does not appear in the hierarchy of the new domain controller and cannot correctly apply OU packages.
How can I force the "DN in AD" field to update?

Best regards,

Christophe.

You can force an inventory update in the console using the
"Refresh workstation inventory"
from the context menu of all workstations.
You must select the workstations you want to update. Only connected workstations will receive the command.

htouvet wrote: ↑Feb 21, 2023 - 6:21 PM You can force an inventory update in the console using the
"Refresh workstation inventory"
from the context menu of all workstations.
You must select the workstations in question. Only connected workstations will receive the command.

Good morning,

Thank you for your feedback.

Despite restarting the workstation and refreshing the workstation inventory in the console, the "DN in AD" field still points to the DN of the old domain controller.
Do you have the command used by the WAPT inventory to retrieve this DN in order to verify what it returns live on the workstation?

Good morning

The information can be retrieved here:
Therefore, it is directly retrieved by the GPO engine of your computer

sfonteneau wrote: ↑Feb 23, 2023 - 3:29 PM Good morning

The information can be retrieved here:

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Distinguished-Name

Therefore, it directly retrieves data from the GPO engine of your computer

Good morning,

OK, thank you. I'll look into why this field isn't updating on the client side.