Univention Bugzilla – Bug 42910
Appliance could not be joined because the license on the DC Master is not activated.
Last modified: 2018-01-16 18:33:02 CET
4.1-3 errata239 (Vahr) The setup shows: """ Kopano Core Appliance could not be joined because the license on the DC Master is not activated. """ Remark: ???
ownCloud Appliance could not be joined because the license on the DC Master is not activated. Reported again, 4.1-4 errata420 (Vahr) I think we should also improve this sentence to be more expeditionary.
Reported again, 4.1-4 errata420 (Vahr)
Reported again, 4.1-4 errata430 (Vahr)
Reported again, 4.1-4 errata439 (Vahr)
Reported again, 4.2-1 errata118 (Lesum)
Version: 4.2-1 errata118 (Lesum)
Version: 4.1-4 errata439 (Vahr)
The check for the license has been moved after checking the SSH connection. If this fails one cannot switch to the next page, so it is ensured the join process can't be started if the license is disabled. The error message has slightly been improved. The wrong IP address was used in certain scenarios, e.g. if the nameserver is not the UCS DC Master. This has been fixed as well so that the address of the DC Master is taken. univention-system-setup (10.0.10-47) 8f592aeee9cc | Bug #42910: fix check of license in an appliance scenario univention-systen-setup.yaml 5f6567b20699 | YAML Bug #42910
OK Error shown when joining into UCS Domain (without license) OK Error shown when joining into AD Domain with existing UCS master (without license) OK Error message OK YAML (64b1b33 Bug #42910: YAML - update version) -> verified
<http://errata.software-univention.de/ucs/4.2/227.html>
Reported again: Version: 4.2-2 errata216 (Lesum)
ownCloud Appliance kann nicht gejoined werden. Es liegt keine aktivierte Lizenz auf dem DC Master vor.
Reported again: Version: 4.2-2 errata216 (Lesum) ownCloud Appliance could not be joined because the license on the DC Master is not activated.
Reported again: Version: 4.2-2 errata216 (Lesum) Remark: check this Ticket#2017121421000131