Skip navigation

Exchange Ideas - 30 Jan 2006

Tips, news, and community resources for messaging admins

Cluster-Creation Modification


In "Build an Exchange 2003 Cluster: Install Exchange on the Cluster," December 2005, InstantDoc ID 47909, I describe how to build a brand-new Exchange Server cluster. For the article, I built a cluster from scratch so that I could verify the correct sequence of tasks, in terms of installing Windows and Exchange service packs and creating the Exchange Virtual Server (EVS). In the article, I described that sequence of tasks, which I'll call Method 1, as follows:

  1. Build a two-node Windows Server 2003 cluster and upgrade each node to Windows 2003 Service Pack 1 (SP1).
  2. Create the dependent EVS resources (e.g., Network Name, IP Address, Storage, Microsoft Distributed Transaction Coordinator—MS DTC).
  3. Install Exchange Server 2003 release to manufacturing (RTM) on Node 1.
  4. Install Exchange 2003 RTM on Node 2.
  5. Create the EVS.
  6. Upgrade Node 1 to Exchange 2003 SP2.
  7. Upgrade the EVS to Exchange 2003 SP2 by using Cluster Administrator (take the EVS offline, then right-click the EVS and select Upgrade Exchange Virtual Server).
  8. Upgrade Node 2 to Exchange 2003 SP2.

This method creates the EVS with Exchange 2003 RTM installed on the cluster, applies the Exchange 2003 SP2 binaries to Node 1, upgrades the EVS to Exchange 2003 SP2, then upgrades the binaries on Node 2 to Exchange 2003 SP2. However, since writing the article, I've discovered an easier way. I'll call this way Method 2:

  1. Build a two-node Windows 2003 cluster and upgrade each node to Windows 2003 SP1.
  2. Create the dependent EVS resources.
  3. Install Exchange 2003 RTM on Node 1.
  4. Install Exchange 2003 RTM on Node 2.
  5. Upgrade Node 1 to Exchange 2003 SP2.
  6. Upgrade Node 2 to Exchange 2003 SP2.
  7. Create the EVS.

The difference between these methods is that in Method 2, you apply Exchange 2003 SP2 to each node before creating the EVS. In order to verify the steps for Method 2, I rebuilt the cluster from scratch, using the new method. Method 1 works, but Method 2 is slightly more straightforward.
—Daragh Morrissey

White Paper Central


White papers can be a great means for finding new (or tried and true) solutions and strategies. However, hunting down the right paper can be a hassle. Windows IT Pro keeps a cache of Exchange Server–related white papers so that you don't have to hunt high and low. Some papers are written by our authors; some are submitted by vendors. A few recent examples include "How to Evaluate and Choose a Messaging Archiving Solution" ( ILumin), "What You Don't Know Can Hurt You: How to Protect and Manage Instant Messaging," (Postini), and "Your Guide to Exchange Server 2003 High Availability" (HP). Paper downloads require registration but are free. Visit White Paper Central at http://www.windowsitpro.com/Whitepapers/.

Exchange Tip: Saying Goodbye to Exchange 5.5


This month's tip comes from John Savill's FAQ for Windows site (part of the Windows IT Pro community). See "Get More Online" for directions to the site and to more tips. (You can find this tip online at http://www.windowsitpro.com, InstantDoc ID 48805.)

How can I remove my last Exchange Server 5.5 installation from my Exchange Server 2003 organization?

If you've migrated your organization from Exchange 5.5 to Exchange 2003 and no resources reside on the Exchange 5.5 server, perform the following actions to remove the server:

  1. Log on to the Exchange 5.5 server and stop all services. The easiest way to do this is to stop the Exchange System Attendant by opening a command line and typing
    net stop MSExchangeSA

    You'll see a warning that this command will stop other services. Click Yes. After the command finishes running, run it again. (Doing so stops the MSExchangeSA service.)
  2. Log on to an Exchange 2003 server and start the Exchange 5.5 Administrator Console application (you must use the Exchange 5.5 version because Exchange 2003 tries to delete the Exchange server configuration from Active Directory—AD). When prompted for a server, point the Exchange 5.5 Administrator Console to the Exchange 2003 server.
  3. Expand the , Configuration, Servers node and select the Exchange 5.5 server in the Exchange administration application's right pane. From the Edit menu, select Delete. The application performs a check for resources; click Yes to any resources still found (assuming you know that you've migrated everything you require). You might also see a warning that the MSFB and MS extensions could not be loaded. Click Ignore, then click OK to delete the confirmation message.
  4. Start Exchange 2003 Exchange System Manager (ESM). The Exchange 5.5 server will no longer be visible under the Servers container (, Administrative Groups,, Servers).
  5. You can now delete the Site Replication Service (SRS) connection by opening the Tools, Site Replication Services node. Select Microsoft Exchange Site Replication Service (), then select Delete from the Edit menu. Click Yes to the confirmation message.
  6. To raise the operational mode of the Exchange organization, right-click the organization at the root of the node tree and select Properties from the context menu. Go to the General tab and select Change Mode. Click Yes to the confirmation dialog box, then click OK.
  7. To remove the Active Directory Connector (ADC) connections, start the Microsoft Management Console (MMC) Active Directory Connector Services snap-in. Right-click each connection under the Active Directory Connector node and select Delete. You might receive a warning that the connection is the primary connection agreement (CA). Click OK, then click Yes to the deletion-confirmation dialog box. You'll usually have at least two connections: one user and one public folder.
  8. Uninstall the ADC tools and services from the server. Your job is done!

Make the Connection


If you haven't already made your plans to attend Microsoft Exchange Connections 2006, you still have time. This year, we've added a spring edition of the conference, so you don't even have to wait until October.

We'll be heading to Orlando for 4 days of heavy lifting, Exchange Server?style. At the Fall 2005 conference, attendees clamored for more Microsoft SharePoint Portal Server and Windows SharePoint Services content, so the Spring 2006 conference will include an entire SharePoint track. Get ready for sessions such as "Backup and Restore Tips and Tricks for SharePoint" (presented by Michael Noel) and "How Does It Work—An Admin-Level Overview of SharePoint" (Darrin Bishop). Exchange sessions include "Using Continuous Backup for Data Protection" (Paul Robichaux) and "Outlook Security: Balancing Protection with Usability" (Sue Mosher). The event will also include Peter O'Dowd's ever-popular, hands-on Exchange Troubleshooting Specialist Course. (Space for that course is limited, and the sessions fill up fast!)

As in years past, the conference will be co-located with Windows Connections 2006, and Exchange Connections attendees can attend Windows sessions at no additional cost. See "Get More Online" for a link to the complete session list and registration information.

Lisa Pèrè ([email protected]) is a senior editor and Exchange SME for Windows IT Pro and Exchange & Outlook Administrator.

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish