Univention Bugzilla – Bug 42539
AD Member Mode: Document how to join new UCS systems to existing UCS in Member Mode
Last modified: 2023-03-25 06:55:32 CET
UCS 4.1-3 errata 282 Windows Server 2012 R2 I joined a first UCS system as part of an existing Active Directory domain (AD Member Mode). This went fine. Afterwards, I wanted to add an UCS Memberserver to this domain. It is unclear ... * what should be the "preferred DNS server", UCS or Windows? * which bullet point during installation/configuration needs to be checked for this second UCS system: ** Join into an existing Active Directory domain ** Join into an existing UCS domain 1. Choosing the first option (join AD domain) with the AD DC as "preferred DNS server" seems to work. The UCS Master can be found via DNS, the join succeeds and there is a computer account in the UCS OpenLDAP and in Active Directory. "Windows-compatible Memberserver" was automatically installed. → But unfortunately, Bug 42538 2. Choosing the second option (join UCS domain) with the AD DC as "preferred DNS server" fails. Somehow the system setup picks the Windows AD DC as the "domain controller master" for the join and the authentication on the page "Domain join information" fails with "Connection refused". You can untick the option "Search domain controller master in DNS" and correct the FQDN to match the real UCS Master. "Windows-compatible Memberserver" needs to be selected manually. I was able to finish the installation and the join. univention-check-join-status -> OK net ads testjoin -> OK Computer account is present in AD -> OK 3. Choosing the second option (join UCS domain) with the UCS Master as "preferred DNS server" seems to work, too. The system setup picks the UCS Master as "domain controller master" for the join. "Windows-compatible Memberserver" needs to be selected manually. univention-check-join-status -> OK net ads testjoin -> OK nameserver1 is changed to the Windows AD DC -> OK Computer account is present in AD -> OK Long story short: We should agree on one way how to do this and document it.
Move setup issues to 4.2-0-errata.
I think we should first fix the product: Bug #44035
Bug #42538 and Bug #43745 have been fixed which should make the installation much easier. Both examples 2 and 3 should work if not it is a bug in UCS. My tests were successful but I've used UCS 4.3. We have currently documented it in this way: If the UCS system is to join a Windows Active Directory domain during the installation, the IP address of an Active Directory domain controller system should be specified as the DNS server. This is essential for the automatic detection of the Windows Active Directory domain controller to function. https://docs.software-univention.de/manual-4.3.html#installation:Netzwerkkonfiguration
yes, setup and documentation have improved.