Exchange SQL And IIS- P130 pot

This page intentionally left blank 623 Chapter 10 Solutions in this chapter: ■ Preparing the Environment for a Transition to Exchange Server 2007 ■ Exchange 2003 and Exchange 2007 Coexistence ■ Replicating Public Folders to Exchange 2007 ■ Pointing Internet Clients to the Client Access Server ■ Moving Legacy Mailboxes to Exchange 2007 ■ Redirecting Inbound Mail to the Exchange 2007 Server ■ Decommissioning the Legacy Exchange Server ˛ Summary ˛ Solutions Fast Track ˛ Frequently Asked Questions Transitioning from Exchange 2000 or 2003 to Exchange 2007 624 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 Introduction Since only the Exchange 2007 64-bit version is supported in a production environment, and because previous versions of Exchange (2000 and 2003) exist only in 32-bit versions, an in-place upgrade from Exchange 2000 or 2003 to Exchange Server 2007 isn’t a supported scenario. Instead you must do a transition from these legacy Exchange Server(s) to Exchange 2007. A transition is the process in which you perform an upgrade to Exchange 2007—that is, you move data from any legacy Exchange servers in your Exchange organization to new Exchange 2007 servers, after which you decommission the legacy Exchange servers. A transition should not be confused with a migration; unlike a transition, a migration is the process in which you move data from a non-Exchange messaging system (such as GroupWise, Lotus Notes or SendMail) to an Exchange organization, or move data from a legacy Exchange organization in an existing Active Directory Forest to an Exchange organization in a new Active Directory Forest. In this chapter we’ll look more closely at performing a transition from a legacy Exchange organization consisting of a single Exchange 2003 server to an Exchange 2007 server, which will be installed as a typical Exchange Server installation. Preparing the Environment for a Transition to Exchange Server 2007 Before we begin deploying the Exchange 2007 Server in our legacy Exchange organization, there are several preliminary requirements that we must complete. We need to prepare the Active Directory forest, the existing Exchange organization, and the server on which we plan to install Exchange Server 2007. In the following sections, we’ll go through each preliminary requirement that must be completed before we even start to think about deploying Exchange Server 2007. Preparing the Active Directory Forest First we must make sure that the domain controller that is the schema master in the Active Directory forest runs Windows Server 2003 with at least Service Pack 1 applied. This is also true for any Global Catalog servers in each Active Directory site in which you plan to deploy Exchange 2007. We recommend that you run Windows Server 2003 with Service Pack 1 applied on all domain controllers in the Active Directory forest, since this version supports Exchange 2007 service notifi cations, allows users to browse the address book in Microsoft Outlook Web Access, and provides the ability to look up distribution list membership in a more effi cient manner than in Windows 2000 Server. NOTE If you have any non-English domain controllers in your Active Directory Forest, you should also be sure you apply the hotfi x mentioned in MS KB article 919166 (http://support.microsoft.com/kb/919166) to the respective domain controller; otherwise you can experience issues accessing the address book when you’re using OWA 2007. Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 625 Although Exchange 2007 supports 32-bit-based Global Catalog servers, you should seriously consider replacing them with 64-bit-based servers instead. An organization with 20,000 Active Directory objects or more will gain a signifi cant increase in performance by doing so. Actually, you can expect a 64-bit Global Catalog server with 14 GBs of RAM installed to handle the workload of up to 11 32-bit Global Catalog servers. Talk about an improvement that saves you a lot of money on hardware in the long term as well as patch management! Finally, Exchange 2007 requires that the domain functional level is set to Windows 2000 Server or Windows Server 2003. You do this by following these steps: 1. Open the Active Directory Users and Computers MMC snap-in on a domain controller in your Active Directory, then right-click the domain and choose Raise Domain Functional Level in the context menu. Now change the domain functional level to Windows Server 2003, as shown in Figure 10.1, then click Raise. Figure 10.1 Raising the Domain Functional Level to Windows Server 2003 2. You will now receive an informational note similar to one shown in Figure 10.2. If you’re dealing with a large topology that contains many domain controllers, you should keep this information in mind, but if you have only a couple of domain controllers deployed, you can safely ignore this information. Click OK. 626 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 Figure 10.2 Raise Domain Functional Level Information Preparing the Legacy Exchange Organization Since Exchange Server 2007 requires the legacy Exchange organization to run 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. Does this mean that you cannot do a transition directly from Exchange 5.5 to Exchange 2007 in the same Active Directory forest? Yes, that is correct! Those of you, hopefully few, who still have an Exchange 5.5 organization and want to move to Exchange 2007 must fi rst upgrade to 2000 or 2003 and then do the transition from Exchange 2000 or 2003 to Exchange 2007. You must also make sure that any Exchange 2000 servers in your Exchange organization run with Exchange 2000 Service Pack 3 and that any Exchange 2003 servers have Service Pack 2 applied. In addition, you should note that if you plan to keep at least one Exchange 2000 or 2003 server in the Exchange organization, the following services are unsupported by Exchange Server 2007: ■ Novell GroupWise connector (Exchange 2003 Service) ■ Microsoft Mobile Information Server (Exchange 2000 Service) ■ Instant Messaging Service (Exchange 2000 Service) ■ Exchange Chat Service (Exchange 2000 Service) ■ Exchange 2000 Conferencing Server (Exchange 2000 Service) ■ Key Management Service (Exchange 2000 Service) ■ cc:Mail connector (Exchange 2000 Service) ■ MS Mail connector (Exchange 2000 Service) NOTE At the time of this writing, the Exchange Product Group is working on an Exchange 2007 version of the Novell GroupWise connector. When you’re ready to switch your Exchange organization to native mode, you do so by following these steps: 1. Open the Exchange 2003 System Manager. Right-click the Exchange Organization node and select Properties in the context menu. Now click the Change Mode button, as shown in Figure 10.3. . 2000 or 2003 and then do the transition from Exchange 2000 or 2003 to Exchange 2007. You must also make sure that any Exchange 2000 servers in your Exchange organization run with Exchange 2000. Service) ■ Exchange Chat Service (Exchange 2000 Service) ■ Exchange 2000 Conferencing Server (Exchange 2000 Service) ■ Key Management Service (Exchange 2000 Service) ■ cc:Mail connector (Exchange. a production environment, and because previous versions of Exchange (2000 and 2003) exist only in 32-bit versions, an in-place upgrade from Exchange 2000 or 2003 to Exchange Server 2007 isn’t