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'
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 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;
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
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:- Entrust - http://www.entrust.net/microsoft/
- Digicert - http://www.digicert.com/unified-communications-ssl-tls.htm
- Comodo - http://www.comodo.com/msexchange
- Webmail.inframan.nl
- Autodiscover.inframan.nl
- 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.-ExternalURL https://webmail.inframan.nl/OWA ‘
-Exchange2003URL https://legacy.inframan.nl/exchange
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.
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.
In my previous article I explained the initial steps that are needed when you want to upgrade an existing Exchange 2003 environment to Exchange Server 2010. The Active Directory was upgraded, the new namespace is planned, a combined CAS/HUB server installed as well as a Mailbox Server, including a storage design. The last step that was performed in the previous article was the Public Folder replication from Exchange Server 2003 to Exchange Server 2010.
In this article we will actually move the various services from Exchange Server 2003 to Exchange Server 2010 and fully decommission the Exchange Server 2003 servers.
Offline Address Book generation
Changing the Offline Address Book generation isn’t the most difficult part of a migration. Logon to the new Exchange 2010 Server and open the Exchange Management Console. In the navigation pane, navigate to the Organization Configuration and select the Mailbox option. In the results pane, select the Offline Address Book tab. Right here you’ll see that the ‘old’ 2003 Mailbox Server is the Offline Address Book generation server. Right click this server and select ‘Move…’. The Move Offline Address Book wizard will appear, use the Browse button to select the Exchange 2010 Mailbox Server Role as the new generation server. Click the Move button to finish the wizard. When finished click the Finish button.Address List conversion
Exchange Server 2010 uses E-mail Address Policies, just like Exchange Server 2007. And, as with Exchange Server 2007 these are not compatible with the Recipient Policies used in Exchange Server 2003. The next step is to convert the Recipient Policies to Exchange Server 2010 Email Address Policies.There’s no way to achieve this using the Exchange Management Console so we need the Exchange Management Shell. When you try to edit a Recipient Policy in Exchange Server 2010 Management Console it gives a clue on how to convert the Recipient Policies to E-mail Address Policies:
Figure 1. You cannot edit Exchange 2003 Recipient Policies in Exchange Server 2010
Besides the fact that you have to convert the Recipient Policies to
Email Address Policies there’s another very important aspect. Exchange
Server 2003 can use LDAP queries for Recipient Policies while Exchange
Server 2007 and Exchange Server 2010 use a new technique called OPATH
filtering for creating queries. The OPATH filtering syntax replaces the
LDAP filtering syntax. Using OPATH it is possible to create filters
directly in the Exchange Management Shell using the –RecipientFilter parameter.LDAP filters are supported in Exchange Server 2010, and they continue to work, but they only exist on objects that are migrated from Exchange Server 2003 or earlier.But if you want to edit LDAP filters they first need to be converted to OPATH filters. Microsoft has created a script that can convert your LDAP filters to OPATH filters. Check the Exchange team blog for more information: “Need help converting your LDAP filters to OPATH?
If you don’t use any LDAP filtering in your Recipient Policies you can convert the Recipient Policies directly to Email Address Policies.
The Set-EmailAddressPolicy cmdlet is needed for this.
Open the Exchange Management Shell and enter the following command:
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”}
This will show a list of Recipient Policies that are available in
your Exchange organization. We can use this output by piping it into the
Set-EmailAddressPolicy cmdlet:
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} |
Set-EmailAddressPolicy –IncludedRecipients AllRecipients
The Recipient Policies are now converted to Exchange Server 2010
Email Address Policies and you can open them in the Exchange Management
Console. Please note that the examples mentioned above are pretty simple
policies. If you have more complex policies please test this
thoroughly. If you have any Mailbox Manager policies, these have to be
removed.Set-EmailAddressPolicy –IncludedRecipients AllRecipients
Warning:
if you happen to do this on Recipient Policies that have (advanced) LDAP queries, all custom filters can be reset to "mailnickname=*" which can result significant email outages. You have to test all these changes in a dedicated lab environment to see how these changes will affect your Exchange environment!
The Address Lists need to be converted to Exchange Server 2010 as
well. To achieve this open an Exchange Management Shell and enter the
following commands:if you happen to do this on Recipient Policies that have (advanced) LDAP queries, all custom filters can be reset to "mailnickname=*" which can result significant email outages. You have to test all these changes in a dedicated lab environment to see how these changes will affect your Exchange environment!
Set-AddressList “All Users” –IncludedRecipients MailboxUsers
Set-AddressList “All Groups” –IncludedRecipients Mailgroups
Set-AddressList “All Contacts” –IncludedRecipients MailContacts
Set-AddressList “Public Folders” –RecipientFilter {RecipientType –eq “PublicFolder”}
Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact'
-or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group'
-or ObjectClass -eq 'publicFolder'))}
When finished you can open all Address Lists using the Exchange
Management Console and using the Exchange 2003 System Manager for
opening the Address Lists is no longer possible.Set-AddressList “All Groups” –IncludedRecipients Mailgroups
Set-AddressList “All Contacts” –IncludedRecipients MailContacts
Set-AddressList “Public Folders” –RecipientFilter {RecipientType –eq “PublicFolder”}
Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact'
-or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group'
-or ObjectClass -eq 'publicFolder'))}
For more detailed information regarding the upgrade of Recipient Policies and Address Lists check the following Microsoft website:
- http://technet.microsoft.com/en-us/library/cc164375.aspx
- http://msexchangeteam.com/archive/2007/03/12/436983.aspx
Mail flow settings
Before changing the actual SMTP mailflow we have to create a Send Connector first. This will allow the Hub Transport Server to send SMTP mail to the Internet directly. In the Exchange Management Console, navigate to the Organization Configuration and select the Hub Transport Server. In the Actions Pane select “New Send Connector…” and create a new SMTP connector to the Internet. Select * in the namespace (this will send all outbound messages go through this connector) and select the DNS or the Smarthost option, depending on your own situation.By default the Receive Connector on the Exchange 2010 Hub Transport Server will not allow any anonymous connections. To change this open the Exchange Management Console, navigate to the Server Configuration and select the Hub Transport Server in the Results Pane. Right Click the default Receive Connector and select its properties. Select the Permissions tab and check the “anonymous” option to enable SMTP anonymous access.
Figure 2. Enable Anonymous access on the Default Receive Connector
Now that everything is in place, we can start moving the messaging
services to Exchange Server 2010. Although there’s no hard requirement
to start with the mail flow I’m going to start here. In the original
configuration, mail from the Internet is delivered to the ISA 2006
Server and from there it is sent to the Exchange 2003 front-end server.
We’ll change the ISA Server configuration so that SMTP mail is delivered
to the Exchange Server 2010 Hub Transport Server. When a mailbox is
still on Exchange Server 2003 the message is sent across the Interop
Routing Group Connector from Exchange Server 2010 to Exchange Server
2003 where it is delivered to the intended Recipient. The Interop
Routing Group Connector was created during setup of the Hub Transport
Server as explained in the previous chapter. On the ISA 2006 Server open
the ISA Server Management Console and navigate to the Firewall Policy.
In the results pane select the SMTP rule and edit it so SMTP messages
are delivered to the new Exchange 2010 Hub Transport Server.Outbound SMTP traffic needs to be changed as well. In the original situation there was an SMTP connector from the Exchange Server 2003 Front-End Server towards the Internet. A new Send Connector on the Exchange Server 2010 Hub Transport Server needs to be created that will replace the old Exchange Server 2003 SMTP Connector.
Log on to the Exchange Server 2010 Hub Transport Server and open the Exchange Management Console. Navigate to the Organization Configuration and select the Hub Transport. In the Results Pane select the Send Connectors tab and select “New Send Connector” in the Actions Pane and follow the wizard to create a new Send Connector. In the Address Space windows select “*” as the address space to make sure all messages are routed through this connector. In the Network Settings window you have to select either to use DNS (the Hub Transport Server will send all messages to other hosts) or to use a smart host (the Hub Transport Server will forward all messages to this host which in turn will send it to all other hosts).
If the new Send Connector is working, the SMTP Connector on the Exchange Server 2003 Front-End Server can be removed. If removed, messages from Exchange Server 2003 mailboxes bound to the Internet go through the Interop Routing Group Connector to the Exchange Server 2010 Hub Transport Server and then through the Send Connector to the Internet.
Client Access Server
In the previous article regarding the upgrade from Exchange Server 2003 to Exchange Server 2010 I explained the different namespaces. On the Exchange Server 2010 Client Access Server there’s a certificate with the following names:- Webmail.inframan.nl
- Autodiscover.inframan.nl
- Legacy.inframan.nl
The new certificate on the Exchange Server 2010 Client Access Server can be exported and imported on the Exchange Server 2003 Front-End Server. This way an error message will not be shown when a client gets redirected to the Exchange Server 2003 Front-End Server.
Note. The certificate needs to be imported on the ISA 2006 Server as well.
Changing the ISA 2006 Server rules takes a bit more planning. Three new rules will be created:
- Exchange 2010 OWA rule;
- Exchange 2010 ActiveSync rule;
- Exchange 2010 Outlook Anywhere and Autodiscover rule;
For the ‘old’ Exchange 2003 legacy environment three rules have to be created on the ISA 2006 Server as well:
- Exchange 2003 OWA rule;
- Exchange 2003 ActiveSync rule;
- Exchange 2003 RPC over HTTP rule (this one can be combined with the previous rule however);
The Web Listener in ISA 2006 Server needs to be changed as well. Since a seamless experience for end-users is needed when the redirection occurs, the Single Sign-On option need to be enabled on the Web Listener.
Figure 3. Enable to single sign-on option for the coexistence phase
In the ISA Server Management Console open the properties of the Web
Listener and navigate to the SSO tab. Add the .inframan.nl in the SSO
domain, please note the leading dot.When you have configured the above options it’s time to apply all changes in the ISA Server. Enable the 2010 firewall rules, enable the legacy Exchange 2003 rules and disable the old Exchange 2003 rules. All clients are now connected to the Exchange Server 2010 Client Access Server and when needed the clients are redirected to the Exchange Server 2003 Front-End Server.
If you want more information regarding the Client Access Server in the coexistence phase you can read more, including step-by-step instructions on the Microsoft Exchange Product Team blogs:
- - ISA 2006 SP1 Configuration with Exchange 2010
- - Upgrading Exchange ActiveSync to Exchange 2010
- - Upgrading Outlook Web App to Exchange 2010
- - Transitioning Client Access to Exchange Server 2010
Move Mailboxes
Before moving the Mailboxes to Exchange 2010 new Mailbox Databases need to be created on the Exchange Server 2010 Mailbox Server. As calculated with the Storage Requirements Calculator (check Table 1 in the previous article) four databases are needed on the Exchange Server 2010 Mailbox Server. To create these open the Exchange Management Console and navigate to the Organization Configuration and select the Mailbox option. In the results pane select the Mailbox Database tab and in the Actions Pane select “New Mailbox Database…”. Create four new Mailbox Databases, named for example DB01 to DB04. Locate the Databases on drive F:\ and the accompanying log files on drive G:\. Moving mailboxes is the easiest part in transitioning from Exchange Server 2003 to Exchange Server 2010. The only thing you have to be aware of is the fact that you must initiate the move to Exchange Server 2010 from the Exchange Management Console (or Exchange Management Shell) and not from the Exchange 2003 System Manager.When you open the Exchange Management Console on the Exchange Server 2010 Mailbox Server and you navigate to the Mailbox option under Recipient Configuration you see a list of mailboxes in the results pane. In the Recipient Type Details column you can see what kind of mailboxes there are. The “Legacy Mailbox” is still an Exchange 2003 Mailbox; a “User Mailbox” is an Exchange Server 2010 Mailbox.
To move a mailbox right click the mailbox and select “New Local Move Request…”. In the wizard that shows up you’ll see the mailbox(es) that you selected. Click the Browse button to select a Mailbox Database you want the mailboxes to move to.
The following window is about corrupted messages and what the move mailbox should do when corrupted messages are found. By default the migration of the mailbox is skipped when corrupt messages are found. When moving from older Exchange versions, like Exchange 2003 it happens that for example old calendar items are corrupt, causing the Mailbox Move to fail. You can increase this number to for example 1,000 to continue moving Mailboxes.
A configuration summary is shown, and when you click the New button the move mailbox starts. After some time, the move mailbox will be finished and the mailbox is on the new Exchange Server 2010 Mailbox Server.
It is also possible to use the Exchange Management Shell for moving mailboxes. It is also possible to create custom scripts which may be useful for larger and more complex environments.
A sample command to move all legacy mailboxes (i.e. Exchange 2003 mailboxes) to Exchange Server 2010 would be:
Get-Mailbox –RecipientTypeDetails legacyMailbox | New-MoveRequest
–TargetDatabase DB01
–TargetDatabase DB01
Note: All Mailboxes will be spread across all four Mailbox Database that were created in the previous stop.
Figure 4. The New-Move-Request and the status of the Move-Requests
When all of them are finished you can remove the completed Move
Requests in the Exchange Management Console or in the Exchange
Management Shell by entering the following command:
Get-MoveRequest | Remove-MoveRequest
Remove Public Folder database
When all mailboxes are moved to the Exchange Server 2010 Mailbox Server it’s time to remove the Public Folder Database from Exchange Server 2003. Since this Public Folder Database contains a replica of the Public Folder data the replica has to be moved to another server, in this case the Exchange Server 2010 Mailbox Server.Logon to the Exchange Server 2003 server and open the Exchange System Manager. Navigate to the Exchange Server 2003 Mailbox Server, right click the Public Folder Database and select “Move All Replicas”. Select the Exchange Server 2010 Public Folder database in the drop down box and click OK.
A warning message is displayed that the Public Folder Replicas will be move to the other Public Folder Database and that this can take a considerable amount of time. I’ve seen situation where this took more than 24 hours to complete. Replication takes place using SMTP messages that are sent across the Interop Routing Group Connector to the Exchange Server 2010 Public Folder Database.
Figure 5. Moving the replica from Exchange Server 2003 to Exchange Server 2010
As can be seen in the warning message you can check the ‘Public
Folders Instances’ folder under the Public Folder database to see if
it’s empty. If it’s not and you want to delete the Public Folder
Database another warning message is displayed that the Database cannot
be deleted.
Figure 6. Deleting the Public Folder database is denied as long as there are Public Folders.
As can be seen in REF _Ref249414839 \h Figure 5 there are still
Public Folders in the Database, therefore the Database cannot be removed
and a warning message is displayed.When all Public Folders are moved out of the Exchange Server 2003 Public Folder Database, it can be removed. The Mailbox Database can be removed at this time as well.
Move the Public Folder Hierarchy
The Public Folder tree itself should also be moved to the new Exchange Server 2007 Public Folder database. Logon to the Exchange Server 2003 server and open the Exchange Service Manager. Expand the Administrative Groups and right click the “Exchange Administrative Group (FYDIBOHF23SPDLT)”, select “New” and select “Public Folders Container”.Then expand the old “First Administrative Group”, expand “Folders” and move the Public Folders tree to the Public Folders container you created in the previous step.
Remove the Interop Routing Group Connector
When the Public Folder Database and the Mailbox Database are removed, and you’ve double checked to ensure that no other clients are using the Exchange 2003 Front-End server as an SMTP relay, the Interop Routing Group Connector can be removed. This can only be done using the Exchange Management Shell on an Exchange Server 2010 server by using the following command:
Get-RoutingGroupConnector | Remove-RoutingGroupConnector
The Get-RoutingGroupConnector will return both Interop Routing
Group Connectors (one from Exchange Server 2003 to Exchange Server 2010
and the other one vice versa) and this output will be used as input for
the Remove-RoutingGroupConnector command.Please make sure that absolutely no messages are remaining to be sent across the Interop Routing Group Connector before deletion!
Remove the Exchange Servers
Now that all services are not needed anymore on Exchange 2003 it’s time to remove the Exchange 2003 Front-End Server from our Exchange organization. Please use the Add/Remove Programs option in the server’s control panel to remove Exchange Server 2003. I’ve seen it several times that customers just turn off their Exchange 2003 Servers and start wondering why their environment became that unstable!Please note that for uninstalling the Exchange 2003 Front-End Server you’ll need the installation media so keep this around.
The Recipient Update Service is the next to remove from the Exchange Server 2003 server. Open the Exchange System Manager and in the Recipients Container select the Recipients Update Service (domain). Right click this Recipient Update Service and select “Delete”. To remove the Enterprise Recipient Update Service it’s not possible to use the Exchange System Manager. To remove this you have to use ADSIEdit.
Open ADSIEdit and open the Configuration Container in Active Directory. Navigate to the
“CN=Recipient Update Services,CN=Address Lists
Container,CN=Inframan, CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=inframan,DC=local”
container. There you’ll find the Recipient Update Server (Enterprise) object. Right click this object and select “Delete”.The Exchange 2003 Mailbox Server is the last Exchange 2003 server and is ready to be removed. As with the Front-End server please remove it using the Add/Remove Programs option in the server’s control panel.
Note: When you check Active Directory
with ADSIEdit you’ll notice that the old Exchange Server 2003
Administrative Group is still present, although empty. Do not remove
this Administrative Group unless you’re absolutely sure there’s no
object in Active Directory referencing this Administrative Group in the
ExchangeLegacyDN attribute. For more information please check this
Microsoft knowledgebase article: http://support.microsoft.com/kb/945602 - Users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2007.
My personal opinion would be just to leave it there and not touch it. Nobody will see this Administrative Group and it will bother nothing else, so just don’t touch it.
My personal opinion would be just to leave it there and not touch it. Nobody will see this Administrative Group and it will bother nothing else, so just don’t touch it.
No comments:
Post a Comment