Exchange SQL And IIS- P134 pot

642 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007
Even if you have legacy Outlook clients in your organization, you don’t need to set up a replica
for the SCHEDULE+ FREE BUSY or the OFFLINE ADDRESS BOOK system folder, since this
will be done automatically when you deploy an Exchange 2007 server in a legacy Exchange
organization.
When all Public Folders have been replicated to the Exchange 2007 server, you can remove the
old Exchange 2000 or 2003 server(s) from the replica lists and then dismount the old Public Folder
database. You should verify that your clients still are capable of seeing Public Folder data as well free/
busy information and accessing the offl ine address book before you delete it, though. If this is not the
case, we recommend that you wait a little longer so that you’re sure the replication has occurred
properly.
Pointing Internet Clients to
the Client Access Server
Now would be a good time to point any Internet client that is OWA, EAS, or RPC over HTTP
(now called Outlook AnyWhere) in your organization to the client access server running on the
Exchange 2007 server. If you’re using a fi rewall such as ISA Server (which you do, right?), this change
is done at your ISA Server fi rewall. If for some reason you don’t use an ISA Server in your DMZ but
perhaps a Check Point FireWall-1 or another “fi rewall” such as a Cisco PIX, you should do the
redirection there. If you don’t have a fi rewall, you should make the change on the external DNS
server hosting your Internet domain.
So, you ask, will any users with a mailbox on my Exchange 2000 or 2003 server still be able to use
OWA, Exchange ActiveSync, or Outlook AnyWhere (formerly known as RPC over HTTP) to access
their mailboxes? Yes, this will work just fi ne, since the client access server is backward compatible and
will redirect the clients to the respective legacy mailboxes on the Exchange 2000 or 2003 server.
SOME INDEPENDENT ADVICE
Unlike previous versions of Outlook Web Access (OWA), OWA 2007 doesn’t include a
GUI for accessing Public Folders. This means that to access Public Folders using
Internet Explorer, you must open a separate browser window and type
https://FQDN/public. It’s important that you’re aware of this missing feature.
NOTE
If your ISA server is confi gured to preauthenticate your OWA users, you must

change the Authentication method for the OWA virtual directory under Server
Confi guration | Client Access in the EMC to Basic authentication, since it’s
configured to use forms-based authentication by default.
Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 643
NOTE
When you make these changes, your users will no longer be able to access their
mailboxes using Outlook Mobile Access (OMA), because OMA has been discontinued
in Exchange 2007.
Moving Legacy Mailboxes
to Exchange 2007
Now we have reached the point at which we’re going to move our legacy mailboxes from Exchange
2000 or 2003 Server to Exchange 2007. Doing so is a straightforward process and can be done using
either the Move Mailbox Wizard in the EMC or the Move-Mailbox CMDlet in the EMS. We’ll use
the EMC. Do the following:
1. If it’s not already open, launch the EMC, then expand the Recipient Confi guration work
center and click the Mailbox subnode. Now highlight all the legacy mailboxes, as shown in
Figure 10.18, and then click the Move Mailbox task in the Action pane.
Figure 10.18 Selecting Legacy Mailboxes in the Exchange Management Console
644 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007
2. This will launch the Exchange 2007 Move Mailbox Wizard, where you need to specify the
destination server, storage group, and mailbox database. Select the Exchange 2007 Server
in the drop-down box (see Figure 10.19), and then click Next.
Figure 10.19 Specifying the Exchange 2007 Server as the Destination Server
3. On the Move Option page, specify how you want to manage any corrupted messages found
in a mailbox, then click Next. This will bring us to the Move Schedule page, where we can
specify whether we want to move the mailboxes immediately or at a scheduled time. In
addition, we have the option of cancelling the Move Mailbox job after X number of hours.
When you have made your selections, click Next, then click Move on the Move Mailbox
page to begin moving the mailboxes to the Exchange 2007 server, as shown in Figure 10.20.
Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 645

Figure 10.20 The Move Mailboxes Summary Page
As is the case with the Move Mailbox Wizard in Exchange 2003, the Exchange 2007 Move
Mailbox Wizard can move four mailboxes at a time, and only one instance of the wizard can run on
a server.
4. When all the mailboxes have been moved to the Exchange 2007 server, click Finish to
exit the Move Mailbox Wizard, and then check to make sure that mail fl ow between the
Internet and the mailboxes on the Exchange 2007 server works as expected in both
directions.
646 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007
NOTE
If you want to move the mailboxes using the EMS, do so using the Move-Mailbox
CMDlet. Using the Move-Mailbox CMDlet gives you a set of advanced options,
among which the most interesting one is the option of specifying the number of
mailboxes to be moved at a time (as you read earlier, the Move Mailbox Wizard is
limited to four).
If you wanted to move all mailboxes from a legacy Exchange server named
EDFS02 to the default Mailbox database on an Exchange 2007 server named EDFS03,
you could use one of the below commands:
Get-Mailbox | Where-Object {$_.servername –eq “EDFS02”} | Move-Mailbox –
TargetDatabase: “EDFS03Mailbox Database”
or
Get-mailbox –Server EDFS02 | Move-Mailbox –TargetDatabase “EDFS03Mailbox
Database”
Redirecting Inbound Mail to
the Exchange 2007 Server
When all legacy mailboxes have been moved to the Exchange 2007 server, we can point SMTP
traffi c (port 25/TCP) directly to the Exchange 2007 server so that inbound messages are routed
directly to it. It’s recommended to deploy an Edge Transport server in your perimeter network
(DMZ) and let this server route inbound messages to the Exchange 2007 server on your internal
network. For instructions on how to deploy an Edge Transport server, see Chapter 7.

If you don’t want to deploy an Edge Transport server, you should bear in mind that you need to
change the Permission Groups settings on the Default <server> receive connector under the Server
Confi guration work center node | Hub Transport subnode in the EMC so that Anonymous users are
allowed to connect to the Exchange 2007 server, as shown in Figure 10.21. Otherwise you won’t be
able to receive e-mail messages from other SMTP servers on the Internet.
If you will be running in a coexistence environment for a period of time, it’s important to
understand that mailboxes stored on an Exchange 2007 server must not be managed using the Active
Directory Users and Computers (ADUC) MMC snap-in but instead must be managed using the
EMC or the EMS. However, Exchange 2003 mailboxes can still be managed using ADUC.