HealthChecker should validate IIS bindings for "All Unassigned" #2209
Labels
Enhancement
New feature or request
good first issue
Good for newcomers
Health Checker
P2
Triage
Needs to be discussed to determine how to handle
Milestone
Is your request related to a problem? Please describe.
Healthchecker should check if IIS bindings are correctly configured, especially on the backend website.
Binding should be "all unassigned" and not for a specific IP address.
Describe The Request
The correct default values on backend should be like this:
Exchange Back End Started False http - *:81: - NULL
https - *:444: - 69DE5CA602D04D03939DA4E2F5BE2D076609B906
Incorrect setting on backend:
Exchange Back End Started False http - *:81: - NULL
https - 192.168.10.48:444: - 69DE5CA602D04D03939DA4E2F5BE2D076609B906
This becomes important when extended protection is enabled. When it is, and the binding is set to a specific IP address of the server the backend will drop the connection with the well known SEC_E_BAD_BNDINGS error; 2148074310.
Additional context
Checked with Exchange Health Checker version 24.10.15.1910
The text was updated successfully, but these errors were encountered: