Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 39
  • Last Modified:

Outlook 2013 and SBS 2011 - Changing cert on server

I have a customer that has a SBS 2011 Server (using Exchange) and Outlook 2013 on the Workstations. Essentially they decided to change the SSL Certificate on the server. At that point when they open Outlook on the workstations they get an error about the SSL certificate not matching (it is looking for the old certificate).

It seems like it only happens once when they first open Outlook and then the error goes away. I have even tried rebooting a workstation and the error does not appear to come back. I understand why the error occurred but can't figure out why it went away.  

Where does Outlook store the certificates and did the error truly go away or is it going to pop up again?
0
LockDown32
Asked:
LockDown32
  • 4
  • 3
1 Solution
 
mbkitmgrCommented:
HI LockDown32.

What message is the SSL warning reporting.  Its should say if its a name mismatch, or expired or........

Also did they use the SSL Certificate wizard in SBS to create the cert req, and install the new cert.
0
 
LockDown32OwnerAuthor Commented:
It is a name mismatch which is expected. They changed the name on the cert. Generated the CSR in the SBS Console, submitted the CSR to GoDaddy and downloaded and installed in via the SBS Console.
0
 
mbkitmgrCommented:
Have they changed the Internet Domain Name ?

If yes, did they use the Domain Name Wizard to reset the internet domain name in SBS
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LockDown32OwnerAuthor Commented:
Yes. All of this was done with the SBS console. First they changed the Internet Domain Name then they chaned the certificate to match the new Internet domain name.
0
 
mbkitmgrCommented:
Have you tried the following
  1. Create a new user with a mailbox, and log onto a PC as that user to see if the error is coming from the config in the exchange profile.
  2. Connect to OWA and see if it is reporting the same error
  3. If there are sufficient workstations, pick a user who hasn't logged onto a workstation and have them log on and see if the msg appears
  4. Run fix my network and see
.

I don't have many SBS clients (half dozen or so) and I have the same exercise coming to rename their internet domain and was told by MS support to use the wizard and all will be fine, but it appears you may prove that advice to be incorrect
0
 
LockDown32OwnerAuthor Commented:
The solution was to delete the Outlook Profile and re-create it with the new cert name/email address
0
 
LockDown32OwnerAuthor Commented:
This is the solution that worked
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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