Prepare AD The Setup.com /PrepareAD command is used to confi gure global Exchange objects in Active Directory, create the Exchange Universal Security Groups (USGs) in the root domain, and prepare the current domain. The global objects reside under the Exchange organization container. In addition, this command creates the Exchange 2007 Administrative Group, which is named Exchange Administrative Group (FYDIBOHF23SPDLT), as well as creating the Exchange 2007 Routing Group, called Exchange Routing Group (DWBGZMFD01QNBJR). You can run the Setup.com /PrepareAD command before running /PrepareLegacyExchangePermissions and /PrepareSchema, as shown in Figure 10.9. Doing so will run the /PrepareLegacyExchangePermissions and /PrepareSchema commands automatically. Running this command requires you log on with an account that is a member of the Enterprise Admins group. Figure 10.8 Running Setup.com with the PrepareSchema Switch 632 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 Setup will now update the schema as necessary, as shown in Figure 10.8. To run this command, the account you’re logged on with must be a member of both the Enterprise and Schema Admins groups. As you might be aware, Exchange 2007 doesn’t use Routing Groups and Administrative Groups, as Exchange 2000 or 2003 did. Administrative Groups have been dropped completely, and message routing in Exchange 2007 is based on Active Directory sites. But for Exchange 2007 to c-exist with Exchange 2000 or 2003, Exchange must create the mentioned Administrative Group and Routing Group, which can only be viewed via an Exchange 2000 or 2003 System Manager or by using ADSI Edit, as shown in Figures 10.10 and 10.11. Figure 10.9 Running Setup.com with the PrepareAD Switch Figure 10.10 Exchange 2007 Administrative and Routing Group in the Exchange 2003 System Manager Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 633 634 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 SOME INDEPENDENT ADVICE Okay, with all these boring switches, it’s time for a little fun! Did you know that although coding a product such as Exchange 2007 is a lot of hard work, the Exchange Product Group always has time for a little humor? To prove it, let’s take the GUID of the Administrative Group shown in Figure 10.10 and shift each letter upward. Now do the same for the GUID of the Exchange Routing Group shown in Figure 10.11, but do it downward. Did you manage to see what it translates to? Yes, it’s EXCHANGE12ROCKS! For those who don’t know, “Exchange 12” was the codename for Exchange Server 2007 until the product got a real name in April 2006. Figure 10.11 Exchange 2007 Administrative and Routing Groups in ADSI Edit Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 635 PrepareDomain and PrepareAllDomains It’s also possible to prepare a local domain or all domains in the Active Directory using the Setup.com / PrepareDomain and Setup.com /PrepareAllDomains, respectively. These switches will set permissions on the Domain container for the Exchange servers, Exchange Organization Administrators, Authenticated Users, and Exchange Mailbox Administrators; create the Microsoft Exchange System Objects container if it does not exist; set permissions on this container for the Exchange servers, Exchange Organization Administrators, and Authenticated Users; and in the current domain, create a new domain global group called Exchange Install Domain Servers. In addition, it will add the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain. Like the commands we’ve already been through, these commands also need to be run from a Command Prompt window, as shown in Figure 10.12. Figure 10.12 Running Setup.com with the PrepareDomain Switch Preparing the Exchange 2007 Server When our environment has been prepared for Exchange Server 2007, the next step is to prepare the server on which you plan to install Exchange 2007 and then begin the actual Exchange installation. Since all these steps were covered intensely in Chapter 2, we won’t repeat them here, but we will quickly mention a couple of things that are different in installing Exchange 2007 into a legacy Exchange organization. During the installation, you’re given the option of creating a routing group connector between the administrative group containing the legacy Exchange server(s) and the Exchange 2007 administrative group, as shown in Figure 10.13. 636 Chapter 10 • Transitioning from Exchange 2000 or 2003 to Exchange 2007 This routing group connector is created in both directions and needs to be created to establish mail fl ow between the servers in the legacy routing group and the Exchange 2007 routing group. In addition, the Exchange 2007 Setup Wizard won’t ask you whether a Public Folder database to support legacy Outlook clients should be created but will instead do so automatically. The reason Figure 10.13 Preparing the Exchange 2007 Routing Group Connector . creating the Exchange 2007 Routing Group, called Exchange Routing Group (DWBGZMFD01QNBJR). You can run the Setup.com /PrepareAD command before running /PrepareLegacyExchangePermissions and /PrepareSchema,. have been dropped completely, and message routing in Exchange 2007 is based on Active Directory sites. But for Exchange 2007 to c-exist with Exchange 2000 or 2003, Exchange must create the mentioned. the PrepareAD Switch Figure 10.10 Exchange 2007 Administrative and Routing Group in the Exchange 2003 System Manager Transitioning from Exchange 2000 or 2003 to Exchange 2007 • Chapter 10 633 634