- Join Domain Error Cannot Complete This Function
- Join Domain Cannot Complete This Function Without
- Join Domain Cannot Complete This Function Using
I started my morning by troubleshooting on-premises Active Directory domain join process in my demo environment. Windows 10 OS used was build 2004.
Additional domain controller's hardware become faulty & was shut down permanently. Now getting server alerts that it is The DFS Replication service failed to communicate with partner ADC1 for replication group Domain System & many similar errors. Now I am unable to join any new computer to the domain. Type 1 to begin the domain registration process. Type D to continue. Type the Active Directory domain name. Type the user who has the right to join the server in the domain. Once you press Enter you will be prompted to enter the password. You will also be prompted to change the computer name if desired.
Join Domain Error Cannot Complete This Function
Domain Join failed and I received the following error
Join Domain Cannot Complete This Function Without
- Event 4097
- Error code 1003
This error is a bit unusual and I couldn’t find any reason for domain join error from W10 logs. I also tested that DNS worked correctly. As many have said, it’s always DNS:)
Next stop was my Domain Controller and there I found root cause for this behavior and domain join error.
Event id 2092 indicates a replication error in FSMO role holder. Reason for this is that I had another domain controllers in the domain but those were offline. FSMO role holder needs to perform initial replication with the replication partners before it’s considered as valid.
Join Domain Cannot Complete This Function Using
Because we are talking of my demo environment I removed the FETADC02 that has been offline for couple of weeks. I real production environment, troubleshooting of replication would be needed in this case.
Removal of offline domain controller
Delete all the metadata
Confirmation that you really want to delete a global catalog server
I also changed FSMORoleOwner attribute for DNS partitions that had deleted domain controller as owner.
When offline domain controller was cleaned my replication tables were empty and I was able to join my device to the on-prem Active Directory.
Hope this helps if you are struggling with same error!