This repository has been archived by the owner on Apr 20, 2020. It is now read-only.
Add initial support for Exchange 2019 #36
Conversation
This file contains 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
Added basic support for Exchange 2019 detection and handling change in ContentIndex state.
|
Is ContentIndexState=Applicable expected in Exchange 2019 due to the new search engine (Big Funnel)? |
|
I think so yes, I believe the change is due them moving the Content Index State from being a Database level feature (where it has to be in sync as part of a DAG), to being at the mailbox level. https://www.codetwo.com/admins-blog/whats-new-in-exchange-2019/#search |
|
thanks for this, was very useful for a current 2019 deployment |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Added basic support for Exchange 2019 detection and handling ContentIndexState no longer existing in Exchange 2019 - when you query it from Exchange 2019 it reports back as NotApplicable but when you query from an Exchange 2013 server it returns ContentIndexState as 11 instead so I have caught both of these.
I've not tested on 2016 as I don't run this, presumably it will return as either 2013 or 2019 do though.
Currently I'm just reporting 2019's ContentIndexState as just Healthy so it shows nicely as green but I guess this could be changed to show as Not Applicable and still show as green if preferred (this was just a quick hack to get the report working).