microsoft / microsoft/CSS-Exchange

[Issue] - Health Checker - Allow local VulnerabilityReport

Open
#2,499 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

By Design / No issue Health Checker Need Investigation
Dominant language
PowerShell
Stars
1.3k
Forks
395
Avg merge
14h 7m
Merged PRs (30d)
5

Description

Provide Version Number
26.02.03.2007

Describe the issue
-VulnerabilityReport alway swants to scan all exchange servers, which fails if the account only has local rights.

Expected behavior
Would be nice to be able to just scan the local server / to add -Server also for -VulnerabilityReport

Script Output
PS C:\Program Files\MSHealthchecker> .\HealthChecker.ps1 -VulnerabilityReport -XMLDirectoryPath "."
Exchange Health Checker version 26.02.03.2007
WARNING: Failed to connect to the following servers: server2, server3, server4. Please run locally.
WARNING: Unable to continue as you must run the script locally on the required server(s) as we aren't able to connect
remotely from here.

There appears to have been some errors in the script. To assist with debugging of the script, please send the HealthChecker-Debug_*.txt, HealthChecker-ScriptDebugObject.xml, and .xml file to ExToolsFeedback@microsoft.com.
Please include in the subject of the email with 'HealthChecker-73d2b0fe-68f5-4a79-9490-137a98dd3806' to avoid duplicate email subjects being sent to us.
Script Debug Object Path: .\HealthChecker-ScriptDebugObject.xml
Output Debug file written to .\HealthChecker-Debug_20260210120456.txt
Do you like the script? Visit https://aka.ms/HC-Feedback to rate it and to provide feedback.

Unable to connect remotely to server(s)
In C:\Program Files\MSHealthchecker\HealthChecker.ps1:11256 Zeichen:17

  •             throw "Unable to connect remotely to server(s)"
    
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : OperationStopped: (Unable to connect remotely to server(s):String) [], RuntimeException
    • FullyQualifiedErrorId : Unable to connect remotely to server(s)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in HealthChecker.ps1 around line 11256 and trace the -VulnerabilityReport path that attempts to connect to every Exchange server. Check how the existing command parameters select servers, then define completion as allowing a local or explicitly selected server without requiring remote access to other servers; validate with the reported command scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
security, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.