{"id":3703,"date":"2019-07-04T10:41:21","date_gmt":"2019-07-04T10:41:21","guid":{"rendered":"https:\/\/www.kerneldatarecovery.com\/blog\/?p=3703"},"modified":"2022-12-07T10:38:08","modified_gmt":"2022-12-07T10:38:08","slug":"resolve-autodiscover-and-ssl-warnings-during-exchange-2010-migration","status":"publish","type":"post","link":"https:\/\/www.kerneldatarecovery.com\/blog\/resolve-autodiscover-and-ssl-warnings-during-exchange-2010-migration\/","title":{"rendered":"Resolve Autodiscover and SSL Warnings During Exchange 2010 Migration"},"content":{"rendered":"

The SSL certificate is essential for secure email communication as it encrypts the outgoing messages and protects them from any unauthorized accesses. Sometimes, when you are installing Exchange Server 2010, then you can get a following security alert message –<\/p>\n

\u2018The security certificate was issued by a company you have chosen not to trust. View the certificate to determine whether you want to trust the certifying authority.<\/em>\u2019<\/p>\n

Cause of Autodiscover and SSL Warnings<\/h4>\n

The warning message occurs due to the inability of the Autodiscover feature to connect the Outlook with the SSL certificate. The Autodiscover is a special feature which automatically connects the Outlook versions ( computer and mobile) with the Exchange\u2019s mailboxes. It also configures the mailbox settings automatically. Whenever you install a new Exchange Server or migrate from older to a new one, then Client Server Access Role is installed, and the Autodiscover service is registered automatically in AD.<\/p>\n

When the Outlook tries to connect with Autodiscover by using an SSL certificate (https protocol), then it gives the warning because Exchange 2010 Client Access Server is configured with only a self-signed SSL certificate on its first installation.
\nHere are some solutions which you need to follow to manage the SSL certificate –<\/p>\n

    \n
  1. Reissue a new SSL certificate from a trusted third-party vendor.<\/li>\n
  2. Purchase an original SSL certificate from an authorized certificate vendor and install to the Exchange Server.<\/li>\n<\/ol>\n

    Install SSL Certificate at the Exchange Server 2010<\/h4>\n

    After purchasing the SSL certificate, you can install it at the Exchange with the help of Exchange Management Console. Follow the below steps:<\/p>\n

      \n
    1. Start Exchange Management Console from applications and go to \u2018Manage Database<\/strong>\u2019 option.<\/li>\n
    2. Select the \u2018Server Configuration<\/strong>.\u2019<\/li>\n
    3. Here, you can see the SSL certificate with the name you requested. For example, \u2018your-domain-name.cer<\/strong>.\u2019<\/li>\n
    4. Select the certificate and click the \u2018Complete Pending Request<\/strong>\u2019 under the \u2018Actions<\/strong>\u2019 menu.<\/li>\n
    5. Browse the SSL certificate<\/strong> and click Open<\/strong>, then click Complete<\/strong>.<\/li>\n<\/ol>\n

      If you are using IIS Server 7 or 8 series, then you may get the error message that \u201cThe source data is corrupted or not properly Base64 encoded.<\/strong>\u201d<\/p>\n

      Refresh the certificate and check the status under \u2018Self Signed<\/strong>\u2019 option. If it says \u2018False<\/strong>,\u2019 then it is fine but if it says \u2018True<\/strong>,\u2019 then it means that either you have selected a wrong certificate, or you had requested the certificate on a different Exchange Server.<\/p>\n

      Enable the SSL Certificate<\/h4>\n
        \n
      1. Go back to Exchange Management Console and choose \u2018Manage Databases<\/strong>.\u2019<\/li>\n
      2. Select \u2018Server Configuration\u2019 and click \u2018Assign Services to Certificate<\/strong>.\u2019<\/li>\n
      3. Select various services for which you want to enable the certificate. Finally, click Next >> Assign >> Finish<\/strong>.<\/li>\n<\/ol>\n

        The SSL certificate is active and is securing your email communication at Exchange Server 2010. It will ensure secure client-server communication, protect you from any external user or hacker, legitimize your identity to the network, and improve the client trust.<\/p>\n

        But, when you are migrating from one version of Exchange to another, you may face such issues constantly before and after migration, or during the migration itself. And after similar warning as errors, you may not be having time to handle such issues. If you want to save yourself from facing any complex problems during migration, then you should use professional Exchange migration<\/a> tools like Exchange Migration<\/strong> software. It can conduct safe and secure migration and hide all the complexities from you.<\/p>\n

        Exchange Migrator Software<\/h4>\n

        It accesses the Exchange data from one Exchange Server to another Exchange Server<\/a>. The great benefit of using the software is that you can schedule your migration at any desired time. It also does not affect the Exchange availability, and users can continue to access their Exchange mailboxes.<\/p>\n