Running and Modifying Exchanger Server 2007 Setup

Exchange Server 2007 Setup is the program you use to perform installation tasks for Exchange Server 2007. You use Exchange Server 2007 Setup to install Exchange Server roles and the Exchange management tools. When you want to manage the Exchange server configuration, you use Add Or Remove Programs in Control Panel. Tasks you can perform with these utilities include:

• Installing Exchange Server roles and management tools

• Adding server roles or management tools

• Maintaining existing components

• Uninstalling Exchange Server

Installing New Exchange Servers

You can install multiple Exchange Server roles on a single computer. For servers deployed within the organization, you can deploy any combination of the Mailbox, Client Access, Hub Transport, and Unified Messaging roles on a single computer. You cannot combine the Edge Transport role with other roles, however, as this is an optional role for the organization's perimeter network and you must install it separately from other roles.

In clustered environments, you use one of the modified cluster Mailbox Server roles rather than the standard Mailbox Server role. For clustered servers, you must use either the active clustered Mailbox role or the passive clustered Mailbox role, depending on whether you are configuring an active node or a passive node in the cluster as a Mailbox server. You cannot install a clustered Mailbox server on a server with any other roles.

Tip 

To reduce network traffic between Exchange servers, domain controllers, and global catalog servers, you'll typically want to deploy the Mailbox, Client Access, Hub Transport and Unified Messaging roles on a computer acting as a domain controller with a global catalog. This is not a requirement, but it is a recommended best practice for most Exchange Server implementations. Edge Transport servers are not members of the Active Directory forest and are not configured as domain controllers or as global catalog servers.

Often, small and medium organizations can deploy a single Exchange server per Active Directory site that hosts the Mailbox, Client Access, Hub Transport, and Unified messaging roles and may not need to have an Edge Transport server in a perimeter zone. As the size and needs of the organization increase, however, it becomes more and more beneficial to host some roles on separate servers. Keep the following in mind:

• You can achieve increased efficiency for message routing and delivery by combining the Mailbox and Hub Transport roles on a single server.

• You can achieve increased security by isolating the Client Access role and deploying it on a server other than one that also hosts the Mailbox and Hub Transport roles.

• You can improve responsiveness for dial-in and voice access by isolating the Unified Messaging role and deploying it on a server other than one that also hosts the Mailbox and Hub Transport roles.

When you use multiple Exchange servers, you should deploy the roles in the following order:

1. Client Access server

2. Hub Transport server

3. Mailbox server

4. Unified Messaging server

For client access to work correctly, install at least one Client Access server in each Active Directory site that has a Mailbox server. For Hub Transport, Mailbox, and Unified Messaging servers, install at least one of each server role for each group of Active Directory sites that are well connected on a common LAN. For example, if the organization consists of Sites A and B, which are well connected on a common LAN, and Sites C and D, which are well connected on a common LAN, with wide area network (WAN) links connecting Sites A and B to Sites C and D, a minimal recommended implementation would be to have Hub Transport, Mailbox, and Unified Messaging servers only in Site A and Site C.

Because you install Edge Transport servers outside the Active Directory forest, you can deploy them at any time. By configuring multiple Edge Transport servers, you can ensure that if one server fails, Edge Transport services continue. If you also configure your Edge Transport servers with round-robin DNS, you can load-balance between them.

Installing Exchange Server

The Exchange Server 2007 installation process has changed considerably since Exchange Server 2003. The installation process now requires. NET Framework version 2.0 or later, Microsoft Management Console version 3.0 or later, and Microsoft Command Shell version 1.0 or later. In Setup, links are provided so that you can download and install the most recent versions of these applications. The installation process also requires Windows Installer 3.0 or later, which is included in Windows Server 2003 Release 2, Windows Server 2003 Service Pack 1, and later releases of Windows Server. Some Exchange server roles also require IIS components, as discussed previously.

Using Windows Installer helps to streamline and stabilize the installation process and it makes modification of install components easier. You can:

• Install additional roles or components by rerunning the Installation Wizard.

• Maintain installed components using Add Or Remove Programs in Control Panel.

• Resume a failed installation or modification using Add Or Remove Programs in Control Panel.

For administration purposes, you can install the Exchange management tools on a workstation computer running Windows XP Service Pack 2 or later. This workstation must also have the Microsoft Command Shell installed.

To install Exchange Server roles on a server, complete the following steps:

1. Log on to the server using an administrator account. When installing the Mailbox, Hub Transport, Client Access, and Unified Messaging roles, you must use a domain account that is a member of the Enterprise Administrators group. If you've already prepared Active Directory, this account must also be a member of the Exchange Organization Administrators group.

2. Insert the Exchange Server 2007 DVD into the DVD-ROM drive. If Autorun is enabled, Exchange Server 2007 Setup should start automatically. Otherwise, double-click Setup.exe on the root folder of the DVD.

3. On the Start page, click the links for steps 1, 2, and 3, each in turn. This helps you download and install. NET Framework version 2.0 or later, Microsoft Management Console version 3.0 or later, and Microsoft Command Shell version 1.0 or later.

4. On the Start page, click Step 4: Install Microsoft Exchange. In the Exchange Server 2007 Installation Wizard, read the introductory text, and then click Next.

5. On the License Agreement page, select I Accept The Terms In The License Agreement, and then click Next.

6. On the Error Reporting page, choose Yes if you'd like to send error repors automatically to Microsoft or No if you would like to turn off automatic error reporting. Click Next.

7. On the Installation Type page, click Custom Exchange Server Installation and then click Next.

8. On the Server Role Selection Page, select the server roles that you want to install on the computer. Select Management Tools to install the Exchange management tools. The default installation location for Exchange Server and all its components is %SystemDrive%∖Program Files∖Microsoft∖Exchange Server. If you want to change the path for the Exchange Server 2007 installation, click Browse, locate the relevant folder in the folder tree, and then click OK. Click Next.

9. If you selected Mailbox Role, Client Access Role, Hub Transport Role, or Unified Messaging Role, and if this is the first Exchange 2007 server in your organization, on the Exchange Organization page, type a name for your Exchange organization or accept the default value of First-Organization. Click Next.

10. If you selected Mailbox Role, and if this is the first Exchange 2007 server in your organization, you'll next see the Client Settings page. If you have client computers that are running Outlook 2003 or earlier, select the Yes option so that Exchange will create a public folder database on the mailbox server. If all of your client computers are running Outlook 2007, public folders are optional, as the OAB and free/busy information are maintained separately. If you select the No option, Exchange will not create a public folder database on the mailbox server. You can add a public folder database later if desired. Click Next.

11. On the Readiness Checks page, Setup then checks to see whether Exchange is ready to be installed with the roles you selected. Review the status to determine if the organization and server role prerequisite checks completed successfully. You must complete any required prerequisites before continuing. Once checks are completed successfully, click Install to install Exchange Server 2007.

12. On the Completion page, click Finish. When the installation completes, you should verify the installation by doing the following on the server:

    • q Start the Exchange Management Shell, and type get-ExchangeServer to display a list of all Exchange roles installed on that server.

    • q Review the application logs for events from Exchange Setup. These events have event IDs 1003 and 1004, with the source as MSExchangeSetup.

    • q Review the Exchange Setup logs in the %SystemRoot%∖ExchangeSetupLogs folder. As these logs contain standard text, you can perform a search using the keyword "error" to find any setup errors that occurred.

Real World With a new Exchange Server 2007 implementation, each new recipient object (such as a mailbox, contact, distribution list, mailbox-agent, or mail-enabled public folder) will have a special attribute called legacyDN that corresponds to the new administrative group for the Exchange Server 2007 server. Because of this legacyDN, Microsoft Outlook will request a full OAB download from the Exchange Server 2007 server for each user in this organization that logs on. In a large organization, this could mean there will be multiple simultaneous OAB downloads, which, in turn, could cause high network utilization.

To complete the installation for an initial deployment of Exchange into an organization, you'll need to perform the following tasks:

• For Client Access servers:

  • q If you plan to use ActiveSync for mobile messaging clients, as discussed in Chapter 4, configure direct push, authentication, and mobile devices.

  • q Configure the Outlook Web Access URL, authentication, and display options.

  • q Enable the server for POP3 and IMAP4, as appropriate.

• For Edge Transport servers:

  • q Export the Edge Transport server subscription file, and import it on Hub Transport servers, as discussed in Chapter 15, "Managing Hub Transport and Edge Transport Servers."

  • q If you are using Edge Transport servers with Exchange 2000 Server or Exchange Server 2003 organizations, you must manually configure the necessary connectors, as discussed previously.

  • q Configure a postmaster mailbox for each mail domain.

  • q Configure DNS MX resource records for each accepted domain.

  • q Configure antispam, junk e-mail, and safe sender features, as appropriate.

• For Hub Transport servers:

  • q Configure domains for which you will accept e-mail. You will need an accepted domain entry for each SMTP domain for which you will accept e-mail, as discussed in Chapter 15, "Managing Hub Transport and Edge Transport Servers."

  • q If you also deployed the Edge Transport Server role, you will need to subscribe to the Edge Transport server so that the EdgeSync service can establish one-way replication of recipient and configuration information from Active Directory to the Active Directory ADAM store on the Edge Transport server. See Chapter 15 for details.

  • q Create a postmaster mailbox so that you can receive mail addresses to the postmaster address, as discussed in Chapter 15.

  • q Configure DNS MX resource records for each accepted domain.

• For Mailbox servers:

  • q Configure OAB distribution for Outlook 2007 clients, as discussed in Chapter 9, "Working with Distribution Groups and Address Lists."

  • q Configure OAB distribution for Outlook 2003 or earlier clients, as discussed in Chapter 9.

  • q Configure storage groups and databases, as discussed in Chapter 11, "Managing Microsoft Exchange Data and Storage Groups."

• For Unified Messaging servers:

  • q Configure a unified messaging dial plan, and add the server to it.

  • q Configure Unified Messaging hunt groups.

  • q Enable users for unified messaging, as appropriate.

  • q Configure your IP/VoIP gateways or IP-PBXs to work with Exchange server.

  • q Configure a Unified Messaging IP gateway in Exchange server.

  • q As desired, create auto-attendant and mailbox policies and configure additional dial plans, gateways, and hunt groups.

Adding, Modifying, or Uninstalling Server Roles

After you install an Exchange server with its initial role or roles, you can add new roles or remove existing roles using Add Or Remove Programs. In Control Panel, double-click Add Or Remove Programs. In Add Or Remove Programs, click the Microsoft Exchange Server 2007 entry to display the Change and Remove buttons.

To add roles or the management tools to an installation, click Change to start the Exchange Server 2007 Setup in update maintenance mode. You will then be able to use Setup to add roles to the server or to install the management tools, if they weren't previously installed. Simply select the check boxes for the roles you want to add, click Next, and then follow the prompts.

To remove roles from an installation, click Remove to start the Exchange Server 2007 Setup in modify maintenance mode. You will then be able to use Setup to remove roles from the server. Simply clear the check boxes for the roles you want to remove, click Next, and then follow the prompts.

Before you can remove the Mailbox role from a server, you must move or delete all mail-boxes hosted in mailbox databases on the server and all offline address books hosted in public folder databases on the server. If the public folder database is the last one in the Exchange organization, such as may be the case if you are uninstalling Exchange on a test or development server, you will need to use Exchange Management Shell to delete the public folder database once you've emptied it.

To remove the last public folder database in the Exchange organization, type the following command at the Exchange Management Shell prompt:

 get-publicfolderdatabase | remove-publicfolderdatabase  -oktoremovelastpublicfolderdatabase 

You'll see the following warning prompt:

 Confirm Are you sure you want to perform this action? Removing Public Folder Database "CORPSVR127\Second Storage Group\Public Folder Database". [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): 

Carefully read the details regarding which public folder database you are removing. Press Y to proceed. You'll then see the following additional warning prompt:

Confirm You are attempting to remove the last public folder database in the organization. If you remove this database, all its contents will be lost and only users running Outlook 2007 or later will be able to connect to your Exchange organization. Are you sure that you want to delete the last public folder database? [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):

Carefully read the details regarding which public folder database you are removing. Press Y to proceed. You'll then see the following additional warning prompt:

Warning 

The specified database has been removed. You must remove the database file located in C:∖Program Files∖Microsoft∖Exchange Server∖Mailbox∖Second Storage Group∖Public Folder Database.edb from your computer manually if it exists.