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

-

 

 

Send and Receive Connectors

Exchange Server 2003 uses SMTP virtual server interfaces for each protocol to send and receive messages between Exchange servers. Configuration is required only when you modify the default values or create connectors that are specific to another organization.

The Exchange 2010 Hub Transport servers use an implicit connector to route messages between sites. This connector is called the intra-organization Send connector. During installation, explicit Receive connectors are automatically created on each Hub Transport server. One Receive connector is configured to receive SMTP traffic from all sources by listening on port 25. A second Receive connector is configured to receive SMTP traffic from non-MAPI clients by listening on port 587. Explicit Send connectors and Receive connectors are created on Hub Transport servers only when you want to create a connector that sends messages to a specific address space or receives messages from a specific address range. For more information about connectors in Exchange 2010, see Understanding Send Connectors and Understanding Receive Connectors.

clip_image0014_thumb2

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. The information is transmitted as the Exch50 binary large object. Exch50 contains data such as spam confidence level, address rewriting information, and other MAPI properties that do not have MIME representation. Because X-EXCH50 is a proprietary Extended Simple Mail Transfer Protocol (ESMTP) verb, Exch50 data cannot be propagated by a non-Exchange server.

Exchange 2010 supports a mapping between MAPI and MIME and does not require Exch50 data to reliably transmit message properties. To correctly coexist with Exchange Server 2003, Exchange 2010 servers can propagate the Exch50 data to Exchange Server 2003 servers. On incoming SMTP connections, Exch50-related properties that are used by Exchange 2010 are promoted to Exchange 2010-equivalent properties. Properties that are not used by Exchange 2010 but are used by Exchange Server 2003 are preserved. On outgoing SMTP connections, the Exchange 2010 server can form the Exch50 data by promoting the Exchange 2010 properties and appending them to the preserved Exchange Server 2003 data.

Routing group connectors between Exchange 2010 and Exchange Server 2003 are automatically configured to support sending and receiving Exch50 data. If you are connecting Exchange 2010 to an Exchange Server 2003 server in a cross-forest scenario, make sure that the connector permissions allow the routing of Exch50 data. For more information, see Configuring Cross-Forest Connectors.

clip_image0015_thumb2 Message Tracking

The message tracking schema in Exchange 2010 is significantly different from the message tracking schema in Exchange Server 2003. The events that are logged by Exchange 2010 message tracking do not correspond directly to the message tracking events that are logged by Exchange Server 2003. Messages that are sent and received by Exchange 2010 can only be tracked by Exchange 2010 servers. There is no Microsoft Windows Management Instrumentation (WMI) support in Exchange 2010. Therefore, an Exchange Server 2003 server cannot query for message tracking logs on an Exchange 2010 server. If a message tracking query in Exchange 2010 indicates that the message was transferred to an Exchange Server 2003 server, you must use the Exchange Server 2003 message tracking tool to continue to search for the message.

clip_image0016_thumb2 Edge Transport Server Coexistence

The Edge Transport server role is designed to provide improved antivirus and anti-spam protection for the Exchange organization. The Edge Transport server also applies policies to messages in transport between organizations. This server role is deployed in the perimeter network and outside the Active Directory forest. The Edge Transport server can be deployed as a smart host and SMTP-relay server for an existing Exchange Server 2003 organization.

You can add an Edge Transport server to an existing Exchange organization without upgrading the internal Exchange servers or making any organizational changes. Because it deployed outside the Active Directory, you do not have to perform any Active Directory preparation steps when you install the Edge Transport server. If you are using the Exchange Intelligent Message Filter in Exchange Server 2003 to perform anti-spam tasks, you can use the Edge Transport server to provide an additional layer of anti-spam protection.

When an Edge Transport server is deployed to support an Exchange organization that has not yet deployed Exchange 2010, certain features cannot be used. You can't create an Edge Subscription in this scenario. Therefore, you cannot use the Recipient Lookup or Safelist aggregation features. For more information about using the Edge Transport server role with an Exchange 2003 organization, see Deploy an Edge Transport Server in an Existing Exchange Server 2003 Organization.


Blog Extended Reading

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

2. REF: Exchange 2010 - Upgrading from Exchange 2003 Transport (Part2)

 

More Information & Reference

1. Upgrading from Exchange 2003 Transport
2. EdgeSync and Send Connectors

Radiohead22_thumb53

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