REF: Exchange 2010 - Upgrading from Exchange 2003 Transport (Part1)

-

 

1. Site to Site 間的HUB傳輸是透過 intra-organization Send connector to route

2. 承上，base on Active Directory site and IP site link

3. 混合模式下，AG及RG 會自動建立

4. E14 的AG & RG及成員不要亂動，更別透過ESM 來操作

 

Upgrading from Exchange 2003 Transport

[This is pre-release documentation and subject to change in future releases. This topic's current status is: Editing.]

Applies to: Exchange Server 2010 Topic Last Modified: 2009-08-19

When upgrading from Exchange 2003 to Exchange 2010, there will be a period of time where both versions coexist in production. This topic provides information to help you make sure that the message flow isn't negatively affected during this period of coexistence.

Important:

If you deploy Exchange 2010 as a new organization, you cannot later install Exchange 2003 in the Exchange 2010 organization. This is not a supported scenario. If you anticipate requiring Exchange 2003 functionality in your organization in the future, you must first install an Exchange 2003 organization and maintain at least one Exchange 2003 server.

Here is a brief overview of the issues discussed in this topic. Refer to each section for more details, including information about actions you may need to take:

  • Routing Topology Differences    
    When you plan for coexistence between Exchange 2010 and Exchange Server 2003, you must understand the differences in how each version determines its routing topology. This section provides an overview of the differences between the topologies, including a discussion of:
    • Routing group connectors
    • Link state updates in a coexistence environment
  • Send and Receive Connectors   
    Exchange Server 2003 uses SMTP virtual server interfaces for each protocol to send and receive messages between Exchange servers. The Exchange 2010 Hub Transport servers use an implicit connector called the intra-organization Send connector to route messages between sites.
  • X-EXCH50 Data   
    Exchange Server 2003 uses the proprietary verb X-EXCH50 to transmit information about messages and recipients that cannot be included in the e-mail message. Exchange 2010 supports a mapping between MAPI and MIME and does not require Exch50 data to reliably transmit message properties.
  • Message Tracking   
    Significant difference between the versions in that events logged by Exchange 2010 message tracking do not correspond directly to the message tracking events that are logged by Exchange Server 2003.
  • Edge Transport Server Coexistence   
    When an Edge Transport server is deployed to support an Exchange organization that has not yet deployed Exchange 2010, certain features cannot be used.

clip_image001

Routing Topology Differences

In Exchange 2010, an administrator doesn't have to define an Exchange-specific routing configuration. Exchange 2010 uses the existing Active Directory site topology to define its routing topology. However, an administrator can make Exchange-specific configuration changes to Active Directory sites and IP site link costs to control mail flow. E-mail that is routed to Exchange servers that are located in different sites must be relayed by Hub Transport servers. Hub Transport servers send e-mail to Hub Transport servers in remote sites by using the intra-organization Send connector. The intra-organization Send connector is an implicit connector that is computed by using Active Directory site and IP site link information. To learn more about how Exchange 2010 uses Active Directory sites to route messages, see Planning to Use Active Directory Sites for Routing Mail.

clip_image001[1] 

Routing Group Connectors

To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange Server 2003 as Exchange Routing Group (DWBGZMFD01QNBJR) within Exchange Administrative Group (FYDIBOHF23SPDLT).

During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, you must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead server that is located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all Exchange 2010 servers, regardless of the Active Directory site in which they reside.

clip_image002Caution:

Do not move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and do not rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use this routing group for communication with Exchange 2003.

The Hub Transport server that you are installing and the Exchange 2003 bridgehead that you select are configured as the source and target servers on two reciprocal routing group connectors. The selected bridgehead server is automatically added to the membership of the ExchangeLegacyInterop universal security group and is granted the permissions that are needed to send e-mail to and receive e-mail from Exchange 2010. This routing group connector creates a single connection point between Exchange 2003 and Exchange 2010.

You can modify the list of source and target servers by using the Set-RoutingGroupConnector cmdlet in the Exchange Management Shell. It is a best practice to specify more than one source server and more than one target server to provide redundancy and server availability.

clip_image002[1]Important:

Placing Exchange 2010 servers and Exchange 2003 servers in the same routing group is not supported.

Every Exchange 2003 routing group should have at least one connector to another routing group before you introduce the first Exchange 2010 server. Event ID 5006 is logged for each Microsoft Exchange Message Database (MDB) that is located in a routing group that does not have a routing group connector path from the Exchange 2010 routing group. For more information about the Exchange Server 2003 routing topology, see Exchange Server Transport and Routing Guide.

 

Important:

When you use the New-RoutingGroupConnector cmdlet, the specified legacy Exchange servers are automatically added to the membership of the ExchangeLegacyInterop universal security group and the permissions that are required to allow a legacy Exchange server to send mail to and receive mail from an Exchange 2010 Hub Transport server are automatically granted. If you use Exchange System Manager to create a routing group connector between the Exchange 2010 routing group and any Exchange 2003 routing group, this group membership is not updated and the connector will not work correctly. Therefore, always use the Shell to create or update routing group connectors between Exchange 2010 and Exchange 2003.

clip_image001[2]

Blog Extended Reading

1. Exchange 2010 – Suppress Link State Updates
2. REF: Exchange 2010 - 與多個E2K3 routing group 的連接方式
3. REF: Exchange 2010 - Upgrading from Exchange 2003 Transport (Part2)

4. REF: Exchange 2010 – Suppress Link State Updates


More Information & Reference

1. Upgrading from Exchange 2003 Transport

 

Radiohead22

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more