Organizational units and machines outside the domain

[seb b]

Good morning,

I am setting up wapt enterprise (1.8.2, Debian server, W10 administration machine) and I would like to understand how the presentation by OU works in the console.
I followed the documentation in order to make the out-of-domain workstations appear in a "fake" OU and everything works until the workstation is reintegrated into AD.
At this point, the OU containing the workstation does not override the previously defined false OU. Uninstalling the package didn't help (which is expected). Deleting the line

Code: Select all

host_organizational_unit_dn

The configuration file shows the workstation appearing in the "computers" OU of the AD tree (it's not there, it's at least three levels lower)

So I'm asking myself the following questions:

• Are the job unit information details dynamic?

• Where are they getting this information? Perhaps the configuration of my test machine is causing the problem

• If this behavior is desired, is it possible to modify the configuration file via a startup script that would perform something like a WMI query to retrieve the OU and write it to wapt-get.ini? (It's not very elegant, but it's the only way I can think of.)

Thank you in advance for your clarifications

[sfonteneau]

Good morning

I just did the test:

Code: Select all

[global]
host_organizational_unit_dn=OU=toto,DC=tata,DC=fr

then a:

Code: Select all

wapt-get register

And it works well

Can you confirm that this works for you?

[seb b]

Hello,

yes, it works perfectly in that direction (I just retested it using a package and manually).

However, if I rejoin the machine to the domain, it doesn't position itself correctly in the directory tree (sorry if I'm not being clear).

[sfonteneau]

Can you contact us by phone (as you have support) because I don't quite understand.

[dcardon]

Hello seb_b,

Hello,

yes, it works very well in that direction (I just retested via a package and manually).

However, if I rejoin the machine to the domain, it doesn't position itself correctly in the directory tree (sorry if I'm not clear).

Joining a machine to the domain does not remove the host_organizational_unit_dn parameter from the wapt-get.ini file. And this parameter takes precedence over the machine's OU membership.

After integrating the machine, you can push a cleaning pack. You can take inspiration from https://store.wapt.fr/store/tis-wapt-conf-policy

Sincerely,

Denis

[seb b]

Hello,

yes, I think it would be best to call you.
I'll contact you as soon as I have the number.

Thanks again.