Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 627 Figure 10.3 Switch the Exchange Organization to Native Mode 2 You will now receive a warning message similar to the one shown in Figure 10.4. Click Ye s , click OK, and then close the Exchange 2003 System Manager. Figure 10.4 Switch the Exchange Organization to Native Mode 628 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 SOME INDEPENDENT ADVICE If it’s not already the case, we also recommend that you check Display routing groups and Display administrative groups (refer back to Figure 10.3) because we’ll need to verify the existence of the routing and administrative groups created by Exchange 2007 Setup later in this chapter. Figure 10.5 Exchange 2007 Readiness Check Option in ExBPA 2.7 If you’re unsure whether your environment is ready for the deployment of the fi rst Exchange 2007 server, it’s a good idea to run the latest version of the Exchange Best Practices Analyzer (ExBPA) to see if there’s anything you need to do before you can proceed. The latest version of ExBPA, version 2.7, which you can download at www.exbpa.com, includes an Exchange 2007 Readiness Check option, as shown in Figure 10.5. Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 629 Suppressing Link State Updates 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, however, that this is required only if you’re planning to establish more than one routing group connector in the organization. To suppress Link State updates on any Exchange 2000 or 2003 servers in your organization: 1. Log onto the respective servers, then open the registry editor by clicking Start | Run and typing regedit followed by pressing Enter. 2. Now navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ RESvc\Parameters and right-click on Parameters, then select New | DWORD. Type SuppressStateChanges as the name value for the new DWORD. Finally, double-click SuppressStateChanges and enable it by entering 1 in the data value fi eld, as shown in Figure 10.6. When the SuppressStateChanges key has been created, close the registry editor, then restart the Simple Mail Transfer Protocol (SMTP) service, the Microsoft Exchange Routing Engine service, and Microsoft Exchange MTA Stacks service so that the change takes effect. Figure 10.6 Suppressing Link State Updates 630 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 For the purpose of this explanation, we’re deploying a single Exchange 2007 server into a legacy Exchange organization consisting of a single Exchange 2003 server, which means we don’t need to suppress Link State updates. But as mentioned, this is a required step on all legacy Exchange servers if you’re planning to establish more than one routing group connector in your Exchange organization. Keep this in mind if you’re planning to move from a multiple Exchange 2000 or 2003 scenario to Exchange 2007. Extending the Active Directory With all prerequisites fulfi lled, we can move on and prepare the Active Directory using the respective Exchange 2007 Setup.exe switches. Exchange 2007 Setup includes several switches; in this section we’ll go through each of those related to preparing the Active Directory. IMPORTANT Each of the switches we discuss here will run automatically during the deployment of the fi rst Exchange 2007 server in the Exchange legacy organization (if the account you’re logged on with has Schema and Enterprise Admin rights!), so it’s not mandatory that you run them before installing Exchange 2007. However, depending on the size as well as the topology of your environment, it might be wise to prepare the Active Directory fi rst using these switches before you start the actual deployment process. Prepare Legacy Exchange Permissions The fi rst thing we need to do in deploying an Exchange 2007 into a legacy Exchange organization is to run Setup.com /PrepareLegacyExchangePermissions, to grant specifi c Exchange permissions in the Active Directory domain(s) in which one or more Exchange 2000 or 2003 Servers exists or where Exchange 2000 or 2003 DomainPrep has been executed. The reason we must run Setup.com /PrepareLegacyExchangePermissions is that the Exchange 2003 or Exchange 2000 Recipient Update Service won’t otherwise function correctly after the Active Directory schema has been updated with Exchange 2007-specifi c attributes. TIP For a detailed explanation of why Setup.com /PrepareLegacyExchangePermissions must be run in an Active Directory domain in which one or more Exchange 2000 or 2003 Servers exists or where Exchange 2000 or 2003 DomainPrep has been executed, search for “preparing legacy Exchange permissions” in the Exchange 2007 Documentation found at www.microsoft.com/technet/prodtechnol/exchange/e2k7help. Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 631 To r u n Setup.com /PrepareLegacyExchangePermissions, you must open a Command Prompt window and navigate to the directory, network share, or DVD media containing your Exchange 2007 Setup fi les, then simply type Setup.com /PrepareLegacyExchangePermissions followed by pressing Enter, as shown in Figure 10.7. Bear in mind that the account you’re logged on with must be a member of the Enterprise Admins group. Figure 10.7 Preparing Legacy Exchange Server Permissions SOME INDEPENDENT ADVICE Some of you might be in a situation where you want to prepare the Active Directory domain before you install the x64-bit version of Windows Server 2003 on a server in the Active Directory forest, and therefore you cannot run Setup.com /PrepareLegacy- ExchangePermissions using the 64-bit version of Exchange 2007 because you don’t have any x64-bit Windows 2003 Servers deployed yet. But fear not—using the 32-bit version of Exchange 2007 to prepare your production Active Directory environment is fully supported. As mentioned in the introduction to this chapter, the 32-bit version of Exchange 2007 is not supported in a production environment except for management tasks, and preparing the Active Directory is considered a management task. Prepare Schema The next command to run to prepare the environment is Setup.com /PrepareSchema, which will connect to the domain controller schema master and import LDAP fi les to update the schema with Exchange 2007-specifi c attributes. To do so, open a Command Prompt window and type Setup.com /PrepareSchema followed by pressing Enter, as we did with the previous switch. . click OK, and then close the Exchange 2003 System Manager. Figure 10.4 Switch the Exchange Organization to Native Mode 628 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 SOME. “preparing legacy Exchange permissions” in the Exchange 2007 Documentation found at www.microsoft.com/technet/prodtechnol /exchange/ e2k7help. Transitioning from Exchange 2000 or 2003 to Exchange 2007. Exchange 2000 or 2003 to Exchange 2007 For the purpose of this explanation, we’re deploying a single Exchange 2007 server into a legacy Exchange organization consisting of a single Exchange 2003 server,