Q: I’ve been trying to install Microsoft Exchange Server 2010 in my organization. I keep receiving the following...
error message during setup: “Problem encountered while validating the state of Active Directory – could not find a domain controller.” I can’t figure out what’s wrong, can you suggest anything?
A: Like many Exchange setup errors, there can be multiple causes. There’s no one thing you can do to “fix” this error, but there are several steps you can take to ensure that setup goes as expected:
1. Make certain that the account you are executing Setup with has the correct permissions required both to configure Exchange at a domain level and on the local server. If you are running Setup from the command line (setup.com), make sure that the CMD instance is “Run as” an administrator, even if the account is considered a local admin. If you are using “Setup.exe,” you should also run this “as the admin.”
More expert answers:
When it comes to ensuring that your Exchange installation account has the correct permissions within your Active Directory infrastructure, follow the guidance issued in the TechNet article on preparing Active Directory and domains.
2. Make sure that all of your domain controllers are online and fully functional; there should not be any replication errors. Additionally, make sure that DNS is functioning correctly within your environment. This will ensure that the Exchange server you’re trying to run Setup from can resolve the FQDN of each relevant domain controller and vice versa.
3. If you are installing Exchange Server 2010 on a server in a child domain in a multi-site configuration, ensure that all domain controllers, global catalogs, DNS functions (as per above) are functional between the child and the parent. Also, ensure that the Schema Master FSMO role holder is online, available and resolvable from the child domain and site.
4. If you are installing Exchange Server 2010 in a multiple-site environment, make sure that the site you are running Setup in contains at least one domain controller that is also a global catalog.
5. If everything above checks out, check the Exchange Setup logs (C:\ ExchangeSetupLogs) and event logs on the Exchange server. They should give you further troubleshooting info that is specific to your environment.
Dig Deeper on Exchange Server setup and troubleshooting
Related Q&A from Andy Grogan
With hosted Exchange email deployment chatter increasing daily, it's crucial to separate fact from fiction when it comes to security and reliability. Continue Reading
An Office 365 outage may be widespread or unique to your deployment. Discover how to find out, as well as the best ways to prepare your organization. Continue Reading
A coexistence period is an important part of any Exchange Server migration -- but why? Our expert explains. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.