Solved

Exchange 2013 coexistance during phaseout of Exchange 2007 Certificate Problem

Posted on 2014-11-24
6
136 Views
Last Modified: 2014-11-30
I am in the process of moving our email to a new Exchange 2013 server. I am at the coexistence point and have moved owa to point to the new server. The Certificate includes the new server name and internal emails seem to be fine. The one test account I have on the new server is able to send and receive emails  from the old server. However my iphone generates a certificate not trusted for the owa server name.

The Certificate was created from a request from the old server while it was the owa ip address. Now I have altered the IP address to the new server making it the owa source. It passes owa to the old server fine however when the mailbox is on the old server.

So what am I missing on the Iphone that would cause this cert error? It also appears to only be on one of the two email accounts I have on the phone. The second generates the error and it is our helpdesk account. But the first does not generate any errors and email flows fine. The helpdesk emails do not  however. So my phone does not have any of the emails since the transition to the new IP address for owa.

The IP address is an internal IP, the external IP is of course our public address. I have a Cisco 5505 ASA as the firewall for the private network and it has rules passing email traffic to the old ip address. So should I change those rules to the new IP allowing all emails to flow to the exchange 2013 in the hopes the server sends them on to the old server, or do I need to generate a new certificate request from the new server.

I'm stumped!
0
Comment
Question by:dpcsit
  • 3
  • 3
6 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
Comment Utility
Do you have an external host name configured within ActiveSync on the Exchange 2007 server?

You haven't said who your SSL provider is, but a lot of them require an additional intermediate or root certificate to be installed on the server. You should check if that is the case and install it.

Simon.
0
 
LVL 1

Author Comment

by:dpcsit
Comment Utility
SSL provider godaddy and I installed the intermediate cert in intermediate Certificate Authorities on both servers using MMC.

The ActiveSync was changed to the legacy address as in legacy.xxx.xxx on the 2007 server.

On the 2013 server it points to the name of the new exchange sever. As in https://xxx.xxx.xxx/Microsoft-Server-ActiveSync
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
If this is a new certificate did you install the new intermediate certificate - it was changed earlier this year.
Run a test account through the Microsoft test site at http://exrca.com/ and see whether that flags anything.

Simon.
0
The problems with reply email signatures

Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

 
LVL 1

Assisted Solution

by:dpcsit
dpcsit earned 0 total points
Comment Utility
I found the issue. Godaddy change the names that could be used and now require the full domain name. We had an entry in a phone that was only the server name without the FQDN thus there was no cert for the server it was authenticating to.

Sorry to have wasted your time.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
Comment Utility
It isn't a GoDaddy rule that was changed - it is a global thing.
From November 2015 no certificates can have internal only names (so hostname, hostname.domain.local) or IP addresses listed.

Simon.
0
 
LVL 1

Author Closing Comment

by:dpcsit
Comment Utility
The actual issue was a change on the godaddy rules that removed a server name without a FQDN. The suggestion by the expert however would be a good starting point for this type of error!
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now