Univention Bugzilla – Bug 48743
UMC wizard for schools has to allow the specification of administrative slaves
Last modified: 2019-03-12 10:58:44 CET
UMC wizard for schools has to allow the specification of administrative slaves because otherwise it's no longer possible to create administrative slaves via the UMC after the "samba simplification" had been merged.
Previously, the computer account of the management slave was created automatically via the UCS@school configuration wizard, which was used to install UCS@school on the relevant DC slave. With the implementation of Samba simplifications in UCS@school 4.4, it is necessary that the computer account of the administration slave has already been created in LDAP before the join process, since UCS@school is automatically installed and provisioned during the join process. The UCS@school "Schools" wizard has therefore been adapted in such a way that the name of the administration slave can also be specified in addition to OU, DisplayName and name of the educational slave. The name of the educational slave must always be specified, as this is necessary for the creation process of the OU. 4f15a78da Bug #48743: update advisory b71f381d8 Bug #48743: add changelog entry 915aa909d Bug #48743: allow creation of administrative slaves via the UMC module "schools" Package: ucs-school-umc-wizards Version: 11.0.0-3A~4.4.0.201902240132 Branch: ucs_4.4-0 Scope: ucs-school-4.4
Changelog: OK Advisory: OK (I guess the other advisories were just fixups of previously missing updates) Package installs: OK The addition of administrative servers is now possible and subjects to the established restrictions in naming and edu!=admin. Upon creation the role at the server object is set/updated. There are two caveats I encountered during testing: ?: If you specify the master as the administrative server the creation in the wizards finishes without any error, but of course neither a role at the master is set/updated nor an administrative server is saved at the school object. Though I am not sure this is part of this bugs scope (if at all it needs to be addressed in the ucsschool.lib) ?: If you specify a previously joined dc the computer objects role is updated, but it is not moved into the OU in the LDAP structure. I am not entirely sure if this behavior is correct, but should anyway not be in the scope of this bug. REOP: Little typo in the new en-tooltip: "[...] A administrative [...]" -> "[...] An administrative [...]" Otherwise it works as expected.
(In reply to Ole Schwiegert from comment #2) > Advisory: OK (I guess the other advisories were just fixups of previously > missing updates) → yes > ?: If you specify the master as the administrative server the creation in > the wizards finishes without any error, but of course neither a role at the > master is set/updated nor an administrative server is saved at the school > object. Though I am not sure this is part of this bugs scope (if at all it > needs to be addressed in the ucsschool.lib) > > ?: If you specify a previously joined dc the computer objects role is > updated, but it is not moved into the OU in the LDAP structure. I am not > entirely sure if this behavior is correct, but should anyway not be in the > scope of this bug. → moved to bug 48763 > REOP: Little typo in the new en-tooltip: "[...] A administrative [...]" -> > "[...] An administrative [...]" → fixed > Otherwise it works as expected. → Great! Package: ucs-school-umc-wizards Version: 11.0.0-4A~4.4.0.201902261157 Branch: ucs_4.4-0 Scope: ucs-school-4.4 b86d53914 Bug #48743: fixed typo in tooltip
Typo has been fixed -> OK -> Verified
UCS@school 4.4 v1 has been released. https://docs.software-univention.de/release-notes-ucsschool-4.4v1-de.html If this error occurs again, please clone this bug.