Exchange 2010 URLs as server name and Exchange 2013

Hi,

If a site has exchange 2010 server names as their local exchange urls, how can we introduce exchange 2013? because web services, rpc url all as localserver.contoso.com instead of mail.contoso.com. Do we need to change all these URLs first? before introduction of exchange 2013? so that when we move url to 2013 it can work?

Thanks

August 30th, 2015 4:16am

Hi


External and Internal DNS settings

Public DNS Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN

The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server

Free Windows Admin Tool Kit Click here and download it now
August 30th, 2015 11:28am

Thanks Sathish

So my question is specific for internal.

it means servername.contoso.com for urls will not work where single exchange 2010 with CHM roles and it has to be mail.contoso.com so that after introduction of 2013, urls can be moved to 2013, is this correct?

Another question: I am trying to understand if namespace is not moved to 2013 and stay on 2010. And we move mailbox to 2013. What exactly issue is?

3nd question is

if primary site has 2013 and branch site has 2010 server, is there any kind of issue?

August 30th, 2015 12:58pm

HI 

When you install Exchange Server 2013 it is pre-configured with default namespaces matching the servers fully-qualified domain name (FQDN)

Create a new certificate using Exchange 2013 server and with SAN of existing OWA URL (e.g. Mail.domain.com), autodiscovery URL (e.g. Autodiscovery.domain.com) and legacy URL (eg. Legacy.domain.com) to point it to the legacy exchange server. Include additional URLs, if required.

Prepare to configure internet firewall to point all OWA (mail.domain.com) web Internet traffic to the load balancer, if you have multiple Exchange 2013 CAS servers, else you can directly point to Exchange 2013, if you have one Exchange server. This is important because Exchange 2013 CAS server has a point of contact for all OWA requests, from both internal and external.

Add legacy.domain.com DNS entry for both; internally and externally to point out to the legacy Exchange 2010 CAS servers and also open the internet firewall ports to point legacy.domain.com to exchange 2010 CAS servers.

If you have TMG/UAG server in the DMZ, create an additional OWA rule for legacy.domain.com to point to the Exchange 2010 server. 

Free Windows Admin Tool Kit Click here and download it now
August 31st, 2015 12:03am

I think my question wasn't clear.

It is for branch site which ALREADY has 2010 with default URLs, means servername.contoso.com with users in.

In this case if we introduce 2013 in this branch, how can we move namespace when it is servername, means we have to change web services URL to mailbranch.contoso.com in existing 2010 before implementing 2013. 

So is my this understanding is correct?

August 31st, 2015 3:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics