Installing Exchange Server
This section explains several installation scenarios and component options and then walks you through an actual installation of the first server in an organization. So boot up your Windows Server 2003 computer, grab your Exchange Server 2003 CD, and get ready.
There are four basic contexts in which Exchange Server 2003 can be installed:
-
As the Exchange Server 2003 computer in an organization
-
As a subsequent Exchange Server 2003 installation
-
As an upgrade from Exchange 2000 Server to Exchange Server 2003
-
As a coexistence with or migration from Exchange Server 5.5 to Exchange Server 2003
In addition to these four contexts, this section also covers installing Exchange on a cluster.
| Note | We will examine the installation and management of Exchange Server 2003 computers for coexistence with and migration from Exchange Server 5.5 in Chapter 11. |
Installing the First Exchange Server
Installing the first Exchange Server 2003 in an organization is a fairly important task. If you have already run (or had someone else run) the ForestPrep and DomainPrep tools, then the Active Directory and Windows domains are all ready for the Exchange installation.
| Note | If you are a member of the Schema Admins, Enterprise Admins, and local Administrators groups, you can forgo running the ForestPrep tool; it is possible to update the schema during the setup of the initial Exchange Server. In addition, if you are installing into a single domain environment, you can forgo running the DomainPrep tool. Be warned, though: If you install Exchange without running the ForestPrep tool into a forest where no version of Exchange already exists, Setup creates an organization based on the name of the domain. |
When installing the first Exchange server, you will be prompted to enter information on the following topics:
Name of the directory for installation The default directory location and name are C:\Program Files\Exchsrvr, but this can be modified by the installer.
CD Key The Setup program will present you with a dialog box requesting the CD Key or Product ID (PID) number. The CD Key is a unique 25-digit number found on the back of the Exchange Server CD case.
Choosing Installation Components
You can initiate Exchange Server Setup by using either the graphical Welcome to Exchange Server 2003 Setup page that loads if auto-play is enabled or alternatively by executing the setup.exe command, which is located on the Exchange Server CD in the \Setup\I386\ directory.
| Note | You can perform the installation from a network share if desired. |
When Setup runs, it checks for a current installation of Exchange on that machine. If it finds one, it goes into maintenance mode and lets you add or remove components and reinstall or remove all components.
If Setup does not find a current installation, it prompts you for the specific components to install, as seen previously in the final screen shown in Exercise 3.2.
There are two main categories of components available under the main Microsoft Exchange entry:
-
Microsoft Exchange Messaging and Collaboration Services, which includes the basic Exchange routing engine and optional subcomponents for the various available messaging connectors
-
Microsoft Exchange System Management Tools, which includes the System Manager snap-in for managing Exchange and a single optional subcomponent—the Exchange 5.5 Administrator tool for managing Exchange 5.5 servers
In addition, there are three installation types that you can choose using the drop-down menu (under the Action heading) to the left of the Microsoft Exchange component at the top of the component list:
-
Typical, which installs the Messaging and Collaboration Services and the System Management Tools components but none of their subcomponents
-
Minimum, which installs only the Messaging and Collaboration Services component itself
-
Custom, which you can use to select individually only the components you want
Note When you install Exchange Server 2003 into a forest where no version of Exchange already exists, Setup creates a default routing group, named First Routing Group, and a default administrative group, named First Administrative Group. If you want to create groups with more imaginative (or useful) names, run the ForestPrep and DomainPrep tools as normal. Then, perform an installation of Exchange Server 2003, but select only the Microsoft Exchange System management Tools to be installed. Using this console, you can then create routing and administrative groups before you ever deploy your first actual Exchange server.
Performing an Installation
Exercise 3.4 provides the actual steps to install Microsoft Exchange Server 2003. This exercise assumes that you have already used both the ForestPrep and DomainPrep tools and that you are installing the first Exchange server in an organization.
| Note | Remember that Setup will run ForestPrep and DomainPrep for you if they have not already been performed and you have all of the required permissions on your user account. |
Please review the system requirements needed by your lab computer to perform these exercises. Those requirements are found in the introduction of this book in the section “How to Use This Book.”
-
Insert the Microsoft Exchange Server CD into the server’s CD-ROM drive. If your CD-ROM drive is set to automatically run CDs, this will automatically open the Welcome to Exchange Server 2003 Setup page as seen previously in Exercise 3.2. If not, browse to the location of your CD-ROM and double-click the setup.exe file.
-
Click the Exchange Deployment Tools link.
-
On the Welcome to the Exchange Server Deployment Tools page, click the Deploy The First Exchange 2003 Server link.
-
On the Deploy the First Exchange Server 2003 page, click the New Exchange 2003 Installation link.
-
Scroll down the Exchange Server Deployment Tools page until you locate item 8, Install Exchange Server 2003. Click the Run Setup Now link.
-
When prompted, agree to the EULA, and click Next to continue.
-
Enter your 25-digit CD key, and click Next to continue.
-
The Component Selection page lists the installation options, as well as the option to choose the directory into which Exchange Server will be installed. This latter option is accessed through the Change Path button. For this exercise, we will assume that the installation directory is the default, C:\Program Files\Exchsrvr. The installation option we will use for this exercise is the Typical option, which includes the messaging components and management tools. If you would like to see the individual components that can be selected, choose the Custom option from the drop-down menu to the left of the first item in the list, Microsoft Exchange. You can then choose whether to install each individual option using that option’s drop-down menu. Once you’ve made all of your decisions, click Next to go on.
-
A Licensing screen appears, explaining the need for you to purchase Client Access Licenses before clients can access this Exchange server. Exchange Server 2003 supports only the per-seat licensing mode. Once you have read and agreed to this licensing, click the I Agree That I Have Read And Will Be Bound By The License Agreements For This Product option, and then click Next.
Note After the initial setup, you can add and remove individual components by running the Setup program again using the same procedure as outlined above. You can also access the Setup program using the Windows Add or Remove Programs Control Panel applet.
-
The Installation Summary dialog box appears, asking you to confirm your installation choices. You can use the Back button to change any settings you have made. When you are satisfied with your choices, click Next to install Exchange Server 2003.
-
The installation process can take some time. When it is done, a Congratulations screen appears, informing you that the installation is complete. Click the Finish button.
Installing Subsequent Exchange Servers
There are many reasons to add additional Exchange servers to an organization. The primary reasons are performance, capacity and scaling, and fault tolerance. Each is briefly discussed below.
Performance An organization could place certain Exchange services on additional Exchange servers, dedicating those servers to those functions. Examples are as follows:
Public and/or private information stores These databases could be located on an additional Exchange server dedicated to performing as a mailbox server or public folder server.
Connector software The same principle relates to running connector software on a dedicated Exchange server.
Capacity and scaling If the physical limits of a particular system are being approached, Exchange services and their related physical resources (e.g., disk space) can be spread out among multiple Exchange servers. This issue also relates to performance problems.
Fault tolerance through redundancy Many Exchange services and resources are replicated throughout an Exchange organization. This redundancy implements a built-in level of fault tolerance. For example, all the Exchange servers within a site share the same directory information through replication. If one particular Exchange server is taken offline, its directory information is automatically updated by another Exchange server through the replication mechanism when it comes back online.
The actual process of adding a subsequent Exchange server to an existing organization is nearly identical to installing the first server. The only difference is when you have defined more than one administrative or routing group in your organization (as detailed in Chapter 8, “Building Administrative and Routing Groups”). In this case, you will see two extra dialog boxes
while using the Installation Wizard. The first lets you choose the administrative group you want the new server to be a part of. The second dialog box, shown in Figure 3.1, lets you choose a routing group within the chosen administrative group that the server should be a part of. If you have not configured more than one administrative or routing group, you will see neither of these screens, and the installation will be identical to installing the first server.
Upgrading from Exchange 2000 Server
Exchange Server 2003 supports upgrades only for servers that are running Exchange 2000 Server with Service Pack 3 or later installed. If you are currently running a previous version of Exchange Server, you can either upgrade it to Exchange 2000 Server with Service Pack 3 to support an upgrade to Exchange Server 2003 or upgrade it to Exchange 5.5 Server with Service Pack 3 for a co-existence/migration scenario, as discussed later in Chapter 11.
The process to upgrade an Exchange Server 2003 Service Pack 3 computer to Exchange Server 2003 is a fairly simple once you’ve met all of the prerequisites. You should ensure that you understand the following points before attempting to upgrade your Exchange 2000 Server:
-
The server must be running Windows 2000 Service Pack 3 or higher or Windows Server 2003.
-
The Exchange 2000 Server installation must not have any of these components installed (you must uninstall them before upgrading):
-
Microsoft Mobile Information Server components
-
The Instant Messaging service
-
The Exchange Chat service
-
The Key Management service
-
The cc:Mail connector
-
The MS Mail connector
Note If you need to continue using any of these components and services, you will not be able to upgrade that server to Exchange Server 2003.
-
If you use a front-end/back-end Exchange server arrangement (discussed more in Chapter 4, “Creating and Managing Exchange Clusters,” and Chapter 7, “Configuring Client Access”), you must upgrade all of your front-end servers before starting to upgrade any of your back-end servers.
-
You can upgrade only the same language version of Exchange. For example, you cannot use the French language version of Exchange Server 2003 to upgrade a German language version of Exchange 2000 Server.
-
The Exchange 2000 Server organization must be operating in native mode.
Note For more information about Exchange 2000 Server to Exchange Server 2003 upgrade considerations, be sure to see Knowledge Base article 822942, located at http://support.microsoft.com/default.aspx?scid=kb;en-us;822942.
Once all of these requirements are in place, upgrading to Exchange 2000 Server is not too difficult.
| Note | Before undertaking an upgrade, you should always perform a complete backup of your current installation. If something goes drastically wrong with the upgrade, you can then go back to your previous installation. |
Performing the Exchange 2000 Server Upgrade
Once you’ve met all of the requirements to upgrade your Exchange 2000 Server native mode servers to Exchange Server 2003, the actual upgrade process is very similar to that of installing a new Exchange Server 2003 computer.
The basic sequence of steps you must perform, as instructed by the Exchange Server Deployment Tools Upgrade From Exchange 2000 Native Mode option, is as follows:
-
Verify that the required services are installed and running as discussed earlier.
-
Run the DCDiag and NetDiag tools to gather diagnostics data on your domain controllers and network.
-
Run ForestPrep to extend the Active Directory schema for Exchange Server 2003.
-
Run DomainPrep to prepare the required domains for Exchange Server 2003.
-
Upgrade the Exchange 2000 Server computer by running the Exchange Setup application and selecting Upgrade on the Component Selection dialog box. The user account you are using must have Full Exchange Administrator permissions and must be a member of the local Administrators group on the server.
Installing Exchange Server 2003 on Clustered Servers
As stated earlier in this chapter, the Enterprise Edition of Exchange Server 2003 is designed to work with the Microsoft Clustering Service. Clustering groups servers logically into an interdependent system, called a cluster, for the purpose of fault tolerance. This cluster appears as a single server to clients and applications. In the event of a failure on one system, the Clustering Service moves the affected services to a functioning node in the cluster. Previously Exchange 5.5 supported only Active/Passive clustering, in which only one node of a cluster was active at a time, and Exchange 2000 Server supported only Active/Active clustering, in which all nodes function simultaneously. Exchange Server 2003 supports both Active/Active clustering with two nodes and Active/Passive clustering with between two and eight nodes. Server clusters allow you to enable resource groups that are not bound to a specific computer and can fail over to another node. Exchange considers each resource group as a separate instance of Exchange, called a virtual server.
Each resource group in a cluster running Exchange must share the following resources:
-
IP address
-
Network name
-
A physical disk or disk system, such as RAID5
-
Exchange System Attendant service
Note Obviously, there is a lot more to clustering than a single chapter can go into. For more detailed information on Exchange clustering, see Chapter 4.
In order to run Exchange with the Microsoft Clustering Service, you must be running Windows Server 2003 Enterprise Edition, Windows Server 2003 Datacenter Edition, Windows 2000 Advanced Server, or Windows 2000 Datacenter Server. The number of nodes you can have in the Exchange Server 2003 cluster is limited by the operating system the server is running:
-
You are limited to two nodes when installing on Windows 2000 Advanced Server SP4.
-
You are limited to four nodes when installing on Windows 2000 Datacenter Server SP4.
-
You can have up to eight nodes when installing on Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Server Edition.
When installing Exchange Server 2003 into a cluster, it must be completely installed on one node before being installed on another node. In addition, you must install Exchange on each node using the same user account that you used to install the Clustering Service. You must also install Exchange on the same drive letter and directory on all nodes. Finally, you must install the same Exchange components on all nodes. We will examine the installation and management of Exchange clusters in more detail in Chapter 4.
Post-installation Considerations
This section discusses some of the results of the Exchange installation. During the installation of Exchange, the activities of setup.exe include creating Exchange services, creating an Exchange directory structure, copying files to that directory structure, creating share points to the directory structure, and adding keys and values to the Windows Registry. Knowing the results of these activities is helpful for the Exchange administrator, especially in troubleshooting situations (which will be discussed later in this chapter).
Exchange Services
After a successful installation of Exchange Server 2003, you can verify that the required services are installed. When you examine the Services console, you should see the following new Exchange services listed:
-
Microsoft Exchange Event
-
Microsoft Exchange IMAP4
-
Microsoft Exchange Information Store
-
Microsoft Exchange Management
-
Microsoft Exchange MTA Stacks
-
Microsoft Exchange POP3
-
Microsoft Exchange Routing Engine
-
Microsoft Exchange Site Replication Service
-
Microsoft Exchange System Attendant
Default Directory and File Structure for Exchange
The default root directory for Exchange is \Program Files\Exchsrvr. Setup creates subdirectories under that root directory and copies Exchange files to those subdirectories. Table 3.2 is a listing of the default Exchange subdirectories under the root and the type of files in those subdirectories.
| Folder | Contents |
|---|---|
| ADDRESS | This directory contains subdirectories with program files (DLLs) that can be used to generate foreign addresses for Exchange recipients. When an Exchange server uses a connector or gateway to create interoperability with a foreign system, the System Attendant component automatically generates a foreign address for each Exchange recipient. This foreign address, also referred to as a proxy address or simply an e-mail address, is what the users of the foreign mail system see and where they send mail. The program files in the subdirectories can generate these proxy addresses. The complete installation downloads files for the following foreign mail systems: Lotus cc:Mail, Microsoft Mail, Novell GroupWise, Lotus Notes, Internet mail (SMTP), and X.400 mail. |
| BIN | This directory contains many of the files that are the components and services of Microsoft Exchange Server. |
| CONNDATA | This directory contains subdirectories that hold the files that are the Microsoft connectors. The complete installation downloads files for the following connectors: the Microsoft GroupWise Connector, the Microsoft Schedule+ Free/Busy Connector, and the Lotus Notes Connector. |
| ExchangeServer_ computername | This directory is named using the NetBIOS name of the computer and holds miscellaneous files for global Exchange support. |
| exchweb | This directory holds files for Outlook Web Access. |
| Computername.log | This directory holds log files for message tracking. |
| Mailroot | This directory holds working directories for message transfer. |
| MDBDATA | This directory is one of the most important on your server, because it contains the Information Store database. This database is composed of the following files: the Private Information Stores (EDB and STM), which are the serverbased storage of mailboxes; the Public Information Stores (EDB and STM), which are the server-based storage of public folder data; and the database transaction log files (LOG), which are the files to which data is initially written in order to provide for faster performance and fault tolerance. |
| MTADATA | This directory holds the files that make up and relate to the Message Transfer Agent (MTA). |
| OMA | This directory holds files for Outlook Mobile Access. |
| RES | This directory holds files that contain message strings used when Exchange logs events to the Windows Event Log. |
| SCHEMA | This directory holds the XML files that support the Exchange extension of the Active Directory Schema. |
| SRSDATA | This directory holds Site Replication Service–related data. |
Share Points and Permissions for Exchange Directories
Table 3.3 lists the Exchange directories that are shared on the network, with the specified share names and permissions, assuming that Exchange was installed on the C: drive.
| Folder | Shared As | Permissions |
|---|---|---|
| C:\EXCHSRVR\ADDRESS | Address | Administrators group: Full Control Everyone group: Read |
| C:\EXCHSRVR\RES | Resource$ | Administrators group: Full Control Everyone group: Read |
| C:\EXCHSRVR\ COMPUTERNAME.LOG | COMPUTERNAME.LOG | Administrators group: Full Control |
Exchange Entries in the Windows Registry
During installation, Setup creates entries in the Windows Registry. Some of these entries are mentioned here.
Registry information about the presence of the Exchange application on a machine, as well as the directory location of the installation, is found in the following Registry location:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Microsoft
\Exchange
\Setup
The following Registry location records the settings for the various Event Logs created by the different Exchange components:
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Services
\EventLog
\Application
\
The Exchange component settings are stored in the Registry at the following location:
\HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Services
\
License settings for Exchange are stored in the following location:
\HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Services
\LicenseInfo
\MSExchangeIS
| Note | Although these Registry locations are good to know, don’t expect to be tested on them during your exam. |
Exchange System Manager
One powerful feature of Microsoft Exchange is the ability to centrally administer an entire Exchange organization. This is accomplished through a snap-in for the Microsoft Management Console named Exchange System Manager (see Figure 3.2). This snap-in can run on any Windows 2000, Windows XP Professional, or Windows Server 2003 computer on the Exchange network. From this single point, an administrator can administer all the Exchange servers in an organization. This is sometimes referred to as single-seat administration.
The actual snap-in file for System Manager is Exchange System Manager.msc and is stored in the \EXCHSRVR\BIN directory. While the Exchange Setup program can install the snap-in on the Exchange Server machine, the administrator will probably also want the Exchange System Manager on their workstation. Installing the Exchange System Manager onto a computer also installs a new version of the Windows Backup utility and extensions to the Active Directory Users and Computers and Performance Monitor programs. These changes enable those programs to work with Exchange Server 2003.
Troubleshooting an Exchange Installation
If any problems arise during an Exchange installation, there are several areas you may want to investigate first. Should you run into installation problems, you should begin your troubleshooting efforts by checking the following:
Make sure that you have installed Internet Information Services (IIS) and the necessary protocol support. IIS is no longer automatically installed on a clean installation of Windows Server 2003. You will need to install IIS and the required services and components of IIS as discussed earlier in this chapter.
Make sure that you have installed Windows 2000 Service Pack 3. Installing Exchange Server 2003 on a Windows 2000 Server computer requires that Windows 2000 Service Pack 3 or later has been installed first. Without SP3 or later installed, the installation of Exchange Server 2003 will fail.
Determine that you have the appropriate permissions to install the software. In order to install Exchange Server 2003, you must have local Administrators permission on the server on which you want to install. In order to run the ForestPrep tool, you must be a member of the Enterprise Admins and Schema Admins groups and the local Administrators group on the computer on which you run the utility. In order to run DomainPrep, you must be a member of the Domain Admins group and the local Administrators group on the computer on which you run the utility.
Verify that you have properly prepared the forest and domain. In order to install Exchange Server 2003 in all but the simplest single-domain situation, the ForestPrep tool may need to be run once in the forest, and the DomainPrep tool may need to be run in each domain in which Exchange Server 2003 will be installed.
Make sure that you have established share permissions. Make sure the necessary Exchange directories are shared if other servers are having problems connecting to the Exchange server after installation.
Observe the Exchange Server boot process for alert messages and to ensure that all necessary services have been started. If there are any problems with the Exchange server boot process, alert messages can be sent to the console and/or written to the Windows Event Log. You may also want to check that all the necessary Exchange services have been started. This can be done by going to Administrative Tools and Services or to a command prompt and executing NET START. Some Exchange services are dependent on other Windows services being started. If the dependent service is not started, the Exchange service will not start.
Use the Setup Log to determine problems that the Exchange Setup program may have logged.
While Setup is running, it creates a log of what it is attempting. This log file, called Exchange Server Setup Progress.log, is stored in the root directory of the drive on which Exchange is installed. If you run into problems during installation, the log file can help you find out what part of the installation failed or, at least, where in the installation process the failure occurred.
0 comments
Post a Comment