Learn Exchange Server 2000: Installing Exchange Server 2000

Monday Apr 8th 2002 by ServerWatch Staff

Michael Bell's latest article in the Learning Exchange Server 2000 in 15 Minutes a Week series wraps up a discussion on two pre-installation utilities, ForestPrep and DomainPrep, and walks the reader through an installation of Exchange Server 2000.

by Michael Bell

Well, as promised last week, we are going to start off this week by finishing our look at Forestprep and Domainprep. After that, we will actually start through an actual installation of Exchange 2000 and see what's new in the installation program. In case you have forgotten, you might want to look back at last week's article for a quick review of how to run setup with either of these switches, as well as what each does.

When we were talking about Forestprep, we mentioned that this process was responsible for extending the AD schema for the introduction of the first Exchange server into our organization. The requirement to run Forestprep was to have both Schema admin and Enterprise Admin permissions. But in a smaller organization, you might be all of those things, as well as the Domain Administrator and the local administrator to boot. If this is the case, then you might not want to run forestprep as a separate process, but instead just run the installation program directly. You can do that, of course, but just be aware that the installation program will appear to take a long time to run, and it is because it will be running forestprep in the background. There is no way around extending the schema before introducing the first Exchange server into your Windows 2000 environment; the forestprep switch actually makes over 1800 changes to the schema of AD! It is simply a question of whether you want to run forestprep by itself, or run it during the installation of the first Exchange 2000 server.

The same could be said for running domainprep. If you are a member of the Domain Administrators group, you wouldn't have to run domainprep separately. By launching the installation, you will run domainprep as part of the installation process. However, there is one situation where you would want to run domainprep as a separate process. This would be the case if you wanted to have mail-enabled recipients in a domain where no Exchange 2000 server existed. In this case, you run domainprep to create the Recipient Update Service (RUS) object. This allows users in a domain where no Exchange 2000 server is installed to still take advantage of the messaging capabilities of Exchange 2000.

One last thing worth mentioning here. Exchange 2000 comes in 2 different flavors, Standard Edition and Enterprise Edition. For our purposes, we will be discussing Enterprise Edition in this series. However, I do want you to be aware of the major differences between the two, so I will enumerate them here. First of all, the Standard Edition has a database size limited to 16GB. It does not allow for multiple databases per server, and you cannot implement active/active clustering. Chat is not available as a product option, and you cannot configure a front-end/back-end configuration with Standard Edition (although the Standard Edition can act as a back-end server to an Enterprise Edition front-end server.)

Installing Exchange Server 2000

Now that we have that out of the way, we are actually ready to start the installation of our first Exchange 2000 server into our organization. At this point, we have already accomplished the forestprep and domainprep portions of the installation, so the only thing that we need at this point are local administrator permissions and Exchange Full Administrator permissions to the Exchange Organization object. Of course, having the Exchange 2000 CD won't hurt either, so let's grab our disc and start the installation.

The first screen that we see is the Exchange 2000 splash screen that shows our different options that are available with Exchange 2000. We select setup, and then we are off and running. Of course, the first screen that we will see will be the welcome screen as follows:

Next up will be our license agreement screen. If you haven't already tried, if you select that you don't agree with the license agreement, the setup program will exit. My guess is that you want to install the product (after all, you already paid for it), so agreeing is the logical choice here:

After we have accepted the license agreement, we see the next screen which requests our Product Identification Key. This will be a 25-digit code, typically located on the back of the CD case that Exchange 2000 came in. Once you have correctly entered the key, you can click on next to continue the installation.

Next up is the Component Selection Screen where we will choose to do either a Custom, Typical, or Minimum installation of Exchange 2000. For testing purposes, this is something worth remembering. The Typical Installation option will install Microsoft Exchange 2000, Microsoft Exchange Messaging and Collaboration Services, and Microsoft Exchange System Management Tools. The Custom Installation option allows you to pick and chose which components you would like to install, including the different connectors for attaching to legacy mail systems like a MS Mail Postoffice or 3rd Party mail systems like GroupWise and Lotus Notes. The Minimum Installation option allows you to install Exchange 2000 and the Microsoft Exchange Messaging and Collaboration Services. If you look at the next screen shot, it should give you a pretty good idea of what is installed with each option.

Of course, you also have to decide where you want to install the Exchange server files. In my case, I have accepted the default installation location. Keep in mind that after the installation, I can use the Exchange System Manager to move the database and log files to alternative locations, preferably a separate disk system. This helps minimize the impact that Exchange has on the system it is installed on. We will be talking about the ideal disk configuration for Exchange 2000 in a later article.

I have also included a screen shot here that shows you a possible error message that you might get during the process of selecting the components for Exchange 2000. The error message looks like this and should pretty much be self-explanatory:

Installation Continued

Exchange 2000 requires that the NNTP service of IIS be installed. If you haven't done so prior to starting the installation of Exchange 2000, you will have to exit the installation, install NNTP, and then restart the installation of Exchange 2000 again. Next up is another license agreement, but unlike the end-user license agreement at the start of the installation program, this license agreement indicates your agreement with the Exchange 2000 licensing terms. Once you have accepted the agreement, and click next, you will see the following component summary screen. Don't dismiss this screen too quickly! It gives you a chance to verify both the component selections and default installation path that you have selected. Take the time to view this over, and you can rest assured that your first Exchange 2000 server will be installed as you intended it.

There will be a brief file copy process, and then installation of Exchange 2000 will begin. This screen should look familiar, because it looks alot like the screen we saw while we were running ForestPrep and DomainPrep.

Once the installation has completed, you will be presented with the final screen, showing that installation has completed successfully.

Click finish to close out the installation, and now you are ready to start working with Exchange 2000. As I mentioned at the start of this series, if you take the time to learn about the necessary prerequisites for installing Exchange 2000, you can assure yourself of a smooth and somewhat painless installation. Next week, we will take a look at administering Exchange 2000, including the utilities that we will be using. We will also talk about some of the new features of Exchange 2000, including Administrative Groups, and how to create and manage them. As always, I hope that you find the information in this article to be useful. If you have any questions, just go out to the Exchange forum and post your questions and I will try to answer them as quickly as possible. Until next time, cya!

Michael Bell


Mobile Site | Full Site