Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 503
  • Last Modified:

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 - 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
MSSC_support
Asked:
MSSC_support
  • 3
  • 3
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
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
 
MSSC_supportAuthor Commented:
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
 
Simon Butler (Sembee)ConsultantCommented:
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now