Configuring Exchange Server 2013 for use with existing Exchange organizations
When managing Exchange servers, you should use the administrative
tools for that Exchange Server version. Exchange Admin Center and
Exchange Management Shell are the primary management tools for Exchange
Server 2013. Mailboxes located on Exchange Server 2007 and Exchange
Server 2010 servers are also displayed in Exchange Admin Center.
You can manage the Exchange 2007 or 2010 mailbox properties using
Exchange Admin Center or Exchange Management Shell. You can use either
tool to move mailbox recipients from Exchange 2007 or Exchange 2010 to
Exchange 2013.
When deploying Exchange 2013 in an Exchange 2007 or Exchange 2010 organization, keep the following in mind:
-
If you want to use the Exchange Server 2013 Client Access server
role, you must deploy the Client Access server role in each Active
Directory site that contains the Mailbox Server role. Clients will see
the Outlook Web App or Exchange ActiveSync version that is on their
mailbox store. With Client Access arrays, the Client Access servers
must all be members of the same Active Directory site.
-
Exchange
2007 mailboxes can be enabled with unified messaging, but they will
need an Exchange 2007 Unified Messaging server. Similarly, Exchange
2010 mailboxes can be enabled with unified messaging, but they will
need an Exchange 2010 Unified Messaging server.
-
If you want to use the legacy Edge Transport server role, you must
deploy this server before installing Exchange 2013. You will then need
to configure SMTP connectors to accept mail from and send mail to the
Internet. Other modifications are required to mail Exchange and smart
host records. Further, you can synchronize the Edge Transport server’s
AD LDS data with Active Directory only if the Exchange Server 2013
Active Directory preparation process has been performed.
-
For management, you must deploy at least one Mailbox server and one Client Access server running Exchange 2013.
Setting the default Offline Address Book
A new Offline Address Book (OAB) will be created when you deploy the
first Exchange 2013 Mailbox server in an existing Exchange
organization. All existing clients that use OAB will see this new OAB
by default the next time they perform an OAB update, and they also will
perform a full OAB download. If you don’t want this to happen, you must
configure existing mailbox databases to explicitly point to the current
default OAB before you deploy the first Exchange 2013 server.
You can do this by following these steps:
-
In Exchange Management Console, navigate to Organization
Configuration, Mailbox, Database Management, and then open the Mailbox
Database Properties dialog box for the mailbox database you want to
work with.
-
On the Client Settings tab of the Mailbox Database Properties dialog
box, you’ll see an entry for the Offline Address Book and a related
Browse button. Use this option to explicitly set the default OAB.
-
Repeat this process for each mailbox database that you want to update.
You also can use Exchange Management Shell to view all mailbox
databases without a default OAB explicitly set on them and then
explicitly set a default OAB. Start by entering the following command:
Get-MailboxDatabase | Where {$_.OfflineAddressBook -eq $Null} |
FT Name,OfflineAddressBook -AutoSize
If no values are returned, a default OAB is already explicitly set
throughout the organization. If values are returned, you need to
configure some databases with an explicitly defined default OAB. The
following commands locate all mailbox databases in an Exchange 2007 or
Exchange 2010 environment with no default OAB defined at the database
level and then set these mailbox databases to the current default OAB
in the organization:
Get-MailboxDatabase | Where {$_.OfflineAddressBook -eq $Null} |
Set-MailboxDatabase -OfflineAddressBook (Get-OfflineAddressBook |
Where {$_.IsDefault -eq $True})
If
you have both Exchange 2007 and Exchange 2010 deployed on premises, you
must run the command twice (using the respective Exchange Management
Shell for each version).
Finally, you can confirm that all mailbox databases now have an
explicitly defined default OAB, by re-running the first command. The
command should return no values.
Moving to Exchange Server 2013
Most organizations have existing Exchange installations. When moving
Exchange 2007 or Exchange 2010 installations to Exchange Server 2013,
you cannot perform an in-place upgrade. Instead, you must install new
Exchange Server 2013 servers into the existing organization and then
migrate to Exchange Server 2013.
Migration from Exchange 2007 or Exchange 2010 to Exchange 2013
involves installing Exchange Server 2013 on new servers and then moving
the mailboxes and public folders from your existing installations to
the new installation. In a migration, only mailbox and public folder
data is moved, and any Exchange configuration data is not maintained.
The steps you perform to migrate from Exchange 2007 or Exchange 2010 to Exchange 2013 are as follows:
-
Plan to migrate all Exchange servers in a particular site to
Exchange 2013 at the same time. You should start with
Internet-accessible Active Directory sites and then migrate internal
Active Directory sites. For each Exchange 2013 Client Access server,
you can configure only one Outlook Web App URL for redirection.
-
If you plan to have a legacy Edge Transport server in your Exchange
2013 organization, install it prior to installing Exchange 2013 on any
server in your organization.
-
Install Exchange Server 2013 on new hardware and make it a member of
the appropriate domain in the forest. You should install the Mailbox
Server role first and then the Client Access Server role. You can
install these roles on a single server or on multiple servers. You must
deploy a Client Access server in each Active Directory site that has a
Mailbox server.
-
Move Internet mail flow from Exchange 2007 or Exchange 2010 to Exchange 2013.
-
Move mailboxes and public folders from the existing Exchange 2007 or
Exchange 2010 installations to the new Exchange Server 2013 Mailbox
server or servers. If you move a mailbox that is part of an email
address policy, the email address for the mailbox is automatically
updated based on the settings in the email address policy. In this
case, the new email address becomes the primary address, and the old
email address becomes the secondary address.
During a migration, the version of a CAS feature that a user sees,
such as Outlook Web App, depends on where the user’s mailbox is
located. If the mailbox is on an Exchange 2007 server, the user sees
Exchange 2007 versions of CAS features. When you move the mailbox to
Exchange 2013, the user will see Exchange 2013 versions of CAS features.
Real World
You
move mailboxes from Exchange 2007 or Exchange 2010 to Exchange 2013 by
using an online move. Perform the move from the Exchange 2013 server by
using move mailbox requests, either with Exchange Management Shell or
Exchange Admin Center. You can’t use the Exchange Management tools for
Exchange 2007 or Exchange 2010 to move the mailboxes.
-
Once you’ve complete the move and have validated the configuration,
you can remove unneeded Exchange 2007 or Exchange 2010 servers from the
organization.
Caution
Before removing the last Exchange 2007 or Exchange 2010
server with a particular role, you must be sure that you will never
need to introduce an Exchange 2007 server with the role again. Once you
remove the last Exchange 2007 or Exchange 2010 server with a particular
role, you can never add another one with that role.
