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.
[RESOLVED] Updating the "DN in AD" field following a domain change.
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
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.
"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.
Tranquil IT
-
croquebert
- Messages: 33
- Registration: March 30, 2022 - 5:41 PM
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?
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
The information can be retrieved here:
Therefore, it is directly retrieved by the GPO engine of your computer
The information can be retrieved here:
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Distinguished-Name-
croquebert
- Messages: 33
- Registration: March 30, 2022 - 5:41 PM
Good morning,sfonteneau wrote: ↑Feb 23, 2023 - 3:29 PM Good morning
The information can be retrieved here:
Therefore, it directly retrieves data from the GPO engine of your computerCode: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Distinguished-Name
OK, thank you. I'll look into why this field isn't updating on the client side.
