Click here to monitor SSC
  • Av rating:
  • Total votes: 215
  • Total comments: 29
Jaap Wesselius

Upgrade Exchange 2003 to Exchange 2010

11 December 2009

 In this article, the first of  two in which Jaap describes how to move from Exchange Server 2003 straight to Exchange Server 2010, he shows what is required before moving mailboxes from Exchange Server 2003 to Exchange Server 2010. He shows how to upgrade Active Directory, install both Exchange Server 2010 and certificates, and set up the Public Folder replication. Jaap's second article in this series is here..

Microsoft released Exchange Server 2010 in October 2009, and this new version of Exchange Server contains a lot of  compelling new features such as the new High Availability, the facility to store your Exchange databases on JBOD (Just a Bunch of Disks), the archiving option and the new Outlook Web App. Oh, and do not forget the new Windows Mobile 6.5 and its new mail client.

If you have an Exchange Server 2003 environment you may want to skip Exchange Server 2007 and move directly to Exchange Server 2010. The easiest way to achieve this is to integrate Exchange Server 2010 into the existing Exchange Server 2003 environment, a so called intra-organizational migration. This is also known as transitioning from Exchange Server 2003 to Exchange Server 2010. But what does it take and what issues might arise?  This is part 1 of a series of two about moving from Exchange Server 2003 to Exchange Server 2010 and in this document I’ll show you what’s needed before you start moving mailboxes from Exchange Server 2003 to Exchange Server 2010.

Exchange Server 2003

Suppose we have a fictitious company called Inframan, which is a consulting company specializing in bridges, tunnels, buildings etc. Inframan has approximately 500 employees, 50 employees are working in the office, 450 employees are working ‘in the field’. Employees within the office have their own desktop which connects to an Exchange 2003 Mailbox Server using Outlook 2003 and Outlook 2007. Employees outside the office connect to the office using their company laptop with Outlook 2007 and Outlook Anywhere and with Windows Mobile devices. When needed they can use their PC at home to use Outlook Web Access to access their mailbox. Typical usage profile is “light”, approximately 25 messages are received per day and 10 messages are sent per day, per user that is. Behind the firewall is an ISA Server 2006 acting as a reverse proxy to publish all Exchange Services to the Internet. Inframan’s environment will look something like this:

Inframan is using only one namespace for accessing all services from the Internet: webmail.inframan.nl. This is used for Outlook Web Access, Outlook Anywhere and Windows Mobile devices.

Recently Inframan has been thinking about upgrading to Exchange Server 2007, but they decided to move directly to Exchange Server 2010.

Coexistence with Exchange Server 2010

Exchange Server 2010 can easily coexist in a Exchange Server 2003 organization as long as the Exchange Server 2010 prerequisites are met:

  • The Active Directory forest needs to be in Windows Server 2003 forest functionality mode;
  • All domains that contain Exchange recipients need to be in Windows Server 2003 domain native mode;
  • The Global Catalog Servers and the Active Directory Schema Master need to be at a minimum level of Windows Server 2003 SP1 (which equals to Windows Server 2003 R2);
  • The Exchange 2003 organization needs to be running in ‘native mode’;
  • Link State updates on all Exchange Server 2003 servers need to be disabled according to Microsoft knowledge base article 'Suppress Link State Updates'

Be careful when upgrading your Active Directory Domain Controllers since not all versions are supported to run with Exchange Server 2003. For a complete overview check the Microsoft Technet Site: http://technet.microsoft.com/en-us/library/ee338574.aspx.

Inframan will build two new Exchange Server 2010 servers, one combined Hub Transport Server / Client Access Server and one dedicated Mailbox Server. These Servers will be installed in the same Windows Server 2003 Active Directory domain as the Exchange Server 2003 organization. This will greatly improve the ease of moving mailbox from Exchange Server 2003 to Exchange Server 2010.

Moving from Exchange Server 2003 to Exchange Server 2010 in the same Active Directory forest is called transitioning. Building a new Active Directory forest with a new Exchange Server 2010 organization and moving mailboxes from the old Active Directory to the new Active Directory is called migrating.

The interim messaging environment, where both Exchange Server 2003 and Exchange Server 2010 coexist in the same Active Directory domain will look like this:

In Exchange Server 2007 Internet clients could connect to the Exchange Server 2007 Client Access Server while the mailbox was still on Exchange Server 2003. The Client Access Server retrieves the data out of the mailbox and sends it back to the Internet client. In Exchange Server 2010 this has changed. When a client connects to Exchange Server 2010, it actually connects to the Exchange Server 2010 Client Access Server and if the mailbox is still on the Exchange Server 2003 Mailbox Server then the client is redirected to the Exchange Server 2003 front-end server. This front-end server then handles the connection request. This automatically means the namespaces of the Exchange environment will change. For Inframan this means that the following namespaces are used:

  • https://webmail.inframan.nl – This is used by all Internet clients that connect to the Exchange environment. This name is not different than in the Exchange Server 2003 namespace, but it will now point to the Exchange Server 2010 Client Access Server;
  • https://autodiscover.inframan.nl – This is used by Outlook 2007 and (Outlook 2010) clients for autodiscover purposes;
  • https://legacy.inframan.nl – This will be the new namespace for the Exchange Server 2003 front-end server. This automatically means that the namespace for the Exchange Server 2003 front-end server is going to change!

The servers that will hold the Exchange Server 2010 server roles have the following prerequisites:

  • The servers need to be running on Windows Server 2008 or Windows Server 2008 R2;
  • .Net framework 3.5 with SP1 needs to be installed;
  • PowerShell 2.0 needs to be installed;
  • Office 2007 Filter packs needs to be installed for the Hub Transport Server role and the Mailbox Server role;

Make sure that after installing Windows on the servers that they are up-to-date with the latest hotfixes and service packs.

The first step for Exchange Server 2010 Server is to upgrade the Active Directory schema to contain the Exchange Server 2010 extensions. This is achieved by using the Exchange Server 2010 setup application followed by a number of parameter:

Setup.com /PrepareLegacyExchangePermissions – Exchange Server 2003 uses the Recipient Update Service to stamp the user with the appropriate Exchange attributes during provisioning. This is replaced in Exchange Server 2010 by E-Mail Address Policies. The /PrepareLegacyExchangePermissions parameter changes security settings so that both the Recipient Update Service and E-mail Address Policies can coexist in the same Active Directory;

Setup.com /PrepareSchema – This command upgrades the Active Directory schema to include the Exchange Server 2010 extensions. This can be checked by using ADSIEDit and checking the value of the UpperRange parameter of the  CN=ms-Exch-Schema-Version-Pt object in the Schema. This should have one of the following values:

Note that the value is the same in Exchange Server 2007 service pack 2 and in Exchange Server 2010 RTM – this is because Exchange Server 2007 service pack 2 will install the Exchange Server 2010 schema extensions.

Setup.com /PrepareAD – This command upgrades the Exchange organization, which is stored in the configuration partition in Active Directory to support Exchange Server 2010. In Exchange Server 2003 information is stored in the “First Administrative Group” or perhaps more if you created additional Administrative Groups. The Exchange Server 2010 setup application will create a new Administrative Group called “Exchange Administrative Group (FYDIBOHF23SPDLT)” where all Exchange Server 2010 configuration information is stored. This will be visible in the Exchange Server 2003 System Manager:

Setup.com /PrepareDomain – This is the last step in preparing the Active Directory and will create all necessary groups in the domain being prepared.

When Active Directory is fully prepared we can continue with installing the first Exchange Server 2010 server in the environment. For our example, this has to be the combined Hub Transport and Client Access Server. Start the graphical setup program (setup.exe) and download the Language File bundle if needed. If you select “install only languages from the DVD” only the language setting of your DVD (for example English or French) will be available. This is used not only for the language of the Exchange Server, but also the available language settings for the clients being used.

During the installation of the combined Hub Transport and Client Access Server a so called ‘custom setup’ will be used. This means we can select which server roles will be installed. In the Inframan example the following needs to be selected during setup:

When continuing the setup application a window will be shown asking if this Client Access Server is Internet facing and if so, what the external domain will be. This is an important step because it configures the Client Access Server automatically with the appropriate settings. Check the “The Client Access server will be Internet-facing” option and enter the external domain name. This is “webmail.inframan.nl” in our example.

Exchange Server 2003 uses Routing Groups to determine the proper way to route messages while Exchange Server 2010 uses Active Directory sites for routing. These are not compatible with each other so a legacy Routing Group Connector will be created within Exchange Server 2010. This legacy connector connects Exchange Server 2010 with Exchange Server 2003 so messages can be sent between the two Exchange versions. During setup of the first Hub Transport Server an Exchange Server 2003 Hub Server needs to be selected. This is the server the legacy Routing Group Connector will connect to:

Note that this choice can be changed and/or added to after setup is complete.

Now finish the setup wizard and install the Client Access and Hub Transport Server roles on this server.

It is also possible to use the command line setup application to setup the above mentioned configuration. Open a command prompt, navigate to the installation media and enter the following command:

Setup.com /mode:install /roles:ht,ca,mt /ExternalCASServerDomain:
webmail.inframan.nl /LegacyRoutingServer:2003FE.inframan.local

Mailbox Storage Design

Before installing the Exchange Server 2010 Mailbox Server role a proper storage design has to be made. Microsoft has recently released the new storage calculator, which is now called the “Exchange 2010 Mailbox Server Role Requirements Calculator” and can be downloaded here:

http://msexchangeteam.com/archive/2009/11/09/453117.aspx.

The Requirements Calculator needs to be used for a proper storage design. The following variables are used in the Requirements Calculator for our example:

The Requirements Calculator will show the following results:

An interesting part of Exchange Server 2010 is the database technology. Microsoft has made significant changes to the database structure to lower the disk performance requirements. It should be sufficient to run the Mailbox databases and its accompanying log files from SATA disks.

In the Requirements Calculator there’s the possibility to enter the disk configuration. For the new Inframan Mailbox server 7.200 RPM SATA disks with a capacity of 500 GB will be used for storing the databases and 7.200 RPM SATA disks with a capacity of 250GB will be used for storing the log files. This disk configuration is not exactly a high end configuration, but it is by far the most cost effective solution.

The Requirements Calculator contains a tab called “Storage Design”. When using the above mentioned values the Calculator recommends a RAID1/0 configuration with 6 SATA disks for storing the Mailbox Databases and a RAID1/0 configuration with 2 SATA disks for storing the Log Files.

Installing the Mailbox Server role

When the storage solution has been properly designed and implemented the Exchange Server 2010 Mailbox Server role can be installed. As with the Client Access and Hub Transport Server roles make sure you download the Language Pack during setup. Select a ‘custom setup’ and select only the Mailbox Server role when you get to the ‘Server Role selection’ window as shown in Figure 5. Finish the setup wizard and install the Mailbox Server role. After installation of the 2nd server the organization is ready to be configured and we can prepare for start moving mailboxes from Exchange Server 2003 to Exchange Server 2010.

Configuring the Exchange Server 2010 servers

When both Exchange servers are installed it is time to configure the Exchange environment properly before Exchange Server 2010 can be used and mailboxes can be moved. The following needs to be configured:

  • Relocate the Mailbox Databases on the new storage solution;
  • Unified Communications certificate on the Client Access Server;
  • New server certificate on the Exchange 2003 front-end server;
  • OWA 2010 needs to be configured for use with Exchange Server 2003;
  • Public Folder replication.
  • A send and receive connector also have to be configured, but I will describe this in the next article when the mail flow will be changed from Exchange Server 2003 to Exchange Server 2010.

Relocate the Mailbox Databases

On the new Mailbox Server there are two drives, from a hardware perspective configured as outlined before. These drives are F:\ for the Mailbox Databases and the Public Folder database and drive G:\ for the Log Files.

To change the location of the Mailbox Database open the Exchange Management Console and navigate to the Database Management, which can be found in the Organization Configuration. Right click the database and select “Move Database Path”. Change the Database file path to a directory on drive F:\ and change the Log folder path to a directory on drive G:\. Repeat this step for the Public Folder database.

If needed create new databases and locate the new database file on drive F:\ and the accompanying log files on driver G:\

Unified Communications Certificate

On the Exchange Server 2010 Client Access Server a new 3rd party Unified Communications certificate needs to be installed. According to Microsoft knowledge base article 929395 (http://support.microsoft.com/kb/929395) the following Certificate Authorities are supported for use with Unified Communications certificates:

However, most SSL Certificate Authorities can generate UC/SAN certificates that will work just fine. New in Exchange Server 2010 is the possibility to request certificates using the Exchange Management Console. Open the Exchange Management Console and select the Server Configuration in the navigation pane. Select the Exchange Server 2010 Client Access Server and create a new certificate request. For our environment we have to use the following domain names in our certificate:

  • Webmail.inframan.nl
  • Autodiscover.inframan.nl
  • Legacy.inframan.nl

During the coexistence phase Internet clients will connect to the Exchange Server 2010 Client Access Server while their mailbox is still on Exchange Server 2003. The client request will then be redirected to the old Exchange Server 2003 front-end server. This server will therefore get a new FQDN (Fully Qualified Domain Name) and thus need a new certificate. This new FQDN will be legacy.inframan.nl.

OWA Configuration

During installation of the Exchange Server 2010 Client Access Server all settings have been configured for use on the Internet. The only thing that needs to be configured is the coexistence information for Outlook Web App. The Client Access Server needs to be configured in case a mailbox is still on Exchange Server 2003 and the client needs to be redirected to the Exchange Server 2003 front-end server.

On an Exchange Server 2010 server enter the following Management Shell Command:

Set-OWAVirtualDirectory <CASHUB01>\OWA ‘
-ExternalURL https://webmail.inframan.nl/OWA ‘
-Exchange2003URL https://legacy.inframan.nl/exchange

This will make sure that when a user connects to Exchange Server 2010 Client Access Server for Outlook Web Access and the mailbox is still on Exchange 2003 the client will be redirected to the old Exchange Server 2003 front-end server.

Public Folder Replication

During installation of the Mailbox Server a new Exchange Server 2010 Mailbox Database will be automatically created. After installation you have to make sure that this database is moved from the default location to an alternate location for recovery and performance reasons.

A new Public Folder database will also be automatically created on the new Mailbox Server. The hierarchy, which is the structure of all Public Folders will be automatically replicated between all Public Folder Databases in the entire organization. The content replication of the Public Folders will have to be configured manually though.

To replicate the Offline Address Book and Free/Busy folders from Exchange Server 2003 to Exchange Server 2010 open the Exchange System Manager on the Exchange Server 2003 server and navigate to the System Folders in the ‘Folders’ folder in the First Administrative Group Navigate to the first Offline Address Book folder, right click it and select “All Tasks…”. The next is to select “Manage Settings”.

If you want to toggle between the System Folders and the normal Public Folders, navigate to the Public Folders, right click the Public Folders and select “View System Folders” or “View Public Folders”.

The “Manage Public Folder Settings wizard” will appear. Click Next on the Welcome page and select the “Modify lists of replica servers”. Follow the wizard and add the Exchange Server 2010 Mailbox Server role as a new replica. When finished, the folder and all its subfolders will be replicated to the Exchange Server 2010 Public Folder database. Repeat this step for the second Offline Address Book folder and the Schedule+ Free Busy folder.

Note: When the “Manage Settings” option is not available you can select “Properties” and select the replication tab to add the Exchange Server 2010 Public Folder Database.

Note: replication of public folders can take quite some time.

The (default) Public Folder that are located on the Exchange Server 2010 Mailbox Server should be replicated to the Exchange Server 2003 Mailbox Server. To accomplish this logon to the Exchange Server 2010 Mailbox Server, open the Exchange Management Console and navigate to the Tools node. Under the Tools node open the Public Folder Management Console.

Right click the Offline Address Book in the results pane, select Properties and click the Replication tab.

Add the Exchange Server 2003 Mailbox Server to the replica list, the contents will now be replicated to the Exchange Server 2003 Mailbox Server. Be aware that Public Folder replication is a low priority mechanism, so it takes some time before both Public Folder databases are in sync.

Repeat these steps for the Schedule+ Free/Busy folder.

Summary part I

In this first article out of a series of 2 I explained what steps are needed before you can start moving mailboxes from Exchange Server 2003 to Exchange Server 2010. In this article the Active Directory was upgraded, two servers with Exchange Server 2010 were installed, certificates were installed and the Public Folder replication was setup.

In the next article I will cover the actual movement of the mailboxes and the steps that are needed to decommission the Exchange 2003 servers like moving the Offline Address Book generation server and conversion of Recipient Policies and Address Books.

Jaap Wesselius

Author profile:

Jaap Wesselius is an independent consultant from The Netherlands focusing on (Microsoft) Business Productivity solutions. Prior to becoming an independent consultant, Jaap worked for 8 years for Microsoft Services in The Netherlands, specializing in Exchange Server. Jaap has a Bsc in Applied Physics & Computer Science, is an MCSE, MCITP and MCT, and has consistently been awarded the Microsoft MVP Award (Exchange Server, fifth year now) for his contributions to the Dutch Exchange community. For his Dutch blog posts, you can visit www.exchangelabs.nl. Besides Exchange Server, Jaap is also very active in virtualization and is a founder of the Dutch Hyper-V Community. If you'd like to get in touch, you can reach Jaap via email at Simple-Talk@jaapwesselius.nl, or on twitter as @jaapwess.

Search for other articles by Jaap Wesselius

Rate this article:   Avg rating: from a total of 215 votes.


Poor

OK

Good

Great

Must read
Have Your Say
Do you have an opinion on this article? Then add your comment below:
You must be logged in to post to this forum

Click here to log in.


Subject: GREAT SUMMARY!!
Posted by: Anonymous (not signed in)
Posted on: Wednesday, December 30, 2009 at 9:44 AM
Message: This is a beast of a project. Good to see someone has outlined the issues and made it clear. This should save anyone 6-10 hours of frustrating work if they have not migrated before. A++

Subject: Re: GREAT SUMMARY
Posted by: Jaap Wesselius (view profile)
Posted on: Saturday, January 02, 2010 at 8:22 AM
Message: thanks for your comments :-)

Subject: Nice article
Posted by: Anonymous (not signed in)
Posted on: Sunday, January 03, 2010 at 4:46 AM
Message: Jaap Wesselius ! your article rocks.you have kept is simple and nice.

Subject: Excellent Article
Posted by: Satish (view profile)
Posted on: Sunday, January 03, 2010 at 11:58 PM
Message: Eagerly waiting for 2nd part of this article.

i have few questions though. will the esm 2003 queue list the exchaneg 2010 queue correctly? i now have an error "Exchange System Manager failed to retrieve queues for the SMTP Virtual Server (error code = 0x800706D9). Check the event log and verify that the required services are running." listed in ESM.

ALso when i move the mailbox to exchange 2010 using local move request on ESM2010, i get "Warning: Failed to cleanup the source mailbox after the move.
Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)" for few mailbox.

also outlook clients 2000 and xp (not os, but office) are not connecting to exchange 2010. it just fails stating logon details are incorrect. the same username password on the same pc works fine when client is upgraded to outlook 2007 or 2010 beta.

are these expected behaviours?

Subject: A few observations.....
Posted by: zoobadger (view profile)
Posted on: Friday, January 15, 2010 at 1:40 PM
Message: Last night I installed Exchange 2010 successfully into my Exchange 2003 environment (one BE server, one FE server, 100GB message store, and 200+ users).

Rather than changing the namespace of my existing 2003 FE server, I created a new namespace for the Exchange 2010 server holding the client access and hub transport roles. So Webmail.zoobadger.org remains the hostname of my '03 FE server and mail.zoobadger.org is the hostname for my CAS 2010 server. If there's some drawback to this approach it's not apparent yet.

Also, if you're not managing your own external DNS, your DNS provider can create the autodiscover SRV record for you using the info below.

Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: mail.contoso.com

Next week, I'll start moving the mailboxes.

Subject: Solution to the Outlook XP and Outlook 2003 issue
Posted by: zoobadger (view profile)
Posted on: Friday, January 15, 2010 at 2:01 PM
Message: I got stuck on this as well. You need to either disable the encryption requirement on your client access server or you'll need to tell each Outlook client to use encryption. Here's a link.

http://support.microsoft.com/default.aspx/kb/2006508

Subject: OWA
Posted by: pxpx (view profile)
Posted on: Tuesday, February 02, 2010 at 2:42 PM
Message: Hi am having trouble typing in the OWA commands, what are the exact commands I need to enter in.

Set-OWAVirtualDirectory Exchange1\OWA
(After typing this command it complains it cant be found on the Domain Controller)

-ExternalURL https://webmail.mycompany.com/OWA ‘
-Exchange2003URL https://legacy.mycompany.com/exchange

Both of the (externalURL Commands do not even work what is the exact syntax)

Subject: public folder replicas management
Posted by: bonora.e (view profile)
Posted on: Wednesday, February 17, 2010 at 6:14 AM
Message: Hi,
I'm following this article and everyting is going well (exchange 2010 is working and all user mailboxes have been moved).
The only issue is with the public folders replication: what is the best tool for managing these folders: public folder management cosole (on the 2010 server) or system manager of exchange 2003?


thanks in advance

Subject: transition from exchange 2003 to exchange 2010
Posted by: Kevin ho (view profile)
Posted on: Wednesday, March 17, 2010 at 6:48 PM
Message: Hi everyone,

Please advise, I am about to write a plan to upgrade our exising exchange 2003 running on windows 2000 server so could anyone recommend me the important steps that I need to do before upgrade from 2003 exchange to exchange 2010.

Existing evinronment;

1. Active directory server is running on windows 2008 server and also running on 2000 native mode

2. Exchange 2003 is running on windows 2000 server Domain controller and also running on 2000 native mode

3. Blackberry server running on windows 2003 server, and running as member of server

4. Install a new exchange 2010 on windows 2008 domain controller and it is also running on 2000 native mode

My first question is should I upgrade my windows 2000 DC server which have exchange 2003 running on it to windows 2003 before I proceed with exchange transition? or it should be fine to proceed exchange upgrade cause the active directory is running on native 2000 mode and a new exchange 2010 is also running on 2000 native mode.

my second question is what will be happened to my blackberry server after i transition my 2003 to 2010 server, should I have do any thing with the black berry so people can keep receiving mail.

Many thanks if anyone can advise me the process that I should take.

Cheers
Kevin

Subject: Certificate confusion migrating from Exchange 2003 to 2007
Posted by: AvalonNYC (view profile)
Posted on: Thursday, March 18, 2010 at 6:54 AM
Message: I'm confused about getting the new certificates when keeping the same FQDN for the new server. I'm told by the CA (godaddy) that I can't request a UCC cert with common name of webmail.inframan.nl without invalidating my current SSL cert of the same name. At which point I have no cert at all, and nobody can get their mail. Or, if I request legacy.inframan.nl first, I can't install it on the 2003 server without taking off the other (webmail.inframan.nl) cert first. At which point nobody can get their mail because because of certificate mismatch.

And getting certs can take hours sometimes. How do we handle this so everyone is not down during all this?

Subject: Public Folder Replication
Posted by: pxpx (view profile)
Posted on: Tuesday, March 23, 2010 at 10:47 AM
Message: I am getting stuck on the Public Folder Replication. The part where you open ESM on the Exchange 2003 Server and drill down to your OAB --> Manage Settings --> Add new replica server. The only servers in the list are the Exchange 2003 Mail Server and Exchange 2003 WebServer, my new Exchange 2010 servers are not in the list. Please help!

Subject: Planing to upgrade my exchange2003 environment to exchange 2010
Posted by: Nikil (view profile)
Posted on: Monday, April 19, 2010 at 2:03 AM
Message: Hi

i have few concerns on this
1.after installing the exchange 2010,can we use both server for relay (independently for sending and receiving the emails)
2.how can we configure the two servers for fail over.

Subject: Thanks alot...
Posted by: navin_bvr (view profile)
Posted on: Monday, May 17, 2010 at 10:34 AM
Message: it was a simplest method i found on net..thanks alot

Subject: Exc Server 2010 in other site with Exc 2003 enviroment
Posted by: earevalo (view profile)
Posted on: Thursday, May 27, 2010 at 8:22 AM
Message: Hi.

I have an exchange 2003 organization at the Main Office and I want to deploy an Exchange 2010 topology (2 mailbox server and 1 hub transport/CAS) at the same 2003 organization but in different site. Is it possible?

What kind of integration Have I do at Exchange 2010 to send and receive email from Exchange 2003 mailbox users?

Thanks and regards

Subject: Great Post
Posted by: jblack (view profile)
Posted on: Saturday, June 26, 2010 at 8:53 PM
Message: This was a very informative article and will help in saving people a LOT of time during Exchange 2010 transitions.

Subject: Not Correctly detecting the exchange 2003 environment
Posted by: nelittle (view profile)
Posted on: Monday, July 12, 2010 at 11:04 AM
Message: Hello,
I'm in the process of following this article and am up to installing my HUB and Client Access roles. I'm stuck at the Mail Flow Settings step in that i'm not getting prompted (that option does not appear below installation type). Our exchange 2003 server is up and running and the new Exchange2010 server that i'm installing on is a member of the domain, is there some reason i'm missing as to why i'm not getting this part of the install?
The behavior appears to me that the 2010 server is not detecting that i'm already running a 2003 instance.
Any guidance you can provide would be greatly appreciated.

thanks,
Niall

Subject: Awesome
Posted by: rmuhammad (view profile)
Posted on: Tuesday, December 07, 2010 at 11:24 AM
Message: Just what I was looking for, thanks!

Subject: Back out plan
Posted by: liquidcourage1 (view profile)
Posted on: Monday, March 14, 2011 at 2:35 PM
Message: I understand the upgrade to an extent, but what is actually changing when the CAS role is installed? If we go step by step with the roles, can I back out after the CAS install by simply redirecting the DNS back to the legacy environment? For instance, users aren't authenticating against the CAS for some strange reason or ActiveSync isn't working.

Subject: Exchange 2010 Migration Plan : Overview
Posted by: migrationx.com (view profile)
Posted on: Monday, March 21, 2011 at 12:17 PM
Message: I found good link for exchange 2003 to 2010 migration

http://migrationx.com/2011/03/exchange-2010-migration-plan-overview/

Take a look

Subject: Re: Upgrade Exchange 2003 to Exchange 2010
Posted by: bikram_singhy (view profile)
Posted on: Wednesday, April 20, 2011 at 7:53 AM
Message: I am not able to see any summary or steps.....

am i missing something????


Subject: Question about Client Access Server external domain
Posted by: jdamone (view profile)
Posted on: Thursday, May 19, 2011 at 12:01 PM
Message: When you enter the namespace, is this the same name that current users are using to configure their smartphones, and outlook 2003 exchange accounts?

For us it would be the same name as out Exchange 2003 full computer name.

Will this cause any problems?

Subject: Question about Client Access Server external domain
Posted by: jdamone (view profile)
Posted on: Thursday, May 19, 2011 at 12:09 PM
Message: When you enter the namespace, is this the same name that current users are using to configure their smartphones, and outlook 2003 exchange accounts?

For us it would be the same name as out Exchange 2003 full computer name.

Will this cause any problems?

Subject: Do we need to have 2 ip addresses
Posted by: pandan22 (view profile)
Posted on: Monday, May 23, 2011 at 6:04 AM
Message: In this transition from 2003 to 2010 , do we also need to have 2 ip addresses since there are 2 servers concurrent ?.

Also the ssl certs for 2010 and 2003 , do they carry all the same names e.g. mail.company.com , legacy.company.com etc., ?

Please advise

Subject: Excelente Trabajo!!
Posted by: castiblancoalex (view profile)
Posted on: Tuesday, May 24, 2011 at 3:25 AM
Message: Jaap que buen articulo. Me ayudó mucho en mis clientes.

Subject: Functionality modes, are these the minimum or maximum requirements
Posted by: gregski (view profile)
Posted on: Monday, January 14, 2013 at 3:33 PM
Message: The Active Directory forest needs to be in Windows Server 2003 forest functionality mode;

All domains that contain Exchange recipients need to be in Windows Server 2003 domain native mode;

What if we are already on 2008 native? Can we still run Exchange 2010 and 2003 simultaneously?

Subject: Legacy host records
Posted by: ObiE (view profile)
Posted on: Monday, March 18, 2013 at 8:36 AM
Message: You need to configure legacy host records for this configuration to work right ?

Subject: active sync coexistence
Posted by: ObiE (view profile)
Posted on: Wednesday, March 27, 2013 at 2:40 AM
Message: For active sync coexistence change the external active sync url to the legacy url and instruct your exchange 2003 users to use the legacy url to connect to active sync.

Subject: Great Blog with Simple Steps
Posted by: adom503 (view profile)
Posted on: Tuesday, June 11, 2013 at 5:20 AM
Message: Here is a post that elaborates about exchange 2003 to 2010 migration: http://www.pcvita.com/exchange-2003-to-exchange-2010.html

Subject: Additional info plus a migration tool
Posted by: isiomir (view profile)
Posted on: Friday, June 14, 2013 at 2:10 AM
Message: Here's some more info on Exchange 2003 to exchange 2010 migrations. Nice migration tool has been launched recently:

http://www.codetwo.com/exchange-migration?sts=2946

 

Top Rated

PowerShell One-Liners: Variables, Parameters, Properties, and Objects
 PowerShell isn't a conventional language, though it draws inspiration widely. Many people learn it, and... Read more...

Migrating to Microsoft BPOS - Part II
 In his last article, Johan gave us a crystal clear guide to preparing to migrate from an on-premises... Read more...

Emulating the Exchange 2003 RUS for Out-of-Band Mailbox Provisioning in Exchange 2007
 Exchange's Recipient Update Service was important in Exchange 2000 or 2003 in order to complete the... Read more...

The Postmasters
 The Exchange Team introduces themselves, and keeps you up-to-date Read more...

For this Exchange Server Archiver, “Transparency” Fits
 Sometimes, it is a great relief when a user of your software gives it a tough test and then reports... Read more...

Most Viewed

Upgrade Exchange 2003 to Exchange 2010
  In this article, the first of two in which Jaap describes how to move from Exchange Server 2003... Read more...

Upgrade Exchange 2003 to Exchange 2010 - Part II
 In Jaap's second article on upgrading straight from Exchange Server 2003 to 2010, he explains how to... Read more...

Goodbye Exchange ExMerge, Hello Export-Mailbox
 ExMerge was a great way of exporting a mailbox to an Exchange PST file, or for removing all occurences... Read more...

Exchange E-mail Addresses and the Outlook Address Cache
 Because Exchange auto-complete cache uses X.500 addresses for e-mail sent to addresses within the... Read more...

Using Exchange 2007 for Resource Booking
 The process of booking various resources to go with a meeting room just got a whole lot easier with... Read more...

Why Join

Over 400,000 Microsoft professionals subscribe to the Simple-Talk technical journal. Join today, it's fast, simple, free and secure.