Installing Exchange Server 2003 into an Exchange Server 5.5 Site

The basic process to install Exchange Server 2003 into an Exchange Server 5.5 site is really not much different than it is to install into a new Exchange Server 2003 organization or an existing Exchange 2000 Server organization. The biggest difference, as we ‚ ve already discussed at length in this chapter, is that you must synchronize Active Directory and the Exchange Directory Service. The Exchange Server Deployment Tools recommends the following steps for deploying the first Exchange Server 2003 in an Exchange Server 5.5 site:

Install the operating system on the future Exchange Server 2003 computer.
Ensure that the NNTP, SMTP, WWW, and ASP.NET services are running on the computer.
Run the DSScopeScan tool to help determine the scope of your deployment.
Install the Windows Support Tools on the new server, dependent on the version of Windows that was installed.
Run the DCDiag tool to check network connectivity and DNS.
Run the NetDiag tool to check network connectivity.
Review the logs created by the DSScopeScan, DCDiag, and NetDiag tools.
Run ForestPrep and DomainPrep to prepare the forest and domain for the installation of Exchange Server 2003.
Run the OrgPrepCheck tool to verify that the schema was properly extended.
Review the logs again for errors.
Install the Active Directory Connector (refer back to Exercise 11.1).
Use the ADC Tools to analyze the Exchange 5.5 site and then create the desired connection agreements (refer back to Exercise 11.2).
Run the SetupPrep tool to check one last time that the installation of Exchange Server 2003 will occur correctly.
Review the logs again for errors.
Install the first Exchange Server 2003 computer into the Exchange 5.5 site (discussed later in Exercise 11.3).
Change the connection agreements to the new server running Exchange Server 2003 to prevent replication problems and GAL viewing problems.

Validate the installation using the ADCConfigCheck, ConfigDSInteg, RecipientDSInteg, and PrivFoldCheck tools.

Note ‚

If your Exchange Server 5.5 servers are running on a Windows 2000 Server domain controller, don ‚ t forget to use the correct LDAP port when running the deployment tools.

Note ‚

The best way to go about this process is to have at least one Windows Server 2003 domain controller and global catalog server already in your organization. Recall that Exchange Server 5.5 will not run on Windows Server 2003, so you ‚ ll likely be faced with an existing Windows 2000 Server Active Directory forest that will need upgrading with the ADPrep tool. You should also have Windows Server 2003 member servers installed and joined to the domain for the Exchange Server 2003 installation. While you can install Exchange Server 2003 on a domain controller, it ‚ s not going to give you the best in performance from either Active Directory or Exchange. There are not any set rules for how to configure your organization, but you will at a minimum want to install one Windows Server 2003 domain controller and global catalog server as discussed above. See Microsoft Knowledge Base Article 309628 at http://support.microsoft.com/default.aspx?scid=kb;en-us;309628 for information on using ADPrep.

Installing Exchange Server 2003

It ‚ s a long path to take to finally get to the point of being able to install Exchange Server 2003 into your Exchange 5.5 site, but you ‚ ve made it ‚ the end is now in sight. The installation process is similar in some ways but distinctly different in others because you will be joining an existing Exchange 5.5 site. Exercise 11.3 outlines the process to install the first Exchange Server 2003 computer into an Exchange 5.5 site.

EXERCISE 11.3: Installing Exchange Server 2003

Start the Exchange Server 2003 Setup routine by double-clicking setup.exe in the
```
 SETUP\I386 directory of your CD or by letting it auto-play. 
```
On the Welcome to Exchange Server 2003 Setup page that opens, click the Exchange Deployment Tools link.
Click the Deploy The First Exchange Server 2003 link.
Click the Coexistence With Exchange 5.5 link.
The Microsoft Exchange Installation Wizard appears. Click Next to dismiss its opening page and continue.
Accept the License Agreement and click Next to continue.
Enter your Product Key and click Next to continue.
Select the components you want installed from the Component Selection page, and click Next to continue.
On the Installation Type page, select Join Or Upgrade An Existing Exchange 5.5 Organization, and click Next to continue.
On the Select a Server in an Exchange 5.5 Organization page, enter the name of one server in the Exchange 5.5 organization you want to join, and click Next to continue.
If prompted that Setup must verify prerequisite conditions, click OK.
You will be required to acknowledge the server licensing mode under which Exchange operates. Be sure to acquire enough CALs for your clients . Click Next to continue.
On the Service Account page, you will need to enter the credentials for the Exchange 5.5 service account. Click Next to continue.
You will have the chance to review your installation options on the Installation Summary page. Click Next to continue.
The installation will begin and will likely take some time to complete. Click Finish to close the Microsoft Exchange Installation Wizard.

Note ‚

For best results you should have one or more Windows Server 2003 global catalog servers in your forest. If you do not, you will likely be unable to change the connection agreements to point toward the Exchange Server 2003 computer on the Windows end. For more information on creating Windows Server 2003 global catalogs, see MS Knowledge Base article 816105 at http://support.microsoft.com/default.aspx?scid=kb;en-us;816105 .

As discussed previously, the next step you will need to perform is to retarget your connection agreements (created previously by ADC Tools) so that the Windows server is configured as the new Exchange Server 2003 server. Figure 11.2 shows the change being made to one of the connection agreements, and Figure 11.3 shows what you should see after you ‚ ve changed them both. It ‚ s important to note that the inability to locate a Windows Server 2003 global catalog at this point will likely prevent you from making this critical change.

Figure 11.2: Changing the target on the connection agreement

Figure 11.3: Viewing the changes

Creating Connection Agreements

If you ‚ ve followed along with the exercises up to now, you really don ‚ t need to create any connection agreements manually. However, situations can change and you may later want to create a connection agreement for some reason. Should this be the case, it ‚ s helpful to understand the various properties pages that make up a connection agreement as well as the basic process to go about creating one.

Whether you are creating a recipient or public folder connection agreement, the creation process is basically the same. Exercise 11.4 outlines the steps for creating a recipient connection agreement.

Configuring Connection Agreement Properties

Whether you are creating a recipient or public folder connection agreement, the property pages you use to configure the agreements are identical. The property pages for a configuration connection agreement are also identical, except that two of the property pages, Deletion and Advanced, are not present. The following sections detail all of the available property pages for a CA.

General Properties

The General page, shown in Figure 11.4, is used to name the CA, to specify whether the CA is two-way or one-way, and to designate a server to run the CA.

Figure 11.4: General properties of a CA

EXERCISE 11.4: Creating a Recipient Connection Agreement

Click Start > Programs > Microsoft Exchange > Active Directory Connector.
Right-click the Active Directory Connector ( computername ) object and select New > Recipient Connection Agreement. This opens the property pages for the new connection agreement, which are discussed in detail in the next section.
Enter a name for the connection agreement on the General page. Try to make the name one that suggests the use of the CA.
Enter the name of the Exchange 5. x server to which you want to connect on the Connections page.
All of the other properties throughout the property pages are optional. When you have finished configuring the connection agreement, click OK.

Connections Properties

The Connections page, shown in Figure 11.5, is used to enter connection information for the bridgehead servers of the connection: the Windows server (the Active Directory server) and the Exchange server (the server running Exchange 5. x ). The Windows server must be running at least Windows 2000 with Windows Service Pack 3 (the minimum requirements to install Exchange Server 2003) and Active Directory. The Exchange server must be running Exchange Server 5.5 with at least Service Pack 3 applied, even though the rest of the servers in the site do not need to run this recent a version of Exchange.

Figure 11.5: Connections properties of a CA

You use the Connections page to specify the authentication method to use for each end of the connection agreement. For more information on authentication methods , see Chapter 15. Also, you use the Connections page to enter the authentication credentials for each server. The account you enter allows each server to connect to the directories on the other end of the connection. The permissions account defined for each server requires only write permissions for its directory.

Finally, you use the Connections page to specify the LDAP port number used by the Exchange 5. x server. Unless Exchange 5. x is running on a Windows 2000 domain controller, this option is not important. However, Active Directory locks port 389 for its own use and renders the Exchange 5. x server unable to accept LDAP connections. A common alternative port number is 390.

Schedule Properties

The Schedule page, shown in Figure 11.6, is like all the other Schedule property pages you ‚ ve seen in this book and throughout Windows Server 2003. It allows you to specify the times during which replication can take place.

Figure 11.6: Schedule properties of a CA

From Exchange Properties

The From Exchange page, shown in Figure 11.7, lets you specify the location of the Exchange Directory container or containers that will be replicated, the location in Active Directory to which they will be replicated, and the specific objects that will be replicated. For public folder connection agreements, these options are already set, and you can ‚ t change them. For recipient connection agreements, you can fine-tune the options to meet your needs. For example, you might want to configure one connection agreement to replicate all of the mailboxes from a specific recipients container throughout the day and another agreement to replicate all other types of objects only at night.

Figure 11.7: From Exchange properties of a CA You can also start an unscheduled replication at any time by right-clicking a connection agreement and choosing the Replicate Now command from the All Tasks submenu.

From Windows Properties

The From Windows page, shown in Figure 11.8, is basically the opposite of the From Exchange page. It lets you configure the organizational units in Active Directory that should be replicated, the destination container they should be replicated to on the Exchange 5. x end, and the types of objects to replicate.

Figure 11.8: From Windows properties of a CA

Deletion Properties

By default, objects deleted in one directory are not deleted in the other directory. Instead, a record of the deletion is stored in a file on the server running ADC in the MSADC\MSADC\< connection agreement name > folder. The Deletion page, shown in Figure 11.9, lets you change this behavior. For each direction of replication, you can choose whether objects deleted in the source directory are deleted in the target directory or not. Note that in a one-way connection agreement, one section of this page will be unavailable, as in Figure 11.9.

Figure 11.9: Deletion properties of a CA

Advanced Properties

The Advanced page, shown in Figure 11.10, lets you configure a number of properties. These include the following:

The Paged Results section lets you specify the number of entries that are paged together to be replicated as a single action. Paging helps improve replication performance, because a separate replication message does not have to be generated for each entry.
A primary connection agreement is able to create new entries in the target directory. A CA that is not a primary agreement can replicate properties only to existing objects in the target directory. There are two primary agreement options on this page, one for each direction of the agreement.
Use the This Is An Inter-Organizational Connection Agreement option if you are replicating information between two different Exchange organizations. Note that this option is not available for public folder connection agreements.
Use the final setting on the page to specify the direction in which replication should occur first if you are configuring a two-way connection agreement.

Figure 11.10: Advanced properties of a CA

The When Replicating A Mailbox Whose Primary Windows Account Does Not Exist In The Domain menu lets you specify what should happen when a mailbox being replicated does not have a primary Windows account in the domain. This setting applies only to primary CAs, because many of the options call for creating new accounts in the target directory.