We have exchange 2007 and are planning on moving to Office 365 in the near future. However our certificate just expired and I renewed it with this method: Get-ExchangeCertificate -Thumbrint "[thumbrint]" | New-ExchangeCertificate populating the
thumbprint with the thumbprint of the expired certificate.
However when I went to assign the services i was warned that SMTP could not be assigned because our hub transport services receive connectors were using a different cert. That different cert is expired as well... like a year ago actually.
The other issues is that I have to manually install this new certificate on everyone's computers.
Would this workflow not break the receive connectors and make it so I don't have to install the certificate manually on pc's?
1. Copy the certificate that is currently expired that the warning told me about.
2. Delete all of the expired certificates(there are like 5 or 6 of them) as well as the first new one I previously created and the one I copied in step 1.
3. Assign the IIS, IMAP, POP and SMTP services to the newest certificate ( from step 1)?
I am concerned that the Hub transport receive connectors will break.
Thanks,
James
EDIT: here is the warning I am receiving.
WARNING: This certificate will not be used for external TLS connections with an FQDN of 'server.domain.com' because the
CA-signed certificate with thumbprint '977EF8E8E267A1066156B1A5F8C7CBCD12B05C67' takes precedence. The following connectors match
that FQDN: Client LGMAIL, Default LGMAIL, SMTP Recieve, Word Press Internal test Relay, LG Pdf Relay, Prineville PDF Relay,
Hermiston PDF Relay.