Hi All,
I have been digging through Google and trying fixes all day, I've never run into this problem quite this bad. I am trying to add another domain controller to my domain. There is only one currently and this is a 2012 R2 DC with the same being added. Here is the full error:
The operation failed because:
The Active Directory Domain Services Installation Wizard (Dcpromo.exe) was unable to convert the computer account CTG-HQ-DC$ to an Active Directory Domain Controller account.
Verify that the user running Dcpromo.exe is granted the "Enable computer and user accounts to be trusted for delegation" user right in the Default Domain Controllers Policy.
For more information, see the resolution section of http://go.microsoft.com/fwlink/?LinkId=178406.
The error was:
"The specified network resource or device is no longer available."
This is what I have verified so far
- I can get through all of the screens to promote the DC, it fails on install
- On the current DC I have verified that the new server is in Active Directory in the domain controllers OU
- Verified that the group policy allows the admin account to enable the trust and the GPO is applying to the current DC
- In Sites and Services the server is under the site but the NTDS settings are missing
- I can ping the domain from the new server
- I can ping the DNS name of the current DC from the new server
- The current DC has the proper service records in DNS
- DCDIAG on the current DC is clear except for a warning
Anyone have any thoughts?
I will get these items for you on Monday as I am not in my office over the weekend.
Sounds good.
Just checking if there's any progress or updates?
--please don't forget to
upvote
andAccept as answer
if the reply is helpful--Running your commands now, I will have an update shortly.
Thanks,
Here is the link to the files.
https://corporatetechnologi-my.sharepoint.com/:f:/g/personal/bfogliano_ctgusa_net/EkQizJYVMElLvd3We1ChuLgBeJ76OqT9pPWqzoHI_GS0NA?e=Up6wEI
One thing that I found interesting was that even after removing after reference to our old DNS server it is still showing up in the DCDIAG. I flushed the DNS, made sure it was not statically assigned anymore and pulled every reference out of the DNS manager. Would a reboot of the server help?
Sign in to comment