Hello all, and thanks for your help. I am slowly making my way through error after error on this upgrade and have owncloud installed and accessible, but no AD connection as it was before the upgrade. I am using a single Univention Server in domain controller master role with AD connector installed to connect to a windows server 2012 domain. It appears Samba4 is not installed and somehow got dropped out during the process, likely when I was trying to fix the schannel error before the upgrade. Now the Univention server is back up and running with all join scripts finished except owncloud. Wekan is up and running and still allows logins from Windows domain users present before the upgrade. In checking up on samba4, it shows as not installed, neither is S4 connector. owncloud is not registering Ad connected users nor allowing logins through Ad. The join script shows incomplete, but the interface is available … really need some help - can I just install samba 4 and let it rerun to join the Active Directory, or is it included in the AD connector somehow?
Would it work to uninstall AD Connector and reinstall?
I’ve installed a fresh copy of UCS as the only AD controller (so, primary). After extensive troubleshooting on why no clients could see CIFS shares, I found that Samba wasn’t installed.
Did you find out the next course of action for your issue?
I’m keen to find out before committing to UCS, as I’m hoping to transfer LDAP & NAS duties from two separate nodes to this new UCS node.
I have the same problem with a freshly installed UCS 5.2:
When I try to install the app “Active Directory-compatible Domain Controller” it gives me the error:
This operation causes problems in the following packages that cannot be resolved:
univention-samba4
univention-s4-connector
When I try to install samba4 using the console (“univention-app install samba4”), it says that the packages univention-samba4 and univention-s4-connector cannot be found.
