Forum Discussion

hassanshakeri's avatar
hassanshakeri
Copper Contributor
Nov 13, 2023

How to test mail flow in Exchange 2019 in an existing Exchange 2013 environment.(Solved)

Hi experts, I'm trying to complete the upgrade process from Exchange 2013(on-premise) to Exchange 2019(on-premise).   I did all the steps that are explained in Best Practice for Upgrade and the Up...
exchange 2019
Exchange Server
Exchange2013
On-Premise
  • hassanshakeri's avatar
    hassanshakeri
    Dec 07, 2023

    Hi,

    As I finally found and solved the issue, I'd like to share my work with you.

    Maybe in future, some one need to know it.

     

    The issue was so less simple than I thought and was just alternative names in the certificate. I created another SAN self-signed certificate with alternative names like the certificate in our live environment and set it in IIS.

    With this script:

    New-SelfSignedCertificate -DnsName "server1name","server2name","mxRecord","autodiscover.domain.com" -KeyAlgorithm RSA -KeyLength 2048 -CertStoreLocation "Cert:\LocalMachine\My" -NotAfter (Get-Date).AddYears(10) -FriendlyName "certificateName"

     

    After binding the certificate, Outlook works and all errors are gone.

     

    I hope in this Artikel you can find any solution that helps you to solve the same issues.

     

    Regards,

    Hassan

hassanshakeri's avatar
hassanshakeri
Copper Contributor
Dec 07, 2023

Hi,

As I finally found and solved the issue, I'd like to share my work with you.

Maybe in future, some one need to know it.

 

The issue was so less simple than I thought and was just alternative names in the certificate. I created another SAN self-signed certificate with alternative names like the certificate in our live environment and set it in IIS.

With this script:

New-SelfSignedCertificate -DnsName "server1name","server2name","mxRecord","autodiscover.domain.com" -KeyAlgorithm RSA -KeyLength 2048 -CertStoreLocation "Cert:\LocalMachine\My" -NotAfter (Get-Date).AddYears(10) -FriendlyName "certificateName"

 

After binding the certificate, Outlook works and all errors are gone.

 

I hope in this Artikel you can find any solution that helps you to solve the same issues.

 

Regards,

Hassan

Resources