Fix Exchange 2016 CU12 Unable to Set Shared Config DC Error
Question details
The user needs to resolve an error that prevents Exchange 2016 CU12 from installing during a migration from Exchange 2010.

- Product
- Microsoft Exchange Server 2016 CU12
- Device & OS
- not provided
- Scenario
- Installing Exchange 2016 CU12 in an environment migrating from Exchange 2010.
- Observed behavior
- Setup fails with an Unable to set shared config DC error.
Record the complete error and identify the domain and domain controller used by the Exchange server. Confirm that the account running setup has the required permissions and that your migration plan meets Microsoft's Exchange coexistence and prerequisite requirements.
Check Active Directory, Connectivity, and Exchange Setup Permissions
Use these checks to identify common directory and access issues before retrying setup.
Open C:\ExchangeSetupLogs\ExchangeSetup.log and search for the shared config DC error. Review the surrounding entries for the domain controller name and any underlying access, DNS, or service errors.
Open Command Prompt on the Exchange server and run nltest /dsgetdc:yourdomain.example, replacing the domain with your Active Directory domain. Investigate any discovery failure and check the server's DNS configuration.
Run dcdiag /test:dns and repadmin /replsummary from a system with the appropriate administrative tools. Resolve reported DNS or replication errors with your Active Directory administrator.
Review Microsoft's Exchange 2016 prerequisites and setup permission requirements for your deployment. Confirm that the Exchange 2010 environment meets coexistence requirements and that the setup account has the necessary permissions for the operations being performed.
After correcting identified issues, run Exchange Setup again. If it fails, return to C:\ExchangeSetupLogs\ExchangeSetup.log and compare the new error with the earlier log entries.

Review Related Exchange Setup Troubleshooting
Use related support discussions for context when the log shows a service or setup failure, and seek dedicated help if the cause remains unclear.
Work With Office Documents Using WPS Office
WPS Office is a free, lightweight alternative for everyday document work, with a familiar interface and support for common Microsoft Office formats to make migration easier. It does not repair Exchange Server installations.

Frequently Asked Questions
Where can I find the Exchange setup log?
Open C:\ExchangeSetupLogs\ExchangeSetup.log and search for the reported error. The entries immediately before it may identify the domain controller or underlying failure.
How can I test whether the server can find a domain controller?
In Command Prompt on the Exchange server, run nltest /dsgetdc:yourdomain.example using your Active Directory domain. If discovery fails, investigate DNS and domain connectivity.
Can I upgrade an Exchange 2010 server directly to Exchange 2016?
No. The move requires a migration between servers rather than an in-place upgrade. Review Microsoft's coexistence requirements and current migration guidance before proceeding.
Does the shared config DC error always mean DNS is broken?
No. DNS or domain controller connectivity may be involved, but permissions, Active Directory health, or other setup issues can also contribute. Check the setup log and directory diagnostics before choosing a fix.




