Exchange SQL And IIS- P136 ppsx

As you saw throughout this chapter, making a transition from an Exchange 2000 or 2003 server to Exchange 2007 in the same Active Directory forest is a straightforward process, and since

4 On the Installation Summary page, click Next, and wait for the Exchange 2003 uninstall

process to complete (see Figure 10.27)

Figure 10.26 Exchange 2003 Installation Wizard Component Selection Page

Figure 10.27 The Exchange 2003 Uninstall Process

NOTE

If the Exchange 2000 Setup fi les aren’t located on an accessible drive or network

share, you will be prompted to insert the Exchange 2003 CD media during the

uninstallation process

Figure 10.28 Exchange 2003 Successfully Uninstalled

NOTE

If the Exchange 2003 uninstallation fails for some reason, it could be necessary to remove the Exchange 2003 server by deleting the Server object in the Exchange System Manager, or if you’re unsuccessful doing this, too, then by using ADSI Edit

5 When the uninstall process has completed, click Finish to exit the Exchange 2003 Setup

Wizard (see Figure 10.28)

As you saw throughout this chapter, making a transition from an Exchange 2000 or 2003 server to

Exchange 2007 in the same Active Directory forest is a straightforward process, and since Exchange

2007 coexists just fi ne with legacy Exchange servers, you can do the transition at your own pace

Coexistence support is laudable, since a transition process typically happens in several phases First,

you redirect your Internet clients to the client access server (CAS), then move the legacy mailboxes

to the Mailbox server, and fi nally, point inbound mail to the Hub Transport server

Solutions Fast Track

Preparing the Environment for a

Transition to Exchange Server 2007

˛ The domain controller that is the schema master in the Active Directory forest should run Windows Server 2003 with at least Service Pack 1 applied

˛ Any Global Catalog servers in each Active Directory site in which you plan to deploy

Exchange 2007 should run Windows Server 2003 with at least Service Pack 1 applied

˛ For any non-English domain controllers in your Active Directory forest, apply the hotfi x

mentioned in MS KB article 919166 (http://support.microsoft.com/kb/919166)

˛ Exchange 2007 requires that the domain functional level is set to Windows 2000 Server or Windows Server 2003

˛ Since Exchange Server 2007 requires that the legacy Exchange organization is running in native mode, we need to decommission any pre-Exchange 2000 servers (that is, Exchange 5.5 servers and previous versions) that exist in the Exchange organization

˛ Depending on your topology, Link State updates must be suppressed on any Exchange

2000 or 2003 servers in the Exchange legacy organization when you’re deploying an

Exchange 2007 Server Bear in mind that this is required only if you’re planning to

establish more than one routing group connector in the organization

Exchange 2003 and Exchange 2007 Coexistence

˛ are several things you should be aware of in dealing with a coexistence environment

consisting of Exchange or 2003 and Exchange 2007 Most of the management-related tasks (creating and moving mailboxes and administering public folders) were mentioned in

Chapter 3

˛ Most of the Global Settings that originally were confi gured on an Exchange 2000 or

2003 server will be transferred to the Exchange 2007 server automatically, since global

Exchange settings are stored in Active Directory This means that recipient policies, Internet Message Formats, SMTP connectors, and Exchange delegation permissions are applied to user mailboxes stored on the Exchange 2007 as well

˛ Any Exchange ActiveSync (EAS) device policy settings you have enabled on an Exchange

2003 SP2 server will not be transferred to Exchange 2007 This means that you must make sure that you enable any EAS polices you created on the Exchange 2007 server for the legacy mailboxes you move to the Exchange 2007 Server

Replicating Public Folders to Exchange 2007

˛ Managing Public Folders using the EMC is not possible in Exchange 2007 RTM but will

be integrated with Exchange 2007 Service Pack 1

˛ Even if you don’t use Public Folders to store data in your environment, there’s one other reason that you might want to keep the Public Folder database mounted on your Exchange

2007 server As you might know, Exchange 2007 no longer uses a Public Folder (or more specifi cally, a System Folder named SCHEDULE+ FREE BUSY in your Public Folder hierarchy) to store free/busy information for the mailbox users in the organization Instead, free/busy information is stored directly in each user’s mailbox and retrieved using a new Web-based service called the Availability service

˛ If you don’t use Public Folders to store data and only have Outlook 2007 clients deployed

in your organization, you can safely remove the Public Folder database because you don’t have anything to use it for

˛ 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

Pointing Internet Clients to the Client Access Server

˛ When the CAS has been deployed, you should 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, this change is done at your ISA Server fi rewall If for some reason you don’t use ISA Server in your DMZ but perhaps a Check Point

FireWall-1 or a wannabe fi rewall such as a Cisco PIX, you should do the redirection there

˛ When you have pointed your Internet clients to the CAS, your users will no longer be able

to access their mailboxes using Outlook Mobile Access (OMA), because OMA has been discontinued in Exchange 2007