Exchange 2007 Outlook MAPI Session超過連線數量或減少連線數量?

-

Exchange 2007/Outlook/MAPI 

 

Exchange 2007 Outlook MAPI Session超過連線數量或減少連線數量?


  

Question1

1. 超過MAPI Session 限制時的處理方式

clip_image008 

Question2

2. 相反的，若使用者想要限定MaxObjsPerMapiSession? (目前暫無解決方式)

如兩個Site 間的慢速專線有透過網路加速設備，可針對某些session 加速，但有限制如只能處理100個Session (不分protocol)。若有數個信箱透過此專線連線，可能兩三個信箱就將網路加速設備給占滿了，可以將Outlook 的MAPI Session 減少或限制嗎?

 

 

Question1

立即解決作法

1. 透過信箱搬移有問題的使用者 (中斷時間15-20mins ，影響範圍小)

2. 重啟IS Service (影響範圍大)

3. 用TCP View tool 中斷使用者的MAPI Session

http://www.calazan.com/exchange-2007-mapi-session-exceeded-the-maximum-of-32-objects-of-type-session/

4. 可參考Microsoft KB的做法去調整MAPI Session Limits

Event ID 9646 is logged in the application event log of your Exchange Server 2003 computer when a client opens many MAPI sessions

or

Exchange 2007 伺服器停止回應 MAPI 用戶端並在應用程式記錄檔中記錄事件識別碼 9646

 

Question2

5. 若使用者想要限定MaxObjsPerMapiSession ?

a. 架構上的考量，建議信箱區分，跨Site 的信箱存取需求量大，頻寬又小時，就可能需考慮在local site 建立Exchange Server

b. 存取方式考量，停用Outlook MAPI，改用其他存取方式，如OWA, POP3

How to Enable or Disable MAPI for a Mailbox User”

拒絕MAPI的連線

– 可使用Exchange管理主控台設定

– 使用Cmdlet

• Set-CASMailbox

– MAPIEnabled $true to allow

» Set-CASMailbox -Identity John -MAPIEnabled $true

– MAPIEnabled $false to block

» Set-CASMailbox -Identity John -MAPIEnabled $false

• 拒絕所有使用者的連線

– Get-Mailbox -Server E2K7Server1 | Set-CASMailbox –MAPIEnabled $false

 

. ....TBC

More Information

事件識別碼 9646 被記錄在應用程式事件日誌，Exchange Server 2003 電腦的用戶端開啟許多的 MAPI 工作階段時

Exchange 2007 伺服器停止回應 MAPI 用戶端並在應用程式記錄檔中記錄事件識別碼 9646

MAPI session limit disabled

Comments

Post a Comment

Popular posts from this blog

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 -Secti...
Read more

REF: Planning Exchange 2010 DAG - Part 1 - Network Requirements

-
Image
  Planning for High Availability and Site Resilience  - Network Requirements (a single MAPI network / one or more Replication networks ) In Exchange 2010, each DAG will have multiple networks: a single MAPI network , which is used by other Exchange 2010 servers to communicate with the Mailbox server in the DAG, and one or more Replication networks , which are used for log shipping and seeding within the DAG. It's important that the DAG networks are configured correctly. (two adapters/ MAPI network failover/ Replication network revert to MAPI Network/ ) Each member of the DAG must have at least two network adapters installed . This configuration provides you with one MAPI network and one Replication network, and the following recovery behaviors: In the event of a failure affecting the MAPI network, a server failover will occur (assuming there are healthy mailbox database copies that can be activated). In the event of a failure affectin...
Read more

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-179c7992...
Read more