Description Sönke Schwardt-Krummrich 2019-07-10 12:29:03 CEST

The UCS@school admin manual has to be adopted for the new installation step.

+++ This bug was initially created as a clone of Bug #49271 +++

When installing a domaincontroller slave the customers are not aware of the fact that for school servers the school has to be created on the domaincontroller master and the computer name of the school server has to be specified beforehand. Currently, more and more slaves are being unintentionally installed as central slaves, which means that the domaincontroller slave systems have to be completely reinstalled (among other manual steps).

If the credentials for joining have been specified in the installer (system setup), the credentials should be used to check whether the master is a UCS@school domain. If this is the case, an additional page in system setup is displayed to the customer asking whether the slave should become a central slave or a school server. If the selection of the customer *does not* match the LDAP settings (e.g. school is missing), a warning with instructions is displayed.

If no join credentials are specified by the customer because the join is to take place later, the installer could try to determine whether the master recognized in the DNS is a UCS@school system and then point out again that a school must be created BEFORE for school servers (concrete instructions should be included).