Shulou(Shulou.com)06/02 Report--

1. What is a surveillance mailbox?

Exchange Server 2013 introduces a new feature called administrative availability, which is a built-in monitoring system with self-healing capabilities. Managed availability can be used to simulate continuous tests of end-user actions to detect possible problems with Exchange components or their dependencies. If the test fails, it performs a gradual simple recovery operation to keep the affected components in a healthy state. It uses special types of mailboxes (called monitoring mailboxes or health mailboxes) to simulate various tests for end users.

The life cycle of monitoring mailboxes is completed entirely by managed availability components.

two。 Monitor mailbox:

The ability to manage availability is implemented by the Microsoft Exchange Health Manager service that runs on each Exchange Server 2013 role.

The Microsoft Exchange Health Manager service is responsible for creating and maintaining monitoring mailboxes

Let's take a look at how Health Manager creates them!

3. How to create a monitoring mailbox:

The MSExchange Health Manager service runs in two processes, MSExchangeHMHost.exe and MSExchangeHMWorker.exe.

The HM worker process checks the availability of the monitoring mailbox at startup and creates the monitoring mailbox as needed.

Starting with Exchange Server 2013 CU1, an account to monitor mailboxes will be created under the following container where the domain Exchange server resides:

\ Microsoft Exchange system object\ Monitoring mailbox

The logic used by the HM worker process to detect and create monitoring mailboxes depends on the cumulative update version (CU) of Exchange installed.

The following logic applies to Exchange Server 2013 servers between RTM and cumulative update CU5 to create monitoring mailboxes:

Each mailbox database copy has one monitoring mailbox and one monitoring mailbox for all CAS servers.

The following is an example of monitoring mailboxes created on an Exchange Server 2013 SP1 server that hosts CAS and mailbox roles:

[PS] C:\ > Get-Mailbox-Monitoring | ft displayname,whencreated

DisplayName WhenCreated

HealthMailbox b285a119be6649b3a89574f078e947f5 11 games2014 9:07:29 AM HealthMailbox 60d8a8d1285e41bfa5ce1ef1fb93d14e 11 games2014 9: 07:36

The display name of the monitoring mailbox created by the database, including the GUID of the mailbox database.

The display name of the monitoring mailbox created by the CAS server, including the GUID for its Exchange server.

The following logic is used to create monitoring mailboxes for Exchange Server 2013 cumulative updates CU6 and later:

Each mailbox database on the mailbox role has one monitoring mailbox, and each CAS server has ten monitoring mailboxes.

The following naming convention is used for the display name of the monitoring mailbox created for the database:

"HealthMailbox-" + hostname of the server + "-" + database name.

At startup, the HM process checks the name of the database that exists on the server, and then checks for the existence of a monitoring mailbox with a display name, as described above. If a monitoring mailbox for a specific database cannot be found, a new monitoring mailbox is created. This means that renaming DB1 to DB2,HM worker will create a new monitoring mailbox for DB2 the next time you start.

The following naming convention is used for the display name of the monitoring mailbox created for the CAS server:

"HealthMailbox-" + hostname of the CAS server + "- 001" to" 010".

For example, if we have only one Exchange server (named EXCH1) running Exchange 2013 CU6 or later that hosts both the CAS and mailbox roles, and there is only one mailbox database, 11 monitoring mailboxes will be created.

4. Password reset

The HM worker process is responsible for maintaining passwords for Monitoring mailboxes. The HM worker process uses complex algorithms to generate passwords for monitoring mailboxes.

The password for monitoring mailboxes is reset under the following conditions:

Creating a new health mailbox

Each time the HM worker process starts and cannot retrieve the existing password for the monitoring mailbox

Any other scenario where the HM worker process cannot obtain the existing password of the monitoring mailbox

5. Best practic

Here are some best practices for managing user accounts associated with monitoring mailboxes and the mailboxes themselves:

Do not apply third-party custom password policies to user accounts for monitoring mailboxes excluding monitoring mailboxes from the user account lockout policy do not remove user accounts from the Monitoring Mailboxes container do not change user account properties, such as restricting password changes. Do not change AD permission inheritance do not move monitoring mailboxes between mailbox databases do not apply mailbox quotas to monitoring mailboxes if you apply a retention policy, make sure that the data in the monitoring mailbox is retained for at least 30 days before deletion

If you see a significant increase in the mailbox size of a specific monitoring mailbox; you only need to disable the specific mailbox. The HM worker process will create a new mailbox the next time it starts. 6. Common tasks for monitoring mailboxes

How to list monitoring mailboxes

The Get-Mailbox command provides a special parameter "- Monitoring" to list only monitored mailboxes.

For example:

List all monitoring mailboxes that exist in the organization:

Get-Mailbox-Monitoring

List the monitoring mailboxes that exist in the database:

Get-Mailbox-Monitoring-Database

However, the mailboxes listed above may be independent of the server of the corresponding database. As described in the creation logic, the name of the client access server or mailbox database is important for searching the associated monitoring mailbox and creating the monitoring mailbox.

Use the following command to list the monitoring mailboxes associated with a specific server:

Get-Mailbox-Monitoring |? {$_ .DisplayName-like "- -"}

Example:

Get-Mailbox-Monitoring |? {$_ .DisplayName-like "- exch3-"} | ft name,displayname,database

Use the following command to list the monitoring mailboxes associated with a specific database:

Get-Mailbox-Monitoring |? {$_ .DisplayName-like "* -"}

Example:

Get-Mailbox-Monitoring |? {$_ .DisplayName-like "*-db2exch3"} | ft name,displayname,database,servername

7. Fault troubleshooting

Here are some troubleshooting methods for monitoring mailboxes.

How to recreate the monitoring mailbox (do not consider regular maintenance! )

Mailbox database deletion does not clear the AD user account associated with the monitoring mailbox. This may result in separate AD user accounts. This occurs because you are monitoring inherited deny permissions on the mailbox container.

If there are too many separate monitoring mailbox accounts, you may need to recreate them.

Steps:

1) make sure there is a "Monitoring Mailbox" container

Turn on Active Directory users and computers

Click View and select Advanced Features

Browse to the Microsoft Exchange system object

Verify that the "Monitoring Mailboxes" container exists.

Example:

If the Monitoring Mailboxes container is missing:

Make sure that Exchange Server 2013 CU1 or later is installed.

Execute PrepareAD with version 2013 of Exchange Server installed to re-extend the schema.

2) stop the "Microsoft Exchange Server Health Manager" service on all Exchange Server 2013 servers.

3) Open the Exchange Management Shell and disable the existing healthy mailbox using the following command:

Get-Mailbox-Monitoring | Disable-Mailbox

4) return to Active Directory users and computers, right-click the domain and search for "HealthMailbox"

5) Delete the healthy mailbox user account.

6) wait for AD replication or force AD replication.

7) start "Microsoft Exchange Server Health Manager" on all Exchange Server 2013 servers.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.