12 April,16 at 11:46 AM
Applies to: DirectControl 4.4.0 and above on all platforms
Question:
Why does adjoin fail with an error "invalid container" error message even though correct container name was provided for (-c) flag ?
Example:
admins-mac-mini:~ admin$ sudo adjoin -z dztest -c services ajax.org -u jdoe
jdoe's Active Directory password:
Using writable domain controller: dc01.ajax.org
Error:invalid container specified in argument
Join to domain 'ajax.org', zone 'dztest' failed.
Answer:
Starting from DirectControl 4.4.0 onwards, adclient accepts full/relative Distinguished Name and full canonical name only.
<snip from man pages for adjoin >
-c, --container container DN
The container DN specifies the distinguished name (DN) of the container or Organizational Unit in which to place this computer account.
You can specify the containerDN by:
- Canonical name (ajax.org/unix/services).
Note: You cannot specify a partial name for the canonical name.
- Fully distinguished name (cn=services, cn=unix,dc= ajax,dc=org)
- Relative distinguished name without the domain suffix(cn=services,cn=unix)
In the above example, you need to specify the adjoin command as follows:
Relative DN:
admins-mac-mini:~ admin$ sudo adjoin -z dztest -c "cn=services,cn=unix" ajax.org -u jdoe
Or Full DN:
admins-mac-mini:~ admin$ sudo adjoin -z dztest -c "cn=services,cn=unix,dc=ajax,dc=org" ajax.org -u jdoe
Or Full Canonical Name:
admins-mac-mini:~ admin$ sudo adjoin -z dztest -c "ajax.org/unix/services" ajax.org -u jdoe