The ActiveDirectory attribute "HomeMTA" is actually no longer used by Exchange 2010, but an error message is still generated in the EventLog if the entry is not set correctly. Event 2937 usually occurs after a migration or after shutting down a mailbox server:
EventID: 2937
Source: MSExchange ADAccess
Process Microsoft.Exchange.RpcClientAccess.Service.exe (PID=10952). Object [CN=Zoechling\, Frank,OU=User,DC=frankysweb,DC=local]. Property [HomeMTA] is set to value [frankysweb.local/Configuration/Deleted Objects/Microsoft MTA
DEL:3f13df32-3d90-43ec-831f-3043434e72e7] and points to the "Deleted Items" container in Active Directory. This property must be corrected as soon as possible.
The responsible entry can be found in the attributes of the user account; there should actually be a valid entry for a mailbox server here:
The command "get-mailbox | update-recipient" has never worked for me, so I have created a script that corrects the entry for the HomeMTA attribute directly in the ActiveDirectory:
$alladusers = Get-ADUser -filter * -Properties homemta | select samaccountname,homemta | where {$_.HomeMTA -match "Deleted Objects"} foreach ($aduser in $alladusers) { $adusername = $aduser.samaccountname $database = (get-mailbox $adusername | select database).database $exserver = ((get-mailboxdatabase $database).ActivationPreference | where {$_.value -eq 1}).key.name [String]$newHomeMTA = "CN=Microsoft MTA," + (get-exchangeserver $exserver).DistinguishedName write-host "Edit user: $adusername`t`tHomeMTA: $exserver" set-aduser $adusername -replace @{homemta="$newHomeMTA"} }
The script can be executed in the Exchange Management Shell and the ActiveDirectory module for the Powershell must be loaded:
import-module activedirectory
The script then searches for all user accounts whose HomeMTA values refer to "Deleted objects" and sets the mailbox server as the HomeMTA, which also holds the first copy of the database.
Funktioniert das auch zuverlässig auf einem Exchange 2019? Habe nach einer Migration von 2013 und dem entfernen des alten Servers event id 5016 (msexchangetransport) und das scheint das gleiche Problem zu sein.