search

microsoft / CSS-Exchange

Exchange Server support tools and scripts
MIT License
1.21k stars 332 forks source link

[Issue] - HealthChecker documentation issue regarding HTML report #2053

Closed worldsdream closed 3 months ago

worldsdream commented 3 months ago

Provide Version Number Exchange Health Checker v24.03.12.1700

Describe the issue An error appears when opening the HTML report.

When you go to the page: https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/, you will see one of the commands:

PS C:> Get-ExchangeServer | ?{$_.AdminDisplayVersion -Match "^Version 15"} | .\HealthChecker.ps1; .\HealthChecker.ps1 -BuildHtmlServersReport; .\ExchangeAllServersReport.html

The above command always worked. But there has been a change where the report now adds a date behind it. So it's not generic "ExchangeAllServersReport.html".

Expected behavior The HTML report needs to open.

Script Output HTML Report Location: .\ExchangeAllServersReport-20240329084414.html .\ExchangeAllServersReport.html : The term '.\ExchangeAllServersReport.html' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:137

Additional context Change the command to a new one, where it will know what name is been given to the report, so it will open the correct report after it finishes.

lusassl-msft commented 3 months ago

Hi @worldsdream. You’re correct - the new html report contains a timestamp which is by design as we received multiple requests from customers to make the name unique. If you want to keep the old name, just run the script like this:

.\HealthChecker.ps1 -BuildHtmlServersReport -HtmlReportFile “ExchangeAllServersReport.html"

worldsdream commented 3 months ago

Hi @lusassl-msft

Thanks for the information you provided.

When you run the command (see screenshot below):

info

The error appears:

info2

So the command needs to change on that page, right?

PS: A unique name is better, that's correct! So I like the small change.

lusassl-msft commented 3 months ago

@worldsdream yep, you're correct. The documentation is wrong. I will update it to reflect the latest changes in HealthChecker. Thanks for pointing this out!