PowerShell (Default Web Site)

Glenn Maxwell 12,981 Reputation points
2025-08-20T05:06:48.2366667+00:00

I am currently running an Exchange 2019 hybrid environment, having just upgraded from Exchange 2016. I am monitoring my Exchange virtual directories through a third-party load balancer.

In Exchange 2016, to monitor the PowerShell (Default Web Site) virtual directory, I used the following health probe on the load balancer.

GET /PowerShell/healthcheck.htm HTTP/1.1

This worked as expected. However, in Exchange 2019, it is not working. Is there a different health probe for PowerShell in Exchange 2019? Please guide me.

Exchange | Exchange Server | Management
0 comments No comments
{count} votes

Accepted answer
  1. Hin-V 3,015 Reputation points Microsoft External Staff Moderator
    2025-08-20T10:09:04.2833333+00:00

    Hi @Glenn Maxwell

    Thank you for posting your question in Microsoft Q&A. 

    I have reviewed all relevant articles and references but found no specific information regarding changes to health probes in Exchange Server 2019. From my perspective, the healthcheck.htm probe might not work as expected due to architectural updates or the integration of Managed Availability.

    If possible, you could consider these workaround: 

    1. Using  the Exchange Management Shell (EMS) to check the health of various components: 

    This command may assist you in viewing a health set, which is a collection of monitors, probes, and responders associated with a specific component. Together, they determine whether the component is functioning in a healthy state.

    Run:

    Get-HealthReport -Server <ServerName> 
    

    References: Manage health sets and server health | Microsoft Learn 

    2.Using Health Checker: 

    This could collect useful information of your server to help speed up the process of common information gathering of your server. 

    You can refer via: HealthChecker - Microsoft - CSS-Exchange 

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link 

    You could give these workarounds a try and evaluate their output first. Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. 


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".      

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. User's image


1 additional answer

Sort by: Most helpful
  1. Andy David - MVP 158.7K Reputation points MVP Volunteer Moderator
    2025-08-20T11:38:55.9466667+00:00

    Ive never heard of anyone using a health checker on the powershell virtual directories.

    IMO, I would only worry about the ports listed here:

    https://learn.microsoft.com/en-us/exchange/architecture/client-access/load-balancing

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.