Exchange Geek's Weblog

I'm a Geek!

Archive for the ‘Exchange Server 2003’ Category

Rapid transition guide from Exchange 2003 to Exchange 2010

Posted by Milind Naphade on 30/01/2010

Rapid transition guide from Exchange 2003 to Exchange 2010


I am glad to present this Rapid Transition Guide From Exchange 2003 to Exchange 2010.

This guide will walk you through the most important considerations and steps that you need to perform before, during, and after the deployment of Exchange 2010 server.

This guide is written for the IT administrators of an existing Exchange 2003 organization which contains small to medium scale deployments.

This guide mainly focuses on a typical transition of Exchange 2003 to Exchange 2010 environment which includes the transition of Exchange 2003 backend and front end servers to Exchange 2010 mailbox server role, client access server role and hub transport server role installed using the typical installation method.

You can download this transition guide from Here

I will appreciate your comments and feedback on this guide. Please feel free to drop me an email at geek @ msexchangegeek . com if you think this guide has some important content missing.

EDIT: There is a change in Exchange 2010 SP1 setup UI which allows you to install and configure Windows Server Features required for Exchange Server 2010 SP1 Server roles. Except those changes in the setup UI this guide remains same for the simplest transition scenario. In case you have further questions please feel free to write tome at geek @ or use the blog contact form.

Thanks to everyone for their valuable feedback. 🙂

Posted in Exchange 2010, Exchange Server, Exchange Server 2003 | 34 Comments »

Installing Exchange Server 2010 in Mixed Mode Environment – Part 2

Posted by Milind Naphade on 06/11/2009

In the first part of this post I described on how to prepare a your existing Exchange 2003 environment to run get it ready for the first Exchange 2010 server. In this post we I am going to talk about the installation part of the Exchange 2010 which is not very much difficult when you have your organization prepared and its schema extended for Exchange 2010.

Before even going to start installation of your Exchange 2010 server you still need to consider few things like; the support for legacy exchange clients like outlook 2003, and the legacy routing server which is supposed to be a bridgehead server in your exchange 2003 organization. Once you have made a decision about these things you can now proceed to installation. In my previous post I said it would be easier for your to go with GUI based installation but if you are planning to install support for legacy outlook clients you will need a public folder database which is not created by Exchange 2010 by default and you have to choose this manually. So, in this case I would prefer and also recommend going with a command line installer which is full of features (command line options) and can also be scripted if required. A notable thing here is if you really want to enable the legacy outlook support on an exchange 2010 server you must specify when you install the first Exchange 2010 server in the organization. By any chance if you have skipped this stage of defining this requirement you can create a public folder database manually and then replicate Free busy  public folders to this new database on your Exchange 2010 PF database.

So, are you prepared? If you think you are then lets start installing the first Exchange 2010 box in the org. I will do it both ways, the command way and the GUI. Due to restrictions of hardware resources I installed just a server with MBX, CAS and HT roles on it. So here is how I did it.

Command line (cmd.exe) from powershell on Windows 2008 R2 – /mode:Install /roles:CA,HT,MB /EnableLegacyOutlook / /


Above command line will install CAS, HT, and MBX roles on the box where it is going to enable the legacy outlook support by creating a public folder database on it. /LegacyRoutingServer refers to a bridgehead server in your existing Exchange 2003 organization. You can specify the FQDN of this server after the switch. /ExternalCASServerDomain will be the domain that will be pointing to your Exchange CAS server.

In GUI you get above mentioned options at following screens. Exchange 2010 RC GUI didn’t provide any option to specify the legacy outlook support though.


Now once you have selected these two very important options you can simply read through the GUI wizard and proceed with other steps and start installation.

Once the setup is completed open the EMC and notice the following things. You will see a public folder database generated during installation


and the domain name that you used for your CAS server:

Here is something interesting, if you ever asked yourself a question that why would exchange 2010 setup ask you to provide this information about the external domain name then the answer is below figure. Exchange setup will automatically use this name in the properties dialog box of the OWA website and you don’t need to configure it manually unless there are any changes in your domain name.


The next step is to verify the mail flow between legacy server and the newly installed Exchange 2010 as well as the OWA accessibility. In my current setup I have Administrator’s mailbox on legacy server and the Exchange Geek’s mailbox on Exchange 2010 server.



Once this is confirmed that both users can send and receive email to each other its time to configure something that can allow users to connect to their legacy mailboxes even after using the domain name. Exchange 2010 OWA will not open the legacy mailboxes for you yet it can help you with redirection to the legacy exchange OWA URL. To set this run

[PS] C:\>Set-OwaVirtualDirectory -Identity "owa (Default Web Site)" -Exchange2003Url


To perform this operation you must have SSL enabled on your Exchange 2003 OWA website as well as the form based authentication configured.Though the redirection will take place automatically on Exchange 2010 you must configure your ISA boxes or firewalls for this redirection.

In next part I will write about rest of the stuff about configuration like OAB and Free/Busy information and other. Till then do let me know if you find any kind of documentation bug or mistakes in the posted entries.



Posted in Exchange 2010, Exchange Server 2003 | 11 Comments »

Installing Exchange Server 2010 in Mixed Mode Environment – Part 1

Posted by Milind Naphade on 27/10/2009

Per the latest news from MS Exchange Team Exchange 2010 is out to manufacturing. With that said, it will be available for the production deployments very soon. In this series of posts I am covering the installation of Exchange 2010 in a mixed mode environment.

Though it can be installed with the legacy version of Exchange there are certain pre-requisites you must fulfil. In this post we are trying to uncover the installation method of Exchange 2010 in an existing Exchange 2003 Organization. So, even before you start installing Exchange 2010 you have to do some preparation on your Exchange 2003 side. Very important and must be understood fact about Exchange 2010 is it can not be installed with any other version of Exchange prior to Exchange Server 2003 SP2. So, if you have an Exchange 2000 Server and planning to transit to Exchange 2010 you must upgrade it to Exchange 2003 SP2 first. Following table illustrates the supportability of co-existence:

Version of Exchange Exchange Organization Co-Existence
Exchange 2000 Not Supported
Exchange 2003 Supported
Exchange 2007 Supported
Exchange 2003 and 2007 together Supported


Once you have understood the supportability of the Exchange 2010 setup and you think that you are good to go, you will have to work a little bit on your Exchange 2003 organization first of all. So, this work out will contain raising the AD DFL, AD FFL and Exchange 2003 org functional level.

1. The first step would be raise your AD Forest Functional Level and AD Domain Functional Level to Windows Server 2003 at least. After changing the DFL or FFL you may need to wait till the replication in your entire AD forest completes.

2. You must change your Exchange 2003 org to operate only in Native Mode. That means it simply discards the support to any Exchange 5.5 servers in your Exchange 2003 org. If you are still running Exchange 5.5 site with your Exchange 2003 it must be migrated over to Exchange 2003 and then decommissioned before changing your Exchange 2003 org mode. To change your Exchange 2003 org to native mode, right click on your Org Name in ESM and select Properties. The Org Properties dialog box appears. Click on the Change Mode button. You will be warned that this setting is irreversible.


3. Considering your AD health, replication and DNS are working absolutely fine you can now think of starting for Exchange 2010 preparation. So what we need here to install Exchange 2010 is either Windows Server 2008 SP2 or Windows Server 2008 R2 which is available only in 64 bit flavour and of course powerful enough hardware to install a 64 bit architecture OS on it. The minimum and recommended system requirements can be found at:,EXCHG.149).aspx

4. Assuming that you have already setup a Windows Server box installed Windows Server 2008 SP2 or Windows Server 2008 R2 on it, its time to configure it to install Exchange 2010 on it. Here, you might notice that Exchange 2010 will still support Windows Server 2008 but it must be installed with SP2. Exchange 2010 can support both of these operating system versions. Yet, the OS configuration part varies due to changes in architecture of both versions. Though the software component prerequisites remain the same on both versions they have their own ways to configure these components. Microsoft already has a publication on technet which talks about the ways to install these software prerequisites. They can be found at Exchange 2010 Prerequisites. It is highly recommended that you should run Windows Update before starting an install of Exchange 2010. Windows update will download all the latest updates for the software components.

Natively, Exchange 2010 will require following software installed on a Windows box:

1. .Net Framework 3.5 SP1 – Exchange code base is built on .Net Framework 3.5 where the Exchange 2007 had it built around 2.0 (Not required to be installed on Windows 2008 R2)

2. Windows Remote Management Tools 2.0 and Power shell V2 (Not required to be installed on Windows 2008 R2)

3. 2007 Office System Converter: Microsoft Filter Pack. (Required to be installed on the servers hosting mailbox server role or hub transport server role)

Apart from these additional software below is the list of required software components need to be installed:

5. As you already have an Exchange 2003 organization setup and running, its now time to setup your first Exchange 2010 server in co-existence. If you have already worked a Exchange 2007 setup you might have been knowing to run the legacy exchange permissions preparation. Yes, in Exchange 2010 you still need to run that switch with to prepare the legacy exchange permissions. There is a known issue detected when Exchange 2007 was a RTM release that the direct install of Exchange 2007 will break the RUS permissions on Exchange 2003. Which results into RUS not stamping email addresses on new Exchange objects. The detailed information is give at Preparing Legacy Exchange Permissions


6. Wait for replication to complete and then you can go ahead with another step of preparing the forest schema. Indeed that’s again similar to Exchange 2007 /PrepareSchema.


You can see the new schema objects being inserted into the Schema partition while the setup goes on or after its completion.

image 7. Once you are done with all above steps now its time to install Exchange Binaries which actually form a Windows Server 2008 box to an Exchange server. At this stage you can either chose to go with the GUI based installation or simply with the command prompt. GUI based installation is always simpler method to go with as it avoids confusions many times. I prefer using command like but for those who are not very comfortable with powershell or command line tools its a good practice to use GUI as far as possible.

Now, before you start installing make sure that you have met all the software component prerequisites on the exchange 2010 box. Again, you may refer the link Exchange 2010 Prerequisites

In the next part of this post I will explain on how to install and what to configure on Exchange 2010 side as there isn’t much that you have to modify in an existing Exchange 2003 server. So stay tuned and do post your comments and your opinion about this post.


 Related Posts:

Installing Exchange Server 2010 in Mixed Mode Environment – Part 2


Posted in Exchange 2010, Exchange Server 2003 | 2 Comments »

Using MFCMAPI to delete delegate rules from mailbox

Posted by Milind Naphade on 30/04/2009

Note: This post is purely intended to demonstrate the use of MFCMAPI to delete calendar delegate rules. There are several other steps you may want to go through before you actually go ahead and follow steps in this post.

Outlook, LDAP and MAPI offer a great feature of delegation of mailboxes to a particular user within the organization. It works almost the same way in all version of Exchange Server 200x family. I am not pretty sure about Exchange 2010 yet because never had a chance to look at it so closely.

Well, though the delegation feature is a great facility provided to end users it becomes a pain for administrators sometimes. One of the most annoying situations I always come across is when someone reports that he/she sent an email to some distribution list and then got an NDR that indicates that the email was not delivered to a user which has been deleted recently and does not work for the company anymore. and the NDR looks like:

From: System Administrator
Sent: Tuesday, April 28, 2009 10:06 AM
To: Geek, Exchange
Subject: Test Meeting Request

Your message did not reach some or all of the intended recipients.

Subject: Test Meeting Request
Sent: 4/28/2009 10:06 AM

The following recipient(s) could not be reached:

Geek, Exchange on 4/28/2009 10:06 AM
    The e-mail address could not be found. Perhaps the recipient moved to a different e-mail    organization, or there was a mistake in the address. Check the address and try again.
     <FQDN of my #5.1.7>

This type of NDR starts generating after you delete some user account from your organization and this user account was also a part of some DL and at the same time was delegated permissions on some other user’s mailbox in the same DL. Another case would be when you already know the delegated mailbox name however you are not able to fix the issue.

1. When you don’t know the name of the delegated mailbox yet you get the NDR:

Download the script at Glenn’s blog and run it in your Exchange Organization to find the user who had the deleted user account set as delegate or have a rule configured to forward emails. This script can be downloaded from (This script requires you having full mailbox access on all mailboxes in your organization)

Script shows all the delegate and forwarding rules in mailboxes. I will strongly recommend reading instructions at above link before you run it.

Once you get the name of desired mailbox you can certainly remove the rule either by logging on to the mailbox or by using MFCMAPI or mdbview32.exe. An alternate location to download it would be here.

2. When you know the delegated user account name but can not remove the rule using outlook:

Now, here you can use MFCMAPI to remove all those calendaring delegates and forward rules from a particular mailbox. Steps are below:

A. Open MFCMAPI.exe and logon to the store with Administrator privileges or with an user account which has full access to other mailboxes. To logon follow Session –> Logon and Display Store Table. This will show up the screen like below;

B. Right click on the mailbox you are logged on as and select Open Store from the context menu.


C. The next screen comes up which explore all visible and invisible folders in your mailbox.

D. Expand Root Container at the top of tree structure –> Expand Top of Information Store –>  right click on Inbox and select Display Rules Table


E. Another windows opens up and shows you the rules configured in the mailbox. Please note that only server side rules are displayed here.


F. This window may display several other rules as well. You have to find and select the rule which is provided by Schedule+ EMS Interface.

G. Right click on the rule and select to delete.

F. Any other rule can also be deleted using the similar method.

Posted in Exchange Server 2003, Exchange Server 2007, MBX | 3 Comments »