Handle missing ExSetup on server#1971
Merged
Merged
Conversation
lusassl-msft
approved these changes
Feb 7, 2024
dpaulson45
force-pushed
the
dpaul-HcMissingExSetup
branch
from
6462206 to
50bb2a3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue:
See linked issue
Reason:
Want Health Checker attempt to complete, then display if we weren't able to find the ExSetup.
Fix:
Use
AdminDisplayVersionfromGet-ExchangeServerto get the build information. While this doesn't get the security updates, it will allow the script to continue. Then we will call out in the display if theExSetup.exewas not found.Resolved #1692
Validation:
Lab tested