Email Migration

How to Fix Exchange 2010 Hybrid Migration Certificate Errors

Kushani NimanthikaKushani Nimanthika Nov 2, 2026 869 views

Question details

The user needs to resolve an Exchange 2010 hybrid migration failure caused by the server using a self-signed certificate, which Autodiscover rejects.

How to Resolve Exchange 2010 Hybrid Migration Certificate Errors
Product
Exchange 2010
Device & OS
not provided
Scenario
Configuring a hybrid email migration to move all mailboxes across multiple domains using Exchange 2010.
Observed behavior
The hybrid connectivity and Autodiscover checks fail because the default domain rejects the self-signed certificate.
Before you start

Ensure you have Exchange Management Console administrator access and have purchased a valid SSL certificate from a trusted third-party Certificate Authority (CA) that covers your domains.

Solution 1Recommended

Install and Assign a Trusted Third-Party SSL Certificate

Replace the self-signed certificate with a trusted third-party CA certificate to satisfy Autodiscover and hybrid connectivity requirements.

Exchange 2010 hybrid configurations do not support self-signed certificates for Autodiscover or Exchange Web Services. You must use a Subject Alternative Name (SAN) certificate if you manage multiple unrelated domains, or a wildcard certificate for a single domain and its subdomains.

1
Obtain the SSL Certificate

Purchase and download a trusted SSL certificate from a recognized Certificate Authority (CA) that covers all required domains for your hybrid environment.

2
Import the Certificate

Open the Exchange Management Console (EMC), navigate to Server Configuration, and use the 'Import Exchange Certificate' action to install the new certificate.

3
Assign Exchange Services

Select the newly imported certificate and choose 'Assign Services to Certificate'. Ensure you assign it to the required services, specifically IIS (Internet Information Services) and SMTP.

4
Run Hybrid Configuration Wizard

Rerun the Exchange Hybrid Configuration Wizard to verify that the third-party certificate is accepted and Autodiscover functions correctly.

Install and Assign a Trusted Third-Party SSL Certificate
Impact on Users: Replacing the server certificate secures server communication and mail flow. It generally does not impact user authentication or require reconfiguration of existing devices, provided it is executed carefully during a low-usage period.
Free Microsoft Office alternative

Manage Your IT Documentation with WPS Office

While troubleshooting Exchange server migrations, you need a reliable productivity suite to manage migration plans, checklists, and administrative communication. WPS Office is a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for IT professionals managing complex deployments.

Highly compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight design ensures fast loading on admin workstations and utility servers.Includes built-in PDF editing tools for creating secure server migration documentation.Free to use with a familiar, tabbed interface to boost productivity during IT projects.
microsoft office alternative - wps office

Frequently Asked Questions

Can I use a self-signed certificate for an Exchange 2010 hybrid migration?

No, Exchange 2010 hybrid migrations require a certificate issued by a trusted third-party Certificate Authority. Autodiscover and hybrid connectivity will reject self-signed certificates, causing the migration configuration to fail.

What happens to users when I replace the Exchange server certificate?

Replacing the server certificate generally does not affect user authentication or require users to reconfigure their email devices. It authenticates the server and secures the communication layer.

Should I use a wildcard or a SAN certificate for multiple domains?

A wildcard certificate is suitable for one primary domain and its subdomains. If your migration involves multiple unrelated domains, you must use a Subject Alternative Name (SAN) certificate to cover all the distinct domain names.