question

Karl-WE avatar image
0 Votes"
Karl-WE asked ·

Exchange 2016 / Exchange 2019 wrong recommendations on Unified Communications Managed API

Today I noticed something very weird. The official docs still links UCMA as a prerequisite for EX2016 and EX2019 on-premises. The linked version 4.0 is not even supported for later .net versions in compliance with Exchange Compat matrix and UCMA 4.0 is not supported on Windows Server 2012 R2, Windows Server 2016 or Windows Server 2019.

The one that is supported is UCMA 6.0. Which is not mentioned in the docs or prerequisite checks.

A customer Exchange 2016 was stuck on downloading updates via sconfig at KB3175339 (Sec fix for UCMA 4.0) which is listed in catalog but the download is no longer available.

He is running Exchange Server 2016 CU 18 on Server 2016 LTSC. CU 18 or previous CUs never mentioned to check for the outdated version of UCMA 4.0, nor did Microsoft update them.

Installing UCMA 6.0 was not an easy task though. Even when all named prerequisites are met the installer will quit after specifying the install path.
Reason was found in the installer logs.
The UCMA Setup tries to Install C++ Redist 2015-2019 x64 package version 14.12.x which is heavily outdated. Unfortunately the one that did the package for UCMA did a wrong hardcoded version check.

So it required me uninstall UCMA 4.0 that's ok.

But it also required me to uninstall C++ Redist 2015-2019 x64
I would like to recommend anyone involved with packaging / assembling installers: never do hardcode version checks with version equal % but with equal or higher %, please.
The current and secure version is C++ 2015-2019 Version 14.28.x


2 Questions:
why no one care to update the docs for UCMA 6.0 and actually reading the requirements on the download page
why no one cared to update UCMA with Exchange CUs while it is a prereq for Exchange?

UCMA 4.0 requirements
40789-image.png

UCMA 5.0 requirements
40914-image.png

UCMA 6.0 requirements
40941-image.png



office-exchange-server-itpro
image.png (97.3 KiB)
image.png (103.7 KiB)
image.png (76.3 KiB)
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BodisHS avatar image
0 Votes"
BodisHS answered ·

Any news on this @Karl-WE ?
Seems to me that Microsoft did not even take a look at this so far.

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BodisHS avatar image
0 Votes"
BodisHS answered ·

Just spoke to Christian from Microsoft support which suggested me to install C++ 2008, since that the best and only solution for this issue.
I have absolutely no clue why they would even consider saying anything like this.

Will try it once more tommorow to see if I can talk to someone else on this matter.

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BodisHS avatar image
0 Votes"
BodisHS answered ·

Sorry for all the messages.
Got a reply on the GitHub of the HealthCheck script of last week Exchange vulnerabilities.
They (Microsoft) will check internally with their Exchange team.

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

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Karl-WE avatar image
0 Votes"
Karl-WE answered ·

C++ 2008 is officially out of support
no need to be sorry. I am still waiting for a response from MSFT.

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.