Wednesday, January 25, 2012

Migrating Exchange from HMC 4.5 to Exchange Server 2010 SP2 whitepaper

It contains a white paper and PowerShell scripts. Together they provide the recommended and supported migration path from HMC 4.5 to Exchange 2010 SP2. The steps in the guide may also be helpful when migrating from non-HMC environments that have configured some form of multi-tenancy.


Check out Migrating Exchange from HMC 4.5 to Exchange Server 2010 SP2

Thursday, January 12, 2012

EMC error: An error caused a change in the current set of domain controllers.

When opening Exchange Manangemnt Console you get the following error:
An error caused a change in the current set of domain controllers. It was running the command ‘Get-OrganizationConfig’.


In the application log you get the following error entries:

Event ID: 5

Source: MSExchange Configuration Cmdlet – Remote Mamagment

General: Task Get-ExchangeServer throwing terminating exception at stage Microsoft.Exchange.Data.Directory.ADTransientException: An error caused a change in the current set of domain controllers..

This happend to me after a domain controller was removed and replaces with a new one on the same site as the Exchange 2010 server.

To solve this problem close the EMC. Delete the file C:\Users\%username%\AppData\Roaming\Microsoft\MMC\Exchange Management Console. Open EMC again and you shold not get the error message again.



Monday, January 9, 2012

Upgrading Exchange Server 2010 SP1 to SP2


Microsoft released the second service pack for Microsoft Exchange Server, SP2.

for more information for SP2 click here. I am going to upgrade my lab to this latest service pack SP2.
Before I start, let me show you my current exchange server versions.
Exchange 2010 SP2, makes changes to Schema, checkout the Schema changes here.
There is a new pre-requisite for the CAS Server, which is the “IIS 6 WMI Capability”, you have to install this before you can install SP2.

Read about this pre-requisite here. You may also receive some warnings regarding RBAC, which detailed in the link given before.

You can install the pre-requisite by below commands:

Import-Module ServerManager

Add-WindowsFeature Web-WMI

Now, you can run setup.exe.

                                         Click on ‘Install Microsoft Exchange Server Upgrade’
                                        Click Next

                                            Accept the EULA, and click Next.

                                          Once the checks are complete, click Upgrade.

                                           Click Finish


If you want to do this in unattended mode, then you can run the following command:

Setup /Mode:Upgrade /InstallWindowsComponents

In real world, you have consider a lot before doing it straight forward like this, for example:

1. Get user downtime.

2. Stop Services

3. Move DAG members to another node, etc.,

I got this error, when running the upgrade on one of the server:

Entry DN: CN=Locale-ID,CN=Schema,CN=Configuration,DC=dinesh,DC=com

Add error on entry starting on line 128: Busy
The server side error is: 0x200e The directory service is busy.
The extended server error is:
0000200E: SvcErr: DSID-02080615, problem 5001 (BUSY), data -1102
An error has occurred in the program

It was the high CPU usage on the DC which caused this error, since I had very memory allocated to the VMs.
After clearing up some tasks , the memory dropped and I was able to successfully upgrade my servers to SP2.
Below is the screenshot after the upgrade, you can see that the server version is now changed to 14.2







Saturday, January 7, 2012

E2E Complete provides new levels of automation for upgrading to Exchange 2010, migrating to Office 365, and consolidating Exchange systems

For migrations from legacy Exchange to Exchange 2010 and Office 365, we have standardized on E2E Complete software from Binary Tree,” stated Ken Young, Microsoft Practice Director at Logicalis. “Logicalis has performed dozens of migrations to Microsoft Exchange 2010, including Office 365 and the utilization of E2E Complete has allowed us to reduce migration project timelines, increase migration accuracy and reduce project costs. The E2E Complete software has placed Logicalis many steps ahead of our competition and allows us to perform the migration effort for our customers at a lower cost than they can perform it themselves.

Read more: 
http://www.binarytree.com/Products/Migrate/E2E-Complete.aspx

Wednesday, January 4, 2012

Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-5

In this multi-part article, we will take a deep dive into how to transition between Exchange forests with different versions of Exchange deployed.



Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-1
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-2
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-3
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-4



9. Decommission


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:
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. 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=Almora, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=almora,DC=com”

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.

10. Reference

This blog series will be completed based on articles from this TechNet page
http://technet.microsoft.com/en-us/library/ff805040.aspx

Here is a nice little checklist that is done for this exercise
http://technet.microsoft.com/en-us/library/ee332309.aspx



Please post your comment so we can improve......

Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-4

In this multi-part article, we will take a deep dive into how to transition between Exchange forests with different versions of Exchange deployed.



Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-1
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-2
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-3
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-5



8. Bulk Movement


Move Mailboxes

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.
                                                   Select New Local Move Request

                                               Select target Exchange 2010 Database name
Now you can view the both mailbox Legacy and Moved mailbox in a single console


                                      After move mailbox you can clear move request

                                               

Move the Public Folder Hierarchy


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.

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.

                                               Select target PF database.
Now we will do some test and then uninstall Exchange 2003 from the environment.

First i created a mailbox in Exchange 2010

I was able to send / receive email from 2003.

I am also able to see free/busy info from both environments, since we replicated the free/busy PF.


Part-5




Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-3

In this multi-part article, we will take a deep dive into how to transition between Exchange forests with different versions of Exchange deployed.



Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-1
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-2
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-4
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-5



7  Pilot Phase


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.

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.


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

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.Almora.com
• Autodiscover.Almora.com
• Legacy.Almora.com

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.Almora.com.

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\OWA-ExternalURLhttps://webmail.Almora.com/OWA ‘
-Exchange2003URL https://legacy.Almora.com/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.

Offline Address Book

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.
                                                                 Click on Update

                                                   Select Exchange 2010 server “MX2010”

                                                                  Click on Move


                                       You can also check the Offline address book properties.

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:


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?

                                                                 You can use cmdlet

                                                      Setting the new Policy.

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.

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.Almora.com
• Autodiscover.Almora.com
• Legacy.Almora.com

When an OWA client logs on to the Exchange Server 2010 Client Access Server and the particular mailbox is still on Exchange Server 2003 the client gets redirected to the Exchange Server 2003 front-end server. This server will have the legacy. Almora.com name, since two servers cannot have the same Fully Qualified Domain Name (webmail.Almora.com).



Part-4















Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-2

In this multi-part article, we will take a deep dive into how to transition between Exchange forests with different versions of Exchange deployed.


Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-1
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-3
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-4
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-5



5. Assessment Planning


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.

https://webmail.almora.com – 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.almora.com – This is used by Outlook 2007 and (Outlook 2010) clients for autodiscover purposes;

https://legacy.almora.com – 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.

6. Build co-existence

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 upgrade 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 upgrade 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. In our example, this has to be the combined Hub Transport, Client Access Server and Mailbox Serve. Start the graphical setup program (setup.exe).

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.

Part-3





Tuesday, January 3, 2012

Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-1

In this multi-part article, we will take a deep dive into how to transition between Exchange forests with different versions of Exchange deployed.

Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-2
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-3
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-4
Transitioning from Exchange Server 2003 to Exchange Server 2010 Part-5



1. Introduction

Microsoft reached the RTM (Release to Manufacturing) milestone for Exchange Server 2010 on October 8, 2009, and it was officially launched on November 9, 2009. Exchange Server 2010 (currently at Service Pack 2) is available in two server editions; Standard edition and Enterprise edition. Microsoft Exchange Server 2010 and this new version of Exchange Server contain a lot of compelling new features such as the Flexible and reliable, anywhere access, Protection and compliance. Exchange 2010 including many changes to its core architecture new High Availability such as incremental deployment, mailbox database copies, and database availability groups work with other feature such as shadow redundancy and transport dumpster to provide a new, unified platform for high availability and site resilience.

June 2010, Microsoft released the public beta of Exchange Server 2010 Service Pack 1 with lot of improvement such as Archiving, control panel, core store functionality changes, Outlook Web App has been improved, and most important thing for Exchange admin Import and Export Mailboxes.

The newest update for Exchange 2010 Service Pack 2 release date 4th December 2011 with Hybrid Configuration Wizard, address book policy, Cross-Site Silent Redirection for Outlook Web App, Mini OWA and multi value custom attributes.

If we have an Exchange Server 2003 environment we 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.

2. Background

Exchange 2003 is slowly getting close to the end of its lifecycle (08-04-2014). Besides the end of mainstream support, there are other good reasons to switch to a newer Exchange version. In particular, Exchange 2010 offers many features that are just too good to be ignored. In addition to high scalability, the most welcome feature is the Database Availability Groups (DAG). It has never been easier to offer High Availability services for your users. But what about the migration to Exchange 2010; is it as simple as building a DAG?

The migration certainly is easier than what most administrators will expect. Microsoft also offers some nice guides, such as the Exchange Server Deployment Assistant. Though I strictly followed the guide, I encountered more than one problem. As problem solving can take quite some time, I decided to share my experience. This is by no means a complete migration guide or an alternative to the documentation available on TechNet or elsewhere. It is merely a supplement to the Exchange Server Deployment Assistant.

3. Current State

We have a fictitious company called Almora, which is a consulting company specializing in tourism. Almora has approximately 30000 employees, 25000 employees are working in the office, and 5000 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 15 messages are received per day and 10 messages are sent per day. Almora is using only one namespace for accessing all services from the Internet: webmail.almora.com. this is used for Outlook Web Access, Outlook Anywhere and Windows Mobile devices.

Recently Almora has been thinking about upgrading to Exchange Server 2010 directly.

Coexistence with Exchange Server 2010

Exchange Server 2010 can easily coexist in an 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'


4. Future State

Almora will build one new Exchange Server 2010 servers, combined Mailbox, Hub Transport Server / Client Access Server. This Server 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.

Part-2