Hello,
I'm currently testing WAPT Enterprise.
For my test, I have a machine located in an Active Directory Organization (OU).
The AD directory tree and the machine appear correctly in the console.
I placed a package in the root unit of the AD: the package installed normally on the PC.
Then I placed another package in the OU containing my machine.
This is where a problem arises: the unit in this OU is not recognized by my machine, and the packages were not installed, even though the machine is correctly placed in the OU in the console.
Does anyone have any ideas?
Thanks in advance.
Guillaume
[SOLVED] Packages in an OU fail to install
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,
have you updated the machine? (checking for updates)
Simon Fonteneau
have you updated the machine? (checking for updates)
Simon Fonteneau
Hello,
Thank you for your reply.
On my machine, I typed the command "wapt-get update". In the console, I also selected the OU and clicked on "Start Installations" (the same on the machine).
I also restarted the PC several times and repeated the operations. In all cases, there was no change.
A few clarifications:
I created a group in which I added packages as dependencies and assigned the group to the OU. I don't know if this is the correct way to do it.
Assigning the group directly to the machine works perfectly.
Guillaume
Thank you for your reply.
On my machine, I typed the command "wapt-get update". In the console, I also selected the OU and clicked on "Start Installations" (the same on the machine).
I also restarted the PC several times and repeated the operations. In all cases, there was no change.
A few clarifications:
I created a group in which I added packages as dependencies and assigned the group to the OU. I don't know if this is the correct way to do it.
Assigning the group directly to the machine works perfectly.
Guillaume
Server: WAPT Enterprise 2.4.0.14143 on Debian
Console: Windows 10
Infrastructure: Windows
Console: Windows 10
Infrastructure: Windows
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello GF68,
are there any special characters in the OU in question (accents, quotes, etc.)? There have been bugs related to this in the past.
Regards,
Denis
are there any special characters in the OU in question (accents, quotes, etc.)? There have been bugs related to this in the past.
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
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
