Skip to content

Write down error when incorrect cores values are present#876

Merged
dpaulson45 merged 5 commits into
mainfrom
dpaul-FixCoreError
Jan 31, 2022
Merged

Write down error when incorrect cores values are present#876
dpaulson45 merged 5 commits into
mainfrom
dpaul-FixCoreError

Conversation

@dpaulson45
Copy link
Copy Markdown
Member

Issue:
In the text file, we didn't state if something was wrong on Exchange 2016 when on 48 cores. Looking over the code, we just color code it as Yellow and don't draw any attention to it.

Reason:
On Exchange 2013 and 2016, if you have over 24 cores that is a problem. On Exchange 2019, if you have over 48 cores, that is also a problem that needs to be called out more clearly in the text files.

Fix:
Appended - Error when we are over the value per Exchange Server version and changed the display color to be Red instead as it is an error.

Resolved #848

Need to write a core error when over 24 cores for Exchange 2013 and 2016. Then over 48 cores when on Exchange 2019.
lusassl-msft
lusassl-msft previously approved these changes Jan 31, 2022
Decided to do a full check on this. Only needs to be done inside of the logic cores as you can't have more physical cores vs logical cores.
@dpaulson45 dpaulson45 merged commit 008deff into main Jan 31, 2022
@dpaulson45 dpaulson45 deleted the dpaul-FixCoreError branch January 31, 2022 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Issue] - Health Checker does not throw error when on Exchange 2016 with 48 cores

2 participants