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

Have wrecked OWA SSL on Exchange 2007 - Certificate problem

Avatar of amlydiate
amlydiate asked on
Exchange
14 Comments1 Solution822 ViewsLast Modified:
Hi all,

Having a knightmare with a 2008 server, in my attempts to try and get various Autodiscover/RPC issues fixed something changed and a couple of clients inside the network started to get autodiscover certificate errors saying the name on the certificate was invalid.  I've since logged on to OWA externally and I'm getting a certificate error as well saying "The certificate was not issued by a trusted authority" even though it is a UCC multi-domain GoDaddy certificate.  So I think I've managed to do something wrong with the certificate being used by OWA and Autodiscover.  I've gone into ESW and typed get-exchange certificate and got the following back:

19AB70EE2E4046A7B4725408C0DC832F9780E517  ...WS      CN=remote.domain.CO.UK
01236CDAAA070508368F9CD8590E75962BD9604E  IP..S      CN=owa.domain.co.uk, OU=Domain Control Validated, O=owa.s-domain.co.uk
BACFEA951F15377FD37924BE6D222252AFA7392B  .....      C=UK, S=shire, L=don, O=company, OU=IT, CN=owa.domain.co.uk
A7685EF4F7217F14050C8A712FC9E0478F1F1055  ....S      CN=remote.domain.CO.UK
6EAB45E4F154F85D80B00FD0AF616462B08A7D3B  ....S      CN=remote.domain.CO.UK
3125E1144085E4EB2EC09CD55586EF2BAE1F2CF0  ....S      CN=SERVER.domain.local
4EDDE5C2C3C42BF23345ED0F1D741E0E5C4EC3F3  ....S      CN=Sites
C2551C26BCAA30B3B6181005FEC118694B0F3DB3  .....      CN=domain-SERVER-CA
9EF59648147547251196342C12AF45196605B4C5  .....      CN=WMSvc-WIN-SER9SCTHZ40


I should point out that the thumbprint of the godaddy certificate is the one ending in 604E.  The URL I want to use for OWA is owa.domain.co.uk I included remote.domain.co.uk as a SAN in the GoDaddy certificate as I wanted to use that as the URL for VPN in the future.  Accessing remote.domain and owa.domain however both end up in the same certificate error.

I've checked the certificate when trying to access OWA and it looks like it's the wrong one.

Can anyone please tell me how to fix this?

Many thanks in advance

Adam
ASKER CERTIFIED SOLUTION
Avatar of lancepurcell
lancepurcell

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Commented:
This problem has been solved!
Unlock 1 Answer and 14 Comments.
See Answers