Installing Exchange 2000 Server

[Previous] [Next]

Finally! After all of the reading and planning, you actually get to run Exchange Server Setup. You can run Setup from either the Exchange 2000 Server CD-ROM or a shared network installation point. If you are using the CD-ROM, you have only to insert the disk and watch Setup start automatically. If you're installing over the network, you have to find and run the Setup program yourself. There could be multiple versions of the installation files for different encryption levels and for different languages. Be sure that you find the right files for your situation. If you are performing a typical installation of Exchange 2000 Server on a computer with an Intel processor, for example, you will find Setup.exe in the \Setup\I386 folder on your CD-ROM.

NOTE
Remember that before you begin the installation you must be logged on with the Windows 2000 user account that you want to be given administrative privileges in Exchange Server. This account should be a member of the Domain Admins, Enterprise Admins, and Schema Admins security groups.

If you insert the Exchange 2000 Server CD-ROM and the Autorun feature is enabled on your system, a splash screen appears from which you can run Setup and access other features on the CD. If Autorun is disabled, you will need to run Setup.exe manually from the CD-ROM. In either case, the first thing you will see is the welcome screen of the Microsoft Exchange 2000 Installation Wizard, shown in Figure 7-5.

click to view at full size.

Figure 7-5. The first screen of the Installation Wizard.

NOTE
Before Setup starts, it may display a warning to shut down any other applications that are running. The single most common reason that an Exchange Server installation fails is that other MAPI-based applications are running in the background while Setup is running. These applications can include e-mail programs, Web browsers, and even components of Microsoft Office. Use the Processes tab of Windows 2000's Task Manager to find and close any such applications. You also need to shut down all instances of System Monitor that are monitoring the server, whether they are running locally or on a remote machine. Finally, you need to make sure that Event Viewer is not running on the server.

Choosing Components for Installation

After you've made sure that no other programs are running, you will encounter one screen that asks you to read and accept Microsoft's End-User License Agreement and one on which you enter the 25-digit key from the back of your Exchange CD cover. After you've completed these two steps and clicked Next, Setup searches for any components of Exchange Server that might already be installed on the computer. If Setup finds an installation of Exchange Server 5.5, you must choose whether you want to perform an upgrade. Exchange 2000 Server supports upgrading only from Exchange Server 5.5 and not from versions previous to Exchange 5.5. For more information about coexisting with Exchange Server 5.5, see Chapter 14. The upgrade process is described later in this chapter. If no previous installation is found, you are taken to the component selection screen shown in Figure 7-6.

click to view at full size.

Figure 7-6. Choosing components for an installation.

Select one of three installation modes using the drop-down menu to the left of the Microsoft Exchange 2000 Server component. Typical mode (the default) installs all available components. Minimum mode installs the main Exchange component and messaging services but does not install System Manager or the collaboration tools. Custom mode lets you pick the components to install. You can designate the drive on which you would like Exchange 2000 Server installed by selecting the Microsoft Exchange 2000 Server component and clicking the Change Drive button. You can also specify the installation path on that drive by clicking the Change Folder button. All components you select to be installed are installed on the drive you choose; you cannot install individual components to different drives. Clicking on the Disk Information button opens a dialog box that shows you all of the drives on your system and the amount of space they have free.

If you are running Setup on a computer on which Exchange 2000 Server is already installed, you may see additional options as well, including Disaster Recovery, which attempts to reinstall the component, and Remove, which removes the component from an installation.

NOTE
For a basic messaging system, it usually is best to install only Microsoft Exchange Messaging and Collaboration Services and Microsoft Exchange System Management Tools. However, you may want to go ahead and install the other available components if you think you might need them at some point. That way, you won't have to return to your CD-ROM to reinstall it.

Table 7-2 describes each of the components available on the component selection screen. Once you have selected your components, click Next to go on to the next screen of the Installation Wizard.

Table 7-2. Components available in an Exchange 2000 Server installation

Component Description
Microsoft Exchange 2000 This is the primary node for the Exchange Server installation. To install any Exchange components, you must select Install on this node. To change the default drive on which other components will be installed, change the drive for this component.
Microsoft Exchange Messaging and Collaboration Services Select Install on this node to install all of the basic messaging components of Exchange, each of which is also described in this table. Once you select this component, all subcomponents are also selected. You must individually deselect any that you don't want installed. You must select this node to install the real-time collaboration components as well. To install this node, your system must be running the NNTP stacks as part of the IIS installation.
Microsoft Exchange MSMail Connector This item supports message and directory information transfer between Exchange 2000 Server and Microsoft Mail for PC Networks.
Microsoft Exchange cc:Mail Connector This item supports message and directory information transfer between Exchange 2000 Server and Lotus cc:Mail.
Microsoft Exchange Connector for Lotus Notes This item supports message and directory information transfer between Exchange 2000 Server and Lotus Notes.
Microsoft Exchange Connector for Novell GroupWise This item supports message and directory information transfer between Exchange 2000 Server and Novell GroupWise.
Microsoft Exchange Key Management Service The Key Management Service is an Exchange-specific security enhancement of the Windows 2000 Server Certificate Services. For more information on using the Key Management Service, see Chapter 21.
Microsoft Exchange System Management Tools This option installs the Exchange System snap-in. You must install this component to manage all Exchange components. You can also install it by itself under Windows 2000 Server or Windows 2000 Professional to manage your Exchange organization remotely. For more information on using this utility, see Chapter 8.
Microsoft Exchange Chat Service These components allow your users to join and form chat communities. For more information about administering Chat Service, see Chapter 18. If you are installing Chat Service, you must also install Exchange System Management Tools and Exchange Messaging and Collaboration Services.
Microsoft Exchange Instant Messaging Services This component allows your users to send and receive instant messages. For more information about administering the Instant Messaging Services, see Chapter 19. If you are installing the Instant Messaging Services, you must also install Exchange System Management Tools and Exchange Messaging and Collaboration Services.

Creating an Organization

In the next phase of installation, you create the organization that you've been planning. First you must specify an installation type, as shown in Figure 7-7. You can choose either to create an Exchange 2000 organization or to join an existing Exchange 5.5 organization. If you will be joining an Exchange 5.5 organization, you will want to check out Chapter 14. If you want to create an Exchange 2000 organization, select the default option, Create A New Exchange Organization. After making your choice, click Next.

On the next screen of the Installation Wizard, shown in Figure 7-8, you will name your organization. Do not take this task lightly. After the installation, even during subsequent installations, you will not be able to change the name without tearing down and completely reinstalling Windows 2000 and Exchange 2000 Server. If you have not yet decided on the name, you haven't properly planned your organization. See Chapters 5 and 6 for more information on planning and naming your organization. Click Next when you've entered the name.

click to view at full size.

Figure 7-7. Specifying an installation type.

NOTE
This section assumes that you're creating a new organization. If you're joining an existing Exchange 2000 organization, see "Installing in an Existing Organization" later in this chapter for a description of the slight differences between the two procedures.

click to view at full size.

Figure 7-8. Specifying a name for a new organization.

Licensing

The next screen of the Installation Wizard, shown in Figure 7-9, shows you the Per Seat licensing agreement. Exchange 2000 Server supports only Per Seat licensing, meaning that any client computer that connects to Exchange 2000 Server requires a Client Access License. For example, a computer that connects to Exchange 2000 Server using Microsoft Outlook 2000, one that connects using Outlook 2000 and Microsoft Internet Explorer, and one that connects using only Internet Explorer would each need a Client Access License. After you've agreed to the licensing agreement, click Next.

click to view at full size.

Figure 7-9. The Per Seat licensing agreement.

Confirming the Installation Choices

You're just about ready to start the actual installation. After you have designated a service account and clicked Next, you see an installation summary screen that looks just like the component selection screen (refer back to Figure 7-6), except that you cannot change anything. You can, however, back up through the screens in the wizard to change any information you want. When you're satisfied with the summary, click Next. Setup then begins copying files. Depending on the components you selected for installation, this can take several minutes.

During the process, Setup may notify you that it needs to extend your Windows 2000 Active Directory Schema, as shown in Figure 7-10. Assuming that you logged on with a user account that has appropriate permissions to do this, go ahead and click OK. Don't be alarmed if it seems as though Setup is not getting anywhere. The schema updating process can take quite a bit of time (even hours), depending upon your situation. This may be a great chance to go get some lunch. When Setup completes the task, the Installation Wizard will indicate that the installation was successful. Click Finish and the new Exchange services will start.

REAL WORLD   What If You're Not Allowed to Update the Schema?

In some large companies, or those with tight administrative policies, only a select few administrators may have permission to mess around with the Windows 2000 Active Directory Schema. How, then, are you, a lowly Exchange administrator, to get your installation job done? Take heart—there is a way. You can run Exchange 2000 Server Setup from the command line, using a switch that causes Setup only to update the Windows 2000 Active Directory Schema without actually installing any of the Exchange 2000 Server components. The command for doing this is Setup /forestprep. This means that you can hand the Exchange CDROM to an administrator who has permission to update the schema and let him or her update the schema for you. The administrator could also update the schema by using Exchange files on a shared network installation point. Once the schema has been updated, you can install Exchange 2000 Server yourself. There are two added bonuses to having someone else update the schema. The first is that you don't have to wait around for the update to finish. The second is that if something goes wrong, someone else gets the blame.

click to view at full size.

Figure 7-10. Extending the Windows 2000 Active Directory Schema.

Installing in an Existing Organization

Installing Exchange 2000 Server in an existing Exchange 2000 organization is nearly identical to installing it as the first server in an organization. You need to be aware of only a couple of small differences in the procedure. You start Setup the same way: from either the CD-ROM or a network installation point. The first difference you will notice is that you are not able to change the organization name. The name is displayed (refer back to Figure 7-8), but it is dimmed.

After you've chosen your administrative and routing groups, the rest of the process is no different from the one you used to install the first server in an organization. Make sure you select the Exchange service account used by other servers in the organization. Because Setup will not need to update the Windows 2000 Active Directory Schema again, the installation will take much less time.

REAL WORLD   Automating Exchange 2000 Server Setup

If you plan to deploy a large number of Exchange servers in your enterprise, or if you need to deploy servers remotely, you will be glad to know that there is a way to automate the setup process. Setup places all of the information that controls its file-copying process in a file named Setup.ini. The file is customized for a particular installation when you make choices in the various Installation Wizard screens described previously.

You can create your own Setup.ini files based on samples on your Exchange CDROM. Go to the Support folder, and then open the Batsetup folder. You'll find the samples in the Setup folder. You can then create a batch script that runs the Setup program, using the information in your customized file. If you are deploying Exchange 2000 Server on existing Windows 2000 servers in your enterprise, you can also use Microsoft Systems Management Server or a similar application to further automate the process.

MORE INFO
To learn more about automating Exchange Server Setup, including all of the parameters for customizing the Setup.ini files, consult the online product documentation.

Upgrading from Exchange Server 5.5

You can upgrade existing servers running Exchange Server 5.5 with Service Pack 3 applied to Exchange 2000 Server. You will have to take the server off line while you perform the upgrade, so it is best to do it during planned downtime. Also, if the existing server is running Microsoft Windows NT 4, you will need to upgrade it to Windows 2000 Server before you can upgrade to Exchange 2000 Server.

NOTE
We suggest that you familiarize yourself with the tools and methods for enabling coexistence between Exchange 2000 Server and Exchange Server 5.5 before deciding to upgrade your Exchange 5.5 servers. Coexistence is discussed in detail in Chapter 14.

When you run Exchange 2000 Server Setup on an existing Exchange 5.5 server, Setup will determine that you are running a previous version of Exchange and give you the option of upgrading the server, as shown in Figure 7-11. Other than this, the upgrade process is nearly identical to the process for installing Exchange 2000 Server outlined previously. The only other difference is that you cannot add any components to the existing server configuration. Once the upgrade is complete, you can rerun Setup to add additional components.

click to view at full size.

Figure 7-11. Upgrading a server from Exchange Server 5.5 with Service Pack 3.

If you are running Exchange 5.5 on a Windows NT primary domain controller (PDC), you will also need to change the LDAP port that the Exchange 5.5 directory service is using to avoid port conflicts. Although you can do this at any time before you upgrade to Exchange 2000, Microsoft recommends that you change the port before you upgrade the operating system to Windows 2000 Server. After you change the LDAP port, you must change the port number on the Active Directory Connector (ADC) connection agreements that are configured on the computer. To change the port, follow these steps:

  1. Open the Exchange 5.5 Administrator program.
  2. Expand the Sitecontainer, expand the Configuration container, expand the Protocols container, and then double-click LDAP (Directory) Site Defaults.
  3. On the General tab, change the value in the Port Number field to something other than 389. Click OK.
  4. Open Control Panel, double-click Services, select Microsoft Exchange Directory, and then click Stop.
  5. After the service stops, click Start. Verify that service has restarted, and then click Close.

REAL WORLD   The Move Mailbox Upgrade

If you find that the hardware on your existing Exchange Server 5.5 server doesn't meet the minimum requirements for Exchange 2000 Server (or if you want to upgrade the hardware anyway), you can upgrade to Exchange 2000 Server using a method called the move mailbox upgrade. In this type of upgrade, you install Exchange 2000 Server on new hardware and join an existing Exchange Server 5.5 site. Once Setup is complete, you can move the information from the old server to the new server and then remove the old server from the network. In addition to mailboxes, you can also move public folders by creating replicas of them on the new server.



Microsoft Exchange 2000 Server Adminstrator's Companion
Microsoft Exchange 2000 Server Adminstrator's Companion
ISBN: N/A
EAN: N/A
Year: 1999
Pages: 193

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