Exchange 2013 coexistance during phaseout of Exchange 2007 Certificate Problem

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!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
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.

dpcsitAuthor Commented:
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 on the 2007 server.

On the 2013 server it points to the name of the new exchange sever. As in
Simon Butler (Sembee)ConsultantCommented:
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 and see whether that flags anything.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

dpcsitAuthor Commented:
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.
Simon Butler (Sembee)ConsultantCommented:
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.

dpcsitAuthor Commented:
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!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.