REF: Exchange 2010 – Suppress Link State Updates

-

 

如何抑制連結狀態更新

Applies to: Exchange Server 2010 Topic Last Modified: 2009-05-01

當 Exchange 組織中的電腦上安裝第一個 Hub Transport server role 時會建立第一個路由群組連接器。在建立其他路由群組連接器之前，請先在組織中的每個 Exchange 2000 和 Exchange 2003 伺服器上執行此程序。當您抑制少量連結狀態更新時，執行 Exchange 2000 和 Exchange 2003 的伺服器不會將連接器標示為關閉。此程序可確保舊版的 Exchange 只使用最低成本的路由，且不會嘗試計算替代路由。

此程序的目的是確保不會發生路由迴圈。Exchange 2007 不使用連結狀態路由表，也不支援轉送連結狀態資訊。如果不抑制少量連結狀態更新，則可能發生路由迴圈。如需在包含 Exchange 2007 伺服器和 Exchange 2003 或 Exchange 2000 伺服器的 Exchange 組織中如何發生路由迴圈的相關資訊


This topic explains how to use Registry Editor to suppress propagation of minor link state updates between routing groups in Microsoft Exchange Server 2010 and Exchange Server 2003.

We recommend that you perform this procedure if the following conditions are true:

  • You have installed the Exchange 2010 Hub Transport server role in an existing Exchange 2003 organization. For more information about this step, see Installing Exchange 2010 in an Existing Exchange 2003 Organization.
  • The existing Exchange organization includes more than one Exchange 2003 routing group.
  • You will configure more than one routing group connector between Exchange 2003 routing groups and Exchange 2010.

The first routing group connector is created when the first Hub Transport server role is installed on a computer in the Exchange organization. Before you create additional routing group connectors, perform this procedure on every Exchange 2003 server in the organization. When you suppress minor link state updates, the servers running Exchange 2003 don't mark connectors as unavailable. This procedure makes sure that earlier versions of Exchange only use least cost routing and don't try to calculate an alternative route.

The purpose of this procedure is to make sure that routing loops can't occur. Exchange 2010 doesn't use a link state routing table and doesn't support relay of link state information. If you don't suppress minor link state updates, routing loops may occur. For more information about how routing occurs in an Exchange organization that includes Exchange 2010 servers and Exchange 2003 servers, see Upgrading from Exchange 2003 Transport.

Caution:

Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

  Suppress Link State Updates on Exchange 2003

To perform this procedure, you must log on to the Exchange 2003 server by using an account that is delegated membership in the local Administrators group.

  1. Open Registry Editor.
  2. Locate HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters.
  3. Right-click Parameters and select New | DWORD value. Name the new DWORD value SuppressStateChanges.
  4. Double-click SuppressStateChanges.
  5. In the Value data field, enter 1.
  6. Close Registry Editor, and then restart the SMTP service, the Microsoft Exchange Routing Engine service, and the Microsoft Exchange MTA Stacks services for the change to take effect.

    image


Blog Extended Reading

1. Exchange 2010 - Upgrading from Exchange 2003 Transport
2. Exchange 2010 - 多個E2K3 Routing Group 與E14 的連接方式

More Information & Reference

1. Suppress Link State Updates


Radiohead22_thumb[5]

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