[Solved]The Computer account ‘DAG’ could not be validated. Access was denied. Check that the current user (NT AUTHORITY\SYSTEM) has permissions to create computer accounts in the domain or to claim the computer account.
During the configuration of DAG, some might have faced such kind of issue, the way I have tried to resolve it has been explained below.
ISSUE:
A server-side database availability group administrative operation failed. Error The operation failed. Create Cluster errors may result from incorrectly configured static
addresses. Error: The computer account ‘DAG1’ could not be validated. Access was denied. Check that the current user (NT AUTHORITY\SYSTEM) has permissions to create
computer accounts in the domain or to claim the computer account.
Resolution:
To Resolve such kind of issue, you need to check three steps,
- Make sure your newly created DAG computer account is in disable mode, if no then disable it manually.
-
Verify that the First Exchange server do have ‘FULL Control’ on the security of DAG as of below.
-
Verify that the ‘Exchange Trusted Subsystem’ do have ‘FULL Control’ on DAG Security Properties.
Hope this will help you to resolve your problem, request for your feedback on this.
Exchange online PowerShell with Modern Authentication
Customizing Exchange 2016 OWA
Multi-Factor Authentication (MFA) with Microsoft Entra ID: Best Practices and Implementation Guide
About Author
pdhewjau
Prashant is a Principal Cybersecurity Specialist at Thakral One Nepal. His prior position as a Modern Work Security Specialist at Microsoft saw him providing invaluable guidance to major clients in Bangladesh, Brunei, Cambodia, and Myanmar, assisting them with their foundational security needs. Awarded the esteemed Microsoft Most Valuable Professional (MVP) accolade in 2017, Prashant is recognized globally among Microsoft peers. Since 2010, he has imparted his expertise as a Microsoft Certified Trainer (MCT), conducting specialized training across Nepal.
Add a Comment
This site uses Akismet to reduce spam. Learn how your comment data is processed.
This solution worked for our environment. Exchange was patched to the latest RU, which at the time of posting this comment is RU18.
That’s brilliant. thanks alot. This issue resolved the pain as I had been searching for this solution the past few hours.