Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2014-09-05
6
Medium Priority
?
486 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 

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 1500 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

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

730 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