Link to home
Start Free TrialLog in
Avatar of Anthony
AnthonyFlag for United States of America

asked on

Certificate Issue When Exporting

Hi All,

I have a Surface RT that I received as a gift and I'm trying to get my office email account added to the Mail app.  We have Exchange 2010 with a valid certificate, that I've actually installed myself in the Trusted Certificate Authority folder.  What is weird is that when I open the certificate on my Surface, it says that the cert has been revoked; however, when I look at the cert on the Exchange Server it says that it's valid and give me it's purpose and the time period it's valid.  I'm really puzzled as to what this could be.  I have a call out to Microsoft who should be calling me back, but I thought some other individuals might have any ideas.

Thanks in advance.

-Anthony
Avatar of cristiantm
cristiantm
Flag of Brazil image

Looks like you may be experiencing this problem here:

http://answers.microsoft.com/en-us/windows/forum/windows_8-ecoms/mail-app-digital-certificate/fd18864f-8d63-4b77-bd40-de0ea42d7bfe?page=1&tm=1386171310544

That is not solved for a year already... is it a self-signed certificate?
Avatar of Anthony

ASKER

No, the cert is signed by godaddy.
Then you should not need to install it on as a Trusted Certificate Authority. Only the GoDady certificate should be there, but I think it probably already is. Maybe this is causing the issue?
Avatar of Anthony

ASKER

The godaddy cert is there, but I've already taken out the other certs.

From what I've determined, for some reason Microsoft shows the cert as being revoked from it's authority, when it hasn't.  We've used this cert on Microsoft Smart Phones.
ASKER CERTIFIED SOLUTION
Avatar of Anthony
Anthony
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 Anthony

ASKER

The issue was larger then just the cert.  I needed to run a diagnostic check to determine that it was actually an IIS setting on the Exchange Server which led to the hiccup and not the certificate itself.