Link to home
Start Free TrialLog in
Avatar of TownTalk
TownTalkFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Certificate problem

SBS 2008 + Exchange Server 2007

Our self signed certificate expired a few weeks ago. I used the wizard in the SBS console to replace it. I noticed today that event 12016 is now being logged quite frequently. This says 'There is no valid SMTP TLs certificate for the FQDN of ouremaildomain.co.uk.

I am not aware that I ever created a certificate for that email domain. When I set up the server, I used a completely different domain ourofficedomain.co.uk because our primary domain is hosted elsewhere for our ecommerce store. I set up an mx record to point mail.ouremaildomain.co.uk to our sbsserver.

I think I need to do some housekeeping. I can see that there are 9 expired certificates. With these names "Sites", "remote.ourserverdomain.com" and "Server.ourdomain.local" Is it definitely ok to delete all expired certificates?

Do I need to create a new certificate for our email domain? or do I just need to make exchange aware of the one i created a few weeks ago? Funny... in the list of certicates, I  can't see any certificate that was created recently
ASKER CERTIFIED SOLUTION
Avatar of Skyler Kincaid
Skyler Kincaid
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of TownTalk

ASKER

Yes I have an smtp server configured. I hadn't realised the event message was referring to that. Our production system uses it to send emails to internal users. I set this up some time after the server installation. So maybe it inherited the previous certificate.

If I re-run the wizard, is there something in there to assign the certificate to the smtp server?
When I ran the wizard to create a new certificate, it only allows one domain to be specified. So I specified the domain referred to by our internal smtp server. But it then configured RWW etc to correspond to that domain. We didn't want this. So I ran the wizard again with the original domain specified and all is well now. Thanks for your help.