Wednesday, January 4, 2012

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





No comments:

Post a Comment