I have seen this: http://exchangepedia.com/blog/2008/01/exchange-server-2007-renewing-self.htmlHere is my error:The STARTTLS certificate will expire soon: subject: mail01.nspire.local, hours remaining:I haven't kicked this off yet because:I have a mail server that responds to both: https://webmail.nspirehealth.com/owa & https://mail01.nspire.local/owaThe server, is for the most part, known by OWA users as https://webmail.nspirehealth.com/owa, both inside and outside, via separate IP's. However, theOutlook 2007 clientsalways validate their users by the mail01.nspire.local.There already IS a Trusted Public Cert for this server that I don't want to mess with that supports OWA. The ERROR is showing present only for MAIL01.NSPIRE.LOCAL (Which is the inside Cert). How do I avoid jacking with the perfectly happy external IIS cert, and get rid of this message, and not disrupt the internal Mail Clients connection to mail01.nspire.local. By the way, the only symptoms that this even existed was that my users of our internal "secure wireless" that receive their certs from this server can no longer connect using the tls. Mail hasn't been a problem.

Hi,There is a difference between the certificates used by the different services in the exchange. You can use one certificate for the web based services (OWA, Autodiscover, ActiveSync, etc.) and SMTP service. You can create a new TLS certificate with the following EMS command:New-ExchangeCertificate -SubjectName 'cn=MAIL01.NSPIRE.LOCAL'-Services SMTPMore information:http://technet.microsoft.com/en-us/library/aa998327.aspxRegards,Zoltnhttp://www.clamagent.org - Free Antivirus for Exchange http://www.it-pro.hu http://emaildetektiv.hu

Hi,Different services can enable on the same certificate or different certificates. For this issue, you just need to create a new certificate for the SMTP service as Zoltn suggested.ThanksAllen