Overview of Exchange Troubleshooting steps

I. Narrowing the scope of the problem
1. How many users are affected
2. Whether all affected users use the same method to access Exchange
3. What users want to do
4. Other users performing the same task is normal
5. Are all users in a database?
6. Are they on the same site?
7. What time occurs and how often the fault occurs

Second, the use of basic barrier tools
1. No matter what happens, first look at Event Viewer
2. Using the test command
{For example: 1. Get test command: Help test-*
All commands that start with test

                  2.get-servercomponentstate                      获取服务器组件状态                  3.test-servicehealth                     查看服务运行状态，此命令会根据CAS或者MAILBOX服务器自动  进行相应服务筛选。                   4.test-mapiconnectivity                      测试客户端连接到优先服务器时所使用的两个关键协议：MAPI\LDAP。并且会间接确认MAPI服务器、exchange存储、目录服务访问DSaccess是否正在工作。                    5.test-replicationhealth                       检查复制服务运行状态并提示发现的错误。                     6.Get-MailboxDatabaseCopyStatus                        验证复制服务后（第5个命令），可以使用Get-MailboxDatabaseCopyStatus检查数据库本身的复制状态。

Get-mailboxdatabasecopystatus | FL name,status,contentindexstate
Contentindexstate is the index state, ensuring that the healthy state is maintained.

                      7.邮件流测试 test-mailflow                         测试邮件的提交、传输、发送。验证服务器是否可以成功的向自身发送邮件。后面可以跟targetmailboxserver \targetdatabase \targetemailaddress参数。如果部署了DAG直接使用targetdatabase参数   }

Third, solve the mailbox server problem
1. Database replication Health is healthy
2. Server performance is limited
3. E-mail delivery is normal
4. Ensure all services are running properly
5. Are there any errors related to Msexchangedatbase, msexchnangedatabase instances, msexchangesubmission in the log.
6. Are there Active Directory issues
7. Test with the test-mapiconnectivity command
This command does not test the Exchange storage service and also tests AD access, rpcoverhttp access.
8. Whether it is quarantined (poison mailbox)
Poison Mailbox Concept: By default, the mailbox server marks any mailbox that causes a thread in the Store.exe service to crash or to connect to five or more "pending" threads. If a mailbox is flagged three times within two hours, Exchange Server 2013 will block access to the mailbox for up to six hours or until the administrator is unblocked, whichever is first. If the user reports that she cannot connect to the mailbox, but other users are not experiencing any problems, check the server for quarantined mailboxes.
command to use: Get-mailboxstatistics | FL isquarantined
If the isquarantined parameter is $ True, the quarantined state.
9.test-replicationhealth
Check the Replication service health status and prompt for problems found

Iv. Resolving mail transmission problems
1. Address the message transmission problem focus
1.1 Can I send all e-mails or only a subset of users
1.2 If I receive a return letter, is there any code
1.3 Whether in the unified organization
1.4 Message Delivery Distance
1.5 message path between sender and recipient
2. Consider whether the following issues exist
2.1 DNS failure could not find a record
2.2 Site link Error The site link does not exist between the sender and the recipient
2.3 Transport limits whether the mailbox is full
2.4 Transport Rules
2.5 messages stuck in Message Queuing
2.6 Reverse voltage situation on the server (back pressure concept Reference blog post)

     3.TEST-MAILFLOW     4.队列查看器、     5.邮件追踪        5.1 自主邮件跟踪报告              OWA-选项-送达报告 （只能跟踪自己的邮件）                    5.2 EXCHANGE管理中心邮件跟踪                          EAC-邮件流-送达报告  （最总所有用户邮件）                    5.3 GET-MESSAGETRACKINGLOG

Overview of Exchange Troubleshooting steps