72 Chapter 2 • Installing Exchange Server 2007 Summary In this chapter we focused on the hardware, software, and system requirements for an Exchange Server 2007 installation. We went through how you prepare a greenfi eld Active Directory forest (that is, an Active Directory forest without an existing Exchange organization) for an Exchange 2007 Server deployment. We also took a step-by-step walk through the process of installing a typical Exchange 2007 server into an Active Directory forest using both the GUI and the CLI. We touched on how to properly license an Exchange 2007 server and introduced the new Finalize Deployment and End-to-End Scenario task lists. Finally, we took a look at how you can add and remove Exchange 2007 server roles from an existing Exchange 2007 server with multiple server roles already installed, as well as how to completely uninstall Exchange 2007 from a server and ultimately from the Active Directory forest. Solutions Fast Track Exchange 2007 Server Editions and CAL Types ˛ As is the case with previous versions of Exchange, Exchange Server 2007 exists in two different editions: a Standard Edition and an Enterprise Edition. ˛ Exchange 2003 and earlier versions offered only one type of Exchange CAL, but with Exchange 2007 we now have two types: a Standard CAL and an Enterprise CAL. ˛ Before you get too involved in planning the budget for a transition to Exchange 2007 in your organization, you should be aware of one very important thing. Many of you who have Exchange 2003 deployed in your organization could very well be aware of the fact that each Exchange 2003 Client Access License (CAL) included the right to install Outlook 2003 on the devices for which these CALs were obtained. You probably think that this hasn’t changed in regard to Exchange 2007 CALs. Think again because Exchange Server 2007 Standard or Enterprise does not include the right to install Outlook on devices for which CALs are obtained! Exchange 2007 Prerequisites ˛ It’s important that you examine the system hardware, software, and Active Directory requirements before you begin installing Exchange 2007 into a production environment. ˛ You’ll need an x64 architecture-based processor that supports Intel Extended Memory 64 Technology (Intel EM64T) and an AMD 64-bit processor that supports the AMD64 platform, but bear in mind that the Intel Itanium IA64 processor isn’t supported by Exchange Server 2007. ˛ The minimum Windows Active Directory functional level for Exchange 2007 is Windows 2000 native mode. If you are installing Exchange Server 2007 into an existing Exchange organization, it is also important to note that the organization should be running in native mode. Installing Exchange Server 2007 • Chapter 2 73 ˛ Exchange Server 2007 exists in 32-bit and 64-bit versions; however, the 32-bit version is not supported in a production environment and is meant to be used for evaluation and testing purposes only. If you install the 32-bit version of Exchange 2007 in a production environment and experience an issue, you will not be able to get any support from Microsoft Support Services. There is one exception to the rule, though: The 32-bit version of the Exchange 2007 Management Tools (more specifi cally, the Exchange Management Console, the Exchange Management Shell, the Exchange Help fi le, and the Exchange Best Practices Analyzer tool) are supported for management tasks in a production environment. ˛ As most of you might recall, Exchange Server 2000 and 2003 made extended use of the Windows Server 2000 or 2003 SMTP and NNTP services, requiring that they be installed components (both subcomponents of IIS) prior to installing the Exchange Server product itself. Both the Hub Transport server and the Edge Transport server requires that both these services aren’t installed, because NNTP support has been dropped in Exchange 2007 and Exchange 2007 now has its own SMTP service. Installing Exchange 2007 Using the Setup Wizard ˛ Because of the heavily improved and role-based Setup Wizard, installing Exchange 2007 is much easier than was the case with previous versions of Exchange. Because the Exchange 2007 Setup Wizard is role based, you can either select to install a typical Exchange Server installation, which will install the Hub Transport, Client Access, and Mailbox Server roles on the same server (which is what you typically want to do in an Exchange organization that will consist of one Exchange 2007 Server only), or you can do a custom Exchange Server installation, which lets you choose the server roles that should be installed on the respective server. You would typically choose to do a custom Exchange Server installation in a large Exchange organization where you want to separate the various Exchange 2007 Server roles among different servers. ˛ A benefi t of a role-based approach is that Exchange 2007 Setup installs only the Exchange fi les and services necessarily for the server role you deploy. This means that the respective server won’t waste disk space and resources on unnecessary fi les and services the way previous versions of Exchange did. ˛ A typical Exchange Server 2007 installation will install the Hub Transport, Client Access, and Mailbox server roles and the Management Tools (more specifi cally, the Exchange Management Console, the Exchange Management Shell, the Exchange Help fi le, and the Exchange Best Practices Analyzer tool) on a server. Installing Exchange 2007 Using Unattended Setup ˛ Setup.com supports many different parameters and switches that will let you install Exchange Server 2007 using unattended setup. To whet your appetite, we recommend that you type Setup.exe /? to list all available parameters and switches, providing a short description of each. 74 Chapter 2 • Installing Exchange Server 2007 Verifying the Installation of Exchange Server 2007 ˛ After Exchange Server 2007 has been installed, we recommend that you verify that the installation completed without any serious warnings or errors. If you didn’t encounter any problems during installation of Exchange Server 2007, there’s a good chance everything is fi ne, but you won’t know for sure until you have checked the Windows Event logs and the Exchange 2007 setup logs as well as do a visual verifi cation that each selected role has been installed. ˛ If the installation of Exchange 2007 completes the installation of one or more server roles but then fails at another one, you don’t need to reinstall the server roles that were already installed. Instead, the Exchange 2007 Setup Wizard will start in maintenance mode the next time you launch it, and from there you can simply tick the server roles that failed the fi rst time. Licensing an Exchange 2007 Server ˛ Unlike Exchange Server 2000 and 2003, you have to license Exchange Server 2007. By default, Exchange Server 2007 has a built-in time bomb (120 days), as you will notice the fi rst time you launch the Exchange Management Console. ˛ You will not be able to license a 32-bit version of Exchange Server 2007, since this version is meant for testing and other evaluation purposes. ˛ If you’re licensing an Exchange 2007 Enterprise Server with the Mailbox server role installed, you need to restart the Microsoft Exchange Information Store service for the change to be refl ected in the EMC. Finalizing Deployment of Exchange Server 2007 ˛ When you launch the Exchange Management Console for the fi rst time, the Microsoft Exchange node will be selected. Under this node you’ll fi nd two new tabs: Finalize Deployment and End-to-End Scenario. The Finalize Deployment tab provides a list of recommended tasks you should perform (depending on the server roles installed on the server) to fi nalize the deployment of your Exchange 2007 server. Installing Exchange Server 2007 • Chapter 2 75 ˛ The tasks listed on the Finalize Deployment tab are applied to features that are enabled by default and that need additional confi guration. We highly recommend you follow each task carefully so as not to overlook anything, but don’t rely 100 percent on this list, since these are just Microsoft’s attempt to show you the most basic confi guration settings. ˛ The End-to-End Scenario tab provides a list of tasks that are optional, but it’s a good idea to review and complete them anyway. Adding and Removing Exchange 2007 Server Roles ˛ All Exchange 2007 server roles can be installed on a single server (except the Edge Transport server role, which must be installed on its own hardware in the perimeter network). So, if you’re a small organization, you do not need to invest in more than one piece of hardware for your Exchange server. Bear in mind, however, that if you plan to cluster the mailbox server role, the mailbox server must run on its own hardware. ˛ You can add and remove Exchange server roles from an Exchange 2007 server as required using the Windows Control Panel’s Add or Remove Programs function or the ExSetup.exe CLI. Uninstalling Exchange Server 2007 ˛ There might be situations in which you want to completely remove an Exchange 2007 server from your Exchange organization. This can be done using either the Exchange 2007 Installation Wizard or Setup.com. ˛ Removing all server roles from an Exchange 2007 server will also remove any installation fi les as well as the Exchange server object and all its child objects from the Active Directory forest. 76 Chapter 2 • Installing Exchange Server 2007 Frequently Asked Questions Q: Which processors (CPUs) are supported by Exchange Server 2007? A: This depends on whether we’re speaking of the 32-bit version or the 64-bit version. The 32-bit version supports any Intel Pentium or compatible 800MHz or faster 32-bit processor. The 64-bit version supports Intel Extended Memory 64 Technology (Intel EM64T) and AMD 64-bit processor that supports AMD64 platform, but bear in mind that the Intel Itanium IA64 processor isn’t supported by the 64-bit version of Exchange 2007. Q: What are the memory requirements of the Exchange Server 2007 64-bit version? A: The minimum requirements are 2GB RAM, but it’s recommended that you install 2GB per server plus 5MB of RAM per mailbox. The more RAM, the better, since the 64-bit architecture allows Exchange 2007 to store much more data in the address space compared to previous versions of Exchange, which only existed in 32-bit versions. If we’re talking about an Exchange 2007 Mailbox Server with more than four storage groups, it’s recommended you install 2GB RAM per three storage groups (if you have between fi ve and eight storage groups, you should install 4GB; if you have between nine and 12, you should install 6GB, and so on). Q: Is it supported to use the 32-bit version of Exchange 2007 in a production environment? A: No! Only the 64-bit version should be used in a production environment. The 32-bit version is meant to be used for evaluation and testing purposes. There is one exception to the rule, though: The 32-bit version of the Exchange 2007 Management Tools (more specifi cally, the Exchange Management Console, the Exchange Management Shell, the Exchange Help fi le, and the Exchange Best Practices Analyzer tool) is supported for management tasks in a production environment. Q: Which operating systems does Exchange 2007 support? A: You must install Exchange 2007 on a server running Windows Server 2003 with SP1 or Windows Server 2003 R2. Both the Standard and Enterprise Editions of these operating systems are supported, but bear in mind that you need to install the Enterprise Edition if you plan to use clustering features such as Cluster Continuous Replication (CCR) or Single Copy Clusters (SCC). Q: I remember that Exchange 2000 and 2003 required the SMTP and NNTP Windows components to be installed before Exchange could be installed. Is this also the case with Exchange 2007? A: No, this has changed with Exchange 2007. Exchange 2007 requires that you install neither the SMTP nor NNTP Windows components. The reason is that Exchange 2007 now includes its own SMTP service, which has been built from the ground up using managed code. The NNTP feature has been dropped in Exchange 2007. . editions: a Standard Edition and an Enterprise Edition. ˛ Exchange 2003 and earlier versions offered only one type of Exchange CAL, but with Exchange 2007 we now have two types: a Standard CAL and an. Directory forest using both the GUI and the CLI. We touched on how to properly license an Exchange 2007 server and introduced the new Finalize Deployment and End-to-End Scenario task lists Server 2007 exists in 32-bit and 64-bit versions; however, the 32-bit version is not supported in a production environment and is meant to be used for evaluation and testing purposes only. If