Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Exchange 2003 certificate error since moving SBS2003 to Hyper-V VM

Avatar of gregmiller4it
gregmiller4itFlag for Australia asked on
ExchangeSBSEncryption
9 Comments1 Solution279 ViewsLast Modified:
I am in the process of migrating SBS2003 with Exchange 2003, to a Server 2012 Hyper-V host, running Server 2012 DC and Exchange 2013.
As part of the process, I have moved SBS2003 into a VM. Most of it is now working ok: DHCP, Shares, printers, etc., but Exchange 2003 is not. I am getting a Security Certificate error, saying that the certificate is expired.  When I view the certificate through the error message, it shows a certificate that expired 2 years ago.
I can connect to the VM SBS2003 from client but when I open Outlook (2010) it gives the Security Certificate error and can't connect to Exchange. If I create another Outlook profile, it wont connect either.

I only renewed the security certificate a couple of months ago, but the expired certificate is not the same one.
Prior to moving the SBS to the VM I had seen the same or similar error a few times, but I was able to continue and everything worked ok. I think I saw it when I set up Outlook for an existing user on a different PC. I think I had also seen it when using OWA. But in both cases it didn't stop me from connecting to Exchange. Now it does stop me connecting.

I've viewed he certificate in IIS and it is the correct, current cert.

I think there is an old certificate that is installed somewhere that I need to remove, and maybe point Exchange at the current certificate.

OWA now does not work either. I get the logon screen, but then get a 503 error when I try to logon.
Cheers,
Greg
ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Commented:
This problem has been solved!
Unlock 1 Answer and 9 Comments.
See Answers