Graphical Installation - Exchange Server 2007

The Exchange 2007 graphical user interface (GUI) setup is one of the best that Microsoft has produced. Rather than start off with an End User Licensing Agreement (EULA) and jump right into the installation, the graphical wizard’s main page is broken into three sections:

Plan An external link to the Exchange Server 2007 website on Technet

Install Information on and downloads for the prerequisites necessary to install Exchange 2007, the Exchange installation files, and a link to Microsoft Update

Enhance Exchange 2007 add-ons like hosted services and Microsoft Forefront Security for Exchange Server

If you are missing any of the software prerequisites, the Exchange install wizard will walk you through them prior to installation. Note in Figure 4.1 that the first three prerequisites are grayed out because they are already met.

Figure 4.1

Exchange 2007 installation steps

You cannot install Exchange (Step 4) until all the following steps are chronologically met:

Step 1: Install .NET Framework 2.0 As mentioned in Chapter 1, you must install the World Wide Web Service component prior to installing .NET 2.0 so the Microsoft .NET Framework

BEGINNING THE SETUP PROCESS 115

and IIS extensions are installed correctly. Remember, if you’re trying to keep your IIS installation to a minimum, you will only need to check the single IIS component shown in the following screen shot:

Tip

IIS is only required for the Client Access and Mailbox roles.

Step 2: Install Microsoft Management Console (MMC) 3.0 The MMC version 3.0 was included in Windows Server 2003 R2; if you are running the original release of Windows Server 2003, you may need to obtain the latest MMC from Microsoft’s website (be sure to get the x64 version if you’re using a 64 bit operating system).

Step 3: Install Microsoft Windows PowerShell Windows Server 2003 R2 with Service Pack 2 doesn’t come with Windows PowerShell; you will have to download it from Microsoft’s website. As this book went to press, the most current PowerShell version was 1.0; do not install subsequent versions of the PowerShell unless they are specifically approved to work with Exchange 2007 because they could render your Exchange server unmanageable.

Step 4: Install required hotfixes Even Windows Server 2003 with Service Pack 2 has a few hotfixes that are required to run Exchange Server 2007 SP1. Ensure that you have installed

KB 931836 (http://go.microsoft.com/fwlink/?LinkID=92858) and a .NET Framework 2.0

fix found athttp://go.microsoft.com/fwlink/?LinkID=74465prior to starting to install

Exchange 2007. Otherwise the setup program will warn you that these are required and must be installed. If you do not install the .NET Framework 2.0 SP1 update, then I also recommend you install the hotfix documented in KB 942027.

116 CHAPTER 4 INSTALLING EXCHANGE SERVER 2007

Preparing Windows Server 2008

If you are starting your Exchange Server 2007 deployment on Windows Server 2008, you don’t have to worry about getting a lot of the updates and service packs installed. You can use any edition of Windows Server 2008 except Server Core. The base installation of Windows must have some additional components installed. You can install the additional components you require in Control

Panel, but the easiest way to install these components is to use theServerManagerCmdcommand-

line utility. The following is a list of components that must be installed and the command necessary to install them.

◆ Install the Active Directory management tools.

ServerManagerCMD -i RSAT-ADDS

◆ Install the Windows PowerShell (included with Windows Server 2008).

ServerManagerCmd -i PowerShell

◆ Install the IIS components required (Client Access).

ServerManagerCmd -I Web-Server ServerManagerCmd -I Web-ISAPI-Ext ServerManagerCmd -I Web-Metabase ServerManagerCmd -I Web-Lgcy-Mgmt-Console ServerManagerCmd -I Web-Basic-Auth ServerManagerCmd -I Web-Digest-Auth ServerManagerCmd -I Web-Windows-Auth ServerManagerCmd -I Web-Dyn-Compression

◆ Install the IIS components required (Client Access if Outlook Anywhere is required).

ServerManagerCmd -I RPC-over-HTTP-Proxy

◆ Install the IIS components required (Mailbox servers).

◆ Install Windows failover clustering (Mailbox servers supporting SCC or CCR).

BEGINNING THE SETUP PROCESS 117

◆ Install Active Directory Lightweight Directory Services, aka AD LDS or ADAM (only required on

Edge Transport).

ServerManagerCmd -I ADLDS

◆ Install the Windows Media audio/video codecs (Uniﬁed Messaging servers only).

ServerManagerCmd -I Desktop-Experience

Once you have prepped your Windows Server 2008 server, you must use the Exchange Server 2007 Service Pack 1 binaries to install the software. You cannot install the Exchange Server 2007 RTM version on Windows Server 2008.

Once the core software prerequisites are met, you can move on to the next step, which is installation. As you’re clicking past the Next buttons you will pass an introduction to Exchange 2007, the end user licensing agreement, and an invitation to send any errors automatically to Microsoft, but you will notice there’s no screen on which to enter a license code. That’s because you don’t need a license key to install Exchange or to run it for the first 120 days. After 120 days, you will automatically be reminded each time you open the Exchange Management Console with a ‘‘nag’’ dialog like the one in Figure 4.2 showing the remaining days before your evaluation period expires.

Figure 4.2

Licensing reminder dialog

Ultimately, you will have the choice of performing a typical or custom installation as shown in Figure 4.3. A typical installation installs the Mailbox, Hub Transport, and Client Access server roles as well as the Exchange administrative tools.

If your organization is relatively simple and requires only one server, the typical Exchange Server installation may suffice; however, I suggest choosing the custom installation so you understand what all of your options are. At this screen, you also have the option of defining an installation path for the Exchange program files.

118 CHAPTER 4 INSTALLING EXCHANGE SERVER 2007

Figure 4.3

Selecting the installation type

If you’re like most Exchange administrators and opt to always choose the custom installation, you will find yourself looking at the Server Role Selection screen (Figure 4.4). Here you can select which Exchange 2007 server roles you would like to install on this Exchange server. Remember, if you forget to install a role or decide to remove a role, you can always do so at a later time.

Note that the wizard will allow you to select only roles that are compatible with each other. For instance, if you select the Edge Transport server role, all other roles will be grayed out because the Edge Transport role must be installed on its own server. Also note that both the active and passive clustered mailbox roles prevent you from selecting any other roles (including the mailbox role) because they must be installed separately from all other Exchange services.

When launched, the Exchange installer searches Active Directory for existing Exchange architecture, resulting in one of the following three scenarios:

◆ _{If it finds that this is the first Exchange 2007 server in your Active Directory infrastructure,}

it will prompt you to supply an Exchange 2007 organization name.

◆ _{If it finds existing Exchange 2007 servers, it will automatically add the additional objects in}

the Active Directory to configure the new server you are creating.

◆ If it finds a legacy Exchange 2000 or 2003 organization, it will prompt you to select an

Exchange 2003 SMTP bridgehead to use for legacy connectivity. We will come back to this possibility in Chapter 5.

If you have selected to install the Mailbox role on this Exchange server, you will be asked whether or not you would like to enable a public folder database at the Client Settings screen. If you have Entourage for the Mac, Outlook 2003, or earlier Outlook clients deployed in your organization, you will need a public folder database to handle legacy functions like free/busy requests and offline address books.

BEGINNING THE SETUP PROCESS 119

Figure 4.4

The Server Role Selection screen

Outlook 2007 uses the Client Access role for these functions and does not require the use of public folders. In case you’re wondering, Microsoft has decided to leverage Microsoft Office SharePoint Server instead of Exchange public folders moving forward. However, this shift in pol- icy doesn’t preclude the use of public folders in Exchange 2007; they will continue to be supported for 10 years after Exchange 2007 is released.

The next screen will automatically run readiness checks for each role you have selected to install (Figure 4.5). If you are missing any prerequisites or need to reconfigure your server, the wizard will identify what needs to be corrected and even provide you with external links to eliminate unresolved dependencies. Once all prerequisites are confirmed, you can click the Install button.

If you have the proper permissions to modify your organization’s Active Directory schema and install Exchange on the server, the wizard will automatically install the necessary extensions into your schema. A major improvement over prior versions of Exchange is the ‘‘realistic’’ indicator showing your progress through the installation. Once installation has completed, you have the option to automatically launch the Exchange Management Console and perform post-installation tasks as shown in Figure 4.6.

At the end of the installation, the Exchange 2007 setup screen will give you the option of immediately checking for updates. I recommend that you do this as soon as possible on each server you install.

In document Exchange Server 2007 (Page 124-129)