I'm running exchange 2013 and it seems to have problems with health mailboxes (monitoring mailboxes). I have 5 mailbox databases on this server, DB1, DB2, DB3, DB4 and DB5.
I know there are 2 health mailboxes per mailbox database.
The command `Get-Mailbox -monitoring | Get-MailBoxStatistics` shows that several of these have not been accessed since December, even though they are in mounted Databases and powershell shows they are healthy.
There is also 2 health mailboxes that are missing from the below output because I got warninings saying these mailboxes have not been logged into yet.
-----
[PS] C:\windows\system32> Get-Mailbox -monitoring | Get-MailBoxStatistics
DisplayName : HealthMailbox98fb2dc7692341ad8a3325ea2b14bbcc
ItemCount : 17426
LastLogonTime : 12/8/2012 3:28:04 PM
Database : DB1
DisplayName : HealthMailboxe27d88df28ae4d53af620604a83aca4d
ItemCount : 12386
LastLogonTime : 2/4/2013 3:29:46 PM
Database : DB1
DisplayName : HealthMailbox815f0ff077a342f7889a53ef38e40256
ItemCount : 291
LastLogonTime : 12/8/2012 3:26:43 PM
Database : DB3
DisplayName : HealthMailboxbca2f3409f1d4ae99098f48b574fc36d
ItemCount : 579
LastLogonTime : 12/8/2012 3:26:05 PM
Database : DB2
DisplayName : HealthMailbox2412e1a0e5d9415b8328f653b2e42efe
ItemCount : 209
LastLogonTime : 2/3/2013 6:08:41 PM
Database : DB3
DisplayName : HealthMailbox594b739a129941e688eafee6bbdfece6
ItemCount : 209
LastLogonTime : 2/3/2013 6:09:52 PM
Database : DB2
DisplayName : HealthMailboxc401cae2a70d4d659f5758908582406e
ItemCount : 210
LastLogonTime : 2/4/2013 3:28:59 PM
Database : DB4
DisplayName : HealthMailbox4b81211d555c4accad1f61a98700382e
ItemCount : 212
LastLogonTime : 2/3/2013 6:09:46 PM
Database : DB5
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox2c62876ca1bb45849c0daf2ecee6d715`, so there is no data to return. After the user logs on, this warning will no longer appear.
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox4399c592609a464d95c993ecee46f671`, so there is no data to return. After the user logs on, this warning will no longer appear.
-----
I am also getting a lot of queued messages in the inboundproxy.com queue that have the subject line "Undelieverable: Inbound Proxy Probe". I dont know how to get these to stop. I just have to clean out the queue once a day to prevent it from getting to large.
The last thing I notice is that I get a lot of audit errors in the event log when the system is trying to login to these mailboxes. That might be what is causing the issue. Here is one of the messages:
-----
An account failed to log on.
Subject:
Security ID:SYSTEM
Account Name:<computer name here>$
Account Domain:<AD DOMAIN>
Logon ID:0x3E7
Logon Type:8
Account For Which Logon Failed:
Security ID:NULL SID
Account Name:HealthMailboxbca2f3409f1d4ae99098f48b574fc36d@<domain.tld>
Account Domain:
Failure Information:
Failure Reason:Unknown user name or bad password.
Status:0xC000006D
Sub Status:0xC0000064
Process Information:
Caller Process ID:0x1265c
Caller Process Name:C:\Windows\System32\inetsrv\w3wp.exe
Network Information:
Workstation Name:<computer name here>
Source Network Address:::1
Source Port:34602
Detailed Authentication Information:
Logon Process:Advapi
Authentication Package:Negotiate
Transited Services:-
Package Name (NTLM only):-
Key Length:0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
-----
As you can see, the system can not login to to this health mailbox account. The one in my example one of the mailboxes that has not been logged into since december.
Is there anywhere to troubleshoot these? or possibly rebuild them? The is a huge lack of documentation on these mailboxes from microsoft, I can not find any commands to interact with these other then 'get-mailbox -monitoring'