Univention Bugzilla – Bug 36413
AD member join fails permanently if first AD member setup fails
Last modified: 2023-03-25 06:53:47 CET
Created attachment 6293 [details] management-console-module-setup.log In my test the initial AD member setup failed because the AD clock was behind the UCS clock and I received a message informing about this. I adjusted the time on the AD server and clicked on "reconfigure" in UCS system setup. The same message appears again, blocking the join permanently. The managment-console-module-setup.log shows a message indicating a different issue: The python code detected that the UCS system is already joined and refuses to try it again. See attached log. +++ This bug was initially created as a clone of Bug #35653 +++ It should be possible to configure the AD member mode in the initial system setup wizard during the installation.
Manually removing /var/univention-join/joined doesn't help much in this case: The error message is replaced by an empty error message.
*** This bug has been marked as a duplicate of bug 44035 ***
(In reply to Stefan Gohmann from comment #2) > > *** This bug has been marked as a duplicate of bug 44035 *** @Stefan: This doesn't seem to be a duplicate. Wrong bug number?
@Arvid, I guess this works now. In UCS 4.1 (or so) we added the possibility to start the join process again.