Unfortunately, it will not let you delete it in the Exchange admin center because it still thinks it’s connected to both the connectors. But, you should delete the old certificate. When you see the above warning, you don’t have to worry. WARNING: The command completed successfully but no settings have been modified. But, the old certificate is also from Let’s Encrypt. In our example, we did add a new Let’s Encrypt certificate. That’s because the new certificate’s Issuer field and certificate’s Subject field are the same as the old certificate. You can get a warning as output when you run the Set-SendConnector and Set-ReceiveConnector cmdlets. C:\>Set-ReceiveConnector "EX02-2016\Default Frontend EX02-2016" -TlsCertificateName $TLSCertName Fill in the receive connector name that you copied in the previous step. Run the Set-ReceiveConnector cmdlet, including the TlsCertificateName parameter. C:\>Set-SendConnector "Outbound to Office 365 - d1c9beac-0655-48e7-9949-5e497af1d38d" -TlsCertificateName $TLSCertName Fill in the send connector name that you copied in the previous step. Run the Set-SendConnector cmdlet, including the TlsCertificateName parameter. C:\>$TLSCertName = "$($TLSCert.Issuer)$($TLSCert.Subject)" Store the certificate issuer and certificate subject values to the $TLSCertName variable. Store the value to the $TLSCert variable. Get the Exchange certificate with the thumbprint that you copied in the previous step. Run Exchange Management Shell as administrator. In our example, it’s Default Frontend EX02-2016. Copy the Default Frontend receive connector name. Copy the Outbound to Office 365 send connector name. Collect informationĭouble-click the new certificate in the Exchange admin center. Important: Do the same steps on the other Exchange Servers.įollow these steps: Step 1. The solution to this error is that we need to assign the new certificate to the: Why do we get this error, and what is the solution for removing the certificates that are tagged with the send connector Outbound to Office 365? Renew certificate in Exchange hybrid with PowerShell If you still want to proceed then replace or remove these certificates from Send Connector and then try this command. Removing and replacing certificates from Send Connector would break the mail flow. When we want to remove the invalid Exchange certificate, we do get an error.Ī special Rpc error occurs on server EX02-2016: These certificates are tagged with following Send Connectors : Outbound to Office 365 – d1c9beac-0655-48e7-9949-5e497af1d38d. Let’s remove the old certificate on the Exchange Server to keep everything tidy. The new certificate is installed and valid.
HOW TO REMOVE OFFICE 365 CERTIFICATE INSTALL
Read more: Install Exchange certificate with PowerShell » These certificates are tagged with following Send Connectors Also, we did assign it to the services IMAP, ISS, and SMTP.
HOW TO REMOVE OFFICE 365 CERTIFICATE FREE
We did install a free Let’s Encrypt certificate on the Exchange Server. Important: In production environments, you need to renew the certificate before it gets invalid. In our example, we have an invalid certificate. Select the Exchange Server from the drop-down menu if you have multiple Exchange Servers.