we have the problem which is described in McAfee KB85252. Solution 1: Update to ePO 5.1.3, solution 2: Update to ePO 5.3.1
The current ePO Version we us is ePO 5.1.3 Build 188 and the last update we did was the last HF for ePO 5.1.3 (Java Update), provided by McAfee via the Downloadsection via valid grant number. So: What to do when solution 1 is in place and we do not want to install 5.3.1? Any suggestions which could prevent us from opening a Service Request?
But at least we do know now our Update Check is flawed and we have to add controlling the query and report section after every update.
5.1.3 does not fix it for me either. I think they transposed the numbers and really meant 5.3.1, not 5.1.3.
If you look at the end of the KB there are 2 solutions. One stating 5.1.3 and the other 5.3.1.
I don't recall what the last minor build in 5.1.3 is without looking but are you on the last update?
Build 188 is the only 5.1.3 build that shows under the list of patches for ePO 5.1, and that's what I'm running (same as the original poster).
Maybe 5.1.4 will fix it, but that seems to be taking forever to release.
hmm I didnt even know 5.1.4 was a thing.
Why the hesitation to go to 5.3.1? It is an extremely seamless upgrade..
Yes, there are several KB articles going back to late 2015 referencing issues expected to be fixed in ePO 5.1.4
Either way, personally I'm waiting for an even newer release that fixes the SHA1 certificate issue.