NethServer Version: V7.4 final Module: Samba4 AD Account provider
I am a bit puzzled on the ‘best practise’ when adding a NS7 Server to a remote AD or Samba4 domain.
My problem is as follows: When a new NS7 is installed, we give it a FQDN. We can find the FQDN in ServerManager under Configuration / Server name
This must be a FQDN. In my ignorance I named it as server.domain.tld, which represents the situation on my LAN.
Now I want to add the server to the domain so the services configured on the server can be used by domain users. I go over to Configuration / Account provider and hit the Active Directory button and after that the ‘join domain’ button.
Then I get back the following error:
Failed to join Active Directory (Failed to enroll machine in realm: Already have domain ad.domain.tld in sssd.conf config file)
All quite logical, but what would be the best practise in this case?
Rename the server to some imaginary FQDN and then join the domain. This works, but then i am stuck with a FQDN that is different from the actual domain.
If I try to rename the server again, I get the error:
Fully qualified domain name
Users and groups provider already configured
Any more elegant solution?
Additional to this: can the data from configuration / organization contacts be copied over during/after domain join? It would make sense to me anyways.
That is correct. I had the same issue and question. First time you get an error about the Realm already being defined in sssd, you then just do the exact same thing, and it will pass.
The hostname-modify event causes the /etc/sssd/sssd.conf template to be expanded, thus the realm procedure fails because it requires sssd.conf to be absent.