Univention Bugzilla – Bug 48048
Improve School object
Last modified: 2023-06-12 15:45:20 CEST
During the implementation of a drop in replacement for the create_ou script using the UCS@school-lib some problems especially with handling dcs for administrative and educative dcs have come up. Some of them were already addressed in Bug #47408 To not stretch the scope of that Bug too much this Bug should focus on a better handling and validation of DC's in a School according to the intended behavior. Known aspects so far (taken from Bug #47408): I can add an already existing school which throws a "notification" but adds the edu server anyways. (I'm not sure if that is indented behavior...) Should the existing computer object be moved into the ou it will manage? New edu servers are created there.
(In reply to Ole Schwiegert from comment #0) > I can add an already existing school which throws a "notification" but adds > the edu server anyways. (I'm not sure if that is indented behavior...) can you give me an example? What do you mean by "adds the edu server anyways"? > Should the existing computer object be moved into the ou it will manage? New > edu servers are created there. Currently there is a special command for this /usr/share/ucs-school-import/scripts/move_domaincontroller_to_ou because with the moment of object movement the computer account becomes invalid and services like the listener or LDAP search will not work anymore because authentication fails. The UCS@school configuration wizard moves the slave object and then immediately call univention-join to rejoin the system with the new URL.
This issue has been filed against UCS@school 4.3 or earlier. UCS 4.3 is out of maintenance and UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.