Comments on: Test-ExchangeServerHealth.ps1 Has Been Updated to V1.16

By: Manoj Kumar

Manoj Kumar — Wed, 09 Nov 2022 22:51:07 +0000

Hello Paul

Does this script for Exchange 2019 server as well?

Manoj

By: Lee

Lee — Wed, 28 Jul 2021 04:45:21 +0000

In reply to Bikerpete.

Recently, the script failed with this error as it can’t convert database value, please help

MAPI connectivity: Cannot process argument transformation on parameter ‘Database’. Cannot convert value “DB02” to type “Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter. Hashtable-to-Object conversion is not supported in restricted language or a Data section.”

By: Bikerpete

Bikerpete — Wed, 28 Oct 2020 14:19:41 +0000

For the non-english Exchange environment users:
If you receive errors at “Mail Flow Test”, you should do the test manually and check the value of the positive result.
Around line 1202 you will find
if ($testmailflowresult -eq “Erfolgreich” -or $testmailflowresult -eq $success)
As you see, it checks the value and on a German system, it is Erfolgreich (which means Success).

Keep up the great work,
Pete

By: ajnabig

ajnabig — Wed, 21 Oct 2020 07:02:43 +0000

In reply to Rhys Evans. Changing internal URL of PowerShell directory to server name resolved the issue.

By: Bob

Bob — Tue, 13 Oct 2020 08:33:45 +0000

This is the best script I have. It’s been great forever. Can you add secure mail options? My preferred SMTP mailer requires a username and password. I can’t work out how to add this myself to the script (apologies if it’s already there, but I couldn’t see it).

Thanks again.

By: Roger Eastman

Roger Eastman — Wed, 25 Mar 2020 13:46:19 +0000

In reply to Özer YÜMSEK. I have the same problem with Exchange 2016 CU 14. I have 2 severs and the server that runs the script reports fine but the other server shows Could not test service health for CS, HUB, MB and UM services. It is also vice versa the other direction. Is there something special the script is expecting for remote servers? I have been using your script on my Exchange 2010 servers with no problems for years. thx.

By: Muthu

Muthu — Wed, 11 Mar 2020 04:23:38 +0000

Thanks for sharing the script. The script is working perfectly.
But one of our exchange server’s mailflow result displaying result as failed while we using this script but actually the server do not have such issue.

Shall we know why the report is detecting such failure when the problem is not exist and how can we fixed it ?

Appreciate your response

By: Fred

Fred — Mon, 17 Jun 2019 08:43:37 +0000

Hi Paul, many thanks for this very useful health check script, just had a quick question regarding the exclusion file.
I have no issue listed servers that I want to exclude, however I have a challenge listing some databases to exclude, i.e I have some restore DBs which are unmounted and want to exclude them from a couple of servers but listing the database names don’t seem to work.
Could you advise what is the correct format to allow this to work.

Thanks, Fred

By: Duncan

Duncan — Tue, 19 Feb 2019 12:29:56 +0000

Hello Paul,

Since we have updated to Exchange 2016 CU11, we receive an error while the script is initializing.

WARNING: Cannot load Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.E2010 because of the following error: Unable to load DLL ‘dsaccessperf.dll’: The specified module could not be found. (Exception from HR
ESULT: 0x8007007E)

Best regards,

Duncan

By: Rhys Evans

Rhys Evans — Fri, 08 Feb 2019 17:34:38 +0000

In reply to Josh Houston.

Just to update this, I just had the same problem in a Exchange 2016 DAG environment and fixed it by doing the following:

Go to “https://mailserver.domain.com/ecp”
Click on Servers, Virtual Directories and look down the list for powershell.
both my servers had public IP as internal address.

So mine was “mail.domain.com” i changed it to “exch01.sub.domain.com” and “exch02.sub.domain.com”

Now the script runs fine and passes.