Ref: 從 Exchange 2007 Transport 升級

-

 

從 Exchange 2007 Transport 升級
1. Exchange 2010 和 Exchange 2007 Hub Transport Server 需有 Exchange 2007 SP2，才能在單一 Active Directory 站台共存

含有版本化路由的訊息流程

版本化路由工作流程


由 Exchange 2007 信箱使用者傳送給 Exchange 2010 收件者的所有郵件，都會依照類似的路徑。

在 SP2 中，已將建立版本路由新增至 Exchange 2007。您必須先將現有的 Exchange 2007 伺服器升級至 SP2，才能讓 Exchange 2010 和 Exchange 2007 在相同的 Active Directory 站台中共存。當您在相同的 Active Directory 站台中擁有 Exchange 2010 和 Exchange 2007 SP2，每一部 Hub Transport Server 便會以相符的版本，來處理信箱伺服器的郵件。建立版本路由不會變更站台內郵件的路由傳送方式。

當您在相同站台中擁有 Exchange 2010 和 Exchange 2007，請考量下列事項：

  • 您不能將不相容的 Hub Transport Server，指定為信箱伺服器的提交伺服器覆寫。
  • 若是特定的信箱伺服器，如果您在本機站台上沒有相符版本的 Hub Transport Server，則該信箱伺服器上的使用者送出的所有郵件，都會保留在信箱伺服器中。
  • 若是特定的信箱伺服器，如果您在本機站台上沒有相符版本的 Hub Transport Server，對於傳送給該信箱伺服器上使用者的所有郵件，會發佈未傳遞回報 (NDR)。
  • 傳送到已啟用郵件的公用資料夾郵件，其處理方式和郵件傳送到信箱相同。

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