error determining whether the target environment requires adprep

Question

I have two domain controllers in the forest called corp.x.x. I'd like to make the third machine as the domain controller, then the problem occur as following picture.

Error event id: 8333

Answer 1

Hi,

Do you have full connectivity to the other Domain Controllers from this new server? Check the firewall rules and ports required for the connectivity - config-firewall-for-ad-domains-and-trusts

Guess you have schema admin roles assigned to the account?

Also can you provide the logs from the below folders -

• %systemroot%\debug\dcpromo.log
• %systemroot%\debug\dcpromo*.log
• %systemroot%\debug\adprep\<datetime>\adprep.log

---

Please don't forget to upvote and Accept as answer if the reply is helpful

If this answer helped you please mark it as "Verified" so other users can reference it.

Answer 2

Hi,

It looks like someone may have accidently deleted the server object. The error message is referring to CN=WIN-MCVUGI718M7\0ADEL:<GUID> the \0ADEL in the name is usual the reference for deleted objects.

You may need to restore the object before you can continue - https://nettools.net/how-to-restore-deleted-ad-objects/

Gary.

Answer 3

Hello there,

Check your DNS settings and make sure they are correct and that you can resolve the proper srv records to locate the domain controllers.

If all your domain controllers are at least Windows Server 2003 and both your domain and forest functional levels are set to at least Windows Server 2003, adding a Windows Server 2012 DC should work fine:

http://technet.microsoft.com/en-us/library/hh994618.aspx#BKMK_FunctionalLevels

The error status 8333 "Directory Object Not Found" has multiple root causes.This article describes an issue where Active Directory Replications fail with error 8333 you can try out the troubleshooting steps from here and see if that helps

Troubleshoot common Active Directory replication errors https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/common-active-directory-replication-errors

-------------------------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer--

Answer 4

I got the similar issue while promoting my server 2019 as DC and I restarted the server as tried again and get resolved by itself. I think my case the issue was the reboot required after installation the role of AD service, that the system didn't ask.

Shemi