Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2007-08-08

This topic explains how to use the Microsoft Exchange Server 2007 Setup wizard to perform a custom installation of Exchange 2007. Performing a custom installation provides added flexibility that is not possible with a typical installation. For example, with a custom installation, you can:

Note:
After you install any Exchange 2007 server roles on a computer, you cannot use the Exchange Server 2007 Setup wizard to add any additional server roles. If you want to add more server roles to a computer, you must use either the Control Panel in Windows Server or Setup.com from a Command Prompt window. For more information about how to modify an installation, see How to Modify an Exchange Installation.

Before You Begin

Before you perform the procedure in this topic, be aware of the following:

  • For e-mail messages to flow correctly, you must install both the Mailbox server role and the Hub Transport server role in each Active Directory directory service site.

  • For client access to work correctly, you must install a Client Access server in each Active Directory site that has a Mailbox server.

  • You can install the Mailbox server role, the Hub Transport server role, the Client Access server role, and the Unified Messaging server role on the same computer or on separate computers.

  • Confirm that your organization meets the requirements that are listed in Exchange 2007 System Requirements.

  • If you have any domain controllers that are running Windows 2000 Server and you are installing Exchange 2007 RTM, you must run Setup.com from a Command Prompt window, and you must use the /DomainController parameter to specify a domain controller that is running Windows Server 2003 SP1. For more information about how to run Setup.com from a Command Prompt window, see How to Install Exchange 2007 in Unattended Mode. If you are installing Exchange 2007 SP1, you do not have to specify a domain controller that is running Windows Server 2003 SP1.

  • To perform the following procedure, the account you use must be delegated membership in the Schema Administrators group if you have not previously prepared the Active Directory schema.

    If you are installing the first Exchange 2007 server in the organization, the account you use must have membership in the Enterprise Administrators group.

    If you have already prepared the schema and are not installing the first Exchange 2007 server in the organization, the account you use must be delegated the Exchange Organization Administrator role. 

    For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations. For more information about preparing Active Directory and domains, see How to Prepare Active Directory and Domains.

Note:
When you install Exchange 2007, Setup creates a mailbox for the Administrator user account. When Exchange 2007 creates a mailbox, if an alias is not specified, Exchange 2007 will, by default, use the user principal name (UPN) and convert all non-ASCII characters to the underscore character. In some languages that use non-standard character sets, the Administrator user account has, by default, a non-ASCII value for the UPN. In this case, after you install Exchange 2007, the Administrator account alias will be changed to all underscore characters. To avoid this, confirm that the Administrator account has an ASCII UPN before you install Exchange 2007.

Procedure

To use the Exchange Server 2007 Setup wizard to perform a custom installation of Exchange 2007

  1. Log on to the server on which you want to install Exchange 2007.

  2. Insert the Exchange Server 2007 DVD into the DVD drive. If Setup.exe does not start automatically, navigate to the DVD drive and double-click Setup.exe.

  3. On the Start page, complete Steps 1 through 3.

    Note:
    If you already have Microsoft .NET Framework 2.0, Microsoft Management Console (MMC) 3.0, and Microsoft Windows PowerShell installed, these steps will be unavailable. If you have not installed Microsoft .NET Framework 2.0, Setup will link to .NET Framework Developer Center. If you have not installed Microsoft Management Console (MMC) 3.0, Setup will link to MMC 3.0 update is available for Windows Server 2003 and for Windows XP. If you have not installed Microsoft Windows PowerShell, Setup will link to Windows PowerShell 1.0 English Language Installation Packages for Windows Server 2003 Service Pack 1 and for Windows XP Service Pack 2.

  4. On the Start page, click Step 4: Install Microsoft Exchange. Setup copies the setup files locally to the computer on which you are installing Exchange 2007.

  5. In the Exchange Server 2007 Setup wizard, on the Introduction page, click Next.

  6. On the License Agreement page, select I Accept the terms in the license agreement, and then click Next.

  7. On the Error Reporting page, click Yes or No, and then click Next.

  8. On the Installation Type page, click Custom Exchange Server Installation. If you want to change the path for the Exchange 2007 installation, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next.


    Installation Type page of Setup Wizard
    Figure 1   Installation Type page

  9. On the Server Role Selection page, select the server roles that you want to install on the computer and click Next.

    Note:
    The Edge Transport server role cannot coexist on the same computer with any other server role.
    Note:
    You must deploy the Edge Transport server role in the perimeter network and outside the Active Directory forest.
    Note:
    If you select Management Tools, you will install the Exchange Management Console, the Exchange cmdlets for the Exchange Management Shell, and the Exchange Help file. The management tools will be installed automatically if you install any other server role.

    Server Role Selection Page of Setup Wizard
    Figure 2   Server Role Selection page

  10. If you selected Hub Transport Role, and if you are installing Exchange 2007 in a forest that has an existing Exchange Server 2003 or Exchange 2000 Server organization, on the Mail Flow Settings page, select a bridgehead server in the existing organization that is a member of the Exchange 2003 or Exchange 2000 routing group to which you want to create a routing group connector.

    Note:
    The Exchange 2007 routing topology is based on Active Directory sites and does not use routing groups. However, to enable mail flow between Exchange 2007 and Exchange 2003 or Exchange 2000, a routing group connector is required between the Exchange 2007 routing group and the routing group in the Exchange 2003 or Exchange 2000 organization.

  11. 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 2007 organization.

    The Exchange organization name can contain only the following characters:

    • A through Z

    • a through z

    • 0 through 9

    • Space (not leading or trailing)

    • Hyphen or dash

    The organization name cannot contain more than 64 characters. The organization name cannot be blank. If the organization name contains spaces, you must enclose it in quotation marks.

  12. If you selected Mailbox Role, and if this is the first Exchange 2007 server in your organization, on the Client Settings page, click the option that describes the client computers in your organization that are running Microsoft Outlook.

    Note:
    If you do have client computers that are running Outlook 2003 or earlier, and you select Yes, Exchange 2007 will create a public folder database on the Mailbox server. If all of your client computers are running Office Outlook 2007, public folders are optional in Exchange 2007. If you select No, Exchange 2007 will not create a public folder database on the Mailbox server. You can add a public folder database later. For example, if you add client computers that are running Outlook 2003, and you need a public folder database, you can create one on the Exchange 2007 Mailbox server. You must then configure the offline address book for public folder distribution, and then restart the Microsoft Exchange Information Store service before client computers that are running Outlook 2003 and earlier will be able to connect to the server.

  13. On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If they have completed successfully, click Install to install Exchange 2007.

  14. On the Completion page, click Finish.

Important:
After you install the first Exchange 2007 server in an organization, if you create a new recipient object (such as a mailbox, contact, distribution list, mailbox agent, or mail-enabled public folder), it will have a LegacyExchangeDN that corresponds to the new administrative group for the Exchange 2007 server. Because of this LegacyExchangeDN, Outlook will request a full offline address book (OAB) download from the Exchange 2007 server for each user in this organization that logs on to a mailbox using Outlook and using OAB versions 2 or 3. This could cause many simultaneous OAB download requests, which causes high network utilization.
Note:
After you install Exchange 2007, you should verify the installation. For more information, see Verifying an Exchange 2007 Installation.
Important:
After installing the Unified Messaging server role, you must restart the system to allow the Microsoft Exchange Unified Messaging service to reserve the TCP ports that are required.

For More Information