Glocap
asked on
exchange 2007
Our current certificate for exchange outlook web access is about to expire November 13,2013.
i installed a new certificate on oct 15,2013 which is valid till Nov,2015.
i can see it on the outlook web access the certificate says Nov,2015.
But i am getting these logs in the exchange server
Certificate for local system with thumbprint is about to expire or already expired.
Do i need to check something or worry about something that's missing?.
i installed a new certificate on oct 15,2013 which is valid till Nov,2015.
i can see it on the outlook web access the certificate says Nov,2015.
But i am getting these logs in the exchange server
Certificate for local system with thumbprint is about to expire or already expired.
Do i need to check something or worry about something that's missing?.
Nick Rhode
Did you remove the old certificate?
If you open Exchange Powershell and type:
Get-ExchangeCertificate and check your new certificate is running with the services with the letter W.
If your new certificate is showing the W service, you can remove it from the certificate management MMC.
Once deleted, you will not get any further alerts.
Get-ExchangeCertificate and check your new certificate is running with the services with the letter W.
If your new certificate is showing the W service, you can remove it from the certificate management MMC.
Once deleted, you will not get any further alerts.
ASKER
i did not remove the old certificate, godaddy told me once you install the new cert it will override the old certificate.
i am ok with the alerts but my main concern is that it should not stop users from accessing outlook web mail.
i am ok with the alerts but my main concern is that it should not stop users from accessing outlook web mail.
That's correct, as long as IIS or the Exchange powershell command is showing a bind to the Exchange Web Service, you are OK.
Adding the new certificate will not 'overwrite' the old certificate as such, but will stay on the server unbound to any services. I would personally remove the old certificate in case it causes some administrative confusion going forward. It's always good to have a clear event log too :)
Adding the new certificate will not 'overwrite' the old certificate as such, but will stay on the server unbound to any services. I would personally remove the old certificate in case it causes some administrative confusion going forward. It's always good to have a clear event log too :)
With the new cert assigned you should not have any problems :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.