Univention Bugzilla – Bug 33366
Singlemaster: windows client objects created at wrong position in S4
Last modified: 2019-02-05 21:26:23 CET
This happens again with UCS@school 3.2 +++ This bug was initially created as a clone of Bug #31443 +++ If windows clients get joined on a single master, their computer objects are created in cn=computers,$ldap_base if the computer objects have not been created before. Since the windows clients objects are not within the OU-subtree of the specific school the computers cannot be assigned to a computer room. → on a single master new windows clients should be created below the standard OU if automatically created via samba.
Not really the same problem. The OpenLDAP position is correct: root@master201:~# univention-s4search cn=WIN7297* dn # record 1 dn: CN=WIN7297,CN=Computers,DC=autotest201,DC=local root@master201:~# univention-ldapsearch cn=WIN7297* dn # WIN7297, computers, School1, autotest201.local dn: cn=WIN7297,cn=computers,ou=School1,dc=autotest201,dc=local root@master201:~# Workaround: /usr/share/univention-s4-connector/univention-s4-position-sync
This also affects DC Slaves
This issue has been filled against UCS@school 3.2. The maintenance with bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016. Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.