Installing the First Exchange Server 2003 System in an Exchange 5.5 Site

 < Day Day Up > 

Because there are many prerequisite tasks and processes to run, getting to the point of the actual Exchange Server setup is a watershed event. The following section double-checks that the prerequisites have been fulfilled. When installing the first Exchange Server 2003 system, it is recommended that you use a server that has been wiped clean and has a fresh installation of Windows Server 2003. This is because the first server in Exchange holds many critical Exchange organizational management and routing master tables, and having a new, clean server ensures that the masters are created and stored on a solidly configured system.

Installing the First Exchange Server 2003 System

The actual Exchange Server 2003 installation of the first server is quite easy after the prerequisite conditions are met. The installation takes about 30 minutes on average.

One final step before running the Exchange Server 2003 setup is to run a tool called SetupPrep, as illustrated in Figure 15.6. This tool validates that all necessary prerequisites are in place for the installation of the first Exchange Server 2003 in the site.

Figure 15.6. Running SetupPrep.

graphics/15fig06.jpg

After SetupPrep has been run, the actual setup of the server can be invoked via the tools or simply by running the Setup.exe in the \setup\i386 folder. The following steps properly install Exchange Server 2003 on the system on which they are run:

  1. Click Next at the Welcome Wizard.

  2. Agree to the end- user licensing agreement and click Next.

  3. Choose the installation path and ensure that Typical Installation is chosen . Click Next.

  4. Select Join or Upgrade an Existing Exchange 5.5 Organization, as illustrated in Figure 15.7, and click Next.

    Figure 15.7. Joining an Exchange 5.5 organization.

    graphics/15fig07.gif

    NOTE

    It is imperative that Join or Upgrade an Existing Exchange 5.5 Organization is chosen at this point. If Create a New Exchange Organization is chosen, connectivity will be lost to the Exchange 5.5 organization, and serious steps will be required to regain the functionality.

  5. Enter the name of an Exchange 5.5 server in a site the Exchange Server 2003 system will join.

  6. Click OK at the prompt to test prerequisite conditions.

  7. Select I Agree to agree to the license agreement.

  8. Enter the password of the Exchange 5.5 service account.

  9. Verify the installation options, and click Next to start the installation.

  10. When the installation is complete, click Finish.

To install additional Exchange Server 2003 systems, the installation process is almost identical, and the same procedure can be followed.

Understanding What Happens Behind the GUI During the Installation

Quite a few items are installed and configured during the installation. The following items describe some of the major components that are installed and configured during setup. The new terms and features are discussed more in depth in the next few sections.

  • Exchange Server 2003 binaries and services installed All the basic services for Exchange Server 2003 are installed and started. The SMTP and NNTP services from IIS are modified for Exchange Server 2003.

  • Changes to Active Directory Configuration container Information about the Exchange installation, such as Administrative and Routing Group configurations, are in the Services container.

  • Exchange Server added to Exchange Domain Servers security group The machine account for the server is added to the Exchange Domain Servers security group to let Exchange Server 2003 run under the local system account.

  • Configuration connection agreement created A new connection agreement is added to the ADC to replicate configuration and routing information between Exchange 5.5 and Exchange Server 2003.

  • Recipient Update Service created The RUS is created to update address lists and recipient policies in Active Directory.

  • Site Replication Service (SRS) installed The SRS is installed and synchronizes the directory with the Exchange 5.5 server in the site.

Configuration Connection Agreement

During the installation, a new connection agreement is added to the Active Directory Connector. The ConfigCA is responsible for replicating the configuration information between the Exchange platforms. The ConfigCA replicates items such as the Site Addressing Policies and the routing information in the Gateway Address Routing Table (GWART).

Site Replication Service

The Site Replication Service provides directory interoperability between the Exchange 5.5 and Exchange 2003 servers. The SRS runs as a service and is needed only during the migration period. SRS uses LDAP to communicate between directories, and to Exchange 5.5 servers it looks just like another Exchange 5.5 server. The SRS works in conjunction with the Active Directory Connector for directory synchronization.

Only one SRS is allowed per Exchange Server 2003 system. Additional SRSs can be added, as long as there are additional Exchange Server 2003 systems available to run the service. The SRS has no configuration parameters in the Exchange Server 2003 System Manager. Synchronization can be forced through the SRS by accessing the SRS from the Exchange 5.5 Administrator program.

SRSs are created on all servers that house Exchange 5.5 Directory Replication Connectors. The Directory Replication Connector is replaced by the SRS to perform intersite replication with the remote Exchange 5.5 site; if an Exchange Server 2003 is configured to communicate with an Exchange 5.5 server, the Site Replication Service automatically is installed and configured at the time of Exchange Server 2003 installation.

TIP

To view the Directory Replication Connector endpoints in the SRS, open Exchange System Manger and expand the Tools icon. Next click the Site Replication Services icon and then select Directory Replication Connector View from the View menu. Each Exchange 5.5 site's Directory Replication Connector is now displayed under the Site Replication Service.


No Service Account in Exchange Server 2003

Exchange Server 2003 runs under the Local System account. This is a major change from Exchange 5.5, where the Exchange Service account had access to every user's mailbox. The benefit of the new architecture is that the service account was a single point of failure in case of a password change or if the account was deleted. When Exchange Server 2003 systems communicate between servers, they are authenticated by the server's machine account in Active Directory.

When the /domainprep option is run, it creates two groups called Exchange Domain Servers and Exchange Enterprise Servers. During Exchange setup, the Exchange server's machine account is added to a Global Security group called Exchange Domain Servers. The Exchange Domain Servers group is granted permissions on all Exchange objects to allow the Exchange Server 2003 services to access and update Active Directory. The Exchange Enterprise Servers group contains the Exchange Domain Servers groups from all domains in the forest and provides cross-domain access between all Exchange Server 2003 systems.

Recipient Update Service

The Recipient Update Service is responsible for updating address lists and email addresses in Active Directory. Two objects are contained in the Recipient Update Services container by default. The Recipient Update Service is responsible for updating the Enterprise Configuration information in Active Directory, such as Administrative and Routing Group information. The domain specified is responsible for updating the address lists and email addresses configured on objects in the Active Directory domain that the Exchange server resides in. The address list and email addresses are configured under the Recipient Policies and Address List icon, discussed previously in this section.

 < Day Day Up > 


Microsoft Exchange Server 2003 Unleashed
Microsoft Exchange Server 2003 Unleashed (2nd Edition)
ISBN: 0672328070
EAN: 2147483647
Year: 2003
Pages: 393
Authors: Rand Morimoto

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net