• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 196
  • Last Modified:

Exchange Certificate update failure

I have an SBS 2011 Standard server with Exchange 2010.

The business recently changed it's name/domain. As a result I have changed the email domain in exchange. Exchange is being used for internal send/receive mail only, no remote access.

After completing the process, everything looks and is operating appropriately, with the exception of the certificate being updated in some fashion.

Users are using outlook 2010, as they also have some pop3 emails configured. Upon launching outlook, they immediately get a certificate warning that pops up twice. They can say yes to proceed and function normally.

The certificate warning is attached below. It references the email domain name at the top, but when I open the certificate, it appears to be for the new email domain name.

I have run the internet setup wizard multiple time, as well as the fix my network wizard without success. Is there another manual means of updating/correcting this issue?
Untitled.jpg
0
tjwo94
Asked:
tjwo94
2 Solutions
 
tjwo94Author Commented:
Additional information:

When I run an autodiscover test from an outlook client I notice these things are still referencing the old domain:


Exchange RPC
Availability URL service
OOF URL
OAB URL
Unified Message Service URL

Exchange HTTP
Availability URL service
OOF URL
OAB URL
Unified Message Service URL
Certificate Principle Name
0
 
David Paris VicenteSystems and Comunications  Administrator Commented:
If you are just using for internal purposes the Exchange organization, you can generate a new certificate with your internal CA, if you have one.

The SAN certificate name is probably wrong you have to generate a new SAN certificate with the correct domain .

Please take a look here:Create a New Exchange Certificate to see how you accomplish that.

Regards
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
After you have installed your cert did you change your Exchange Virtual directories to reflect your new domain name on the cert? Also if you users mailboxes that reside on the old exchange server your certificate will need to have the following...

- autodiscover.domain.com
- mail.domain.com
- legacy.domain.com

You will then need to install the cert on the new Exchange server, export it and import it on any other CAS servers in your environment, including your old Exchange server.

If you do not have your old Exchange server in play then you probably just need to modify your virtual directories in the ECP or using powershell.

Will.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
tjwo94Author Commented:
Will,

I have not updated exchange virtual directories, and can't say that I know how. There is only one exchange server which is what I have updated.
0
 
tjwo94Author Commented:
Will,

Looks like you pointed me in the right direction. While determining how to update virtual directories, I came upon this:

http://premnair.wordpress.com/2010/07/03/configure-ews-autodiscover-owa-oab-ecp-on-exchange-server-2010/

Ran through the steps, and now my test outlook client isn't popping up cert errors. I'll check regular users tomorrow and update.
0
 
Simon Butler (Sembee)ConsultantCommented:
Your mistake was making the changes in Exchange directly.
If you had ran the wizards in SBS Console it would have changed the domain for you AND generated an SSL certificate that was suitable for the task. SBS should not be managed in the same way as the full product, as you will never make all of the changes the wizards make (I read somewhere it was over 200).

Simon.
0
 
tjwo94Author Commented:
I re ran the wizards first Simon. First the internet setup wizard to change the email domain, then a fix network wizard ti hopefully clean up any lose ends. The certificate was created, however the wizard failed to apply all the changes necessary to other exchange components in order for everything to work properly. The url I posted shows the pieces the wizard failed to complete, otherwise the wizard did a great job.
0
 
tjwo94Author Commented:
What I found did the trick, no more cert errors. Thank for getting me looking in the right place.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now