MSSC_support
asked on
How to stop certificate errors on new Exchange 2013 CAS server running in 2010 environment.
We are in the process of migrating all of our servers away from exchange 2010 and onto exchange 2013 with the long term view of migrating mailboxes to exchange online in a hybrid environment. I began by introducing the Exchange 2013 server with the CAS and Mailbox role. We use round robin DNS for our CAS with the internal URL matching the external webmail address so I ran the set-clientaccessserver -identity -servername - autodiscoverserviceinterna lUri https://domain.org/autodiscover/autodiscover.xml and then began migrating mailboxes across for testing.
All email come through and send ok however I receive certificate errors stating that the server name does not match the certificate. Can anyone help me?
I am not sure what the next step to take is.
All email come through and send ok however I receive certificate errors stating that the server name does not match the certificate. Can anyone help me?
I am not sure what the next step to take is.
ASKER
Hi Simon,
Apologies if I am a little slow in understanding what you are saying. I have a URL for the new and old server. The new 2013 server has the certificate too that was used on 2010. This will eventually replace the 2010 server. The entry is also in DNS so that the certificate error doesn't get thrown but it still does.
Have I missed anything here?
Thanks
Apologies if I am a little slow in understanding what you are saying. I have a URL for the new and old server. The new 2013 server has the certificate too that was used on 2010. This will eventually replace the 2010 server. The entry is also in DNS so that the certificate error doesn't get thrown but it still does.
Have I missed anything here?
Thanks
You cannot use the same URL for both servers.
The only time you could use the same URL is if you were doing a big bang, where everyone is being migrated in a very short space of time.
At the very least, you need to have the current URL going to Exchange 2013, with a legacy URL on the older server. Exchange will proxy some web based traffic, but others it will redirect.
Simon.
The only time you could use the same URL is if you were doing a big bang, where everyone is being migrated in a very short space of time.
At the very least, you need to have the current URL going to Exchange 2013, with a legacy URL on the older server. Exchange will proxy some web based traffic, but others it will redirect.
Simon.
ASKER
Also, should I point the autodiscover for all the exchange 2010 servers to the new exchange 2013 cas server as currently the old 2010 environment I have left as is and only ammended autodiscover for the new exchange CAS server.
Is the 2013 cas server role backward compatible? Can I just point all the mailboxes to that CAS server instead?
Is the 2013 cas server role backward compatible? Can I just point all the mailboxes to that CAS server instead?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Managed to get it working by removing the round robin DNS for the old cas servers and adding the new CAS server in there and also by configuring outlook anywhere with the external url.
Pointing the URLs at the Exchange 2010 server isn't going to work either.
You need a URL for Exchange 2010 and a URL for exchange 2013.
Simon.