I'm testing Exchange 2013 for a client to upgrade from Exchange 2003

I had a issue with Exchange 2013 couple of days ago.

Turned out to be a Certificate error...

Ok... so I created another Certificate

I can login to OWA and Outlook fine- ** less than 2 hours later its NO longer working!

Are there any log I can see why ?
is it possible to fix without redoing the Cert ?

All I've done in those 2 hours is connect a new account and import some mail from PST ?

-------------------------------------------------------------
I understand that this is not Fully Trusted but I'm NOT yet ready & I don't own the domain

There MUST be a better way to test all functionality - Outlook specially

-------------------------------------------------------------

is Exchange 2013 just flaky software - Installing own CA should work & carry on working

Any ideas what I can c

If you use an internal CA on the Exchange and connect from a client on the internal network that actually can rust the cert then it should be fine. 

Accessing owa that have a bad cert will only give you the standard warning that the cert is not verified. What error do you get when accessing OWA?

To troubleshoot look in the IIS logs of the CAS server

Hi,

We can check on each CAS the IIS logs files to find out the detailed errors. Also, we can use Outlook logging for more troubleshooting. To enable it, please open Outlook and click File > Options > Advanced > Enable troubleshooting logging.

Additionally, Installing own CA can work fine in Internal environment. And a Root Certification Authority(enterprise CA) which is added to a trust list can also be trusted to External communication.

About your certificate issue, please try removing all the unnecessary certificate including the new created one. Re-importing it to Exchange and enable it on the corresponding services.

Then restart the IIS service to see whether it works now.

Thanks,

Winnie