Fix Exchange versions on UM mitigation#439
Merged
Merged
Conversation
erinIs1337
approved these changes
Apr 10, 2021
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:
Code contains a comment that UM mitigation is skipped for Exchange 2019. That code specifically seeks Exchange 2013 and skips Exchange 2016.
Reason:
As per version listing:
https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019
Exchange 2016 is 15.1.x. The existing "not like 15.0" check meant UM would not apply. The fact it does so silently is a problem for troubleshooting.
Fix:
Replace with a match on 15.0 and 15.1. Added a verbose log.
Validation:
I have run this on an Exchange 2016 (15.1.2176.9) server.