Did you run the repair on the object as it indicated in the error? Because you had issues that prompted the restore you may just need to repair it. You can check here. https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/troubleshoot-issues-accounts-used-failover-clusters This should help you with that problem.
Failover Cluster Manager can't reach AD
Hi guys!
I encountered some issues with my main Domain Controller server at work this week. Consequently, I had to resort to using a backup from a few weeks ago (I know, don't restore DC, but there was nothing else I could do).
The problem I'm encountering now is that somehow my SQL Server roles in Failover Cluster Manager can't reach the AD to read their VCOs, even though the CNO of the CLUSTER has rights to read and create computer objects.
Upon inspection, my cluster server reaches the domain controller, replication is OK, nothing is missing in the OU, DNS is alright, date and time are in sync. After the backup, everything that acted like a secondary domain was reinstalled, so I don't know where else to look anymore.
I configured a new cluster server, and there I have absolutely no problem with installing new roles or reaching the VCOs from the OU in the domain, but I don't want to start migrating all the databases to new servers.
2 answers
Sort by: Most helpful
-
-
ZoeHui-MSFT 36,116 Reputation points
2024-02-19T06:37:34.53+00:00 Hi @GABE99, Check Configuring cluster accounts in Active Directory to see if you have configured the account correctly. Regards, Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.