Escolar Documentos
Profissional Documentos
Cultura Documentos
In the current article, I would like to review the subject of the required preparation
that we will need to implement in the Exchange CAS 2007 environment before or
while we are moving to the new Exchange 2013 coexistence environment.
In this article, we will briefly review the different parts that we will need to relate
to when implementing Exchange 2013/2007 coexistence environment and review in
more details the specific updates that relate to the legacy namespace that we need
to configure the different Exchange CAS 2007 services.
Page 2 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 3 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 4 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
This commercial certificate that will be leveraged by external clients will contain at a
minimum three SAN value (note that other scenarios may require you to add
additional values):
mail.contoso.com (your primary OWA/EAS/OA accesses URL)
autodiscover.contoso.com
legacy.contoso.com (your OWA/EAS namespace for legacy mailbox access)
Page 5 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 6 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
In a Split DNS infrastructure, the updates of the DNS records will need to be
implemented for the Internal DNS infrastructure and the External DNS
infrastructure,
Page 7 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
In the following diagram, we can see an example of the required DNS configuration
settings.
Page 8 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 9 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 10 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 11 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Other considerations
When implementing an Exchange 2013 coexistence environment, there are many
other additional elements and consideration that need to be included in the
preparation checklist. Its recommend to read the detailed description that appear
in the Exchange Server Deployment Assistant
Page 12 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Firewall infrastructure
We will need to update the Firewall rule that relates to the mail infrastructure
was pointed to the IP address of the Exchange 2007 server to the new IP
address of the Exchange 2013 server.
When we say that: we need to update the Exchange CAS 2007 URL address the
meaning is: replacing the host name part of the Exchange CAS 2007 URL address
that is allocated for the different Exchange CAS 2007 services.
The new legacy namespace that we update is related to the part of the FQDN from
the URL address of a specific Exchange web service. In other words: we dont
Page 13 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
change or update that structure of the Exchange CAS 2007 URL address but only
the server name.
For example: in case that the URL address of OWA mail services was:
https://mail.o365info.com/owa
We will update the URL address to use the new
FQDN: legacy.mail.o365info.com and the new URL address will
be: https://legacy.mail.o365info.com/owa
Page 14 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Exchange 2007 OWA clients we will need to update the internal + the external
OWA URL address to use the legacy namespace.
Exchange 2007 ActiveSync clients external Exchange 2007 ActiveSync will be
served by the Exchange CAS 2013. For this reason we need to set the external
URL address to empty.
Regarding the internal ActiveSync URL, we will need to set the URL address to use
the legacy namespace.
Exchange 2007 Outlook clients in case that the Exchange CAS 2007 support
Outlook Anywhere services, we can leave the value of the external host name
as it is because the value is based on the primary namespace. In case that the
Page 15 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Exchange CAS 2007 didnt include support for Outlook Anywhere services, we will
need to enable the Outlook Anywhere services and for the value of the external
host name use the host name who will be mapped to the Exchange CAS 2013
server.
Page 16 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 17 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
ActiveSync
Page 18 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 19 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Verify if the Exchange CAS 2007 supports the Outlook Anywhere services.
Case 1: in case that the Exchange CAS 2007 support Outlook Anywhere services, we
will need to update the authentication protocol setting (in the next section xxx we
will relate to the authentication protocol setting).
Case 2: in case that the Exchange CAS 2007 doesnt support Outlook Anywhere
services, we will need to enable the Outlook Anywhere services, and for the value of
the external host name choose the host name who is used by Exchange CAS 2013.
For example, in our scenario, we will configure the external host name
as: mail.o365info.com
External host name
Outlook
Anywhere
We will need to verify that the value of the external host name
uses the primary namespace. In our scenario, the external host
name is: mail.o365info.com
Page 20 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 21 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
To be able to simplify the update operation, we can use a simple PowerShell script
which includes two variables: the Exchange CAS 2007 server name + the legacy
namespace.
After we update these variables, we apply the legacy namespace to all the required
Exchange CAS 2007 URL addresses.
Set the Exchange CAS 2007 services.
Page 22 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
In our example, we will set the following Exchange CAS 2007 services:
OWA
ActiveSync
Exchange web service
The updates will include the legacy namespace that we have chosen for our legacy
Exchange 2007 infrastructure. In our scenario, the legacy namespace
is: legacy.mail.o365info.com
The Exchange CAS 2007 server name in our scenario is: CAS2007
In the following diagram, we can see that syntax of the PowerShell syntax that we
will need to use
Page 23 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Page 24 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
Get-ActiveSyncVirtualDirectory -Server CAS2007 | Set-ActiveSyncVirt
ualDirectory -InternalURL "https://legacy.mail.o365info.com/Microso
ft-Server-ActiveSync" -ExternalURL $null
The PowerShell command that we use for viewing the setting of the ActiveSync URL
address is:
PowerShell
Get-ActiveSyncVirtualDirectory -server CAS2007 | FL identity, inter
nalUrl, ExternalUrl
The PowerShell command that we use for viewing the setting of the Exchange web
service URL address is:
PowerShell
Get-WebServicesVirtualDirectory -server CAS2007 | FL identity,
internalUrl, ExternalUrl
Page 25 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
The PowerShell command that we use for viewing the setting of the Outlook
Anywhere settings is:
PowerShell
Get-OutlookAnywhere -Server CAS2007
Page 26 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence
In case that the Exchange CAS 2007 was registered at the Active Directory SCP using
an internal name, we will need to update the existing value of the Autodiscover
Endpoint to point the Exchange CAS 2013 Autodiscover Endpoint name.
The syntax of the PowerShell that we will us for updating and viewing the value of
theAutoDiscoverServiceInternalUri is:
Additional reading
Page 27 of 27 | Part 09#23 | The checklist for preparing your Exchange 2007 infrastructure
for Exchange 2013 coexistence