Update Exchange 2003 Clustering

Hi Just to update on exchange 2003 clustering topic in previous post (https://netoverme.wordpress.com/2011/02/07/exchange-2003-clustering/).


What Did I do?

Before I install Exchange server 2003, I have to make sure I am running on the same version of windows server for instance windows server 2003 Enterprise edition R2.

I also have to make sure that I have 2 nics which is for heartbeat and public LAN. Since Windows Server 2003 Enterprise Edition is a member of a domain, my  SAN storage is running on a domain controller.

Furthermore, I need to create a user name for cluster, which I called admincluster. this should be created on local administrator of both servers.

Then run the cluster administrator and create a new cluster, for example a exchangecluster.

Add the first node and check the local quorum. make sure the quorum drive is set on the first node before adding the second node.

run the check up and analysis. Add the second node if it’s succeed.

I have to make sure that I install a component of Enable Network DTC access in both servers.

After that I have add a resource of Microsoft Distributed Transaction Coordinator. This can be done on a cluster resources.

We need a second drive to be shared as disk resource on clustering for mailbox databases. In this example, it is a drive E:ExchangeData.

Don’t forget to add a second node cluster. before install exchange server, test the cluster by shutting down the first node and the result the second node should be up.

after the clustering was successfully configured, then Exchange installation can be begun.

After Exchange software has successfully installed on both server, I have to add a resource of Microsoft Exchange System Attedant on cluster administrator.

Here is my attachment on step I’ve done on clustering before exchange installation

What Did I do on clustering before exchange installation


Exchange 2003 Clustering

Sorry for late update on this blog… I have been busy with the exchange clustering environment. It’s been a while I’ve been doing clustering in windows server 2003. In Exchange Server 2007, there are many type of clustering you can do for having high availability.

here is a simple scenario that I want to share with you all below:

 I will update on this following scenario above later.

Success of Installation on Transition Exchange 2003 and 2007

Hi back to my previous topic on transitioning Exchange 2003 to Exchange 2007.

I have my snapshot of the successful installation.

If you noticed during the installation, the Routing group between Exchange 2003 and Exchange server 2007 is created. Please see image below. This should be unchanged. The routing group is installed by default.

After that, you can view the mailbox of user in exchange server 2007. When you view their mailbox, in Exchange 2007, it will view Legacy Mailbox. This means that the mailbox is still stored in Exchange 2003 environment. Please see image below:

Another process example of mailbox user has been moved to Exchange 2007 mailbox database. please see image below:


To move mailbox, Expand Recipient Organization and choose Mailbox, right click the name of user mailbox and choose Move Mailbox. what you only have to do is to choose the mailbox store of Exchange 2007

After success moving mailbox, I also attach another image to show the sample of the different type of recipient mailbox store on image below.

Transition Exchange 2003 to Exchange 2007

Can you upgrade Exchange 2003 to Exchange 2007?

the answer is “no”.

so How? do I need to uninstall it?

you may don’t want to to do that if you have exchange server 2003 in the organization. You still can have your exchange 2003 alive in your company. What you need to do is to add new server that runs Exchange 2007, but yet it’s costly because your production server which is Exchange server 2007 needs 64 bit processor. There is no 32 bit for exchange server 2007 unless for trial version.

There are many pre-requisites to make your hand dirty.

On your domain controller, you need to raise up domain functional level to windows server 2003 and your exchange server should be in Native Mode.

To check  domain functional level. -> go to Active Directory for Users and Computers -> right click the servername -> Domain Functional level – If still Windows server 2000 native mode, change it to window server 2003

To check Exchange Server Organization. -> go to your exchange server -> Open Exchange System Manager. Right-click the server and properties

Extract your exchange server 2007 installer to the drive. In my case, I use Exchange server 2007 SP 1 32 bit trial version.


This is needed to run so that it will check the exchange server compatibility.

look at the image below:

click this url below:


use the command that given url above. make sure you run PrepareLegacyExchangePermission first and make sure that the Exchange 2003 is powered on and running.

Preparing Exchange 2007 SP1 in Windows Server 2003 SP2

There are steps to be done before installing Exchange 2007 SP1.

In Windows Server 2003. This is what I need to do:

  • I need to ensure it is upgraded to service pack 2 since I don’t have Windows Server 2003 R2. You can install service pack 2 right away without installing service pack 1
  • I Install .netframework 2.0 sp2 or above. I prefer to install .netframework 3.5
  • Microsoft Management Consosle (mmc) 2.0
  • Windows Server 2003 Power Shell 1.0  Knowledge Base KB KB926139
  • Cumulative Time Zone for windows server 2003 KB 931836
  • Joined Domain
  • ADAM for Edge Transport Server Exchange 2007 (Optional) (which is not in a domain member)


After that, extract the Exchange Server 2007 SP1 to local hard drive.

Run the setup to prepare the unattended installation

in Command Prompt:

– I sequently running the command

  • PrepareLegacy   – setup /PrepareLegacyExchangePermission
  • PrepareSchema – setup /PrepareSchema
  • PrepareAD        – setup /PrepareAD /OrganizationName:”netoverme”

Exchange Server 2007 SP1 on ISA Server 2006 architecture

Hi there, I would like to share my experience on setting up Exchange Server 2007 with the existing servers below:

  • ISA Server 2006 SP1
  • Edge Transport Server – Exchange Server 2007 SP1
  • Hub Transport, Mailbox, and Client Access Server – Exchange Server 2007 SP1
  • Active Directory
  • DNS Server

hoping the diagram looks like below:



Figure 1: Exchange 2007 & ISA Server 2006

Figure 2: DNS flow


Figure 1 and Figure 2 explained on which ports should be allowed to make the email is received and sent.

Ony my set up:

  • ISA Server is a member of a domain (joined domain)
  • Edge Server is NOT a domain member  – In Windows Server 2003, I used ADAM to connect to the LDAP. That’s why in figure 1, I open a port to allow the port 50636 and 50389 to connect Secure LDAPS.
  • DNS server integrated with Active Directory
  • Public DNS using the domain hosting providers – Creating MX Records and resolve domain for example, mail.netoverme.info
  • Publishing a Firewall Policy – SMTP port 25 between DMZ and Internal should be allowed where in figure it is between hub transport server (netoverme-exc) and edge server (netoverme-edge). Also, this port should be allowed from edge server to external network for outbound (by creating a a firewall rule) and from external to edge server for inbound the tcp 25 port smtp traffic (this is done by publishing SMTP server).

Installing Exchange 2003

I think I better start to show you on installing exchange 2003 before I start to install Exchange 2007. For beginner, better start from MS Exchange server 2003 so that we know the differences on ways to install in different version of exchange.

As we know, Microsoft Exchange Server is a Email Server application. It provides convenient to send or receive email using our own domain, such as netoverme.info.

What we need in our network infrastructure before proceeding email application(exchange 2003)…? of course, our domain controller. Let’s say I have my own domain controller which is netoverme.info. Second, you would be like to need DNS Server. We can add our DNS server integrated with the domain controller.

Let’s say the exchange server is only a single server installed in my example. I would suggest that the Exchange server is installed on different server so that I would have headache to troubleshoot my network if the exchange server is installed in domain controller itself.

What do services and tools do I need to install Exchange Server 2003?

  1. I would suggest to use Windows Server 2003 SP2 or Windows Server 2003 R2
  2. The Server should be joined the domain into netoverme.info.
  3. Restart Computer and log on to the domain using Administrator or user that have member of schema and enterprise admin group.
  4. An Internet Information Services 6.0 is installed together with ASP.NET, WWW, SMTP and NNTP Service

Start Installing Exchange 2003

Put on your Exchange CD into CD-ROM. Let it run

Click on Exchange Deployment Tools

Click on Deploy the first Exchange Server 2003

you will be asked to do the eight steps. Please make sure you do the steps. the final step, you run the setup.exe

There are lot of information to be asked especially n the Component Selection after you click on setup. If there is a dash “—” on the action at the component selection, you have missed some steps. If the action says “typical”, you just click the “Next” Button. and proceed to create Ogranization. In organization wizard, I type “NETOVERME.INFO” as for my organization and click Next Button.

On Licensing Agreement, just click on I aggree that I read and will be bound by the licence agreements for this product.

Then, confirm the installation. There is a waning says that the domain would be unsafe… just click OK for proceeding the successful installation.