Installing Message Header Analyzer (MHA) Addin on Exchange server.

In this blog, I will review the simple installation process of Message Header Analyzer (MHA) Addin for Outlook/OWA, on the Exchange server.

General

Message Header Analyzer is a very useful tool for Exchange administrators in order to analyze and review the mail flow process and to get more information about the email header like IP addresses of the components where the email was routed, scanning devices, and to check where the email was delayed.

Here is how it looks in Outlook:

And in OWA:

for more information about the Add-In, please visit the next link: https://appsource.microsoft.com/en-us/product/office/WA104005406?src=office&tab=Overview

Installing Message Header Analyzer.

The first step before installing MHA is downloading the XML file (Manifest.xml) from the next location: https://github.com/stephenegriffin/MHA/blob/master/Manifest.xml

1. After we have downloaded the file, we can install it on our Exchange servers.
   In order to do so, navigate to the Add-Ins section, under Organization at the ECP (Exchange Control Panel):

2. Click on the Plus sign + and choose Add from file:

3. Now select the location of Manifest.xml you have just downloaded, by clicking Browse, selecting the file and click Next.
in my example, its located under C:\Setup

Setting the Add-In access

After we installed the Add-In, it is disabled by default, therefore no user will be able to use it until we will change the setting:

To change the setting and make it available for part of the users by default or to give them the choice to install it, double click on the MHA Add-In:

• Optional, enabled by default:
  Use this setting if you want to allow your users to turn off the add-in.
• Optional, disabled by default:
  Use this setting if you want to allow your users to turn on the add-in.
• Mandatory, always enabled. Users can’t disable this add-in:
  Use this setting if you don’t want your users to turn off the add-in.

In case that has chosen the 3rd option, this Add-In will appear almost instantly on every Outlook and OWA, although there will cases where the user will have to close and reopen the Outlook in order to view the Add-In.

If you would like to allow access an Add-In only for specific users or groups, you have to verify first that the default App (Add-In) settings are still in place and set to Optional, disabled by default.

Now let’s get the Add-In Identity, in order to set it to the right user or groups.
To do so, run the next command and search for the MHA app:

Get-App -OrganizationApp | Format-List DisplayName,AppId,Enabled,DefaultStateForUser,ProvidedTo,UserList

After we have the AppID we can set it to a user or a group.

• In order to set the Add-In to a specific user (flow@msft.net), run the next command from Exchange PowerShell:

Set-App -Identity 62916641-fc48–44ae-a2a3–163811f1c945 -OrganizationApp -ProvidedTo SpecificUsers -UserList flow@msft.net -DefaultStateForUser Enabled

We can view that the setting of the MHA Add-In was changed, by checking the Add-Ins configuration at the ECP:

When the user will review his ECP configuration, he will be able to see that the Administrator has set this Add-In for him:

• In order to set the Add-In to a group (IT-GROUP), run the next 2 commands from Exchange PowerShell:

1. $MBR = Get-DistributionGroupMember IT-Group
2. Set-App -Identity 62916641-fc48–44ae-a2a3–163811f1c945 -OrganizationApp -ProvidedTo SpecificUsers -UserList $MBR.Identity -DefaultStateForUser Enabled

This Addin MUST has internet connectivity since there are many manifests and code parts that relay on other web servers which are located on the internet.

HTH :-)