Check for Exchange Organization Hybrid Configuration#604
Merged
Conversation
dpaulson45
requested changes
Jun 3, 2021
Code optimizations
lusassl-msft
force-pushed
the
lusassl-HybridWork
branch
from
839e717 to
50ecc3c
Compare
dpaulson45
approved these changes
Jun 4, 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.
Description:
This is the first draft of the Exchange Organization Hybrid Configuration implementation. We query the information via
Get-HybridConfigurationand store the results inpublic class ExchangeInformationaspublic object GetHybridConfiguration;.We only run the validation of these values when the server is no Edge Transport server and Exchange version is greater or equal Exchange2013. We simply skip the checks when no Hybrid Configuration is available.
Work item #539
Validation:
Validated in Exchange 2016 Hybrid lab with Edge Transport server in place; possible Pester unit test case