Solved

How to stop certificate errors on new Exchange 2013 CAS server running in 2010 environment.

Posted on 2014-09-05
6
446 Views
Last Modified: 2014-09-15
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 - autodiscoverserviceinternalUri 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.
0
Comment
Question by:MSSC_support
  • 3
  • 3
6 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40306103
You need to ensure that you have a certificate on the new server and all of the URLs are correct. Adjusting just the Autodiscover one is NOT enough.
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.
0
 

Author Comment

by:MSSC_support
ID: 40306123
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
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40306162
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.
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:MSSC_support
ID: 40306179
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?
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40307422
Point all of your current URLs at the Exchange 2013 server and configure a new legacy URL for the Exchange 2010 server, with the exception of the Autodiscover URL.

With regards to mailboxes though, don't change that. The behaviour changes between the Exchange versions. On Exchange 2013 all connection is through Outlook Anywhere and each user will have a unique endpoint in their client. Therefore let Outlook/Exchange redirect the traffic for you when you move the mailbox to the Exchange 2013 platform.

OWA doesn't proxy, it only redirects, so you will need to have two URLs available.

I suggest that you read the co-existence documentation on TechNet. A migration of this kind needs to be planned due to the architecture changes. You cannot really make the changes on the fly.

Simon.
0
 

Author Closing Comment

by:MSSC_support
ID: 40323332
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.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Need to make a disk image of 2008 R2 RAID array . . . but VSS not working 8 59
EXCHANGE, ACTIVE DIRECTORY 1 28
Exhange 2010 10 29
Application Crash 2 19
A procedure for exporting installed hotfix details of remote computers using powershell
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

816 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

8 Experts available now in Live!

Get 1:1 Help Now