Some lucky network administrators get to install Exchange 2000 from scratch. They don’t have to worry about coexistence with previous versions of Exchange. Chances are, you’re not one of them, though. Unfortunately, you can’t blindly install Exchange 2000 into an Exchange 5.5 environment without doing a little bit of preparation work. In this Daily Feature, I’ll show you what you must do to prepare Exchange 2000 and Exchange 5.5 to play together nicely.
The prep work
Even after you’ve upgraded your server to Windows 2000 and verified that your server meets the hardware requirements, there are still several housekeeping chores you’ll have to take care of before you can install Exchange 2000. The first of these chores is to install the NNTP services for IIS. To do so, open the Control Panel and double-click the Add/Remove Programs icon. When you see the Add/Remove Programs dialog box, click the Windows Setup button. After a brief delay, you’ll see a window displaying all of the installed Windows components. (This window often appears behind the existing window, so you may have to move it to the foreground.)
Navigate through the list of Windows components until you locate the Internet Information Services (IIS). Select IIS and click the Details button. You’ll now see a list of the available IIS components. Select NNTP Service from the list, as shown in Figure A, and then click OK. You’ll now be returned to the Windows Components Wizard. Follow the remaining prompts to copy the files off of your Windows 2000 installation CD (or the service pack CD).
|You must install the NNTP Service before you’ll be able to upgrade to Exchange 2000.|
The next step that you must perform before you can install Exchange 2000 only applies if you have Exchange 5.5 servers in your organization. Remember that Exchange 5.5 and Windows 2000 both use LDAP and rely on a directory service. Unfortunately, these directory services aren’t completely compatible with each other. Therefore, before you install Exchange 2000, you’ll have to make sure that the existing Exchange directory service and the Windows 2000 Active Directory aren’t set to use the same LDAP port.
However, before I tell you how to change the Exchange LDAP port number, I should point out a couple of things. First, it’s best to change the port number before you upgrade the server from Windows NT to Windows 2000. This will help you avoid confusion. If you’ve already upgraded to Windows 2000 though, the process will still work. Second, all of your Exchange servers need to use the same LDAP port number. When you change the LDAP port in the manner that I described above, it will change the port number for all of the Exchange servers in the site. However, if your organization has multiple Exchange server sites, you should consider changing the port number for all sites.
To change the LDAP port number, open the Exchange Administrator program that comes with Exchange 5.5. When the Exchange 5.5 Administrator program opens, navigate through the tree structure to: your organization | your site | Configuration | Protocols. When Protocols is selected, you’ll see a list of installed Exchange protocols in the column on the right. Double-click on the LDAP (Directory) Site Defaults protocol. You’ll now see the LDAP (Directory) Site Defaults Properties sheet. The LDAP services are set to use port number 389 by default. This is the same port number used by the Windows 2000 Active Directory. Therefore, you must change the port number to something other than 389. On my test servers, I selected 390. When you’ve made the change, click OK.
Once you’ve made the change to the LDAP port number, you must stop and restart the Exchange services for the change to take effect. Once you’ve verified that the Exchange services have successfully restarted, you can continue with the configuration process.
After you’ve changed the LDAP port number for any existing Exchange 5.5 servers, you must make sure that those servers are running Exchange Service Pack 3. Even though you’re not currently upgrading those servers to Exchange 2000, there’s a component you’ll have to load on the existing servers to allow them to talk to the new Exchange 2000 server. This component requires Exchange Service Pack 3 or later. If you don’t currently have Exchange 5.5 Service Pack 3 or later installed on your server, you can either use the copy that comes with TechNet, or you can download a copy from Microsoft’s Web site.
Installing the Active Directory Connector
The last step in the preparation process is to install the Active Directory Connector on one of the existing Exchange 5.5 servers. The Active Directory Connector is a component that allows the Exchange Directory Service to share data with the Windows 2000 Active Directory. You don’t have to install this component on every Exchange 5.5 server. Installing it on a single server will take care of the entire site.
To install the Active Directory Connector, begin by inserting the Exchange Server 2000 CD into the CD-ROM drive of one of your Exchange 5.5 servers. When you insert the Exchange 2000 CD, you’ll see an introduction screen. On the splash screen, click the icon labeled ADC Setup. When you do, Windows will launch the Microsoft Active Directory Connector Setup Wizard.
The first screen in the wizard is merely an introduction screen. You can skip it by clicking Next. The following screen asks you to select which components you want to install. Select both check boxes and click Next. At this point, you’ll see a screen asking which folder that you’d like to install the Active Directory Connector into. Make your selection and click Next.
The wizard will now ask you for the user name and password of the service account that’s used to run the Active Directory Connector. When picking out a service account, keep in mind that the service account must have administrative privileges and must also have permission to modify the Active Directory schema. After you’ve entered this information, click Next and the wizard will begin to copy the necessary files.
When the copy process completes, click Finish and the wizard will return you to the main Exchange 2000 installation screen. Close this screen and you’re done with the Exchange 5.5 preparation work. Now you’re ready to use Exchange 2000.
If you’re already running Exchange 5.5 on your network, you can’t just throw an Exchange 2000 server on your network and expect it to play nicely without a little advance work. In this Daily Feature, I’ve shown you some of the things you must take into consideration when putting Exchange 2000 into an Exchange 5.5 environment.
The authors and editors have taken care in preparation of the content contained herein but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.