Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HealthChecker - [New Check] Check installed UCMA version #535

Closed
dpaulson45 opened this issue Apr 26, 2021 · 8 comments
Closed

HealthChecker - [New Check] Check installed UCMA version #535

dpaulson45 opened this issue Apr 26, 2021 · 8 comments

Comments

@dpaulson45
Copy link
Member

Creating an issue to track this pending investigating of UCMA version.

Original Request:

Describe the issue
Currently Microsoft offers UCMA 4.0 as required for a 2013/2016/2019 Exchange installation.
UCMA 4.0 is outdated and not supported anymore on Server 2016 and 2019.
UCMA 6.0 is the latest supported version (which currently has some issues which Microsoft does not seem to have fixed)

Additional context
Source: https://docs.microsoft.com/en-us/answers/questions/167684/exchange-2016-exchange-2019-wrong-recommendations.html

Migrated From: https://github.com/dpaulson45/HealthChecker/issues/538

@JustinHoeky
Copy link

Hi @lusassl-msft ,
Any news on this topic?
We talked about this one in March https://github.com/dpaulson45/HealthChecker/issues/538

@Karl-WE
Copy link

Karl-WE commented Jun 29, 2021

@JustinHoeky unfortunately haven't received any feedback from the Exchange Team yet on the Microsoft Q&A or Microsoft Techcommunity forums. Also Exch Docs.microsoft.com are not connected publicly to github so one could create an issue or PR for updating the documentation.
My main concern is still the wrong hardcoded C++ Redist on UCMA 6.0 setup. I have few hope that someone could change it from = to >= in the MSI. It would be easy though not sure who can be asked / is responsible.

Also unclear what is the need for the UCMA anyway as Skype for Business is dead. I am not sure if Teams in a Exchange Hybrid would still need it.

@lusassl-msft
Copy link
Contributor

lusassl-msft commented Jun 30, 2021

@JustinHoeky it's still under investigation. Until it is clarified you should use UCMA 4.0 (as stated in the prerequisites: https://docs.microsoft.com/en-us/exchange/plan-and-deploy/prerequisites?view=exchserver-2019#exchange-2019-mailbox-servers-on-windows-server-2019).
We also ship this version with the Exchange bits (version which can be used on Server 2019 Core) and use it to run unit tests in development etc. . Keep you posted when I have more recent information on this topic.

@Karl-WE
Copy link

Karl-WE commented Sep 4, 2021

Hi @lusassl-msft any news from the Exchange Team on this?

Karl-WE added a commit to Karl-WE/OfficeDocs-Exchange that referenced this issue Sep 4, 2021
UCMA 4.0 is not supported on modern OS as by requirements of Exchange 2016 or 2019 and .net 4.8 by information of MS download pages.
please check with: microsoft/CSS-Exchange#535
Karl-WE added a commit to Karl-WE/OfficeDocs-Exchange that referenced this issue Sep 4, 2021
As described in the download description UCMA 4.0 is not supported on OS that would qualify the requirements of Exchange 2016 or 2019 or later, nor is compatible for .net 4.8
references: microsoft/CSS-Exchange#535
@Karl-WE
Copy link

Karl-WE commented Sep 9, 2021

Hi @lusassl-msft @dpaulson45 good news. UCMA 4.0 is not the correct version for Exchange Server 2016 and 2019. My doubts seem to be about right.
Exchange Team signed off my PR on docs.
https://github.com/MicrosoftDocs/OfficeDocs-Exchange/pull/2771#event-5280924630

@tiburd
Copy link

tiburd commented Sep 10, 2021

@Karl-WE - The Exchange team noticed your change and asked me to revert it:

AFAIK the 6.0 version was not yet tested with Exchange so I'd strongly recommend reverting the change.
We still ship UCMA 4.0 by default with Exchange 2019 and our testing is done by using UCMA 4.0.

It was reverted in this PR, and a note has been added that states UCMA 4.0 must be used even if the documentation for UCMA 4.0 stated that it's not supported with Windows server 2016/2019.

@Karl-WE
Copy link

Karl-WE commented Sep 10, 2021

I am fine to close this PR @dpaulson45

@dpaulson45
Copy link
Member Author

If this changes, we will make sure we update the script to handle it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants