microsoft / microsoft/CSS-Exchange
[Feature Request] add some sanity checking for OAB virtual directory configuration in HealthChecker.ps1
@dpaulson45 is already working on this.
Since Dec 6, 2024.
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 395
- Avg merge
- 14h 7m
- Merged PRs (30d)
- 5
Description
Is your request related to a problem? Please describe.
there are obviously many ways someone can break an OAB directory configuration
a nice feature add to HealthChecker.ps1 tool would be to some basic checks of sane/modern configuration settings
Describe The Request
suggestion would be some OAB configuration health validation
e.g.
- does an OAB exist?
- has it been updated recently?
- is an external URL value present?
- is an internal URL value present?
- do the URLs use https://? (probably should flag an http:// url at this point)
- is global web distribution enabled?
- is shadow distribution enabled?
- authentication mechanisms might be worth listing (i've seen OAuth getting enabled on for OabVirtualDirectory even when its not supported in the environment)
- (i feel like there are some other commonly misconfigured OAB related items i'm not remembering here)
Additional context
OAB is an example of a neglected service that is mostly out of sight and often misconfigured IME.
the HealthChecker.ps1 script has done a great job surfacing other items like this and i think there is some opportunity to add some functionality to the tool to help folks find some less obvious configuration issue they might want to tune
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.